// pns-case-data.jsx — Case study content, written for search + AI-answer visibility.
// Each entry drives one indexable page at /case-studies/<slug>/
// Structure follows current SEO practice: answer-first summary, entity-rich
// headings, quantified results, and FAQ/Article/Breadcrumb schema.

const PNS_CASES = {

'hipaa-network-security-medical-group': {
  cat:'Cybersecurity', catColor:'#e8714a',
  title:'HIPAA-Compliant Network Security for a 4-Location Medical Group',
  metaTitle:'HIPAA Network Security Case Study | Medical Group IT | Premier Network Solutions',
  metaDesc:'How a Southern California medical group with four clinics closed 31 HIPAA security gaps, cut incident response from days to minutes, and passed audit — in 11 weeks.',
  keywords:'HIPAA compliant IT services, healthcare cybersecurity Southern California, medical practice IT support, HIPAA risk assessment, EHR security',
  heroImg:'1695668548342-c0c1ad479aee',
  heroAlt:'Clinical network operations dashboard monitoring a multi-site medical group',
  bodyImg:'1576091160399-112ba8d25d1d',
  bodyAlt:'Medical staff accessing patient records on a secured clinical workstation',
  client:{ industry:'Healthcare — Multi-Site Clinical Group', size:'4 locations · 120 staff · 38 clinicians', region:'Los Angeles & Orange County, CA', engagement:'11-week remediation, ongoing managed security' },
  summary:'A four-clinic medical group failed an internal HIPAA readiness review with 31 open findings across endpoint security, access control, and audit logging. Premier Network Solutions rebuilt the security architecture around a zero-trust access model, deployed 24/7 SOC monitoring, and produced the documented evidence set the group needed. All 31 findings were closed in 11 weeks; mean time to detect a security event dropped from 4 days to under 9 minutes.',
  challenge:[
    'Patient records were reachable from any workstation on a flat network. A single compromised front-desk PC would have exposed the full EHR database across all four clinics.',
    'There was no centralized audit logging. When a suspicious login was reported, the practice manager had no way to reconstruct who accessed which record, which alone would have failed a HIPAA audit.',
    'Nine legacy imaging workstations ran an unsupported operating system that could not be patched, and clinicians shared four generic logins for after-hours access.',
  ],
  solution:[
    { h:'Network segmentation and zero-trust access', p:'We separated clinical, administrative, guest, and medical-device traffic into isolated VLANs with firewall policy between each. Access to the EHR now requires an identity, a managed device, and multi-factor authentication — no exceptions, including for on-site staff.' },
    { h:'Endpoint detection and 24/7 SOC monitoring', p:'EDR agents were deployed to every endpoint and server, feeding a SIEM watched around the clock by our Security Operations Center. Ransomware behavior triggers automatic host isolation before encryption spreads laterally.' },
    { h:'Identity cleanup and per-clinician credentials', p:'Shared logins were eliminated. Every clinician received an individual identity with role-based permissions, conditional access rules by location and device, and automatic session expiry on shared clinical workstations.' },
    { h:'Isolating unpatchable medical devices', p:'The nine legacy imaging workstations were placed behind a dedicated, tightly filtered segment with allow-listed destinations — keeping the imaging hardware in service without leaving an unpatched attack path into the clinical network.' },
    { h:'Audit evidence and documentation', p:'We produced the full HIPAA Security Rule evidence set: risk analysis, policies, access reviews, log retention configuration, and an incident response plan the practice manager can actually run.' },
  ],
  results:[
    { n:'31', s:'', l:'HIPAA findings closed', d:'Every finding from the readiness review remediated and documented within the engagement.' },
    { n:'9', s:' min', l:'Mean time to detect', d:'Down from roughly 4 days, measured across simulated and live security events.' },
    { n:'100', s:'%', l:'MFA coverage', d:'All clinical and administrative accounts, including after-hours and remote access.' },
    { n:'0', s:'', l:'Downtime during cutover', d:'Segmentation and identity migration completed across four clinics without a lost appointment slot.' },
  ],
  tech:['Fortinet next-generation firewall','VLAN segmentation','Microsoft Entra ID conditional access','SentinelOne EDR','24/7 SOC + SIEM','Immutable encrypted backup','Phishing simulation and staff training'],
  quote:{ t:'The audit evidence alone would have taken our office manager a year. What actually changed day to day is that we finally know who touched which record, and we know within minutes if something is wrong.', a:'Practice Administrator', c:'Multi-site medical group, Orange County' },
  faqs:[
    { q:'Does a small medical practice really need this level of security?', a:'Yes. HIPAA obligations do not scale down with headcount, and small clinics are targeted precisely because attackers expect weaker controls. A single exposed EHR database triggers the same breach notification requirements for a four-clinic group as for a hospital system.' },
    { q:'How long does HIPAA security remediation usually take?', a:'For a practice of this size, 8 to 14 weeks is typical. The technical work — segmentation, EDR, identity — moves faster than most people expect. Producing defensible documentation and completing staff training is what sets the timeline.' },
    { q:'Can you secure medical devices that cannot be patched?', a:'Yes. Imaging and diagnostic hardware often runs vendor-locked software that cannot be updated. We isolate those devices on a restricted segment with allow-listed destinations, so the device stays in clinical service without becoming an entry point into the wider network.' },
    { q:'What happens if a ransomware attack still gets through?', a:'Our SOC isolates the affected host automatically, and recovery runs from immutable backups that ransomware cannot encrypt or delete. The incident response plan we document names who decides what, so the first hour is not spent deciding who is in charge.' },
  ],
  related:['cybersecurity','managed-it','backup-monitoring'],
},

'azure-cloud-migration-professional-services': {
  cat:'Cloud Services', catColor:'#2bb5a0',
  title:'Azure Cloud Migration for a 50-User Professional Services Firm',
  metaTitle:'Azure Cloud Migration Case Study | 50-User Firm | Premier Network Solutions',
  metaDesc:'A Southern California professional services firm retired its aging on-premise server room, moved 50 users to Azure over a single weekend, and cut infrastructure spend 34% annually.',
  keywords:'Azure migration Southern California, cloud migration services SMB, server room replacement, hybrid cloud consulting, business cloud services',
  heroImg:'1506399558188-acca6f8cbf41',
  heroAlt:'Cloud infrastructure architecture visualized across distributed data centers',
  bodyImg:'1451187580459-43490279c0fa',
  bodyAlt:'Global network connectivity representing distributed cloud workloads',
  client:{ industry:'Professional Services', size:'50 users · 2 offices', region:'Southern California', engagement:'9-week migration, ongoing cloud management' },
  summary:'A professional services firm was running its practice on two aging on-premise servers, both out of warranty, in a converted storage closet with a single failing air conditioner. Premier Network Solutions migrated all workloads to Microsoft Azure across one weekend cutover. The firm eliminated its server room entirely, reduced annual infrastructure cost by 34%, and gained full remote access for every user without a VPN client.',
  challenge:[
    'Both production servers were past end of warranty. A motherboard failure would have taken the firm offline for days while replacement hardware was sourced.',
    'Remote work depended on a legacy VPN appliance that supported 12 concurrent sessions for a 50-person firm — a hard ceiling the business had already outgrown.',
    'Backups ran to a USB drive that someone was supposed to swap weekly. It had not been swapped in seven months, and no restore had ever been tested.',
  ],
  solution:[
    { h:'Assessment and right-sizing before anything moved', p:'We profiled six weeks of actual CPU, memory, and I/O usage rather than matching existing hardware specs. Right-sizing to real demand is where most of the cost savings came from — the on-premise servers were roughly three times larger than the workload required.' },
    { h:'Identity first, workloads second', p:'Microsoft Entra ID was established and synchronized ahead of the migration, so users kept one set of credentials throughout. Single sign-on and conditional access replaced the VPN concurrency limit with policy-based access from any location.' },
    { h:'Single-weekend cutover with a tested rollback', p:'Data was pre-seeded and synchronized for two weeks before the cutover. The final delta sync, DNS change, and validation ran Friday evening through Sunday. A documented rollback path stayed available until Monday close of business.' },
    { h:'Backup that is actually verified', p:'Azure Backup with geo-redundant retention replaced the USB drive. Restores are tested on a monthly schedule and the results are reported to the firm — an untested backup is not a backup.' },
    { h:'Cost governance from day one', p:'Budget alerts, reserved instance planning, and monthly cost review were built into the handover, so cloud spend stays predictable instead of drifting upward unnoticed.' },
  ],
  results:[
    { n:'34', s:'%', l:'Lower annual infrastructure cost', d:'Versus the projected cost of replacing both servers and maintaining the server room.' },
    { n:'1', s:' weekend', l:'Total cutover window', d:'Users left Friday on the old environment and returned Monday to the new one.' },
    { n:'50', s:'', l:'Users with unrestricted remote access', d:'The 12-session VPN ceiling was removed entirely.' },
    { n:'99.9', s:'%', l:'Measured uptime since migration', d:'Sustained across the first full year of Azure operation.' },
  ],
  tech:['Microsoft Azure IaaS','Azure Files and Azure AD DS','Microsoft Entra ID with conditional access','Azure Backup, geo-redundant','Azure Site Recovery','Cost management and budget alerting'],
  quote:{ t:'We expected to lose a week. We lost a weekend. The part nobody warned us about is how much quieter the office is now that the server closet is gone.', a:'Managing Partner', c:'Professional services firm, Southern California' },
  faqs:[
    { q:'How much does an Azure migration cost for a 50-user business?', a:'Migration projects at this scale typically run as a fixed-scope engagement, with ongoing Azure consumption billed separately. The comparison that matters is against the true cost of staying on-premise: hardware refresh, warranties, power, cooling, and the downtime risk of aging equipment.' },
    { q:'Will our team need to learn new software after moving to Azure?', a:'For a lift-and-shift migration like this one, no. Users open the same applications and see the same files. What changes is where the workload runs and how access is granted — both invisible in daily use.' },
    { q:'What happens to our data during the migration?', a:'Data is replicated to the cloud environment and kept synchronized for weeks before cutover, so the final switch moves only the delta. The on-premise copy stays intact and untouched until the new environment has been validated in production.' },
    { q:'Is the cloud actually cheaper than owning servers?', a:'Only when workloads are right-sized and governed. Matching cloud instances to existing hardware specs is the most common reason cloud bills disappoint. We size to measured demand and set budget alerts before go-live.' },
  ],
  related:['managed-it','microsoft-365','backup-monitoring'],
},

'microsoft-365-deployment-teams-sharepoint': {
  cat:'Microsoft 365', catColor:'#3b82f6',
  title:'Complete Microsoft 365 Deployment with Teams, SharePoint, and SSO',
  metaTitle:'Microsoft 365 Deployment Case Study | Teams & SharePoint | Premier Network Solutions',
  metaDesc:'A full Microsoft 365 rollout — Exchange migration, SharePoint document architecture, Teams adoption, and Entra ID single sign-on — completed with zero mailbox downtime.',
  keywords:'Microsoft 365 migration Southern California, SharePoint implementation, Teams deployment, Entra ID SSO, M365 consulting SMB',
  heroImg:'1663596990274-3fc2f5a4ce27',
  heroAlt:'Team collaborating across Microsoft 365 applications on multiple devices',
  bodyImg:'1600880292203-757bb62b4baf',
  bodyAlt:'Staff training session on a new Microsoft 365 collaboration workspace',
  client:{ industry:'Multi-Department Services Business', size:'85 users · 6 departments', region:'Southern California', engagement:'7-week deployment with structured adoption program' },
  summary:'An 85-user business was running email on a hosted Exchange server, files on an aging network share, and informal team chat on three different consumer apps. Premier Network Solutions consolidated everything into Microsoft 365 with a designed SharePoint information architecture and single sign-on. Mailbox migration completed with zero downtime, and after eight weeks 94% of staff had moved off the legacy file share voluntarily.',
  challenge:[
    'Files lived in a 14-year-old folder tree nobody fully understood. Six departments had each invented their own naming conventions, and the same document often existed in four places with no way to tell which was current.',
    'Staff coordinated across three unmanaged consumer chat apps, meaning business conversations and shared documents sat outside company control with no retention or discovery capability.',
    'Every application had its own password. Helpdesk password resets were the single largest category of support tickets.',
  ],
  solution:[
    { h:'Information architecture before migration', p:'We did not lift the old folder tree into SharePoint. We mapped how each department actually works and designed a site and library structure around it, with metadata instead of nested folders — the single biggest factor in whether a SharePoint rollout is adopted or abandoned.' },
    { h:'Zero-downtime Exchange migration', p:'Mailboxes moved in staged batches using hybrid coexistence, so mail flowed correctly between migrated and unmigrated users throughout. No user experienced a mail outage or lost a calendar item.' },
    { h:'Teams structure with governance', p:'Teams were provisioned along real working groups with naming standards, guest-access policy, and lifecycle rules — preventing the sprawl of hundreds of abandoned teams that makes M365 unsearchable within a year.' },
    { h:'Single sign-on across every application', p:'Entra ID became the single identity for Microsoft 365, the line-of-business platform, and the CRM. One login, multi-factor protected, with conditional access by device and location.' },
    { h:'Adoption program, not just a rollout', p:'Department-specific training sessions, a two-week floor-walking period, and named internal champions per department. Deployment is the easy half; adoption is what determines whether the investment returns anything.' },
  ],
  results:[
    { n:'0', s:'', l:'Minutes of mailbox downtime', d:'All 85 mailboxes migrated in staged batches with hybrid coexistence.' },
    { n:'94', s:'%', l:'Staff off the legacy file share', d:'Measured eight weeks after go-live, without mandate or enforcement.' },
    { n:'71', s:'%', l:'Fewer password-reset tickets', d:'Single sign-on removed the largest recurring helpdesk category.' },
    { n:'3', s:' → 1', l:'Chat platforms consolidated', d:'Business conversations moved into a governed, discoverable environment.' },
  ],
  tech:['Exchange Online, hybrid migration','SharePoint Online with metadata architecture','Microsoft Teams with lifecycle governance','Microsoft Entra ID SSO and MFA','OneDrive known-folder redirection','Purview retention policy'],
  quote:{ t:'The training is what made it stick. We had tried SharePoint once before on our own and everyone quietly went back to the old drive within a month.', a:'Director of Operations', c:'Multi-department services business' },
  faqs:[
    { q:'How long does a Microsoft 365 migration take for 85 users?', a:'Six to eight weeks is realistic for a full deployment including Exchange, SharePoint, Teams, and single sign-on. Mailbox migration is the fastest part. Designing the document architecture and running proper adoption training is where the time is genuinely well spent.' },
    { q:'Will we lose email during the migration?', a:'No. A staged hybrid migration keeps mail flowing correctly between migrated and unmigrated mailboxes throughout the cutover. Users typically notice nothing beyond a one-time Outlook profile restart.' },
    { q:'Should we move our existing folder structure into SharePoint?', a:'Almost never. Lifting a legacy folder tree into SharePoint is the most common reason these projects fail — it imports the confusion along with the files. SharePoint works best with a flatter structure and metadata, which requires designing the architecture around how departments actually work.' },
    { q:'Do we still need third-party backup with Microsoft 365?', a:'Yes. Microsoft protects the platform, not your data against accidental deletion, malicious insiders, or ransomware that syncs to the cloud. Retention policies are not backups, and default retention windows are shorter than most businesses assume.' },
  ],
  related:['microsoft-365','managed-it','cybersecurity'],
},

'enterprise-network-infrastructure-wifi6-sdwan': {
  cat:'Network Infrastructure', catColor:'#e8714a',
  title:'Enterprise Network Rebuild: Structured Cabling, Wi-Fi 6, and SD-WAN',
  metaTitle:'Enterprise Network Infrastructure Case Study | Wi-Fi 6 & SD-WAN | Premier Network Solutions',
  metaDesc:'A three-floor office complex replaced failing cabling and consumer access points with structured Cat6A, Wi-Fi 6, and SD-WAN — eliminating dead zones and daily dropouts.',
  keywords:'structured cabling Southern California, Wi-Fi 6 installation business, SD-WAN implementation, office network design, commercial network cabling',
  heroImg:'1558618666-fcd25c85cd64',
  heroAlt:'Structured network cabling terminated in an organized enterprise rack',
  bodyImg:'1544197150-b99a580bb7a8',
  bodyAlt:'Server room with enterprise switching and structured cable management',
  client:{ industry:'Multi-Tenant Commercial Office', size:'3 floors · 140 desks · 2 sites', region:'Southern California', engagement:'6-week phased installation, out of hours' },
  summary:'A three-floor office complex was running 140 desks on partially undocumented Cat5e cabling installed in stages over a decade, with consumer-grade wireless access points added wherever someone complained. Video calls dropped daily and the second site connected over a consumer broadband line with no failover. Premier Network Solutions rebuilt the physical layer with Cat6A structured cabling, designed Wi-Fi 6 coverage from an on-site RF survey, and linked both sites with SD-WAN and automatic failover.',
  challenge:[
    'Cabling had been added floor by floor over ten years with no documentation. Tracing a single fault meant physically following a cable through the ceiling.',
    'Fourteen consumer access points on overlapping channels were interfering with each other. Adding more had made coverage worse, not better.',
    'The second site ran on a single consumer broadband circuit. When it failed — roughly monthly — that office simply stopped working until the provider restored service.',
  ],
  solution:[
    { h:'Full physical layer rebuild with documentation', p:'Cat6A structured cabling throughout, terminated into properly organized racks, with every run labeled at both ends and recorded in as-built documentation. Future faults are traced from a diagram, not from a ladder.' },
    { h:'Wi-Fi 6 designed from an actual RF survey', p:'We ran a predictive and on-site survey before specifying a single access point. Coverage was designed around the building materials and real desk density — which is why fewer, correctly placed access points outperformed the fourteen that were there before.' },
    { h:'SD-WAN with automatic failover', p:'Both sites now run a primary business circuit with an independent secondary path. Failover is automatic and sub-second, so a carrier outage no longer stops work. Voice and video traffic are prioritized by policy.' },
    { h:'Segmentation built into the design', p:'Corporate, guest, voice, and IoT traffic are separated at the network layer from day one. Retrofitting segmentation later is significantly more disruptive than designing it in.' },
    { h:'Phased, out-of-hours installation', p:'Work ran floor by floor outside business hours, with each floor cut over and validated before the next began. No department lost a working day.' },
  ],
  results:[
    { n:'0', s:'', l:'Wireless dead zones remaining', d:'Verified by post-installation site survey across all three floors.' },
    { n:'<1', s:' sec', l:'Failover time between circuits', d:'Carrier outages no longer interrupt work at either site.' },
    { n:'140', s:'', l:'Desks recabled and documented', d:'Every run labeled at both ends with as-built diagrams delivered.' },
    { n:'0', s:'', l:'Business days lost to installation', d:'Phased floor-by-floor cutover ran entirely outside business hours.' },
  ],
  tech:['Cat6A structured cabling','Wi-Fi 6 access points, survey-designed','Managed PoE+ switching','SD-WAN with dual-circuit failover','Next-generation firewall','VLAN segmentation for voice, guest, and IoT'],
  quote:{ t:'We had spent three years buying access points to fix a cabling problem. One survey told us what nobody had bothered to check.', a:'Facilities Director', c:'Commercial office complex, Southern California' },
  faqs:[
    { q:'Do we need Cat6A, or is Cat6 enough?', a:'Cat6 handles current gigabit needs. Cat6A supports 10 gigabit over full distance and is the sensible choice when walls are already open, because the incremental cost is small compared to the labor of pulling cable twice.' },
    { q:'Why did adding more access points make our Wi-Fi worse?', a:'Access points on overlapping channels interfere with each other. Beyond a certain density, each additional unit adds noise rather than coverage. This is why proper wireless deployment starts with an RF survey rather than a device count.' },
    { q:'What is SD-WAN and does a small business need it?', a:'SD-WAN intelligently steers traffic across multiple internet circuits and fails over automatically when one degrades. Any business where an internet outage stops work — which now means nearly all of them — gets a direct return from it.' },
    { q:'How disruptive is a network installation?', a:'Properly phased, it is not. We cable and cut over one floor or department at a time, outside business hours, validating each phase before starting the next. In this project no department lost a working day.' },
  ],
  related:['network-infrastructure','managed-it','cybersecurity'],
},

'ai-workflow-automation-data-entry': {
  cat:'AI Solutions', catColor:'#2bb5a0',
  title:'AI Workflow Automation That Removed 70% of Manual Data Entry',
  metaTitle:'AI Workflow Automation Case Study | 70% Less Data Entry | Premier Network Solutions',
  metaDesc:'How intelligent document processing and workflow automation eliminated roughly 70% of manual data entry for a Southern California operations team — with a 4-month payback.',
  keywords:'AI automation for small business, intelligent document processing, workflow automation Southern California, Power Automate consulting, business process automation',
  heroImg:'1682562031269-58a59c81432c',
  heroAlt:'Automated data processing pipeline visualized as connected workflow nodes',
  bodyImg:'1639066648921-82d4500abf1a',
  bodyAlt:'Operations team reviewing an automated document processing dashboard',
  client:{ industry:'Distribution and Operations', size:'~2,300 documents processed monthly', region:'Southern California', engagement:'10-week phased automation build' },
  summary:'An operations team was rekeying roughly 2,300 supplier documents a month by hand from PDFs and email attachments into their ERP — three full-time equivalents of typing, with a persistent error rate that caused downstream billing disputes. Premier Network Solutions built an intelligent document processing pipeline with human review on low-confidence extractions. Manual entry dropped by about 70%, error rates fell sharply, and the build paid for itself in four months.',
  challenge:[
    'Supplier documents arrived in dozens of formats — PDFs, scans, spreadsheets, and text in email bodies — with no consistent structure to key from.',
    'Typing errors surfaced weeks later as billing disputes, and reconciling them cost more staff time than the original entry did.',
    'A previous automation attempt using rigid templates broke whenever a supplier changed their document layout, and had been quietly abandoned.',
  ],
  solution:[
    { h:'Process mapping before any automation', p:'We measured where the hours actually went. Two document types accounted for 68% of the manual effort, so those were automated first. Automating the wrong step produces impressive demonstrations and no savings.' },
    { h:'Intelligent extraction, not rigid templates', p:'The pipeline uses AI document understanding rather than fixed coordinate templates, so it handles layout variation between suppliers — the exact failure mode that killed the previous attempt.' },
    { h:'Confidence thresholds with human review', p:'Every extracted field carries a confidence score. High-confidence records post automatically; anything below threshold routes to a review queue with the source document displayed alongside. Staff verify rather than retype.' },
    { h:'Direct ERP integration', p:'Validated records write straight into the ERP through its API. No intermediate spreadsheet, no copy-paste step, no second place for data to drift out of sync.' },
    { h:'Exception handling and monitoring', p:'Failed extractions, new document formats, and unusual values raise alerts rather than failing silently. Accuracy is reviewed monthly and thresholds are tuned as the system learns each supplier.' },
  ],
  results:[
    { n:'70', s:'%', l:'Reduction in manual data entry', d:'Measured across the two highest-volume document types.' },
    { n:'2,300', s:'', l:'Documents processed monthly', d:'Handled without adding operations headcount.' },
    { n:'4', s:' months', l:'Payback period', d:'Recovered labor cost against total build and licensing spend.' },
    { n:'96', s:'%', l:'Straight-through processing rate', d:'Records posting automatically without human review.' },
  ],
  tech:['Azure AI Document Intelligence','Microsoft Power Automate','ERP API integration','Confidence-scored human review queue','Exception alerting and monitoring','Monthly accuracy reporting'],
  quote:{ t:'The review queue is what sold the team on it. Nobody was asked to trust a black box — they check what the system is unsure about, and it is unsure about less every month.', a:'Operations Manager', c:'Distribution business, Southern California' },
  faqs:[
    { q:'Is AI automation realistic for a small business?', a:'Yes, when it targets a specific high-volume, repetitive process with a measurable cost. The projects that fail are the open-ended ones. The projects that pay back are narrow: one document type, one workflow, one measurable number.' },
    { q:'What happens when the AI extracts something incorrectly?', a:'Every field carries a confidence score. Anything below threshold routes to a human review queue with the source document shown alongside, so staff verify rather than retype. Confident records post automatically.' },
    { q:'How long before an automation project pays for itself?', a:'For document-heavy processes at this volume, four to nine months is typical. The calculation is straightforward: hours recovered per month against build cost plus ongoing licensing.' },
    { q:'Will automation replace our staff?', a:'In this engagement it did not. The team stopped retyping and started handling exceptions, supplier relationships, and reconciliation — work that was previously being squeezed out by data entry.' },
  ],
  related:['ai-solutions','it-consulting','managed-it'],
},

};

window.PNS_CASES = PNS_CASES;
window.PNS_CASE_ORDER = ['hipaa-network-security-medical-group','azure-cloud-migration-professional-services','microsoft-365-deployment-teams-sharepoint','enterprise-network-infrastructure-wifi6-sdwan','ai-workflow-automation-data-entry'];