Control: 5.A.1 Operations Functional Requirements Understood
| Title | Description |
Context |
Opportunity teams can lock into a single solution too soon and not explore adequately the operational context and requirements during the Assess phase. This may be caused by poor Front End Loading due to an accelerated Assess phase or not having a senior competent operations representative familiar with the asset to define the operations requirements. This control is needed to ensure that the appropriate level of Operations Readiness (OR) input is given to define the operational requirements. |
Activity |
Operations requirements and opportunities are to be included in the Minimum Technical Scope (MTS). |
Purpose |
The feasibility assessment and scope identification are based on clear operational trade-off decisions, supported by senior competent operations readiness representatives who are familiar with the final asset and its operational context. |
Requirements from other Standards |
None |
Evidence recorded in |
Feasibility Report |
Accountability for meeting Control Intent |
Front End Development Manager |
Phase |
Assess |