/* ===================================================== SOLUTIONS — hub + 7 detail pages Brief §15–§19 Template: Hero · Problem · What Cortexa does · Modules · Industries · CTA ===================================================== */ /* --- Data: one entry per solution -----------------------------------*/ const SOLUTION_GROUPS = [ { label: 'Safety & Compliance', accent: 'var(--coral)', slugs: ['permit-to-work', 'alarm-response', 'incident-detection'], }, { label: 'Operations & Procedure', accent: 'var(--teal)', slugs: ['procedural-compliance', 'shift-handover'], }, { label: 'Extensibility & Analytics', accent: 'var(--amber)', slugs: ['custom-detection', 'multilingual-operations'], }, ]; const SOLUTIONS = { 'permit-to-work': { n: '16', eyebrow: 'SOLUTION — PERMIT-TO-WORK & CONFINED-SPACE COMPLIANCE', title: 'Permit-to-work, verified in conversation.', short: 'Every permit communication watched, every breach surfaced with playable evidence.', subhead: 'Every permit-to-work and confined-space entry generates a sequence of radio communications — issuance, watcher confirmation, status updates, closure. Cortexa watches every one of them, confirms the right communications happened, and flags it the moment they didn’t.', problem: 'Permits live on paper or in your permit system. The actual safety happens on radio — and that’s where most breaches go unrecorded today. A watcher who wasn’t named, a confined-space entry that wasn’t acknowledged, a permit closure that was never radioed in — these are the gaps that drive incidents, and they’re invisible to your current systems.', outcomes: [ { t: 'Detects every permit-to-work issuance', b: 'spoken on radio, in any supported language, and links it to the relevant permit record.' }, { t: 'Verifies the named watcher', b: 'is acknowledged on the channel.' }, { t: 'Flags conflicting permits', b: '— hot work near a permit-to-work area, simultaneous confined-space entries on the same channel without correct handover.' }, { t: 'Tracks closure', b: '— open permits with no closure communication by end of shift are flagged automatically.' }, { t: 'Produces audit-ready records', b: '— every detection, every supervisor decision, every closure, with the original audio and transcripts.' }, ], modules: ['voice', 'safe', { slug: 'signal', label: 'Cortexa Signal · optional', note: 'For site-specific permit variants' }], industries: ['energy', 'energy', 'mining', 'construction', 'aviation'], industryLabels: ['Energy & Utilities', 'Oil & Gas', 'Mining', 'Construction & Heavy Industry', 'Aviation (FOD permits, ramp area control)'], accent: 'var(--coral)', photoHero: 'assets/promise-01-permit.png', photoHeroCorner: ['', 'PERMIT BOARD'], photoDetail: null, photoDetailTag: 'GLOVED HAND · PERMIT + RADIO', }, 'procedural-compliance': { n: '17', eyebrow: 'SOLUTION — PROCEDURAL COMMUNICATION COMPLIANCE', title: 'The right words, in the right order, every time.', short: 'Real-time verification of procedural radio communication, not quarterly audit.', subhead: 'Operator rounds, startup and shutdown procedures, switching, and emergency drills depend on specific communications happening in a specific order. Cortexa verifies them — and tells you within minutes when they don’t.', problem: 'Procedural compliance is measured by audit, not by observation. By the time a regulator or internal auditor notices that operator rounds are slipping or that startup checklists aren’t being followed on the radio, it’s already a quarterly trend — not an actionable signal. Cortexa moves this from quarterly audit to real-time verification.', outcomes: [ { t: 'A structured checklist', b: 'of expected communications, defined once for any monitored procedure.' }, { t: 'Automatic activation', b: 'on trigger phrases — "starting Unit 4", "beginning rounds", "switching to position 2".' }, { t: 'Checkpoint-level verification', b: 'against the actual transmission — what was said, by whom, in what order.' }, { t: 'Substantiated, not just claimed', b: '— the system grounds every confirmation in playable evidence.' }, { t: 'Pass / partial / not-completed verdict', b: 'with attached transcripts and a structured record for audit.' }, ], modules: ['voice', 'ops', { slug: 'signal', label: 'Cortexa Signal · optional', note: 'For custom procedure definitions' }], industries: ['energy', 'energy', 'aviation', 'mining'], industryLabels: ['Energy & Utilities', 'Oil & Gas', 'Aviation (ground handling, MRO)', 'Mining'], accent: 'var(--teal)', photoHero: 'assets/solution-procedural-hero.png', photoHeroCorner: ['', 'PROCEDURE BINDER'], photoDetail: null, photoDetailTag: 'CHECKLIST · LINE ILLUSTRATION', }, 'shift-handover': { n: '18', eyebrow: 'SOLUTION — SHIFT HANDOVER INTEGRITY', title: 'Nothing falls between shifts.', short: 'Structured, multilingual handover summaries generated from the actual radio record.', subhead: 'Cortexa generates a structured handover summary at the end of every shift — open permits, in-progress work, unresolved incidents, equipment under maintenance — and verifies the incoming crew acknowledged it. In their own language.', problem: 'Shift handovers are where operational state is most likely to be lost. A near-miss reported but not formally closed; an open permit nobody mentioned; equipment isolated but never returned to service. Most operations rely on a paper logbook and a brief verbal handover — neither of which captures the actual radio traffic from the outgoing shift.', outcomes: [ { t: 'Automatic structured handover', b: 'generated from the full conversation record of the outgoing shift.' }, { t: 'Prioritised by what matters', b: '— safety events, unresolved incidents, open permits, and procedural slippages first.' }, { t: 'Delivered in each crew’s language', b: '— English, Arabic, Spanish, French, Dutch, German.' }, { t: 'Acknowledgement tracked', b: '— the incoming shift confirms receipt; open items not addressed by next shift are escalated.' }, { t: 'Searchable across shifts', b: '— the incoming crew can query the outgoing shift’s conversations in plain language.' }, ], modules: ['voice', 'ops'], industries: ['energy', 'energy', 'mining', 'emergency-services', 'defense'], industryLabels: ['Energy & Utilities', 'Oil & Gas', 'Mining', 'Emergency Services', 'Defense'], accent: 'var(--teal)', photoHero: 'assets/solution-handover-hero.png', photoHeroCorner: ['', 'SHIFT-CHANGE BOARD'], photoDetail: null, photoDetailTag: 'HANDOVER DOC + TABLET', }, 'alarm-response': { n: '19a', eyebrow: 'SOLUTION — GAS, FIRE & HAZARD ALARM RESPONSE', title: 'Every alarm acknowledged. Every response timed.', short: 'From the moment an alarm sounds to the moment it’s resolved — captured, timed, defensible.', subhead: 'When a gas, fire, or hazard alarm sounds, what happens next is a sequence of radio communications. Cortexa watches every one of them, times the response, captures the acknowledgement chain, and produces a structured record of the entire event.', problem: 'Today, post-event review of an alarm response is reconstructed from manual notes and partial audio logs. By the time the timeline is assembled — sometimes days later — the operational lesson has already faded. Cortexa makes the timeline available as the event happens.', outcomes: [ { t: 'Alarm-mention detection', b: 'across every channel, in every supported language.' }, { t: 'Acknowledgement timing', b: '— how long before the right operator acknowledged on the right channel.' }, { t: 'Response sequence capture', b: '— who was dispatched, who confirmed arrival, when the all-clear was given.' }, { t: 'Cross-channel correlation', b: '— a single event reconstructed across multiple talk-groups.' }, { t: 'Audit-ready records', b: 'with playable audio, transcripts, and a defensible timeline.' }, ], modules: ['voice', 'safe'], industries: ['energy', 'energy', 'mining', 'emergency-services'], industryLabels: ['Energy & Utilities', 'Oil & Gas', 'Mining', 'Emergency Services'], accent: 'var(--coral)', photoHero: 'assets/solution-alarm-hero.png', photoHeroCorner: ['', 'ALARM PANEL'], photoDetail: null, photoDetailTag: 'ALARM RESPONSE · STILL LIFE', v2: true, }, 'incident-detection': { n: '19b', eyebrow: 'SOLUTION — INCIDENT DETECTION & RECONSTRUCTION', title: 'Every incident, reconstructed end to end.', short: 'From the first radio transmission to the all-clear, in a single searchable record.', subhead: 'An incident is rarely contained to one channel or one conversation. Cortexa detects incidents from the language of the radio traffic, links every related transmission across channels and crews, and produces a single chronologically-ordered record ready for post-incident review.', problem: 'Post-incident review depends on supervisors manually reconstructing what happened from partial audio recordings, paper logs, and witness recollection. The reconstruction is slow, incomplete, and frequently disputed. Cortexa removes the manual work and the disputes.', outcomes: [ { t: 'Automatic incident detection', b: 'from operational language — "I need medical", "shut down the line", "evacuate", and dozens of site-specific signals.' }, { t: 'Cross-channel linking', b: '— every related transmission across every talk-group, in the order they happened.' }, { t: 'Multilingual reconstruction', b: '— Arabic, Spanish, French, Dutch, German transmissions transcribed and translated alongside the English.' }, { t: 'Roles and entities identified', b: '— who said what, on which channel, about which equipment.' }, { t: 'Exportable evidence-grade record', b: 'in your incident report templates, with verbatim transcript citations.' }, ], modules: ['voice', 'safe', 'ops'], industries: ['emergency-services', 'energy', 'mining', 'defense'], industryLabels: ['Emergency Services', 'Energy & Utilities', 'Mining', 'Defense'], accent: 'var(--coral)', photoHero: 'assets/solution-incident-hero.png', photoHeroCorner: ['', 'INCIDENT BOARD'], photoDetail: null, photoDetailTag: 'EVIDENCE FOLDER', v2: true, }, 'custom-detection': { n: '19c', eyebrow: 'SOLUTION — CUSTOM EVENT DETECTION', title: 'Watch for the events your operation has decided matter.', short: 'Anything your team manually reviews today — defined once, watched continuously.', subhead: 'Your operation has events it cares about that no off-the-shelf product can predict. Cortexa Signal lets your team define those events in plain language, evaluate them against your historical traffic, and put them into continuous monitoring with verifiable evidence.', problem: 'Bespoke operational signals — contractor arrivals, FOD reports, tool handovers, specific equipment-state phrases — are exactly the things that get reviewed manually today because no platform knows about them. Manual review is slow, inconsistent, and impossible to scale.', outcomes: [ { t: 'Plain-language concept definition', b: '— anchors, confirmations, exclusions. No code.' }, { t: 'Live evaluation', b: 'against your historical conversations before any concept goes live.' }, { t: 'Precision and recall visible', b: 'before save — adjust until it’s right for your operation.' }, { t: 'Continuous tuning', b: '— every supervisor review of a concept-driven detection sharpens its precision automatically.' }, { t: 'No retraining cycles', b: '— concepts evolve without taking the system offline.' }, ], modules: ['voice', 'signal'], industries: ['aviation', 'energy', 'construction', 'emergency-services'], industryLabels: ['Aviation', 'Energy & Utilities', 'Construction & Heavy Industry', 'Emergency Services'], accent: 'var(--amber)', photoHero: 'assets/solution-custom-hero.png', photoHeroCorner: ['', 'CONCEPTS BOARD'], photoDetail: null, photoDetailTag: 'WHITEBOARD CONCEPT', v2: true, }, 'multilingual-operations': { n: '19d', eyebrow: 'SOLUTION — MULTILINGUAL FIELD OPERATIONS', title: 'One operational record. Every language your crews speak.', short: 'English, Arabic, Spanish, French, Dutch, German — one platform, one record.', subhead: 'Field operations rarely happen in one language. Cortexa transcribes and structures every transmission in the language it was spoken, links related conversations across crews and shifts, and gives supervisors a single operational record they can search and act on.', problem: 'Multilingual operations today rely on translators, bilingual supervisors, or post-hoc translation of audio recordings. The result is operational blind spots that grow with every new crew. Cortexa removes the language barrier from the platform, not from the workforce.', outcomes: [ { t: 'Six languages, auto-detected', b: 'on every transmission. Channels pinnable to specific crews when accents or noise demand it.' }, { t: 'Native handling of mixed-language utterances', b: '— a Spanish operator speaking English equipment IDs is handled correctly.' }, { t: 'One record per operation', b: '— search across every language in the language you speak.' }, { t: 'Multilingual alerts and summaries', b: '— supervisors and operators receive content in their own language.' }, { t: 'New languages added', b: 'without taking the system offline.' }, ], modules: ['voice'], industries: ['aviation', 'construction', 'energy', 'emergency-services'], industryLabels: ['Aviation', 'Construction & Heavy Industry', 'Energy & Utilities', 'Emergency Services'], accent: 'var(--amber)', photoHero: 'assets/solution-multilingual-hero.png', photoHeroCorner: ['', 'MULTILINGUAL CREW'], photoDetail: null, photoDetailTag: 'EN · AR · ES · FR · NL · DE', v2: true, }, }; const MODULE_META = { voice: { label: 'Cortexa Voice', to: '/products/voice', note: 'Foundation — capture, threading, transcription, entities.', accent: 'var(--slate-100)' }, safe: { label: 'Cortexa Safe', to: '/products/safe', note: 'Safety event detection.', accent: 'var(--coral)' }, ops: { label: 'Cortexa Ops', to: '/products/ops', note: 'Procedural verification.', accent: 'var(--teal)' }, signal: { label: 'Cortexa Signal', to: '/products/signal', note: 'Custom concept definition.', accent: 'var(--amber)' }, }; const SOLUTION_LABEL = { 'permit-to-work': 'Permit-to-Work & Confined-Space Compliance', 'procedural-compliance': 'Procedural Communication Compliance', 'shift-handover': 'Shift Handover Integrity', 'alarm-response': 'Gas, Fire & Hazard Alarm Response', 'incident-detection': 'Incident Detection & Reconstruction', 'custom-detection': 'Custom Event Detection', 'multilingual-operations': 'Multilingual Field Operations', }; /* --- Solution template -----------------------------------*/ function SolutionPage({ slug }) { useReveal(); const s = SOLUTIONS[slug]; if (!s) return ; return ( <> {/* HERO */}
{s.eyebrow}
{s.v2 && V2 DETAIL}

{s.title}

{s.subhead}

Request a Pilot → All solutions →
{/* PROBLEM */}

What’s missing today.

{s.problem}

{/* WHAT CORTEXA DOES — outcome bullets */}
Five things this solution does the moment it goes live.} sideNote={s.short} />
    {s.outcomes.map((o, i) => (
  1. {String(i+1).padStart(2,'0')}

    {o.t}{' '}{o.b}

    2. ))}
{/* MODULES */}

How it composes from the Cortexa modules.

{s.modules.map((m, i) => { const key = typeof m === 'string' ? m : m.slug; const meta = MODULE_META[key]; const label = typeof m === 'object' ? m.label : meta.label; const note = typeof m === 'object' ? (m.note || meta.note) : meta.note; return ( {String(i+1).padStart(2,'0')} / {String(s.modules.length).padStart(2,'0')}

{label} →

{note}

); })}
{/* INDUSTRIES */}

Where this solution applies most directly.

    {s.industryLabels.map((label, i) => { const indSlug = s.industries[i]; return (
  • {label} →
    • ); })}
); } /* --- Solutions hub -----------------------------------*/ function SolutionsHubPage() { useReveal(); return ( <>

Solutions for the problems your operation actually has.

Cortexa’s modules combine to solve specific operational and safety problems. Each solution below names the problem in your language, the outcome you’ll get, and the modules that power it.

{SOLUTION_GROUPS.map((group, gi) => (

{group.label}

{group.slugs.length} {group.slugs.length === 1 ? 'SOLUTION' : 'SOLUTIONS'}
{group.slugs.map((slug) => { const sol = SOLUTIONS[slug]; return (

{SOLUTION_LABEL[slug]}

{sol.short}

Read solution → ); })}
))}
); } Object.assign(window, { SolutionPage, SolutionsHubPage, SOLUTIONS, SOLUTION_LABEL });