SE 2.0 Product Realization
SE 2.0 Product Realization
Delivering the completed system of interest that meets the design specifications and stakeholder expectations. This includes producing products; acquiring, reusing, or coding products; integrating products into higher-level assemblies; verifying products against design specifications; validating products against stakeholder expectations; and transitioning products to the next level of the system.
Select a competency from the outline menu or scroll down the page.
Categories and Competencies
SE 3.0 Technical Management
Common Competencies
C 1.0 NASA Internal and External Environments
C 2.0 Human Capital Management
C 3.0 Security, Safety, and Mission Assurance
C 4.0 Professional and Leadership Development
C 5.0 Knowledge Management
SE 2.1 Product Implementation
Generating a specific product through buying, making, or reusing so as to satisfy the design requirements. This includes preparing the implementation strategy; building or coding the product; reviewing vendor technical information; inspecting delivered, built, or reused products; and preparing product support documentation for integration.
Underlying Skills
- Clear verbal and written communications
- Effective application of NASA’s SE Engine
- Systems thinking
- Win-win negotiating
- Working in teams
Fundamental Knowledge of:
- Project mission, goals, and objectives
- Project Concept of Operations, use cases, and expected scenarios
- Existing suitable products that could be reused or purchased off-the-shelf
- The procurement organizations, processes, and contacts
- The manufacturing organizations, processes, and contacts
Explore proficiencies for each role.
Discipline EngineerProficiency Level
Participates as a team member to gain an overall understanding of the Product Implementation Process and to gain initial experience in the competency.
Participates as a team member to gain an overall understanding of the Product Implementation Process and to gain initial experience in the competency.
Illustrations
Discipline Engineers should be able to:
Discipline Engineers should be able to:
- Understand the Product Implementation Process.
- Understand the processes for product purchasing, manufacturing, and inspection.
- Participate as part of a team to perform market surveys, gather the status of activity progress, and review technical information.
Subsystem Lead
Proficiency Level
- Leads teams at the subsystem level in product implementation.
- Provides guidance and expertise at the subsystem level, identifying subsystem issues.
Illustrations
Subsystem Leads should be able to:
Subsystem Leads should be able to:
- Develop criteria for selecting the implementation strategy for review by the team.
- Collaborate with Subject Matter Experts to develop and review implementations of a product within a discipline.
- Review and identify incorrect technical information supplied for a product.
- Cooperate with acquisition and manufacturing teams to identify issues.
Project Systems Engineer
Proficiency Level
- Leads teams at the project level in product implementation.
- Provides guidance and expertise at the project level, resolving project issues.
Illustrations
Project Systems Engineers should be able to:
Project Systems Engineers should be able to:
- Lead the team in developing implementation strategies.
- Identify inconsistencies across received products and associated technical information.
- Coordinate reviews of technical information or product compliance.
- Direct development or acquisition of enabling products.
- Cooperate with organizational points of contact to identify and resolve issues in procurement or manufacturing.
- Direct and make recommendations for acceptance of the product.
Chief Engineer
Proficiency Level
Leads overall effort, reviews and approves products, resolves issues, and maintains relationships with the highest level internal, external, and international contacts.
Leads overall effort, reviews and approves products, resolves issues, and maintains relationships with the highest level internal, external, and international contacts.
Illustrations
Chief Engineers should be able to:
Chief Engineers should be able to:
- Manage the overall effort.
- Approve final results.
- Provide guidance and mentoring in the product implementation efforts of the team.
- Collaborate with other centers or external organizations to obtain agreements.
- Resolve complex issues in the procurement or manufacturing of the product.
- Identify, describe, and define product implementation policies for the agency and/or center.
SE 2.2 Product Integration
Assembling and integrating lower-level validated end products into the desired end product of the higher-level product. This includes preparing the product integration strategy, performing detailed planning, obtaining products to integrate, confirming that the products are ready for integration, preparing the integration environment, and preparing product support documentation.
Underlying Skills
- Clear verbal and written communications
- Effective application of NASA’s SE Engine
- Systems thinking
- Win-win negotiating
- Working in teams
Fundamental Knowledge of:
- Project mission, goals, and objectives
- Project Concept of Operations, use cases, and expected scenarios
- Capabilities of internal and external facilities for integration
- Assembly tools and processes
Explore proficiencies for each role.
Discipline EngineerProficiency Level
Participates as a team member to gain an overall understanding of the Product Integration Process and to gain initial experience in the competency.
Participates as a team member to gain an overall understanding of the Product Integration Process and to gain initial experience in the competency.
Illustrations
Discipline Engineers should be able to:
Discipline Engineers should be able to:
- Understand the processes for product integration.
- Participate as part of a team to gather the status of activity progress.
- Review technical information.
Subsystem Lead
Proficiency Level
- Leads teams at the subsystem level in product integration.
- Provides guidance and expertise at the subsystem level, identifying subsystem issues.
Illustrations
Subsystem Leads should be able to:
Subsystem Leads should be able to:
- Develop procedures for simple product integration for review by the team.
- Collaborate with Subject Matter Experts to participate in the integration of products within a discipline.
- Review and identify incorrect technical information supplied for a product.
- Collaborate with integration teams to identify and resolve subsystem issues.
Project Systems Engineer
Proficiency Level
- Leads teams at the project level in product integration.
- Provides guidance and expertise at the project level, resolving project issues.
Illustrations
Project Systems Engineers should be able to:
Project Systems Engineers should be able to:
- Lead the team in developing integration strategies for complex projects.
- Identify inconsistencies across assembled products and associated technical information.
- Collaborate with organizational points of contact to identify and resolve internal issues during integration.
- Direct and make recommendations for acceptance of the assembled product.
Chief Engineer
Proficiency Level
Leads overall effort, reviews and approves products, resolves issues, and maintains relationships with the highest level internal, external, and international contacts.
Leads overall effort, reviews and approves products, resolves issues, and maintains relationships with the highest level internal, external, and international contacts.
Illustrations
Chief Engineers should be able to:
Chief Engineers should be able to:
- Manage the overall effort.
- Approve final results.
- Provide guidance and mentoring in the product integration efforts of the team.
- Cooperate with other centers or external organizations to obtain agreements.
- Resolve complex issues arising during integration.
- Identify, describe, and define product integration policies for the agency and/or center.
SE 2.3 Product Verification
Proving the end product conforms to its requirements. This includes preparing for the verification efforts, analyzing the outcomes of verification (including identifying anomalies and establishing recommended corrective actions), and preparing a product verification report providing evidence of product conformance with the applicable requirements.
Underlying Skills
- Clear verbal and written communications
- Effective application of NASA’s SE Engine
- Systems thinking
- Working in teams
- Win-win negotiating
Fundamental Knowledge of:
- Project mission, goals, and objectives
- Project Concept of Operations, use cases, and expected scenarios
- Requirements for each product being verified
- Capabilities of internal and external facilities for verification
- Verification tools and processes
- Anomaly/discrepancy and corrective action process
Explore proficiencies for each role.
Discipline EngineerProficiency Level
Participates as a team member to gain an overall understanding of the Product Verification Process and to gain initial experience in the competency.
Participates as a team member to gain an overall understanding of the Product Verification Process and to gain initial experience in the competency.
Illustrations
Discipline Engineers should be able to:
Discipline Engineers should be able to:
- Understand the processes for product verification.
- Participate as part of a team to define verification activities.
- Gather the status of activity progress.
- Review verification reports.
Subsystem Lead
Proficiency Level
- Leads teams at the subsystem level in product verification.
- Provides guidance and expertise at the subsystem level, identifying subsystem issues.
Illustrations
Subsystem Leads should be able to:
Subsystem Leads should be able to:
- Develop procedures for simple product verification for review by the team.
- Work with Subject Matter Experts to participate in the verification of products within a discipline.
- Review and identify discrepancies between verification results and requirements.
- Work with verification teams to identify issues.
- Propose corrective actions.
Project Systems Engineer
Proficiency Level
- Leads teams at the project level in product verification.
- Provides guidance and expertise at the project level, resolving project issues.
Illustrations
Project Systems Engineers should be able to:
Project Systems Engineers should be able to:
- Lead the team in developing verification strategies for complex projects.
- Look for inconsistencies across verified products and associated verification results and configurations.
- Obtain verification enabling products.
Coordinate reviews to determine the completeness of verification activities. - Work with organizational points of contact to identify and resolve internal issues during verification.
- Direct and make recommendations for corrective actions for products that don’t meet the requirements.
Chief Engineer
Proficiency Level
Leads overall effort, reviews and approves products, resolves issues, and maintains relationships with the highest level of internal, external, and international contacts.
Leads overall effort, reviews and approves products, resolves issues, and maintains relationships with the highest level of internal, external, and international contacts.
Illustrations
Chief Engineers should be able to:
Chief Engineers should be able to:
- Manage the overall effort.
- Approve final results.
- Provide guidance and mentoring in the product verification efforts of the team.
- Work with other centers or external organizations to obtain agreements.
- Resolve complex issues arising during verification.
- Identify, describe, and define product verification policies for the agency and/or center.
SE 2.4 Product Validation
Confirming that a verified end product satisfies the stakeholder expectations for its intended use when placed in its intended environment and ensuring that any anomalies discovered during validation are appropriately resolved prior to product transition. This includes preparing to conduct product validation, performing the product validation, analyzing the results of validation (including identifying anomalies and establishing recommended corrective actions), and preparing a product validation report providing evidence of product conformance with the stakeholder expectations baseline.
Underlying Skills
- Clear verbal and written communications
- Effective application of NASA’s SE Engine
- Systems thinking
- Working in teams
- Win-win negotiating
Fundamental Knowledge of:
- Project mission, goals, and objectives
- Project Concept of Operations, use cases, and expected scenarios
- Expectations and intended environment for each product being validated
- Capabilities of internal and external facilities for validation
- Validation tools and processes
- Anomaly and corrective action process
Explore proficiencies for each role.
Discipline EngineerProficiency Level
Participates as a team member to gain an overall understanding of the product validation process and to gain initial experience in the competency.
Participates as a team member to gain an overall understanding of the product validation process and to gain initial experience in the competency.
Illustrations
Discipline Engineers should be able to:
Discipline Engineers should be able to:
- Understand the processes for product validation.
- Participate as part of a team to define validation activities.
- Gather the status of activity progress.
- Review validation reports.
Subsystem Lead
Proficiency Level
- Leads teams at the subsystem level in product validation.
- Provides guidance and expertise at the subsystem level, identifying subsystem issues.
Illustrations
Subsystem Leads should be able to:
Subsystem Leads should be able to:
- Develop procedures for simple product validation for review by the team.
Work with Subject Matter Experts to participate in the validation of products within a discipline. - Review and identify differences between validation results and expectations.
- Collaborate with validation teams to identify issues.
- Propose corrective actions.
Project Systems Engineer
Proficiency Level
- Leads teams at the project level in product validation.
- Provides guidance and expertise at the project level, resolving project issues.
Illustrations
Project Systems Engineers should be able to:
Project Systems Engineers should be able to:
- Lead the team in developing validation strategies for complex projects.
- Identify inconsistencies across validated products and associated validation results and configurations.
- Obtain validation enabling products.
- Coordinate reviews to determine the completeness of validation activities.
- Cooperate with organizational points of contact to identify and resolve internal issues during validation.
- Direct and make recommendations for corrective actions for products that don’t meet expectations.
Chief Engineer
Proficiency Level
Leads overall effort, reviews and approves products resolves issues, and maintains relationships with the highest of internal, external, and international contacts.
Leads overall effort, reviews and approves products resolves issues, and maintains relationships with the highest of internal, external, and international contacts.
Illustrations
Chief Engineers should be able to:
Chief Engineers should be able to:
- Manage the overall effort.
- Approve final results.
- Provide guidance and mentoring in the product validation efforts of the team.
- Work with other centers or external organizations to obtain agreements.
- Resolve complex issues arising during validation.
- Identify, describe, and define product validation policies for the agency and/or center.
SE 2.5 Product Transition
Transitioning the verified and validated product to the customer at the next level in the system structure. This includes preparing to conduct product transition, evaluating the product and enabling product readiness for product transition, preparing the product for transition (including handling, storing, and shipping preparation), preparing sites, and generating required documentation to accompany the product.
Underlying Skills
- Clear verbal and written communications
- Effective application of NASA’s SE Engine
- Systems thinking
- Working in teams
- Win-win negotiating
Fundamental Knowledge of:
- Project mission, goals, and objectives
- Project Concept of Operations, use cases, and expected scenarios
- Shipping and handling methods and procedures
- Capabilities of internal and external facilities and capabilities for transitioning a product
- Process for identification and resolution of shipping/handling issues
Explore proficiencies for each role.
Discipline EngineerProficiency Level
Participates as a team member to gain an overall understanding of the product transition process and to gain initial experience in the competency.
Participates as a team member to gain an overall understanding of the product transition process and to gain initial experience in the competency.
Illustrations
Discipline Engineers should be able to:
Discipline Engineers should be able to:
- Understand the processes for product transition.
- Participate as part of a team to perform facility surveys.
- Gather the status of activity progress.
- Review product documentation.
Subsystem Lead
Proficiency Level
- Leads teams at the subsystem level in product transition.
- Provides guidance and expertise at the subsystem level, identifying subsystem issues.
Illustrations
Subsystem Leads should be able to:
Subsystem Leads should be able to:
- Develop procedures for simple product transitioning for review by the team.
- Work with Subject Matter Experts to participate in the transitioning of products within a discipline.
- Review and identify transition issues.
- Propose corrective actions.
Project Systems Engineer
Proficiency Level
- Leads teams at the project level in product transition.
- Provides guidance and expertise at the project level, resolving project issues.
Illustrations
Project Systems Engineers should be able to:
Project Systems Engineers should be able to:
- Lead the team in developing transition strategies for complex projects.
- Identify inconsistencies between planned product security needs and selected transitioning strategies, procedures, and configurations.
- Coordinate reviews to determine the readiness for transition.
- Work with organizational points of contact to identify and resolve internal issues during the transition.
- Direct and make recommendations for corrective actions for issues arising from shipping or handling.
Chief Engineer
Proficiency Level
Leads overall effort, reviews and approves products, resolves issues, and maintains relationships with the highest level internal, external, and international contacts.
Leads overall effort, reviews and approves products, resolves issues, and maintains relationships with the highest level internal, external, and international contacts.
Illustrations
Chief Engineers should be able to:
Chief Engineers should be able to:
- Manage the overall effort.
- Approve final results.
- Provide guidance and mentoring in the product transition efforts of the team.
- Work with other centers or external organizations to obtain agreements.
- Resolve complex issues arising during the transition.
- Identify, describe, and define product transition policies for the agency and/or center.