1. Information Technology
Solution Engineering/Engineering Process
Maturity
Product Integration
IRM 2.120.3
July 2015
Darren Toyer
Patrick McQuinn

2. Product Integration | Solution Engineering2
Agenda
• Training Objective
• Purpose
• Process Overview
• Procedure-level details
• Contact Information

3. Product Integration | Solution Engineering3
Training Objective
• To increase understanding of the Product Integration
(PI) process and its procedures

4. Product Integration | ITS4
Agenda
• Training Objective
• Purpose
• Process Overview
• Procedure-level details
• Contact Information
4 Product Integration | Solution Engineering

5. Product Integration | Solution Engineering5
Purpose
• The purpose of the Product Integration process is to
assemble the product from the Product components,
ensure that the Product, as integrated, behaves
properly (i.e., possesses the required functionality and
quality attributes), and deliver the Product.

6. Product Integration | Solution Engineering6
Agenda
• Training Objective
• Purpose
• Process Overview
• Procedure-level details
• Contact Information

7. Product Integration | Solution Engineering7
When PI Is Not Done Well…
• Sub-products do not operate together
• Increased integration test time
• The integration environment can be inadequate to
support the integration activities
• Products can be released without component
integration fully tested

8. Product Integration | Solution Engineering8
PI relationship to other processes – 1
• The PI Process is a mandatory process within the CMMI
Engineering Category (IRM 2.120.3)
• The Engineering process areas cover the development and
maintenance activities that are shared across engineering
disciplines
• Engineering processes are both recursive and iterative
• Recursive – Solves a problem by breaking up a task into
smaller and smaller pieces until it can be completed;
combine the results. e.g. Looping algorithms
• Iterative – repeating until a task is completed e.g. a loop
counter reaches a limit

9. Product Integration | Solution Engineering9
PI relationship to other processes – 2
The Product Integration process relies on:
• Requirements Management
• Identifying Interface requirements
• Derived requirements resulting from the selected components
• Technical Solution
• Government Equipment List (GEL)
• Design Specification Report (DSR)
• Interface Control Document (ICD)
• Define the interfaces and the integration environment
• Decision Analysis and Resolution procedure
• Make and document significant decisions
• Select the Integration sequence and environment

10. Product Integration | Solution Engineering10
The Product Integration process relies on:
• Software Testing, Standards, and Procedures
• Verification Process specific practices
• Validation process specific practices
• Component and Product Validation
• Configuration/Change Management
• Use of Configuration Items
• Managing changes
• IT Security management
• Establish Security criteria
• Establish procedures to evaluate Security
PI relationship to other processes – 3

11. Product Integration | Solution Engineering11
The Product Integration process relies on:
• Project Planning
• Provides information about establishing and maintaining
plans that define project activities.
• IT Operations Management
• Site preparation
• Product Installation
• Confirms correct operation of installed system
PI relationship to other processes – 4

12. Product Integration | Solution Engineering12
PI Process Flow Diagram

13. Product Integration | Solution Engineering13
Enterprise Life Cycle
• The execution of the Product Integration engineering
process normally occurs through a project’s passage
through the ELC
• The next few slides detail what is expected in each
ELC Phase to complete PI
PI Relationship to the ELC

14. Product Integration | Solution Engineering14
Prepare for Product Integration
Vision & Strategy/Enterprise Architecture Phase (Milestone 0)
• How do we plan to integrate what we are designing/building into
the existing production environment?
• SP 1.1 Establish an Integration Strategy
• SP 1.2 Establish the PI environment(s)
• Develop Solution Concept
Project Initiation (Milestone 1)
• Initial analysis, identification, & assessment of the existing product
and product components to be integrated & existing sequence for
integration
• SP 1.3 Establish PI Procedures & Criteria
• Develop Engineering Plan

15. Product Integration | Solution Engineering15
Prepare for Product Integration
(cont.)
Domain Architecture Phase (Milestone 2)
• Refine Integration Strategy in the Engineering Plan. How do we
integrate what we are designing/building into the existing
production environment? (Solution Concept)
• SP 1.1 Update and maintain the Integration Strategy
• SP 1.2 Update and maintain the PI environment(s)
• SP 1.3 Update and maintain the PI procedures & criteria
• Update Engineering Plan
Preliminary Design Phases (Milestones 3 & 4A)
• SP 1.1 Update and maintain the Integration Strategy
• SP 1.2 Update and maintain the PI environment(s)
• SP 1.3 Update and maintain the PI procedures & criteria
• Update Engineering Plan

16. Product Integration | Solution Engineering16
Ensure Interface Compatibility
Preliminary & Detailed Design Phases (Milestones 3 & 4A)
• Comprehensive examinations & review of internal & external
interfaces for completeness
• External Interfaces are defined to the physical level
• Review interfaces with stakeholder organizations
• Interfaces should be managed throughout the project lifecycle
• SP 2.1 Review Interface Description for Completeness
• SP 2.2 Manage Interfaces
• Develop and Update DSR & ICD

17. Product Integration | Solution Engineering17
Assemble the Product
Components & Deliver the Product
Milestone 4b: System Development Phase
• Generate final reports, prep integrated product solution for delivery to
the deployment site
• Deploy at the production site
• Integration Testing & Evaluation
• Ensure the product components are delivered to PI environment,
check & confirm components meet description
• SP 3.1 Confirm Readiness of Product Components for Integration
• SP 3.2 Assemble Product Components
• SP 3.3 Evaluate Assembled Product Components
• Develop the System Deployment Plan
• Develop the Test Plan
• Develop Delivery Documentation (VDDs and Transmittals)
• Develop Physical Configuration Audit
• Develop End-of-Test Completion Report

18. Product Integration | Solution Engineering18
Planned Maintenance Projects
Maintenance Projects Entering ELC at Milestone Phase 3
• If the project requires acquisition of HW to accomplish the
project’s objectives, adherence to the GEL and PI processes is
required
• Formal evaluations are required for adding new technologies,
new tools, or new products into the IRS IT environments
• Functional Equivalents may be utilized
• Requires an Integration Strategy or sequence
Maintenance Projects Entering ELC at Milestone Phase 4A
• Functional Equivalents may be utilized
• Requires an Integration Strategy or sequence
• No formal evaluations are required

19. PI Tailoring
• The Product Integration process step 1 may be tailored for
projects with modest integration need. These projects may
document an integration sequence with rationale instead
of developing and documenting a full Integration Strategy.
All other PI steps may not be tailored.
• All tailoring requests should be submitted in writing to
Solution Engineering via the Solution Engineering Front
Door.
Product Integration | Solution Engineering19

20. Product Integration | Solution Engineering20
PI’s Specific Goals

21. Product Integration | Solution Engineering21
PI Specific Practices – SG 1 & 2

22. Product Integration | Solution Engineering22
PI Specific Practices – SG 3

23. Product Integration | Solution Engineering23
PI Roles & Responsibilities 1/2
Role Description Definition of Responsibility
Lead Integrator Responsible for:
• Planning and executing the integration of product
components into a Product
Component Designer Responsible for:
• Integration of Product components into larger Product
components or into the final Product
• Management of component and sub-component
interfaces both internal and external
• Design of components and sub-components
• Developing all required design documentation
Stakeholder Responsible for:
• Ensuring the needs and concerns are considered
• These are the specific people or groups who have a
stake, or an interest, in the outcome of the project
• The stakeholders may be different for each step or
activity.

24. Product Integration | Solution Engineering24
PI Roles & Responsibilities 2/2
Role Description Definition of Responsibility
Developer Responsible for:
• Creating and /or modifying code
• Performing own unit testing on the created code and notifying
their lead integrator when unit testing is completed
• Documenting code
• Ensuring that all development work products are completed
Operations Personnel Responsible for:
• Site preparation
• Product Installation
• Confirms correct operation of installed system
Tester Responsible for:
• Defined verification tests against requirements
Security Responsible for:
• Security Requirements
• Security Criteria
• Security Procedures

25. Product Integration | Solution Engineering25
Agenda
• Training Objective
• Purpose
• Process Overview
• Procedure-level details
• Contact Information

26. Product Integration | Solution Engineering26
PI Process Steps
1. Prepare for Product Integration
2. Review Interface Descriptions for Completeness
3. Manage Interfaces
4. Confirm Readiness of Product Components for Integration
5. Assemble Product Components
6. Evaluate Assembled Product Components
7. Package and Deliver the Product or Product Component

27. Product Integration | Solution Engineering27
PI Step 1
Prepare for Product Integration
Roles: Lead Integrator, Component Designer, Stakeholder
Activities:
 Identify the Product components to be integrated.
 Identify the verifications to be performed during the integration of the Product
components. This identification includes verifications to be performed on
interfaces.
 Identify alternative Product component integration strategies. Developing an
Integration Strategy can involve specifying and evaluating several alternative
integration strategies or sequences.
 Select the best Integration Strategy.
 Periodically review the product Integration Strategy and revise as needed.
 Record the rationale for decisions made and deferred.
Outputs:
 Product Integration Strategy
 Waivers

28. Product Integration | Solution Engineering28
PI Step 1
Prepare for Product Integration

29. Product Integration | Solution Engineering29
PI Step 2
Review Interface Descriptions for
Completeness
Roles: Component Designer, Developer, Stakeholder
Activities:
 Review interface data for completeness and ensure
complete coverage of all interfaces
 Ensure that Product components and interfaces are marked
to ensure easy and correct connection to the joining Product
component
 Periodically review the adequacy of interface descriptions
Outputs:
 Categories of interfaces
 List of interfaces per category
 Mapping of the interfaces to the Product components and
the Product Integration environment

30. Product Integration | Solution Engineering30
PI Step2
Review Interface Descriptions for
Completeness

31. Product Integration | Solution Engineering31
PI Step 3
Manage Interfaces
Roles: Lead Integrator, Component Designer, Stakeholder
Activities:
 Identify the interfaces and the requirements that need to be managed
 Establish the organizational structure for the management of the interfaces
 Ensure the compatibility of the interfaces throughout the life of the Product
 Resolve conflict, noncompliance, and change issues
 Maintain a repository for interface data accessible to project participants
Outputs:
 Table of relationships among the Product components and the external environment
 List of agreed-to interfaces defined for each pair of Product components, when
applicable
 Reports from the interface control working group meetings or equivalent
 Action items for updating interfaces
 Application program interface (API)
 Updated interface description or agreement (ELC Documents: DSR and ICD)

32. Product Integration | Solution Engineering32
PI Step3
Manage Interfaces

33. Product Integration | Solution Engineering33
PI Step 4
Confirm Readiness of Product
Components for Integration
Roles: Component Designer, Developer, Stakeholder
Activities:
 Ensure that each received Product component meets its description
 Check the configuration status against the expected configuration
 Perform a pre-check (e.g., by a visual inspection, using basic
measures) of all the physical interfaces before connecting Product
components together
 Check security configurations of the Product components and the
integration environment
Outputs: Readiness is verified

34. Product Integration | Solution Engineering34
PI Step 4
Confirm Readiness of Product
Components for Integration

35. Product Integration | Solution Engineering35
PI Step 5
Assemble Product Components
Roles: Component Designer, Developer
Activities:
 Ensure the readiness of the Product Integration
environment
 Conduct integration in accordance with the Product
Integration strategy, procedures, and criteria
 Revise the Product Integration strategy, procedures,
and criteria as appropriate
Outputs:
 Assembled Product or Product components

36. Product Integration | Solution Engineering36
PI Step 5
Assemble Product Components

37. Product Integration | Solution Engineering37
PI Step 6
Evaluate Assembled Product Components
Roles: Lead Integrator, Component
Designer, Developer, Stakeholder
Activities:
 Conduct the evaluation of assembled
Product components following the
Product Integration test plans
 Record the evaluation results
Outputs:
 Exception reports
 Interface evaluation reports
 Product Integration summary reports

38. Product Integration | Solution Engineering38
PI Step 6
Evaluate Assembled Product Components

39. Product Integration | Solution Engineering39
PI Step 7
Package & Deliver the Product or
Product Components
Roles: Lead Integrator, Component Designer, Stakeholder, Operations
Personnel
Activities:
 Package and deliver the Product
 Prepare the operational site for product installation
 Install the Product at the operational site and confirm correct operation
 Deliver the Product and related documentation and confirm receipt
Outputs:
 Packaged Product or Product components
 Delivery documentation
 Transmittals
 Version Description Documents (VDDs)

40. Product Integration | Solution Engineering40
PI Step 7
Package & Deliver the Product or
Product Components

41. Product Integration | ITS41
Agenda
• Introduction
• Engineering Plan
• Process Overview
• Procedure-level details
• Contact Information
41 Product Integration | Solution Engineering

42. Product Integration | Solution Engineering42
Contact for
Product Integration Process