Systems Engineering Competencies

ACADEMY OF PROGRAM/PROJECT & ENGINEERING LEADERSHIP
NASA’s Systems Engineering

Competencies
1
Systems Engineering Competencies*

Competency Area: Competency Area:
1.0 Concepts and Architecture 6.0 NASA Internal and External Environments
1.1 Mission Needs Statement 6.1 Agency Structure, Mission, and Internal Goals
1.2 System Environments 6.2 NASA PM/SE Procedures and Guidelines
1.3 Trade Studies 6.3 External Relationships
1.4 System Architecture
2.0 System Design 7.0 Human Capital Management
2.1 Stakeholder Expectation Definition & Management 7.1 Technical Staffing and Performance
2.2 Technical Requirements Definition 7.2 Team Dynamics and Management
2.3 Logical Decomposition
2.4 Design Solution Definition
3.0 Production, Product Transition, Operations 8.0 Security, Safety and Mission Assurance
3.1 Product Implementation 8.1 Security
3.2 Product Integration 8.2 Safety and Mission Assurance
3.3 Product Verification
3.4 Product Validation
3.5 Product Transition
3.6 Operations
4.0 Technical Management 9.0 Professional and Leadership Development
4.1 Technical Planning 9.1 Mentoring and Coaching
4.2 Requirements Management 9.2 Communication
4.3 Interface Management 9.3 Leadership
4.4 Technical Risk Management
4.5 Configuration Management
4.6 Technical Data Management
4.7 Technical Assessment
4.8 Technical Decision Analysis
5.0 Project Management and Control 10.0 Knowledge Management
5.1 Acquisition Strategies and Procurement 10.1 Knowledge Capture and Transfer
5.2 Resource Management
5.3 Contract Management
5.4 Systems Engineering Management
2
Description of Proficiency Levels Associated with the APPEL Model for Systems Engineers
To determine how best to proceed after entering the NASA workforce and progress through the technical professional development model,
it is helpful to understand the definition of each level. The following table is intended as a guide for use with the technical development
model for systems engineers.
SE Proficiency Level I SE Proficiency Level II SE Proficiency Level III SE Proficiency Level IV
Engineering Technical Engineer / Project Subsystem Lead Project Systems Engineer Program Systems Engineer or
Leadership Team Member Center/Agency
Performs fundamental and Performs SE activities for a Performs as a systems Oversees SE activities for a
Description of routine SE activities while subsystem or simple project engineer for a complex project program with several systems
Role/ supporting a Level II-IV (e.g. no more than two simple (e.g. several distinct and/or establishes SE policies
Responsibility systems engineer as a internal/external interfaces, subsystems or other defined at the Agency or Center level.
member of a project team simpler contracting processes, services, capabilities, or
smaller team/budget, shorter products and their associated
duration) interfaces)
Practitioners have obtained a Practitioners participated in or Practitioners have taken a Practitioners will have
working knowledge of technical led SE activities (e.g. significant leadership role in contributed to Agency goals
integration, systems requirements development, multiple phases of a project life and be effective in managing
engineering (SE) and project budget and schedule cycle managing both programmatic, technical, and
management (PM) concepts development, risk programmatic and technical strategic interfaces both
and tools and performed tasks management). They aspects and/or managing all internal and external to the
Level of and activities to support and demonstrated the application technical integration and SE Agency. They demonstrated
Expertise contribute to a project. They of SE/PM tools, techniques, functions for a subsystem or superior competencies in all
(LEO)/ demonstrated an awareness and lexicon at the project small project. They Systems Engineering
Competency and understanding of NASA's subsystem level, including use demonstrated the integration of formulation and
to Attain SE and PM tools, techniques, of SE/PM best practices. They SE/PM tools, techniques, and implementation activities.
Proficiency and lexicon. They have have sufficient experience and best practices across They have sufficient
Level sufficient experience and responsibility and are prepared subsystems at the project experience and responsibility
responsibility and are prepared to lead SE and technical level. They have sufficient and are prepared for a
to contribute to fundamental integration activities for a experience and responsibility technical leadership role at the
and routine SE activities. subsystem or simple project. and are prepared for a program, center, or agency
technical leadership role in level.
support of a major system or
project
Validation of Practitioner’s immediate Center Peer Group and EDP Center Peer Group and EDP Center Peer Group, EDP and
Levels supervisor panel panel Agency-wide panels
The emphasis at Level I is The emphasis at Level II is The emphasis at Level III is the The emphasis at Level IV is on
Learning and knowledge and understanding leadership application and directing, structuring, and the strategy for SE of large
Development of technical integration, SE and participation in SE. integration activities of SE. complex initiatives and the
emphasis basic project management. strategy and management of
Agency initiatives.
3
Structure of the Systems Engineering Competency Framework
The SE Competencies are structured as follows:
1) Competency Areas: These describe, in broad terms, what is expected of Systems Engineer personnel in terms of
particular components or functions of the job.
2) Competencies: These express the overall knowledge, skills, behaviors that SEs are expected to posses and/or perform
as a part of their job.
3) Competency Elements: Each Competency Area and Competency consists of Competency Elements that describe the
specific knowledge, skills, behaviors, which can be measured against established standards, can be improved via
training and development activities, and correlate to performance on the job.
4) Proficiency Level Descriptions: These specify the knowledge/performance to be achieved in order to demonstrate
successful mastery of the competency and are expressed in terms of levels.
5) HQ courses, Center courses, OJL activities, Other learning activities, Assessment Guidelines: These outline the
required/suggested courses and activities to obtain proficiency in the competencies by level. The Assessment
Guidelines indicate the evaluation and/or assessment of the competencies by level and are used as entry/exit criteria
for each level of development.
6) The Competency framework is hierarchal and the numbering scheme is as follows:
Competency Area – #.0
Competency – #.# – the first number indicates the Competency Area the competency falls into, the second is the
Competency number
Competency Element - #.#.# - the first and second numbers indicate the Competency Area and
Competency, respectively, that the Element is related to, the third is the particular Element number
4
Competency Area: 1.0 Concepts and Architecture
Competency: 1.1 Mission Needs Statement

Competency Elements Proficiency Level Descriptions
and Descriptions Level 1 Level 2 Level 3 Level 4
1.1.1 Mission Need Aware that projects start with Able to (for a subsystem or Able to (for a system): Able to (for a program):
a. Identify need users having an unsatisfied simple project): • Identify the users • Identify the users
b. Identify basis of need need • Identify the users • Distinguish between what • Distinguish between what
• Distinguish between what the users want and what the the users want and what the
the users want and what the users need users need
users need
1.1.2 Current Situation Contribute to definition of the Able to (for a subsystem or Able to (for a system) describe Able to (for a program)
a. Describe current current situation to include simple project) describe the the current situation to include: describe the current situation to
situation what does and doesn’t work current situation to include • What does and doesn’t work include:
what does and doesn’t work • What has and hasn’t worked • What does and doesn’t work
b. Identify deficiencies of
in similar projects • What has and hasn’t worked
situation in similar programs
c. Identify what works in
current situation
1.1.3 Mission Needs Contribute to preparation of Able to (for a subsystem or Able to (for a system) create Able to (for a program) create
Statement Formulation the mission needs statement simple project): consensus regarding the consensus regarding the
• Create consensus regarding problem definition problem definition
a. Get agreement on
the problem definition
problem definition • Describe, identify or define Direct (for a system): Direct (for a program):
b. Define desired outcomes desired outcomes and • Description, identification or • Description, identification or
c. Define success criteria success criteria definition of desired definition of desired
d. Document Need • Write a mission needs outcomes and success outcomes and success
statement criteria criteria
• Drafting of a mission needs • Drafting of a mission needs
statement statement
HQ courses
Center courses
OJL activities
Other learning activities
Assessment
5
Competency: 1.2 System Environments

1.2.1 System Involved in identifying Able to (for a subsystem or Direct (for a system): Direct(for a program):
Environment constraints and the expected simple project): • Identification of constraints • Identification of constraints
system environment • Identify constraints • Identification of expected • Identification of expected
Identification • Identify expected system system environment system environment
a. Identify constraints Able to analyze/quantify environment • Analysis/quantification of • Analysis/quantification of
b. Identify expected system expected environment • Analyze/quantify expected expected environment expected environment
environment environment
c. Analyze/quantify
expected environment
1.2.2 Design Guidance Understand the purpose of Apply (for a subsystem or Establish (for a system): Establish (for a program):
a. Establish margin having a margin philosophy simple project): • Margin philosophy against • Margin philosophy against
philosophy against the against the expected • Margin philosophy against the expected environment the expected environment
expected environment
environment and how that the expected environment • Design guidance • Design guidance
leads to design guidance • Design guidance
b. Establish design Define Agency/Center design
guidance for the Apply provided design guidance policies
expected environment guidance
HQ courses
Center courses
OJL activities
Assessment
6
Competency: 1.3 Trade Studies

1.3.1 Concept Definition Contribute to definition of Able to define (for a Direct (for a system): Direct (for a program):
a. Define scope options scope options subsystem or simple project): • Definition of scope options • Definition of scope options
b. Define operations • Scope options • Definition of technical • Definition of technical
concept
Understand the need for an • Technical solution options solution options solution options
operations concept early in the • Development of the • Development of the
c. Define technical solution project Contribute to (for a subsystem operations concept operations concept
options or simple project) development
of the operations concept
1.3.2 System Model Contribute to: Able to (for a subsystem or Direct (for a system): Direct (for a program):
a. Create system model • Creation of system model simple project): • Creation, validation, and • Creation, validation, and
b. Validate system model • Validation of system model • Create, validate, and operate operation a system model operation a system model
c. Operate system model • Correlation of system model a system model • Correlation of system model • Correlation of system model
with operational data • Correlate a system model with operational data with operational data
d. Correlate system model with operational data
with operational data Able to operate a system
model
1.3.3 System Contribute to: Able to (for a subsystem or Direct (for a system): Direct (for a program):
Performance • Evaluation of possible simple project): • Evaluation of possible • Evaluation of possible
concepts • Evaluate possible concepts concepts concepts
a. Evaluate possible
• Recommendation of a • Recommend a technical • Selection of a technical • Selection of a technical
concepts technical solution that solution that balances solution that balances solution that balances
b. Select technical solution balances technical and non technical and non technical technical and non technical technical and non technical
technical features of the features of the system features of the system features of the system
system
HQ courses
Center courses
OJL activities
Assessment
7
Competency: 1.4 System Architecture

1.4.1 Functional Aware that overall architecture Able to (for a subsystem or Direct (for a system): Direct (for a program):
Analysis can be broken into functional simple project): • Identification of system • Identification of system
segments • Identify system boundaries boundaries including external boundaries including external
a. Establish system
including external interfaces interfaces interfaces
boundaries Able to analyze functional • Segment an architecture into • Segmentation of an • Segmentation of an
b. Define architecture performance of at least one functions architecture into functions architecture into functions
functions segment of the architecture • Analyze functional • Functional analysis of all • Functional analysis of all
c. Analyze architecture performance of multiple systems architecture systems architecture
functional performance segments segments segments
1.4.2 Subsystem Aware that architecture Able to define (for a Direct definition of (for a Direct definition of (for a
Mapping functions become subsystems subsystem or simple project): system): program):
• Subsystems from the • Subsystems from the • Subsystems from the
a. Map architecture Contribute to: architecture functions architecture functions architecture functions
functions to subsystems • Definition of subsystem • Subsystem relationships • Subsystem relationships • Subsystem relationships
b. Define subsystem relationships • Internal interfaces • Internal interfaces • Internal interfaces
relationships • Identification of internal
c. Identify internal interfaces
interfaces
1.4.3 Systems Contribute to documentation Participate in documentation Able to (for a system) Direct (for a program)
Architecture of systems architecture of the systems architecture document systems architecture documentation of systems
architecture
Documentation
a. Document the systems
architecture
HQ courses
Center courses
OJL activities
Assessment
8
Competency Area: 2.0 System Design
Competency: 2.1 Stakeholder Expectation Definition & Management

2.1.1 Stakeholder Aware that stakeholders must Able to (for a subsystem or Able to (for a system) identify Able to identify program
Identification be involved early in the project simple project) identify project project stakeholders stakeholders
lifecycle stakeholders
a. Identify all stakeholders
2.1.2 Stakeholder Contribute to: Contribute to (for a subsystem Direct (for a system): Direct (for a program):
Expectation Definition • Translation of stakeholder or simple project) obtaining • Obtaining of stakeholder • Obtaining of stakeholder
expectations into acceptable stakeholder expectations expectations expectations
a. Elicit stakeholder
statements • Translation of stakeholder • Translation of stakeholder
expectations • Creation of MOEs from Able to (for a subsystem or expectations into acceptable expectations into acceptable
b. Define stakeholder stakeholder expectation simple project): statements statements
expectation in statements • Translate stakeholder • Creation of MOEs from • Creation of MOEs from
acceptable statements expectations into acceptable stakeholder expectation stakeholder expectation
c. Generate MOEs from statements statements statements
stakeholder expectation • Create MOEs from
statements stakeholder expectation
statements
2.1.3 Stakeholder Contribute to: Able to (for a subsystem or Direct (for a system): Direct (for a program):
Expectation Validation • Validation of stakeholder simple project): • Validation of stakeholder • Validation of stakeholder
expectations statements • Validate stakeholder expectations statements expectations statements
a. Validate traceability of
• Baselining of stakeholder expectations statements • Baselining of stakeholder • Generation of baselined
defined stakeholder expectations • Baseline stakeholder expectations stakeholder expectations
expectation statements expectations
b. Obtain stakeholder buy- Aware that stakeholder buy-in Able to (for a system) obtain Able to (for a program) obtain
in of validated set of must be obtained Contribute to (for a subsystem stakeholder buy-in of validated stakeholder buy-in of validated
expectations or simple project) obtaining expectations expectations
c. Baseline stakeholder stakeholder buy-in of validated
expectations expectations
2.1.4 Stakeholder Aware that stakeholders Participate in management of Able to (for a system) manage Able to (for a program)
Expectation expectations must be managed stakeholders expectations stakeholders expectations manage stakeholders
throughout the project lifecycle throughout the project lifecycle throughout the project lifecycle expectations throughout the
Management project lifecycle
a. Manage expectations of
stakeholders Define Agency/Center
stakeholder expectation
management policies
HQ courses
Center courses
OJL activities
9
Assessment
10
Competency: 2.2 Technical Requirements Definition

2.2.1 Requirements Aware that Aware of technology Aware of technology Aware of technology
Scope • Design cannot begin until developments developments developments
technical scope has been
a. Analyze scope of the Contribute to (for a Able to define (for a system): Able to define:
defined
technical problem • Design and product subsystem or simple project) • Technical problem scope • Technical problem scope (for
b. Define design and constraints will impact the definition of: • Design and product a program)
product constraints product • Technical problem scope constraints • Design and product
• Design and product constraints (for
constraints Agency/Center)
2.2.2 Conversion from Contribute to: Able to (for a subsystem or Direct (for a system): Direct (for a program):
Expectations to • Conversion of functional and simple project): • Conversion of functional and • Conversion of functional and
behavioral expectations into • Convert functional and behavioral expectations into behavioral expectations into
Requirements technical terms with behavioral expectations into technical terms with technical terms with
a. Define functional and performance requirements technical terms with performance requirements performance requirements
behavioral expectations • Expression of technical performance requirements • Expression of technical • Expression of technical
in acceptable technical requirements in an • Express technical requirements in an requirements in an
terms acceptable form requirements in an acceptable form acceptable form
b. Define the performance acceptable form
requirements for each
defined functional and
behavioral expectation
c. Define technical
requirements in
acceptable “shall”
statements
2.2.3 Conversion from Contribute to definition of Able to (for a subsystem or Direct (for a system) definition Direct (for a program)
Requirements to MOPs and TPMs simple project) define MOPs of MOPs and TPMs definition of MOPs and TPMs
and TPMs
Technical Performance
Measures
a. Define measures of
performance (MOPs) for
each measure of
effectiveness (MOE)
b. Define technical
performance measures
(TPMs)
11
2.2.4 Requirements Contribute to: Able to (for a subsystem or Direct (for a system): Direct (for a program):
Documentation • Validation of requirements simple project) validate • Validation of requirements • Validation of requirements
a. Validate the technical • Development of specification requirements • Development of specification • Development of specification
doc. doc. doc.
requirements Contribute to (for a subsystem
b. Baseline technical or simple project) development Define Agency/Center
requirements of specification doc. technical requirements
definition policies
HQ courses
Center courses
OJL activities
Assessment
12
Competency: 2.3 Logical Decomposition

2.3.1 Requirements Flow Contribute to: Able to (for a subsystem or Direct (for a system): Direct (for a program):
a. Decompose • Decomposition of simple project): • Decomposition of • Decomposition of
requirements requirements • Decompose requirements requirements requirements
b. Allocate requirements • Allocation of requirements • Allocate requirements • Allocation of requirements • Allocation of requirements
• Identification and resolution • Identify and resolve • Identification and resolution • Identification and resolution
c. Resolve derived
of requirements conflicts requirements conflicts of requirements conflicts of requirements conflicts
requirements conflicts
2.3.2 Derived Contribute to: Able to (for a subsystem or Direct (for a system): Direct (for a program):
Requirements • Validation of derived simple project): • Validation of derived • Validation of derived
requirements • Validate derived requirements requirements
Documentation • Development of specification requirements • Development of specification • Development of specification
a. Validate derived document • Develop specification document document
requirements document
b. Baseline derived Define Agency/Center logical
requirements decomposition policies
HQ courses
Center courses
OJL activities
Assessment
13
Competency: 2.4 Design Solution Definition

2.4.1 Alternative Contribute to: Able to (for a subsystem or Direct (for a system): Direct (for a program):
Designs • Definition of alternative simple project): • Definition of alternative • Definition of alternative
design solutions • Define alternative design design solutions design solutions
a. Define alternative design
• Evaluation of alternative solutions • Evaluation of alternative • Evaluation of alternative
solutions design solutions • Evaluate alternative design design solutions design solutions
b. Analyze alternative solutions
design solutions Able to recommend best • Recommend best design Able to (for a system) select Able to (for a program) select
c. Select best design design solution solution best design solution best design solution
solution alternative
2.4.2 Design Solution Contribute to: Able to (for a subsystem or Direct (for a system): Direct (for a program):
Documentation • Generation of full design simple project): • Generation of full design • Generation of full design
description • Generate full design description description
a. Generate full design
• Verification of the design description • Verification of the design • Verification of the design
description solution • Verify the design solution solution solution
b. Verify design solution • Baselining of selected design • Baseline selected design • Baselining of selected design • Baselining of selected design
c. Baseline selected design solution solution solution solution
solution
Define Agency/Center design
solution policies
HQ courses
Center courses
OJL activities
Assessment
14
Competency Area: 3.0 Product, Product Transition, Operations
Competency: 3.1 Product Implementation

3.1.1 Product Aware that product Contribute to (for a subsystem Ensure (for a system): Ensure (for a program):
Implementation implementation requires or simple project): • Acquisition or development • Acquisition or development
enabling products and lower • Acquisition or development of enabling products of enabling products
Preparation level products of enabling products • Development of next lower- • Development of next lower-
a. Begin enabling product • Development of next lower- level products level products
development or Contribute to review of level products • Readiness of existing • Readiness of existing
acquisition existing product configuration • Readiness of existing product configuration product configuration
b. Begin development of documentation product configuration documentation documentation
next lower-level products documentation
c. Prepare product • Development of the product Develop (for a system) the Direct (for a program)
implementation strategy implementation strategy product implementation development of the product
d. Review existing product strategy implementation strategy
configuration
documentation
3.1.2 Product Purchase Contribute to product Able to (for a subsystem or Direct (for a system) SE Direct (for a program) SE
a. Review product technical purchase by: simple project) provide SE participation in the product participation in the product
information • Reviewing product technical participation in the product purchase: purchase:
information purchase: • Review of product technical • Review of product technical
b. Prepare vendor requests
• Assisting product inspection • Review of product technical information information
c. Assist product inspection • Preparation of vendor • Preparation of vendor
• Assessing product validation information
d. Assess product status • Assess product validation requests requests
validation status • Assessing enabling product status • Product inspection • Assisting product inspection
e. Assess enabling product status • Assess enabling product • Assessment of product • Assessment of product
status status validation status validation status
• Assessment of enabling • Assessment of enabling
Contribute to (for a subsystem product status product status
or simple project) SE
participation in the product
purchase:
• Preparation of vendor
requests
• Product inspection
3.1.3 Product Contribute to product Able to (for a subsystem or Direct (for a system) SE Direct (for a program) SE
Fabrication fabrication by: simple project) provide SE participation in product participation in product
• Enabling products status participation in product fabrication: fabrication:
a. Evaluate readiness of
assessment fabrication: • Assessment of enabling • Assessment of enabling
implementation of • Product fabrication • Assess enabling products products status products status
enabling products monitoring status • Monitoring product • Monitoring product
15
b. Fabricate product • Support documentation • Monitor product fabrication fabrication fabrication
c. Prepare support preparation • Preparing support • Preparing support
documentation Contribute to (for a subsystem documentation documentation
or simple project) preparation
of support documentation
3.1.4 Product Reuse Contribute to acquiring the Able to (for a subsystem or Direct (for a system) SE Direct (for a program) SE
a. Review product technical product for reuse by: simple project) provide SE participation in acquiring the participation in acquiring the
information • Reviewing product technical participation in acquiring the product for reuse by: product for reuse by:
information product for reuse by: • Review of product technical • Review of product technical
b. Assess supporting
• Assessing status of • Review of product technical information information
documentation status supporting documentation information • Assessment of supporting • Assessment of supporting
c. Assess enabling product and user manuals • Assessment of supporting documentation and user documentation and user
status • Assessing enabling products documentation and user manuals status manuals status
d. Assist in requests to status manuals status • Assessment of enabling • Assessment of enabling
acquire the product from • Assisting in requests to • Assessment of enabling products status products status
Government source acquire the product from products status • Assisting in requests to • Assisting in requests to
e. Assist in product Government sources • Assisting in requests to acquire the product from acquire the product from
inspection • Assisting product inspection acquire the product from Government sources Government sources
Government sources • Product inspection • Assisting product inspection
• Product inspection
3.1.5 Product Contribute to capture of work Participate in capture of work Direct (for a system) capture of Direct (for a program) capture
Implementation products from product products from product work products from product of work products from product
implementation activities implementation activities implementation activities implementation activities
Documentation
a. Capture product Define Agency/Center product
implementation work implementation policies
products
HQ courses
Center courses
OJL activities
Assessment
16
Competency: 3.2 Product Integration

3.2.1 Product Integration Understand integration Contribute to (for a subsystem Develop (for a system) the Direct (for a program)
Preparation preparation or simple project) development product integration strategy development of:
of: • Product integration strategy
a. Prepare product
• Product integration strategy Direct (for a system) • Detailed planning for
integration strategy • Detailed planning for development of: integration
b. Review existing product integration • Detailed planning for • Integration sequence and
configuration • Integration sequence and integration procedures
documentation procedures • Integration sequence and
procedures Ensure (for a program) existing
Ensure (for a subsystem or product configuration
simple project) existing product Ensure (for a system) existing documentation will permit
configuration documentation product configuration product integration
will permit product integration documentation will permit
product integration
3.2.2 Lower Level Aware that lower level Ensure (for a subsystem or Ensure (for a system) lower Ensure (for a program) lower
Product Procurement products must be obtained and simple project) lower level level products are in place and level products are in place and
validated products are in place and have have been validated have been validated
a. Obtain lower level been validated
products
b. Confirm received
products have been
validated
3.2.3 Product Assembly Aware of process to prepare Ensure (for a subsystem or Ensure (for a system) Ensure (for a program)
a. Prepare integration integration environment simple project) readiness of: readiness of: readiness of:
environment • Product integration enabling • Product integration enabling • Product integration enabling
Contribute to assembly and products products products
b. Assemble and integrate integration • Product integration workforce • Product integration workforce • Product integration workforce
the received products
Participate in (for a subsystem Direct (for a system) assembly Direct (for a program)
or simple project) assembly and integration of received assembly and integration of
and integration of received products received products
products
3.2.4 Product Integration Contribute to capture of work Participate in capture of work Direct (for a system) capture of Direct (for a program) capture
Documentation products and related products and related work products and related of work products and related
information from product information from product information from product information from product
a. Prepare product support integration activities integration activities integration activities integration activities
documentation
b. Capture product Define Agency/Center product
integration work integration policies
17
products
HQ courses
Center courses
OJL activities
Assessment
18
Competency: 3.3 Product Verification

3.3.1 Product Aware of steps to prepare for Review (for a subsystem or Review (for a system) product Review (for a program) product
Verification Preparation product verification simple project) product verification plan verification plan
verification plan
a. Prepare to conduct Ensure (for a system): Ensure (for a program):
product verification Contribute to (for a subsystem • Product verification enabling • Product verification enabling
or simple project): products are obtained products are obtained
• Obtaining product verification • Specification and • Specification and
enabling products configuration baseline configuration baseline
• Obtaining specification and against which the verification against which the verification
configuration baseline is to be made are obtained is to be made are obtained
against which the verification • Readiness of verification • Readiness of verification
is to be made environment environment
• Readiness of verification
environment
3.3.2 Product Contribute to: Participate in (for a subsystem Direct (for a system): Direct (for a program):
Verification Execution • Product verification or simple project): • Product verification • Product verification
• Analysis of product • Product verification • Analysis of product • Analysis of product
a. Perform product
verification outcomes • Analysis of product verification outcomes verification outcomes
verification verification outcomes • Identification of anomalies • Identification of anomalies
b. Analyze product Able to: • Identification of anomalies and corrective action and corrective action
verification outcomes • Identify verification and corrective action recommendations recommendations
anomalies or conformance recommendations
Able to (for a system): Able to (for a system):
Establish (for a subsystem or • Establish product • Establish product
simple project): product conformance or conformance or
conformance • Select corrective action • Select corrective action
3.3.3 Product Contribute to: Participate in: Direct (for a system): Direct (for a program):
Verification • Preparation of product • Preparation of product • Preparation of product • Preparation of product
verification report verification report verification report verification report
Documentation • Capture of work products • Capture of work products • Capture of work products • Capture of work products
a. Prepare product and related information from and related information from and related information from and related information from
verification report product verification activities product verification activities product verification activities product verification activities
b. Capture product
verification work Define Agency/Center product
products verification policies
HQ courses
Center courses
19
OJL activities
Assessment
20
Competency: 3.4 Product Validation

3.4.1 Product Validation Aware of steps to prepare for Review (for a subsystem or Review (for a system) product Review (for a program) product
Preparation product validation simple project) product validation plan validation plan
validation plan
a. Prepare to conduct Ensure (for a system): Ensure (for a program):
product validation Contribute to (for a subsystem • Product validation enabling • Product validation enabling
or simple project): products are obtained products are obtained
• Obtaining product validation • Getting the end product to be • Getting the end product to be
enabling products validated in place validated in place
• Getting the end product to be • Stakeholder expectations • Stakeholder expectations
validated in place baseline against which the baseline against which the
• Obtaining stakeholder validation is to be made is validation is to be made is
expectations baseline obtained obtained
against which the validation • Readiness of validation • Readiness of validation
is to be made environment environment
• Readiness of validation
environment
3.4.2 Product Validation Contribute to: Participate in (for a subsystem Direct (for a system): Direct (for a program):
Execution • Execution of product or simple project): • Product validation • Product validation
validation • Product validation • Analysis of product validation • Analysis of product validation
a. Perform product
• Analysis of product validation • Analysis of product validation outcomes outcomes
validation outcomes outcomes • Identification of anomalies • Identification of anomalies
b. Analyze product • Identification of anomalies and corrective action and corrective action
validation outcomes Able to: and corrective action recommendations recommendations
• Identify validation anomalies recommendations
or conformance Able to (for a system): Able to (for a system):
Establish (for a subsystem or • Establish product • Establish product
simple project): product conformance or conformance or
conformance • Select corrective action • Select corrective action
3.4.3 Product Validation Contribute to: Participate in: Direct (for a system): Direct (for a program):
Documentation • Preparation of product • Preparation of product • Preparation of product • Preparation of product
validation report validation report validation report validation report
a. Prepare product
• Capture of work products • Capture of work products • Capture of work products • Capture of work products
validation report and related information from and related information from and related information from and related information from
b. Capture product product validation activities product validation activities product validation activities product validation activities
validation work products
Define Agency/Center product
validation policies
HQ courses
21
Center courses
OJL activities
Assessment
22
Competency: 3.5 Product Transition

3.5.1 Product Transition Aware of steps to prepare for Participate in (for a subsystem Develop (for a system) product Direct (for a program)
Preparation product transition or simple project) preparing: transition strategy development of product
• Documentation that will transition strategy
a. Determine type of Ensure (for a system) the
accompany the product
product transition • Product transition readiness of: Ensure (for a program) the
b. Identify special transition procedures • Documentation that will readiness of:
procedures and enabling • Personnel availability and accompany the product • Documentation that will
product needs skills • Product transition accompany the product
c. Prepare end product for • Packaging material, handling procedures • Product transition
transition equipment, storage facilities, • Personnel availability and procedures
and shipping services skills • Personnel availability and
• Packaging material, handling skills
Oversee (for a subsystem or equipment, storage facilities, • Packaging material, handling
simple project) packaging, and shipping services equipment, storage facilities,
storing, moving end product to and shipping services
shipping location Oversee (for a system)
packaging, storing, moving end Oversee (for a program)
product to shipping location packaging, storing, moving end
product to shipping location
3.5.2 Product Transition Aware that product transition Ensure (for a subsystem or Ensure (for a system): Ensure (for a program):
Execution can be to the next higher level simple project): • End product and its • End product and its
for integration or to end user • End product and its documentation transition to documentation transition to
a. Transition product to end
documentation transition to customer customer
user customer • Receiving sites are ready for • Receiving sites are ready for
b. Prepare sites for end • Receiving sites are ready for end product end product
product end product
3.5.3 Product Transition Contribute to capture of work Participate in capture of work Direct (for a system) capture of Direct (for a program) capture
information from product information from product information from product information from product
a. Capture product transition activities transition activities transition activities transition activities
transition work products
Define Agency/Center product
transition policies
HQ courses
Center courses
OJL activities
23
Assessment
24
Competency: 3.6 Operations

3.6.1 Operations Contribute to development of Participate in development of Direct (for a system) Direct (for a program)
Planning the operations plan the operations plan development of the operations development of the operations
plan plan
a. Develop operations plan
3.6.2 Operations Contribute to operation of the Participate in (for a subsystem Participate in (for a system) Participate in (for a program)
Execution product or simple project) operation of operation of the product operation of the product
the product
a. Manage Operations
HQ courses
Center courses
OJL activities
Assessment
25
Competency Area: 4.0 Technical Management
Competency: 4.1 Technical Planning

4.1.1 Technical Planning Aware that common technical Participate in (for a subsystem Develop (for a system) or Develop (for a program) or
Preparation processes need to be planned or simple project): update planning strategies for update planning strategies for
• Collection of information for common technical processes common technical processes
a. Prepare a planning Contribute to technical technical planning
strategy for common planning by providing inputs as • Definition of technical work to Able to (for a system): Direct (for a program):
technical processes requested be done • Collect information for • Collection of information for
b. Define technical work to • Schedule, organize and cost technical planning technical planning
be done the technical work • Define technical work to be • Definition of technical work to
c. Schedule, organize and done be done
cost the technical work • Schedule, organize and cost • Schedule, organize and cost
the technical work the technical work
4.1.2 Technical Plans Contribute to development of Participate in (for a subsystem Direct (for a system) Direct (for a program)
Development technical plans or simple project) development development of formal development of formal
of formal technical plans (i.e. technical plans (i.e. SEMP, technical plans (i.e. SEMP,
a. Prepare Systems Aware that stakeholders can’t SEMP, Product Verification Product Verification Plan, Product Verification Plan,
Engineering be ignored during technical Plan, Product Validation Plan, Product Validation Plan, etc) Product Validation Plan, etc)
Management Plan planning etc)
(SEMP) Able to (for a system) obtain Able to (for a program) obtain
b. Prepare product Able to (for a subsystem or stakeholder agreements with stakeholder agreements with
verification plan simple project) obtain the technical plans the technical plans
c. Prepare product stakeholder agreements with
validation plan the technical plans
d. Prepare other technical
plans as needed
e. Obtain stakeholder buy-
in to the technical plans
4.1.3 Technical Work Able to follow technical work Participate in (for a subsystem Develop (for a system) Direct (for a program)
Directives directives or simple project) development technical work directives development of technical work
of technical work directives directives
a. Issue authorized
technical work directives
4.1.4 Technical Planning Contribute to capture of work Participate in capture of work Direct (for a system) capture of Direct (for a program) capture
information from technical information from technical information from technical information from technical
a. Capture technical planning activities planning activities planning activities planning activities
planning work products
Define Agency/Center
technical planning policies
26
HQ courses
Center courses
OJL activities
Assessment
27
Competency: 4.2 Requirements Management

4.2.1 Requirements Aware of activities to prepare Contribute to (for a Develop (for a system) Develop (for a program)
Management Preparation for requirements management subsystem or simple project) strategies for requirements strategies for requirements
strategies for requirements management management
a. Prepare strategies for management
requirements management
4.2.2 Requirements Contribute to collection of Participate in (for a Ensure (for a system): Ensure (for a program):
Management Execution requirements for documenting subsystem or simple project): • Requirements are • Requirements are
• Documenting requirements documented in proper documented in proper
a. Document expectations Able to review requirement in the proper format format format
and requirements in proper statements to ensure • Validating the requirements • Requirements baseline is • Requirements baseline is
format compliance with guidelines baseline validated validated
b. Confirm requirements • Identification of out-of- • Identification of out-of-
baseline has been Able to (for a subsystem or tolerance technical tolerance technical
validated simple project) identify and parameters parameters
c. Identify and propose propose changes to out-of-
changes to out-of- tolerance technical parameters Approve (for a system) Approve (for a program)
tolerance technical changes to out-of-tolerance changes to out-of-tolerance
parameters technical parameters technical parameters
4.2.3 Contribute to: Able to (for a simple project or Able to (for a system): Direct (for a program):
Expectation/Requirements • Development and subsystem) track between • Track between baselines • Tracking between baselines
maintenance of compliance baselines • Develop and maintain • Development and
Traceability matrices compliance matrices maintenance of compliance
a. Track expectations and Participate in development matrices
requirements between and maintenance of
baselines compliance matrices
b. Establish and maintain
requirements compliance
matrices
4.2.4 Able to review ECPs Contribute to (for a Direct (for a system): Direct (for a program):
Expectation/Requirements subsystem or simple project): • Review ECPs and provide • Review ECPs and provide
• Review ECPs and provide recommendations recommendations
Change Management recommendations • Implementation of change • Implementation of change
a. Review engineering • Disseminate approved procedures procedures
change proposals (ECPs) changes • Dissemination of approved • Disseminate approved
b. Implement formal change changes changes
procedures
c. Disseminate approved
changes
28
4.2.5 Requirement Contribute to capture of work Participate in capture of work Direct (for a system) capture Direct (for a program) capture
Management products from requirements products from requirements of work products from of work products from
management activities management activities requirements management requirements management
Documentation activities activities
a. Capture requirement
management work Define Agency/Center
products requirements management
policies
HQ courses
Center courses
OJL activities
Assessment
29
Competency: 4.3 Interface Management

4.3.1 Interface Aware of activities to prepare Contribute to (for a subsystem Develop (for a system) Direct (for a program)
Management for interface management or simple project) development procedures for interface development of procedures for
of procedures for interface management interface management
Preparation management
a. Prepare procedures for
interface management
4.3.2 Interface Contribute to interface Participate in interface Direct (for a system) interface Direct (for a program) interface
Management During management during system management during system management during system management during system
design design design design
System Design
a. Integrate interface and
requirements management
activities
b. Identify interfaces not in the
stakeholder set of
expectations
c. Document interfaces as
system structure emerges
d. Document origin,
destination, stimulus, and
special characteristics of
interfaces
e. Maintain the design solution
for internal interfaces
f. Maintain horizontal
traceability across
interfaces
g. Confirm ICDs validated with
parties on both sides of
interface
4.3.3 Interface Contribute to interface Participate in interface Direct (for a system) interface Direct (for a program) interface
Management During management during product management during product management during product management during product
integration integration integration integration
Product Integration
a. Review product integration
procedures
b. Identify interface
discrepancies
c. Confirm a pre-check is
30
completed on all physical
interfaces
d. Evaluate assembled
products for interface
compatibility
e. Confirm product V/V plans
include confirming
interfaces
f. Prepare and interface
evaluation report
4.3.4 Interface Control Contribute to interface control Participate in interface control Direct (for a system) interface Direct (for a program) interface
Execution activities activities control activities control activities
a. Manage interface changes
with the system structure
b. Identify and track changes
to interface documentation
c. Confirm interface issues
are analyzed and resolved
when a change affects
products on both sides of
the interface
d. Control traceability of
interface changes
e. Disseminate approved
interface change
information
4.3.5 Interface Contribute to capture of work Participate capture of work Direct (for a system) capture of Direct (for a program) capture
Management products from interface products from interface work products from interface of work products from interface
management activities management activities management activities management activities
Documentation
a. Capture interface Define Agency/Center
management work products interface management policies
HQ courses
Center courses
OJL activities
Assessment
31
Competency: 4.4 Technical Risk Management

4.4.1 Technical Risk Aware of activities to prepare Contribute to development of Develop (for a system) Direct (for a program)
Management for technical risk management strategies to conduct technical strategies to conduct technical development of strategies to
risk management risk management conduct technical risk
Preparation management
a. Prepare strategies to
conduct technical risk
management
4.4.2 Technical Risk Contribute to: Participate in (for a subsystem Able to (for a system) conduct: Direct (for a program):
Identification and • Identification of risk or simple project): • Risk identification • Identification of risk
• Risk analysis • Identification of risk • Stakeholder coordination • Stakeholder coordination
Assessment • Stakeholder coordination • Risk analysis
a. Identify risks Direct risk analysis
b. Coordinate with Able to perform risk analysis
stakeholders
c. Analyze risks for severity
of consequences and
likelihood of occurrence
4.4.3 Technical Risk Contribute to: Able to recommend risks for Able to (for a system) select Able to (for a program) select
Mitigation • Risk monitoring mitigation risks for mitigation risks for mitigation
a. Prepare for technical risk • Development of risk
mitigation/contingency action Participate in: Direct (for a system): Direct (for a program):
mitigation plans • Development of risk • Development of risk • Development of risk
b. Monitor status of each • Implementation of plans mitigation/contingency action mitigation/contingency action mitigation/contingency action
technical risk plans plans plans
c. Implement technical risk • Plan implementation • Plan implementation • Plan implementation
mitigation and
contingency action plans
as triggered
4.4.4 Technical Risk Contribute to capture of work Participate in capture of work Direct (for a system) capture of Direct (for a program) capture
Documentation products from technical risk products from technical risk work products from technical of work products from technical
management activities management activities risk management activities risk management activities
a. Capture technical risk
products technical risk management
policies
HQ courses
Center courses
32
OJL activities
Assessment
33
Competency: 4.5 Configuration Management

4.5.1 Configuration Aware of activities to prepare Participate in (for a subsystem Develop (for a system) Direct (for a program)
Management for configuration management or simple project) development strategies to conduct development of strategies to
of strategies to conduct configuration management conduct configuration
Preparation configuration management management
conduct configuration
management
4.5.2 Configuration Aware of activities to baseline Contribute to (for a subsystem Able to (for a system): Direct (for a program) SE
Control Baseline a configuration or simple project) SE • Identify items to be place participation in configuration
participation in configuration under configuration control control baseline:
a. Identify configuration control baseline: • Establish baseline • Identify items to control
control items • Identify items to control • Establish baseline
b. Establish baseline for • Establish baseline
each configuration item
4.5.3 Configuration Aware of configuration change Contribute to (for a subsystem Contribute to (for a system) Contribute to (for a program)
Control Management control or simple project) configuration configuration change control configuration change control
change control
a. Establish configuration
change process
b. Implement configuration
change process
4.5.4 Configuration Aware of content of Contribute to (for a subsystem Able to (for a system) identify Able to (for a program) identify
Documentation Status configuration control or simple project) identification content of configuration control content of configuration control
of content for configuration
a. Maintain configuration control
item description records
b. Maintain change records
c. Maintain differences
between baselines
4.5.5 Configuration Contribute to configuration Participate in configuration Direct (for a system) SE Direct (for a program) SE
Audits audits audits participation in configuration participation in configuration
audits audits
a. Audit baselines
b. Identify risks caused by
poor configuration
control
c. Track action items to
correct anomalies
4.5.6 Configuration Contribute to capture of work Participate capture of work Direct (for a system) capture of Direct (for a program) capture
34
Management products from configuration products from configuration work products from of work products from
Documentation management activities management activities configuration management configuration management
activities activities
a. Capture configuration
products configuration management
policies
HQ courses
Center courses
OJL activities
Assessment
35
Competency: 4.6 Technical Data Management

4.6.1 Technical Data Aware of activities to prepare Contribute to (for a subsystem Develop (for a system) Direct (for a program)
Management for technical data management or simple project) strategies to strategies to conduct technical development of strategies to
conduct technical data data management conduct technical data
Preparation management management
conduct technical data
management
4.6.2 Technical Data Provide: Provide (for a subsystem or Direct (for a system): Direct (for a program):
Collection and Storage • Data for storage simple project): • Data for storage • Data for storage
• Lessons learned • Data for storage • Development of lessons • Development of lessons
a. Collect and store
• Lessons learned learned learned
technical data
b. Record and distribute
lessons learned
c. Perform technical data
integrity checks
4.6.3 Technical Data Aware of measures to protect Aware of measures to protect Ensure (for a system) Ensure (for a program)
Maintenance technical data technical data measures to protect technical measures to protect technical
data data
a. Manage the databases
b. Perform technical data
maintenance
c. Protect stored data
4.6.4 Technical Data Aware of procedures to access Contribute to (for a subsystem Direct (for a system) Direct (for a program)
Access technical data or simple project) development development of procedures to development of procedures to
of procedures to access access technical data access technical data
a. Maintain an information technical data
library Define Agency/Center
b. Process requests for technical data management
technical data policies
c. Confirm that electronic
access rules are
followed
d. Provide proof of
correctness, reliability
and security of technical
data
HQ courses
36
Center courses
OJL activities
Assessment
37
Competency: 4.7 Technical Assessment

4.7.1 Technical Aware of activities to prepare Contribute to (for a subsystem Develop (for a system) Direct (for a program)
Assessment Preparation for technical assessments or simple project) strategies to strategies to conduct technical development of strategies to
conduct technical assessments assessments conduct technical assessments
a. Prepare strategies for
conducting technical
assessments
4.7.2 Technical Work Aware of technical work Able to (for a subsystem or Direct (for a system) Direct (for a program)
Productivity productivity assessment simple project): identification of process identification of process
• Identify process measures measures measures
Assessment • Monitor progress against
a. Identify, collect, and plans Monitor (for a system) Monitor (for a program)
analyze process progress against plans progress against plans
measures
b. Monitor technical data
management against
plans
4.7.3 Technical Product Aware of quality assessment Participate in (for a subsystem Direct (for a system) Direct (for a program)
Quality Assessment measures against technical or simple project) determination determination of: determination of:
requirements of: • Degree to which product • Degree to which product
a. Identify, collect, and
• Degree to which product satisfies requirements satisfies requirements
analyze the degree of satisfies requirements • Product performance • Product performance
technical requirement • Product performance variances variances
and technical variances and recommend
performance measures corrective action Able to select corrective action Able to select corrective action
satisfaction
b. Determine any variances
from expected values of
product performance
4.7.4 Technical Reviews Aware of review types and Able to (for a simple project or Able to (for a system) identify Able to (for a program) identify
a. Identify the type of their purposes subsystem) identify type and type and when a technical type and when a technical
technical reviews when a technical review is review is needed review is needed
Contribute to: needed
b. Determine progress
• Review material preparation Direct (for a system): Direct (for a program):
toward satisfying entry • Identification and resolution Contribute to (for a subsystem • Review material preparation • Review material preparation
criteria of action items or simple project): • Action item identification and • Action item identification and
c. Establish make up of the • Review material preparation resolution resolution
review team • Action item identification and
d. Prepare the review resolution Able to chair variety of Able to chair variety of review
38
presentation materials technical review boards (e.g. boards for other projects (e.g.
e. Identify and resolve PDR, CDR, TRR) PNAR, NAR)
action items
4.7.5 Technical Contribute to capture of work Participate in capture of work Direct (for a system) capture of Direct (for a program) capture
Assessment products from technical products from technical work products from technical of work products from technical
assessment activities assessment activities assessment activities assessment activities
Documentation
a. Capture technical Define Agency/Center
assessment work technical assessment policies
products
HQ courses
Center courses
OJL activities
Assessment
39
Competency: 4.8 Technical Decision Analysis

4.8.1 Decision Analysis Apply decision making Contribute to (for a simple Develop (for a system) Direct (for a program)
Preparation guidelines project or subsystem) guidelines for: development of guidelines for:
guidelines for: • When to use formal decision • When to use formal decision
a. Establish guidelines for
• When to use formal decision making making
when and how to use a making • Who will make decisions • Who will make decisions
formal decision making • Who will make decisions
process
4.8.2 Criteria Definition Contribute to criteria definition Participate in establishing Establish (for a system) Direct (for a program)
a. Define types of criteria to criteria definition: criteria definition: establishment of criteria
include • Types and ranges • Types and ranges definition:
• Rank criteria • Rank criteria • Types and ranges
b. Define acceptable range
• Rank criteria
and scale of criteria
c. Rank each criterion by
importance
4.8.3 Decision Contribute to identification Able to: Able to (for a system) select: Able to (for a program) select:
Alternatives and evaluation of alternatives • Recommend evaluation • Evaluation method • Evaluation method
a. Select evaluation method • Solution • Solution
Able to: • Identify and evaluate
methods and • Recommend evaluation alternatives Direct (for a system) Direct (for a program)
tools/techniques method • Recommend a solution identification and evaluation of identification and evaluation of
b. Identify and evaluate • Recommend solution alternatives alternatives
alternative solutions
c. Select recommended
solutions
4.8.4 Decision Analysis Contribute to capture of work Participate in capture of work Direct (for a system) capture of Direct (for a program) capture
Documentation products from decision analysis products from decision analysis work products from decision of work products from decision
activities activities analysis activities analysis activities
a. Capture decision
analysis work products Define Agency/Center decision
analysis policies
HQ courses
Center courses
OJL activities
Assessment
40
Competency Area: 5.0 Project Management and Control
Competency: 5.1 Acquisition Strategies and Procurement

5.1.1 Acquisition Contribute to acquisition Participate in acquisition Direct (for a system) effort to Direct (for a program) effort to
Strategies strategy technical inputs strategy development provide acquisition strategy provide acquisition strategy
technical inputs technical inputs
a. Identify technical inputs
for acquisition strategies Contribute to (for a system) Contribute to (for a very large,
b. Develop acquisition acquisition strategy complex project) acquisition
strategies development strategy development
5.1.2 Procurement Contribute to technical Participate in technical Direct (for a system) technical Direct (for a program) technical
a. Write technical proposal writing and evaluation proposal writing and evaluation proposal writing and evaluation proposal writing and evaluation
proposals
Aware of execution and Contribute to execution and Participate in (for a system) Participate in (for a program)
b. Review and evaluate management of acquisition management of acquisition execution and management of execution and management of
technical proposals instruments instruments acquisition instruments acquisition instruments
c. Execute acquisition
instruments
d. Manage acquisition
instruments
HQ courses
Center courses
OJL activities
Assessment
41
Competency: 5.2 Resource Management

5.2.1 Resource Margin Aware of margins and how Identify (for a subsystem or Identify (for a system) Identify (for a program)
Determination they are used to manage the simple project) resources to resources to track resources to track
project track
a. Identify resources to be Direct (for a system) Direct (for a program)
allocated and tracked Contribute to (for a subsystem development of resource development of resource
b. Provide resource or simple project) development estimates and margins down to estimates and margins down to
estimates to include of resource estimates and subsystem level subsystem level
cost, schedule, and labor margins down to subsystem
c. Define acceptable level
resource margins
d. Allocate resources
among subsystems
5.2.2 Resource Tracking Contribute to resource Participate in resource Manage (for a system) Manage (for a program)
a. Implement earned value tracking: tracking: resource tracking: resource tracking:
for systems engineering • Monitor assigned resources • Monitor resources and • Monitor resources and • Monitor resources and
and margins using tools as margins using tools as margins using tools as margins using tools as
tasks
appropriate appropriate appropriate appropriate
b. Monitor resources and • Provide resource status • Provide resource status • Provide resource status • Provide resource status
margins and re-allocate inputs
as required
c. Provide status relative to
cost, schedule, and
technical progress
HQ courses
Center courses
OJL activities
Assessment
42
Competency: 5.3 Contract Management

5.3.1 Contractor Contribute to: Participate in (for a subsystem Develop (for a system) Direct (for a program)
Monitoring • Development of technical or simple project) technical technical penetration of development of technical
penetration of contractor penetration of contractor contractor penetration of contractor
a. Develop technical
• Monitoring of contractor
penetration/insight technical performance Monitor (for a subsystem or Monitor (for a system) Monitor (for a program)
required for contractor simple project) contractor contractor technical contractor technical
activities technical performance performance performance
e. Monitor technical
performance of
contractors
5.3.2 Technical Inputs Provide technical inputs for Develop (for a subsystem or Develop (for a system) Develop (for a program)
a. Provide technical inputs contract management simple project) technical inputs technical inputs for contract technical inputs for contract
for project contract for contract management management management
management including
change control
HQ courses
Center courses
OJL activities
Assessment
43
Competency: 5.4 Systems Engineering Management

5.4.1 Systems Contribute to portion of SE Participate in SE effort: Direct (for a system) SE effort: Direct (for a program) SE
Engineering effort: • Implement technical plans • Implement technical plans effort:
• Implement technical plans • Monitor and report SE status • Monitor and report SE status • Implement technical plans
Implementation • Monitor and report SE status • Monitor and report SE status
a. Implement the SEMP
and other technical plans
b. Monitor and report on
Systems Engineering
status
5.4.2 Systems Aware of SE management Contribute to management of Able to (for a system) manage Able to (for a program)
Engineering activities SE effort: SE effort: manage SE effort:
• Evaluate and make • Evaluate and make • Evaluate and make
Management improvements improvements improvements
Responsibilities • Prioritize technical team • Prioritize technical team • Prioritize technical team
a. Evaluate systems activities activities activities
engineering process and • Integrate information across • Integrate information across • Integrate information across
make improvements as subsystems subsystems subsystems
necessary • Manage deliverables • Manage deliverables • Manage deliverables
b. Prioritize/reprioritize • Monitor system build-up • Monitor system build-up • Monitor system build-up
activities of technical
teams
c. Integrate information
across subsystems
d. Manage system
engineering deliverables
(e.g., technical baseline,
TPMs, etc)
e. Monitor build-up of the
system
HQ courses
Center courses
OJL activities
Assessment
44
Competency Area: 6.0 NASA Internal and External Environments
Competency: 6.1 Agency Structure, Mission, and Internal Goals

6.1.1 Agency Internal Knowledge of: Perform (for a subsystem or Lead and manage (for a Establish (for a program) the
Environment • Agency structure; goals at all simple project) system system) system engineering system engineering
levels; vision, mission, plans engineering activities within the activities within the Agency requirements needed to
a. Function within the Agency structure and across structure and across programs, achieve program goals within
and objectives
Agency structure and • How to align technical programs, Centers and NASA, Centers and NASA, as needed the Agency structure and
culture activities and metrics with as needed to achieve project to achieve project and system ensure mission success
b. Align technical activities Agency vision, mission, and subsystem goals goals
with Agency vision, plans, and objectives Make decisions from an
mission, objectives, Contribute to the alignment of Lead and manage (for a Agency perspective through
goals and plans a subsystem’s technical system) the alignment of a the understanding of NASA’s
activities and metrics with system’s technical activities functional, social, cultural, and
Agency vision, mission, plans, and metrics with Agency vision, political environments to
and objectives mission, plans, and objectives ensure mission success
Contribute to the Lead the alignment of a

establishment of the Agency’s Agency’s technical activities
technical requirements and and metrics with Agency vision,
infrastructure mission, plans, and objectives
Establish the Agency’s

technical requirements and
infrastructure to ensure mission
success
6.1.2 Center Internal Knowledge of: Perform (for a subsystem or Perform (for a system) system Lead the alignment of a
Environment • Center structure; goals at all simple project) system engineering activities within the Center’s technical activities and
levels; vision, mission, plans engineering activities within the Center structure and across metrics with Agency vision,
a. Function within the Center structure and across divisions and Center, as mission, plans, and objectives
and objectives
Center structure and • How to align technical divisions and Center, as needed to achieve project and
culture activities and metrics with needed to achieve project and system goals Establish the Center’s
b. Align technical activities Center vision, mission, plans, subsystem goals technical requirements and
with Center vision, and objectives Lead and manage (for a infrastructure to be aligned with
mission, objectives, Contribute to alignment of the system) the alignment of the Agency structure
goals and plans subsystem’s technical activities system’s technical activities
and metrics with Center vision, and metrics with Center vision,
mission, plans, and objectives mission, plans, and objectives
HQ courses
Center courses
OJL activities
45
Assessment
46
Competency: 6.2 NASA PM/SE Procedures and Guidelines

6.2.1 Agency PM/SE Knowledge of NASA Structure and manage (for a Structure and manage (for a Establish (for a program)
Procedures and engineering of systems and PM subsystem or simple project) system) technical activities to requirements for technical
policies and guidelines outlined technical activities to comply comply with NASA systems activities that comply with
Guidelines in NASA procedures and with NASA engineering of engineering and PM policies NASA systems engineering
a. Structure technical guidelines documents systems and PM policies and and guidelines and PM policies and guidelines
activities to comply with guidelines
relevant Agency Contribute to the review and Assess the Agency’s technical
processes and development of Agency processes and guidelines
guidelines systems engineering policies
and guidelines to ensure Lead the review and
mission success development of Agency
systems engineering policies
and guidelines to ensure
mission success
6.2.1 Center PM/SE Knowledge of Center Structure and manage (for a Structure and manage (for a Establish (for a program)
Procedures and engineering of systems and PM subsystem or simple project) system) technical activities to requirements for technical
policies and guidelines outlined technical activities to comply comply with Center systems activities that comply with
Guidelines in Center procedures and with Center engineering of engineering and PM policies Center systems engineering
a. Structure technical guidelines documents systems and PM policies and and guidelines and PM policies and guidelines
activities to comply with guidelines
relevant Center Contribute to the review and Assess the Center’s technical
processes and development of Center processes and guidelines
guidelines systems engineering policies
and guidelines to ensure Lead the review and
mission success development of Center
systems engineering policies
and guidelines to support
Agency policy
HQ courses
Center courses
OJL activities
Assessment
47
Competency: 6.3 External Relationships

6.3.1 Professional Participate in: Contribute to professional Participate in leadership Provide leadership to
Associations • Professional societies/ societies/ organizations roles within professional professional societies/
organizations societies/ organizations organizations to guide the
a. Membership and
• Technical activities that Maintain knowledge of current establishment of
participation in conform to up-to-date research and key Maintain knowledge of current industry/professional
professional societies/ industry/professional individuals in the field up-to-date research and key standards, procedures, and
organizations standards, procedures, and individuals in the field regulations
b. Contribution to regulations Manage (for a subsystem or
profession simple project) technical Lead and manage (for a Contribute to the knowledge
c. Structure technical activities that conform to system) technical activities that and up-to-date research in the
activities to conform to industry/ professional conform to industry/ discipline
industry/professional standards, procedures, and professional standards,
regulations procedures, and regulations Establish (for a program)
standards, procedures, technical requirements that
and regulations Develop key contacts within conform to industry/
the discipline (both within and professional standards,
outside of NASA) procedures, and regulations
6.3.2 International Aware of international Contribute to (for a subsystem Lead and manage (for a Establish international
Relationships (when partnerships, agreements, or simple project) the system) the development of partnerships and agreements
standards, and ITAR as they development of international international partnerships and to ensure mission success
engineering systems for relate to the team’s technical partnerships and agreements agreements as they relate to
or with international activities as they relate to the subsystem the system Comply with ITAR and
partners) international agreements and
a. Develop international Comply with ITAR and Comply with ITAR and standards as they relate to the
partnerships and international agreements and international agreements and program
agreements standards as they relate to the standards as they relate to the
subsystem system
b. Comply with ITAR
c. Comply with
international agreements
and standards
HQ courses
Center courses
OJL activities
Assessment
48
Competency Area: 7.0 Human Capital Management
Competency: 7.1 Technical Staffing and Performance

7.1.1 Staffing Function Understand the roles and Define (for a subsystem of Integrate (for a system) the Establish staffing strategies
a. Define roles and responsibilities of each simple project) the technical technical team members’ roles and selection criteria for
responsibilities of the member of a technical team team members’ roles and and responsibilities recruiting, evaluating, selecting
responsibilities for performing and staffing technical teams for
technical workforce Aware of NASA’s processes for technical activities Employ skills analysis and a program
b. Identify and obtain the selecting, staffing, and team selection techniques to
required technical evaluating teams Assist in identifying and build technical teams (for a Identify and obtain the
personnel resources obtaining the required system) with complementary required technical leadership
technical personnel resources talents and the necessary personnel resources for a
for developing a subsystem skills, expertise, and program
experiences
Ensure that the technical team Establish the Agency’s
members (for a subsystem of Contribute to the technical workforce personnel
simple project) have the assessment of the Agency’s and infrastructure requirements
appropriate skills, expertise, technical workforce’s to ensure mission success
and experience capabilities and gaps for
achieving mission success Lead the assessment of the
Agency’s technical workforce’s
capabilities and gaps for
achieving mission success
7.1.2 Performance Understand and achieve the Monitor (for a subsystem or Establish (for a system) the Establish performance criteria
Assessment desired performance level for simple project) the desired performance level of for a program’s technical
the assigned technical activities performance of a subsystem’s the system’s technical workforce to ensure mission
a. Monitor performance of technical team members workforce success
technical workforce Monitor own technical
b. Achieve desired performance level Apply appropriate team Establish (for a system) the Monitor the program’s systems
performance level of the management techniques and performance criteria for the engineers’ performance
technical workforce concepts to guide a qualified system’s technical workforce
technical team (for a Establish the desired
subsystem or simple project) Monitor the subsystems leads’ performance level for the
toward maintaining the desired performance Agency’s technical workforce
performance level
HQ courses
Center courses
OJL activities
Assessment
49
Competency Area: 7.0 Human Capital Management
Competency: 7.2 Team Dynamics and Management

7.2.1 Team Development Understand team members’ Employ appropriate team Communicate the technical Establish and communicate
a. Motivate and reward roles and responsibilities, how management techniques and team’s direction and focus to the direction and focus of a
technical team members’ they interact as a unit, and concepts to effectively develop ensure mission success program’s technical leadership
what motivates them to achieve and motivate a technical team team to ensure mission
performance peek performance (for a subsystem or simple Implement the incentive success
b. Manage relationships project) program for motivating and
among technical team Understand own roles, rewarding the technical team Establish the incentive
members responsibilities, and desired Understand (for a subsystem members’ performance (for a program to enhance
performance level for or simple project) each system) performance and productivity of
performing technical activities technical team member’s a program’s technical
capabilities, function, and the Apply appropriate team workforce teams
Manage own relationships interrelationships among them management techniques and
among technical team concepts to build on a technical Establish and manage
members Manage the relationships team members’ capabilities productive relationships among
among technical team and functions in order to a program’s technical
members (for a subsystem or facilitate the interrelationships leadership team in order to
simple project) and improve team performance ensure mission success
7.2.2 Team Processes Understand the relationships Manage (for a subsystem or Establish and manage (for a Identify and manage the
a. Establish and manage between technical team simple project) interfaces and system) the interfaces and interfaces and relationships
interfaces and members, customers, relationships with the technical relationships with the technical among the stakeholders and
stakeholders and partners team members, customers, team members, customers, partners that may impact
relationships with stakeholders and partners stakeholders and partners program and mission success
technical team Participate in team
members, customers, brainstorming, conflict Lead (for a subsystem or Create an environment within Determine and mitigate long-
stakeholders and resolution, negotiation, and simple project) brainstorming, the technical team (for a term consequences of any
partners problem solving activities conflict resolution, negotiation, system) that fosters impacts resulting from
b. Facilitate brainstorming, and problem solving activities opportunities to conduct interfaces and relationships
conflict resolution, Understand and work within for the technical team activities for brainstorming, among the stakeholders and
negotiation, and problem the team’s communication, conflict resolution, negotiation, partners
solving collaboration and integration Establish and facilitate (for a and problem solving
dynamics subsystem or simple project) Employ a range of conflict
c. Facilitate the communication, Manage the group dynamics resolution techniques to bring
communication, collaboration, and integration and cooperation of the about positive change and
collaboration and dynamics for the technical technical team (for a system) to commitment, build trust and
integration team facilitate communication, respect, and mitigate the
collaboration, and integration in negative effects of conflict
order to ensure mission
success Create an open and non-
critical environment, that
50
facilitates collaboration,
communication, and individual
empowerment to insure
mission success
7.2.3 Team Meetings Contribute to the outcomes of Plan, lead and facilitate (for a Establish a system’s technical Establish a program’s
a. Plan effective technical technical team meetings to subsystem or simple project) team meeting’s requirements technical team meeting’s
team meetings enhance success effective technical team that align with the program’s requirements to ensure mission
meetings requirements success
b. Facilitate effective
technical team meetings Plan, lead and facilitate (for a Plan, lead and facilitate (for a
system) effective technical program) effective technical
team meetings leadership team meetings
HQ courses
Center courses
OJL activities
Assessment
51
Competency Area: 8.0 Security, Safety and Mission Assurance
Competency: 8.1 Security

8.1.1 IT Security Participate in the identification Manage (for a subsystem or Lead and Manage (for a Establish program
a. Identify IT security of IT security requirements simple project): system): requirements for IT security for
requirements • Identification of IT security • Identification of IT security the systems engineering
Aware of the IT security plan requirements for the requirements for the system
b. Develop and implement and its impact on the team’s subsystem • Development and Lead the development of IT
IT security plan technical activities • Development and implementation of the IT security for the systems
implementation of the IT security plan for the system engineering
security plan for the
subsystem Contribute to the
establishment of program
and/or Agency requirements for
IT security for the systems
engineering
8.1.2 Other Security Participate in the identification Manage (for a subsystem or Lead and Manage (for a Establish program
Related Issues of other security requirements simple project): system): requirements for other security
related to the subsystem • Identification of other security • Identification of other security related to systems engineering
a. Identify other security
requirements related to the requirements related to the
requirements Aware of the security plan for subsystem system Lead the development of other
b. Develop and implement the subsystem and its impact • Development and • Development and security related to systems
security plan on the team’s technical implementation of a security implementation of a security engineering
activities plan for the subsystem plan for the system
Contribute to the establishment

of program and/or Agency
requirements for IT security for
the systems engineering
HQ courses
Center courses
OJL activities
Assessment
52
Competency Area: 8.0 Security, Safety and Mission Assurance

Competency: 8.2 Safety and Mission Assurance
8.2.1 System Safety Participate in: Manage the safety planning Lead and manage the system Establish system safety
Planning and • Identifying relevant safety and implementation (for a safety planning and planning and management
regulations/ procedures and subsystem or simple project): implementation for a system policy and procedures for a
Management assessing potential hazards • Identify relevant safety program
a. Identify relevant safety for a subsystem regulations/ procedures Review subsystem safety
regulations/ procedures • Performing system safety • Assess potential hazards plans and implementation for Review system safety plans
b. Assess potential hazards analysis, verifying system • Monitor and control, the program and implementation for
c. Monitor and control, safety, and conducting failure eliminate, or reduce aprogram
eliminate, or reduce resolution and reporting identified hazards Employ systems safety
hazards • Perform subsystem safety concepts and Continuous Risk Ensure that system safety
d. Perform system safety analysis Management procedures to hazards within a program are
• Verify subsystem safety identify and evaluate systems identified controlled and/or
analysis engineering safety threats eliminated
e. Verify system safety • Conduct failure resolution
f. Conduct failure and reporting
Contribute to the development Provide proactive leadership to
resolution and reporting of system safety planning and improve systems engineering
management policy and safety in a program
procedures (for a program and
the Agency) Lead the development of
system safety planning and
management policy and
procedures for the Agency
8.2.2 Safety Aware of safety management Identify and manage (for a Identify and manage (for a Review system safety
Management activities that relate to assigned subsystem or simple project): system): management activities for the
technical activities and • Test safety for the • Test safety for the system program
a. Identify and manage test subsystem subsystem • Operations safety for the
safety • Operations safety for the system Foster a safety culture
b. Identify and manage subsystem • Industrial safety throughout the program by
operations safety • Industrial safety advocating engineering
c. Identify and manage Review system safety excellence
industrial safety management activities for
subsystems
8.2.3 Safety and Mission Understand and comply with Identify (for a subsystem or Identify (for a system) mission Identify mission assurance
Assurance Planning and NASA safety and mission simple project) mission assurance requirements for the requirements for a program
assurance strategies, policies, assurance requirements for a system
Management and standards subsystem Review system safety and
a. Identify Mission Develop (for a system) Safety mission assurance activities for
assurance requirements Participate in identifying Develop (for a subsystem or and Mission Assurance: a program
b. Develop Safety and mission assurance simple project) Safety and • Plan for the system,
Mission assurance plan, requirements Mission Assurance: including system quality, Develop Safety and Mission
53
including system quality, • Plan for the subsystem, reliability and maintainability, Assurance policy and
reliability and Able to follow Safety and including system quality, that complies with NASA procedures (for a program
maintainability Mission Assurance plan as it reliability and maintainability, safety and mission and/or Agency)
c. Develop Safety and relates to technical activities for that complies with NASA assurance strategies,
a subsystem safety and mission policies, and standards
Mission assurance
assurance strategies, • Implementation strategies
implementation policies, and standards
strategies • Implementation strategies Review system safety and
mission assurance activities for
subsystems
8.2.4 Safety and Mission Contribute to: Contribute to preparing for Lead (for a system) the Chair engineering and safety
Assurance Reviews • Safety and Mission and participating in: activities to prepare the system review boards:
Assurance Readiness • Safety and Mission for and participate in: • Safety and Mission
a. Prepare for and
Review Assurance Readiness • Safety and Mission Assurance Readiness
participate in Safety and • Program Audit and Review Reviews Assurance Readiness Reviews
Mission Assurance process • Program Audit and Review Reviews • Program Audit and Review
Readiness Review • Certificate of Flight process • Program Audit and Review process
(SMARR) Readiness process • Certificate of Flight process • Certificate of Flight
b. Prepare for and Readiness process • Certificate of Flight Readiness process
participate in Program Readiness process
Audit and Review
(PA&R) process Participate in review boards
c. Prepare for and for other projects and programs
participate in Certificate
of Flight Readiness
(CoFR) process
HQ courses
Center courses
OJL activities
Assessment
54
Competency Area: 9.0 Professional and Leadership Development
Competency: 9.1 Mentoring and Coaching

9.1.1 Mentoring and Secure own mentor to receive Identify technical team Provide guidance to enhance Communicate expertise,
Coaching Tasks advice and guidance members’ key strengths and performance, facilitate success, advice, and knowledge
opportunities for development and build commitment. effectively for the purpose of
a. Provide advice and Receive periodic personal in order to enhance broadening the proficiency of
guidance coaching to improve identified performance Serve as a mentor to at least others, positively influencing
b. Teach juniors weaknesses one subsystem engineer, decision-making, and
c. Receive periodic Serve as a mentor to at least meeting on a regular basis to establishing cooperative
personal coaching to one team member of a provide advice and guidance relationships
improve identified subsystem technical team,
weaknesses meeting on a regular basis to Secure own mentor to receive Serve as a mentor to at least
provide advice and guidance advice and guidance one system engineer, meeting
on a regular basis to provide
Secure own mentor to receive Apply coaching skills to advice and guidance
advice and guidance improve, sustain and/or
enhance technical performance Advocate for and support
Apply coaching skills to of team members for a mentoring and coaching
improve, sustain and/or complex project resources for system engineers
enhance technical performance
of team members (for a simple Receive periodic personal Establish a coaching and
project or subsystem) coaching to improve identified mentoring climate within the
weaknesses technical team
Receive periodic personal
coaching from a systems Receive periodic personal
engineer to improve identified coaching to improve identified
weaknesses weaknesses
HQ courses
Center courses
OJL activities
Assessment
55
Competency: 9.2 Communication

9.2.1 Technical Develop own ability to Write and present (for a Write and present (for a Write and present to Center
Communication effectively write and present subsystem or simple project) system) technical information, and HQ management technical
technical information, as well technical information, as well as well as communicate information, as well as
a. Write technical as communicate technical as communicate technical technical decisions, relating to communicate technical
information decisions decisions, relating to the the system’s technical activities decisions, relating to technical
b. Present technical subsystem’s technical activities activities for a program
information Lead and manage (for a
c. Communicate technical Effectively and concisely system) the communication of Establish processes and
decisions communicate technical technical information and procedures to communicate
information to provide a technical decisions relating to technical information and
comprehensive and concise the system’s technical activities technical decisions relating to a
recommendation program’s technical activities
Communicate effectively and
concisely technical information Establish processes and
to provide a comprehensive procedures to communication
and concise recommendation of technical information and
to top management technical decisions relating to
the Agency’s technical
activities
9.2.2 Reporting Results Develop own ability to write Write and present reports that Write and present reports that Write and present reports to
a. Write reports and present reports that effectively communicate effectively communicate Center and HQ management
b. Present reports communicate technical status, technical status, challenges, technical status, challenges, that effectively communicate
challenges, problem solutions problem solutions and/or problem solutions and/or technical status, challenges,
and/or accomplishments accomplishments for a accomplishments for a system problem solutions and/or
subsystem in order to provide a in order to provide a accomplishments for a program
comprehensive account of a comprehensive account of a
particular phenomenon particular phenomenon Communicate the results of a
technical assessment, analysis
Review the technical reports of Lead and manage (for a and/or investigation that is
others to insure quality and system) the writing and targeted to a particular
accurate reporting of technical presenting of technical reports audience and provides a
information that effectively and concisely comprehensive account of
communicate the results of a engineering issues, as well as
Communicate the results of a technical assessment, analysis evidence-based
technical assessments, and/or investigation and recommendations
analyses, reviews, and/or provides evidence based
investigations recommendations
Review the technical reports of
56
subsystem leads to insure
quality and accurate reporting
of technical information
Communicate technical
information from a variety of
data sources that is targeted to
a particular audience and
provides an evidence-based,
comprehensive account of a
phenomenon concerning
systems engineering issues
related to a system
9.2.3 Interpersonal Demonstrate skills in: Apply appropriate skills for Apply appropriate skills for Create an environment that
Communication • Speaking and writing (both using a variety of media to using a variety of media to facilitates positive
formally and informally) for effectively communicate effectively communicate communication approaches
a. Demonstrate skills in technical information about a technical information about a within the technical workforce
understanding
speaking and writing • Demonstrate skills in subsystem system of a program
(both formally and listening for understanding
informally) for Promote communication Promote communication Communicate and advocate
understanding approaches that establish an approaches that establish an information regarding technical
b. Demonstrate skills in open and positive environment open and positive environment information to high levels of
listening for within a subsystem’s technical within a system’s technical Government and pubic media
understanding team team
Model and encourage Create an environment in the

listening skills that include technical team of a system that
involving, responding, and encourages listening, involving,
appreciating behaviors. responding, and appreciating
behaviors
HQ courses
Center courses
OJL activities
Assessment
57

Competency: 9.3 Leadership
9.3.1 Delegating Understand own technical Assign, delegate, and Assign, delegate, and Develop technical tasks/ work
Function tasks / work assignments and reassess (for a subsystem or reassess technical tasks/ work assignments for the leadership
performance success criteria simple project) technical tasks/ assignments (for a system) team for a program
a. Assign, delegate, and work assignments
reassess technical tasks/ Track and manage own Contribute to defining the Define success criteria for
work assignments performance to insure Implement (for a subsystem or success criteria for performing performing technical tasks/
b. Define success criteria achievement of success criteria simple project) success criteria technical tasks/ work work assignments for a
for performing technical for performing technical tasks/ assignments for a system program
tasks/ work assignments work assignments
c. Track and manage Implement (for a system) Conduct trend analyses of
success criteria for Track and manage (for a success criteria for performing significant trends and/or
performance subsystem or simple project) technical tasks/ work anomalies concerning technical
success criteria for technical assignments performance and develop a
performance proactive recommendations for
Track and manage (for a the program
system) success criteria for
technical performance
9.3.2 Influencing Role Understand: Provide (for a subsystem or Provide vision, direction, and Provide vision, direction, and
a. Provide vision, direction, • Leadership techniques by simple project) vision, direction, guidance for technical activities guidance for technical activities
and guidance focusing on strategies for and guidance for technical for a system for a program
personal and team activities
b. Motivate and inspire Employ leadership techniques Employ empowerment
professional growth
individuals to perform • Power of influence, Motivate and inspire (for a that encourage individual strategies to initiate ideas and
technical tasks/ work motivation, vision, and subsystem or simple project) empowerment and guides actions from others that foster
assignments resolve, as well as the members of the subsystem’s individuals toward the technical innovations to support
successfully relationship between leading technical team to perform successful obtainment of their mission success
c. Recognize and reward and managing technical tasks/ work goals
accomplishments assignments successfully Communicate expertise,
d. Establish and maintain Function to maintain a Motivate and inspire (for a advice, and knowledge
collaborative and open collaborative and open work Recognize and reward (for a system) members of the effectively for the purpose of
environment subsystem or simple project) system’s technical team to broadening the proficiency of
work environment the accomplishments of perform technical tasks/ work others, positively influencing
members of the subsystem’s assignments successfully decision-making, and
technical team establishing cooperative
Recognize and reward (for a relationships
Establish and maintain (for a system) the accomplishments
subsystem or simple project) a of members of the system’s Establish and maintain an
collaborative and open work technical team environment within the
environment within the program’s technical workforce
subsystem’s technical team Establish and maintain (for a that promotes motivation,
58
system) a collaborative and positive recognition, and
open work environment within collaboration
the system’s technical team
9.3.3 Decision-Making Participate in a technical Manage a subsystem’s Manage a system’s technical Establish the technical
and Solving Problems team’s decision-making and technical team’s decision- team’s decision-making and workforce decision-making and
problem solving activities making and problem solving problem solving processes problem solving processes for
a. Define problem processes technical activities for a
b. Establish solution criteria Understand and follow the Lead (for a system) the program
c. Evaluate alternatives technical team’s decision- Lead a subsystem’s technical system’s technical team in
d. Determine solution(s) making and problem-solving team in decision-making and decision-making and problem Create an environment that
based on facts, processes problem solving activities solving activities encourages consensus
evidence, criteria and building, as well as minority
risk Employ team decision-making opinions, and results in
Evaluate and select among techniques that foster decisions that are based on
alternative approaches, consensus building, while sound evidence
concepts, architectures, etc. allowing for minority opinions,
and resulting in evidence- Employ analytical decision-
based decisions making tools and knowledge
within a systematic framework
to make effective evidence-
based decision
HQ courses
Center courses
OJL activities
Assessment
59
Competency Area: 10.0 Knowledge Management
Competency: 10.1 Knowledge Capture and Transfer

10.1.1 Lessons Learned Contribute to the technical Manage (for a subsystem or Manage and integrate (for a Lead (for a program) the
Documentation team’s lessons learned simple project) the identification system) the identification and identification and
activities and documentation of systems documentation of systems documentation of systems
a. Identify lessons learned engineering activities, including engineering activities, including engineering activities, including
from system engineering Aware of lessons learned/best their impact on project history their impact on project history their impact on project history
activities practices from previous and lessons learned and lessons learned and lessons learned
b. Record lessons learned programs, projects and
from system engineering significant studies Captures appropriate Implement proper knowledge Establish proper knowledge
activities knowledge and trends relating management strategies that management strategies that
c. Evaluate lessons to engineering issues within the provide integration of technical will facilitate communication,
learned/best practices of subsystem in order to input into knowledge and information enable proactive information
system engineering a knowledge management from reports, trend analyses, use, improve/enhance
and lessons learned into a decision-making, expedite
activities and related Evaluate lessons learned/best knowledge management best-practices in engineering,
significant studies practices from previous system that will enable and transfer lessons-learned.
programs, projects and proactive information use,
significant studies assist in problem-solving, and Coordinate the development
improve decision-making. and maintenance of an
engineering knowledge
Evaluate lessons learned/best management system that is
practices from previous useful for improving decision-
programs, projects and making, information sharing,
significant studies and resolving engineering
issues.
Develop lesson-learned case
studies based on NASA Promote and require the
engineering experiences that effective application of lessons
can benefit the Agency and learned/best practices from
junior engineers previous programs, projects
and significant studies
10.1.2 Work Products Contribute to the technical Manage (for a subsystem or Manage (for a system) the Establish processes (for a
a. Capture work products team’s capture of work simple project) the capture of capture of work products, program) for the capture of and
throughout the product products work products, including including decision(s) made, access to work products,
decision(s) made, supporting supporting rationale and including decision(s) made,
life cycle Aware of access to work rationale and assumptions, and assumptions, and any supporting rationale and
b. Make work products products by appropriate users any corrective actions corrective actions assumptions, and any
available to appropriate corrective actions
users/stakeholders Provide access to the work Provide access to the work
products of a subsystem to products of a system to Establish policy and
60
appropriate users appropriate users processes for the Agency
concerning the capture of and
access to work products
HQ courses
Center courses
OJL activities
Assessment
61

Systems Engineering Competencies

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Systems Engineering Competencies

Uploaded by

Copyright:

Available Formats

ACADEMY OF PROGRAM/PROJECT & ENGINEERING LEADERSHIP

NASA’s Systems Engineering

Systems Engineering Competencies*

Structure of the Systems Engineering Competency Framework

The SE Competencies are structured as follows:

Competency Area: 1.0 Concepts and Architecture

Competency: 1.1 Mission Needs Statement

Competency Area: 1.0 Concepts and Architecture

Competency: 1.2 System Environments

Competency Area: 1.0 Concepts and Architecture

Competency: 1.3 Trade Studies

Competency Area: 1.0 Concepts and Architecture

Competency: 1.4 System Architecture

Competency Area: 2.0 System Design

Competency: 2.1 Stakeholder Expectation Definition & Management

Competency Area: 2.0 System Design

Competency: 2.2 Technical Requirements Definition

Competency Area: 2.0 System Design

Competency: 2.3 Logical Decomposition

Competency Area: 2.0 System Design

Competency: 2.4 Design Solution Definition

Competency Area: 3.0 Product, Product Transition, Operations

Competency: 3.1 Product Implementation

Competency Area: 3.0 Product, Product Transition, Operations

Competency: 3.2 Product Integration

Competency Area: 3.0 Product, Product Transition, Operations

Competency: 3.3 Product Verification

Competency Area: 3.0 Product, Product Transition, Operations

Competency: 3.4 Product Validation

Competency Area: 3.0 Product, Product Transition, Operations

Competency: 3.5 Product Transition

Competency Area: 3.0 Product, Product Transition, Operations

Competency: 3.6 Operations

Competency Area: 4.0 Technical Management

Competency: 4.1 Technical Planning

Competency Area: 4.0 Technical Management

Competency: 4.2 Requirements Management

Competency Area: 4.0 Technical Management

Competency: 4.3 Interface Management

Competency Area: 4.0 Technical Management

Competency: 4.4 Technical Risk Management

Competency Area: 4.0 Technical Management

Competency: 4.5 Configuration Management

Competency Area: 4.0 Technical Management

Competency: 4.6 Technical Data Management

Competency Area: 4.0 Technical Management

Competency: 4.7 Technical Assessment

Competency Area: 4.0 Technical Management

Competency: 4.8 Technical Decision Analysis

Competency Area: 5.0 Project Management and Control

Competency: 5.1 Acquisition Strategies and Procurement

Competency Area: 5.0 Project Management and Control

Competency: 5.2 Resource Management

Competency Area: 5.0 Project Management and Control

Competency: 5.3 Contract Management

Competency Area: 5.0 Project Management and Control

Competency: 5.4 Systems Engineering Management

Competency Area: 6.0 NASA Internal and External Environments

Competency: 6.1 Agency Structure, Mission, and Internal Goals

Contribute to the Lead the alignment of a

Establish the Agency’s

Competency Area: 6.0 NASA Internal and External Environments

Competency: 6.2 NASA PM/SE Procedures and Guidelines

Competency Area: 6.0 NASA Internal and External Environments