Difference between revisions of "Subsystems Integrator"
Joelmartin (talk | contribs) |
Joelmartin (talk | contribs) m (→Goals) |
||
| Line 9: | Line 9: | ||
==Goals== | ==Goals== | ||
| − | + | ===Requirements Management=== | |
maintain a current and approved set of requirements | maintain a current and approved set of requirements | ||
| Line 19: | Line 19: | ||
Thoughtful analysis and management of requirements can help lay the foundation for system affordability. | Thoughtful analysis and management of requirements can help lay the foundation for system affordability. | ||
| + | |||
| + | ===Process Responsibilities=== | ||
| + | The PM should keep leadership and all stakeholders informed of cost, schedule, and performance impacts associated with requirement changes and requirements growth. | ||
| + | |||
| + | Through the Requirements Management process, the Systems Engineer tracks requirements changes and maintains traceability of end-user needs to the system performance specification and, ultimately, the delivered capability. | ||
| + | |||
| + | As the system design evolves to lower levels of detail, the Systems Engineer traces the high-level requirements down to the system elements through the lowest level of the design. | ||
| + | |||
| + | The Systems Engineer also establishes and maintains a Requirements Traceability Matrix (RTM) that captures all requirements in the system performance specification, their decomposition/ derivation and allocation history, and rationale for all entries and changes. | ||
| + | |||
| + | ===Risk Management=== | ||
| + | The Systems Engineer is responsible for prioritizing identified technical risks and developing mitigation actions. The Program Manager reviews and approves the risk priorities and mitigation plans and ensures that required resources are available to implement the mitigation plans. | ||
| + | |||
| + | Activity | ||
| + | Intent Is to Answer the Question | ||
| + | |||
| + | Risk Identification | ||
| + | |||
| + | What can go wrong? What is the future root cause? | ||
| + | |||
| + | Risk Analysis | ||
| + | |||
| + | How big is the risk? What is the probability of occurrence? What is the consequence of occurrence? | ||
| + | Risk Mitigation | ||
| + | |||
| + | What is the program approach (cost, schedule, and technical) for addressing this potential root cause or unfavorable consequence? | ||
| + | |||
| + | How can the planned risk mitigation be implemented? How do we ensure that successful risk mitigation occurs? | ||
| + | |||
| + | Risk Monitoring | ||
| + | |||
| + | How are risk management plans going? | ||
| + | |||
| + | ===Configuration Management=== | ||
| + | Configuration management is the means by which the results of the systems engineering effort are documented and tracked as changes occur. | ||
| + | |||
| + | The Configuration Management process allows technical insight into all levels of the system design and is the principal methodology for establishing and maintaining consistency of a system’s functional, performance, and physical attributes with its requirements, design, and operational information throughout the system's life cycle. | ||
| + | |||
| + | |||
| + | Configuration Management consists of five interrelated functions that, when collectively applied, allow the program to maintain consistency between product configuration information and the product throughout its life cycle. | ||
| + | |||
| + | The following are the five Configuration Management functions: | ||
| + | |||
| + | Configuration Management Planning and Management is a formal document and plan to guide the Configuration Management program that includes items such as: | ||
| + | |||
| + | Personnel | ||
| + | Responsibilities and Resources | ||
| + | Training requirements | ||
| + | Administrative meeting guidelines including a definition of procedures and tools | ||
| + | Baselining processes | ||
| + | Configuration control and Configuration status accounting | ||
| + | Naming conventions | ||
| + | Audits and Reviews | ||
| + | Configuration Identification | ||
| + | Configuration Change Management | ||
| + | Configuration Status Accounting | ||
| + | Configuration Verification and Audit | ||
==Core Competency== | ==Core Competency== | ||
Revision as of 17:00, 24 April 2020
Subsystems Integrator a.k.a The Systems Engineer
 | |||||||||||||||||||||||||||
Goals
Requirements Management
maintain a current and approved set of requirements
The Requirements Management process helps ensure delivery of capability that meets intended mission performance to the operational end user.
The end-user needs are usually identified in operational terms at the system level during implementation of the Stakeholder Requirements Definition and Requirements Analysis processes.
Robust Requirements Management, implemented in synchronization with the program’s Configuration Management process, can help the program to avoid or mitigate unintended or unanticipated consequences of changes through rigorous documentation of the system performance specification.
Thoughtful analysis and management of requirements can help lay the foundation for system affordability.
Process Responsibilities
The PM should keep leadership and all stakeholders informed of cost, schedule, and performance impacts associated with requirement changes and requirements growth.
Through the Requirements Management process, the Systems Engineer tracks requirements changes and maintains traceability of end-user needs to the system performance specification and, ultimately, the delivered capability.
As the system design evolves to lower levels of detail, the Systems Engineer traces the high-level requirements down to the system elements through the lowest level of the design.
The Systems Engineer also establishes and maintains a Requirements Traceability Matrix (RTM) that captures all requirements in the system performance specification, their decomposition/ derivation and allocation history, and rationale for all entries and changes.
Risk Management
The Systems Engineer is responsible for prioritizing identified technical risks and developing mitigation actions. The Program Manager reviews and approves the risk priorities and mitigation plans and ensures that required resources are available to implement the mitigation plans.
Activity Intent Is to Answer the Question
Risk Identification
What can go wrong? What is the future root cause?
Risk Analysis
How big is the risk? What is the probability of occurrence? What is the consequence of occurrence? Risk Mitigation
What is the program approach (cost, schedule, and technical) for addressing this potential root cause or unfavorable consequence?
How can the planned risk mitigation be implemented? How do we ensure that successful risk mitigation occurs?
Risk Monitoring
How are risk management plans going?
Configuration Management
Configuration management is the means by which the results of the systems engineering effort are documented and tracked as changes occur.
The Configuration Management process allows technical insight into all levels of the system design and is the principal methodology for establishing and maintaining consistency of a system’s functional, performance, and physical attributes with its requirements, design, and operational information throughout the system's life cycle.
Configuration Management consists of five interrelated functions that, when collectively applied, allow the program to maintain consistency between product configuration information and the product throughout its life cycle.
The following are the five Configuration Management functions:
Configuration Management Planning and Management is a formal document and plan to guide the Configuration Management program that includes items such as:
Personnel Responsibilities and Resources Training requirements Administrative meeting guidelines including a definition of procedures and tools Baselining processes Configuration control and Configuration status accounting Naming conventions Audits and Reviews Configuration Identification Configuration Change Management Configuration Status Accounting Configuration Verification and Audit
Core Competency
- Create Direction, Alignment and Commitment
- Critical thinking and problem solving
- Excels at decision-making
- Primary Leadership and Planning (leader of leaders)
- Leads Conflict resolution
- High Degree of Adaptability
- Stress Tolerant
- Engages in contract negotiation
Technical Assessment responsibilities
Establish event-driven technical planning Identify appropriate measures and metrics Identify performance measures to assess program health and technical progress Conduct analyses to determine risk and to develop risk mitigation strategies Conduct assessments of technical maturity, process health and stability, and risk to communicate progress to stakeholders and authorities at key decision points Propose changes in the technical approach to address risk mitigation activities Advise the PM regarding the technical readiness of the program to proceed to the next phase of effort Obtain independent subject matter experts as appropriate for reviews and audits
Primary Roles and Responsibilities
Plan and implement the RobotX project
Integration Plan
The PM and SE are responsible for planning, managing, and executing the Integration process.
Programs that develop an integration plan are more successful.
This plan defines the stages of integration, during which system elements are successively integrated to form higher level elements, and eventually the finished product.
The integration plan should include a description of the required teams, test standards, testing methods, and integration schedule.