System Operation

The role of systems engineering (SE) during the operation of the system consists of ensuring that the system maintains key mission and business functions and is operationally effective; that maintenance actions and other major changes are performed according to the long-term vision of the system, meet the evolving needs of stakeholders, and are consistent with the architecture; and that the eventual decommissioning or disposal of the system occurs according to disposal/retirement plans that are compliant with relevant laws and regulations (for additional information on disposal or retirement, please see the System Life Cycle Management Knowledge Area (KA)). When the system of interest (soi) replaces an existing or legacy system, it may be necessary to manage the migration between systems such that persistent stakeholders do not experience a breakdown in services (INCOSE 2010, 145).

Definition & Purpose

During operations the Systems Engineering (SE) function provides a critical role to ensure that the system maintains key mission and business functions within design parameters. The Operational Availability (Ao) provides the target that is impacted both unplanned and planned maintenance during operations phases. The impact of maintenance actions and Ao measurement and analysis is addressed further in “Maintenance of the System” Knowledge Area. This process assigns personnel to operate the system and monitors the services and operator‐system performance. In order to sustain services, it identifies and analyzes operational problems in relation to agreements, stakeholder requirements, and organizational constraints (ISO/IEC 2009, 1).

Process Approaches

During the operational phase, SE activities ensure the system maintains certain operational attributes and usefulness throughout its expected life span. Maintaining operational effectiveness consists of evaluating certain operationally relevant attributes and trends, taking actions to prevent degradation of performance (see 11.4 Maintenance, below), evolving the system to meet changing mission or business needs (see the System Life Management KA), and eventually decommissioning the system and disposing of its components (see the System Life Management KA). Several activities are specifically associated with system use, including:

• Development of training requirements for operational and support personnel. Identification of training requirements is generally most effective when they are developed early and fulfilled consistently with operational or support needs before system transition.

• Evaluation of the readiness of the operational and support personnel to operate and assume support responsibility for the system. Evaluation of personnel readiness may include completion of required training or demonstration of capability to operate or support the system.

• Evaluation of operational effectiveness. Early in the planning phases of a new system or capability, measures of operational effectiveness are established based on mission and business goals. These measures are equally important during system operation. These attributes are unique for each system and represent characteristics describing the usefulness of the system as defined and agreed to by system stakeholders. Systems engineers monitor and analyze these measurements and recommend actions.

Applicable Methods & Tools

• Training and Certification. Adequate training must be provided for the operators who are required to operate the system. The objectives of training are to:
  • Provide initial training for all operators in order to equip them with the skill and knowledge to operate the system. Ideally, this process will begin prior to system transition and will facilitate delivery of the system. It is important to define the certification standards and required training materials up front (for more information on material supply, please see Logistics).
  • Provide continuation training to ensure currency of knowledge.
  • Monitor the qualification/certification of the operators to ensure that all personnel operating the system meet the minimum skill requirements and that their currency remains valid.
  • Monitor and evaluate the job performance to determine the adequacy of the training program.

Practical Consideration

The operation process sustains system services by assigning trained personnel to operate the system, as well as by monitoring operator-system performance and monitoring the system performance. In order to sustain services, the operation process identifies and analyzes operational problems in relation to agreements, stakeholder requirements, and organizational constraints. When the system replaces an existing system, it may be necessary to manage the migration between systems such that persistent stakeholders do not experience a breakdown in services.

As a result of the successful implementation of the operation process:

• An operation strategy is defined and refined along the way.
• Services that meet stakeholder requirements are delivered.
• Approved, corrective action requests are satisfactorily completed.
• Stakeholder satisfaction is maintained.

Outputs of the operation process include:

• Operational strategy, including staffing and sustainment of enabling systems and materials. This may incorporate the strategy first defined during the transition process.
• System performance reports (statistics, usage data, and operational cost data).
• System trouble/anomaly reports with recommendations for appropriate action.
• Operational availability constraints to influence future design and specification of similar systems or reused systems-elements

Activities of the operation process include:

• Provide operator training to sustain a pool of operators.
• Track system performance and account for operational availability.
• Perform operational analysis.
• Manage operational support logistics.
• Document system status and actions taken.
• Report malfunctions and recommendations for improvement.

References

This article relies heavily on limited sources. Reviewers are requested to identify additional sources.

Citations

None.

Primary References

Blanchard, B.S. and Fabrycky, W.J. 2011. Systems Engineering and Analysis. 5th Edition. Englewood Cliffs, NJ, USA:Prentice Hall.

Institute of Engineers Singapore. 2009. Systems Engineering Body of Knowledge. Provisional version 2.0. Singapore: Institute of Engineers Singapore.

INCOSE. 2011. INCOSE Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities. Version 3.2.1. San Diego, CA, USA: International Council on Systems Engineering (INCOSE), INCOSE-TP-2003-002-03.2.1.

ISO/IEC/IEEE. 2008. Systems and Software Engineering - System Life Cycle Processes. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electronical Commission (IEC), Institute of Electrical and Electronics Engineers. ISO/IEC/IEEE 15288:2008 (E).

Author. Date. Title. City: Publisher.

Additional References

No additional references have been identified for version 0.5. Please provide any recommendations on additional references in your review.

---

<- Previous Article | Parent Article | Next Article ->