Systems Engineering Management (2)
Systems Engineering Management Plan (SEMP)
the development of a complex system, the act of ensuring that all the key
participants in the system development process not only know their own
responsibilities but also know how they interface with one another is referred to
as Systems Engineering Management Plan (SEMP).
Place of SEMP in program management plans
Image
SEMP can be considered to consist of three types of activity:
- Development Program Planning and Control:
describes the
systems engineering tasks that must be implemented in managing the
development program including:
statements of work
organization
technical performance measurement; and
Scheduling
risk management.
program, design, and test readiness reviews;
- Systems Engineering Process:
describes the systems engineering
process as it applies to the development of the system including:
functional analysis,
systems analysis and trade - off strategy, and
operational requirements,
system test and evaluation strategy.
- Engineering Specialty Integration:
describes how the areas of specialty
engineering are to be integrated into the primary system design and
development including:
producibility engineering;
safety engineering; and
reliability, availability and maintainability (RAM) engineering;
human factors engineering.
Risks
These are unpredictable or predictable situations that can
negatively impact on a system’s performance.
The methodology that is employed to identify and minimize risk in
system development is called risk management
The goal of every system is to minimize risks and maximize
performance
Risk Reduction through the System Life Cycle
Reducing program risks is a continual process throughout the
life cycle. For example
the concept exploration phase reduces the risk of deriving
irrelevant or unrealistic system performance requirements and
the concept definition phase selects a system concept that utilizes technical approaches that are neither excessively immature nor unaffordable, but rather one that has the best chance of meeting
all system goals.
the needs analysis phase reduces the risk of embarking on the development of a system that does not address vital operational
needs.
Variation of program risk and effort throughout system development
Image
Components of Risk Management
The Risk Management Guide divides the subject of risk
management into:
risk prioritization,
risk handling, and risk monitoring.
risk planning,
However these can be combined into two categories:
Risk assessment
Risk mitigation
risk planning and prioritization,
risk handling and monitoring.
Risk Assessment
Risk assessment is used to eliminate alternative concepts that are
dependent on
unproven technical approaches, or
other ambitious advances that do not appear to be warranted by their projected benefits compared to the uncertainty of their
realization.
immature technologies,
The seriousness of risk can be expressed as a function of its
likelihood and consequence
Risk Likelihood and Consequence chart
Risk Criticality
Image
Image
Risk Mitigation
Common methods of dealing with identified program risks:
consideration of relieving critical design requirements (complex
unyielding integration)
special analysis and testing of critical design items (components
with unresolved advanced tech
special oversight of designated component engineering
(components focused)
rapid prototyping and test feedback (unproven components)
intensified technical and management reviews of the design
(design focused)
initiation of fall back parallel developments (components with new
tech.)
Risk Likelihood
Sample Risk Plan Worksheet
Image
Image
Sample Risk Plan Worksheet
Image