Arc Skills / Technical management and design reviews
Prepare an operational readiness review
Use Arc Skills to prepare an operational readiness review for a deployed system and its support organization. The packet checks whether operators can perform normal service, respond to faults and maintain the approved configuration using tested procedures and available resources.
Use this skill
Use Arc Skills to prepare an operational readiness review.
Inputs:
- Installed configuration and operational baseline
- Validated nominal, degraded and recovery scenarios
- Procedures, training, support resources, deviations and review criteria
Return an ORR readiness matrix and operational constraints with evidence, owner and authority. Distinguish delivery acceptance, completed tests and readiness of the full operating organization.What you provide and what you get
| What you have | How it is used | What you get |
|---|---|---|
| Installed system and operational baseline | Check what is entering service | Configuration and deviation findings |
| Scenario validation and procedures | Check real operator workflows | Normal, fault and recovery coverage |
| Training and support evidence | Check organizational readiness | An evidence-backed ORR packet |
The system passed its tests, but the night shift has no recovery procedure
Illustrative engineering example.
A monitoring station has passed its product tests and been installed. ORR evidence must also address the deployed configuration and people who will operate it.
Installed: station HW-B, firmware F5; acceptance report used F4.
Nominal startup validated with day shift. Alarm recovery procedure OPS-9 still draft.
Night shift training covers startup only. Critical spare converter absent.
A known sensor deviation has no recorded operational limit or authorized residual-risk decision.| Review question | Available evidence | Finding | Required action / owner |
|---|---|---|---|
| Deployed configuration | HW-B / F5 versus F4 acceptance evidence | Applicability to installed firmware unresolved | Configuration owner assesses delta and required validation |
| Normal operation | Day-shift startup demonstration | Evidence covers that scenario and trained group | Operations owner checks remaining roles, modes and duty periods |
| Alarm and recovery | OPS-9 draft; night shift untrained for recovery | Fault-response readiness gap | Validate procedure and demonstrate recovery with assigned operators |
| Maintenance support | Critical spare converter absent | Recovery-resource assumption not met | Support owner resolves spare or approves a bounded operating constraint |
| Residual deviation | Known sensor departure; no disposition/limit | Operational use decision unresolved | Authorized owner records acceptability and applicable constraints |
Acceptance testing supplies product evidence. ORR additionally checks the deployed version, procedures, trained staff and support resources against real operating scenarios.
The day-shift startup result remains useful within its scope. It cannot stand in for night-shift recovery or validate a later firmware configuration. The packet names these handoffs so the review decision can be specific.
Walk the operating organization through real scenarios
- Compare installed equipment, software, data and interfaces with the approved operational baseline.
- Walk startup, routine service, alarms, degraded operation, maintenance and shutdown.
- Check procedure validation, assigned staff, training and support resources for each scenario.
- Carry residual risks and deviations into explicit operating limits and authorized decisions.
Questions about this task
Is delivery acceptance the same as operational readiness?
No. Accepted hardware may still lack trained operators, validated recovery procedures, deployed-configuration evidence or required support resources. Review the complete operating situation.
Sources and further reading
- NASA NPR 7123.1D, Appendix G: life-cycle review criteria: A NASA reference for different review purposes. Use your project’s governing review criteria.
- NASA Systems Engineering Handbook: technical assessment: Background on measures, review evidence and action resolution.
References inspected on 3 October 2026. The worked output is an authored example using the stated inputs.