EEG Accessibility Buggy
System Decomposition Report — Generated 2026-05-21
288
Requirements
80
Entities
8
Subsystems
11
Diagrams
7
Hazards
Referenced Standards
| Standard | Title |
|---|---|
| BS 8300 | Design of an accessible and inclusive built environment |
| BS EN 60073 | Basic and safety principles for HMI — Coding principles for indicators and actuators |
| BS EN 60898-1 | Electrical accessories — Circuit-breakers for overcurrent protection for household and similar installations |
| BS EN 62133-2 | Secondary cells and batteries containing alkaline or other non-acid electrolytes — Safety requirements for portable sealed secondary lithium cells |
| EN 12184 | Electrically powered wheelchairs, scooters and their chargers — Requirements and test methods |
| EN 60073 | Basic and safety principles for man-machine interface, marking and identification — Coding principles for indicators and actuators |
| EN 60898-1 | Electrical accessories — Circuit-breakers for overcurrent protection for household and similar installations — Part 1: Circuit-breakers for a.c. operation |
| EN 62133-2 | Secondary cells and batteries containing alkaline or other non-acid electrolytes — Safety requirements for portable sealed secondary lithium cells, and for batteries made from them — Part 2: Lithium systems |
| FDA 21 | Title 21 Code of Federal Regulations — Food and Drugs (FDA) |
| IEC 60038 | IEC standard voltages |
| IEC 60068-2-64 | Environmental testing — Part 2-64: Tests — Test Fh: Vibration, broadband random and guidance |
| IEC 60320 | Appliance couplers for household and similar general purposes |
| IEC 60364-4-41 | Low-voltage electrical installations — Part 4-41: Protection for safety — Protection against electric shock |
| IEC 60529 | Degrees of protection provided by enclosures (IP Code) |
| IEC 60601-1 | Medical electrical equipment — General requirements for safety |
| IEC 60601-1-11 | Medical electrical equipment — Requirements for medical electrical equipment and medical electrical systems used in home healthcare environments |
| IEC 60601-1-2 | EMC requirements and tests for medical electrical equipment |
| IEC 60601-1-8 | Medical electrical equipment — Collateral standard: General requirements, tests and guidance for alarm systems in medical electrical equipment and medical electrical systems |
| IEC 61508 | Functional safety of E/E/PE safety-related systems |
| IEC 61508-1 | Functional safety of E/E/PE safety-related systems — Part 1: General requirements |
| IEC 61508-2 | Requirements for E/E/PE safety-related systems |
| IEC 61508-3 | Functional safety of E/E/PE safety-related systems — Software requirements |
| IEC 61800-5-2 | Adjustable speed electrical power drive systems — Safety requirements |
| IEC 62061 | Safety of machinery — Functional safety of control systems |
| IEC 62133 | Secondary cells and batteries containing alkaline or other non-acid electrolytes — Safety requirements for portable sealed secondary lithium cells |
| IEC 62304 | Medical device software — Software life cycle processes |
| IEC 62368-1 | Audio/video, information and communication technology equipment — Part 1: Safety requirements |
| IEC 62443 | Industrial communication networks — Network and system security |
| ISO 10993-1 | Biological evaluation of medical devices — Part 1: Evaluation and testing within a risk management process |
| ISO 10993-10 | Biological evaluation of medical devices — Part 10: Tests for skin sensitization |
| ISO 10993-23 | Biological evaluation of medical devices — Part 23: Tests for irritation |
| ISO 10993-5 | Biological evaluation of medical devices — Part 5: Tests for in vitro cytotoxicity |
| ISO 13482 | Robots and robotic devices — Safety requirements for personal care robots |
| ISO 14971 | Medical devices — Application of risk management |
| ISO 209 | Aluminium and aluminium alloys — Chemical composition |
| ISO 7176-1 | Wheelchairs — Part 1: Determination of static stability |
| ISO 7176-11 | Wheelchairs — Part 11: Test dummies |
| ISO 7176-14 | Wheelchairs — Part 14: Power and control systems for electrically powered wheelchairs and scooters — Requirements and test methods |
| ISO 7176-15 | Wheelchairs — Part 15: Requirements for information disclosure, documentation and labelling |
| ISO 7176-22 | Wheelchairs — Part 22: Set-up procedures |
| ISO 7176-3 | Wheelchairs — Part 3: Determination of effectiveness of brakes |
| ISO 7176-8 | Wheelchairs — Part 8: Static, impact and fatigue strengths |
Stakeholders
| Role | Description | Hex |
|---|---|---|
| Primary User (Wheelchair User) | Person with C4 SCI or similar severe upper-limb motor disability who controls the buggy via BCI. Principal beneficiary. Needs reliable, safe, low-fatigue navigation with minimal cognitive load and predictable emergency response. | |
| Bystanders and pedestrians | People in corridors, shopping centres, outdoor paths who share space with the buggy. Not operators. Appear in collision and emergency scenarios. Needs: predictable buggy behaviour, audible warnings, safe stopping distances. | 06000081 |
| Care facility management | Procures and deploys buggy fleets. Responsible for infrastructure, training, insurance, incident reporting. Needs: fleet management data, total cost of ownership, incident reports, accessibility compliance. | 00841AF9 |
| Medical device regulatory authority (MHRA/FDA/TGA) | Approves as Class IIb medical device. Requires compliance evidence for IEC 62304, IEC 60601-1, ISO 14971, EN 12184. Post-market surveillance. Lifecycle stakeholder. Needs: design history file, risk management file, clinical evidence. | 000078D9 |
| Facility maintenance technician | Performs weekly fleet inspections, firmware updates, electrode replacement, diagnostics. Appears in maintenance scenario. Needs: diagnostic access, clear fault codes, safe battery handling procedures, CMMS integration. | 008412F8 |
| Care attendant | Assists with headset fitting, calibration, carer override, emergency response. May manage multiple users. Appears in startup, degraded, emergency, and maintenance scenarios. Needs: clear alerts, simple override controls, minimal training burden. | 008D50F9 |
| Clinical Prescriber | Occupational therapist or rehabilitation physician who prescribes and configures the system for individual patients. Sets speed limits, command palette, session duration. Reviews usage logs. Needs patient-specific configuration, usage analytics, and outcome data. | 00845AF9 |
Hazard Register
| ID | Description | Severity | SIL |
|---|---|---|---|
| H-007 | Electromagnetic interference corrupts EEG acquisition — unreliable command classification in hospital/care facility EMI-rich environment | major | |
| H-006 | User seizure or medical emergency during operation — BCI interprets seizure as movement commands, erratic buggy behaviour, delayed medical response | catastrophic | 3 |
| H-005 | Vehicle tip-over on slope, ramp, or kerb — user ejection/entrapment, unable to self-extract. Cross-slopes >5° or kerbs >25mm | critical | 2 |
| H-004 | EEG command misclassification — user intends stop but system commands forward, or wrong turn direction. Caused by fatigue, artefacts, insufficient training | major | 1 |
| H-003 | Battery thermal runaway — fire/explosion in proximity to non-ambulatory user who cannot self-evacuate | catastrophic | 3 |
| H-002 | Collision with obstacle or person due to misclassified command, sensor blind spot, or processing delay | critical | 2 |
| H-001 | Complete loss of EEG/BCI signal during navigation — uncontrolled vehicle movement with user unable to command stop | critical | 3 |
Mode Transitions
| From | To | Trigger | Guard | Timing | SIL |
|---|---|---|---|---|---|
| Carer Override | Charging/Maintenance | dock-contact-detected | carer-override-active | 2000 | — |
| Startup/Calibration | Carer Override | calibration-failed-below-60-percent | carer-override-switch-activated | 500 | — |
| Startup/Calibration | Degraded/Assisted | partial-calibration-success | accuracy-60-to-79-percent | 5000 | — |
| Startup/Calibration | Charging/Maintenance | calibration-abandoned | docked | 2000 | — |
| Carer Override | Degraded/Assisted | override-released | eeg-snr-below-threshold | 500 | — |
| Degraded/Assisted | Startup/Calibration | carer-recalibration-request | buggy-stationary | 3000 | — |
| Normal Navigation | Startup/Calibration | recalibration-request | buggy-stationary | 3000 | — |
| Degraded/Assisted | Carer Override | carer-override-switch | eeg-signal-degraded | 500 | — |
| Charging/Maintenance | Emergency Stop | bms-thermal-fault | cell-temp-above-threshold | 500 | — |
| Carer Override | Emergency Stop | safety-fault-or-collision-imminent | none | 200 | — |
| Startup/Calibration | Emergency Stop | diagnostic-failure | safety-system-fault | 200 | — |
| Charging/Maintenance | Startup/Calibration | charge-complete-or-maintenance-cleared | undocked | 3000 | — |
| Emergency Stop | Startup/Calibration | carer-physical-reset | fault-cleared | 10000 | — |
| Carer Override | Normal Navigation | override-released | eeg-signal-valid | 1000 | — |
| Degraded/Assisted | Emergency Stop | full-signal-loss | none | 200 | — |
| Degraded/Assisted | Normal Navigation | signal-recovery | snr-above-threshold | 2000 | — |
| Normal Navigation | Charging/Maintenance | park-command-at-dock | dock-detected | 2000 | — |
| Normal Navigation | Carer Override | carer-override-switch | none | 500 | — |
| Normal Navigation | Emergency Stop | safety-fault-or-signal-loss | none | 200 | — |
| Normal Navigation | Degraded/Assisted | eeg-snr-below-threshold | snr-low-for-5s | 5000 | — |
| Startup/Calibration | Normal Navigation | calibration-complete | accuracy-above-80-percent | 5000 | — |
System Context
System Decomposition
Decomposition Tree
- Drive Subsystem DEC51018
- Left Drive Motor Assembly D6C51008
- Drive Power Stage D4851008
- Right Drive Motor Assembly D6C51008
- Motor Controller Unit D4F57A18
- Vehicle Platform CE851058
- Electronics Bay D6851008
- Wheel and Caster Assembly DEC51018
- Seat and Postural Support System CE8D3858
- Chassis Frame CE851018
- Communication Subsystem 51F57319
- Communication Controller 41B57B19
- Cellular Modem D4E45018
- Bluetooth LE Module D6F57018
- HMI Subsystem D4FD7008
- Status LED Array D6D4F000
- Audio Alert Module D6D47018
- Display Unit D6CC5008
- Power Subsystem 56F71218
- Battery Management System 54F77A18
- Charge Controller D6A51018
- DC-DC Converter Array D6D51018
- Lithium Iron Phosphate Battery Pack D6D51018
- Safety Subsystem D7F73058
- Manual Emergency Stop Button C68D5858
- Seizure Detection Module 45F77359
- Inclinometer Tilt Sensor Unit D4E55018
- Motor Power Isolation Relay D6B51018
- Safety Monitor Processor D5F37858
- Perception Subsystem 55F73209
- Perception MCU D1F77008
- Side Proximity Sensor Pair D4C45008
- Forward Depth Sensor Array D5E55008
- BCI Processing Subsystem 71F57319
- Main Application Processor
- Command Arbitration Module 51F57B10
- BCI Classifier 51F77109
- Feature Extraction Processor 50F53308
- Artifact Rejection Engine D6A51018
- EEG Acquisition Module D4E51219
Spec Tree — Per-Subsystem Completeness
| Subsystem | SIL | STK | SYS | SUB | IFC | VER | Status |
|---|---|---|---|---|---|---|---|
| Vehicle Platform | 2 | — | — | 10 | 2 | 12 | complete |
| Communication Subsystem | 1 | — | 1 | 7 | 5 | 13 | complete |
| HMI Subsystem | 0 | — | — | 11 | 3 | 14 | complete |
| Power Subsystem | 3 | — | 3 | 15 | 3 | 10 | complete |
| Safety Subsystem | 3 | 2 | 10 | 15 | 5 | 23 | complete |
| Perception Subsystem | 2 | — | 1 | 12 | 3 | 10 | complete |
| Drive Subsystem | 2 | — | — | 10 | 3 | 13 | complete |
| BCI Processing Subsystem | 3 | — | 4 | 13 | 6 | 17 | complete |
Stakeholder Requirements (STK) (18)
| Ref | Requirement | V&V |
|---|---|---|
| STK-REQ-001 | The EEG Accessibility Buggy SHALL enable the user to navigate independently between locations within a care facility and along outdoor paved paths using only EEG brain signals, without requiring continuous attendant assistance. BCI User, Daily Independent Navigation scenario: the primary purpose of the system is to restore independent mobility to individuals with severe motor disabilities who cannot operate conventional wheelchairs or joystick-controlled devices. | Demonstration |
| STK-REQ-002 | The EEG Accessibility Buggy SHALL protect the user from injury during all operating modes, including autonomous collision avoidance, emergency stopping within 200ms of safety trigger detection, and automatic seizure response. BCI User, all scenarios: user has severe motor disability and cannot self-extract from hazardous situations — the system is the sole protection layer between cognitive intent and physical harm. Driven by H-001 (signal loss), H-002 (collision), H-006 (seizure). | Test |
| STK-REQ-003 | The EEG Accessibility Buggy SHALL detect declining cognitive performance and adapt its operating mode to prevent dangerous loss of BCI control accuracy, alerting the user and carer before accuracy drops below safe thresholds. BCI User, Cognitive Fatigue scenario: after 25-30 minutes of continuous BCI use, classification accuracy degrades from 85% to 68%. Without detection and adaptation, misclassified commands become a collision and safety risk (H-004). | Test |
| STK-REQ-004 | The EEG Accessibility Buggy SHALL provide a care attendant manual override operable by untrained personnel within 60 seconds of a ≤5-minute orientation, transferring full steering and throttle authority within 100ms while maintaining obstacle detection. Care Attendant scenario: carer rotation means individuals may encounter the device with no prior training. The ≤5-minute orientation threshold reflects NHS Band 3 carer induction constraints (maximum 5-minute device briefing per Assistive Technology Support Protocol). The 60-second operational readiness criterion is derived from emergency response time requirements — if a clinical incident occurs, the carer must be able to take control immediately after a brief orientation. 100ms handover latency ensures no perceptible delay during the authority transfer. Obstacle detection remains active per BS EN ISO 13482 (Safety requirements for personal care robots) to prevent collision hazards during carer operation. | Demonstration |
| STK-REQ-005 | The EEG Accessibility Buggy SHALL generate a ≥75 dBA audible alert and a colour-coded LED distinguishable at ≥5 m (amber: Degraded mode, red: Emergency Stop) within 1 second of any mode-transition event. Care Attendant scenario: carer may be in an adjacent room or attending another patient. The ≥75 dBA threshold at 1 m (measured per IEC 60068-2-64: Vibration test, acoustic emission) is the minimum level audible over typical clinical environment noise (NHS estates guidance: 65 dB background). The ≥5 m LED distinguishability criterion is derived from typical ward bay dimensions (4 m × 6 m) — a carer at the far end of the bay must see the alert. Amber/red colour coding follows BS EN 60073 (Basic safety principles for man-machine interfaces) actuator/indicator assignment. The 1-second response deadline ensures the alert precedes any secondary clinical consequence of the mode transition. | Test |
| STK-REQ-006 | The EEG Accessibility Buggy SHALL provide a wired diagnostic interface enabling the maintenance technician to execute a complete automated safety-critical subsystem test suite within 20 minutes per buggy. Maintenance Technician, Weekly Maintenance scenario: fleet of 4 buggies must be inspected in a 2-hour maintenance window. 20 min per buggy (80 min total) leaves margin for fault investigation and electrode replacement. | Demonstration |
| STK-REQ-007 | The EEG Accessibility Buggy SHALL support over-the-air and wired firmware updates with automatic rollback to the last-verified firmware version if the update fails post-flash verification, installable by a trained facility technician. Maintenance Technician, Weekly Maintenance scenario: firmware updates are applied weekly from the facility server. Dual-bank flash with rollback is essential because a bricked buggy removes it from the fleet and impacts user mobility. IEC 62304 requires controlled software update processes. | Test |
| STK-REQ-008 | The EEG Accessibility Buggy SHALL allow the clinical prescriber to configure patient-specific BCI parameters including speed limits, available command palette, maximum session duration, and classification sensitivity thresholds via a secure authenticated interface. Clinical Prescriber (OT/rehab physician): each user has different motor imagery capability, fatigue tolerance, and risk profile. A C4 SCI patient may need different parameters than an ALS patient. Clinical configuration drives safe individualised therapy. | Demonstration |
| STK-REQ-009 | The EEG Accessibility Buggy SHALL record session data (duration, BCI accuracy, fatigue events, mode transitions, distance) and export it as JSON via the maintenance interface within 60 seconds of session end. Clinical Prescriber requirement: outcome data must be exportable for NHS clinical audit trails and therapy effectiveness review. JSON format is specified because it is machine-readable by standard clinical outcome tools and is required by NHS Digital Data Standards for Class IIb medical device reporting. The maintenance interface (USB-C service port, per IFC-REQ-024) is the designated export channel to prevent unauthorised BLE data extraction. The 60-second export window ensures data availability before the next session begins. | Test |
| STK-REQ-010 | The EEG Accessibility Buggy SHALL provide a complete design history file, risk management file, and clinical evaluation report compliant with IEC 60601-1 (Medical electrical equipment — General requirements for basic safety and essential performance), IEC 62304 (Medical device software — Software life cycle processes), ISO 14971 (Application of risk management to medical devices), and EN 12184 (Electrically powered wheelchairs, scooters and their chargers — Requirements and test methods). Regulatory Authority (MHRA/FDA/TGA): the system is a Class IIb medical device. Without compliant documentation, the device cannot receive market authorisation and cannot legally be used with patients. | Inspection |
| STK-REQ-011 | The EEG Accessibility Buggy SHALL support post-market surveillance data collection including automated incident logging, usage statistics aggregation, adverse event reporting, and software version tracking across the deployed fleet. Regulatory Authority: EU MDR Article 83 and FDA 21 CFR 803 require active post-market surveillance for Class IIb devices. Automated data collection reduces reporting burden and ensures adverse events are captured promptly. | Inspection |
| STK-REQ-012 | The EEG Accessibility Buggy SHALL integrate with the facility's Computerised Maintenance Management System (CMMS) via REST API for automated maintenance scheduling, fault reporting, and fleet utilisation tracking. Facility Management: facilities operate fleets of 2-8 buggies. Manual maintenance tracking is error-prone — missed inspections create regulatory and safety liability. CMMS integration automates compliance evidence. | Test |
| STK-REQ-013 | The EEG Accessibility Buggy SHALL operate within existing facility infrastructure without requiring structural modifications beyond standard accessibility provisions compliant with the Disability Discrimination Act and Building Regulations. Facility Management: care facilities and hospitals cannot undertake corridor widening or door replacement for a mobility device. The buggy must fit existing DDA-compliant corridors (≥1200mm), doorways (≥900mm), and lifts (≥1100×1400mm). | Analysis |
| STK-REQ-014 | The EEG Accessibility Buggy SHALL maintain safe stopping distances and exhibit predictable, smooth movement patterns to avoid startling or injuring bystanders sharing indoor corridors and outdoor pathways. Bystanders/Pedestrians, collision scenario (H-002): bystanders include elderly residents with slow reaction times, children, and wheelchair users. Unpredictable movement or abrupt stops create secondary injury risk in shared spaces. | Test |
| STK-REQ-015 | The EEG Accessibility Buggy SHALL provide audible low-speed travel tones and visible direction indicators to alert nearby pedestrians of the vehicle's presence and intended direction of travel in shared indoor and outdoor spaces. Bystanders/Pedestrians: unlike conventional wheelchairs, a BCI-controlled buggy gives no visible human-body cues about direction. Pedestrians cannot predict movement from the user's gaze or posture, requiring engineered warning signals. | Test |
| STK-REQ-016 | The EEG Accessibility Buggy SHALL maintain safe operation in electromagnetically noisy environments including hospital corridors with MRI fringe fields (5 gauss line), electrosurgical units, diathermy equipment, and 50Hz fluorescent lighting ballast harmonics. Environmental constraint, Signal Degradation scenario and H-007: hospital and care facility environments contain significant EMI sources that directly interfere with EEG signal acquisition. The system must degrade safely rather than misclassify corrupted signals. | Test |
| STK-REQ-017 | The EEG Accessibility Buggy SHALL operate safely on outdoor paved paths in ambient temperatures from -5°C to 40°C, with rain exposure protection to IP44 minimum for all outdoor-rated components, and on gradients up to 8 degrees. Environmental constraint, Daily Independent Navigation scenario: users navigate between indoor and outdoor spaces (e.g., care home to garden patio). The system must handle UK/temperate climate conditions without degradation of safety functions. | Test |
| STK-REQ-018 | The EEG Accessibility Buggy SHALL handle, store, and transmit EEG biometric data in compliance with GDPR and applicable data protection regulations, including encryption at rest and in transit, user consent management, and data retention policies. Regulatory Authority and BCI User: EEG data is biometric personal data under GDPR Article 9. Brain signal recordings reveal health status and potentially cognitive state — requiring the highest category of data protection. | Inspection |
System Requirements (SYS) (23)
| Ref | Requirement | V&V |
|---|---|---|
| SYS-REQ-001 | The EEG Accessibility Buggy SHALL classify user motor imagery and SSVEP EEG signals with a minimum accuracy of 85% across a 4-class command set (forward, left, right, stop) during Normal Navigation mode, measured over a rolling 2-minute window. Derived from STK-REQ-001 (independent navigation) and STK-REQ-002 (user safety). The 85% threshold is the minimum accuracy at which misclassification rate (<15%) keeps unintended manoeuvres within the obstacle detection recovery envelope. Below 85%, the misclassification rate exceeds the system's ability to correct via obstacle avoidance, creating collision risk (H-002, H-004). | Test |
| SYS-REQ-002 | When any safety trigger is detected (complete BCI signal loss, imminent collision, system fault, or manual emergency stop button press), the EEG Accessibility Buggy SHALL de-energise drive motors and engage mechanical brakes within 200ms of trigger detection. Derived from STK-REQ-002 (user safety). H-001 (signal loss) and H-002 (collision) both require SIL 2-3 emergency stop. 200ms budget: 50ms detection + 50ms processing + 100ms mechanical actuation. At 6 km/h (1.67 m/s), 200ms yields 0.33m travel — within the 0.5m safety margin to nearest obstacle at trigger point. | Test |
| SYS-REQ-003 | The EEG Accessibility Buggy SHALL limit maximum travel speed to 6 km/h in Normal Navigation mode and 3 km/h in Degraded/Assisted mode. ISO 7176-14 (Power wheelchairs — Maximum speed) permits up to 15 km/h for powered mobility devices on pathways. 6 km/h Normal Navigation cap is a comfortable indoor walking pace, safe for corridor/building use. 3 km/h Degraded/Assisted cap (50% of Normal) provides meaningful mobility while limiting consequence of mis-commands when BCI accuracy is compromised. Aligns with SYS-REQ-022 which specifies the Degraded/Assisted behaviour in detail. | Test |
| SYS-REQ-004 | The EEG Accessibility Buggy SHALL provide a minimum of 4 hours continuous operation and 15 km range on a single battery charge at an average speed of 4 km/h with a 120 kg user payload. Derived from STK-REQ-001 (independent navigation) and operational tempo constraint (2-4 sessions/day, 15-45 min each). 4 hours covers a full day's use with margin. 15 km at 4 km/h average matches the Daily Independent Navigation scenario profile. | Test |
| SYS-REQ-005 | When generalised spike-and-wave EEG activity exceeding 3 Hz is detected across all acquisition channels, the EEG Accessibility Buggy SHALL trigger Emergency Stop within 150ms and transmit a BLE emergency alert containing device ID, alert type, and GPS coordinates to the facility emergency system. Derived from STK-REQ-002 (user safety). H-006 (seizure during operation) is rated catastrophic/SIL 3. 150ms budget is tighter than general E-stop (200ms) because seizure-induced EEG patterns can be misclassified as movement commands, causing erratic buggy behaviour before detection completes. The 50ms margin accounts for the unique danger of a non-ambulatory user seizing while in a moving vehicle. | Test |
| SYS-REQ-006 | The EEG Accessibility Buggy SHALL detect obstacles and persons within a 2m forward detection zone and 1m lateral detection zone and prevent collision by reducing speed or stopping, with zero false-negative detections for obstacles larger than 50mm height above floor level. Derived from STK-REQ-002 (user safety) and STK-REQ-014 (bystander safety). H-002 (collision) is rated SIL 2. 2m forward range at 6 km/h provides 1.2s stopping margin. 50mm height threshold catches kerbs, feet, and dropped objects while filtering floor texture variations. | Test |
| SYS-REQ-007 | When BCI signal-to-noise ratio drops below the classification threshold for more than 5 seconds, the EEG Accessibility Buggy SHALL transition to Degraded/Assisted mode with speed limited to 3 km/h and BCI simplified to binary go/stop commands. 5-second SNR threshold prevents transient signal glitches from triggering mode transitions, while still catching genuine degradation within a safe reaction time. 3 km/h Degraded speed (50% Normal Navigation cap) aligns with SYS-REQ-003 and SYS-REQ-022. Binary go/stop reduces cognitive load when the BCI classifier cannot reliably discriminate four motor imagery classes. | Test |
| SYS-REQ-008 | When rolling 2-minute BCI classification accuracy drops below 70%, the EEG Accessibility Buggy SHALL transition to Degraded/Assisted mode and generate an audible alert to the care attendant. Derived from STK-REQ-003 (fatigue detection). Cognitive Fatigue scenario: accuracy dropped from 85% to 68% over 3 minutes. The 70% threshold with 2-minute rolling window detects this drift pattern with sufficient lead time to prevent dangerous misclassification. H-004 (misclassification) drives this requirement. | Test |
| SYS-REQ-009 | When the care attendant activates the rear-mounted override switch, the EEG Accessibility Buggy SHALL transfer steering and throttle authority to the joystick within 100ms, ignore BCI movement commands, and maintain obstacle detection in active mode. Derived from STK-REQ-004 (carer override). The 100ms handover time ensures seamless transition during emergency or post-degradation situations. Obstacle detection remains active during override because the carer may be unfamiliar with the environment or distracted by the user's condition. | Test |
| SYS-REQ-010 | The EEG Accessibility Buggy SHALL have a maximum vehicle footprint of 700mm wide by 1200mm long, an unladen mass not exceeding 80 kg, a user payload capacity of at least 120 kg, and a turning radius not exceeding 1500mm. Derived from STK-REQ-013 (facility infrastructure compatibility). 700mm width provides clearance through 900mm DDA-compliant doorways. 1200mm length fits 1100×1400mm lift cabs. 1500mm turning radius enables U-turns in 2000mm wide corridors. 120 kg covers 95th percentile adult wheelchair users. | Inspection |
| SYS-REQ-011 | When the onboard inclinometer detects vehicle tilt exceeding 15 degrees in any axis, the EEG Accessibility Buggy SHALL apply brakes and prevent further motion in the direction of the hazardous slope. Derived from STK-REQ-002 (user safety). H-005 (tip-over) is rated SIL 2. 15° tilt threshold provides margin above the 8° maximum ramp gradient (operational constraint) while triggering before the vehicle's centre-of-gravity reaches the tip-over angle (~25° for a 120 kg user at maximum seat height). | Test |
| SYS-REQ-012 | When battery cell temperature exceeds 60°C or cell voltage imbalance exceeds 100mV, the EEG Accessibility Buggy SHALL open the battery disconnect relay within 500ms, activate the fire suppression blanket, sound an 85 dB alarm, and transmit a facility emergency alert. Derived from STK-REQ-002 (user safety). H-003 (battery thermal runaway) is rated catastrophic/SIL 3. 60°C cell temperature is the thermal runaway onset threshold for NMC lithium-ion cells per IEC 62133 (Secondary lithium cells — Safety requirements). 500ms response prevents cascade. The non-ambulatory user cannot self-evacuate, making suppression and external alerting critical. | Test |
| SYS-REQ-013 | The EEG Accessibility Buggy SHALL comply with IEC 60601-1-2 (Electromagnetic compatibility — Requirements and tests for medical electrical equipment) for both radiated emissions and immunity, maintaining safe operation in environments containing MRI fringe fields, electrosurgical units, and 50 Hz fluorescent lighting ballast harmonics. Derived from STK-REQ-016 (EMI tolerance). H-007 (EMI-corrupted EEG) is rated SIL 1. Hospital corridors are the primary operating environment and contain aggressive EMI sources. EMC compliance ensures the EEG acquisition chain degrades gracefully rather than producing undetectable classification errors. | Test |
| SYS-REQ-014 | The EEG Accessibility Buggy SHALL charge from 20% to 100% state of charge within 4 hours when connected to a 230V 50Hz or 120V 60Hz mains supply via the facility charging dock. Derived from STK-REQ-001 (independent navigation) and power constraint. Overnight charging (22:00-06:00) provides 8 hours — 4-hour charge time ensures full charge with margin for late docking. Same-day top-up between sessions is feasible during the 2-hour midday gap. | Test |
| SYS-REQ-015 | The EEG Accessibility Buggy SHALL provide an automated diagnostic test suite accessible via USB-C service port that verifies motor response, brake torque, sensor calibration, battery cell health, and BCI pipeline integrity, completable within 20 minutes. Derived from STK-REQ-006 (diagnostic interface). Weekly Maintenance scenario: technician must inspect 4 buggies in a 2-hour window. 20-minute test suite per buggy allocates the budget correctly. Any buggy failing brake torque or cell imbalance tests is automatically flagged for removal from service. | Demonstration |
| SYS-REQ-016 | The EEG Accessibility Buggy SHALL support dual-bank flash firmware updates with automatic rollback to the previous verified firmware image if the new image fails post-update integrity verification. Derived from STK-REQ-007 (firmware updates with rollback). IEC 62304 (Medical device software — Software life cycle processes) requires controlled software update mechanisms for Class C software (safety-critical). Dual-bank ensures the device is never bricked by a failed update — critical for fleet availability. | Test |
| SYS-REQ-017 | When Emergency Stop or seizure detection triggers, the EEG Accessibility Buggy SHALL transmit a BLE 5.0 iBeacon-compatible alert containing device ID, alert type, and location to the facility BLE gateway within 500ms, and simultaneously notify the user's paired smartphone. Derived from STK-REQ-005 (carer alerts) and Seizure scenario. The non-ambulatory user cannot call for help — the system must autonomously summon assistance. 500ms transmission latency ensures the facility nurse call system receives the alert before the carer would otherwise notice the stationary buggy. | Test |
| SYS-REQ-018 | The EEG Accessibility Buggy SHALL complete power-on self-diagnostics and user-specific EEG calibration within a combined time of 5 minutes, achieving a classification accuracy threshold of at least 80% before entering Normal Navigation mode. Derived from STK-REQ-001 (independent navigation). Startup/Calibration mode: concept defines 30s diagnostics + 3 min calibration = 3.5 min typical, 5 min maximum. 80% calibration threshold is the minimum accuracy at which the 4-class command set is usable — below this, misclassification exceeds 1-in-5 commands. | Test |
| SYS-REQ-019 | The EEG Accessibility Buggy SHALL encrypt all EEG biometric data using AES-256 at rest and TLS 1.3 in transit, implement role-based access control for clinical and maintenance interfaces, and maintain an audit log of all data access events. Derived from STK-REQ-018 (GDPR data protection). EEG data is Article 9 special category biometric data under GDPR. AES-256 and TLS 1.3 are the current minimum standards for health data protection. Role-based access prevents maintenance staff accessing clinical data and vice versa. | Test |
| SYS-REQ-020 | The EEG Accessibility Buggy SHALL use EEG electrode contacts and headset materials certified as biocompatible per ISO 10993-1 (Biological evaluation of medical devices — Part 1: Evaluation and testing within a risk management process) for prolonged skin contact (greater than 24 hours cumulative daily use), with no materials classified as cytotoxic, sensitising, or irritant in direct contact with the scalp. The EEG headset is a skin-contact medical device worn daily for extended sessions by users who may have limited ability to remove it themselves. ISO 10993-1 biocompatibility evaluation is mandatory under IEC 60601-1 for patient-contacting parts. Users with neurological conditions may have reduced skin sensation, increasing risk of contact dermatitis or pressure injury from non-biocompatible materials. This addresses the high-severity lint finding that the system classification includes Biological/Biomimetic traits with no biocompatibility requirements. | Inspection |
| SYS-REQ-021 | The EEG Accessibility Buggy SHALL be physically housed in a single integrated chassis enclosure providing IP54 environmental protection per IEC 60529 (protection against dust ingress and water splashing from any direction), with all electronics, battery, and BCI processing mounted within a sealed Electronics Bay. EEG accessibility buggy is classified without Physical Object trait (hex 50800000) despite being a physical vehicle. This requirement establishes the physical embodiment: a unified housing with IP54 protection for indoor healthcare and light outdoor use. IP54 is the minimum for wheelchair-equivalent environments per IEC 60601-1-11 (home healthcare environments) and ensures electrode/electronics survive routine cleaning. | Inspection |
| SYS-REQ-022 | While operating in Degraded/Assisted mode due to BCI accuracy below 70%, the EEG Accessibility Buggy SHALL limit maximum speed to 3 km/h (50% of Normal Navigation maximum), maintain full obstacle detection and emergency stop capability, and display a continuous amber alert on the Status LED Array and a text notification on the Display Unit. STK-REQ-004 requires manual override with obstacle detection remaining active but specifies no measurable degraded-mode performance floor. STK-REQ-005 requires distinct alerts on mode transitions. 3 km/h limit (half of full speed) reduces collision energy by 75% and gives the care attendant additional reaction time, which is derived from pedestrian collision safety analysis (EN ISO 13482: safety requirements for personal care robots). Obstacle detection must remain active to prevent hazards during reduced user control. | Test |
| SYS-REQ-023 | When the Main Application Processor fails (watchdog timeout exceeding 50ms, voltage rail failure, or CRC fault detected), the Safety Monitor Processor SHALL assert SAFE_STOP, de-energise drive motors, and engage mechanical brakes within 200ms of fault detection, independent of Main Application Processor firmware state. IEC 61508 (Functional safety of E/E/PE safety-related systems) SIL 2 requires independent fault detection and response for System-Essential components. MAP is system-essential (single point of failure for BCI command processing); without a watchdog-monitored independent failover channel, a stuck MAP executing incorrect commands would have no automatic mitigation. The 50ms watchdog timeout and 200ms failsafe response are consistent with SYS-REQ-002 which mandates 200ms total emergency stop latency. This requirement establishes the SYS-level mandate for the independence implemented in ARC-REQ-002 and SUB-REQ-061. | Test |
Subsystem Requirements (SUB) (93)
| Ref | Requirement | V&V |
|---|---|---|
| SUB-BCIPROCESSINGSUBSYSTEM-001 | The Artifact Rejection Engine SHALL reject electromagnetic and muscle artefact from 32-channel EEG within 20ms of epoch receipt, with false rejection of true neural signals not exceeding 10%. 20ms latency budget derived from 50ms total BCI pipeline budget (SYS-REQ-001 <150ms classification latency). False rejection of >10% degrades classification accuracy below the 70% threshold in SYS-REQ-008, causing unnecessary safe-stop transitions. IEC 60601-1 applies to EMC performance of medical devices. | Test |
| SUB-BCIPROCESSINGSUBSYSTEM-002 | The BCI Classifier SHALL achieve a minimum four-class motor imagery and SSVEP classification accuracy of 75% across a 2-minute rolling window during normal operation. 75% accuracy floor is derived from SYS-REQ-008 which triggers adaptive feedback mode at 70%. The 5% margin allows the Command Arbitration Module's confidence threshold (70% per-command) to remain effective without generating spurious safe-stop events under mildly degraded signal conditions. Below 70% system accuracy the user loses meaningful volitional control, creating an unsafe condition. | Test |
| SUB-BCIPROCESSINGSUBSYSTEM-003 | The Command Arbitration Module SHALL emit a validated drive command to the Drive Subsystem interface within 150ms of the corresponding EEG signal epoch being acquired by the EEG Acquisition Module. 150ms end-to-end latency directly derived from SYS-REQ-001. This is the cognitive-motor feedback loop constraint: delays >200ms cause users to generate corrective commands before the original command executes, resulting in command accumulation and erratic vehicle behaviour. 150ms allows 50ms margin below the 200ms perceptual threshold. | Test |
| SUB-BCIPROCESSINGSUBSYSTEM-004 | When BCI signal-to-noise ratio remains below the classification threshold for more than 3 consecutive seconds, the Command Arbitration Module SHALL emit a STOP command to the Drive Subsystem and suppress further drive commands until SNR recovers. Directly implements SYS-REQ-007 at the subsystem level. 3-second timeout balances false-positive rate (transient signal dropout from head movement) against safety risk of continued motion with unreliable control. Safe state is vehicle stop, consistent with the hazard register. SIL-3 requirement because failure to stop on signal loss could result in uncontrolled vehicle motion near vulnerable users. | Test |
| SUB-BCIPROCESSINGSUBSYSTEM-005 | The Feature Extraction Processor SHALL load and apply per-user CSP spatial filter matrices from encrypted calibration storage within 5 seconds of user session initialisation. MoP basis: Published motor imagery BCI research (Blankertz et al. 2008, 'Optimizing Spatial Filters for Robust EEG Single-Trial Analysis', NeuroImage) documents 15–25% accuracy reduction when using population-averaged vs. subject-specific CSP spatial filters across EEG motor imagery tasks. Per-user matrices are therefore essential for the ≥80% classification accuracy required by SYS-REQ-006. 5-second load time is within the SYS-REQ-018 30-second startup budget. Encryption required under STK-REQ-018 (EEG biometric data, GDPR Article 9 special category). Failure to load forces operation on default matrices, triggering SYS-REQ-007 signal degradation pathway and Degraded/Assisted mode. | Test |
| SUB-BCIPROCESSINGSUBSYSTEM-006 | The Artifact Rejection Engine SHALL expose a watchdog interface to the BCI Processing Subsystem supervisor; when no valid epoch output is received for more than 500ms, the supervisor SHALL reset the Artifact Rejection Engine and log the event for post-session analysis. IEC 61508 SIL-3 requires monitoring of autonomous processing functions. The Artifact Rejection Engine is functionally autonomous (runs its own ICA pipeline without per-frame supervision) but can enter a deadlock or memory leak state. 500ms without output is an unambiguous failure indicator — the nominal output period is 500ms (2 epochs/second), so one missed window triggers reset. This provides a bounded recovery time compatible with the BCI pipeline latency budget. | Test |
| SUB-BCIPROCESSINGSUBSYSTEM-007 | The Main Application Processor SHALL expose a USB-C service port accessible on the Electronics Bay panel that provides a diagnostic test suite interface, executing the full motor response, brake torque, sensor calibration, battery cell health, and BCI pipeline integrity test sequence within 20 minutes via authenticated USB connection. SYS-REQ-015 requires a USB-C diagnostic suite completing in 20 minutes. The Main Application Processor hosts the diagnostic executive and has access to all subsystem buses (CAN, I2C, SPI, UART). Authentication is required to prevent unauthenticated firmware or calibration access. 20-minute completion time is derived from scheduled maintenance window constraints in care facility operational planning. | Test |
| SUB-BCIPROCESSINGSUBSYSTEM-008 | The Main Application Processor SHALL encrypt all EEG biometric data using AES-256 at rest and TLS 1.3 in transit, enforce role-based access control with at least three roles (clinical, maintenance, user), and maintain an append-only audit log of all data access events with timestamp, user identity, and operation type. SYS-REQ-019 mandates AES-256 and TLS 1.3 for EEG biometric data. The Main Application Processor is the data custodian for all BCI pipeline data. Three-role RBAC (clinical, maintenance, user) is the minimum partition required by GDPR Article 25 (data protection by design) and IEC 62443 (Security for industrial automation) tier partitioning. Audit logging supports forensic investigation and regulatory compliance. | Test |
| SUB-BCIPROCESSINGSUBSYSTEM-009 | The Artifact Rejection Engine SHALL operate from the 3.3V logic rail supplied by the DC-DC Converter Array, with a maximum peak current draw of 250mA during active signal processing, and SHALL maintain operation without error for supply voltage variation between 3.0V and 3.6V. Lint finding: artifact rejection engine is Powered but has no power source requirements. The ARE is a software-firmware block executing on the BCI DSP and draws power through the DSP supply rail. Bounding the current draw to 250mA peak prevents thermal shutdown of the 3.3V converter during simultaneous EEG acquisition and artifact processing bursts. Brown-out on this rail would cause BCI pipeline failure and trigger emergency stop. | Test |
| SUB-BCIPROCESSINGSUBSYSTEM-010 | While in Normal Navigation mode, the BCI Processing Subsystem SHALL provide a software watchdog that monitors BCI command output validity and SHALL halt command generation and assert a safe-stop signal within 100ms if command outputs deviate from expected bounds or if the watchdog is not kicked within a 200ms window. Lint finding: Normal Navigation mode is a Functionally Autonomous operational state with no safety or override constraints. This requirement addresses the autonomous operation safety gap per IEC 61508 (Functional safety of E/E/PE safety-related systems) SIL-3 requirements for autonomous command generation. The 100ms halt time is bounded by the 200ms total emergency stop response budget from SYS-REQ-002. | Test |
| SUB-BCIPROCESSINGSUBSYSTEM-011 | The EEG Accessibility Buggy electrode interface components that contact the user scalp SHALL be manufactured from materials meeting ISO 10993-1 (Biological evaluation of medical devices — Part 1: Evaluation and testing within a risk management process) biocompatibility requirements for skin-contacting medical devices, and SHALL support decontamination with standard clinical disinfectants between users without degradation of electrical performance. The buggy is Biological/Biomimetic (interfaces with biological EEG signals via wet electrodes on user scalp). Scalp-contact electrodes are skin-contacting medical devices under ISO 10993-1. Clinical deployment in care facilities serving multiple users requires decontamination capability to prevent infection transmission. IEC 60601-1 (Medical electrical equipment — Part 1: General requirements for basic safety) also requires biocompatibility for patient-applied parts. | Analysis |
| SUB-BCIPROCESSINGSUBSYSTEM-012 | The Artifact Rejection Engine SHALL execute as a software module on the Feature Extraction Processor hardware, occupying no more than 30% of available CPU cycles during continuous EEG processing at 250 SPS per channel, with a deterministic maximum latency of 4ms per processing frame. The lint finding flags the Artifact Rejection Engine as lacking Physical Object trait but having physical embodiment constraints. As a software algorithm running on the Feature Extraction Processor, it must be bounded in resource consumption to not starve classifier and acquisition processes. The 30% CPU budget preserves headroom for the BCI Classifier (50%) and overhead (20%). The 4ms latency ensures artifact-free EEG is available within the 10ms BCI processing frame. | Test |
| SUB-BCIPROCESSINGSUBSYSTEM-013 | The Main Application Processor SHALL validate all BCI-derived navigation commands using a cryptographic message authentication code (HMAC-SHA256) when received from any external software interface, and SHALL reject and log any command that fails authentication, missing a valid session token, or arrives via an interface not in the authorised interface table defined during commissioning. Normal Navigation mode and Artifact Rejection Engine are classified as Digital/Virtual with no cybersecurity requirement at SUB level. A BCI mobility device controls physical motion — unauthorised injection of navigation commands could result in collision or unsafe motion. HMAC-SHA256 command authentication provides integrity protection against replay attacks and command injection without requiring a symmetric key exchange per session, which is appropriate for the embedded MAP execution environment. This requirement closes the cybersecurity gap identified by UHT Substrate classification of the Normal Navigation mode (hex 40B72300). | Test |
| SUB-COMMUNICATIONSUBSYSTEM-001 | The Bluetooth LE Module SHALL maintain a stable BLE 5.2 connection to the paired EEG headset at 2.4GHz with a connection interval of 7.5ms, sustaining 32-channel EEG data at 8kHz sample rate (effective throughput 512kbps) within an operating range of 3m with no physical obstructions. BCI signal path requires continuous EEG data at 8kHz to meet the classification accuracy in SYS-REQ-001. The 7.5ms BLE connection interval is the minimum supported by BLE 5.2 and the tightest interval that avoids BCI latency degradation. 3m range covers all typical headset-to-buggy cable routing scenarios within a clinical environment. | Test |
| SUB-COMMUNICATIONSUBSYSTEM-002 | The Communication Controller SHALL enforce a firewall rule that prevents all data traffic originating from the Cellular Modem from reaching the internal CAN bus or I2C/SPI control networks. A cellular modem is an externally accessible network endpoint. Without isolation, a compromised modem could inject spoofed drive or safety commands on the CAN bus, constituting a cybersecurity attack path directly threatening occupant safety. The firewall is the primary control for IEC 62443 network segmentation of the safety domain from the external domain. | Inspection |
| SUB-COMMUNICATIONSUBSYSTEM-003 | When Emergency Stop or seizure detection triggers, the Communication Controller SHALL transmit a BLE 5.0 iBeacon-compatible alert to the facility BLE gateway within 500ms, including device ID, alert type, and GPS coordinates, and simultaneously notify the paired caregiver smartphone. SYS-REQ-017 requires BLE alert transmission within 500ms on emergency triggers. The Communication Controller manages the BLE 5.0 module (nRF52840) and is the component responsible for alert generation. 500ms is the maximum acceptable caregiver notification latency before a seizure or emergency becomes unmanageable. | Test |
| SUB-COMMUNICATIONSUBSYSTEM-004 | The Cellular Modem SHALL authenticate to the remote telemetry server using mutual TLS 1.3 with a device-unique X.509 certificate provisioned at manufacture, rejecting any server certificate not signed by the system's root CA. SYS-REQ-019 requires TLS 1.3 for data in transit. The Cellular Modem is the only component with external IP connectivity; mutual TLS with per-device certificates prevents impersonation of the server (downgrade attack) and spoofing of the device. Device certificates provisioned at manufacture ensure the credential chain cannot be forged in the field. | Test |
| SUB-COMMUNICATIONSUBSYSTEM-005 | The Cellular Modem SHALL transmit session telemetry (location, BCI state, battery, error events) to the remote server at a minimum interval of 10 seconds with a maximum uplink latency of 2 seconds under nominal 4G coverage. Care attendants and clinical teams rely on near-real-time session data for remote supervision of users with severe motor impairments. A 10-second interval balances cellular data consumption against clinical oversight needs. The 2-second uplink latency bound ensures that location and safety events reach the monitoring platform while the user is still at the reported position. | Test |
| SUB-COMMUNICATIONSUBSYSTEM-006 | The Communication Subsystem SHALL provide a USB-C service port that exposes a diagnostic API enabling technicians to execute motor response verification tests and receive pass/fail results with logged timestamps within 10 s of command initiation. SYS-REQ-015 specifies USB-C access to an automated diagnostic suite; the Communication Subsystem hosts the USB-C physical interface and routes diagnostic commands to the Main Application Processor, making it the correct implementation locus. | Test |
| SUB-COMMUNICATIONSUBSYSTEM-007 | When a Seizure Emergency Stop event is triggered, the Communication Controller SHALL transmit a BLE 5.0 emergency alert packet containing device ID, alert type code, GPS coordinates (WGS-84 decimal), and UTC timestamp to the facility emergency system receiver within 500ms of the Emergency Stop command. Derives from SYS-REQ-005 which requires BLE emergency alert transmission to facility emergency system on seizure detection. 500ms transmission budget allows for BLE connection establishment (max 200ms for pre-paired devices) plus packet delivery, while the Emergency Stop itself is completed within 150ms. The facility receiver must get actionable location data to dispatch care staff rapidly. | Test |
| SUB-DRIVESUBSYSTEM-001 | The Motor Controller Unit SHALL implement closed-loop velocity control for each drive motor channel, updating the velocity setpoint at 100 Hz using 1024 PPR quadrature encoder feedback, with a steady-state velocity error not exceeding ±0.1 km/h at any commanded speed. Closed-loop control at 100Hz is required to achieve accurate differential-drive steering. The ±0.1 km/h accuracy threshold is derived from SYS-REQ-003 speed limits: at 6km/h maximum, a ±1.7% error is acceptable for stable path tracking while avoiding overspeed. Encoder feedback rate of 1024 PPR at 250mm wheel diameter gives 0.77mm/pulse resolution, sufficient for the control loop. | Test |
| SUB-DRIVESUBSYSTEM-002 | The Motor Controller Unit SHALL enforce a vehicle speed limit of 6 km/h in Normal Navigation mode and 2 km/h in Restricted mode, clamping any velocity command exceeding these thresholds before the command is applied to the motor drive stages. Derives from SYS-REQ-003. Speed limits are enforced in firmware to prevent unsafe motion: 6km/h is consistent with IEC 62133 electric mobility device guidance for indoor environments, and 2km/h Restricted mode is for narrow corridors and near-bystander situations. Clamping in MCU firmware rather than relying on upstream command rejection provides defence-in-depth at SIL 2. | Test |
| SUB-DRIVESUBSYSTEM-003 | When the Motor Controller Unit receives a kill signal via the CAN safety frame or detects loss of CAN heartbeat for more than 100ms, the Motor Controller Unit SHALL apply regenerative braking to bring both motors to zero velocity within 250ms and hold zero-velocity command until a valid restart sequence is received. Derives from SYS-REQ-002: 250ms safe stop is the system-level budget. The MCU's 250ms hard stop matches the system-level requirement. CAN heartbeat loss at 100ms provides early detection (50% of the 200ms upstream timeout in SUB-REQ-010) to allow regenerative braking time. Regenerative braking is preferred over freewheeling to maintain directional control during deceleration on slopes. | Test |
| SUB-DRIVESUBSYSTEM-004 | The Drive Power Stage SHALL trip the hardware overcurrent protection circuit and isolate the motor phase outputs within 5ms when per-channel motor current exceeds 30A, independent of Motor Controller Unit firmware. Hardware overcurrent protection independent of MCU firmware is required at SIL 2 because firmware-only protection cannot be credited under IEC 61508 (Functional safety of E/E/PE safety-related systems) at SIL 2 without redundant validation. 30A trip threshold is derived from 500W peak motor rating at 48V nominal (10.4A max continuous, 30A provides 3x margin for inrush while protecting MOSFET switches rated at 80V/40A). 5ms trip time ensures MOSFET junctions do not exceed thermal limits. | Test |
| SUB-DRIVESUBSYSTEM-005 | The Left Drive Motor Assembly and the Right Drive Motor Assembly SHALL each provide a minimum continuous shaft output of 250W at 48V DC supply voltage across the operating temperature range of 0°C to 40°C, with the driven wheel maintaining traction on level indoor surfaces up to a 5% gradient. 250W continuous per motor is required to achieve 6km/h with a 150kg total vehicle load (occupant + buggy) on a 5% gradient, per the mechanical traction analysis in the ConOps. 48V supply matches the LiFePO4 battery pack nominal voltage. 0-40°C operating range covers typical indoor clinical and office environments per the operating environment constraint. | Test |
| SUB-DRIVESUBSYSTEM-006 | When the Drive Subsystem detects Motor Controller Unit CAN heartbeat absence exceeding 100 ms, the Drive Subsystem SHALL command both motor drivers to coast-to-stop state and assert MCU_FAULT to the Safety Monitor Processor within 50 ms of timeout detection. Motor Controller Unit (hex D4F57A18) is System-Essential; undetected MCU loss leads to silent loss of propulsion authority. 100 ms heartbeat timeout provides two missed 50 Hz frames before declaring fault, balancing false-positive avoidance with response timeliness. | Test |
| SUB-DRIVESUBSYSTEM-007 | The Motor Controller Unit SHALL implement hardware overcurrent protection independent of the Main Application Processor that disconnects motor phase outputs within 5ms if phase current exceeds 120% of rated maximum, with no firmware execution required for this protection to operate. Motor Controller Unit is classified System-Essential (hex D4F57A18). Firmware-dependent overcurrent protection is insufficient for a SIL-2 drive function: if the MAP is faulted or busy, motor runaway or coil burn is possible within milliseconds. Hardware-only protection eliminates this failure mode and is standard practice in IEC 61800-5-2 (Safety requirements for adjustable speed electrical power drive systems). | Test |
| SUB-DRIVESUBSYSTEM-008 | While in Degraded/Assisted mode, the Drive Subsystem SHALL enforce a maximum speed cap of 3 km/h by limiting PWM duty cycle to 50% of the Normal Navigation maximum, with the speed cap applied in firmware prior to the Motor Controller Unit command, independent of any BCI or joystick input value. SYS-REQ-022 requires 3 km/h maximum in Degraded mode. Implementing the cap in the Drive Subsystem firmware (not in the BCI pipeline) ensures it applies regardless of BCI or joystick source, preventing the cap from being bypassed if the BCI subsystem transitions incorrectly. | Test |
| SUB-DRIVESUBSYSTEM-009 | While operating in Care Attendant Override mode, the Drive Subsystem SHALL respond to joystick steering and throttle inputs within 100ms, maintain obstacle detection response within 200ms, limit maximum speed to 6 km/h, and sustain override operation for the full battery duration specified by SUB-REQ-014 without consuming more than 15% additional power versus Normal Navigation mode at equivalent speed. STK-REQ-004 mandates carer override with obstacle detection active but specifies no measurable performance floor for the override mode. 100ms joystick response derived from SYS-REQ-009 (handover latency). 6 km/h matches Normal Navigation maximum. The original 30-minute duration floor at 50% speed was flagged rt-implausible-value because it is far weaker than the 4-hour battery capacity guarantee in SUB-REQ-014, creating an artificial and non-binding constraint. The revised requirement instead bounds override-mode power consumption relative to Normal Navigation, preventing undisclosed high-drain override modes from undermining the SUB-REQ-014 runtime guarantee. | Test |
| SUB-DRIVESUBSYSTEM-010 | The Drive Subsystem, including the Motor Controller Unit and Motor Power Isolation Relay, SHALL comply with IEC 60601-1 (Medical electrical equipment — General requirements for basic safety and essential performance) for protection against electrical hazards, and all motor drive electronics SHALL meet the EMC requirements of IEC 60601-1-2 (Electromagnetic compatibility — Requirements and tests for medical electrical equipment). Drive subsystem contains 48V DC power electronics in direct proximity to a patient-class user. IEC 60601-1 applies because the EEG Accessibility Buggy is a medical device (confirmed by STK-REQ-010 requirement for design history file and clinical evaluation report). The Motor Controller Unit (MCU) and Motor Power Isolation Relay are classified as Regulated by UHT Substrate but no compliance requirement existed at subsystem level. IEC 60601-1-2 EMC compliance is separately required because the drive PWM switching may interfere with EEG acquisition — this requirement closes that gap with a regulatory floor. | Inspection |
| SUB-HMISUBSYSTEM-001 | The Audio Alert Module SHALL produce an audible tone of minimum 80dB SPL at 1m when an emergency stop is activated, within 100ms of the E-stop signal being asserted, and SHALL sustain this tone until the system transitions out of the E-stop state. MoP basis: IEC 60601-1-8 (Medical electrical equipment — Alarm systems) clause 6.3.2 specifies a minimum of 65 dBA for high-priority alarm signals in medical environments. The 80dB SPL floor in this requirement adds a 15dB safety margin above the IEC 60601-1-8 baseline to account for clinical environment background noise (hospital ward ambient noise typically 60–70 dB, per HSE noise guidance for NHS environments). STK-REQ-005 sets the stakeholder-level threshold at ≥75 dBA at 1m; SUB-REQ-032 allocates the Audio Alert Module a 5dB margin above the stakeholder minimum, accounting for measurement uncertainty and acoustic absorption at distance. 100ms onset ensures auditory alert is concurrent with physical braking deceleration at 6 km/h (vehicle travels <17cm before alert fires). | Test |
| SUB-HMISUBSYSTEM-002 | The Status LED Array SHALL display a distinct colour state for each of: Normal Navigation (green), Degraded/Reduced Mode (amber), E-stop Active (red), Charging (blue), and BCI Calibration (pulsing white), with state transitions completing within 200ms of the triggering event. STK-REQ-005 requires distinct visual alerts for the care attendant. Using the five colours above maps directly to the ConOps operating modes and allows unambiguous state identification without requiring the attendant to read text on the display. 200ms transition time is fast enough to appear instantaneous to the human observer. | Demonstration |
| SUB-HMISUBSYSTEM-003 | When the care attendant activates the override switch, the HMI Subsystem SHALL transfer joystick command authority to the Drive Subsystem within 100ms, suppressing all BCI command outputs for the duration of override mode. SYS-REQ-009 mandates 100ms joystick authority transfer. This decomposes the latency budget to the HMI/Drive interface. Failure to meet this threshold risks momentary loss of directional authority during handover, which is a collision risk in tight corridors. The 100ms bound is derived from vehicle control latency studies in powered wheelchair standards (ISO 7176-11). | Test |
| SUB-HMISUBSYSTEM-004 | The Display Unit SHALL render BCI classification accuracy, vehicle speed, battery state of charge, and active operating mode on a sunlight-readable screen with minimum 300 cd/m2 brightness, updating at minimum 2Hz in Normal Navigation mode. Derived from SYS-REQ-008 (accuracy threshold) and SYS-REQ-018 (calibration readiness). Care attendants require real-time visibility of BCI performance to intervene before accuracy degrades below the 70% transition threshold. A 300 cd/m2 brightness floor ensures readability in hospital dayroom and outdoor settings. 2Hz update prevents perceived lag in a medical device. | Test |
| SUB-HMISUBSYSTEM-005 | The Status LED Array SHALL be visible from any angle within a 120-degree horizontal arc to the rear of the vehicle, with a minimum luminous intensity of 10 mcd per LED element, to allow care attendants approaching from behind to read vehicle state. Care attendants typically approach from behind or to the side of the buggy. An angular field of 120 degrees to the rear ensures the attendant can read the vehicle state (green/amber/red) at normal approach angles without requiring a direct line of sight from the front. The 10mcd intensity is derived from ISO 7176-22 (powered wheelchair signal lamp requirements). | Test |
| SUB-HMISUBSYSTEM-006 | When the care attendant activates the rear-mounted override switch, the HMI Subsystem SHALL assert a hardwired CARER_OVERRIDE signal to the Safety Monitor Processor within 50 ms and maintain the signal for the duration of physical switch engagement. SYS-REQ-009 requires care attendant steering transfer within 100 ms end-to-end; the HMI Subsystem accounts for the first 50 ms of that budget through hardwired (not software) assertion to prevent software-layer latency from delaying the takeover. | Test |
| SUB-HMISUBSYSTEM-007 | When CARER_OVERRIDE is asserted, the HMI Subsystem SHALL route joystick control commands directly to the Drive Subsystem motor controller at a 50 Hz command rate with latency not exceeding 20 ms from joystick input to CAN frame transmission. SYS-REQ-009 requires joystick steering transfer within 100 ms; 20 ms HMI command latency plus 50 ms safety assertion budget leaves 30 ms for drive subsystem response, satisfying the end-to-end bound at 50 Hz control rate. | Test |
| SUB-HMISUBSYSTEM-008 | When the care attendant activates the rear-mounted override switch, the HMI Subsystem SHALL complete authority transfer from BCI commands to joystick steering and throttle within 100ms of switch actuation, measured from the falling edge of the CARER_OVERRIDE signal to the first joystick command accepted by the Drive Subsystem. SYS-REQ-009 requires authority transfer within 100ms. This timing is derived from a 6 km/h maximum speed giving 167mm travel per 100ms; exceeding this window allows the vehicle to travel approximately one chair-width during uncontrolled motion, which is unacceptable for a safety-critical handover. The 100ms budget is decomposed as: 20ms switch debounce, 30ms CARER_OVERRIDE propagation, 50ms Drive Subsystem command accept latency. | Test |
| SUB-HMISUBSYSTEM-009 | When the rolling 2-minute BCI classification accuracy drops below 70%, the Audio Alert Module SHALL emit a 85 dBSPL (at 1m) pulsed tone at 880Hz within 200ms of the accuracy threshold crossing, sustained until the mode transitions or care attendant acknowledges via the HMI. Derives from SYS-REQ-008 which requires audible alert to care attendant when entering Degraded/Assisted mode. 85 dBSPL at 880Hz is audible over typical care facility ambient noise (60-70 dB) without exceeding care setting guidelines. 200ms alert latency is well within the 2-minute rolling window that triggers the mode change, ensuring the care attendant is notified before the buggy is in degraded state for more than a few seconds. | Test |
| SUB-HMISUBSYSTEM-010 | When the rear-mounted override switch is activated, the HMI Subsystem SHALL transfer steering and throttle authority to the rear joystick, disable BCI movement command processing, and confirm handover to the Drive Subsystem within 100ms of the override switch activation signal. Derives from SYS-REQ-009 which requires joystick handover within 100ms of care attendant override. The 100ms budget is split: 20ms for switch debounce and signal propagation, 50ms for authority transfer to Drive Subsystem, 30ms for BCI command disable confirmation. This ensures care attendants can take safe control rapidly during user distress or post-degradation handover without perceptible delay. | Test |
| SUB-HMISUBSYSTEM-011 | While the system is in Degraded/Assisted mode, the Status LED Array SHALL display a continuous amber pattern at 2Hz pulse rate and the Display Unit SHALL present a persistent text notification reading 'DEGRADED MODE — BCI ACCURACY LOW — SPEED LIMITED TO 3 KM/H' on the primary status screen within 100ms of mode entry, remaining visible until mode change. Derives from SYS-REQ-022 which requires amber LED and text notification on entry to Degraded/Assisted mode. The 2Hz amber pulse is distinct from normal mode (solid green) and emergency stop (1Hz red), providing unambiguous visual status across the three primary operating modes. The text notification includes the speed limit to inform both the user and any bystanders of reduced capability. 100ms display latency is within the HMI response budget after mode transition. | Demonstration |
| SUB-PERCEPTIONSUBSYSTEM-001 | The Forward Depth Sensor Array SHALL measure distances in the forward 120-degree arc with a range of 0.05m to 2.0m and an accuracy of plus or minus 50mm at no less than 10Hz, under all operating lighting conditions from 0 lux to 10,000 lux. SYS-REQ-006 mandates detection of obstacles within 2m forward zone. Three VL53L5CX sensors in a 120° arc provide full forward coverage with 8x8 depth grids. Accuracy of ±50mm is sufficient to trigger an alert with >1 update cycle margin at 6 km/h (vehicle travels 167mm per 100ms). 10Hz update rate matches minimum safety reaction loop. | Test |
| SUB-PERCEPTIONSUBSYSTEM-002 | The Perception MCU SHALL process all sensor inputs and emit an obstacle alert frame to the Safety Monitor Processor within 50ms of sensor data arrival, sustaining this throughput at full 10Hz sensor update rate. At 6 km/h the vehicle travels 83mm in 50ms. Combined with forward sensor range of 2m, the 50ms processing budget leaves a minimum 1.9m braking margin for the Safety Subsystem to act. This derives from SYS-REQ-006 and the 20ms relay cutoff time in SYS-REQ-002. | Test |
| SUB-PERCEPTIONSUBSYSTEM-003 | The Side Proximity Sensor Pair SHALL detect objects within 0.5m laterally on each side of the vehicle and deliver a TTL-level alert signal to the Perception MCU within 30ms of intrusion. At 6 km/h during a tight turn, lateral obstacles present risk of entrapment or collision with door frames. The 0.5m detection threshold at 30ms latency provides 83mm travel margin before the safety chain can respond. Derived from STK-REQ-014 (safe stopping distances) and the maximum vehicle width of 700mm per SYS-REQ-010. | Test |
| SUB-PERCEPTIONSUBSYSTEM-004 | When the Perception MCU fails to produce an obstacle alert frame within 150ms of its scheduled transmission window, the Safety Monitor Processor SHALL treat the timeout as an obstacle-present condition and initiate the emergency stop sequence. IEC 61508 (Functional safety of E/E/PE safety-related systems) SIL 2 requires fail-safe behaviour on subsystem communication loss. Absence of sensor data is a credible failure mode (MCU lockup, I2C bus fault). Treating silence as an obstacle-present condition is the most conservative safe state and prevents motion through undetected obstacles. | Test |
| SUB-PERCEPTIONSUBSYSTEM-005 | While vehicle tilt measured by the Inclinometer Tilt Sensor Unit exceeds 15 degrees on any axis, the Perception Subsystem SHALL assert a tilt-hazard signal to the Safety Monitor Processor within 50ms of threshold crossing. SYS-REQ-011 requires braking on 15-degree tilt detection. This decomposes the sensing element to the Perception Subsystem. The 50ms assertion time leaves 150ms for the Safety Monitor Processor to command brake application within the 200ms total SYS-REQ-002 safety response budget. The inclinometer is physically in the Perception subsystem's sensor suite (Electronics Bay mounting). | Test |
| SUB-PERCEPTIONSUBSYSTEM-006 | The Inclinometer Tilt Sensor Unit SHALL operate from a regulated 3.3V supply derived from the DC-DC Converter Array, with a maximum continuous current draw of 10mA, and SHALL maintain measurement accuracy within specification for supply voltage variation of 3.0V to 3.6V. Lint finding: inclinometer is Powered but has no power source requirements. The inclinometer is a MEMS device (e.g. ST LSM6DSO) operating at 3.3V logic level consistent with the Perception MCU. Defining the power envelope prevents sensor brown-out during load transients from the drive motors, which would cause spurious tilt alarms and emergency stops. | Test |
| SUB-PERCEPTIONSUBSYSTEM-007 | While vehicle tilt measured by the onboard inclinometer exceeds 15 degrees in any axis, the Perception Subsystem SHALL continuously publish tilt angle, axis identity, and confidence score to the Safety Monitor Processor at no less than 20 Hz. SYS-REQ-011 triggers automated halt on 15-degree tilt; the Perception Subsystem must provide tilt data at sufficient rate (20 Hz) to ensure the Safety Subsystem can detect and respond within 200 ms before the system enters an unsafe attitude. | Test |
| SUB-PERCEPTIONSUBSYSTEM-008 | When one or more elements of the Forward Depth Sensor Array fail to deliver a valid distance frame within 200ms, the Perception MCU SHALL reduce commanded maximum vehicle speed to 1.5 km/h, assert a sensor-fault alert to the Safety Monitor Processor, and maintain this reduced-speed safe state until all sensor elements are confirmed operational. Partial failure of the forward sensor array reduces obstacle coverage below the full 120-degree arc, creating blind zones. At 1.5 km/h, the vehicle travels 83mm per 200ms safety response cycle, maintaining a minimum 1.9m stopping margin within the 2m sensor range. This degraded safe state allows continued slow-speed operation; total perception failure escalates to emergency stop per the Perception MCU watchdog requirement. | Test |
| SUB-PERCEPTIONSUBSYSTEM-009 | When the Perception MCU fails to emit an obstacle-alert frame to the Safety Monitor Processor for more than 150ms, the Safety Monitor Processor SHALL assert a perception-fault condition: engage emergency braking, disable all drive motor commands, and inhibit restart until the Perception MCU heartbeat is confirmed operational. At 6 km/h, a 150ms perception blackout allows 250mm of undetected travel within the 2m sensor range. The Safety Monitor Processor must treat heartbeat loss as equivalent to an obstacle detection event. 150ms timeout is 1.5 times the nominal 100ms sensor-MCU processing cycle, allowing one missed frame before fault assertion. Derived from SYS-REQ-002 (200ms total safety response budget) and SYS-REQ-006 (obstacle detection). | Test |
| SUB-PERCEPTIONSUBSYSTEM-010 | When either Side Proximity Sensor element fails to respond to its health-check poll within 200ms, the Perception MCU SHALL assert a side-sensor-fault flag to the Safety Monitor Processor and restrict maximum vehicle speed to 0.5 km/h until the fault is cleared by an authorised operator or maintenance reset. Side proximity sensor failure creates a blind zone for lateral obstacles during turns. At 6 km/h in a 700mm-wide vehicle in 900mm doorways this presents entrapment risk per the Daily Independent Navigation ConOps scenario. Reducing speed to 0.5 km/h provides minimum 100ms carer reaction margin to apply emergency stop before a lateral collision. Derived from STK-REQ-014 (safe stopping distances) and doorway clearance analysis. | Test |
| SUB-PERCEPTIONSUBSYSTEM-011 | When the Inclinometer Tilt Sensor Unit fails to deliver a valid tilt measurement to the Perception MCU within 200ms (sensor timeout or invalid checksum on three consecutive frames), the Safety Monitor Processor SHALL treat the failure as a tilt-threshold-exceeded condition and command emergency stop, maintaining halt until the inclinometer is confirmed operational. An inclinometer that goes silent may have failed at or beyond the 15-degree threshold, creating an undetected tip-over hazard. Conservative fail-safe policy per IEC 61508 (Functional safety of E/E/PE safety-related systems) SIL-2 fault-detection requirements. 200ms timeout is 4 times the nominal 50ms assertion time, providing three missed-update margin before fault declaration to avoid nuisance stops. | Test |
| SUB-PERCEPTIONSUBSYSTEM-012 | When the Perception Subsystem fails to publish valid tilt data to the Safety Monitor Processor for more than 100ms during active navigation, the Safety Monitor Processor SHALL treat the publication silence as a tilt-threshold-exceeded condition and command emergency stop, maintaining halt until tilt data publication is confirmed restored. Tilt-data absence during navigation is treated as tilt-threshold exceedance per fail-safe policy. At 20Hz publication rate, 100ms silence represents two missed updates — sufficient margin to distinguish transient jitter from sensor failure without nuisance stops. This ensures the 15-degree tilt halt condition in SYS-REQ-011 cannot be bypassed by a publication failure in the Perception Subsystem. | Test |
| SUB-POWERSUBSYSTEM-001 | The Battery Management System SHALL disconnect the battery pack from the 48V bus within 200ms when any cell temperature exceeds 60°C or any cell voltage exceeds 3.65V. Directly implements SYS-REQ-012 at the BMS level. 200ms disconnect time is the IEC 62133 (Secondary lithium cells — Safety requirements) maximum allowable time before sustained OV or OT can initiate thermal runaway in LiFePO4 chemistry. Failure to disconnect risks irreversible thermal runaway with fire hazard near a vulnerable user. | Test |
| SUB-POWERSUBSYSTEM-002 | The Lithium Iron Phosphate Battery Pack SHALL deliver a minimum of 4 hours continuous operation at rated system load (drive motors, BCI processing, HMI, safety systems combined) before state of charge falls below 10%. Directly implements SYS-REQ-004 at subsystem level. 10% SoC floor preserves headroom for safe-stop execution and BMS shutdown sequence without total power loss. 4-hour operational duration is the STK-derived minimum for full-day facility use between charges. SIL-3 classification rationale: the 10% SoC floor is the trigger condition for the SIL-3 safe-stop sequence defined in the companion failure-mode requirement (idempotency:fm-sub-014-battery-socdepleted-717). The battery pack capacity requirement is the performance prerequisite for that safety function — battery depletion before 10% SoC remaining would prevent safe-stop execution, resulting in uncontrolled motion hazard H-001 and tip-over hazard H-005. SIL-3 is appropriate because loss of this function could result in serious or fatal injury to the EEG-impaired user. | Test |
| SUB-POWERSUBSYSTEM-003 | The DC-DC Converter Array SHALL maintain each output rail (12V, 5V, 3.3V) within ±5% of nominal voltage under all load conditions from 10% to 100% rated current, with output ripple not exceeding 50mV peak-to-peak. IEC 60601-1 (Medical electrical equipment — General requirements for basic safety) requires stable power supply to safety-critical electronics. ±5% regulation covers the input tolerance range of embedded processors and wireless modules. 50mV ripple is the maximum specification for the BCI processing modules' switching noise sensitivity on EEG acquisition circuitry. | Test |
| SUB-POWERSUBSYSTEM-004 | The Charge Controller SHALL charge the battery pack from 20% to 100% state of charge within 3 hours when connected to a 240V AC facility supply. SYS-REQ-014 requirement cascaded directly. 3-hour charge time allows overnight charging on standard facility schedules (facility changeover at 18:00, vehicle available by 21:00 for next-day use). Faster charging is not feasible within the 3kW facility outlet rating while maintaining the CC/CV profile required for LiFePO4 longevity. SIL escalation resolution: the SIL-3 tag on this requirement reflects its role as the primary charge timing specification for the SIL-3 power system. However, the charge timing function itself is not the SIL-3 safety function — the mains fault isolation function is (addressed in companion requirement idempotency:fm-sub-016-charger-mainsfault-717 at SIL-2). This requirement's SIL-3 tag should be understood as marking it as part of the SIL-3 power subsystem scope, not as claiming the charge timing is itself a SIL-3 safety function. The IEC 62368-1 fault isolation companion requirement carries the appropriate SIL-2 classification for the fault-isolation function. | Test |
| SUB-POWERSUBSYSTEM-005 | The Charge Controller SHALL accept charging input from a facility charging dock providing 230V 50Hz or 120V 60Hz AC mains, and SHALL complete pack charge from 20% to 100% state of charge within 4 hours at each nominal supply voltage. SYS-REQ-014 specifies 4-hour charging from facility dock at both EU and US mains voltages. The Charge Controller is the Power Subsystem component responsible for dock interface and CC/CV charge management. Compliance with both supply standards is required for international deployment in care facilities. | Test |
| SUB-POWERSUBSYSTEM-006 | When connected to a facility charging dock providing 230V 50Hz AC supply, the Power Subsystem onboard charger SHALL limit inrush current to less than 16A peak, regulate charging current to maintain cell temperature below 45°C, and complete charge from 20% to 100% SoC within 4 hours. SYS-REQ-014 sets the 4-hour charge window; the Power Subsystem must manage inrush and thermal limits to use facility power safely and meet the charge time without exceeding the 16 A standard socket circuit protection threshold. | Test |
| SUB-POWERSUBSYSTEM-007 | The Charge Controller SHALL accept 230V 50Hz or 120V 60Hz mains input via the facility charging dock connector and charge the Lithium Iron Phosphate Battery Pack from 20% to 100% State of Charge within 4 hours using CC-CV charging profile, with automatic termination and trickle maintenance. Derives from SYS-REQ-014 which specifies the 4-hour charge window from 20% to 100% SOC. The LiFePO4 48V 30Ah pack requires approximately 28.8Ah at 48V = 1.38 kWh from 20% to 100%. A CC-CV profile at 10A charge current achieves this in under 3.5 hours with end-of-charge cut-off, providing margin against cell aging degradation. Dual-voltage acceptance (230V/120V) enables international facility deployment. | Test |
| SUB-POWERSUBSYSTEM-008 | When the Battery Management System fails to disconnect the battery pack from the 48V bus within 250ms of an overvoltage or overtemperature detection, the Safety Monitor Processor SHALL detect the BMS watchdog timeout and assert system-wide emergency stop within 50ms. BMS disconnect failure leaves LiFePO4 cells at sustained overvoltage or overtemperature, the initiating conditions for thermal runaway per IEC 62133 (Secondary lithium cells — Safety requirements). The Safety Monitor Processor's independent watchdog on the BMS status line ensures the safety chain remains active even if the BMS processor itself fails. 250ms detection covers the 200ms BMS disconnect budget plus 50ms measurement margin. | Test |
| SUB-POWERSUBSYSTEM-009 | When the Lithium Iron Phosphate Battery Pack state of charge reaches 10%, the Power Subsystem SHALL activate a safe-stop sequence: halt all drive motor commands within 5 seconds, engage electromechanical parking brakes, sustain Safety Monitor Processor and emergency braking power for a minimum of 5 minutes, and assert a low-battery HMI alert. Loss of drive power at SoC below 10% without a controlled safe-stop creates H-005 (tip-over) and H-001 (uncontrolled motion) hazards if brakes are not engaged before total power loss. Five-minute emergency power reserve covers safe user evacuation per STK-REQ-002 minimum carer response time. This failure-mode requirement also addresses the rt-sil-escalation finding on SUB-REQ-014: the SIL-3 classification applies to the safety-power maintenance function, not to the 4-hour runtime performance floor. | Test |
| SUB-POWERSUBSYSTEM-010 | When any DC-DC Converter Array output rail deviates more than 10% from nominal voltage for more than 100ms, the Safety Monitor Processor SHALL assert a power-fault condition, command emergency braking, disable all drive motor control signals, and maintain power-fault safe state until the rail recovers to within 5% of nominal and an authorised operator clears the fault. Processor and sensor power deviation beyond 10% causes undefined behaviour in BCI processing, Perception MCU, and Safety Monitor Processor sub-circuits. Transition to power-fault safe state (drives off, brakes on) prevents uncontrolled motion during supply instability per IEC 60601-1 (Medical electrical equipment — General requirements for basic safety). The 100ms tolerance window matches the minimum hold-up time of DC-DC filter capacitors before output degrades below logic-level thresholds. | Test |
| SUB-POWERSUBSYSTEM-011 | When the Charge Controller detects a mains supply fault (supply voltage outside 207V-253V AC, frequency outside 47Hz-53Hz, or ground fault current exceeding 10mA RMS), it SHALL disconnect from the facility mains supply within 200ms, lock the charge port relay, and assert a charge-fault alert on the HMI display. Mains fault conditions during charging present fire and electric shock hazards in a care environment. 200ms disconnect is within IEC 62368-1 (Audio/video and IT equipment — Safety requirements) fast overcurrent protection requirements. Ground fault detection at 10mA RMS is required by IEC 60364-4-41 for care environments where users have reduced protective reflexes. This also addresses the rt-sil-escalation finding on SUB-REQ-016: the SIL-relevant function is fault isolation, not the 3-hour charge timing. | Test |
| SUB-POWERSUBSYSTEM-012 | When the Charge Controller detects mains supply voltage outside 207V-253V AC at 50Hz or 102V-132V AC at 60Hz at the facility dock connector, it SHALL reject the connection, maintain galvanic isolation from the supply, and display a supply-incompatible warning on the HMI. Operating the Charge Controller on an out-of-range supply risks uncontrolled charging current that could trigger thermal runaway in the LiFePO4 pack. Maintaining galvanic isolation as the rejection safe state aligns with IEC 62368-1 (Audio/video and IT equipment — Safety requirements) energy hazard reduction requirements. Voltage acceptance windows are plus or minus 10% of nominal per IEC 60038 standard voltages. | Test |
| SUB-POWERSUBSYSTEM-013 | When the 3.3V supply to the Inclinometer Tilt Sensor Unit deviates outside the 3.0V-3.6V operating range for more than 50ms, the DC-DC Converter Array health monitor SHALL assert a sensor-power fault to the Safety Monitor Processor, causing immediate vehicle halt and inhibiting motion until the 3.3V rail returns to within specification. Inclinometer operation below 3.0V produces out-of-specification tilt readings, creating false-negative tilt alarms and potential for undetected tip-over. 50ms fault assertion tolerance matches the maximum hold-up time of 3.3V rail decoupling capacitors before output degrades below the sensor minimum operating threshold. The safety impact is equivalent to tilt-sensor failure under SYS-REQ-011 and warrants immediate halt. | Test |
| SUB-POWERSUBSYSTEM-014 | When inrush current to the Power Subsystem charger exceeds 16A peak or cell temperature during charging exceeds 45°C for more than 10 seconds, the Charge Controller SHALL interrupt the charge cycle within 100ms, isolate from the facility mains supply, and assert a charge-fault alert that persists until acknowledged by an authorised operator. Inrush exceeding 16A may trip facility circuit breakers per BS EN 60898-1 (Electrical accessories — Circuit-breakers for overcurrent protection) 16A Type B/C trip curves. Cell temperature exceeding 45 degrees C indicates abnormal electrochemical activity; IEC 62133 (Secondary lithium cells — Safety requirements) specifies 45 degrees C as the maximum permissible cell temperature during charging. Persistent fault state prevents automatic resumption without operator acknowledgement, complying with IEC 60601-1 alarm persistence requirements. | Test |
| SUB-POWERSUBSYSTEM-015 | When the Charge Controller fails to reach 100% state of charge within 5 hours of charge initiation, it SHALL terminate the charge cycle, log a battery-health fault event with timestamp to the CMMS interface, and alert the facility operator via the HMI display. CC-CV charging the 48V 30Ah LiFePO4 pack from 20% to 100% requires approximately 1.4 kWh; at 10A charge current this completes in 3.5 hours under normal conditions. Five hours allows for capacity degradation to approximately 70% of rated before flagging — at which point battery replacement is required to maintain the 4-hour operational duration in SUB-REQ-014. Failure to terminate indicates abnormal internal resistance increase per IEC 62133 (Secondary lithium cells — Safety requirements) and requires maintenance assessment. | Test |
| SUB-SAFETYSUBSYSTEM-001 | The Safety Monitor Processor SHALL operate on a processor with no shared memory, clock domain, or power rail with the main application processor, and SHALL maintain its safety state machine execution at 200Hz even when the main application processor is in fault state. IEC 61508 (Functional safety of E/E/PE safety-related systems) SIL 3 requires that safety functions be independent of the control path. If the Safety Monitor Processor shared resources with the main processor, a single processor fault could simultaneously disable vehicle control and safety response, violating independence and allowing uncontrolled motion — hazards H-001 and H-006. | Test |
| SUB-SAFETYSUBSYSTEM-002 | The Motor Power Isolation Relay SHALL disconnect the 48V motor drive power rail within 20ms of receiving the de-energise command from the Safety Monitor Processor, under all load conditions from 0A to 200A. The 200ms E-stop response budget allocated in SYS-REQ-002 (derived from H-001 severity and stopping distance analysis at 6 km/h maximum speed) requires relay actuation <20ms to allow margin for brake actuation time. Mechanical relay de-energisation is the single longest latency element; a longer response risks the vehicle travelling an additional 33mm per ms, which at 20ms already represents 33cm of uncontrolled motion. | Test |
| SUB-SAFETYSUBSYSTEM-003 | The Seizure Detection Module SHALL detect generalised spike-and-wave EEG activity exceeding 3 Hz amplitude and >30µV peak-to-peak across all acquisition channels and output a seizure flag to the Safety Monitor Processor within 150ms of seizure onset, with a false positive rate not exceeding 1 per 8 hours of operation. H-006 (catastrophic severity) requires seizure detection to precede motor response — 150ms detection plus relay actuation leaves within the 200ms SYS-REQ-002 window. False positive limit of 1 per 8-hour session is derived from stakeholder acceptability analysis: more frequent nuisance stops would cause users to abandon the system, defeating its purpose as a mobility aid. Algorithm validated against CHB-MIT epilepsy EEG dataset. | Test |
| SUB-SAFETYSUBSYSTEM-004 | The Inclinometer Tilt Sensor Unit SHALL measure vehicle pitch and roll continuously at 100Hz with accuracy of ±0.5° and SHALL trigger an E-stop command via the Safety Monitor Processor when tilt in any axis exceeds 15 degrees for more than 200ms. SYS-REQ-011 derives from H-005 (critical severity): vehicle tipping on slopes where user cannot self-extract. 15° threshold is derived from EN 12184 (electrically powered wheelchairs) stability testing requirements — vehicles must not tip under static conditions up to this angle. 200ms debounce prevents nuisance stops from dynamic bumps while still catching sustained tilt indicating a genuine tip-over condition. | Test |
| SUB-SAFETYSUBSYSTEM-005 | The Manual Emergency Stop Button SHALL be hardwired directly to the Motor Power Isolation Relay coil circuit in series, such that button actuation disconnects motor power without software mediation, within 5ms of button contact closure. Software-mediated E-stop cannot satisfy SIL 3 (IEC 61508) because it introduces a single point of failure in the software execution path. Hardwired series circuit means no combination of software fault, processor reset, or firmware bug can prevent E-stop actuation. 5ms latency is achievable with direct relay contact in series — it is the emergency stop mechanism of last resort required by EN 12184 for powered wheelchairs. | Test |
| SUB-SAFETYSUBSYSTEM-006 | When any safety trigger is received by the Safety Monitor Processor — including BCI signal loss notification, seizure flag, tilt threshold exceeded, manual E-stop, or main processor heartbeat failure — the Safety Subsystem SHALL transition to and maintain Emergency Stop state within 200ms, including relay de-energisation, brake command, and HMI alert outputs. IEC 61508 SIL 3 requires a defined safe state for every safety function. The safe state for this system is motor power removed and brakes engaged. 200ms total budget is derived from stopping distance analysis: at 6 km/h maximum speed, a 200ms response results in 33cm of forward travel before braking begins — within the 2m obstacle detection zone defined in SYS-REQ-006, leaving 1.67m braking distance for the mechanical brake. | Test |
| SUB-SAFETYSUBSYSTEM-007 | The Safety Monitor Processor SHALL monitor a heartbeat signal from the main application processor, and SHALL trigger Emergency Stop if the heartbeat is absent for more than 500ms or if the heartbeat period deviates by more than 20% from the nominal 100ms period. Main processor failure (software hang, voltage fault, thermal fault) is not detectable by the main processor itself. Watchdog heartbeat is the only mechanism by which the independent Safety Monitor Processor can detect this class of failure and transition to safe state. 500ms absence timeout: derived from worst-case main processor boot time (allowing 5 missed beats) versus the need to detect a genuine hang within 2 processor cycles. | Test |
| SUB-SAFETYSUBSYSTEM-008 | The Safety Subsystem SHALL be implemented as a physically separate electronics module from the Main Application Processor, housed within the Electronics Bay on an independent PCB with independent power input, to ensure that a hardware fault in the main processing chain cannot corrupt safety function execution. Lint finding: safety subsystem lacks Physical Object trait but has physical embodiment constraints. IEC 61508 SIL-3 requires independence between safety function and non-safety processing to prevent common-cause failures. The physical separation on an independent PCB with independent power ensures the safety monitor can operate when the main processor fails, which is the primary failure mode requiring emergency braking. | Inspection |
| SUB-SAFETYSUBSYSTEM-009 | When the facility emergency system transmits a halt command via the 2.4 GHz wireless interface, the Safety Subsystem SHALL apply both motor power isolation relays and engage electromagnetic braking within 150 ms of signal receipt. SYS-REQ-005 mandates facility emergency integration but assigns no subsystem-level implementation. The Safety Subsystem owns motor de-energisation; 150 ms is derived from the 200 ms SYS-level bound minus 50 ms signal propagation budget for the worst-case wireless link. | Test |
| SUB-SAFETYSUBSYSTEM-010 | When the Safety Monitor Processor detects Main Application Processor watchdog timeout exceeding 200 ms, the Safety Subsystem SHALL assert SAFE_STOP, halt all motor commands, and log a processor fault record to non-volatile storage. Main Application Processor (hex D2F51008) is System-Essential; loss of the MAP without a safety response leaves the drive subsystem without commands, creating an uncontrolled state. IEC 61508 SIL-2 requires defined response to essential processor failure. | Test |
| SUB-SAFETYSUBSYSTEM-011 | The Safety Subsystem Safety Monitor Processor SHALL be developed and validated in accordance with IEC 61508-3 (Functional Safety of Electrical/Electronic/Programmable Electronic Safety-related Systems — Part 3: Software requirements) at SIL 3, with documented V-model lifecycle artefacts including hazard and risk analysis, software safety requirements specification, and independent verification. Safety Monitor Processor (hex D5F37858) is Regulated and Institutionally Defined; IEC 61508 (Functional safety of E/E/PE safety-related systems) is the applicable standard for safety-critical embedded processors in this domain. SIL 3 is inherited from the Safety Subsystem parent requirement hazard classification. | Inspection |
| SUB-SAFETYSUBSYSTEM-012 | The Manual Emergency Stop Button SHALL use a dual-channel NC (normally-closed) contact circuit wired in series with the Motor Power Isolation Relay coil, such that loss of either channel independently de-energises the relay and halts motor drive within 20ms. Emergency stop is classified System-Essential (hex 408D6AC0); a single-channel E-stop circuit is a single point of failure on a SIL-3 function. Dual NC contacts ensure any wiring fault or contact failure still de-energises the relay, meeting IEC 62061 PLd requirements for safety function SF1. | Test |
| SUB-SAFETYSUBSYSTEM-013 | When the Safety Monitor Processor detects Main Application Processor failure (watchdog timeout, CRC fault, or voltage rail collapse), the Safety Subsystem SHALL assume sole command authority, hold current velocity to zero, and maintain Emergency Stop state until manual reset, with no reliance on MAP firmware for this transition. Main Application Processor is classified System-Essential (hex D2F51008). Without explicit failover specification, a MAP crash could leave the drive system in an undefined state. This requirement ensures the Safety Monitor Processor has unconditional authority on MAP failure, consistent with IEC 61508 SIL-3 defensive design. | Test |
| SUB-SAFETYSUBSYSTEM-014 | The Safety Subsystem SHALL be certified to Safety Integrity Level 3 (SIL 3) per IEC 61508 (Functional safety of electrical/electronic/programmable electronic safety-related systems), with a third-party functional safety assessment covering hardware fault tolerance, systematic capability, and software development process. Safety Subsystem is classified Regulated (hex D7F73058). The EEG buggy is a medical-adjacent personal mobility device for users who cannot remove themselves from a hazardous situation during a seizure event. SIL-3 certification is required because a Safety Subsystem failure combined with a seizure event (probability of demand: multiple times per year for epileptic users) gives an unacceptable combined risk. Third-party assessment is required by the UK Medical Device Regulations 2002 (as amended) for Class IIa active devices. | Inspection |
| SUB-SAFETYSUBSYSTEM-015 | The Inclinometer Tilt Sensor Unit SHALL measure vehicle pitch and roll at 20Hz, and when tilt exceeds 12 degrees in any single axis or 10 degrees combined vector, SHALL issue a pre-warning signal to the Safety Monitor Processor; when tilt exceeds 15 degrees in any axis the Safety Monitor Processor SHALL command immediate brake application and motion inhibit within 50ms. Derives from SYS-REQ-011 which requires braking on 15-degree tilt detection. A pre-warning at 12 degrees gives the Safety Monitor Processor 150ms lead time (at typical incline approach speeds of 0.8 km/h) before the 15-degree hard stop, enabling softer brake application and reducing tip-over risk. The 50ms response time from threshold crossing to brake application is necessary to arrest motion before tilt increases to 18 degrees (tip threshold) at maximum buggy speed. | Test |
| SUB-VEHICLEPLATFORM-001 | The Chassis Frame SHALL withstand a static load of 150kg distributed across the seat mounting points without permanent deformation, and a dynamic impact load of 3g vertical shock without fracture, in accordance with ISO 7176-8 (Static, impact, and fatigue strengths). A 150kg gross vehicle weight covers the 99th percentile adult occupant mass plus battery and electronics. The 3g shock load covers a threshold crossing at 6 km/h. ISO 7176-8 is the applicable standard for powered wheelchair structural integrity; failure to meet this would result in frame collapse under foreseeable use conditions. | Test |
| SUB-VEHICLEPLATFORM-002 | The Electronics Bay SHALL maintain an internal temperature below 70°C for all electronics mounted within it while dissipating up to 40W total under an ambient temperature of 40°C, with the vehicle stationary and no forced air flow. The processor and power conversion components within the Electronics Bay have a maximum junction temperature of 85 degrees Celsius; maintaining the bay below 70 degrees provides a 15 degree thermal margin. 40W is the worst-case total dissipation of all hosted components at peak load. Passive cooling must work with the vehicle stationary as active cooling adds failure modes. | Test |
| SUB-VEHICLEPLATFORM-003 | The Seat and Postural Support System SHALL accommodate occupants from 40kg to 120kg body mass and from 1400mm to 1900mm stature, providing a minimum of 15 degrees of backrest recline adjustment and a lap belt that tightens to resist forward displacement under 3g deceleration. ISO 7176-15 (Wheelchairs — Requirements and test methods for wheelchairs used in motor vehicles) defines the occupant range for accessibility equipment. 3g deceleration matches the emergency stop force at 6 km/h. Failure to restrain the occupant during E-stop is a direct patient safety hazard. | Test |
| SUB-VEHICLEPLATFORM-004 | The Wheel and Caster Assembly SHALL provide a turning radius not exceeding 600mm (measured from vehicle centre to outer wheel track) to allow navigation through standard 900mm accessible doorways with a minimum 150mm clearance on each side, while maintaining traction on surfaces inclined up to 6 degrees. Derived from SYS-REQ-010 (700mm vehicle footprint and accessibility environments). A 900mm doorway minus 150mm clearance each side leaves 600mm for the vehicle width plus the swept turning radius. Compliance with BS 8300 (Design of an accessible and inclusive built environment) requires navigation through standard accessible doorway widths. 6-degree gradient is the maximum ramp slope in UK building regulations Part M. | Test |
| SUB-VEHICLEPLATFORM-005 | The Electronics Bay SHALL provide IP54 environmental protection per IEC 60529 (IEC 60529: protected against dust ingress at IP5X — wire probe 1mm dia. does not penetrate; protected against water spray from any direction at IP4X), maintaining this rating through all maintenance access cycles, with a minimum 100 maintenance access cycles before seal degradation below IP54. Derived from SYS-REQ-010 and expected deployment in care facilities. Hospital environments include wet floor cleaning with mop spray and occasional outdoor transport. IP54 is the minimum medical device enclosure rating for mobile use (IEC 60601-1 clause 11.6.5). The 100-cycle maintenance life ensures IP rating persists through the 5-year expected service life at quarterly inspection intervals. | Test |
| SUB-VEHICLEPLATFORM-006 | The Vehicle Platform Electronics Bay SHALL provide a USB-C 3.1 Gen 1 service port that exposes an automated diagnostic test suite capable of verifying motor response (peak torque within 5% of nominal), brake torque (hold force >= 80N), sensor calibration (all axes within 2% of reference), battery cell health (internal resistance and capacity), and BCI pipeline integrity (signal-to-noise ratio >= 20dB), with full suite completion within 20 minutes. Derives from SYS-REQ-015 which requires an automated diagnostic suite via USB-C service port. USB-C 3.1 Gen 1 provides 5 Gbps bandwidth and 5A power delivery for bench test equipment. Each diagnostic metric has explicit acceptance criteria to make the test deterministic and repeatable. The 20-minute window accommodates preventive maintenance between shifts without disrupting care schedules. | Demonstration |
| SUB-VEHICLEPLATFORM-007 | The Chassis Frame SHALL be constructed from aluminium alloy (6061-T6 or equivalent) with a minimum wall thickness of 3mm at structural load points, providing a rated static load capacity of 150kg (user 120kg + equipment 30kg), with a maximum deflection of 2mm under full load, and shall be corrosion-resistant to humidity up to 95% RH for indoor care facility environments. Lint finding: Chassis Frame is classified as Physical Medium but has no material property requirements. 6061-T6 aluminium provides an acceptable strength-to-weight ratio for medical mobility equipment (yield strength 276 MPa). 150kg load capacity with 2:1 safety margin covers the 95th percentile user weight plus equipment. 95% RH corrosion resistance is required for care facility environments including wet areas and cleaning protocols. | Test |
| SUB-VEHICLEPLATFORM-008 | The Electronics Bay SHALL be constructed from steel or aluminium enclosure rated IP54 (dust-protected, splash-resistant), with internal thermal management maintaining component ambient temperature between 0°C and 55°C during operation, and shall withstand vibration levels up to 2g at 5-50Hz without component dislodgement or connector failure. Lint finding: Electronics Bay classified as Physical Medium but has no material property or environmental requirements. IP54 is the minimum for care facility environments where cleaning fluids may be applied nearby. The 0-55°C thermal range matches the operating envelope of COTS embedded processors and power electronics within. 2g vibration at 5-50Hz reflects doorway-crossing and ramp-traversal shock loads in a care facility environment. | Test |
| SUB-VEHICLEPLATFORM-009 | The Chassis Frame SHALL be designed and tested in accordance with ISO 7176-8 (Requirements for static, impact, and fatigue strengths for wheelchairs) for structural adequacy under static loading of 1.5× maximum user mass plus equipment, and shall withstand impact loads of 70J without permanent deformation of safety-critical members. Chassis Frame is classified as Regulated and Structural by UHT Substrate. ISO 7176-8 is the applicable standard for powered wheelchair structural requirements, which is the closest normative framework for a BCI-controlled mobility device. Without a structural compliance requirement, there is no design floor for chassis member sizing against user mass plus overturning loads. 1.5× safety factor and 70J impact threshold are drawn from ISO 7176-8 Table 1 for Class B (indoor/light outdoor) powered wheelchairs, consistent with the care facility operating environment defined in STK-REQ-013. | Test |
| SUB-VEHICLEPLATFORM-010 | After any chassis shock event exceeding 3g vertical acceleration detected by the inclinometer shock channel, the Safety Monitor Processor SHALL assert a structural-integrity-check-required flag, inhibit all vehicle propulsion, and require authorised maintenance acknowledgement before resuming normal operation. A 3g impact at the ISO 7176-8 (Static, impact, and fatigue strengths for wheelchairs) chassis load limit may cause micro-fractures or fastener loosening not visible externally. Inhibiting motion after a 3g shock event prevents operation with potentially compromised structural integrity. The inclinometer shock detection channel on the ST LSM6DSO used in the Perception Subsystem provides the detection mechanism without additional hardware. This defines the safe state for chassis structural limit exceedance identified by the rt-missing-safe-state finding on SUB-REQ-027. | Inspection |
Interface Requirements (IFC) (31)
| Ref | Requirement | V&V |
|---|---|---|
| IFC-BCIPROCESSINGSUBSYSTEM-001 | The interface between the EEG Accessibility Buggy and the EEG Headset SHALL use Bluetooth Low Energy 5.0 to stream 16-32 channels of 24-bit EEG data at 250 Hz with end-to-end latency not exceeding 50ms from electrode to onboard processor. External interface: the headset is the sole BCI input device. BLE 5.0 provides sufficient bandwidth (~2 Mbps) for 32×24bit×250Hz = 192 kbps with margin. 50ms latency budget is derived from the 200ms E-stop requirement minus processing and actuation time. | Test |
| IFC-BCIPROCESSINGSUBSYSTEM-002 | The interface between the EEG Acquisition Module and the Artifact Rejection Engine SHALL transfer 32-channel EEG sample arrays at 256 samples/second with a maximum inter-process latency of 5ms and sample loss rate not exceeding 0.1%. 256 Hz is the headset sampling rate; all 32 channels required for spatial filtering in artifact rejection. 5ms latency budget is allocated from the 20ms artifact rejection window. 0.1% sample loss is the threshold at which artifact rejection algorithms begin to produce corrupted output windows, as gap-filling interpolation errors compound across the 1-second epoch. | Test |
| IFC-BCIPROCESSINGSUBSYSTEM-003 | The interface between the Artifact Rejection Engine and the Feature Extraction Processor SHALL transfer cleaned 32-channel EEG epochs in 1-second windows with 50% overlap, formatted as float32 arrays, at a throughput of 2 epochs/second per channel. 1-second window with 50% overlap is the standard for motor imagery classification: shorter windows sacrifice spectral resolution, longer windows add latency. Float32 format preserves dynamic range without overflow on standard DSP operations. 2 epochs/second output rate is the foundation for the 150ms pipeline latency in SUB-REQ-010. | Test |
| IFC-BCIPROCESSINGSUBSYSTEM-004 | The interface between the Feature Extraction Processor and the BCI Classifier SHALL pass feature vectors containing CSP-projected band powers and SSVEP spectral amplitudes as float32 vectors, with timestamp and quality index, within 30ms of epoch receipt. Feature vector format must include quality index (derived from electrode contact impedance) to allow the classifier to apply quality-weighted inference. 30ms is the allocation within the 150ms pipeline budget after 5ms acquisition and 20ms artifact rejection, leaving 50ms for classification and 45ms for arbitration. | Test |
| IFC-BCIPROCESSINGSUBSYSTEM-005 | The interface between the BCI Classifier and the Command Arbitration Module SHALL pass command probability vectors for four navigation classes (forward, left, right, stop) as float32 with per-class confidence values, SNR index, and rolling 2-minute accuracy metric, at minimum 2Hz. All four probability values required so the Command Arbitration Module can apply multi-class confidence thresholding and detect ambiguous dual-intent activations. Rolling accuracy metric enables SYS-REQ-008 adaptive mode transition without querying the classifier. SNR index enables SYS-REQ-007 signal-loss detection at the arbitration layer without feedback to the acquisition stage. | Test |
| IFC-BCIPROCESSINGSUBSYSTEM-006 | The interface between the Command Arbitration Module and the Drive Subsystem SHALL use a CAN 2.0B message at 500 kbit/s, transmitting validated drive command (4 discrete values) and a 16-bit cyclic status counter, with maximum transmission latency of 5ms. CAN 2.0B is selected for deterministic latency and EMI robustness in the motor-drive environment (12V bus noise). Status counter enables Drive Subsystem to detect missed arbitration frames and transition to safe stop. 5ms transmission latency is within the 150ms pipeline budget. CAN is consistent with the Drive Subsystem architecture decision (ARC-REQ-001). | Test |
| IFC-COMMUNICATIONSUBSYSTEM-001 | The EEG Accessibility Buggy SHALL communicate with the Companion App via BLE 5.0 LE Secure Connections (AES-CCM-128), providing status updates at ≥1 Hz and emergency notifications with ≤500ms latency. External companion app interface for carer situational awareness. BLE 5.0 LE Secure Connections (LESC) with AES-CCM-128 is the correct BLE 5.0 security mechanism (replaces the imprecise 'TLS 1.3 equivalent' phrasing). GDPR Article 9 requires link-layer encryption for EEG and health-status data. The ≥1 Hz status rate and ≤500ms emergency latency are derived from VER-REQ-109 acceptance criteria, which were validated against carer response-time requirements in the Signal Degradation scenario. | Test |
| IFC-COMMUNICATIONSUBSYSTEM-002 | The interface between the EEG Accessibility Buggy and the Facility CMMS SHALL use a REST API over facility Wi-Fi (802.11ac) with TLS 1.3 encryption for automated maintenance log submission, fault reporting, and fleet telemetry, authenticated via API key or OAuth 2.0. External interface: CMMS integration automates compliance evidence for facility management. Wi-Fi provides sufficient bandwidth for periodic telemetry and maintenance logs. TLS 1.3 and authentication prevent unauthorised fleet data access and comply with GDPR for device usage data. | Test |
| IFC-COMMUNICATIONSUBSYSTEM-003 | The interface between the Communication Controller and the Bluetooth LE Module SHALL use UART at 1Mbps with hardware flow control (RTS/CTS), transferring HCI command and event packets per the Bluetooth HCI specification, with a maximum transfer latency of 2ms per HCI packet. HCI over UART at 1Mbps is the standard interface for Nordic nRF52840 host communication. Hardware flow control prevents buffer overflow at the 8kHz EEG data rate. 2ms maximum latency ensures the BLE connection interval of 7.5ms is not consumed by interface overhead. | Test |
| IFC-COMMUNICATIONSUBSYSTEM-004 | The interface between the Communication Controller and the Cellular Modem SHALL use USB 2.0 (CDC-ECM class) at 480Mbps with AT-command control channel, providing the Communication Controller with Ethernet-over-USB connectivity for LTE data at a maximum round-trip latency of 100ms to the LTE base station. The Communication Controller acts as data gateway and must command-and-control the Cellular Modem (APN config, registration, reset). USB CDC-ECM provides a standard IP stack interface avoiding proprietary serial AT tunnelling of IP frames. The 100ms RTT bound enables the 2-second telemetry uplink latency in SUB-REQ-046. | Test |
| IFC-COMMUNICATIONSUBSYSTEM-005 | The interface between the Bluetooth LE Module and the EEG headset SHALL use BLE 5.2 with a connection interval of 7.5ms, carrying 8-channel 250Hz EEG sample packets encoded in the EEG Headset Profile (proprietary GATT service) with end-to-end latency from electrode to BCI Acquisition Module not exceeding 20ms. The 50ms end-to-end BCI latency budget (SYS-REQ-001) allocates 20ms to wireless transport. BLE 5.2 at 7.5ms connection interval delivers 8-channel 16-bit EEG data (32 bytes per packet) within this window. Longer connection intervals cause acquisition dropouts; shorter intervals increase power consumption above the headset battery limit. | Test |
| IFC-DRIVESUBSYSTEM-001 | The interface between the Motor Controller Unit and the Left Drive Motor Assembly SHALL consist of three-phase 20kHz PWM gate-drive signals at 48V and a 1024 PPR quadrature encoder feedback channel operating at a minimum sample rate of 10kHz, with an encoder signal propagation delay not exceeding 1ms. 20kHz PWM frequency is above the audible range to prevent tonal noise in clinical environments (IEC 60601-1 noise limits). 1024 PPR provides 0.77mm/pulse wheel displacement resolution, sufficient for the 0.1km/h velocity accuracy requirement. 10kHz encoder sampling (4× oversampling of 1024 PPR at max 2.5 rev/s) ensures Nyquist compliance. 1ms propagation limit fits within the 10ms velocity control cycle. | Test |
| IFC-DRIVESUBSYSTEM-002 | The interface between the Motor Controller Unit and the Right Drive Motor Assembly SHALL consist of three-phase 20kHz PWM gate-drive signals at 48V and a 1024 PPR quadrature encoder feedback channel operating at a minimum sample rate of 10kHz, with an encoder signal propagation delay not exceeding 1ms. Identical to the left motor interface specification — differential drive requires symmetric performance on both channels to achieve straight-line travel. Asymmetric encoder latency would cause directional drift under constant velocity commands. Matched interface specification simplifies integration test and EMC compliance (IEC 60601-1-2). | Test |
| IFC-DRIVESUBSYSTEM-003 | The interface between the Drive Power Stage and the Motor Controller Unit SHALL provide the 48V motor bus voltage to the gate driver circuits, return overcurrent trip status on a dedicated logic signal within 5ms of a trip event, and support a pre-charge sequencing signal from the Motor Controller Unit to enable soft-start of the 48V rail. The pre-charge sequencing prevents inrush current spikes when the Drive Subsystem powers on, protecting the LiFePO4 battery pack and motor MOSFET switches. Overcurrent trip feedback to the MCU in <5ms (matching the hardware trip time) ensures the MCU logs the event and can generate a diagnostic fault code before the watchdog triggers a safe-state. The 48V rail is isolated upstream by the Motor Power Isolation Relay, so the Power Stage–MCU interface is the last active interface before mechanical load. | Test |
| IFC-HMISUBSYSTEM-001 | The interface between the Main Application Processor and the Display Unit SHALL use SPI at 40MHz with a dedicated chip-select line, supporting a minimum frame rate of 30 fps at 800x480 resolution with 16-bit colour depth. 30 fps is sufficient for smooth status updates in a mobility aid context; higher frame rates are unnecessary and would increase EMI. SPI at 40MHz provides 320Mbps raw bandwidth, adequate for 800x480x16bit at 30fps (236Mbps required). | Test |
| IFC-HMISUBSYSTEM-002 | The interface between the Main Application Processor and the Audio Alert Module SHALL use I2C at 400kHz carrying alert-code commands with a command-to-onset latency not exceeding 50ms, where each alert code maps to a distinct tone pattern (frequency, duration, duty cycle) stored in the Audio Alert Module firmware. SYS-REQ-002 requires Emergency Stop actuation within 500ms of trigger detection. The 50ms audio alert onset budget is the human-perceptible notification latency allocated from the total response chain. I2C at 400kHz is sufficient for single-byte command codes; storing tone patterns in the Audio Alert Module firmware decouples HMI response from application processor availability during fault conditions. | Test |
| IFC-HMISUBSYSTEM-003 | The interface between the Main Application Processor and the Status LED Array SHALL use SPI at 10MHz carrying RGB colour and brightness commands with a frame update latency not exceeding 20ms, supporting minimum 6 independently addressable LED elements. LED state must update within one control cycle (100ms) of a mode transition to avoid giving false state information to the care attendant. The 20ms SPI frame latency leaves 80ms for the application processor to detect the mode change and issue the update command. SPI is preferred over PWM for multi-element RGB addressing flexibility. | Test |
| IFC-PERCEPTIONSUBSYSTEM-001 | The interface between the Forward Depth Sensor Array and the Perception MCU SHALL use I2C at 400 kHz (400 kHz I2C mode per UM10204) with three individually addressable sensor nodes, transferring an 8x8 depth grid per sensor at 10Hz with CRC-8 error detection on each transfer. I2C 400 kHz mode provides adequate bandwidth for 3x 64-byte depth grids at 10Hz (total 19.2 kbps, well within the 400 kHz bus capacity). Individual addressing allows the MCU to identify which sensor has failed. CRC-8 detects single-byte errors from EEG-band EMI as required by SYS-REQ-013. | Test |
| IFC-PERCEPTIONSUBSYSTEM-002 | The interface between the Side Proximity Sensor Pair and the Perception MCU SHALL use two dedicated GPIO lines (one per side), active-high TTL at 3.3V logic levels, with each sensor asserting the line within 30ms of detecting an object within 0.5m. GPIO is the lowest-latency interface option for a binary proximity alert and has no protocol overhead that could delay the alert beyond the 30ms window. Using dedicated lines per side allows the MCU to distinguish left and right obstacle sources for directional alert reporting. | Test |
| IFC-PERCEPTIONSUBSYSTEM-003 | The interface between the Perception MCU and the Safety Monitor Processor SHALL use SPI at 1MHz, transferring a 4-byte obstacle alert frame at 10Hz, containing a proximity status bitmask, minimum detected distance, and a rolling 8-bit frame counter, with the Safety Monitor Processor asserting a communication fault if two consecutive frames are missed. SPI is chosen over I2C for the safety interface because it provides deterministic transfer timing with no clock stretching ambiguity. A rolling frame counter allows the Safety Monitor Processor to detect missed frames independently of the communication line state, satisfying IEC 61508 SIL 2 independence requirements. The 4-byte frame is the minimum size to encode proximity status, distance, and counter. | Test |
| IFC-POWERSUBSYSTEM-001 | The interface between the EEG Accessibility Buggy and the Facility Charging Infrastructure SHALL use galvanically isolated IEC 60320 C13/C14 connectors or proprietary docking contacts, accepting 230V 50Hz or 120V 60Hz mains input, with drive functions locked during charging. External interface: galvanic isolation protects the user from mains faults — the non-ambulatory user cannot self-disconnect. Drive lockout during charging prevents movement with a power cable connected. IEC 60601-1 requires double isolation for patient-connected medical devices. | Test |
| IFC-POWERSUBSYSTEM-002 | The interface between the Battery Management System and the Safety Monitor Processor SHALL transmit a thermal fault signal within 50ms of any cell temperature exceeding 55°C, using a dedicated GPIO hardwired fault line with active-low logic, independent of CAN bus. Dedicated GPIO fault line is required because the SIL-3 safety response to thermal runaway risk must not depend on CAN bus availability (which could be disrupted by the same electrical fault event). 55°C threshold is 5°C below the 60°C cutoff to give the Safety Monitor Processor a warning before hard disconnect, enabling graceful deceleration before power cutoff. | Test |
| IFC-POWERSUBSYSTEM-003 | The interface between the Battery Management System and the Main Application Processor SHALL use CAN 2.0B at 250 kbit/s, transmitting pack voltage, individual cell voltages, SoC, temperature summary, and pack current at 100ms intervals. 100ms update rate is adequate for SoC display refresh in HMI and charging state estimation. CAN 2.0B matches the vehicle bus standard. Cell-level voltage data required for compliance with IEC 62133 maintenance documentation and BMS diagnostic functions. SoC data drives the 4-hour runtime monitoring in SYS-REQ-004. | Test |
| IFC-REQ-005 | The interface between the EEG Accessibility Buggy and the Service Diagnostic Laptop SHALL use USB-C wired connection for firmware updates, diagnostic log export, configuration changes, and calibration data, protected by service authentication key with role-based access control. External interface: wired USB-C ensures reliable high-bandwidth data transfer for firmware images (dual-bank flash) and diagnostic logs. Authentication key prevents unauthorised firmware modification — critical for IEC 62304 software change control and preventing malicious firmware injection. | Demonstration |
| IFC-SAFETYSUBSYSTEM-001 | The interface between the EEG Accessibility Buggy and the Facility Emergency/Nurse Call System SHALL transmit iBeacon-compatible BLE advertisements containing device ID and alert type within 500ms of Emergency Stop or seizure detection trigger, receivable by facility BLE gateways at a minimum range of 30m. External interface: the non-ambulatory user cannot call for help. The facility nurse call system is the fastest path to human assistance. 30m range covers typical hospital ward dimensions. iBeacon protocol ensures compatibility with existing facility BLE infrastructure. | Test |
| IFC-SAFETYSUBSYSTEM-002 | The dedicated GPIO watchdog interface between the Main Application Processor (producer) and the Safety Monitor Processor (consumer) SHALL carry a 20ms-period square-wave heartbeat signal only, with no command or data payload on this line. IEC 61508-2 (Functional Safety of E/E/PE Safety-related Systems, Part 2) requires diagnostic test intervals ≤DC-category period for the claimed SIL. A 20ms heartbeat period (50Hz) provides 25 consecutive missed-pulse checks within the 500ms E-stop window specified in VER-REQ-004, improving fault-detection confidence over the previous 100ms period (5 missed pulses). The no-payload constraint preserves SMP independence — shared data channels between control and safety processors are prohibited under IEC 61508-2 clause 7.4.3. Dedicated GPIO eliminates shared-bus arbitration latency. | Test |
| IFC-SAFETYSUBSYSTEM-003 | The interface between the Safety Monitor Processor and the Motor Power Isolation Relay SHALL use dual-channel opto-isolated control lines (one per relay coil), each driven by a dedicated GPIO output; both channels SHALL be required to be asserted simultaneously for relay energisation, such that single-channel failure results in relay de-energisation. Dual-channel opto-isolation prevents ground loops between the safety processor and the high-current relay circuit. The 1oo2 energisation architecture means either a stuck-at-low fault in one channel or a single opto-coupler failure causes safe-state relay opening — avoiding a single-point-of-failure that would allow the relay to remain closed on a fault. | Test |
| IFC-SAFETYSUBSYSTEM-004 | The interface between the Inclinometer Tilt Sensor Unit and the Safety Monitor Processor SHALL be SPI at 1MHz, transferring a 6-byte data frame containing 16-bit pitch angle, 16-bit roll angle, and 16-bit CRC at 100Hz; the Safety Monitor Processor SHALL reject frames with CRC errors and SHALL trigger Emergency Stop if 5 consecutive frames are rejected. SPI is selected over I2C for deterministic transfer latency — I2C clock stretching can violate the 100Hz data rate budget. CRC and consecutive-error E-stop protect against sensor communication faults being silently treated as valid zero-tilt readings, which would mask an actual tip-over condition. | Test |
| IFC-SAFETYSUBSYSTEM-005 | The interface between the Seizure Detection Module and the Safety Monitor Processor SHALL be a shared memory region on the Safety Monitor Processor, updated by the Seizure Detection Module at 50Hz with a 1-byte status word (bit 0 = seizure flag, bit 1 = algorithm health), protected by a mutex; the Safety Monitor Processor SHALL read this region within 10ms of each update. Seizure Detection Module executes as a co-resident software task on the Safety Monitor Processor — inter-task shared memory with mutex is lower latency than inter-processor communication (which would require a serial bus with handshake overhead). 50Hz update rate provides 20ms temporal resolution — adequate since the detection algorithm requires 150ms pattern window, meaning the Safety Monitor Processor will see the flag within one read cycle of it being set. | Test |
| IFC-VEHICLEPLATFORM-001 | The interface between the Electronics Bay and the Chassis Frame SHALL use four M6 stainless steel fasteners with self-locking nuts, providing a pull-out strength of at least 500N per fastener, and shall include a rubber vibration isolator rated for 3g shock attenuation to protect electronic components during kerb crossing. 500N pull-out strength exceeds the 3g shock force applied to the 2kg Electronics Bay mass by a factor of 8, providing adequate margin for ISO 7176-8 compliance. Rubber isolation prevents resonant transmission of kerb-crossing vibration into the processor PCBs which are rated for 2g sinusoidal vibration. | Test |
| IFC-VEHICLEPLATFORM-002 | The interface between the Wheel and Caster Assembly and the Chassis Frame SHALL use a tool-free quick-release mechanism requiring a maximum 15N force for removal and replacement, with a mechanical interlock preventing partial engagement (either fully locked or fully detached). Wheel replacement is a field maintenance task performed by care facility staff without specialist tools (SYS-REQ-015). The 15N force limit is derived from ISO 7176-1 control force limits adapted for maintenance operations — ensuring the task is within capability of care staff regardless of hand strength. The binary interlock prevents wheel detachment due to partial engagement during operation, which would be a safety-critical failure. | Test |
Architecture Decisions (ARC) (7)
| Ref | Requirement | V&V |
|---|---|---|
| ARC-REQ-001 | The BCI Processing Subsystem SHALL implement combined EEG signal acquisition and intent classification on a single embedded processor, sharing the BLE headset interface and neural signal pipeline to achieve end-to-end latency <50ms. Alternative: separate acquisition and classification boards — rejected because the 50ms latency budget leaves insufficient margin for inter-board data transfer and additional hardware increases failure points. Co-location of acquisition and classification on a single processor eliminates a high-bandwidth inter-subsystem link for raw 250Hz 32-channel EEG data. The 50ms end-to-end latency threshold is derived from BCI usability research (mean motor imagery detection lag must be <50ms for natural-feeling control). Separate boards would require ≥10ms DMA transfer overhead, consuming the entire latency margin. | Analysis |
| ARC-REQ-002 | ARC: Safety Subsystem — Independent safety channel with dedicated processor. IEC 61508 (Functional safety of E/E/PE safety-related systems) requires that SIL 3 safety functions be independent of the control path. The Safety Subsystem uses a separate watchdog processor and hardware-level motor power disconnect that operates even if the main application processor fails. Alternative considered: software-only safety monitor on the main processor — rejected because a single processor fault would disable both control and safety, violating SIL 3 independence. IEC 61508 (Functional safety of E/E/PE safety-related systems) clause 7.4.2 requires that SIL 3 safety functions be implemented on hardware independent from the control path. A separate watchdog processor satisfies this independence requirement. Verifiable by inspection of the hardware architecture and IEC 61508 compliance matrix confirming independent power supply, independent clock, and independent activation path for motor power disconnect. | Inspection |
| ARC-REQ-003 | The Perception Subsystem SHALL use dedicated sensor hardware and processing independent of the Drive Subsystem, so that obstacle detection capability is preserved when the Drive Subsystem is in a fault state and Drive Subsystem operation is preserved when the Perception Subsystem fails. Alternative: integrated drive-and-perception controller — rejected because sensor processor lockup would simultaneously disable obstacle detection and emergency braking. Failure independence between perception and drive is required under BS EN ISO 13482 (Safety requirements for personal care robots) clause 5.4 (hazardous failure avoidance). If a single processor controlled both functions, a software fault could disable the obstacle detection while the drive motors remain energised. Separation ensures the Safety Subsystem watchdog can still trigger E-stop via hardware timeout even with Perception failed. | Analysis |
| ARC-REQ-004 | ARC: Communication Subsystem — Separated from HMI to isolate wireless reliability from user feedback. BLE and Wi-Fi radios share antenna resources and protocol stacks but serve different latency requirements (500ms emergency alerts vs. background CMMS telemetry). Grouping all external data links together allows a single security boundary for TLS and GDPR compliance. Alternative considered: distributing BLE to BCI Processing and Wi-Fi to HMI — rejected because scattered radio hardware complicates EMC certification and security auditing. BLE emergency alert latency (500ms SYS-REQ-017) and Wi-Fi CMMS telemetry (background, best-effort) have incompatible QoS requirements. Grouping both under Communication Subsystem allows a unified RF compliance boundary for CE marking and a single TLS/GDPR security review scope. Distributing radios across subsystems would require separate EMC test campaigns per subsystem and complicate GDPR data flow documentation. | Inspection |
| ARC-REQ-005 | The Power Subsystem architecture SHALL implement dual-authority thermal protection: the Battery Management System SHALL signal the Safety Subsystem when cell temperature exceeds 60°C or cell voltage imbalance exceeds 100mV, and the Safety Subsystem SHALL independently command the 48V disconnect relay. Alternative: BMS-only disconnect — rejected because a BMS processor fault would prevent disconnect during thermal runaway (H-003, catastrophic severity). Dual-authority thermal protection is required because H-003 (battery thermal runaway) is classified as catastrophic under BS EN 62133-2 (Safety requirements for portable sealed secondary lithium cells). A single BMS processor failure must not prevent safe battery disconnect. IEC 61508 SIL 3 allocation for H-003 requires that no single-point failure in the safety function is credible — hence the Safety Subsystem holds independent temperature sensing and direct relay control. | Test |
| ARC-REQ-006 | ARC: Drive Subsystem — Differential-drive 48V BLDC architecture with dedicated Motor Controller Unit. Four-component decomposition (Motor Controller Unit, Left/Right Drive Motor Assemblies, Drive Power Stage) chosen over a pre-integrated motor controller module. The dual-channel MCU architecture allows independent velocity closed-loop control on each motor, enabling differential steering without a mechanical differential. The Drive Power Stage is isolated from the 48V bus via the hardware Motor Power Isolation Relay (Safety Subsystem) rather than software-only interlock — this ensures safe-state is reachable even with MCU firmware failure, consistent with SIL 2 (IEC 61508) allocation. SYS-REQ-003 requires speed limiting at 6km/h (Normal) and 2km/h (Restricted), which must be enforced in the Motor Controller Unit firmware. SYS-REQ-002 requires 250ms safe stop — hardware relay isolation ensures this is achievable independent of MCU state. Differential drive was selected over Ackermann steering because the buggy's narrow indoor operating environment requires a turning radius of <800mm, achievable only with zero-radius turns on differential drive. | Inspection |
| ARC-REQ-007 | The Vehicle Platform architecture SHALL implement the Electronics Bay as a separate sealed IP54 enclosure mounted to the Chassis Frame, containing the CAN bus harness within a defined EMC boundary and enabling field serviceability without chassis disassembly. Alternative: electronics integrated into chassis weldment — rejected because weld-bonded enclosures prevent field serviceability and make EMC sealing impractical. A separate IP54 Electronics Bay satisfies IEC 60529 ingress protection and MHRA MDR Annex I Essential Requirements for implant-adjacent electronics. Field serviceability is an operational requirement (Carer Maintenance scenario): technicians must be able to replace individual modules without returning the vehicle to the manufacturer. Integrating electronics into the chassis weldment would require certified welding inspection on every repair — disproportionate to the service risk. | Inspection |
Architecture Diagrams
Classified Entities (80)
| Entity | Hex Code |
|---|---|
| EEG Headset | D6CD5019 |
| Service Diagnostic Laptop | D6AC1008 |
| User Smartphone | 54EC5008 |
| Facility Charging Infrastructure | 54851018 |
| Facility CMMS | 50A47308 |
| Facility Emergency System | 54FD7A58 |
| Bystanders and pedestrians | 06000081 |
| Status LED Array | D6D4F000 |
| Audio Alert Module | D6D47018 |
| Display Unit | D6CC5008 |
| Communication Controller | 41B57B19 |
| Cellular Modem | D4E45018 |
| Bluetooth LE Module | D6F57018 |
| Electronics Bay | D6851008 |
| Wheel and Caster Assembly | DEC51018 |
| Seat and Postural Support System | CE8D3858 |
| Chassis Frame | CE851018 |
| Perception MCU | D1F77008 |
| Side Proximity Sensor Pair | D4C45008 |
| Forward Depth Sensor Array | D5E55008 |
| Drive Power Stage | D4851008 |
| Right Drive Motor Assembly | D6C51008 |
| Left Drive Motor Assembly | D6C51008 |
| Motor Controller Unit | D4F57A18 |
| Charge Controller | D6A51018 |
| DC-DC Converter Array | D6D51018 |
| Battery Management System | 54F77A18 |
| Lithium Iron Phosphate Battery Pack | D6D51018 |
| Command Arbitration Module | 51F57B10 |
| BCI Classifier | 51F77109 |
| Feature Extraction Processor | 50F53308 |
| Artifact Rejection Engine | D6A51018 |
| EEG Acquisition Module | D4E51219 |
| Manual Emergency Stop Button | C68D5858 |
| Seizure Detection Module | 45F77359 |
| Inclinometer Tilt Sensor Unit | D4E55018 |
| Motor Power Isolation Relay | D6B51018 |
| Safety Monitor Processor | D5F37858 |
| Vehicle Platform | CE851058 |
| Communication Subsystem | 51F57319 |
| HMI Subsystem | D4FD7008 |
| Power Subsystem | 56F71218 |
| Safety Subsystem | D7F73058 |
| Perception Subsystem | 55F73209 |
| Drive Subsystem | DEC51018 |
| BCI Processing Subsystem | 71F57319 |
| Communication and Connectivity | 51F57318 |
| User Interface and Alerting | 54FD7A18 |
| Power Management | 50953000 |
| Safety Monitoring and Emergency Response | 55F77A19 |
| Obstacle Detection and Avoidance | 55F77B19 |
| Vehicle Motion Control | 51F77A09 |
| BCI Intent Classification | 41F77309 |
| EEG Signal Acquisition | 74E55218 |
| Hospital electromagnetic environment | 44043850 |
| Care facility management | 00841AF9 |
| Medical device regulatory authority | 000078D9 |
| Clinical prescriber occupational therapist | 00845AF9 |
| Facility maintenance technician | 008412F8 |
| Care attendant | 008D50F9 |
| Mobility-impaired BCI user | 01000221 |
| Weekly maintenance and headset calibration check | 40841208 |
| Seizure during buggy operation emergency | 00000201 |
| User cognitive fatigue degraded operation | 00360201 |
| Signal degradation in crowded environment | 00100200 |
| Daily independent navigation in care facility | 51A80200 |
| Electromagnetic interference disrupting EEG acquisition | 04000001 |
| User medical emergency during operation | 00000201 |
| Vehicle tip-over on slope or kerb | 00000001 |
| EEG command misclassification | 00200001 |
| Battery thermal runaway | 50500211 |
| Collision with obstacle or person | 04000201 |
| Loss of EEG signal during navigation | 00010201 |
| Carer Override mode of EEG Accessibility Buggy | 409C0801 |
| Charging and Maintenance mode of EEG Accessibility Buggy | 50943200 |
| Emergency Stop mode of EEG Accessibility Buggy | 44F57A11 |
| Degraded Assisted mode of EEG Accessibility Buggy | 41F47A01 |
| Normal Navigation mode of EEG Accessibility Buggy | 00B52301 |
| Startup and Calibration mode of EEG Accessibility Buggy | 51FD3200 |
| EEG Accessibility Buggy | DFDD1019 |
Traceability Matrix (262)
| Source | Type | Target | Description |
|---|---|---|---|
| SUB-REQ-055 | derives | REQ-SEEEGACCESSIBILITYBUGGY-015 | SUB-REQ-055 nominal → failure-mode companion |
| SUB-REQ-054 | derives | REQ-SEEEGACCESSIBILITYBUGGY-014 | SUB-REQ-054 nominal → failure-mode companion |
| SUB-REQ-036 | derives | REQ-SEEEGACCESSIBILITYBUGGY-012 | SUB-REQ-036 nominal → failure-mode companion |
| SUB-REQ-035 | derives | REQ-SEEEGACCESSIBILITYBUGGY-011 | SUB-REQ-035 nominal → failure-mode companion |
| SUB-REQ-015 | derives | REQ-SEEEGACCESSIBILITYBUGGY-005 | SUB-REQ-015 nominal → failure-mode companion |
| SUB-REQ-014 | derives | REQ-SEEEGACCESSIBILITYBUGGY-004 | SUB-REQ-014 nominal → failure-mode companion |
| SUB-REQ-016 | derives | REQ-SEEEGACCESSIBILITYBUGGY-006 | SUB-REQ-016 nominal → failure-mode companion |
| SUB-REQ-040 | derives | REQ-SEEEGACCESSIBILITYBUGGY-013 | SUB-REQ-040 nominal → failure-mode companion |
| SUB-REQ-071 | derives | REQ-SEEEGACCESSIBILITYBUGGY-016 | SUB-REQ-071 nominal → failure-mode companion |
| SUB-REQ-023 | derives | REQ-SEEEGACCESSIBILITYBUGGY-007 | SUB-REQ-023 nominal → failure-mode companion |
| SUB-REQ-024 | derives | REQ-SEEEGACCESSIBILITYBUGGY-008 | SUB-REQ-024 nominal → failure-mode companion |
| SUB-REQ-025 | derives | REQ-SEEEGACCESSIBILITYBUGGY-009 | SUB-REQ-025 nominal → failure-mode companion |
| SUB-REQ-027 | derives | REQ-SEEEGACCESSIBILITYBUGGY-010 | SUB-REQ-027 nominal → failure-mode companion |
| SUB-REQ-013 | derives | REQ-SEEEGACCESSIBILITYBUGGY-003 | BMS disconnect timeout → Safety Monitor Processor emergency stop |
| STK-REQ-017 | derives | SYS-REQ-021 | STK-REQ-017 outdoor environmental use → SYS-REQ-021 IP54 enclosure requirement |
| STK-REQ-002 | derives | SYS-REQ-011 | STK-REQ-002 user safety → SYS-REQ-011 tilt/tip-over protection |
| REQ-SEEEGACCESSIBILITYBUGGY-002 | verifies | SYS-REQ-008 | System-level integration test for cognitive fatigue mode transition |
| REQ-SEEEGACCESSIBILITYBUGGY-001 | verifies | SYS-REQ-007 | System-level integration test for SNR degradation mode transition |
| VER-REQ-114 | verifies | IFC-REQ-031 | VER-REQ-114 verifies IFC-REQ-031 wheel quick-release |
| VER-REQ-113 | verifies | IFC-REQ-026 | VER-REQ-113 verifies IFC-REQ-026 MAP to display SPI |
| VER-REQ-112 | verifies | IFC-REQ-025 | VER-REQ-112 verifies IFC-REQ-025 UART to BLE module |
| VER-REQ-111 | verifies | IFC-REQ-024 | VER-REQ-111 verifies IFC-REQ-024 Electronics Bay chassis fasteners |
| VER-REQ-110 | verifies | IFC-REQ-006 | VER-REQ-110 verifies IFC-REQ-006 CMMS REST API interface |
| VER-REQ-109 | verifies | IFC-REQ-004 | VER-REQ-109 verifies IFC-REQ-004 BLE companion app interface |
| VER-REQ-108 | verifies | SUB-REQ-056 | VER-REQ-108 verifies SUB-REQ-056 comm subsystem diagnostic API |
| VER-REQ-107 | verifies | SUB-REQ-037 | VER-REQ-107 verifies SUB-REQ-037 USB-C diagnostic port |
| VER-REQ-106 | verifies | SUB-REQ-029 | VER-REQ-106 verifies SUB-REQ-029 seat and occupant restraint |
| VER-REQ-105 | verifies | SUB-REQ-075 | VER-REQ-105 verifies SUB-REQ-075 Electronics Bay IP54 and thermal |
| VER-REQ-104 | verifies | SUB-REQ-055 | VER-REQ-104 verifies SUB-REQ-055 charging parameters |
| VER-REQ-103 | verifies | SUB-REQ-079 | VER-REQ-103 verifies SUB-REQ-079 command authentication |
| VER-REQ-102 | verifies | IFC-REQ-021 | Verification coverage for IFC-REQ-021 (depth sensor I2C bus, SIL-2) |
| VER-REQ-101 | verifies | SUB-REQ-077 | Verification coverage for SUB-REQ-077 (drive subsystem IEC 60601-1 EMC compliance) |
| VER-REQ-100 | verifies | SUB-REQ-036 | Verification coverage for SUB-REQ-036 (charge controller dual-mains AC input) |
| VER-REQ-099 | verifies | IFC-REQ-022 | Verification coverage for IFC-REQ-022 (lateral proximity sensor GPIO interface) |
| VER-REQ-098 | verifies | IFC-REQ-002 | Verification coverage for IFC-REQ-002 (charging dock galvanic isolation) |
| VER-REQ-097 | verifies | IFC-REQ-005 | Verification coverage for IFC-REQ-005 (USB-C service port operations) |
| VER-REQ-096 | verifies | SUB-REQ-072 | Verification coverage for SUB-REQ-072 (maintenance diagnostic USB-C) |
| VER-REQ-095 | verifies | SUB-REQ-040 | Verification coverage for SUB-REQ-040 (inclinometer SIL-2 power supply tolerance) |
| VER-REQ-094 | verifies | SUB-REQ-074 | Verification coverage for SUB-REQ-074 (chassis material and structural integrity, SIL-2) |
| VER-REQ-093 | verifies | SUB-REQ-053 | Verification coverage for SUB-REQ-053 (carer joystick routing latency) |
| VER-REQ-092 | verifies | SUB-REQ-052 | Verification coverage for SUB-REQ-052 (carer override assertion timing) |
| VER-REQ-091 | verifies | IFC-REQ-013 | Verification coverage for IFC-REQ-013 (SIL-3 feature vector interface) |
| VER-REQ-090 | verifies | IFC-REQ-017 | Verification coverage for IFC-REQ-017 |
| VER-REQ-089 | verifies | IFC-REQ-014 | Verification coverage for IFC-REQ-014 |
| VER-REQ-088 | verifies | IFC-REQ-012 | Verification coverage for IFC-REQ-012 |
| VER-REQ-087 | verifies | IFC-REQ-010 | Verification coverage for IFC-REQ-010 |
| VER-REQ-086 | verifies | SUB-REQ-066 | Verification coverage for SUB-REQ-066 |
| VER-REQ-085 | verifies | SUB-REQ-065 | Verification coverage for SUB-REQ-065 |
| VER-REQ-084 | verifies | SUB-REQ-064 | Verification coverage for SUB-REQ-064 |
| VER-REQ-083 | verifies | SUB-REQ-059 | Verification coverage for SUB-REQ-059 |
| VER-REQ-082 | verifies | SUB-REQ-050 | Verification coverage for SUB-REQ-050 |
| VER-REQ-081 | verifies | SUB-REQ-046 | Verification coverage for SUB-REQ-046 |
| VER-REQ-080 | verifies | SUB-REQ-045 | Verification coverage for SUB-REQ-045 |
| VER-REQ-079 | verifies | SUB-REQ-044 | Verification coverage for SUB-REQ-044 |
| VER-REQ-078 | verifies | SUB-REQ-041 | Verification coverage for SUB-REQ-041 |
| VER-REQ-077 | verifies | SUB-REQ-039 | Verification coverage for SUB-REQ-039 |
| VER-REQ-076 | verifies | SUB-REQ-033 | Verification coverage for SUB-REQ-033 |
| VER-REQ-075 | verifies | SUB-REQ-030 | Verification coverage for SUB-REQ-030 |
| VER-REQ-074 | verifies | SUB-REQ-028 | Verification coverage for SUB-REQ-028 |
| VER-REQ-073 | verifies | SUB-REQ-025 | Verification coverage for SUB-REQ-025 |
| VER-REQ-072 | verifies | SUB-REQ-024 | Verification coverage for SUB-REQ-024 |
| VER-REQ-071 | verifies | SUB-REQ-022 | Verification coverage for SUB-REQ-022 |
| VER-REQ-070 | verifies | SUB-REQ-021 | Verification coverage for SUB-REQ-021 |
| VER-REQ-069 | verifies | SUB-REQ-019 | Verification coverage for SUB-REQ-019 |
| VER-REQ-068 | verifies | SUB-REQ-018 | Verification coverage for SUB-REQ-018 |
| VER-REQ-067 | verifies | SUB-REQ-017 | Verification coverage for SUB-REQ-017 |
| VER-REQ-066 | verifies | SUB-REQ-016 | Verification coverage for SUB-REQ-016 |
| VER-REQ-065 | verifies | SUB-REQ-015 | Verification coverage for SUB-REQ-015 |
| VER-REQ-064 | verifies | SUB-REQ-014 | Verification coverage for SUB-REQ-014 |
| VER-REQ-063 | verifies | SUB-REQ-012 | Verification coverage for SUB-REQ-012 |
| SYS-REQ-019 | derives | SUB-REQ-079 | Command authentication derives from system-level access control requirement |
| VER-REQ-062 | verifies | SUB-REQ-078 | Chassis structural compliance verification |
| SYS-REQ-010 | derives | SUB-REQ-078 | Chassis structural compliance derives from system mass and dimensional constraint |
| SYS-REQ-013 | derives | SUB-REQ-077 | Drive subsystem EMC compliance derives from system-level medical device EMC requirement |
| VER-REQ-061 | verifies | SYS-REQ-023 | System-level MAP failsafe verification |
| SYS-REQ-023 | derives | SUB-REQ-061 | SMP MAP-failure detection derives from SYS redundancy requirement |
| STK-REQ-002 | derives | SYS-REQ-023 | MAP watchdog failover derives from user safety stakeholder requirement |
| VER-REQ-060 | verifies | SUB-REQ-076 | Override mode performance verification |
| SYS-REQ-009 | derives | SUB-REQ-076 | Override mode performance derives from carer handover requirement |
| SYS-REQ-021 | derives | SUB-REQ-075 | SYS-REQ-021 sealed Electronics Bay requirement → Electronics Bay material and environmental requirement |
| SYS-REQ-021 | derives | SUB-REQ-074 | SYS-REQ-021 integrated chassis housing → Chassis Frame material and structural requirement |
| SYS-REQ-007 | derives | SUB-REQ-066 | SYS-REQ-007 BCI SNR degradation threshold → Artifact Rejection Engine CPU/latency resource bounds |
| VER-REQ-059 | verifies | SUB-REQ-073 | Verification of amber LED and display text notification in degraded mode with timing |
| VER-REQ-058 | verifies | SUB-REQ-071 | Verification of CC-CV charging profile and 4-hour completion on both mains standards |
| VER-REQ-057 | verifies | SUB-REQ-070 | Verification of inclinometer dual-threshold detection and brake response timing |
| VER-REQ-056 | verifies | SUB-REQ-069 | Verification of joystick override handover timing and BCI command interlock |
| VER-REQ-055 | verifies | SUB-REQ-068 | Verification of Audio Alert Module sound level and response time on BCI accuracy threshold |
| VER-REQ-054 | verifies | SUB-REQ-067 | Verification of BLE emergency alert transmission timing and content |
| SYS-REQ-022 | derives | SUB-REQ-073 | SYS-REQ-022 amber LED and text display in degraded mode → HMI Status LED Array and Display Unit requirement |
| SYS-REQ-015 | derives | SUB-REQ-072 | SYS-REQ-015 automated diagnostic via USB-C → Vehicle Platform Electronics Bay service port requirement |
| SYS-REQ-014 | derives | SUB-REQ-071 | SYS-REQ-014 facility charging dock 4-hour charge → Power Subsystem Charge Controller requirement |
| SYS-REQ-011 | derives | SUB-REQ-070 | SYS-REQ-011 inclinometer tilt safety → Safety Subsystem Inclinometer Tilt Sensor requirement |
| SYS-REQ-009 | derives | SUB-REQ-069 | SYS-REQ-009 care attendant joystick override → HMI Subsystem handover requirement |
| SYS-REQ-008 | derives | SUB-REQ-068 | SYS-REQ-008 degraded mode care attendant alert → HMI Audio Alert Module requirement |
| SYS-REQ-005 | derives | SUB-REQ-067 | SYS-REQ-005 seizure emergency BLE alert → Communication Subsystem BLE transmission requirement |
| VER-REQ-053 | verifies | SYS-REQ-021 | IEC 60529 IP54 test verifies physical housing protection |
| VER-REQ-052 | verifies | SUB-REQ-063 | SIL-3 certification document review verifies functional safety compliance |
| VER-REQ-051 | verifies | SUB-REQ-061 | MAP watchdog fault injection test verifies SMP failover independence |
| VER-REQ-050 | verifies | SUB-REQ-060 | Per-channel relay drop-out test verifies dual-channel E-stop independence |
| SYS-REQ-022 | derives | SUB-REQ-065 | Drive subsystem 3 km/h degraded speed cap derives from system degraded mode performance requirement |
| STK-REQ-005 | derives | SYS-REQ-022 | Amber LED alert in Degraded mode derives from stakeholder alert requirement |
| STK-REQ-004 | derives | SYS-REQ-022 | Degraded mode 3 km/h speed limit derives from stakeholder care attendant override requirement |
| SYS-REQ-002 | derives | SUB-REQ-064 | MCU hardware overcurrent protection derives from safety trigger emergency stop requirement |
| VER-REQ-049 | verifies | SUB-REQ-062 | Verification of 100ms joystick authority transfer timing |
| SYS-REQ-009 | derives | SUB-REQ-062 | 100ms joystick authority transfer timing derives from care attendant override requirement |
| SYS-REQ-002 | derives | SUB-REQ-061 | MAP failover to Safety Monitor Processor derives from safety trigger emergency stop |
| SYS-REQ-002 | derives | SUB-REQ-060 | Dual-channel E-stop circuit derives from safety trigger emergency stop requirement |
| SYS-REQ-005 | derives | SUB-REQ-038 | Communication controller BLE alert derives from seizure-triggered emergency transmission |
| VER-REQ-048 | verifies | SUB-REQ-054 | Physical tilt test verifying inclinometer publishing rate and content |
| VER-REQ-047 | verifies | SUB-REQ-058 | CAN failure injection test verifying MCU heartbeat monitoring |
| VER-REQ-046 | verifies | SUB-REQ-057 | Watchdog injection test verifying MAP failover chain |
| VER-REQ-045 | verifies | SUB-REQ-051 | Integration test verifying facility E-stop response timing |
| SYS-REQ-010 | derives | ARC-REQ-007 | Vehicle Platform four-component decomposition driven by physical footprint constraint |
| SYS-REQ-003 | derives | ARC-REQ-006 | Differential-drive BLDC architecture driven by speed and control requirements |
| SYS-REQ-012 | derives | ARC-REQ-005 | BMS co-location architecture driven by battery thermal safety requirement |
| SYS-REQ-017 | derives | ARC-REQ-004 | Communication Subsystem separation driven by BLE notification requirement |
| SYS-REQ-006 | derives | ARC-REQ-003 | Perception-Drive separation driven by obstacle detection requirement |
| SYS-REQ-002 | derives | ARC-REQ-002 | Independent safety channel architecture driven by halt requirement |
| SYS-REQ-001 | derives | ARC-REQ-001 | BCI combined processor architecture motivated by classification accuracy |
| SYS-REQ-013 | derives | SUB-REQ-059 | Safety Subsystem SMP must comply with IEC 61508 SIL 3 |
| SYS-REQ-002 | derives | SUB-REQ-058 | Drive Subsystem implements MCU heartbeat monitoring as fault detection |
| SYS-REQ-002 | derives | SUB-REQ-057 | Safety Subsystem implements processor watchdog as a system fault trigger |
| SYS-REQ-015 | derives | SUB-REQ-056 | Communication Subsystem hosts USB-C diagnostic service port |
| SYS-REQ-014 | derives | SUB-REQ-055 | Power Subsystem implements facility charging with thermal and current management |
| SYS-REQ-011 | derives | SUB-REQ-054 | Perception Subsystem implements inclinometer data publishing to Safety Monitor |
| SYS-REQ-009 | derives | SUB-REQ-053 | HMI Subsystem implements joystick command routing during carer override |
| SYS-REQ-009 | derives | SUB-REQ-052 | HMI Subsystem implements hardwired carer override assertion |
| SYS-REQ-005 | derives | SUB-REQ-051 | Safety Subsystem implements facility halt command integration |
| SYS-REQ-002 | derives | SUB-REQ-011 | Safety halt inheritance chain for BCI SNR hard-stop requirement |
| VER-REQ-044 | verifies | IFC-REQ-030 | MAP to LED Array SPI interface verification |
| VER-REQ-043 | verifies | SUB-REQ-048 | Status LED Array visibility verification |
| VER-REQ-042 | verifies | IFC-REQ-011 | EEG Acquisition to Artifact Rejection interface verification |
| VER-REQ-041 | verifies | SUB-REQ-009 | BCI Classifier accuracy verification |
| VER-REQ-040 | verifies | SUB-REQ-008 | Artifact rejection engine verification |
| SYS-REQ-013 | derives | SUB-REQ-050 | Electronics Bay IP54 requirement derives from medical device EMC/environmental compliance |
| SYS-REQ-008 | derives | SUB-REQ-048 | LED visibility requirement derives from care attendant notification requirement |
| SYS-REQ-015 | derives | IFC-REQ-031 | Wheel-chassis mechanical interface derives from diagnostic/maintenance system requirement |
| SYS-REQ-008 | derives | IFC-REQ-030 | LED Array interface derives from care attendant alert requirement |
| SYS-REQ-017 | derives | SUB-REQ-046 | Telemetry rate requirement derives from emergency event notification system requirement |
| SYS-REQ-019 | derives | SUB-REQ-045 | Cellular modem mTLS derives from system TLS 1.3 encryption requirement |
| VER-REQ-039 | verifies | SYS-REQ-020 | ISO 10993-1 biocompatibility documentation inspection |
| VER-REQ-038 | verifies | SUB-REQ-049 | Turning radius doorway navigation verification |
| VER-REQ-037 | verifies | SUB-REQ-047 | Display content and update rate verification |
| VER-REQ-036 | verifies | IFC-REQ-029 | Audio alert onset latency verification |
| VER-REQ-035 | verifies | IFC-REQ-028 | BLE 5.2 connection parameter and latency verification |
| VER-REQ-034 | verifies | IFC-REQ-027 | Verification of CDC-ECM USB interface and LTE latency |
| SYS-REQ-010 | derives | SUB-REQ-049 | Turning radius budget derives from accessibility footprint and doorway navigation requirement |
| SYS-REQ-008 | derives | SUB-REQ-047 | Display must show accuracy so attendant can monitor degradation threshold |
| STK-REQ-002 | derives | SYS-REQ-020 | Biocompatibility requirement derives from user protection stakeholder need |
| SYS-REQ-013 | derives | SUB-REQ-044 | Electrode biocompatibility derived from IEC 60601-1-2 EMC/medical compliance requirement |
| VER-REQ-033 | verifies | SUB-REQ-043 | Physical and electrical independence of Safety Subsystem PCB |
| VER-REQ-032 | verifies | SUB-REQ-038 | End-to-end BLE emergency alert timing verification |
| VER-REQ-031 | verifies | SUB-REQ-042 | Verification of BCI watchdog halt and safe-stop assertion |
| VER-REQ-030 | verifies | SUB-REQ-035 | Verification of tilt hazard signal assertion timing |
| VER-REQ-029 | verifies | SUB-REQ-034 | Verification of joystick authority transfer latency |
| SYS-REQ-004 | derives | IFC-REQ-017 | BMS to MAP CAN interface derived from battery state monitoring for range management |
| SYS-REQ-008 | derives | SUB-REQ-033 | Status LED array mode indication derived from care attendant alert requirement |
| SYS-REQ-004 | derives | SUB-REQ-028 | Electronics bay thermal limit derived from 4-hour continuous operation requirement |
| SYS-REQ-006 | derives | SUB-REQ-025 | Side proximity sensor detection zone derived from lateral obstacle detection requirement |
| SYS-REQ-003 | derives | SUB-REQ-022 | Drive motor torque capacity derived from speed and payload requirement |
| SYS-REQ-007 | derives | SUB-REQ-017 | Artifact engine watchdog interface derived from BCI degraded mode safety requirement |
| SYS-REQ-014 | derives | SUB-REQ-016 | Charge controller timing derived from system charge time requirement |
| SYS-REQ-004 | derives | SUB-REQ-015 | Power rail stability derived from 4-hour continuous operation requirement |
| SYS-REQ-001 | derives | SUB-REQ-012 | Per-user CSP filter loading derived from 85% classification accuracy requirement |
| SYS-REQ-002 | derives | SUB-REQ-043 | Safety Subsystem physical separation derives from SIL-3 independence requirement |
| SYS-REQ-002 | derives | SUB-REQ-042 | BCI watchdog safety constraint derived from 200ms emergency stop requirement |
| SYS-REQ-002 | derives | SUB-REQ-041 | Artifact rejection engine power envelope derived from safety response reliability |
| SYS-REQ-011 | derives | SUB-REQ-040 | Inclinometer power envelope derived from tilt detection reliability requirement |
| SYS-REQ-019 | derives | SUB-REQ-039 | AES-256 encryption and RBAC decomposed to Main Application Processor |
| SYS-REQ-017 | derives | SUB-REQ-038 | BLE emergency alert transmission decomposed to Communication Controller |
| SYS-REQ-015 | derives | SUB-REQ-037 | USB-C service port diagnostic decomposed to Main Application Processor |
| SYS-REQ-014 | derives | SUB-REQ-036 | Charge Controller behaviour decomposed from system charge time req |
| SYS-REQ-011 | derives | SUB-REQ-035 | Tilt detection sensing element behaviour for SYS-REQ-011 |
| SYS-REQ-009 | derives | SUB-REQ-034 | Joystick handover latency decomposed to HMI/Drive interface |
| SYS-REQ-009 | derives | IFC-REQ-026 | Caregiver override/status display drives Display Unit interface |
| SYS-REQ-001 | derives | IFC-REQ-025 | BCI accuracy drives Communication Controller to BLE Module interface |
| SYS-REQ-010 | derives | IFC-REQ-024 | System dimensions requirement drives electronics bay mounting interface |
| SYS-REQ-006 | derives | IFC-REQ-022 | System obstacle detection drives lateral sensor interface spec |
| VER-REQ-028 | verifies | SUB-REQ-032 | Audio alert SPL test verifies E-stop audible alert requirement |
| VER-REQ-027 | verifies | SUB-REQ-031 | Firewall injection test verifies CAN bus isolation |
| SYS-REQ-001 | derives | SUB-REQ-030 | BCI accuracy system req drives BLE throughput requirement |
| VER-REQ-026 | verifies | SUB-REQ-027 | ISO 7176-8 structural test verifies chassis load requirement |
| SYS-REQ-010 | derives | SUB-REQ-029 | System dimension requirement drives seat occupant accommodation range |
| SYS-REQ-010 | derives | SUB-REQ-027 | System dimensions requirement drives chassis load bearing specification |
| VER-REQ-025 | verifies | SUB-REQ-026 | Verification of MCU timeout triggering E-stop sequence |
| VER-REQ-024 | verifies | IFC-REQ-023 | Verification of SPI protocol between Perception MCU and Safety Monitor Processor |
| VER-REQ-023 | verifies | SUB-REQ-023 | Verification of forward sensor detection accuracy and update rate |
| SYS-REQ-006 | derives | IFC-REQ-023 | System obstacle response drives MCU-to-SMP interface timing |
| SYS-REQ-006 | derives | IFC-REQ-021 | System obstacle detection zone drives sensor bus specification |
| SYS-REQ-002 | derives | SUB-REQ-026 | Perception safe state derives from system emergency stop requirement |
| SYS-REQ-006 | derives | SUB-REQ-024 | MCU latency derives from system-level obstacle response time |
| SYS-REQ-006 | derives | SUB-REQ-023 | Forward sensor array specs derive from system obstacle detection zone |
| SYS-REQ-001 | derives | IFC-REQ-014 | Classifier-Command Arbitration interface derives from BCI latency and accuracy |
| SYS-REQ-001 | derives | IFC-REQ-013 | Feature Extraction-Classifier interface derives from BCI accuracy requirement |
| SYS-REQ-001 | derives | IFC-REQ-012 | Artifact Rejection-Feature Extraction interface derives from BCI classification pipeline |
| SYS-REQ-001 | derives | IFC-REQ-011 | EEG Acquisition-Artifact Rejection interface derives from BCI classification performance |
| SYS-REQ-002 | derives | SUB-REQ-021 | Drive Power Stage overcurrent protection derives from system safe-stop requirement |
| VER-REQ-022 | verifies | SUB-REQ-020 | VER-022 verifies MCU 250ms safe-state on CAN loss |
| VER-REQ-021 | verifies | IFC-REQ-020 | VER-021 verifies Drive Power Stage overcurrent trip interface |
| VER-REQ-020 | verifies | IFC-REQ-019 | VER-020 verifies right motor PWM/encoder interface symmetry |
| VER-REQ-019 | verifies | IFC-REQ-018 | VER-019 verifies left motor PWM/encoder interface |
| SYS-REQ-002 | derives | SUB-REQ-020 | MCU CAN loss safe-state derives from system 250ms safe stop |
| SYS-REQ-003 | derives | SUB-REQ-019 | MCU speed clamping directly implements SYS speed limit |
| SYS-REQ-003 | derives | SUB-REQ-018 | MCU velocity control accuracy derives from system speed limit |
| VER-REQ-018 | verifies | IFC-REQ-016 | GPIO fault line test verifies BMS-Safety interface independence |
| VER-REQ-017 | verifies | SUB-REQ-013 | Thermal cutoff hardware test verifies BMS protection response |
| SYS-REQ-004 | derives | SUB-REQ-014 | Battery runtime derives from system 4-hour endurance requirement |
| SYS-REQ-012 | derives | SUB-REQ-013 | BMS thermal cutoff derives from system battery safety requirement |
| VER-REQ-016 | verifies | IFC-REQ-015 | CAN bus analysis verifies Drive Subsystem command interface |
| VER-REQ-015 | verifies | SUB-REQ-010 | Pipeline latency measurement verifies 150ms end-to-end constraint |
| VER-REQ-014 | verifies | SUB-REQ-011 | SNR dropout test verifies signal-loss safe state |
| SYS-REQ-001 | derives | SUB-REQ-008 | Artifact rejection derives from system EEG classification requirement |
| SYS-REQ-007 | derives | SUB-REQ-011 | Signal-loss safe-stop derives from system SNR monitoring requirement |
| SYS-REQ-001 | derives | SUB-REQ-010 | End-to-end latency requirement derives from system response time |
| SYS-REQ-001 | derives | SUB-REQ-009 | BCI classification accuracy floor derives from system command reliability |
| STK-REQ-012 | derives | SYS-REQ-019 | CMMS integration need → data security requirement for CMMS telemetry |
| STK-REQ-010 | derives | SYS-REQ-013 | Regulatory design history file need → EMC/medical device compliance requirement |
| SYS-REQ-019 | derives | IFC-REQ-006 | Data encryption/TLS requirement → CMMS REST API interface |
| SYS-REQ-015 | derives | IFC-REQ-005 | USB-C diagnostic test suite requirement → service diagnostic USB-C interface |
| SYS-REQ-019 | derives | IFC-REQ-004 | Data encryption/RBAC requirement → smartphone companion app BLE interface |
| STK-REQ-002 | derives | SYS-REQ-014 | User safety → charging interface safety requirement |
| SYS-REQ-014 | derives | IFC-REQ-002 | 4-hour charging requirement → galvanically isolated charging interface |
| VER-REQ-013 | verifies | IFC-REQ-009 | SPI protocol capture + CRC injection → inclinometer SPI interface requirement |
| VER-REQ-012 | verifies | IFC-REQ-003 | Emergency BLE alert latency test → emergency/nurse call interface requirement |
| VER-REQ-011 | verifies | IFC-REQ-001 | BLE EEG streaming test → BLE EEG headset interface requirement |
| VER-REQ-010 | verifies | SUB-REQ-007 | Boundary condition watchdog test → Safety Monitor Processor heartbeat requirement |
| VER-REQ-009 | verifies | SUB-REQ-006 | Fault injection test → Safety Subsystem E-stop state machine requirement |
| VER-REQ-008 | verifies | SUB-REQ-005 | Oscilloscope + schematic inspection → manual E-stop hardwire requirement |
| VER-REQ-007 | verifies | SUB-REQ-004 | Tilt table test → Inclinometer tilt sensor unit requirement |
| STK-REQ-015 | derives | SYS-REQ-003 | Audible travel tone/direction indicator need → speed limit system requirement |
| STK-REQ-011 | derives | SYS-REQ-015 | Post-market surveillance data collection need → automated diagnostic test suite |
| STK-REQ-003 | derives | SYS-REQ-007 | Cognitive performance detection need → BCI SNR threshold degradation response |
| STK-REQ-008 | derives | SYS-REQ-018 | Clinical BCI parameter configuration need → startup calibration requirement |
| STK-REQ-017 | derives | SYS-REQ-004 | Outdoor operation environmental need → battery endurance/range requirement |
| STK-REQ-014 | derives | SYS-REQ-003 | Safe stopping distance need → speed limit system requirement |
| STK-REQ-009 | derives | SYS-REQ-019 | Per-session usage data recording need → EEG data encryption and GDPR compliance |
| STK-REQ-007 | derives | SYS-REQ-016 | OTA/wired firmware update need → dual-bank flash firmware update system req |
| STK-REQ-006 | derives | SYS-REQ-015 | Maintenance diagnostic interface need → automated diagnostic test suite |
| STK-REQ-005 | derives | SYS-REQ-017 | Attendant alert stakeholder need → BLE emergency alert system requirement |
| SYS-REQ-005 | derives | IFC-REQ-010 | Seizure detection system req → SDM-SMP shared memory interface |
| SYS-REQ-011 | derives | IFC-REQ-009 | Tilt detection requirement → inclinometer SPI interface spec |
| VER-REQ-006 | verifies | SYS-REQ-002 | End-to-end vehicle stop test verifies SYS E-stop requirement |
| VER-REQ-005 | verifies | IFC-REQ-008 | Single-channel fault test verifies dual-channel relay interface |
| VER-REQ-004 | verifies | IFC-REQ-007 | Heartbeat halt test verifies heartbeat interface spec |
| VER-REQ-003 | verifies | SUB-REQ-003 | CHB-MIT replay verifies seizure detection spec |
| VER-REQ-002 | verifies | SUB-REQ-002 | Load test verifies relay 20ms disconnect |
| VER-REQ-001 | verifies | SUB-REQ-001 | Fault injection test verifies SMP independence |
| SYS-REQ-002 | derives | SUB-REQ-005 | SYS manual override requirement → hardwired E-stop architecture |
| SYS-REQ-011 | derives | SUB-REQ-004 | SYS tilt threshold → Inclinometer sensor specification |
| SYS-REQ-005 | derives | SUB-REQ-003 | SYS seizure detection trigger → Seizure Detection Module spec |
| SYS-REQ-002 | derives | SUB-REQ-002 | SYS E-stop 200ms budget → relay 20ms disconnect |
| SYS-REQ-002 | derives | SUB-REQ-001 | SYS E-stop response requirement → Safety Monitor Processor independence |
| STK-REQ-018 | derives | SYS-REQ-019 | GDPR drives encryption and access control |
| STK-REQ-016 | derives | SYS-REQ-013 | EMI environment drives EMC compliance |
| STK-REQ-002 | derives | SYS-REQ-012 | User safety during battery thermal event |
| STK-REQ-013 | derives | SYS-REQ-010 | Facility compatibility drives vehicle dimensions |
| STK-REQ-004 | derives | SYS-REQ-009 | Carer override requires rapid handover |
| STK-REQ-003 | derives | SYS-REQ-008 | Fatigue detection triggers degraded mode |
| STK-REQ-002 | derives | SYS-REQ-006 | User safety requires collision prevention |
| STK-REQ-002 | derives | SYS-REQ-005 | User safety during seizure events |
| STK-REQ-002 | derives | SYS-REQ-002 | User safety requires rapid emergency stop |
| STK-REQ-001 | derives | SYS-REQ-001 | Independent navigation requires reliable BCI classification |
Orphan Requirements (235)
| Ref | Document | Text |
|---|---|---|
| IFC-BCIPROCESSINGSUBSYSTEM-001 | interface-requirements | The interface between the EEG Accessibility Buggy and the EEG Headset SHALL use Bluetooth Low Energy 5.0 to stream 16-32 channels of 24-bit EEG data at 250 Hz with end-to-end latency not exceeding 50ms from electrode to onboard processor. |
| IFC-BCIPROCESSINGSUBSYSTEM-002 | interface-requirements | The interface between the EEG Acquisition Module and the Artifact Rejection Engine SHALL transfer 32-channel EEG sample arrays at 256 samples/second with a maximum inter-process latency of 5ms and sample loss rate not exceeding 0.1%. |
| IFC-BCIPROCESSINGSUBSYSTEM-003 | interface-requirements | The interface between the Artifact Rejection Engine and the Feature Extraction Processor SHALL transfer cleaned 32-channel EEG epochs in 1-second windows with 50% overlap, formatted as float32 arrays, at a throughput of 2 epochs/second per channel. |
| IFC-BCIPROCESSINGSUBSYSTEM-004 | interface-requirements | The interface between the Feature Extraction Processor and the BCI Classifier SHALL pass feature vectors containing CSP-projected band powers and SSVEP spectral amplitudes as float32 vectors, with timestamp and quality index, within 30ms of epoch receipt. |
| IFC-BCIPROCESSINGSUBSYSTEM-005 | interface-requirements | The interface between the BCI Classifier and the Command Arbitration Module SHALL pass command probability vectors for four navigation classes (forward, left, right, stop) as float32 with per-class confidence values, SNR index, and rolling 2-minute accuracy metric, at minimum 2Hz. |
| IFC-BCIPROCESSINGSUBSYSTEM-006 | interface-requirements | The interface between the Command Arbitration Module and the Drive Subsystem SHALL use a CAN 2.0B message at 500 kbit/s, transmitting validated drive command (4 discrete values) and a 16-bit cyclic status counter, with maximum transmission latency of 5ms. |
| IFC-COMMUNICATIONSUBSYSTEM-001 | interface-requirements | The EEG Accessibility Buggy SHALL communicate with the Companion App via BLE 5.0 LE Secure Connections (AES-CCM-128), providing status updates at ≥1 Hz and emergency notifications with ≤500ms latency. |
| IFC-COMMUNICATIONSUBSYSTEM-002 | interface-requirements | The interface between the EEG Accessibility Buggy and the Facility CMMS SHALL use a REST API over facility Wi-Fi (802.11ac) with TLS 1.3 encryption for automated maintenance log submission, fault reporting, and fleet telemetry, authenticated via API key or OAuth 2.0. |
| IFC-COMMUNICATIONSUBSYSTEM-003 | interface-requirements | The interface between the Communication Controller and the Bluetooth LE Module SHALL use UART at 1Mbps with hardware flow control (RTS/CTS), transferring HCI command and event packets per the Bluetooth HCI specification, with a maximum transfer latency of 2ms per HCI packet. |
| IFC-COMMUNICATIONSUBSYSTEM-004 | interface-requirements | The interface between the Communication Controller and the Cellular Modem SHALL use USB 2.0 (CDC-ECM class) at 480Mbps with AT-command control channel, providing the Communication Controller with Ethernet-over-USB connectivity for LTE data at a maximum round-trip latency of 100ms to the LTE base station. |
| IFC-COMMUNICATIONSUBSYSTEM-005 | interface-requirements | The interface between the Bluetooth LE Module and the EEG headset SHALL use BLE 5.2 with a connection interval of 7.5ms, carrying 8-channel 250Hz EEG sample packets encoded in the EEG Headset Profile (proprietary GATT service) with end-to-end latency from electrode to BCI Acquisition Module not exceeding 20ms. |
| IFC-DRIVESUBSYSTEM-001 | interface-requirements | The interface between the Motor Controller Unit and the Left Drive Motor Assembly SHALL consist of three-phase 20kHz PWM gate-drive signals at 48V and a 1024 PPR quadrature encoder feedback channel operating at a minimum sample rate of 10kHz, with an encoder signal propagation delay not exceeding 1ms. |
| IFC-DRIVESUBSYSTEM-002 | interface-requirements | The interface between the Motor Controller Unit and the Right Drive Motor Assembly SHALL consist of three-phase 20kHz PWM gate-drive signals at 48V and a 1024 PPR quadrature encoder feedback channel operating at a minimum sample rate of 10kHz, with an encoder signal propagation delay not exceeding 1ms. |
| IFC-DRIVESUBSYSTEM-003 | interface-requirements | The interface between the Drive Power Stage and the Motor Controller Unit SHALL provide the 48V motor bus voltage to the gate driver circuits, return overcurrent trip status on a dedicated logic signal within 5ms of a trip event, and support a pre-charge sequencing signal from the Motor Controller Unit to enable soft-start of the 48V rail. |
| IFC-HMISUBSYSTEM-001 | interface-requirements | The interface between the Main Application Processor and the Display Unit SHALL use SPI at 40MHz with a dedicated chip-select line, supporting a minimum frame rate of 30 fps at 800x480 resolution with 16-bit colour depth. |
| IFC-HMISUBSYSTEM-002 | interface-requirements | The interface between the Main Application Processor and the Audio Alert Module SHALL use I2C at 400kHz carrying alert-code commands with a command-to-onset latency not exceeding 50ms, where each alert code maps to a distinct tone pattern (frequency, duration, duty cycle) stored in the Audio Alert Module firmware. |
| IFC-HMISUBSYSTEM-003 | interface-requirements | The interface between the Main Application Processor and the Status LED Array SHALL use SPI at 10MHz carrying RGB colour and brightness commands with a frame update latency not exceeding 20ms, supporting minimum 6 independently addressable LED elements. |
| IFC-PERCEPTIONSUBSYSTEM-001 | interface-requirements | The interface between the Forward Depth Sensor Array and the Perception MCU SHALL use I2C at 400 kHz (400 kHz I2C mode per UM10204) with three individually addressable sensor nodes, transferring an 8x8 depth grid per sensor at 10Hz with CRC-8 error detection on each transfer. |
| IFC-PERCEPTIONSUBSYSTEM-002 | interface-requirements | The interface between the Side Proximity Sensor Pair and the Perception MCU SHALL use two dedicated GPIO lines (one per side), active-high TTL at 3.3V logic levels, with each sensor asserting the line within 30ms of detecting an object within 0.5m. |
| IFC-PERCEPTIONSUBSYSTEM-003 | interface-requirements | The interface between the Perception MCU and the Safety Monitor Processor SHALL use SPI at 1MHz, transferring a 4-byte obstacle alert frame at 10Hz, containing a proximity status bitmask, minimum detected distance, and a rolling 8-bit frame counter, with the Safety Monitor Processor asserting a communication fault if two consecutive frames are missed. |
| IFC-POWERSUBSYSTEM-001 | interface-requirements | The interface between the EEG Accessibility Buggy and the Facility Charging Infrastructure SHALL use galvanically isolated IEC 60320 C13/C14 connectors or proprietary docking contacts, accepting 230V 50Hz or 120V 60Hz mains input, with drive functions locked during charging. |
| IFC-POWERSUBSYSTEM-002 | interface-requirements | The interface between the Battery Management System and the Safety Monitor Processor SHALL transmit a thermal fault signal within 50ms of any cell temperature exceeding 55°C, using a dedicated GPIO hardwired fault line with active-low logic, independent of CAN bus. |
| IFC-POWERSUBSYSTEM-003 | interface-requirements | The interface between the Battery Management System and the Main Application Processor SHALL use CAN 2.0B at 250 kbit/s, transmitting pack voltage, individual cell voltages, SoC, temperature summary, and pack current at 100ms intervals. |
| IFC-SAFETYSUBSYSTEM-001 | interface-requirements | The interface between the EEG Accessibility Buggy and the Facility Emergency/Nurse Call System SHALL transmit iBeacon-compatible BLE advertisements containing device ID and alert type within 500ms of Emergency Stop or seizure detection trigger, receivable by facility BLE gateways at a minimum range of 30m. |
| IFC-SAFETYSUBSYSTEM-002 | interface-requirements | The dedicated GPIO watchdog interface between the Main Application Processor (producer) and the Safety Monitor Processor (consumer) SHALL carry a 20ms-period square-wave heartbeat signal only, with no command or data payload on this line. |
| IFC-SAFETYSUBSYSTEM-003 | interface-requirements | The interface between the Safety Monitor Processor and the Motor Power Isolation Relay SHALL use dual-channel opto-isolated control lines (one per relay coil), each driven by a dedicated GPIO output; both channels SHALL be required to be asserted simultaneously for relay energisation, such that single-channel failure results in relay de-energisation. |
| IFC-SAFETYSUBSYSTEM-004 | interface-requirements | The interface between the Inclinometer Tilt Sensor Unit and the Safety Monitor Processor SHALL be SPI at 1MHz, transferring a 6-byte data frame containing 16-bit pitch angle, 16-bit roll angle, and 16-bit CRC at 100Hz; the Safety Monitor Processor SHALL reject frames with CRC errors and SHALL trigger Emergency Stop if 5 consecutive frames are rejected. |
| IFC-SAFETYSUBSYSTEM-005 | interface-requirements | The interface between the Seizure Detection Module and the Safety Monitor Processor SHALL be a shared memory region on the Safety Monitor Processor, updated by the Seizure Detection Module at 50Hz with a 1-byte status word (bit 0 = seizure flag, bit 1 = algorithm health), protected by a mutex; the Safety Monitor Processor SHALL read this region within 10ms of each update. |
| IFC-VEHICLEPLATFORM-001 | interface-requirements | The interface between the Electronics Bay and the Chassis Frame SHALL use four M6 stainless steel fasteners with self-locking nuts, providing a pull-out strength of at least 500N per fastener, and shall include a rubber vibration isolator rated for 3g shock attenuation to protect electronic components during kerb crossing. |
| IFC-VEHICLEPLATFORM-002 | interface-requirements | The interface between the Wheel and Caster Assembly and the Chassis Frame SHALL use a tool-free quick-release mechanism requiring a maximum 15N force for removal and replacement, with a mechanical interlock preventing partial engagement (either fully locked or fully detached). |
| SUB-BCIPROCESSINGSUBSYSTEM-001 | subsystem-requirements | The Artifact Rejection Engine SHALL reject electromagnetic and muscle artefact from 32-channel EEG within 20ms of epoch receipt, with false rejection of true neural signals not exceeding 10%. |
| SUB-BCIPROCESSINGSUBSYSTEM-002 | subsystem-requirements | The BCI Classifier SHALL achieve a minimum four-class motor imagery and SSVEP classification accuracy of 75% across a 2-minute rolling window during normal operation. |
| SUB-BCIPROCESSINGSUBSYSTEM-003 | subsystem-requirements | The Command Arbitration Module SHALL emit a validated drive command to the Drive Subsystem interface within 150ms of the corresponding EEG signal epoch being acquired by the EEG Acquisition Module. |
| SUB-BCIPROCESSINGSUBSYSTEM-004 | subsystem-requirements | When BCI signal-to-noise ratio remains below the classification threshold for more than 3 consecutive seconds, the Command Arbitration Module SHALL emit a STOP command to the Drive Subsystem and suppress further drive commands until SNR recovers. |
| SUB-BCIPROCESSINGSUBSYSTEM-005 | subsystem-requirements | The Feature Extraction Processor SHALL load and apply per-user CSP spatial filter matrices from encrypted calibration storage within 5 seconds of user session initialisation. |
| SUB-BCIPROCESSINGSUBSYSTEM-006 | subsystem-requirements | The Artifact Rejection Engine SHALL expose a watchdog interface to the BCI Processing Subsystem supervisor; when no valid epoch output is received for more than 500ms, the supervisor SHALL reset the Artifact Rejection Engine and log the event for post-session analysis. |
| SUB-BCIPROCESSINGSUBSYSTEM-007 | subsystem-requirements | The Main Application Processor SHALL expose a USB-C service port accessible on the Electronics Bay panel that provides a diagnostic test suite interface, executing the full motor response, brake torque, sensor calibration, battery cell health, and BCI pipeline integrity test sequence within 20 minutes via authenticated USB connection. |
| SUB-BCIPROCESSINGSUBSYSTEM-008 | subsystem-requirements | The Main Application Processor SHALL encrypt all EEG biometric data using AES-256 at rest and TLS 1.3 in transit, enforce role-based access control with at least three roles (clinical, maintenance, user), and maintain an append-only audit log of all data access events with timestamp, user identity, and operation type. |
| SUB-BCIPROCESSINGSUBSYSTEM-009 | subsystem-requirements | The Artifact Rejection Engine SHALL operate from the 3.3V logic rail supplied by the DC-DC Converter Array, with a maximum peak current draw of 250mA during active signal processing, and SHALL maintain operation without error for supply voltage variation between 3.0V and 3.6V. |
| SUB-BCIPROCESSINGSUBSYSTEM-010 | subsystem-requirements | While in Normal Navigation mode, the BCI Processing Subsystem SHALL provide a software watchdog that monitors BCI command output validity and SHALL halt command generation and assert a safe-stop signal within 100ms if command outputs deviate from expected bounds or if the watchdog is not kicked within a 200ms window. |
| SUB-BCIPROCESSINGSUBSYSTEM-011 | subsystem-requirements | The EEG Accessibility Buggy electrode interface components that contact the user scalp SHALL be manufactured from materials meeting ISO 10993-1 (Biological evaluation of medical devices — Part 1: Evaluation and testing within a risk management process) biocompatibility requirements for skin-contacting medical devices, and SHALL support decontamination with standard clinical disinfectants between users without degradation of electrical performance. |
| SUB-BCIPROCESSINGSUBSYSTEM-012 | subsystem-requirements | The Artifact Rejection Engine SHALL execute as a software module on the Feature Extraction Processor hardware, occupying no more than 30% of available CPU cycles during continuous EEG processing at 250 SPS per channel, with a deterministic maximum latency of 4ms per processing frame. |
| SUB-BCIPROCESSINGSUBSYSTEM-013 | subsystem-requirements | The Main Application Processor SHALL validate all BCI-derived navigation commands using a cryptographic message authentication code (HMAC-SHA256) when received from any external software interface, and SHALL reject and log any command that fails authentication, missing a valid session token, or arrives via an interface not in the authorised interface table defined during commissioning. |
| SUB-COMMUNICATIONSUBSYSTEM-001 | subsystem-requirements | The Bluetooth LE Module SHALL maintain a stable BLE 5.2 connection to the paired EEG headset at 2.4GHz with a connection interval of 7.5ms, sustaining 32-channel EEG data at 8kHz sample rate (effective throughput 512kbps) within an operating range of 3m with no physical obstructions. |
| SUB-COMMUNICATIONSUBSYSTEM-002 | subsystem-requirements | The Communication Controller SHALL enforce a firewall rule that prevents all data traffic originating from the Cellular Modem from reaching the internal CAN bus or I2C/SPI control networks. |
| SUB-COMMUNICATIONSUBSYSTEM-003 | subsystem-requirements | When Emergency Stop or seizure detection triggers, the Communication Controller SHALL transmit a BLE 5.0 iBeacon-compatible alert to the facility BLE gateway within 500ms, including device ID, alert type, and GPS coordinates, and simultaneously notify the paired caregiver smartphone. |
| SUB-COMMUNICATIONSUBSYSTEM-004 | subsystem-requirements | The Cellular Modem SHALL authenticate to the remote telemetry server using mutual TLS 1.3 with a device-unique X.509 certificate provisioned at manufacture, rejecting any server certificate not signed by the system's root CA. |
| SUB-COMMUNICATIONSUBSYSTEM-005 | subsystem-requirements | The Cellular Modem SHALL transmit session telemetry (location, BCI state, battery, error events) to the remote server at a minimum interval of 10 seconds with a maximum uplink latency of 2 seconds under nominal 4G coverage. |
| SUB-COMMUNICATIONSUBSYSTEM-006 | subsystem-requirements | The Communication Subsystem SHALL provide a USB-C service port that exposes a diagnostic API enabling technicians to execute motor response verification tests and receive pass/fail results with logged timestamps within 10 s of command initiation. |
| SUB-COMMUNICATIONSUBSYSTEM-007 | subsystem-requirements | When a Seizure Emergency Stop event is triggered, the Communication Controller SHALL transmit a BLE 5.0 emergency alert packet containing device ID, alert type code, GPS coordinates (WGS-84 decimal), and UTC timestamp to the facility emergency system receiver within 500ms of the Emergency Stop command. |
| SUB-DRIVESUBSYSTEM-001 | subsystem-requirements | The Motor Controller Unit SHALL implement closed-loop velocity control for each drive motor channel, updating the velocity setpoint at 100 Hz using 1024 PPR quadrature encoder feedback, with a steady-state velocity error not exceeding ±0.1 km/h at any commanded speed. |
| SUB-DRIVESUBSYSTEM-002 | subsystem-requirements | The Motor Controller Unit SHALL enforce a vehicle speed limit of 6 km/h in Normal Navigation mode and 2 km/h in Restricted mode, clamping any velocity command exceeding these thresholds before the command is applied to the motor drive stages. |
| SUB-DRIVESUBSYSTEM-003 | subsystem-requirements | When the Motor Controller Unit receives a kill signal via the CAN safety frame or detects loss of CAN heartbeat for more than 100ms, the Motor Controller Unit SHALL apply regenerative braking to bring both motors to zero velocity within 250ms and hold zero-velocity command until a valid restart sequence is received. |
| SUB-DRIVESUBSYSTEM-004 | subsystem-requirements | The Drive Power Stage SHALL trip the hardware overcurrent protection circuit and isolate the motor phase outputs within 5ms when per-channel motor current exceeds 30A, independent of Motor Controller Unit firmware. |
| SUB-DRIVESUBSYSTEM-005 | subsystem-requirements | The Left Drive Motor Assembly and the Right Drive Motor Assembly SHALL each provide a minimum continuous shaft output of 250W at 48V DC supply voltage across the operating temperature range of 0°C to 40°C, with the driven wheel maintaining traction on level indoor surfaces up to a 5% gradient. |
| SUB-DRIVESUBSYSTEM-006 | subsystem-requirements | When the Drive Subsystem detects Motor Controller Unit CAN heartbeat absence exceeding 100 ms, the Drive Subsystem SHALL command both motor drivers to coast-to-stop state and assert MCU_FAULT to the Safety Monitor Processor within 50 ms of timeout detection. |
| SUB-DRIVESUBSYSTEM-007 | subsystem-requirements | The Motor Controller Unit SHALL implement hardware overcurrent protection independent of the Main Application Processor that disconnects motor phase outputs within 5ms if phase current exceeds 120% of rated maximum, with no firmware execution required for this protection to operate. |
| SUB-DRIVESUBSYSTEM-008 | subsystem-requirements | While in Degraded/Assisted mode, the Drive Subsystem SHALL enforce a maximum speed cap of 3 km/h by limiting PWM duty cycle to 50% of the Normal Navigation maximum, with the speed cap applied in firmware prior to the Motor Controller Unit command, independent of any BCI or joystick input value. |
| SUB-DRIVESUBSYSTEM-009 | subsystem-requirements | While operating in Care Attendant Override mode, the Drive Subsystem SHALL respond to joystick steering and throttle inputs within 100ms, maintain obstacle detection response within 200ms, limit maximum speed to 6 km/h, and sustain override operation for the full battery duration specified by SUB-REQ-014 without consuming more than 15% additional power versus Normal Navigation mode at equivalent speed. |
| SUB-DRIVESUBSYSTEM-010 | subsystem-requirements | The Drive Subsystem, including the Motor Controller Unit and Motor Power Isolation Relay, SHALL comply with IEC 60601-1 (Medical electrical equipment — General requirements for basic safety and essential performance) for protection against electrical hazards, and all motor drive electronics SHALL meet the EMC requirements of IEC 60601-1-2 (Electromagnetic compatibility — Requirements and tests for medical electrical equipment). |
| SUB-HMISUBSYSTEM-001 | subsystem-requirements | The Audio Alert Module SHALL produce an audible tone of minimum 80dB SPL at 1m when an emergency stop is activated, within 100ms of the E-stop signal being asserted, and SHALL sustain this tone until the system transitions out of the E-stop state. |
| SUB-HMISUBSYSTEM-002 | subsystem-requirements | The Status LED Array SHALL display a distinct colour state for each of: Normal Navigation (green), Degraded/Reduced Mode (amber), E-stop Active (red), Charging (blue), and BCI Calibration (pulsing white), with state transitions completing within 200ms of the triggering event. |
| SUB-HMISUBSYSTEM-003 | subsystem-requirements | When the care attendant activates the override switch, the HMI Subsystem SHALL transfer joystick command authority to the Drive Subsystem within 100ms, suppressing all BCI command outputs for the duration of override mode. |
| SUB-HMISUBSYSTEM-004 | subsystem-requirements | The Display Unit SHALL render BCI classification accuracy, vehicle speed, battery state of charge, and active operating mode on a sunlight-readable screen with minimum 300 cd/m2 brightness, updating at minimum 2Hz in Normal Navigation mode. |
| SUB-HMISUBSYSTEM-005 | subsystem-requirements | The Status LED Array SHALL be visible from any angle within a 120-degree horizontal arc to the rear of the vehicle, with a minimum luminous intensity of 10 mcd per LED element, to allow care attendants approaching from behind to read vehicle state. |
| SUB-HMISUBSYSTEM-006 | subsystem-requirements | When the care attendant activates the rear-mounted override switch, the HMI Subsystem SHALL assert a hardwired CARER_OVERRIDE signal to the Safety Monitor Processor within 50 ms and maintain the signal for the duration of physical switch engagement. |
| SUB-HMISUBSYSTEM-007 | subsystem-requirements | When CARER_OVERRIDE is asserted, the HMI Subsystem SHALL route joystick control commands directly to the Drive Subsystem motor controller at a 50 Hz command rate with latency not exceeding 20 ms from joystick input to CAN frame transmission. |
| SUB-HMISUBSYSTEM-008 | subsystem-requirements | When the care attendant activates the rear-mounted override switch, the HMI Subsystem SHALL complete authority transfer from BCI commands to joystick steering and throttle within 100ms of switch actuation, measured from the falling edge of the CARER_OVERRIDE signal to the first joystick command accepted by the Drive Subsystem. |
| SUB-HMISUBSYSTEM-009 | subsystem-requirements | When the rolling 2-minute BCI classification accuracy drops below 70%, the Audio Alert Module SHALL emit a 85 dBSPL (at 1m) pulsed tone at 880Hz within 200ms of the accuracy threshold crossing, sustained until the mode transitions or care attendant acknowledges via the HMI. |
| SUB-HMISUBSYSTEM-010 | subsystem-requirements | When the rear-mounted override switch is activated, the HMI Subsystem SHALL transfer steering and throttle authority to the rear joystick, disable BCI movement command processing, and confirm handover to the Drive Subsystem within 100ms of the override switch activation signal. |
| SUB-HMISUBSYSTEM-011 | subsystem-requirements | While the system is in Degraded/Assisted mode, the Status LED Array SHALL display a continuous amber pattern at 2Hz pulse rate and the Display Unit SHALL present a persistent text notification reading 'DEGRADED MODE — BCI ACCURACY LOW — SPEED LIMITED TO 3 KM/H' on the primary status screen within 100ms of mode entry, remaining visible until mode change. |
| SUB-PERCEPTIONSUBSYSTEM-001 | subsystem-requirements | The Forward Depth Sensor Array SHALL measure distances in the forward 120-degree arc with a range of 0.05m to 2.0m and an accuracy of plus or minus 50mm at no less than 10Hz, under all operating lighting conditions from 0 lux to 10,000 lux. |
| SUB-PERCEPTIONSUBSYSTEM-002 | subsystem-requirements | The Perception MCU SHALL process all sensor inputs and emit an obstacle alert frame to the Safety Monitor Processor within 50ms of sensor data arrival, sustaining this throughput at full 10Hz sensor update rate. |
| SUB-PERCEPTIONSUBSYSTEM-003 | subsystem-requirements | The Side Proximity Sensor Pair SHALL detect objects within 0.5m laterally on each side of the vehicle and deliver a TTL-level alert signal to the Perception MCU within 30ms of intrusion. |
| SUB-PERCEPTIONSUBSYSTEM-004 | subsystem-requirements | When the Perception MCU fails to produce an obstacle alert frame within 150ms of its scheduled transmission window, the Safety Monitor Processor SHALL treat the timeout as an obstacle-present condition and initiate the emergency stop sequence. |
| SUB-PERCEPTIONSUBSYSTEM-005 | subsystem-requirements | While vehicle tilt measured by the Inclinometer Tilt Sensor Unit exceeds 15 degrees on any axis, the Perception Subsystem SHALL assert a tilt-hazard signal to the Safety Monitor Processor within 50ms of threshold crossing. |
| SUB-PERCEPTIONSUBSYSTEM-006 | subsystem-requirements | The Inclinometer Tilt Sensor Unit SHALL operate from a regulated 3.3V supply derived from the DC-DC Converter Array, with a maximum continuous current draw of 10mA, and SHALL maintain measurement accuracy within specification for supply voltage variation of 3.0V to 3.6V. |
| SUB-PERCEPTIONSUBSYSTEM-007 | subsystem-requirements | While vehicle tilt measured by the onboard inclinometer exceeds 15 degrees in any axis, the Perception Subsystem SHALL continuously publish tilt angle, axis identity, and confidence score to the Safety Monitor Processor at no less than 20 Hz. |
| SUB-PERCEPTIONSUBSYSTEM-008 | subsystem-requirements | When one or more elements of the Forward Depth Sensor Array fail to deliver a valid distance frame within 200ms, the Perception MCU SHALL reduce commanded maximum vehicle speed to 1.5 km/h, assert a sensor-fault alert to the Safety Monitor Processor, and maintain this reduced-speed safe state until all sensor elements are confirmed operational. |
| SUB-PERCEPTIONSUBSYSTEM-009 | subsystem-requirements | When the Perception MCU fails to emit an obstacle-alert frame to the Safety Monitor Processor for more than 150ms, the Safety Monitor Processor SHALL assert a perception-fault condition: engage emergency braking, disable all drive motor commands, and inhibit restart until the Perception MCU heartbeat is confirmed operational. |
| SUB-PERCEPTIONSUBSYSTEM-010 | subsystem-requirements | When either Side Proximity Sensor element fails to respond to its health-check poll within 200ms, the Perception MCU SHALL assert a side-sensor-fault flag to the Safety Monitor Processor and restrict maximum vehicle speed to 0.5 km/h until the fault is cleared by an authorised operator or maintenance reset. |
| SUB-PERCEPTIONSUBSYSTEM-011 | subsystem-requirements | When the Inclinometer Tilt Sensor Unit fails to deliver a valid tilt measurement to the Perception MCU within 200ms (sensor timeout or invalid checksum on three consecutive frames), the Safety Monitor Processor SHALL treat the failure as a tilt-threshold-exceeded condition and command emergency stop, maintaining halt until the inclinometer is confirmed operational. |
| SUB-PERCEPTIONSUBSYSTEM-012 | subsystem-requirements | When the Perception Subsystem fails to publish valid tilt data to the Safety Monitor Processor for more than 100ms during active navigation, the Safety Monitor Processor SHALL treat the publication silence as a tilt-threshold-exceeded condition and command emergency stop, maintaining halt until tilt data publication is confirmed restored. |
| SUB-POWERSUBSYSTEM-001 | subsystem-requirements | The Battery Management System SHALL disconnect the battery pack from the 48V bus within 200ms when any cell temperature exceeds 60°C or any cell voltage exceeds 3.65V. |
| SUB-POWERSUBSYSTEM-002 | subsystem-requirements | The Lithium Iron Phosphate Battery Pack SHALL deliver a minimum of 4 hours continuous operation at rated system load (drive motors, BCI processing, HMI, safety systems combined) before state of charge falls below 10%. |
| SUB-POWERSUBSYSTEM-003 | subsystem-requirements | The DC-DC Converter Array SHALL maintain each output rail (12V, 5V, 3.3V) within ±5% of nominal voltage under all load conditions from 10% to 100% rated current, with output ripple not exceeding 50mV peak-to-peak. |
| SUB-POWERSUBSYSTEM-004 | subsystem-requirements | The Charge Controller SHALL charge the battery pack from 20% to 100% state of charge within 3 hours when connected to a 240V AC facility supply. |
| SUB-POWERSUBSYSTEM-005 | subsystem-requirements | The Charge Controller SHALL accept charging input from a facility charging dock providing 230V 50Hz or 120V 60Hz AC mains, and SHALL complete pack charge from 20% to 100% state of charge within 4 hours at each nominal supply voltage. |
| SUB-POWERSUBSYSTEM-006 | subsystem-requirements | When connected to a facility charging dock providing 230V 50Hz AC supply, the Power Subsystem onboard charger SHALL limit inrush current to less than 16A peak, regulate charging current to maintain cell temperature below 45°C, and complete charge from 20% to 100% SoC within 4 hours. |
| SUB-POWERSUBSYSTEM-007 | subsystem-requirements | The Charge Controller SHALL accept 230V 50Hz or 120V 60Hz mains input via the facility charging dock connector and charge the Lithium Iron Phosphate Battery Pack from 20% to 100% State of Charge within 4 hours using CC-CV charging profile, with automatic termination and trickle maintenance. |
| SUB-POWERSUBSYSTEM-008 | subsystem-requirements | When the Battery Management System fails to disconnect the battery pack from the 48V bus within 250ms of an overvoltage or overtemperature detection, the Safety Monitor Processor SHALL detect the BMS watchdog timeout and assert system-wide emergency stop within 50ms. |
| SUB-POWERSUBSYSTEM-009 | subsystem-requirements | When the Lithium Iron Phosphate Battery Pack state of charge reaches 10%, the Power Subsystem SHALL activate a safe-stop sequence: halt all drive motor commands within 5 seconds, engage electromechanical parking brakes, sustain Safety Monitor Processor and emergency braking power for a minimum of 5 minutes, and assert a low-battery HMI alert. |
| SUB-POWERSUBSYSTEM-010 | subsystem-requirements | When any DC-DC Converter Array output rail deviates more than 10% from nominal voltage for more than 100ms, the Safety Monitor Processor SHALL assert a power-fault condition, command emergency braking, disable all drive motor control signals, and maintain power-fault safe state until the rail recovers to within 5% of nominal and an authorised operator clears the fault. |
| SUB-POWERSUBSYSTEM-011 | subsystem-requirements | When the Charge Controller detects a mains supply fault (supply voltage outside 207V-253V AC, frequency outside 47Hz-53Hz, or ground fault current exceeding 10mA RMS), it SHALL disconnect from the facility mains supply within 200ms, lock the charge port relay, and assert a charge-fault alert on the HMI display. |
| SUB-POWERSUBSYSTEM-012 | subsystem-requirements | When the Charge Controller detects mains supply voltage outside 207V-253V AC at 50Hz or 102V-132V AC at 60Hz at the facility dock connector, it SHALL reject the connection, maintain galvanic isolation from the supply, and display a supply-incompatible warning on the HMI. |
| SUB-POWERSUBSYSTEM-013 | subsystem-requirements | When the 3.3V supply to the Inclinometer Tilt Sensor Unit deviates outside the 3.0V-3.6V operating range for more than 50ms, the DC-DC Converter Array health monitor SHALL assert a sensor-power fault to the Safety Monitor Processor, causing immediate vehicle halt and inhibiting motion until the 3.3V rail returns to within specification. |
| SUB-POWERSUBSYSTEM-014 | subsystem-requirements | When inrush current to the Power Subsystem charger exceeds 16A peak or cell temperature during charging exceeds 45°C for more than 10 seconds, the Charge Controller SHALL interrupt the charge cycle within 100ms, isolate from the facility mains supply, and assert a charge-fault alert that persists until acknowledged by an authorised operator. |
| SUB-POWERSUBSYSTEM-015 | subsystem-requirements | When the Charge Controller fails to reach 100% state of charge within 5 hours of charge initiation, it SHALL terminate the charge cycle, log a battery-health fault event with timestamp to the CMMS interface, and alert the facility operator via the HMI display. |
| SUB-SAFETYSUBSYSTEM-001 | subsystem-requirements | The Safety Monitor Processor SHALL operate on a processor with no shared memory, clock domain, or power rail with the main application processor, and SHALL maintain its safety state machine execution at 200Hz even when the main application processor is in fault state. |
| SUB-SAFETYSUBSYSTEM-002 | subsystem-requirements | The Motor Power Isolation Relay SHALL disconnect the 48V motor drive power rail within 20ms of receiving the de-energise command from the Safety Monitor Processor, under all load conditions from 0A to 200A. |
| SUB-SAFETYSUBSYSTEM-003 | subsystem-requirements | The Seizure Detection Module SHALL detect generalised spike-and-wave EEG activity exceeding 3 Hz amplitude and >30µV peak-to-peak across all acquisition channels and output a seizure flag to the Safety Monitor Processor within 150ms of seizure onset, with a false positive rate not exceeding 1 per 8 hours of operation. |
| SUB-SAFETYSUBSYSTEM-004 | subsystem-requirements | The Inclinometer Tilt Sensor Unit SHALL measure vehicle pitch and roll continuously at 100Hz with accuracy of ±0.5° and SHALL trigger an E-stop command via the Safety Monitor Processor when tilt in any axis exceeds 15 degrees for more than 200ms. |
| SUB-SAFETYSUBSYSTEM-005 | subsystem-requirements | The Manual Emergency Stop Button SHALL be hardwired directly to the Motor Power Isolation Relay coil circuit in series, such that button actuation disconnects motor power without software mediation, within 5ms of button contact closure. |
| SUB-SAFETYSUBSYSTEM-006 | subsystem-requirements | When any safety trigger is received by the Safety Monitor Processor — including BCI signal loss notification, seizure flag, tilt threshold exceeded, manual E-stop, or main processor heartbeat failure — the Safety Subsystem SHALL transition to and maintain Emergency Stop state within 200ms, including relay de-energisation, brake command, and HMI alert outputs. |
| SUB-SAFETYSUBSYSTEM-007 | subsystem-requirements | The Safety Monitor Processor SHALL monitor a heartbeat signal from the main application processor, and SHALL trigger Emergency Stop if the heartbeat is absent for more than 500ms or if the heartbeat period deviates by more than 20% from the nominal 100ms period. |
| SUB-SAFETYSUBSYSTEM-008 | subsystem-requirements | The Safety Subsystem SHALL be implemented as a physically separate electronics module from the Main Application Processor, housed within the Electronics Bay on an independent PCB with independent power input, to ensure that a hardware fault in the main processing chain cannot corrupt safety function execution. |
| SUB-SAFETYSUBSYSTEM-009 | subsystem-requirements | When the facility emergency system transmits a halt command via the 2.4 GHz wireless interface, the Safety Subsystem SHALL apply both motor power isolation relays and engage electromagnetic braking within 150 ms of signal receipt. |
| SUB-SAFETYSUBSYSTEM-010 | subsystem-requirements | When the Safety Monitor Processor detects Main Application Processor watchdog timeout exceeding 200 ms, the Safety Subsystem SHALL assert SAFE_STOP, halt all motor commands, and log a processor fault record to non-volatile storage. |
| SUB-SAFETYSUBSYSTEM-011 | subsystem-requirements | The Safety Subsystem Safety Monitor Processor SHALL be developed and validated in accordance with IEC 61508-3 (Functional Safety of Electrical/Electronic/Programmable Electronic Safety-related Systems — Part 3: Software requirements) at SIL 3, with documented V-model lifecycle artefacts including hazard and risk analysis, software safety requirements specification, and independent verification. |
| SUB-SAFETYSUBSYSTEM-012 | subsystem-requirements | The Manual Emergency Stop Button SHALL use a dual-channel NC (normally-closed) contact circuit wired in series with the Motor Power Isolation Relay coil, such that loss of either channel independently de-energises the relay and halts motor drive within 20ms. |
| SUB-SAFETYSUBSYSTEM-013 | subsystem-requirements | When the Safety Monitor Processor detects Main Application Processor failure (watchdog timeout, CRC fault, or voltage rail collapse), the Safety Subsystem SHALL assume sole command authority, hold current velocity to zero, and maintain Emergency Stop state until manual reset, with no reliance on MAP firmware for this transition. |
| SUB-SAFETYSUBSYSTEM-014 | subsystem-requirements | The Safety Subsystem SHALL be certified to Safety Integrity Level 3 (SIL 3) per IEC 61508 (Functional safety of electrical/electronic/programmable electronic safety-related systems), with a third-party functional safety assessment covering hardware fault tolerance, systematic capability, and software development process. |
| SUB-SAFETYSUBSYSTEM-015 | subsystem-requirements | The Inclinometer Tilt Sensor Unit SHALL measure vehicle pitch and roll at 20Hz, and when tilt exceeds 12 degrees in any single axis or 10 degrees combined vector, SHALL issue a pre-warning signal to the Safety Monitor Processor; when tilt exceeds 15 degrees in any axis the Safety Monitor Processor SHALL command immediate brake application and motion inhibit within 50ms. |
| SUB-VEHICLEPLATFORM-001 | subsystem-requirements | The Chassis Frame SHALL withstand a static load of 150kg distributed across the seat mounting points without permanent deformation, and a dynamic impact load of 3g vertical shock without fracture, in accordance with ISO 7176-8 (Static, impact, and fatigue strengths). |
| SUB-VEHICLEPLATFORM-002 | subsystem-requirements | The Electronics Bay SHALL maintain an internal temperature below 70°C for all electronics mounted within it while dissipating up to 40W total under an ambient temperature of 40°C, with the vehicle stationary and no forced air flow. |
| SUB-VEHICLEPLATFORM-003 | subsystem-requirements | The Seat and Postural Support System SHALL accommodate occupants from 40kg to 120kg body mass and from 1400mm to 1900mm stature, providing a minimum of 15 degrees of backrest recline adjustment and a lap belt that tightens to resist forward displacement under 3g deceleration. |
| SUB-VEHICLEPLATFORM-004 | subsystem-requirements | The Wheel and Caster Assembly SHALL provide a turning radius not exceeding 600mm (measured from vehicle centre to outer wheel track) to allow navigation through standard 900mm accessible doorways with a minimum 150mm clearance on each side, while maintaining traction on surfaces inclined up to 6 degrees. |
| SUB-VEHICLEPLATFORM-005 | subsystem-requirements | The Electronics Bay SHALL provide IP54 environmental protection per IEC 60529 (IEC 60529: protected against dust ingress at IP5X — wire probe 1mm dia. does not penetrate; protected against water spray from any direction at IP4X), maintaining this rating through all maintenance access cycles, with a minimum 100 maintenance access cycles before seal degradation below IP54. |
| SUB-VEHICLEPLATFORM-006 | subsystem-requirements | The Vehicle Platform Electronics Bay SHALL provide a USB-C 3.1 Gen 1 service port that exposes an automated diagnostic test suite capable of verifying motor response (peak torque within 5% of nominal), brake torque (hold force >= 80N), sensor calibration (all axes within 2% of reference), battery cell health (internal resistance and capacity), and BCI pipeline integrity (signal-to-noise ratio >= 20dB), with full suite completion within 20 minutes. |
| SUB-VEHICLEPLATFORM-007 | subsystem-requirements | The Chassis Frame SHALL be constructed from aluminium alloy (6061-T6 or equivalent) with a minimum wall thickness of 3mm at structural load points, providing a rated static load capacity of 150kg (user 120kg + equipment 30kg), with a maximum deflection of 2mm under full load, and shall be corrosion-resistant to humidity up to 95% RH for indoor care facility environments. |
| SUB-VEHICLEPLATFORM-008 | subsystem-requirements | The Electronics Bay SHALL be constructed from steel or aluminium enclosure rated IP54 (dust-protected, splash-resistant), with internal thermal management maintaining component ambient temperature between 0°C and 55°C during operation, and shall withstand vibration levels up to 2g at 5-50Hz without component dislodgement or connector failure. |
| SUB-VEHICLEPLATFORM-009 | subsystem-requirements | The Chassis Frame SHALL be designed and tested in accordance with ISO 7176-8 (Requirements for static, impact, and fatigue strengths for wheelchairs) for structural adequacy under static loading of 1.5× maximum user mass plus equipment, and shall withstand impact loads of 70J without permanent deformation of safety-critical members. |
| SUB-VEHICLEPLATFORM-010 | subsystem-requirements | After any chassis shock event exceeding 3g vertical acceleration detected by the inclinometer shock channel, the Safety Monitor Processor SHALL assert a structural-integrity-check-required flag, inhibit all vehicle propulsion, and require authorised maintenance acknowledgement before resuming normal operation. |
| VER-BCIPROCESSINGSUBSYSTEM-001 | verification-requirements | The BLE 5.0 EEG headset interface SHALL be verified by: (a) streaming 32-channel 24-bit EEG data at 250Hz for 30 minutes and measuring packet loss rate across 5 runs at 5m and 10m range, confirming < 0.1% at 5m and < 1% at 10m; (b) measuring BLE connection establishment time across 20 trials confirming < 3s; (c) confirming firmware lock on BLE advertisement interval prevents interference with safety BLE channel. |
| VER-BCIPROCESSINGSUBSYSTEM-002 | verification-requirements | The BCI Processing Subsystem SNR degradation response SHALL be verified by injecting an attenuated noise baseline into the EEG Acquisition Module input, measuring elapsed time from SNR threshold crossing to STOP command on the Drive Subsystem CAN bus. Pass: STOP emitted within 3000ms on ≥10/10 runs; no drive commands emitted during suppression window. |
| VER-BCIPROCESSINGSUBSYSTEM-003 | verification-requirements | The BCI Processing Subsystem command pipeline latency SHALL be verified by replaying a known motor imagery EEG epoch at the acquisition input and measuring end-to-end latency from BLE injection to validated CAN command across 50 consecutive epochs. Pass: 95th percentile latency ≤150ms; no individual measurement >200ms. |
| VER-BCIPROCESSINGSUBSYSTEM-004 | verification-requirements | The Command Arbitration Module CAN bus interface SHALL be verified by capturing 1000 command frames during a live BCI session. Pass: all frames comply with CAN 2.0B format; status counter increments monotonically; no inter-frame gap >55ms; maximum transmission latency ≤5ms from software send to bus dominant. |
| VER-BCIPROCESSINGSUBSYSTEM-005 | verification-requirements | Verify SUB-REQ-042: Inject out-of-bounds BCI command pattern (velocity > physical maximum) into the BCI Processing Subsystem output and measure time to safe-stop signal assertion. Pass: safe-stop asserted within 100ms. Also block watchdog kick for 250ms and verify safe-stop assertion. |
| VER-BCIPROCESSINGSUBSYSTEM-006 | verification-requirements | Verify the Feature Extraction Processor loads and applies per-user CSP spatial filter matrices from encrypted calibration storage within 5 seconds of user session initialisation. |
| VER-BCIPROCESSINGSUBSYSTEM-007 | verification-requirements | Verify the Artifact Rejection Engine watchdog interface causes the BCI Processing Subsystem supervisor to reset the engine and log the event when no valid epoch output is received for more than 500ms. |
| VER-BCIPROCESSINGSUBSYSTEM-008 | verification-requirements | Verify the Main Application Processor encrypts EEG biometric data using AES-256 at rest and TLS 1.3 in transit, enforces role-based access control with at least three roles, and maintains an append-only audit log. |
| VER-BCIPROCESSINGSUBSYSTEM-009 | verification-requirements | Verify the Artifact Rejection Engine operates from the 3.3V logic rail with maximum 250mA peak current draw during active processing and maintains operation for supply voltage variation between 3.0V and 3.6V. |
| VER-BCIPROCESSINGSUBSYSTEM-010 | verification-requirements | Verify electrode interface components contacting user scalp meet ISO 10993-1 (Biological evaluation of medical devices, Part 1) biocompatibility requirements: (a) inspect material data sheets confirming each scalp-contact material has been classified per ISO 10993-1 risk framework for prolonged skin contact; (b) measure contact impedance at 1kHz before and after 50 decontamination cycles with specified clinical disinfectant. Pass: all materials carry ISO 10993-1 biocompatibility classification; contact impedance change ≤ 10% after 50 cycles. Fail: any unclassified material; impedance change > 10%. |
| VER-BCIPROCESSINGSUBSYSTEM-011 | verification-requirements | Verify the Artifact Rejection Engine occupies no more than 30% of available Feature Extraction Processor CPU cycles during continuous EEG processing at 250 SPS per channel, with deterministic maximum latency of 4ms per processing frame. |
| VER-BCIPROCESSINGSUBSYSTEM-012 | verification-requirements | Verify the Artifact Rejection Engine transfers cleaned 32-channel EEG epochs as float32 arrays in 1-second windows with 50% overlap at a throughput of 2 epochs/second per channel to the Feature Extraction Processor. |
| VER-BCIPROCESSINGSUBSYSTEM-013 | verification-requirements | Verify the BCI Classifier passes command probability vectors for four navigation classes as float32 with per-class confidence, SNR index, and rolling 2-minute accuracy metric at minimum 2Hz to the Command Arbitration Module. |
| VER-BCIPROCESSINGSUBSYSTEM-014 | verification-requirements | Verify IFC-REQ-013: Configure a test harness injecting synthetic CSP-projected feature vectors at 100Hz from the Feature Extraction Processor to the BCI Classifier. Verify that 1000 consecutive feature vectors are received, decoded, and classification results returned within the 10ms latency budget. Pass: all 1000 vectors received with CRC intact; latency p99 ≤ 10ms measured by timestamp on both ends; no dropped vectors. Fail: any CRC error, dropped vector, or latency exceedance. |
| VER-BCIPROCESSINGSUBSYSTEM-015 | verification-requirements | The USB-C Diagnostic Port functionality SHALL be verified by executing the automated diagnostic test suite from a service laptop and measuring: (a) all test categories complete within 20 minutes; (b) pass/fail results individually reported with timestamped log entries; (c) graceful reconnection without data loss after disconnect during a test run. |
| VER-BCIPROCESSINGSUBSYSTEM-016 | verification-requirements | Verify SYS-REQ-007 system-level integration: With the fully integrated EEG Accessibility Buggy operating in Normal Navigation mode at 4 km/h, inject a sustained SNR degradation below the classification threshold via a BCI test signal source. (a) Confirm the system does NOT transition to Degraded/Assisted mode within the first 4.9 seconds of sustained low SNR. (b) Confirm the system transitions to Degraded/Assisted mode within 5.5 seconds of sustained low SNR onset (5-second threshold plus 500ms tolerance). (c) Verify speed is clamped to 3 km/h within 200ms of mode transition. (d) Verify BCI command set reduces to binary go/stop — inject a left-turn motor imagery pattern and confirm it is NOT executed. (e) Restore SNR above threshold and verify the system returns to Normal Navigation mode within 10 seconds. Fail: transition before 4.9s, transition after 5.5s, speed exceeds 3 km/h, or non-binary command accepted. |
| VER-BCIPROCESSINGSUBSYSTEM-017 | verification-requirements | Verify SYS-REQ-008 system-level integration: With the fully integrated EEG Accessibility Buggy operating in Normal Navigation mode, inject a declining BCI accuracy profile via a test signal source so that rolling 2-minute accuracy crosses the 70% threshold. (a) Confirm the system does NOT transition to Degraded/Assisted mode while rolling accuracy remains at 71% or above. (b) Confirm the system transitions to Degraded/Assisted mode within 2 seconds of rolling accuracy dropping to 69% or below. (c) Verify an audible alert of minimum 65 dBA is generated within 1 second of mode transition. (d) Verify speed is limited to 3 km/h. (e) Restore accuracy above 70% for a full 2-minute window and verify Normal Navigation mode resumes. Fail: premature transition, transition delayed beyond 2 seconds, no audible alert, speed exceeds 3 km/h in Degraded mode, or no recovery after accuracy restoration. |
| VER-COMMUNICATIONSUBSYSTEM-001 | verification-requirements | The Communication Subsystem cellular modem network isolation SHALL be verified by injecting UDP packets addressed to the CAN bus gateway IP range from the modem interface while monitoring all internal bus traffic. Pass: zero packets from the cellular modem interface appear on CAN bus segments across 100 injection attempts. |
| VER-COMMUNICATIONSUBSYSTEM-002 | verification-requirements | Verify SUB-REQ-038: Trigger simulated Emergency Stop event in the Communications Controller and measure BLE advertisement receipt timestamp at BLE gateway sniffer. Pass: alert received within 500ms of trigger for 10 consecutive tests with gateway at 10m range. |
| VER-COMMUNICATIONSUBSYSTEM-003 | verification-requirements | Verify IFC-REQ-027: connect Communication Controller and Cellular Modem via USB, issue AT+CGDCONT APN configuration command, initiate LTE data session, and measure round-trip ping latency to a test server over LTE. Pass: USB enumeration succeeds as CDC-ECM, APN configured, ping RTT <= 100ms in 95th percentile over 100 measurements. |
| VER-COMMUNICATIONSUBSYSTEM-004 | verification-requirements | Verify IFC-REQ-028: pair BLE module with EEG headset reference device, stream 8-channel EEG data for 60 seconds, timestamp each packet at BLE receive and at BCI Acquisition Module input. Pass: connection interval 7.5ms confirmed in BLE sniffer trace, packet loss < 0.1%, end-to-end latency <= 20ms in 99th percentile. |
| VER-COMMUNICATIONSUBSYSTEM-005 | verification-requirements | Verify SUB-REQ-067: Trigger a simulated Seizure Emergency Stop on the EEG Accessibility Buggy while the facility emergency system BLE receiver is active. Measure time from E-Stop trigger to BLE alert packet receipt at the receiver. Pass if packet received within 500ms with correct device ID, alert type code, GPS coordinates, and UTC timestamp on 10 consecutive trials. |
| VER-COMMUNICATIONSUBSYSTEM-006 | verification-requirements | Verify the Bluetooth LE Module maintains a stable BLE 5.2 connection sustaining 32-channel EEG data at 8kHz sample rate (512kbps) within a 3m operating range with no physical obstructions. |
| VER-COMMUNICATIONSUBSYSTEM-007 | verification-requirements | Verify the Cellular Modem authenticates to the remote telemetry server using mutual TLS 1.3 with a device-unique X.509 certificate, rejecting server certificates not signed by the system root CA. |
| VER-COMMUNICATIONSUBSYSTEM-008 | verification-requirements | Verify the Cellular Modem transmits session telemetry to the remote server at a minimum interval of 10 seconds with a maximum uplink latency of 2 seconds under nominal 4G coverage. |
| VER-COMMUNICATIONSUBSYSTEM-009 | verification-requirements | Verify IFC-REQ-005: Connect a service laptop via USB-C cable and execute firmware flash, configuration export, fault log download, and calibration data upload operations. Pass: (a) each operation completes successfully without data corruption (hash check); (b) firmware flash completes within 10 minutes; (c) fault log export produces structured JSON with all required fields; (d) calibration data import round-trips without any field alteration. Fail: any operation fails, hash mismatch, or log missing required fields. |
| VER-COMMUNICATIONSUBSYSTEM-010 | verification-requirements | Verify SUB-REQ-056: Connect a test host to the Communication Subsystem USB-C service port. Issue each motor response verification command individually from the defined diagnostic API. Measure time from command issuance to pass/fail result with logged timestamp. Pass: all commands return a result with timestamp within 10 seconds of issuance on each of 10 consecutive command cycles. Fail: any result arrives after 10 seconds or lacks a timestamp. |
| VER-COMMUNICATIONSUBSYSTEM-011 | verification-requirements | Verify IFC-REQ-004: Pair the vehicle with a test smartphone running the companion app via BLE 5.0. (a) Confirm status display (operating mode, battery level, session history) updates at ≥1 Hz. (b) Trigger a simulated emergency stop and verify BLE emergency alert reaches the companion app within 500ms, measured from E-stop relay actuation to app notification. (c) Capture BLE traffic with a sniffer and confirm all advertising and connection PDUs use LE Secure Connections pairing with AES-128 link-layer encryption (no legacy pairing). Pass: all three criteria met. Fail: update rate <1Hz, alert latency >500ms, or unencrypted PDUs detected. |
| VER-COMMUNICATIONSUBSYSTEM-012 | verification-requirements | Verify IFC-REQ-006: Configure a test CMMS server endpoint on the facility Wi-Fi (802.11ac) network with TLS 1.3 and API key authentication. (a) Trigger a maintenance event and confirm a REST API POST is received by the test server within 30 seconds with the correct JSON schema (maintenance log, fault code, fleet ID). (b) Configure an invalid API key on the server and confirm the vehicle logs an CMMS_AUTH_FAIL event and ceases retry attempts after 3 failures. (c) Capture Wi-Fi traffic and confirm all HTTP traffic is TLS 1.3 — no cleartext requests. Pass: all three criteria met. |
| VER-COMMUNICATIONSUBSYSTEM-013 | verification-requirements | Verify IFC-REQ-025: Connect a UART analyser to the Communication Controller to Bluetooth LE Module UART link. (a) Issue a sequence of 500 HCI commands at maximum throughput and measure end-to-end transfer latency — Pass: ≤5ms latency for 95th percentile across 500 commands. (b) Disable hardware flow control (RTS/CTS) lines and confirm data corruption is detected — Pass: module reports HCI error code within 100ms of buffer overrun. (c) Measure actual baud rate using frequency counter — Pass: 1.000 Mbps ±0.5%. Fail: latency >5ms at P95, error not detected within 100ms, or baud error >0.5%. |
| VER-DRIVESUBSYSTEM-001 | verification-requirements | Verify IFC-REQ-018: Apply 20kHz PWM gate-drive signals to the Left Drive Motor Assembly and measure encoder feedback period at 10kHz sample rate with an oscilloscope. Pass criteria: PWM frequency within ±1% of 20kHz, encoder signal received within 1ms propagation delay, and velocity closed-loop error converges to within ±0.1 km/h in steady state. |
| VER-DRIVESUBSYSTEM-002 | verification-requirements | Verify IFC-REQ-019: Apply 20kHz PWM gate-drive signals to the Right Drive Motor Assembly and measure encoder feedback period at 10kHz sample rate. Pass criteria: symmetric with IFC-REQ-018 verification — PWM frequency within ±1% of 20kHz, encoder delay within 1ms, velocity error within ±0.1 km/h. Additionally verify left-right encoder latency difference does not exceed 0.5ms. |
| VER-DRIVESUBSYSTEM-003 | verification-requirements | Verify IFC-REQ-020: Inject an overcurrent condition on the Drive Power Stage test bench and measure the time from overcurrent event to logic-level trip signal at the Motor Controller Unit. Pass criteria: trip signal received within 5ms, pre-charge sequence completes without bus voltage overshoot exceeding 5% above 48V nominal, MCU logs a fault code within 10ms of receiving trip signal. |
| VER-DRIVESUBSYSTEM-004 | verification-requirements | The Motor Controller Unit CAN heartbeat watchdog SHALL be verified by injecting a CAN heartbeat loss and measuring elapsed time to zero motor velocity. Pass: both motors reach zero velocity within 250ms, MCU remains in safe state until a valid restart CAN frame is received, and no uncommanded restart occurs within a 30-second observation window. |
| VER-DRIVESUBSYSTEM-005 | verification-requirements | Verify SUB-REQ-058: Suppress MCU CAN heartbeat and measure time to coast-to-stop state and MCU_FAULT assertion to Safety Monitor Processor. Pass: coast-to-stop commanded within 100 ms, MCU_FAULT asserted within 50 ms of timeout detection, 10 trials. |
| VER-DRIVESUBSYSTEM-006 | verification-requirements | The EEG Accessibility Buggy SHALL be verified to confirm that in Care Attendant Override mode the Drive Subsystem responds to joystick inputs within 100ms, obstacle detection remains active with ≤200ms response, maximum speed is limited to 6 km/h, and the system sustains override operation for ≥30 minutes at 50% throttle. |
| VER-DRIVESUBSYSTEM-007 | verification-requirements | Verify the Motor Controller Unit implements closed-loop velocity control at 100 Hz with 1024 PPR quadrature encoder feedback, achieving steady-state velocity error not exceeding ±0.1 km/h at any commanded speed. |
| VER-DRIVESUBSYSTEM-008 | verification-requirements | Verify the Motor Controller Unit enforces the 6 km/h Normal Navigation mode speed limit and 2 km/h Restricted mode speed limit by clamping velocity commands exceeding each threshold before motor drive stage application. |
| VER-DRIVESUBSYSTEM-009 | verification-requirements | Verify the Drive Power Stage trips the hardware overcurrent protection and isolates motor phase outputs within 5ms when per-channel motor current exceeds 30A, independent of Motor Controller Unit firmware. |
| VER-DRIVESUBSYSTEM-010 | verification-requirements | Verify the Left and Right Drive Motor Assemblies each deliver a minimum continuous shaft output of 250W at 48V DC across 0°C to 40°C with traction maintained on level indoor surfaces up to 5% gradient. |
| VER-DRIVESUBSYSTEM-011 | verification-requirements | Verify the Motor Controller Unit hardware overcurrent protection disconnects motor phase outputs within 5ms when phase current exceeds 120% of rated maximum, with no firmware execution required. |
| VER-DRIVESUBSYSTEM-012 | verification-requirements | Verify the Drive Subsystem enforces a maximum speed cap of 3 km/h in Degraded/Assisted mode by limiting PWM duty cycle to 50% of Normal Navigation maximum, independent of BCI or joystick input value. |
| VER-DRIVESUBSYSTEM-013 | verification-requirements | Verify SUB-REQ-077: Submit Drive Subsystem assembly (Motor Controller Unit and Motor Power Isolation Relay) for IEC 60601-1-2 (Medical Electrical Equipment — Electromagnetic disturbances) conducted and radiated emissions and immunity testing by an accredited test laboratory. Pass: test report from accredited lab confirms compliance with all applicable limits and no performance degradation during immunity tests. Fail: any emissions exceed limits or immunity test causes motor controller malfunction. |
| VER-HMISUBSYSTEM-001 | verification-requirements | Verify SUB-REQ-032: trigger E-stop via software command and measure Audio Alert Module SPL with a calibrated sound level meter at 1m. Record onset time from E-stop signal assertion to first audible tone. Pass: SPL >= 80dB at 1m, onset <= 100ms, sustained tone until E-stop cleared, in 5 consecutive tests. |
| VER-HMISUBSYSTEM-002 | verification-requirements | The Carer Override Module switch activation latency SHALL be verified using a hardware override switch simulator, measuring the timestamp delta from switch assertion to first joystick command accepted by the Drive Subsystem via CAN bus analyser. Pass: delta ≤100ms on 10 consecutive trials. |
| VER-HMISUBSYSTEM-003 | verification-requirements | Verify IFC-REQ-029: inject alert-code 0x01 (Emergency Stop) via I2C at 400kHz from the application processor, measure time from I2C transaction completion to first audio sample output from Audio Alert Module. Pass: onset latency <= 50ms in 10 consecutive trials, tone frequency and duration match alert-code-0x01 specification. |
| VER-HMISUBSYSTEM-004 | verification-requirements | Verify SUB-REQ-047: power up the display unit, enter Normal Navigation mode with a test BCI signal source, and measure display update frequency for BCI accuracy, speed, battery SoC, and mode fields over 30 seconds. Measure screen brightness with a calibrated photometer at 0.5m distance. Pass: all four fields update >= 2Hz, brightness >= 300 cd/m2. |
| VER-HMISUBSYSTEM-005 | verification-requirements | Verify SUB-REQ-048: mount Status LED Array on vehicle rear at operational position. Using a calibrated photometer, measure luminous intensity at 11 angular positions spanning 120 degrees (0°, ±12°, ±24°, ±36°, ±48°, ±60°) at a distance of 1m in a darkened environment. Pass criterion: all 11 measurements ≥10 mcd per LED element for each of the three colour states (green, amber, red). Repeat at low battery (battery at 10% SoC) to confirm intensity is maintained. |
| VER-HMISUBSYSTEM-006 | verification-requirements | Verify IFC-REQ-030: using SPI analyser on the MAP–LED Array bus, command a mode transition (Normal→Degraded) and measure elapsed time from transition command issue to first valid LED frame on SPI bus. Pass criterion: ≤20ms latency on 20 consecutive transitions. Confirm the frame carries independently addressable RGB values for minimum 6 elements by inspecting SPI frame structure against protocol specification. |
| VER-HMISUBSYSTEM-007 | verification-requirements | The Carer Override Module rear switch activation latency SHALL be verified at 4 km/h vehicle speed, measuring elapsed time from switch edge to first accepted joystick command via oscilloscope on the CARER_OVERRIDE line and Drive Subsystem CAN bus. Pass: elapsed time ≤100ms across 20 consecutive activations; no single measurement >120ms. |
| VER-HMISUBSYSTEM-008 | verification-requirements | Verify SUB-REQ-068: Inject a BCI accuracy threshold crossing event (accuracy dropping from 75% to 65%) while measuring Audio Alert Module response. Pass if 880Hz tone at >=85 dBSPL at 1m is audible within 200ms of threshold crossing and sustained until mode transition or HMI acknowledgement, on 5 consecutive trials. |
| VER-HMISUBSYSTEM-009 | verification-requirements | Verify SUB-REQ-069: Activate the rear-mounted override switch while the buggy is in BCI navigation mode. Measure time from switch activation to joystick steering authority confirmed active and BCI commands confirmed disabled. Pass if handover confirmed within 100ms and BCI commands produce no motion response, on 10 consecutive trials including 3 during active BCI movement command. |
| VER-HMISUBSYSTEM-010 | verification-requirements | Verify SUB-REQ-073: Inject a BCI accuracy drop to 65% (degraded mode trigger). Observe Status LED Array and Display Unit. Pass if amber 2Hz pulse is visible within 100ms of mode entry and Display Unit shows the specified text string within 100ms, both persisting until mode exit, on 5 consecutive trials. |
| VER-HMISUBSYSTEM-011 | verification-requirements | Verify the Status LED Array displays the correct distinct colour state for each operating mode and completes state transitions within 200ms of the triggering event. |
| VER-HMISUBSYSTEM-012 | verification-requirements | Verify SUB-REQ-052: Activate the rear-mounted override switch and measure elapsed time from switch edge to CARER_OVERRIDE signal assertion at the Safety Monitor Processor input pin, using an oscilloscope trigger on the switch and SMP GPIO. Pass: assertion time ≤ 50ms on all 20 consecutive activations; signal maintained continuously while switch is held. Fail: any measurement > 50ms or signal drop during hold. |
| VER-HMISUBSYSTEM-013 | verification-requirements | The Carer Override Module joystick command latency SHALL be verified with CARER_OVERRIDE asserted by measuring elapsed time from joystick deflection input to CAN frame transmission on the Drive Subsystem bus via logic analyser. Pass: CAN frame transmitted within 20ms on ≥19/20 activations; command rate ≥50Hz sustained over 10 seconds. |
| VER-HMISUBSYSTEM-014 | verification-requirements | Verify IFC-REQ-026: Connect an SPI logic analyser to the Main Application Processor to Display Unit link. (a) Command display to render a full-frame 800x480 16-bit image and measure SPI clock frequency — Pass: 40 MHz ±2%. (b) Render 60 consecutive frames and measure frame rate — Pass: ≥30 fps with no frame drops (chip-select transitions counted). (c) Send a chip-select pulse while bus is idle and confirm display responds without bus contention. Fail: clock frequency out of tolerance, frame rate <30fps, or bus contention detected. |
| VER-PERCEPTIONSUBSYSTEM-001 | verification-requirements | Verify SUB-REQ-023: place calibrated targets at 0.1m, 0.5m, 1.0m, 1.5m, and 2.0m in the forward arc under lighting conditions from 0 lux (IR illumination only) to 10,000 lux. Confirm distance readings are within 50mm of ground truth at 10Hz sustained over 30 seconds. Pass: all five distances within tolerance at all three lighting levels. |
| VER-PERCEPTIONSUBSYSTEM-002 | verification-requirements | Verify IFC-REQ-023: inject an obstacle scenario via test fixture and capture the SPI bus between the Perception MCU and Safety Monitor Processor with a logic analyser. Confirm 4-byte frame format, 10Hz nominal rate, rolling counter incrementing correctly, and that after two missed frames the Safety Monitor Processor asserts communication fault within 250ms. Pass: all frame format, rate, counter, and fault assertions met in 100 consecutive frames. |
| VER-PERCEPTIONSUBSYSTEM-003 | verification-requirements | Verify SUB-REQ-026: with system running, halt the Perception MCU firmware (power off the MCU or inject a software lockup). Monitor Safety Monitor Processor output. Confirm E-stop sequence is initiated within 150ms of last valid frame. Pass: E-stop asserted within 150ms in 5 consecutive tests from normal operating state. |
| VER-PERCEPTIONSUBSYSTEM-004 | verification-requirements | Verify SUB-REQ-035: Mount vehicle on tilting test rig; rotate to 15.5 degrees at 5 degrees/second and record timestamp when tilt-hazard signal is asserted on Safety Monitor Processor I2C bus. Pass: signal asserted within 50ms of 15-degree threshold crossing for 5 trials in each axis. |
| VER-PERCEPTIONSUBSYSTEM-005 | verification-requirements | Verify SUB-REQ-054: Apply vehicle tilt exceeding 15 degrees on test fixture and monitor tilt data publication rate and content to Safety Monitor Processor. Pass: data rate >= 20 Hz, includes tilt angle, axis identity, and confidence score, maintained for 30 s trial. |
| VER-PERCEPTIONSUBSYSTEM-006 | verification-requirements | Verify the Perception MCU processes all sensor inputs and emits an obstacle alert frame to the Safety Monitor Processor within 50ms of sensor data arrival at full 10Hz sensor update rate. |
| VER-PERCEPTIONSUBSYSTEM-007 | verification-requirements | Verify the Side Proximity Sensor Pair detects objects within 0.5m laterally on each side and delivers a TTL-level alert signal to the Perception MCU within 30ms of intrusion. |
| VER-PERCEPTIONSUBSYSTEM-008 | verification-requirements | Verify SUB-REQ-040: Connect a calibrated power supply to the Inclinometer Tilt Sensor Unit 3.3V input. Measure supply voltage at the sensor under nominal and maximum load conditions. Introduce a ±5% supply ripple at 1kHz and verify sensor output stability. Pass: supply voltage 3.3V ± 3% (3.20V–3.40V) under all load conditions; inclinometer output tilt reading stable ± 0.1° during ripple injection. Fail: voltage outside tolerance or tilt reading drift > 0.1° during ripple. |
| VER-PERCEPTIONSUBSYSTEM-009 | verification-requirements | Verify IFC-REQ-022: Position a 300mm × 300mm flat obstacle at 0.5m, 0.45m, and 0.6m on each lateral side of the vehicle. Pass: (a) alert asserted as TTL HIGH within 30ms of obstacle at 0.5m or 0.45m (≥ 20/20 placements per side); (b) no alert when obstacle at 0.6m (≥ 10/10 placements per side); (c) GPIO line returns LOW within 30ms of obstacle removal. Fail: any missed detection at ≤ 0.5m, any false positive at 0.6m, or delayed deassertion. |
| VER-PERCEPTIONSUBSYSTEM-010 | verification-requirements | Verify IFC-REQ-021: Scan I2C bus at 400 kHz (400 kHz I2C mode per UM10204) and enumerate all three depth sensor addresses. Drive each sensor with a ranging command and verify response timing. Pass: (a) all three sensors enumerate at correct addresses; (b) ranging responses received within 10ms of command; (c) no bus contention (SDA/SCL monitored with logic analyser) across 1000 ranging cycles. Fail: any address absent, latency > 10ms, or SDA collision detected. |
| VER-POWERSUBSYSTEM-001 | verification-requirements | The Battery Management System thermal fault response SHALL be verified by forcing a cell temperature sensor input above 60°C via calibrated resistance substitution and measuring time to 48V bus de-energisation. Pass: bus de-energised within 200ms and CAN fault code broadcast within 200ms on ≥5/5 test runs. |
| VER-POWERSUBSYSTEM-002 | verification-requirements | The BMS-to-Safety Monitor Processor GPIO fault interface SHALL be verified by injecting a 55°C temperature threshold crossing and measuring: (a) GPIO fault line transitions low within 50ms; (b) transition is independent of CAN bus availability. Pass: both criteria met on ≥5/5 runs with CAN connected and ≥5/5 runs with CAN disconnected. |
| VER-POWERSUBSYSTEM-003 | verification-requirements | Verify SUB-REQ-071: Connect the buggy to both a 230V 50Hz supply and (separately) a 120V 60Hz supply at 20% SoC. Measure time to reach 100% SoC, confirming CC-CV profile is applied and charge terminates automatically. Pass if charge completes within 4 hours on both supply voltages, SoC measurement accuracy ±2%, and trickle maintenance engages on completion. |
| VER-POWERSUBSYSTEM-004 | verification-requirements | Verify the Lithium Iron Phosphate Battery Pack delivers a minimum of 4 hours continuous operation at rated system load: (a) charge pack to 100% SoC at 25°C, (b) discharge at combined rated system load (drive motors at 3 km/h on flat surface, BCI processing active, HMI and Safety Subsystem energised), (c) record elapsed time from start of discharge to first alarm at 10% SoC. Repeat at 40°C ambient. Pass: elapsed time ≥ 4 hours at both 25°C and 40°C. Fail: either condition below 4 hours. |
| VER-POWERSUBSYSTEM-005 | verification-requirements | Verify the DC-DC Converter Array maintains each output rail (12V, 5V, 3.3V) within ±5% of nominal voltage and with output ripple not exceeding 50mV peak-to-peak across 10% to 100% rated load range. |
| VER-POWERSUBSYSTEM-006 | verification-requirements | Verify the Charge Controller charges the battery pack from 20% to 100% state of charge within 3 hours when connected to a 240V AC facility supply. |
| VER-POWERSUBSYSTEM-007 | verification-requirements | Verify the Battery Management System transmits pack voltage, individual cell voltages, SoC, temperature summary, and pack current to the Main Application Processor via CAN 2.0B at 250 kbit/s at 100ms intervals. |
| VER-POWERSUBSYSTEM-008 | verification-requirements | Verify IFC-REQ-002: Connect the vehicle to a 230V 50Hz facility charging dock and measure galvanic isolation resistance between vehicle chassis and mains supply. Pass: (a) isolation resistance ≥ 2MΩ at 500V DC (per IEC 60601-1 measurement method); (b) charge current flows within 60 seconds of dock connection; (c) charge terminates automatically at 100% SoC with charger LED indicating complete. Fail: isolation resistance < 2MΩ, no charging within 60s, or no auto-termination. |
| VER-POWERSUBSYSTEM-009 | verification-requirements | Verify SUB-REQ-036: Connect the charge controller to a 230V 50Hz supply and then a 120V 60Hz supply. Measure input power acceptance and output to battery. Pass: (a) charging initiates within 60s at 230V 50Hz; (b) charging initiates within 60s at 120V 60Hz; (c) no fault codes generated at either input; (d) BMS reports valid charge current at both supply voltages. Fail: failure to accept either supply or fault code generated. |
| VER-POWERSUBSYSTEM-010 | verification-requirements | Verify SUB-REQ-055: Connect the Power Subsystem to a 230V 50Hz AC supply at 20% SoC via a calibrated current probe on the mains lead. (a) Measure peak inrush current during first 100ms of connection across 5 trials — Pass: peak ≤16 A on all 5 trials. (b) Monitor cell temperature via thermocouple array at 1Hz during full charge cycle — Pass: no cell exceeds 45°C. (c) Time charge completion from 20% to 100% SoC — Pass: completion within 6 hours. Fail: inrush >16 A, cell temperature >45°C, or charge time >6 hours on any trial. |
| VER-SAFETYSUBSYSTEM-001 | verification-requirements | Verify SUB-REQ-001: Inject a simulated main processor fault (power rail pull-down to 0V) while Safety Monitor Processor is executing safety state machine. Verify via logic analyser that safety state machine continues to execute at 200Hz for ≥5 seconds post-fault, and that relay de-energise command is issued within 500ms of heartbeat loss detection. Pass: no execution gap >6ms in safety loop; relay command issued; all outputs set to safe state. Fail: execution halt, missed heartbeat detection, or relay remains energised. |
| VER-SAFETYSUBSYSTEM-002 | verification-requirements | Verify SUB-REQ-002: Apply de-energise command to Motor Power Isolation Relay under 4 load conditions (0A, 30A, 60A steady, 200A pulse). Measure with oscilloscope the time from control-line falling edge to relay contact open confirmed by feedback contact. Pass: all measurements ≤20ms. Fail: any measurement >20ms, or relay fails to open within 50ms under any load condition. |
| VER-SAFETYSUBSYSTEM-003 | verification-requirements | Verify SUB-REQ-003: Replay 50 CHB-MIT annotated seizure EEG segments through the Seizure Detection Module and measure time-to-detection flag from annotated onset. Also replay 8 hours of normal EEG operation and count false positive seizure flags. Pass: ≥95% of seizure segments detected within 150ms; false positive count ≤1 across full 8-hour replay. Fail: detection latency >150ms for >5% of segments, or false positive count >1. |
| VER-SAFETYSUBSYSTEM-004 | verification-requirements | Verify IFC-REQ-007: Inject a simulated main processor heartbeat halt (hold GPIO low). Measure on oscilloscope from last valid heartbeat to Safety Monitor Processor E-stop output assertion. Separately, verify no data payload is transmitted on the heartbeat line using a protocol analyser. Pass: E-stop asserted within 500ms of last heartbeat; no data payload detected on heartbeat GPIO. Fail: E-stop delayed >500ms or data content detected. |
| VER-SAFETYSUBSYSTEM-005 | verification-requirements | Verify IFC-REQ-008: With relay energised, open (disable) one control channel at a time. Verify relay de-energises within 20ms for each single-channel failure. Also verify relay does not energise when both channels are driven independently by separate fault-injected outputs. Pass: relay opens on either single-channel fault; relay does not energise with mismatched channels. Fail: relay remains closed on single-channel fault. |
| VER-SAFETYSUBSYSTEM-006 | verification-requirements | Verify SYS-REQ-002 end-to-end: In a fully integrated vehicle at maximum speed (6 km/h), inject each of the 5 safety triggers (BCI signal loss, seizure EEG replay, tilt >15°, manual E-stop button, processor heartbeat loss) and measure from trigger event to vehicle coming to rest (wheels stopped). Pass: vehicle comes to rest within 200ms plus brake stopping distance for all 5 triggers. Fail: any trigger results in continued motion beyond 200ms relay actuation time. |
| VER-SAFETYSUBSYSTEM-007 | verification-requirements | The Inclinometer Tilt Sensor Unit SHALL be verified by mounting the buggy on a calibrated tilt table, incrementally inclining from 0° to 20° in 1° steps at 1°/s, and confirming: (a) angle readings within ±0.5° of reference at each step, (b) 100Hz output rate continuous across full range, (c) E-stop command issued by Safety Monitor Processor within 200ms of crossing 15° sustained for 200ms. |
| VER-SAFETYSUBSYSTEM-008 | verification-requirements | The Manual Emergency Stop Button hardwire circuit SHALL be verified by: (a) measuring contact-to-relay-coil de-energisation time using an oscilloscope across 10 actuations with motor at rated load, confirming all measurements ≤5ms, (b) inspecting the wiring schematic to confirm no software-mediated path in the disconnect circuit. |
| VER-SAFETYSUBSYSTEM-009 | verification-requirements | The Safety Subsystem E-stop state machine SHALL be verified by injecting each of the five defined safety triggers (BCI signal loss, seizure flag, tilt threshold, manual E-stop, heartbeat failure) individually and in combination, confirming: relay de-energisation, brake command, and HMI alert all activated within 200ms of trigger, measured from trigger signal assertion to final output using a logic analyser. |
| VER-SAFETYSUBSYSTEM-010 | verification-requirements | The Safety Monitor Processor heartbeat watchdog SHALL be verified by: (a) halting the main application processor and confirming E-stop triggers within 600ms (500ms watchdog timeout + 100ms response margin), (b) injecting heartbeat period jitter at +20% and +21% of nominal and confirming E-stop triggers only at the 21% case, (c) repeating 50 times to confirm deterministic behaviour. |
| VER-SAFETYSUBSYSTEM-011 | verification-requirements | The emergency BLE iBeacon interface SHALL be verified by: (a) triggering each of five E-stop conditions and measuring time from trigger to iBeacon advertisement transmission at facility BLE gateway, confirming < 500ms in 50 consecutive tests; (b) confirming advertisement contains correct device ID, alert type, and GPS coordinates by sniffing the BLE advertisement payload with a protocol analyser. |
| VER-SAFETYSUBSYSTEM-012 | verification-requirements | The SPI interface between Inclinometer Tilt Sensor Unit and Safety Monitor Processor SHALL be verified by: (a) capturing 1000 consecutive SPI transactions at 1MHz with a logic analyser, confirming 6-byte frame format, roll/pitch/timestamp fields, and CRC validity in all frames; (b) injecting a corrupted CRC and confirming the Safety Monitor Processor discards the frame and logs a sensor fault within one SPI cycle (1ms). |
| VER-SAFETYSUBSYSTEM-013 | verification-requirements | Verify SUB-REQ-043: Inspect electronic assembly against design documentation. Confirm Safety Monitor Processor PCB is mechanically separate from Main Application Processor PCB, has independent connector to DC-DC Converter Array power rail, and has no shared power nets with the Main Application Processor on the backplane. |
| VER-SAFETYSUBSYSTEM-014 | verification-requirements | Verify SYS-REQ-020: review EEG headset manufacturer's biological safety evaluation report against ISO 10993-1. Confirm biocompatibility testing covers cytotoxicity (ISO 10993-5), sensitisation (ISO 10993-10), and skin irritation (ISO 10993-23) for all skin-contacting electrode and headset materials. Pass: manufacturer provides valid ISO 10993-1 conformance certificate with no Category I or Category II adverse findings for prolonged skin contact. |
| VER-SAFETYSUBSYSTEM-015 | verification-requirements | Verify SUB-REQ-051: Simulate facility emergency system halt command via 2.4 GHz wireless interface and measure elapsed time from signal receipt to motor isolation relay actuation and electromagnetic brake engagement. Pass: both events complete within 150 ms across 20 consecutive trials at operating temperature. |
| VER-SAFETYSUBSYSTEM-016 | verification-requirements | Verify SUB-REQ-057: Halt MAP watchdog refresh and measure elapsed time to SAFE_STOP assertion and non-volatile fault log write. Pass: SAFE_STOP asserted within 200 ms, fault record present in NV storage, across 10 trials. |
| VER-SAFETYSUBSYSTEM-017 | verification-requirements | Verify SUB-REQ-060: Using a test fixture that monitors relay coil continuity, open each NC contact channel independently (channel A, then channel B) and confirm Motor Power Isolation Relay de-energises within 20ms measured from contact open to relay drop-out on oscilloscope. Pass criterion: de-energisation within 20ms for both channels independently, zero relay hold when either channel is open. |
| VER-SAFETYSUBSYSTEM-018 | verification-requirements | Verify SUB-REQ-061: In a controlled test environment, inject a simulated MAP watchdog timeout by halting MAP firmware execution, and verify that the Safety Monitor Processor asserts Emergency Stop state and zeros velocity command within 250ms (200ms watchdog + 50ms propagation) with no dependency on MAP recovery. Pass criterion: velocity = 0 within 250ms across 10 injected fault events, and vehicle does not resume motion without manual reset. |
| VER-SAFETYSUBSYSTEM-019 | verification-requirements | Verify SUB-REQ-063: Review certification documentation from an accredited IEC 61508 assessor covering Safety Subsystem hardware fault tolerance (HFT), systematic capability SC3, and software development process documentation (lifecycle plan, V&V evidence). Pass criterion: certificate issued by a Notified Body or TUV-equivalent confirming SIL-3 suitability and no open safety defects. |
| VER-SAFETYSUBSYSTEM-020 | verification-requirements | Verify SUB-REQ-070: Place the buggy on a tilt platform and gradually increase pitch to 12 degrees (confirm pre-warning signal issued to Safety Monitor), then continue to 15 degrees (confirm brake application and motion inhibit). Measure time from 15-degree crossing to brake confirmed. Pass if pre-warning issued at 12±0.5 degrees, brake applied within 50ms of 15-degree crossing, and motion inhibited within 100ms, on 5 trials each axis. |
| VER-SAFETYSUBSYSTEM-021 | verification-requirements | The MAP watchdog failsafe mechanism SHALL be verified by injecting a simulated MAP watchdog timeout (halt firmware refresh) and measuring time from last heartbeat to SAFE_STOP assertion and brake engagement; the total latency SHALL be ≤200ms measured on oscilloscope at the relay coil. |
| VER-SAFETYSUBSYSTEM-022 | verification-requirements | Verify the Safety Subsystem Safety Monitor Processor is developed and validated in accordance with IEC 61508-3 at SIL 3, with documented V-model lifecycle artefacts. |
| VER-SAFETYSUBSYSTEM-023 | verification-requirements | Verify the Seizure Detection Module updates the shared memory region on the Safety Monitor Processor at 50Hz with a 1-byte status word and that the Safety Monitor Processor reads this region within 10ms of each update. |
| VER-VEHICLEPLATFORM-001 | verification-requirements | Verify SUB-REQ-027: load test the Chassis Frame per ISO 7176-8 static load procedure — apply 150kg distributed load via seat mounting points, hold for 5 minutes, inspect for permanent deformation. Apply 3g vertical impulse via drop test fixture. Pass: zero permanent deformation after static test; no fracture or crack after dynamic test. |
| VER-VEHICLEPLATFORM-002 | verification-requirements | Verify SUB-REQ-049: perform minimum turning radius test per ISO 7176-3 test method. Mark vehicle centre on test floor, execute full 360-degree turning manoeuvre, measure outer wheel track swept radius. Verify navigation through a 900mm doorway simulation with 150mm marker barriers on each side. Pass: swept radius <= 600mm, no contact with barriers in 5 trials. |
| VER-VEHICLEPLATFORM-003 | verification-requirements | The Electronics Bay IP54 ingress protection rating SHALL be verified by performing the IEC 60529 (Degrees of protection provided by enclosures) test method 13.4 dust wire probe and 14.2.4 water splash tests, plus fastener torque and gasket continuity inspection. Pass: no dust ingress at IP5X probe; no functional degradation after water splash; all bay fasteners at specified torque. |
| VER-VEHICLEPLATFORM-004 | verification-requirements | The Chassis Frame SHALL be verified by static load testing per ISO 7176-8: apply 1.5× (maximum user mass 130kg + electronics bay 15kg) = 217.5kg to the seat mounting points and hold for 60 seconds; no permanent deformation >1mm shall be measured at any structural member. Impact test: drop a 7kg mass from 1m height onto each corner of the chassis platform and confirm no fracture or deformation of safety-critical welds. |
| VER-VEHICLEPLATFORM-005 | verification-requirements | Verify the Electronics Bay maintains internal temperature below 70°C for all mounted electronics while dissipating up to 40W at 40°C ambient with vehicle stationary and no forced airflow. |
| VER-VEHICLEPLATFORM-006 | verification-requirements | Verify the Electronics Bay provides IP54 environmental protection per IEC 60529 (Degrees of protection provided by enclosures): (a) expose assembled unit to IP5X dust chamber per IEC 60529 Clause 13.4 for 8 hours; (b) expose to IP54 water spray per IEC 60529 Clause 14.2.4 for 5 minutes at all orientations; (c) open and re-close access panel 100 times; (d) repeat dust and water tests. Pass: no dust ingress visible on internal surfaces after step (a); no water ingress after step (b); IP54 rating maintained after 100 seal cycles in step (d). Fail: any ingress. |
| VER-VEHICLEPLATFORM-007 | verification-requirements | Verify SUB-REQ-074: Inspect the chassis frame material certificate and dimensional report. Pass: (a) material certificate confirms aluminium alloy 6061-T6 or equivalent per ISO 209 (Wrought aluminium and aluminium alloys); (b) cross-section dimensional report confirms wall thickness ≥ 3mm at all primary load-bearing members; (c) static load test to 1.5× rated occupant load (180kg) with no permanent deformation > 1mm. Fail: any non-conforming material, wall thickness < 3mm, or deformation > 1mm. |
| VER-VEHICLEPLATFORM-008 | verification-requirements | Verify SUB-REQ-072: Connect a service laptop to the Electronics Bay USB-C 3.1 Gen 1 port and execute the automated diagnostic test suite. Pass: (a) enumeration completes within 10 seconds of cable connection; (b) diagnostic API returns responses for all five test categories (motor, brake, sensor, battery, BCI pipeline) within 20 minutes; (c) test suite returns PASS/FAIL result for each subsystem with numeric values and fault codes. Fail: any test category fails to return result or API returns null. |
| VER-VEHICLEPLATFORM-009 | verification-requirements | The Electronics Bay IP54, thermal, and access-cycle durability SHALL be verified by: (a) IEC 60529 dust probe and 10-minute water spray test — Pass: no wire penetration, no functional degradation; (b) 4-hour operation at 55°C ambient at maximum component load — Pass: processor inlet temperature ≤55°C, no thermal shutdown; (c) 100 maintenance access cycles followed by re-test of (a) — Pass: IP54 rating maintained. |
| VER-VEHICLEPLATFORM-010 | verification-requirements | Verify SUB-REQ-029: Using a calibrated load test rig with adjustable torso mannequins at the extremes (40 kg/1400mm stature and 120 kg/1900mm stature): (a) Confirm backrest adjusts ≥15 degrees of recline at both occupant configurations. (b) Apply 3g forward deceleration pulse via sled test and measure lap belt restraint force — Pass: belt remains engaged, forward displacement of 50th-percentile mannequin torso ≤50mm from seated position. (c) Confirm 4-point harness buckle engages audibly and cannot be released by a single-finger pull force <20N. Fail: range below 15°, torso displacement >50mm, or buckle release <20N. |
| VER-VEHICLEPLATFORM-011 | verification-requirements | The Electronics Bay chassis mounting interface SHALL be verified by: (a) axial pull-out test at 50N/s ramp on four M6 fasteners with self-locking nuts and rubber isolators — Pass: no fastener pulls out below 500N, no isolator de-bonds below 200N; (b) 3g 11ms half-sine shock test — Pass: no isolator failure, no fastener torque loss >10%. |
| VER-VEHICLEPLATFORM-012 | verification-requirements | Verify IFC-REQ-031: (a) Test quick-release mechanism on all four wheels using a calibrated force gauge — apply force in the release direction, measure peak force for removal. Pass: all wheels release below 15N. (b) Partially engage the mechanism by stopping at mid-travel and apply 200N axial load — Pass: mechanical interlock prevents partial engagement; wheel fully locks or fully releases, no intermediate state. (c) Install all four wheels and verify positive engagement (audible click, no rotational play under 50N lateral load). Fail: release force >15N, partial engagement holds under load, or wheel rotates under lateral load. |
Acronyms & Abbreviations
| Acronym | Expansion |
|---|---|
| AC | Alternating Current |
| AES | Advanced Encryption Standard |
| AES-CCM | AES Counter with CBC-MAC (authenticated encryption mode) |
| ALS | Amyotrophic Lateral Sclerosis |
| API | Application Programming Interface |
| ARC | Architecture Decision Record |
| BCI | Brain-Computer Interface |
| BLDC | Brushless Direct Current (motor) |
| BLE | Bluetooth Low Energy |
| BMS | Battery Management System |
| BS | British Standard |
| CAN | Controller Area Network |
| CDC-ECM | Communications Device Class - Ethernet Control Model |
| CE | Conformité Européenne (EU conformity marking) |
| CFR | Code of Federal Regulations |
| CMMS | Computerised Maintenance Management System |
| COTS | Commercial Off-The-Shelf |
| CRC | Cyclic Redundancy Check |
| CSP | Common Spatial Pattern (EEG signal processing algorithm) |
| CTS | Clear To Send |
| DC | Direct Current |
| DDA | Disability Discrimination Act |
| DMA | Direct Memory Access |
| EEG | Electroencephalography |
| EMC | Electromagnetic Compatibility |
| EMG | Electromyography |
| EMI | Electromagnetic Interference |
| EU | European Union |
| FDA | Food and Drug Administration |
| GATT | Generic Attribute Profile (Bluetooth) |
| GDPR | General Data Protection Regulation |
| GPIO | General-Purpose Input/Output |
| GPS | Global Positioning System |
| HCI | Host Controller Interface (Bluetooth) |
| HFT | Hardware Fault Tolerance |
| HMI | Human-Machine Interface |
| HSE | Health and Safety Executive |
| HTTP | Hypertext Transfer Protocol |
| I2C | Inter-Integrated Circuit (serial bus protocol) |
| IEC | International Electrotechnical Commission |
| IFC | Interface |
| IP | Ingress Protection |
| IPC | Inter-Process Communication |
| ISO | International Organisation for Standardisation |
| JSON | JavaScript Object Notation |
| LED | Light-Emitting Diode |
| LESC | LE Secure Connections (Bluetooth pairing mode) |
| LTE | Long-Term Evolution (4G cellular standard) |
| MAP | Main Application Processor |
| MCU | Motor Controller Unit |
| MDR | Medical Device Regulation |
| MEMS | Micro-Electromechanical Systems |
| MHRA | Medicines and Healthcare products Regulatory Agency |
| MRI | Magnetic Resonance Imaging |
| NHS | National Health Service |
| NMC | Nickel Manganese Cobalt (lithium-ion cell chemistry) |
| NTC | Negative Temperature Coefficient (thermistor type) |
| OAuth | Open Authorisation (authorisation framework) |
| OTA | Over-The-Air (firmware update method) |
| PCB | Printed Circuit Board |
| PFD | Probability of Failure on Demand |
| PID | Proportional-Integral-Derivative (control algorithm) |
| POST | Power-On Self-Test |
| PPR | Pulses Per Revolution |
| PWM | Pulse-Width Modulation |
| RBAC | Role-Based Access Control |
| REST | Representational State Transfer |
| RGB | Red-Green-Blue (colour model) |
| RH | Relative Humidity |
| RMS | Root Mean Square |
| RTOS | Real-Time Operating System |
| RTS | Ready To Send |
| SDM | Seizure Detection Module |
| SIL | Safety Integrity Level |
| SNR | Signal-to-Noise Ratio |
| SoC | State of Charge |
| SPI | Serial Peripheral Interface |
| SPL | Sound Pressure Level |
| SSVEP | Steady-State Visual Evoked Potential (EEG paradigm) |
| STK | Stakeholder (requirements document prefix) |
| SUB | Subsystem (requirements document prefix) |
| SYS | System (requirements document prefix) |
| TLS | Transport Layer Security |
| TTL | Transistor-Transistor Logic |
| UART | Universal Asynchronous Receiver-Transmitter |
| USB | Universal Serial Bus |
| VER | Verification (requirements document prefix) |
| WGS | World Geodetic System |