1. DRAFT_LT2_CPM_SOW_16_December_v0_3_3

PEO-STRI-08-W025

W900KK-08-X-XXXX

16 December 2008 Version 0.3.3

PEO-STRI-08-W025

W900KK-08-X-XXXX

16 December 2008 Version 0.3.3

STATEMENT OF WORK

FOR THE

LIVE TRAINING TRANSFORMATION (LT2)

CONSOLIDATED PRODUCT-LINE MANAGEMENT

(CPM) IMPLEMENTATION

Prepared by:

Program Executive Office Simulation, Training and Instrumentation (PEO STRI)

12350 Research Parkway

Orlando, Florida 32826-3276

REVISION LOG

TABLE OF CONTENTS

21.0. Scope.

21.1. Purpose.

21.2. Background.

22.0. Applicable Documents.

22.1. Department of Defense Directives.

22.2. Availability of Department of Defense Directives.

22.3. Other Government Documents, Drawings, and Publications.

22.4. Availability of Other Government Documents, Drawings and Publications.

22.5. Order of Precedence.

23.0. Requirements.

23.1. LT2 CPM

23.1.1. LT2 CPM Design.

23.1.2. LT2 CPM Implementation.

23.1.2.1. LT2 CPM Processes.

23.1.2.2. LT2 CPM Training.

23.1.3. LT2 CPM Sustainment.

23.1.3.1. LT2 CPM Information Technology Sustainment.

23.1.3.2. Fielded Product Line Support.

23.1.3.3. Integration Lab.

23.2. LT2 CPM Activities.

23.2.1. Core Asset Development and Sustainment Activity.

23.2.2. Product Development Support Activity.

23.2.2.1. Product Line Obsolescence Management.

23.2.2.2. CPM Help Desk.

23.2.3. Management Activity.

23.2.4. Configuration Management Activity.

23.2.5. Technology Insertion/Refresh Activity.

23.3. Program Management.

23.3.1 Integrated Product Team (IPT).

23.3.2. Program Reviews.

23.3.2.1. Technical Design Review (TDR).

23.3.2.2. Technical Interchange Meetings (TIMs).

23.3.2.3. Management Reviews.

23.3.3. Program Schedule.

23.3.4. Contract Invoicing and Payment.

23.3.5. Cost-Plus Financial Reporting.

23.3.6. Earned Value Management System (EVMS).

23.3.7. Associate Contractor Agreements (ACA).

23.3.8 Risk Management.

23.3.9. Contractor Work Breakdown Structure (CWBS).

23.4. System Engineering.

23.4.1. System Baseline.

23.4.2. Information Assurance.

23.4.2.1. Automated Information System (AIS) Security.

23.4.2.2. Information Assurance Vulnerability Alert (IAVA).

23.4.2.3. Information Assurance Training.

23.4.2.4. Department of Defense Certification and Accreditation Process (DIACAP) Support.

23.4.3. Engineering Change Proposal (ECP).

23.4.4. Quality Assurance (QA).

23.4.5. System Verification.

23.4.5.1. Early System Integration Platform and Demonstration.

23.4.5.2. Test and Verification.

23.4.6. Software Engineering.

23.4.6.1. Software Design.

23.4.7. Configuration Management.

23.4.8. Product Definition Data (PDD).

23.5. Logistic Management.

23.5.1. Maintenance Support Strategy.

23.5.2. Technical Publications.

23.5.2.1. Validation.

23.5.2.2. Publications In Process Reviews (IPRs).

23.5.3. Training Course.

23.5.3.1. Training Classes.

23.5.3.2. Course Completion Criteria.

23.5.4. Unique Identification (UID) of Tangible Items.

23.6. CPM Transition Planning.

2Appendix A

2Definition of Terms

2Appendix B

2Core CPM Capabilities

2Appendix C

2Core CPM Functionalities

2Appendix D

2CPM Work Breakdown Structure

2Appendix E

2CPM Concept Paradigm

STATEMENT OF WORK

FOR THE

LIVE TRAINING TRANSFORMATION (LT2)

CONSOLIDATED PRODUCT LINE MANAGEMENT

(CPM) IMPLEMENTATION

1.0. Scope.

This Statement of Work (SOW) defines the work efforts for the design, prototyping, development, integration, verification, operations, and maintenance of the LT2 product line across live training under the Consolidated Product-line Management (CPM) strategy, to include the necessary processes and procedures to implement the CPM strategy. This SOW also defines the work efforts for the implementation, maturation, technology insertion and life cycle controls associated with the real-time instantiations of the CPM strategy; this includes but is not limited to the maturation and development the Common Training Instrumentation Architecture (CTIA), LT2 components, synchronization of components and fielded as-built configurations, configuration management of components, and maintaining concurrency of existing product line components/technology with state-of-the-art technologies and processes.

1.1. Purpose.

PM TRADE’s Consolidated Product-Line Management (CPM) is the integration of several disparate processes into a unified effort. Consolidated does not equate to centralized. PM TRADE and the Product Managers (PdM) have the mission of managing the configuration baseline of systems throughout the total life cycle to ensure the integrity of the product line and to ensure systems remain relevant to emerging systems, evolving requirements, and changing technology.

The process by which the Project Manager (PM)/Product Manager (PdM) manages products must be deliberate, disciplined and coordinated in order to: maximize re-use of components and products in the development of new systems, synchronize the production of products to gain efficiencies, facilitates technology refresh and obsolescence/retrofit efforts, enable supporting efforts, and maintain seamless interoperability between components, products and systems. CPM is the framework by which PM/PdM can achieve these elements and execute control of a system’s life cycle to maximize the commonality, reuse and interoperability of the system while maintaining integrity of the product lines from which it is based. CPM encompasses that deliberate process for managing the development, production, and sustainment of PM products. It enables managers to maintain visibility and control of the configuration of those systems for which they are responsible throughout the life cycle of that system.

1.2. Background.

The LT2 CPM is a consolidation product line based configuration management construct. The LT2 CPM is focused on Product Lines and configuration of common components and product builds associated with the Product Lines. The LT2 CPM must consider the existing solutions and components within CTIA, Future Army System of Integrated Targets (FASIT), One Tactical Engagement Simulation System (OneTESS), etc, as well as emerging components. The LT2 CPM must support technology insertion, technology refreshment, experimentation, plan for obsolescence, and prototype development of components and subsystems as related to the various LT2 architectures and live training systems.

CPM may be the mechanism to support the live product line approach into overarching Army initiatives, such as, the Live-Virtual-Constructive Integrating Architecture (LVC-IA) and Future Immersive Training Environment (FITE). CPM may include the initiatives to facilitate the Army’s live component of the LVC-IA and the Joint Capabilities Technology Demonstration (JCTD) for FITE.

2.0. Applicable Documents.

The following documents of issue shown on the Document Summary List (DSL) form a part of this SOW to the extent specified herein.

2.1. Department of Defense Directives.

DIACAP

Interim Department of Defense (DOD) Certification and Accreditation (C&A) Process (DIACAP) Guidance

DOD 8570.01 M

Information Assurance Workforce Improvement Program

DODD 8500.1

Information Assurance

DODI 8500.2

Information Assurance (IA) Implementation

2.2. Availability of Department of Defense Directives TC "2.2 Availability of Department of Defense Directives" \f C \l "1" .

Copies are available on the WWW at URL: http://www.dtic.mil/whs/directives/

2.3. Other Government Documents, Drawings, and Publications.

AR25-2

IA

CTIA

Common Training Instrumentation Architecture (www.lt2portal.org)

LT2-MGMT-04-0001

Live Training Transformation (LT2) Product Line Management Concept of Operations (PLM CONOPS) (www.lt2portal.org)

MIL-DTL-31000

Technical Data Packages

MIL-STD-40051-2

Preparation of Digital Technical Information for Page-Based Technical Manuals

MIL-PRF-49506

Logistics Management Information

MIL-STD-130

Unique Identification (UID) of Tangible Items

2.4. Availability of Other Government Documents, Drawings and Publications.

Copies of the documents are available form PEO STRI, SFAE-STRI-K-L, 12350 Research Parkway, Orlando, FL 32826, or may be available at: http://assist.daps.dla.mil/quicksearch/

2.5. Order of Precedence.

In the event of a conflict between the text of this SOW and the references cited herein, the text of the SOW shall take precedence.

3.0. Requirements.

The work tasks described in the Statement of Work are intended to address the Core Functionalities of the CPM, however it is envisioned that individual program/product efforts may instantiate some or all of these functionalities for the fulfillment of their individual programmatic requirements. The Government’s expectation is that all instantiations and efforts completed under the CPM contract shall be consistent and synchronized with the Core Functions. Individual programmatic requirements shall be addressed within separate Delivery Orders placed on the CPM IDIQ contract, and have their own Statements of Work.

3.1. LT2 CPM

You shall perform all of the required tasks necessary to design, implement, and sustain the LT2 CPM construct for all of the LT2-Family of Training System (FTS) products, components, and architectures. You shall ensure that the LT2 CPM construct is inherently consistent with the LT2 Portal and supports real-time access/update to the LT2 component data.

3.1.1. CPM Design.

You shall design, develop, integrate and verify the CPM construct to fulfill the Core CPM Capabilities (ref Appendix B), Functionalities (ref Appendix C) and CPM Activities (sec 3.2 of this SOW). You shall ensure that the CPM construct is consistent with all applicable Information Assurance requirements, and if required, support the obtainment of appropriate IA certifications and approvals.

You shall facilitate a structured process/method to ensure early discovery of stakeholders driving requirements and/or quality attributes for CPM, and utilize this data for architecture, process, and application focus and improvement efforts (i.e., optimize CPM design and implementation).

3.1.2. CPM Implementation.

You shall implement and instantiate CPM for all LT2-Family of Training System (FTS) products, components, and architectures. You shall develop, document, and instantiate the processes to support the implementation of Core CPM Capabilities and Activities, both for current elements (components, products, and architectures) contained within CPM, and for the development/insertion of new elements.

3.1.2.1. CPM Optimization.

You shall conduct a formal attribute driven structured and reiterative process (at least yearly) to assess the effectiveness of the CPM implementation and instantiate corrective action changes. This process shall consider a decomposition of processes, design, implementation and architecture of the CPM.

3.1.2.2. CPM Processes.

You shall conduct an analysis of the current business practices relative to CPM (utilized by the Government and the current CTIA contractor) and conduct a gap analysis between the current and end state processes. You shall identify and document the operating processes to define roles, responsibilities, and mechanisms inherent to the implementation of the CPM construct. You shall include in the analysis the processes for management of change requests, problem reports, and engineering change proposals; for both developmental and fielded components and products.

The process analysis shall focus on Configuration Change Board (CCB) and overarching Configuration Management (CM) processes and common component agreement. The CCB processes shall consider both baseline impact changes as well as non-baseline impact changes. The CM processes shall consider proactive obsolescence execution; both as a forcing function to move existing baselines to latest configuration components, and a mechanism to identify where obsolescence will impact/hinder the entirety of the product line within CPM.

You shall conduct iterative assessments of the processes to ensure they remain relevant and up to date (consistent with technology and usage of CPM).

3.1.2.3. LT2 CPM Training.

You shall conduct an analysis of the CPM functions and mechanisms (tools) and develop appropriate Computer Based Training (CBT) modules to be hosted on the LT2 Portal. These modules shall be stand-alone, and provide step-by-step instruction for the completion of common tasks and efforts associated with the management and running of the CPM. You shall coordinate with the Government on the level of CBT required for each training elements, and provide a combination of Level 1 and Level II CBT. The CBT shall provide a student assessment at the end of each training module to certify student mastery of the objectives.

You shall develop and provide periodic in-class training for the CPM. The in-class training shall include two separate elements, one focused on overarching familiarization and management of the CPM, the other focused on the technology use-case and development execution aspects of the CPM. You shall update and provide periodic in-class and on-line training for LT2 familiarization and component development. These classes shall be linked to the CPM training and execution methods. (Ref sec 3.5.3 for further delineation of requirements)

3.1.3. LT2 CPM Sustainment.

You shall support component development and maturation, to include the Common Training Instrumentation Architecture (CTIA) and other developed and maintained common components, utilizing the CPM construct. You shall utilize defined Systems and Software Engineering requirements. You shall support, refine, and develop existing LT2 elements to allow for technology refresh and insertion into CPM. You shall ensure synchronization of the LT2 CPM construct with the work efforts/products from WarFighter Focus in the maintenance of the various product-lines and architectures.

3.1.3.1. LT2 CPM Information Technology Sustainment.

You shall sustain the Information Technology (IT) components and infrastructure that support the operations of the CPM. You shall synchronize these efforts (as applicable) with the appropriate Information Assurance requirements and constraints of the Government’s IT components. These efforts shall include the sustainment, modernization, and disposal of all IT elements required to operate the CPM.

You shall maintain, operate, synchronize, and refresh the LT2 Portal to align to the operation needs and requirements of the CPM, to allow users access to software, products, documentation, configuration information, or other data/metadata required within the CPM construct. You shall maintain and update the LT2 CPM Portal Engine as a separate entity from the CPM construct, to support utilization by other organizations.

3.1.3.2. Fielded Product Line Support.

You shall provide technical, CM, and management support for fielded/deployed elements of the LT2 FTS product line via CPM functionalities. These efforts shall include integration support, interoperability support, site acceptance support, and demonstration/experimentation support. You shall conduct engineering assessment and provide implementation plans to support the release of new components, products, and architectures.

You shall conduct analyses of CPM components, products, and architectures and provided assessments as to change/maturation impacts of the components, products, and architectures. These assessments shall include the cost trade off between maintaining multiple versions of components and product baseline vice cost of maturing older systems/products to the latest releases.

3.1.3.3. Integration Lab.

You shall establish, maintain, and run a core integration lab associated with the operations and sustainment of the CPM and associated Common Components. This lab shall be utilized to ensure operational stability of the components, stability/accuracy of the interfaces, and assessment impacts of changes associated with other components within the Product Line. The Core Integration Lab shall provide support to the Help Desk, and ensure synchronization with the CM and Management Activities. The Integration lab shall also support the common component development, technology insertion, and obsolescence remediation execution. You shall instantiate (as required) integration labs, or extend the Core integration lab to support individual products to ensure timely support and execution of changes to maintain operational readiness of the products. Individual labs may have the requirements for classified processing and execution.

3.2. LT2 CPM Activities.

You shall apply iterative processes to support Core Asset Development and Sustainment, Product Development Support, and Management activities in the design, implementation, and sustainment of the CPM construct. You shall apply an overarching Configuration Management activity across all LT2 CPM activities, components and elements. You shall apply (as required) processes to support Technology Insertion and Refresh activities while maintaining the product line integrity of the CPM construct activities, components and elements.

3.2.1. Core Asset Development and Sustainment Activity.

You shall materially participate in the core asset development activity, which includes the development and support for products, support/updates for preexisting assets, product line scope, and core asset base definition. These activities shall include software development, component definition and development, CM tracking, new component opportunities, component transition from development to sustainment phase to include merging of enhancements and software fixes across multiple product baseline, and production planning of components into LT2 products.

3.2.1.1. Interoperability.

You shall design, implement, test and integrate any enhancements required to establish an interface between core assets and external systems. You shall ensure that the interface support conversions of the data and that no fidelity is lost in the conversion. You shall ensure that the design supports live, virtual, and constructive simulation interoperability.

3.2.1.2. Reusability.

You shall perform a continuous assessment of existing software components from commercial and Department of Defense repositories, legacy systems, and other available sources for potential reuse in the LT2 Product Line as core assets. You shall investigate the reuse of the CTIA compliant software components for multiple products or components.

3.2.1.3. Extensibility.

You shall develop and maintain an extensible architecture that will enable applications to be easily upgraded or modified to support additional requirements with minimal system perturbation.

3.2.1.4. Malleability.

You shall create and maintain an architecture that is flexible and robust to allow responsiveness to changing technology and requirements.

3.2.1.5. Information Assurance.

You shall develop, modify, and maintain all core asset software to the Common Training Instrumentation Architecture (CTIA) Development Environment Certification process to ensure Information Assurance worthiness of the resultant components.

3.2.2. Product Development Support Activity.

You shall materially participate in the Product Development Support activity as required to support the maturation, reuse, and integration of common components with respect to implementation in programs utilizing the product line elements. These activities shall be synchronized with the Core Asset Development and Sustainment activities. These activities shall include feedback mechanisms into the product line processes, and CM tracking of core assets. These activities shall also include software development and integration, performance testing, and coordination with prime system contractors.

3.2.2.1. Architecture Verification.

You shall perform architecture verification through life of the CPM. During development of the initial CPM the architecture shall be verified through a combination of the following:

· Formal and informal reviews.

· Analysis of architecture.

· Architecture metric collection (both programmatic and technical) and analysis.

· Application of static and dynamic modeling.

The analysis of architectural tradeoffs shall follow the guidelines defined by the Software Engineering Institute.

3.2.2.2. Information Assurance.

You shall develop, modify, and maintain all core asset software to the Common Training Instrumentation Architecture (CTIA) Development Environment Certification process to ensure Information Assurance worthiness of the resultant components.

3.2.2.3. Product Line Obsolescence Management.

You shall conduct proactive processes to identify, manage, and execute an obsolescence mitigation plan to reduce overall risk (technical, cost, and schedule), and maintain the overall LT2 FTS Product Line and CPM. You shall establish an iterative process to implement the obsolescence management to include total ownership impact assessments and recommendations to the Government.

3.2.2.4. CPM Help Desk.

You shall implement and sustain a CPM Help Desk. The Help Desk shall act as a single point of entry into the CPM for problem identification and support. The Help Desk shall be supported by the Configuration Management and Management Activities to synchronize sustainment and development efforts for common components and product line elements.

You shall instantiate instances of the Help Desk (as required), or extend Help Desk functionalities to support individual fielded products to ensure timely support and execution of changes to maintain operational readiness of the individual fielded products. You shall instantiate processes for handling emergency/exception changes to Common Components and maintained elements for post inclusion into the CPM.

3.2.2.5. Test Readiness Reviews.

You shall support and participate in Test Readiness Reviews (TRR) for supported programs under the Product Development Support Activity. The support shall include assessment on readiness of the common components or product line elements to enter test.

3.2.3. Management Activity.

You shall implement proactive management processes and resources at both the technical and organizational levels to support the product line efforts. The management shall identify production constraints, funding models, tracking of product line evolution, communication between activities, and risk management. The management processes shall include mechanisms and support for the multi-program adjudication of priorities and architectural impacts as related to the common components and central repository.

3.2.4. Configuration Management Activity.

You shall implement Configuration Management (CM) to establish and maintain the integrity of the components, products, and elements throughout the Product Line life cycle. CM shall be initiated at the onset of the contract, and implemented throughout the entire period of execution for all components, products, and elements of the product line. CM shall be a proactive activity within the CPM construct. CM shall identify, track, and document configuration items; control the configuration items and changes to them; and record and report status and change activities to these configuration items.

The CPM CM shall function as a multidimensional version of a typical CM process (multi-phased, multi-program, multi-tiered, multi-instantiated, and multi-baseline), acting as a bind between the CPM products and activities. The CPM CM shall support parallel development, distribution, and build releases. The CPM CM shall address use by all developers and products. The CPM CM shall:

· Identify the configuration items, components, and related work products that will be placed under configuration management.

· Establish and maintain a configuration management and change management system for controlling work products.

· Create or release baselines for internal use and for delivery to the customer.

· Track change requests for the configuration items.

· Control changes in the content of configuration items.

· Establish and maintain records describing configuration items.

· Perform configuration audits to maintain the integrity of the configuration baselines.

3.2.5. Technology Insertion/Refresh Activity.

You shall support, as directed, new technology development and insertion into the product line and components, or technology refresh of existing product line elements and components. These efforts shall include all necessary activities to synchronize, deploy, sustain, and track the new/updated elements of the product line. These activities, when exercised, must align with the core CPM activities noted above. These activities shall include software development, standards evolution development, hardware research and development, software integration, trade-off studies/analyses, prototype development, design of experiments, experimentation support, compliance testing, component agreement development, documentation, training, and coordination.

3.3. Program Management.

You shall provide overall program management and administrative support to ensure the requirements of the contract are accomplished. You shall develop, maintain, and integrate an overall integrated master plan for the execution of the CPM. You shall monitor and track key cost, schedule performance, and supportability metrics on a monthly basis, and notify the government of any issues and concerns that arise. Metrics are to be tracked for the program as a whole (per contract). You shall track and maintain resources to ensure overall programmatic performance.

3.3.1 Integrated Product Team (IPT) TC "3.2.2. Integrated Product Teams (IPTs)" \f C \l "1" .

You shall materially participate, provide membership, and assume leadership/management roles (as coordinated with the Government) throughout the various Integrated Product Teams required for the LT2 CPM execution.

3.3.2. Program Reviews TC "3.2.3. Program Reviews" \f C \l "1" .

You shall attend and conduct the program reviews. The reviews shall provide a forum for IPT members to clarify integration, installation, and management issues. You shall provide meeting minutes, document action items, coordinate resolutions, and track action items until closure.

3.3.2.1. Technical Design Review (TDR) TC "3.2.3.1 Preliminary Design Review (PDR)" \f C \l "1" .

You shall conduct, as appropriate, a Technical Design Review (TDR) to demonstrate the construct for the LT2 CPM. The TDR shall be a formal technical review of the basic design approach, the allocated baseline, and changes made to the allocated baseline. The TDR shall cover the progress and technical adequacy of the selected design approach. The TDR shall allow the Government to evaluate the technical risk associated with the selected design approach. The TDR shall include a functional diagram, design standards and logistical considerations (including training and manuals), and interference analysis. You shall, as required, conduct a limited verification demonstration to verify the system’s ability to fulfill operational requirements. The demonstration shall allow the government to verify the operational status of the system. The demonstration shall allow early system feedback and highlight areas of performance concerns. The TDR shall be satisfied upon successful demonstration of the CPM construct.

3.3.2.2. Technical Interchange Meetings (TIMs) TC "3.2.3.3 Technical Interchange Meetings (TIMs)" \f C \l "1" .

You shall support Technical Interchange Meetings (TIMs) as required during the execution of CPM. A TIM shall address specific technical or programmatic topics or issues during the design, implementation and sustainment of CPM. The TIMs shall include (but not limited too) topics such as developmental issues and solutions, functions and processes of working groups, or coordination of technical or training publications.

TIMs shall be utilized to support business case analyses with respect to programs decision making on leveraging an existing component or pursuing COTS, or GOTS, or custom development based on the data from the CPM and CM activity.

3.3.2.3. Management Reviews.

You shall conduct periodic program reviews of you management, subcontractor management, and vendors to ensure adequate coverage and responses to the requirements of the CPM. You shall ensure proper oversight and management of subcontractors in the execution of their assigned responsibilities and functions. You shall ensure the CPM team functions as a comprehensive whole. You are responsible for providing visibility on the progress, performance, and status of major subcontractors.

3.3.3. Program Schedule TC "3.2.4. Program Schedule" \f C \l "1" .

You shall develop and maintain a schedule that shows planned efforts to achieve each significant accomplishment, LT2-FTS program synchronization relative to component and baseline releases, and events relating to the program. You shall generate and maintain an Integrated Master Schedule (IMS), to include child schedules, of the core and non-core activities required to execute CPM. (DI-MISC-81183A)

3.3.4. Contract Invoicing and Payment TC "3.2.5 Contract Invoicing and Payment" \f C \l "1" .

You shall document and track the status of all appropriated funds associated with the contract to include payments, cancellations and invoices against each contract line item and sub-line item. (DI-MGMT-81651)

3.3.5. Cost-Plus Financial Reporting.

You shall plan, budget, schedule, and control the resources allocated to meet the requirements of the contract. You shall document and track the status of all appropriated funds associated with the contract to include payments, cancellations and invoices against each contract line item and sub-line item. You shall create and maintain a resource loaded, detail schedule that contains critical paths and predecessors to allow for what if tradeoffs and schedule variance impact with respect to the cost and schedule risk to the program. The Contract Funds Status Report (CSFR) shall be combined with the Cost /Schedule Status Report (C/CSSR). (DI-MGMT-81467, DI-MGMT-81468)

3.3.6. Earned Value Management System (EVMS).

You shall plan, develop, implement and maintain an Earned Value Management system for planning and tracking the CPM activities. You shall show interrelationships between activities and events to the degree necessary for management visibility and control of the program. You shall document the integrated cost and schedule status of work progress on the contract and relate technical performance with cost and schedule accomplishment using procedures for planning work, controlling costs, and measuring performance based on earned value techniques. You shall provide overall program management and administrative support to ensure that the requirements of the contract are completed. (DI-MISC-81466)

3.3.7. Associate Contractor Agreements (ACA).

You shall initiate and implement ACAs as needed to instantiate CPM collaboration efforts and to maintain CPM with emerging requirements/systems.

3.3.8 Risk Management.

You shall prepare, implement, and maintain a cost, technical and schedule risk management process which includes risk detection and identification, assignment of risk categories, corrective action, tracking of compliance, reporting of status and planning for risk abatement. You shall ensure that the program interdependencies are highlighted and the risks are monitored on a continuous basis.

3.3.9. Contractor Work Breakdown Structure (CWBS).

You shall prepare, implement, and maintain a Contractor Work Breakdown Structure to address the core functionalities and efforts associated with CPM, and the additional product tasks added to the overall effort into a cohesive WBS. You shall utilize the Government WBS provided in Appendix D as the basis of the CWBS. The CWBS shall be maintained and synchronized with the Integrated Master Schedule (IMS) and Integrated Master Plan (IMP). (DI-MGMT-81334)

3.4. System Engineering.

You shall provide an overall system engineering approach and activities necessary to maintain the allocated baselines and to deploy complete and functional systems. System engineering includes all planning, organizing, and control to ensure that the operational needs and requirements are delineated as functional requirements. You shall include into the Systems Engineering process considerations for supportability, maintenance concepts, obsolescence, and total ownership cost management (reduction). The system engineering approach shall be one of an incremental build. Each build shall add functionality to the previous build, so that the final build shall be one that is tested and verified at acceptance testing. Systems integration includes the integration of technical components, organizational components, and verification (acceptance testing). The area of system integration may make use of technical laboratories, prototype systems, and pilot systems. The development of these systems shall include all necessary safety, reliability/maintainability engineering, Manpower and Personnel Integration (MANPRINT), pollution prevention, and human factor considerations. You shall employ a quality engineering program to measure and track key processes and establish metrics and process controls.

3.4.1. System Baseline TC "3.3.1. System Baseline" \f C \l "1" .

You shall define, maintain, and integrate the allocated baselines to meet the requirements of the contract. You shall track the requirements in an automated management tool from requirements development through final acceptance. You shall track and account for all requirements (including derived requirements) through the use of a requirement traceability matrix implemented using a commercially available database tool. You shall maintain and update the requirements traceability database throughout the contract.

3.4.2. Information Assurance.

You shall develop and maintain an information assurance process to guide management and design actions, document decisions, specify and track Information Assurance requirements, document certification efforts, identify possible solutions and maintain operational systems security. You shall conduct an assessment of the LT2 CPM construct and the supporting infrastructure for security vulnerabilities and weaknesses. You shall continually evaluate the security of the system, both physical and logical, identifying exposures and providing protective options for reducing security risk.

You shall implement protective measures to address identified vulnerabilities and weaknesses. You shall integrate protective mechanisms into the system and applications to provide identification and authentication, access control, accountability, availability, confidentiality, privacy, data integrity, and non-repudiation.

3.4.2.1. Automated Information System (AIS) Security TC "3.3.5. Automated Information System (AIS) Security" \f C \l "1" .

You shall consider and integrate a holistic approach to AIS and data security that protects against unauthorized (accidental or intentional) disclosure, modification, or destruction. The AIS security shall consider the following:

a. All hardware and software functions, characteristics, and features.

b. Operational procedures.

c. Accountability procedures.

d. Access controls, remote computers, and terminal facilities.

e. Management constraints.

The security system shall provide an adequate level of protection for the AIS and data contained in the AIS. An adequate system ensures a security approach commensurate with the risk and magnitude of harm resulting from the loss, misuse, or unauthorized access to or modification of information. The AIS security system and approach shall include controls that are part of the day-to-day operations of the system, and are compliant with AR25-2, DODD 8500.1, and DODI 8500.2.

3.4.2.2. Information Assurance Vulnerability Alert (IAVA) TC "3.3.5.1 Information Assurance Vulnerability Alert (IAVA)" \f C \l "1" .

You shall implement processes and ensure compliance to the IAVA requirements throughout the development, integration, fielding, and verification of the system. You shall ensure and record the implementation of the IAVA requirements. You shall acknowledge IAVAs within five days of an alert and comply with IAVAs within thirty days of alert.

3.4.2.3. Information Assurance Training.

You shall develop and provide operator and maintenance training with respect to the nature, personnel, and criticality of the protective mechanisms in place to secure the AIS assets. This shall include the methods, skills, use and mechanisms to maintain the level of security of the AIS. The training shall be geared toward the audience and their roles and responsibilities with respect to the system’s operation and maintenance (i.e., system administrator, network administrator, hardware maintain, etc).

3.4.2.4. Department of Defense Certification and Accreditation Process (DIACAP) Support TC "3.3.5.2 DoD Information Technology Security Certification and Accreditation Process (DITSCAP) Support" \f C \l "1" .

You shall provide assistance in the development of the documentation required to achieve accreditation and certification (DIACAP Package). You shall assist the government during the definition, verification, and validation phases of the certification and accreditation process. The DIACAP Package includes documents defined within the PEO STRI Basic Accreditation Manual; such as the System Identification Profile (SIP), the DIACAP Implementation Plan (DIP), Information Security Plan (ISP), Configuration Management Plan (CMP), and the Continuity of Operation Plan (COOP).

3.4.3. Engineering Change Proposal (ECP) TC "3.3.8 Engineering Change Proposal (ECP)" \f C \l "1" .

You shall document and the IPT shall review all changes to established LT2 CPM construct baseline (as opposed to the changes tracked via the CPM construct) and all changes to the requirements (other than the functional baseline), including changes to the statement of work, contract data requirements list (CDRL), and the contract schedule. In coordination with the government, you shall hold a requirements review on all proposed changes prior to the submittal of the engineering change proposal in order to clarify requirements, format and content. Depending upon the criticality of the proposed changes, this review may take the form of a teleconference, a formal meeting at PEO STRI, or a formal meeting at your facility. Minutes shall be a historical record to allay any miscommunications.

3.4.4. Quality Assurance (QA).

You shall implement a QA program to ensure the system requirements are met. You shall implement and maintain a QA program using industry-accepted best practices and subject to government program approval. You shall establish the QA process with full government insight.

You shall establish measurement points that will provide maximum visibility into new and prior processes to assure contractual requirements are being met. You shall select the proper methods to analyze these processes to continuously improve the system. Metrics shall be developed to assist management visibility into an adequate process control system.

3.4.5. System Verification TC "3.4. System Verification" \f C \l "1" .

You shall provide an overarching verification assurance approach and methodology for the fulfillment of contract requirements. These efforts shall include tracking to closure all anomalies, failures, or issues discovered during the test and evaluation of the system. You shall develop a holistic approach and plan for the verification of the requirements, and shall coordinate the overall approach with the Government prior to the development of individual verification procedures. This plan shall address timeframes of verification efforts, resources required to support verification processes, and the envisioned verification methods to be employed. You shall also prepare and maintain a cross-reference of all requirements to the verification procedures that will be used to determine successful compliance.

3.4.5.1. Early System Integration Platform and Demonstration TC "3.4.1. Early System Integration Platform and Demonstration" \f C \l "1" .

You shall develop and maintain an early LT2 CPM construct. You shall coordinate with the Government on the most appropriate location to implement and maintain this construct. You shall utilize the construct to conduct demonstrations of the LT2 CPM. The demonstrations shall be a non-structured informal verification of the requirements, sufficient in showing the base operational performance of the construct.

3.4.5.2. Test and Verification TC "3.4.2. Test and Verification" \f C \l "1" .

You shall test and evaluate the LT2 CPM construct to ensure it meets and fulfills the requirements of the contract. The test efforts shall consist of a logical sequence of system level tests to include a complete system re-initialization and technical performance measurements.

3.4.6. Software Engineering TC "3.5. Software Engineering" \f C \l "1" .

You shall, as required, develop and implement a software development process, utilizing formal requirements development, traceability and allocation, algorithm development, configuration management, and coding practices. These processes shall be utilized for all developed software, from fully developed to 4GL (Fourth Generation Language) programming to the creation of script, command, and batch files. You shall review the software development process periodically to assure the process complies with the contract and adheres to the plans. You shall establish, control, and maintain a software engineering environment to perform the software engineering effort to ensure that each element of environment performs intended functions. You shall define and record the software requirements to be met and the traceability between the requirements and system requirements and verification methodologies.

3.4.6.1. Software Design.

You shall develop the system software and firmware and shall follow your organizational software development practices that are compliant with at least Level 4 of CMMI. You shall provide sufficient evidence that the producing software development processes are compliant with CMMI Level 4. The design process shall incorporate features that promote assessment of open source software products, ease of operation, ease of software maintenance, ease of future updates and modifications, data void work around, and also any smart designs that can justify a reduction in the amount of documentation.

3.4.7. Configuration Management TC "3.8. Configuration Management" \f C \l "1" .

You shall implement an internal configuration management system for identification, control, configuration status accounting, and auditing of all configuration documentation, hardware, and software representing or comprising the LT2 CPM construct. You shall use an internal configuration management process to monitor, update, and control all configuration documentation, physical media, and physical parts representing or comprising the system configuration items. The configuration management system shall include the process for installing all security related patches, ensuring proper IA Vulnerability Management (IAVM) and maintain the status of all security related patches.

3.4.8. Product Definition Data (PDD) TC "3.8.1. Product Definition Data (PDD)" \f C \l "1" .

You shall develop, produce, and maintain product definition data (PDD) in accordance with MIL-DTL-31000 that accurately depicts the final LT2 CPM construct. The PDD shall disclose complete design, logistics, manufacturing requirements, and the means of measuring compliance with the requirements. You shall obtain document numbers from the government for the PDD elements. All unused numbers shall be returned upon completion of PDD preparation. You shall identify the following data elements to assist in the procurement of spares/repair parts: Commercial and Government Entity (CAGE) code, National Stock Number (NSN), manufacturer’s part number, alternate part numbers, and the reliability and maintainability data if available. You shall determine performance characteristics for each re-procurable spare part, component, and assembly in accordance with the established logistic repair procedures. You shall document and describe an accurate detailed site survey description of infrastructure and training system with respect to site layout. (DI-SESS-81000C, DI-SDMP-81493A)

3.5. Logistic Management.

You shall ensure the supportability of the CPM through planning, implementation and verification of materials and services to meet the operational requirements. Readiness, Availability and Supportability shall be the primary design factors. Your design shall minimize life-cycle costs and maximize life-cycle supportability by avoiding the use of proprietary items, and recurring fees. You shall conduct an analysis of the impact of new or modified designs on CPM support resources and tasks to determine the required support equipment, software tools, system level spares, repair parts, consumables and expended materials required. Analysis shall review and produce operator’s and system maintenance manuals and procedures required to support CPM. (DI-TMSS-80527A, DI-ALSS-81529)

3.5.1. Maintenance Support Strategy.

The LT2 CPM construct shall be self sustaining via application of the CPM itself. The LT2 CPM life cycle support shall be administered and managed by APM LT2 and PM TRADE.

3.5.2. Technical Publications.

You shall describe each operation and maintenance task in detail and in logical, systematic steps for the work to be accomplished. The operations and maintenance instructions shall accurately provide all the information needed to keep the CPM construct operational. It shall provide system and subsystem oriented instructions for installation, operation, maintenance, and testing. You shall describe cold start and system initialization as well as data storage/archival and recovery processes. All manuals shall be reviewed to ensure changes, updates, revisions, or supplementation reflect the components being installed. All publications shall reflect the configuration of instantiated CPM construct. (DI-IPSC-81448A, DI-ADMN-80925)

3.5.2.1. Validation.

You shall accomplish a validation and support Government verification of all technical publications, changes, supplemental data, and revisions thereto. Publications shall be validated prior to start of system testing. A technical publication shall not be ready for validation or verification until the following conditions have been fulfilled:

a. An Engineering technical review has been completed.

b. Information, illustrations and parts lists reflect correct configurations of the system and equipment, to include all engineering changes.

c. Procedural instructions are readily understandable by the intended user and adequate to perform all operations and maintenance functions.

d. All procedures have been performed to assure accuracy and performance requirements.

e. Adequacy of data is checked to ensure that it supports the approved maintenance and support plan.

3.5.2.2. Publications In Process Reviews (IPRs).

You shall host and co-chair publication reviews to ensure the technical publications and other logistics data are being prepared according to contract requirements. Each IPR shall be scheduled to coincide with a system level program review defined in the integrated master plan. You shall act on reported decisions and discrepancies resulting from or associated with each IPR. Each review shall include a review of incorporated corrections or comments from previous IPRs prior to proceeding with the current IPR. The IPR shall be considered complete only when all outstanding IPR issues have been resolved.

3.5.3. Training Course.

You shall develop and provide system operation and maintenance familiarization training through a combination of classroom, written instructions, and hands-on operation. You shall analyze, and prepare all training courseware including program of instruction, lesson plans, practical exercises, and a train-the-trainer package to accommodate new equipment training, sustainment training, and training of testers and evaluators. You shall analyze, and prepare all training courseware including program of instruction, lesson plans, and practical exercises to accommodate user, management and administrative functionalities.

3.5.3.1. Training Classes.

You shall schedule training course(s) to an effective class size to ensure that each student receives the greatest benefit from the training. You shall conduct the training courses on location at the government site or at another mutually agreed upon location. You shall provide all required classroom equipment and training equipment for courses conducted. Training shall include classroom and practical exercise and shall total no more than eight hours per day.

3.5.3.2. Course Completion Criteria.

You shall develop a criterion referenced performance test to measure the student’s ability to perform all job-related competencies. You shall maintain a record of students attending the class, their test results and the completed student course evaluation.

3.5.4. Unique Identification (UID) of Tangible Items TC "3.8.2 Unique Identification (UID) of Tangible Items" \f C \l "1" .

You shall implement a Unique Identification of tangible items programs in accordance with MIL-STD-130. Unique item identifier means a set of data marked on items that is globally unique, unambiguous, and robust enough to ensure data information quality throughout life and to support multi-faceted business applications and users. These requirements apply to developed and commercial items. You shall coordinate among the IPT members and identify UID type, the UID to be used, and items requiring unique identification including embedded subassemblies, components and parts.