Att_06.1_Construct_PWS.docx

PWS-2018-067

Version 1.1 20 Nov 2018

PERFORMANCE WORK STATEMENT

FOR THE

LIVE TRAINING TRANSFORMATION (LT2)

CONSOLIDATED PRODUCT-LINE MANAGEMENT (CPM)

PLUS CONSTRUCT

U.S. Army Program Executive Office for Simulation, Training, and Instrumentation (PEO STRI) 12211 Science Drive Orlando, FL 32826-3276

Engineering

Acquisition Logistics Concurrence: ____________________ Matt Brothers Product Support Manager Date: __________

Program Management

TABLE OF CONTENTS

REVISION LOG

Corrected paragragh numbering from 3.3.5.2 to 3.3.6.2

i i

PERFORMANCE WORK STATEMENT

FOR THE

LIVE TRAINING TRANSFORMATION (LT2) CONSOLIDATED PRODUCT-LINE MANAGEMENT (CPM) PLUS CONSTRUCT

DELIVERY ORDER

Scope:

This Performance Work Statement (PWS) defines the work efforts for the continued development and evolution of the Live Training Transformation (LT2) Consolidated Product-Line (P/L) Management (LT2 CPM) Plus core functions. This PWS also defines the work efforts for the implementation, maturation, technology insertion, and life cycle controls associated with the real-time instantiations of the LT2 strategy. This includes, but is not limited to, the recommendation of changes, upgrades, and modifications agreed upon by governance bodies such as the Core Asset Work Group for the purposes of guiding the maturation and development of the Common Training Instrumentation Architecture (CTIA), LT2 shared assets, synchronization of components and fielded as-built configurations, configuration management (CM) of components, and maintaining concurrency of existing product line components/technology with state-of-the-art technologies and processes, PM TRADE Enterprise Architecture (business vision, goals, etc.), PM TRADE System of Systems (SoS) model-based systems engineering approach, Service Oriented Architecture (SOA) implementation, Training as a Service (TaaS) strategy, data analytics, quality management system, LT2 Construct and LT2 Portal.

Applicable Documents:

The following documents form a part of this PWS to the extent specified herein. Unless otherwise specified, the issues of these documents are those listed in the latest issue of the Department of Defense Index of Specifications and Standards (DoDISS) and supplement thereto.

1.1. Department of Defense Directives:

1.2. Availability of Department of Defense Directives:

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

1.3. Other Government Documents, Drawings, and Publications:

AR25-2 Information Assurance

CTIA Common Training Instrumentation Architecture (www.lt2portal.mil)

LT2-TRADE-PLN-000384 LT2 Operations Guide (www.lt2portal.mil)

AR 380-49 Industrial Security

Availability of Other Government Documents, Drawings and Publications:

Copies of the documents are available from ACC-Orlando, 12350 Science Drive, Orlando, FL 32826 Order of Precedence:

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

Requirements:

The tasks described in the PWS are intended to address the core functionalities of the LT2 CPM, however it is envisioned that individual program/product efforts may instantiate some or all of these functionalities for the fulfillment of the individual programmatic requirements. The contractor shall ensure all instantiations and efforts completed under the LT2 CPM Plus contract shall be consistent and synchronized with the core LT2 CPM capabilities listed here and the LT2 construct. The contractor shall:

a. Provide a holistic CM capability which addresses the multi-phase status of multiple product lines which utilize common components, services and products.

b. Provide a holistic change control process and procedures to maintain baseline control of the common products, services and components.

c. Leverage LT2 TDP development framework (Lighthouse initiatives such as ARAS and FLARE) to provide an audit of as fielded configurations, with migration and change updates.

d. Leverage LT2 TDP development framework (Lighthouse solutions such as ARAS and FLARE) provide an obsolescence audit to identify when products, services and components are no longer being utilized within fielded systems.

e. Provide for a synergy of product line CM data for systems being developed and already fielded. Establish objectives to maintain a single baseline between fielded systems and new products. Provide mitigation efforts to minimize the number of product baseline and common component and service versions released.

f. Utilize existing LT2 Portal infrastructure as required to achieve performance, insight, and configuration management of data.

g. Provide regular on-demand quantitative and qualitative metrics of the fielded product baselines (e.g.; performance metrics in operational environment, number of operational issues, operational downtime, etc.)

h. Track key metrics of performance and stability of the LT2 Family of Training Systems (FTS) Product Line components, reusability rates, and the projection of cost avoidance realized via reuse.

i. Utilize existing LT2 standard processes and working groups to coordinate LT2 FTS architecture evolution, while maintaining the integrity of the product line through systematic reuse of the common components and services. Processes shall include using the LT2 Portal to provide visibility of product software deficiencies and planned enhancements allowing programs to foster collaborative development and reduce life cycle costs.

j. Maintain a technology insertion plan for LT2 FTS architectures, services and components and utilize cost, schedule, and performance risk mitigation approaches to integrating new capabilities to ensure product line integrity and usability efficiencies that reduce total ownership costs.

k. Ensure LT2 FTS architectures, services and components achieve and maintain the following software quality objectives: reliability, stability & functionality, usability, agility & testability and supportability.

l. Synchronize tech insertion activities with LCPM and sustainment contractors using LT2 product line process.

m. Support transitioning efforts between contracts with current CPM Next prime contractor (GDMS) to mitigate impacts to current product development efforts and schedule.

n. Continue the evolution of and develop an implementation approach to achieve the PM TRADE Business Goals: reduce operation costs and complexity; align and support product development (common standards, interfaces, etc.); enhance soldier training; reduce sustain and development costs; increase technology agility; leverage other Army systems and Commercial Off the Shelf (COTS) technologies; align to Army Common Operating Environment (COE), mobile computing, and distributed computing strategies.

o. Establish strategy for the LT2 P/L Consolidated Post Development System Support (PDSS) and Post Production System Support (PPSS) to result in cost avoidance, increased performance, sustained Cybersecurity accreditation, and higher quality products.

p. Establish an integrated and open approach for LT2 P/L Technical Data Packages (TDP) to be seamlessly incorporated into sustainment activities repositories.

q. Establish strategy for the LT2 P/L development and sustainment of logistics products (such as training, operator, and support manuals, to include TDP artifacts such as drawings, interface control documents, etc.) to result in cost avoidance, increased performance, enhanced usability, and higher quality products.

r. Establish SoS management and CM across the LT2 portfolio of systems and products across the life cycle, ensuring that it is consist with the SoS model-based systems engineering approach.

s. Optimize testing methodologies and environments across the lifecycle within a P/L environment to result in cost avoidance, increased performance, and higher quality products.

t. Shall evolve the LT2 P/L to integrate intelligent data analytics which includes but not limited to real time data logging, machine learning, and predictive performance models in operational environment.

u. Shall implement and maintain the variation management approach to manage differences in features and functions of the multiple products throughout the software lifecycle as described in the LT2 Operations Guide

The LT2 CPM capabilities shall include:

1. All necessary software development to develop, maintain, update, and adapt existing LT2 architectures, services, components, shared assets and products.

2. All necessary engineering technical support to integrate new products and components into the LT2 CPM baselines (validation and certification of component agreements).

3. All necessary management and technical support to ensure synchronization with the “as fielded” baseline configuration of the LT2 FTS product line components and services. This includes establishment of any required agreements within the LT2 product line process (LT2 OPS Guide) with the LCPM and the sustainment prime contractors and subcontractors.

4. Definition of all component level interfaces internal and external to the LT2 FTS enterprise architecture and provide Component Agreement, Service Contract, and Service Level Agreement documentation in accordance with the LT2 Operations Guide.

5. A Government provided Integrated Development Environment (IDE) secured facility with integrated lab, providing access to cleared developers that will support component and product software development, integration and testing, verification of requirements required to support material release for all LT2 FTS programs as well as provide remote system and software support Consolidated Product-Line Management, Organization, and Processes:

LT2 CPM:

The contractor shall perform all of the required tasks necessary to continue to develop, evolve and sustain the LT2 CPM construct for all of the LT2 FTS products, components, and architectures. The contractor shall ensure that the LT2 Construct is inherently consistent with the LT2 Portal, LT2 strategy, PM TRADE Enterprise Architecture (business vision, goals, etc.), LT2 software quality objectives, PM TRADE SoS model-based systems engineering approach, SOA philosophy and supports real-time access/update to the CTIA, LT2 components, and services data.

All LT2 CPM assets, digital information, and documentation shall reside on Government LT2 CPM resources and LT2 Portal. The contractor shall not remove or destroy any assets, digital information, or documentation without Government approval.

Core LT2 CPM Evolution:

The contractor shall continue the development, evolution, integration and verification of the LT2 CPM construct to fulfill the Core LT2 CPM capabilities and core LT2 CPM activities (see section 3 of this PWS).

1. The contractor shall facilitate a structured process/method to ensure early discovery of stakeholders driving requirements and/or quality attributes for the LT2 CPM core functions, and utilize this data for architecture, process, and application focus and improvement efforts (i.e., optimize LT2 CPM evolution).

2. The contractor shall protect and leverage the Army’s LT2 P/L investment to include Lighthouse initiatives while evolving shared assets and the LT2 Construct tools and processes to ensure technology relevance across the P/L. The Contractor shall continue the development and evolution of the LT2 products/systems, shared assets, architectural frameworks, and the LT2 P/L Construct, while continuing to provide PM TRADE an efficient, effective, and agile method to accomplish:

a. Development, integration, testing, management, maintenance, and evolution of the LT2 P/L (products, systems, SoS capabilities, architectures, processes, and shared assets)

b. Total life-cycle system management and P/L support

c. P/L support of products, systems, and SoS capabilities that leverage LT2 P/L assets

d. Architectural and system development, and shared asset evolution in support of external interoperability initiatives such as Live, Synthetic Training Environment (STE) COE, Joint services initiatives, multi-national interoperability, and Foreign Military Sales as required within the LT2 P/L

e. Synchronization with other PEO STRI efforts and initiatives as required by the LT2 P/L (such as the Lifecycle Consolidated Program Management (LCPM) and Army Training Maintenance Program (ATMP) contract)

f. Continue the evolution of and develop an implementation approach to achieve PM TRADE Business Goals: reduce operation costs and complexity; align and support product development (common standards , interfaces, etc.); enhance soldier training; reduce sustain and development costs; increase technology agility; leverage other Army systems and Commercial Off the Shelf (COTS) technologies; align to Army COE, mobile computing, and distributed computing strategies

g. Establish strategy for the LT2 P/L Consolidated PDSS and PPSS to result in cost avoidance, increased performance, sustained cybersecurity accreditation, and higher quality products.

h. Establish an integrated and open approach for LT2 P/L TDP to be seamlessly incorporated into sustainment activities repositories.

i. Establish strategy for the LT2 P/L development and sustainment of logistics products (such as training, operator, and support manuals, to include TDP artifacts such as drawings, interface control documents, etc.) to result in cost avoidance, increased performance, enhanced usability, and higher quality products.

j. Establish SoS management and configuration management across the LT2 portfolio of systems and products across the life cycle, ensuring that it is consist with the SoS model-based systems engineering approach.

k. Optimize testing methodologies and environments across the lifecycle within a P/L environment to result in cost avoidance, increased performance, and higher quality products.

Core LT2 CPM Evolution Management:

The contractor shall manage the evolution, document, and instantiate the processes to support the core LT2 CPM capabilities and activities, both for current assets (components, services, products, and architectures) and artifacts contained within LT2 CPM, and for the development and insertion of new assets and artifacts.

LT2 CPM Transition:

Transition In:

The contractor shall support the transfer of the LT2 CPM responsibility to this contract:

1. The contractor shall support the transfer of the LT2 responsibility, assets, CPM construct, digital information, and documentation from the current contractor to this contract. These efforts shall ensure the effective, efficient transfer of responsibility as well as technical data. The contractor shall identify any potential shortfalls or missing data, processes, and tools.

2. Support shall include those services required to ensure the effective, efficient transfer of responsibility as well as technical data, tools and test equipment and repair and spare parts, in sufficient detail and coverage to enable other personnel with comparable skills to operate and maintain the system. The transition effort shall include an analysis of all failures and maintenance actions undertaken during the interim support and revising technical publications to reflect actual fielded experience. The LT2 CPM transfer shall include 100 percent of provisioned items.

3. The contractor shall use the current tool suites and established governance processes when assuming responsibility for the LT2 CPM. The contractor shall assume responsibility for maintaining and keeping current all necessary software and hardware licenses to ensure the day to day functions of the CPM.

4. The contractor shall conduct an analysis of the LT2 CPM construct, the attached processes, and core implementation schema to delineate the operations, constraints, management, working groups, tools and mechanics. The contractor shall review, revise, and update the existing LT2 Operations Guide and CPM Configuration Management Operational Procedures Guide to align to the LT2 CPM construct and implementation processes. LT2 Operations Guide and LT2 Configuration Management Operational Procedures Guide shall be uploaded to the LT2 Portal. The contractor is required to ensure that this document is current on the LT2 Portal. The Government may require this document via a CDRL submission as outlined in the CDRL. The Contracting Officer or their duly authorized representative will request this document in writing when a formal CDRL submission is required.

DI-MISC-80711A: LT2 Operations Guide

5. The contractor shall assume responsibility for the CPM Core capabilities in section 3 of this PWS.

Transition out:

The contractor shall develop a Transition Plan and provide support for the transfer of the LT2 CPM responsibility to the Government or another contractor at the end of your contract.

DI-MISC-80711A: Scientific and Technical Reports (Transition Plan)

Core LT2 CPM Optimization:

The contractor shall conduct a formal and reiterative process (at least yearly) to assess the effectiveness of the Core LT2 CPM implementation and instantiate corrective action changes. The contractor shall identify, maintain, and track key metrics regarding the implementation and key measure points for the LT2 CPM. This process shall consider a decomposition of processes, design, implementation, and architecture of the LT2 CPM.

The contractor shall implement appropriate metrics for the LT2 CPM to gather measurement data. The contractor shall establish the processes to effectively use the measurement results to drive decision making and improvements within LT2 CPM.

Core LT2 CPM Processes:

The contractor shall conduct an analysis of the current business practices relative to LT2 CPM and conduct a gap analysis between the current and end state processes.

1. The contractor shall identify and document any proposed changes to the current operating processes to define roles, responsibilities, and mechanisms inherent to the implementation of the core LT2 Construct.

2. The contractor 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.

3. The process analysis shall focus on Configuration Change Board (CCB) and overarching CM processes, component agreements, service level agreements, and service contracts. 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 LT2 CPM.

4. The process analysis shall also focus on the delineation of integrated processes for the entirety of the product-line management.

Test and Verification:

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

LT2 CPM Sustainment:

The contractor shall support component and services development, evolution, and maturation, to include the Common Training Instrumentation Architecture (CTIA), Live Training Engagement Composition (LTEC) and other developed and maintained common components, services, architectures, and product line assets, utilizing the core LT2 CPM construct.

1. The contractor shall support, refine, and develop existing LT2 assets (inclusive of documentation) to allow for technology refresh and insertion into the LT2 CPM.

2. The contractor shall ensure synchronization of the LT2 CPM construct; leveraging the Lighthouse initiatives solutions (such as ARAS) with the work efforts/products from LCPM and ATMP in the operations and maintenance of the various products, documentation, product lines, product line artifacts, architectures, and system configurations.

3. The contractor shall utilize the currently defined LT2 product line processes (Shared Asset Working Group (SAWG), etc.) to realize the LT2 CPM activities within the construct.

Sustainment of Core LT2 CPM Processes:

The contractor shall conduct iterative assessments of the processes to ensure they remain relevant and up-to-date (consistent with technology and usage of LT2/Core LT2 CPM).

LT2 CPM Information Technology Sustainment:

The contractor shall sustain the Information Technology (IT) components and infrastructure that support the operations of the LT2 CPM. The contractor shall synchronize these efforts (as applicable) with the appropriate CS requirements and constraints of the Government’s IT components.

1. These efforts shall include the sustainment, modernization, and disposal of all IT elements required to operate the LT2 CPM.

2. The contractor shall administer, maintain, operate, synchronize, evolve and refresh the LT2 Portal to align to the operation needs and requirements of the LT2 CPM, to allow users access to software, products, documentation, configuration information, or other data/metadata required within the LT2 Construct.

3. The contractor shall maintain and update the LT2 CPM portal engine as a separate entity from the LT2 Construct, to support utilization by other organizations.

Fielded Product Line Support:

The contractor shall leverage the LT2 TDP development framework (Lighthouse Initiatives) to provide technical, CM, documentation, and management support for assets of the LT2 FTS product line via Core LT2 CPM functionalities.

1. These efforts shall include integration support, interoperability support, site acceptance support, and demonstration/experimentation support.

2. The contractor shall conduct engineering assessment and provide implementation and transition plans to support the release of new components, products, and architectures.

3. The contractor shall conduct analyses of LT2 CPM components, services, products, and architectures and provide assessments as to change/maturation impacts of the components, products, and architectures. These assessments shall include the cost tradeoff between maintaining multiple versions of components and product baseline vice cost of maturing older systems/products to the latest releases.

Integration Lab:

The contractor shall evolve, maintain, and run a core Government provided integration lab (located in the Integration and Development Environment (IDE)) associated with the operations and sustainment of the LT2 CPM and associated LT2 Product Line core assets.

1. 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.

2. The core integration lab shall provide support to the Help Desk, and ensure synchronization with the CM and management activities.

3. The integration lab shall also support the common component development, common services development, technology insertion, and obsolescence remediation execution.

4. The contractor shall instantiate (as required) classified or unclassified 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.

The lab shall replicate the operational environment and configuration as much as possible to include (e.g.; MILES, player units, PU simulator, RMDS, etc.)

LT2 CPM Training Classes:

The contractor shall develop and provide periodic in-class training for the LT2 CPM.

1. The in-class training shall include two separate elements; one focused on overarching familiarization and management of the LT2 CPM, the other focused on the technology use case and development execution aspects of the LT2 CPM.

2. The contractor shall update and provide periodic in-class and on-line training for LT2 familiarization and asset development. These classes shall be linked to the LT2 CPM training and execution methods.

3. The contractor shall analyze and prepare all training courseware, including program of instruction, lesson plans, and practical exercises to accommodate user, management and administrative functionalities.

Computer Harware, Enterprise Software Solutions (CHESS) Program The contractor shall comply with the Army’s Computer Hardware, Enterprise Software Solutions (CHESS) program as defined within and across Delivery/Task Orders. Under PEO EIS, CHESS is the mandatory source for commercial their Information Technology (IT) purchases. CHESS contracts provide IT products and services that comply with NETCOM, Army and DoD policy and standards. Purchasers of commercial hardware and software must satisfy IT requirements by utilizing CHESS contracts and DoD Enterprise Software Initiative agreements first, regardless of dollar value. Any purchase made outside of CHESS contracts requires a waiver. A complete list of CHESS contracts and the on-line waiver process can be found at https://chess.army.mil.

LT2 CPM Activities:

The contractor shall apply iterative processes to support shared asset development and sustainment, product development support, and management activities in the evolution and sustainment of the LT2 CPM construct.

1. The contractor shall apply an overarching CM activity across all LT2 CPM activities, components, services and assets.

2. The contractor shall apply (as required) processes to support technology insertion and refresh activities, while maintaining the product line integrity of the LT2 Construct activities, components, services, and assets.

Shared Asset Development and Sustainment Activity:

The contractor shall materially participate in the shared asset development activity, which includes the development and support for products, support/updates for preexisting assets, product line scope, and shared asset base definition.

1. These activities shall include software development, component/services definition and development, CM tracking, new component/service opportunities, component/service 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.

2. The contractor shall develop and ensure that all software, component agreements, service level agreements, and service contracts are per the CTIA Compliance Definitions, LT2 Operations Guide, LT2 Configuration Management Operational Procedures Guide, LT2 Component Agreement Template, Service Level Agreement Template, or Service Contract Template.

Interoperability:

The contractor shall design, implement, test and integrate any enhancements required to establish an interface between LT2 Product Line shared assets and external systems.

1. The contractor shall ensure the interface support conversions of the data and that no fidelity is lost in the conversion.

2. The contractor shall ensure that the design supports live, virtual, constructive and gaming simulation interoperability, as required.

3. The contractor shall ensure that the design supports multi-national interoperability in the LVC domain.

Reusability:

The contractor shall perform a continuing assessment of existing software components from commercial and Department of Defense repositories, legacy systems, and other available sources for potential reuse in the LT2 P/L as shared assets. The contractor shall investigate the reuse of the CTIA and LTEC-compliant software components for multiple products, services, or components.

Extensibility:

The contractor shall ensure that the architectures remain extensible and flexible to enable applications to be easily upgraded or modified to support additional requirements with minimal system perturbation.

3.1.2.1.4. Testability Engineering:

The contractor shall design, implement, and maintain an innovative system testability process satisfying all testability requirements of the LT2 Construct components, services and shared assets throughout the system life cycle which is traceable throughout the design process, is integrated with other system engineering product line requirements, and is disseminated to design personnel and subcontractors.

1. Testability Engineering shall be initiated at the onset of the delivery order, and implemented throughout the entire period of execution for all components, services, and shared assets of the LT2 P/L.

2. Testability Engineering shall be a proactive activity within the Construct and LT2 P/L. The contractor shall establish controls for ensuring that each subcontractor's testability practices are consistent with overall system requirements.

3. The contractor shall define the means for demonstrating and validating that the diagnostic capability meets specified requirements, using maintainability demonstrations, test program verification, and other demonstration methods.

4. The contractor shall ensure that as test and evaluation of the system progresses, problems presented by new failure modes, test voids, ambiguities, and test tolerance difficulties are recognized and defined, and solutions are traceable to diagnostic hardware and software, and technical publication procedures are updated.

5. The contractor shall identify the test conditions that will replicate the operational environment for each product.

6. The contractor shall develop and integrate test tools required to replicate the operational environment.

7. The contractor shall embed test and simulation tools in the production baseline to enable continuous testing at fielded sites.

8. The contractor shall define an approach for the analysis of acceptance test and evaluation results to determine how built in test hardware and software, automatic test equipment hardware and software, and maintenance documentation performed as a means for satisfying production testing, and meeting testability requirements.

9. The contractor shall establish an efficient, achievable and affordable diagnostic concept and state-of-the-art testability built-in and off-line test performance requirements.

10. The contractor shall integrate test approach and solution into equipment and systems during the design process in coordination with the maintainability design Process The contractor shall ensure design meets the testability requirement.

11. The LT2 CPM testing shall synchronize with all of testing activities for products and product support within the LT2 FTS, LCPM and ATMP programs and provide an overarching testing method for all product line shared assets, artifacts, and processes.

12. The testing methodology to include test management activity, process and practices shall be outlined in a Test Plan (Strategy). The contractor is required to ensure that this document is current on the LT2 Portal. The Government may require this document via a CDRL submission as outlined in the CDRL. The Contracting Officer or their duly authorized representative will request this document in writing when a formal CDRL submission is required.

DI-MISC-80711A: Test Strategy Product Development Support Activity:

The contractor shall materially participate in the product development support activity as required to support the maturation, reuse, and integration of common components and services with respect to implementation in programs utilizing the product line assets.

1. These activities shall be synchronized with the shared asset development and sustainment activities.

2. These activities shall include feedback mechanisms into the product line processes and CM tracking of shared assets.

3. These activities shall also include software development and integration, performance testing, and coordination with prime system contractors.

Architecture Verification/Validation:

The contractor shall perform core architecture verification and validation through the life of the LT2 CPM.

1. During the continued evolution of the LT2 CPM the architecture shall be verified through a combination of the following:

a. Formal and informal reviews

b. Analysis of architecture

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

d. Application of static and dynamic modeling

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

LT2 Model-Based Systems Engineering (MBSE), and System of Systems (SoS) Architecture Development and Department of Defense Architectural Framework (DoDAF) Evolution Activity:

The contractor shall materially participate in the LT2 MBSE and SoS Architecture development and evolution activity initially utilizing the Government approved MBSE tool, which includes the development and support for SoS and DoDAF models, support/updates for preexisting SoS and DoDAF models, SoS and DoDAF architecture scope, and SoS and DoDAF model definition for the LT2 P/L.

1. These activities shall include SoS change impact assessment, CM tracking, new SoS modeling opportunities, model transition from development to sustainment phase to include merging of enhancements and model updates across multiple product/system baselines, and production planning of SoS models into LT2 products/compositions.

2. The contractor shall develop and ensure that all MBSE activities, and SoS and DoDAF models are per the LT2 CPM Operations Guide.

LT2 Model-Based Systems Engineering (MBSE) and System of Systems (SoS) Architecture Training:

The contractor shall provide and adjust as necessary the curriculum and supporting instructional materials suitable to train practicing engineers on MBSE, the Government approved MBSE tools and applications, and the support language Systems Modeling Language (SysML). Instruction shall provide a combination of theory and practical modeling exercises, and targeted knowledge and skills that include at least the following:

· Requirements architecture and definition (operational, functional, performance, physical, etc.)

· Use cases, behavior, functional analysis, and impact assessments

· System architecture and physical analysis

· Constraints and boundaries

· Model simulation

· Verification and validation techniques

· Team work and document generation Product Line Obsolescence Management:

The contractor 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 LT2 CPM. The contractor shall establish an iterative process to implement the obsolescence management to include total ownership impact assessments and recommendations to the Government.

LT2 CPM Help Desk:

The contractor shall sustain a 24 hours/ 7days LT2 CPM Help Desk located on the LT2 Portal.

1. The Help Desk shall act as a single point of entry into the LT2 CPM for problem identification and support to include real time issue debugging. The Help Desk shall be supported by the CM and management activities to synchronize sustainment and development efforts for common components and product line assets.

2. The contractor 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.

3. The contractor shall instantiate processes for handling emergency/exception changes to common components, services and maintained assets for post inclusion into the LT2 CPM.

Technical Data Package (TDP) The contractor shall follow the LT2 Data Driven Product-Line Methodology as described on the LT2 Portal and the LT2 Operations Guide. The contractor shall develop the content for the new data through the LT2 tools and processes utilized on the LT2 Portal in accordance with the LT2 Operations Guide. This documents shall use the LT2 TDP development framework (“Lighthouse Initiative”) tools and processes, however, they do not supersede the requirements of the DID/CDRLs. The contractor shall be responsible for TDP updates, availability and accuracy.

Management Activity:

The contractor shall implement proactive management processes and resources at both the technical and organizational levels to support the product line efforts and ensure consistency and synchronization across all delivery orders.

1. The management shall identify production constraints, funding models, tracking of product line evolution, communication between activities, and risk management.

2. The management processes shall include mechanisms and support for the multi-program adjudication of priorities and architectural impacts as related to the common components, services, and central repository.

Configuration Management Activity:

The contractor shall initially sustain and mature the current CM methodology to establish and maintain the integrity of the components, services, products, and assets throughout the product line life cycle.

1. CM shall be implemented throughout the entire period of execution for all components, services, products, and assets of the product line.

2. CM shall be a proactive activity within the LT2 Construct.

3. 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.

4. CM shall function as a multidimensional version of a typical CM process (multi-phased, multi-program, multi-tiered, multi-instantiated, and multi-baseline), binding the LT2 CPM products and activities.

5. CM shall support parallel development, distribution, and build releases.

6. CM shall address use by all developers and products.

7. CM shall:

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

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

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

d. Track change requests for the configuration items

e. Control changes in the content of configuration items

f. Establish and maintain records describing configuration items

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

8. The LT2 CPM CM shall synchronize with all of CM activities for products and product support within the LT2 FTS, LCPM and ATMP programs and provide an overarching CM method for all product line assets, artifacts, and processes.

Technology Insertion/Refresh Activity:

The contractor shall support new technology development and insertion into the product line, services and components, as well as technology refresh of existing product line assets, services and components.

1. These efforts shall include all necessary activities to synchronize, deploy, sustain, and track the new/updated assets of the product line. These activities, when exercised, must align with the core LT2 CPM Plus activities noted above.

2. 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, services contract development, documentation, training, and coordination.

3. The contractor shall ensure the technology insertion and obsolescence management applies appropriate CS considerations in the decision making process. Additionally, CS policy (and changes to these policies) shall be a driving consideration for potential technology insertion and obsolescence management methodologies.

Cybersecurity:

The contractor shall implement a comprehensive multi-approach methodology with respect to CS and the LT2 CPM.

1. The contractor shall leverage the National Information Assurance Partnership (NIAP) and the Common Criteria Evaluation and Validation Scheme (CCEVS) to ensure Defense Information Systems Agency (DISA) approved software and hardware are utilized within the CPM construct and CPM supported components, services, and product line assets.

2. The contractor shall also ensure that the common components and services developed and maintained within LT2 CPM and the CTIA development environment are implemented in accordance with DISA Security Technical Implementation Guide (STIG) compliance.

3. The contractor shall develop and maintain a CS process to guide management and design actions, document CS decisions and certification efforts, specify and track CS requirements, identify possible CS solutions, synchronize CS with CM activities, and maintain operational systems security.

4. The contractor shall conduct an assessment of the LT2 CPM construct and the supporting infrastructure for security vulnerabilities and weaknesses.

5. The contractor shall continually evaluate the security of the system, both physical and logical, identifying exposures and providing protective options for reducing security risk. The contractor shall deliver upgrades to the system in a configuration that will pass a certification and will not negatively impact the existing accreditation.

6. The contractor shall implement protective measures to address identified vulnerabilities and weaknesses. When Classified or Controlled information is introduced into the CPM, the contractor shall adhere to the provisions within AR 380-5 regarding the classification, transmission, transportation, and safeguarding of this information.

7. The contractor 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.

8. Per DOD 8570.01-M , Defense Federal Acquisition Regulation Supplement (DFARS) 252.239.7001 and AR 25-2, the Contractor employees supporting cybersecurity/IT functions shall be appropriately certified upon contract award. The baseline certification as stipulated in DOD 8570.01-M must be completed upon contract award for the role to be performed.

Information System (IS) Security:

The contractor shall consider and integrate a holistic approach to IS security and data security that protects against unauthorized (accidental or intentional) disclosure, modification, or destruction.

1. The IS 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

2. The security system shall provide an adequate level of protection for the IS and data contained in the IS. 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.

3. The IS security system and CS approach shall include controls that are part of the day-to-day operations of the system, and are compliant with AR25-2, , DoDI 8500.01, DoDI 8510.01, CNSSI 1253, NIST SP 800-53, DoDI 8582.01 and AR 25-2. The contractor shall support accreditations under the Risk Management Framework (RMF) IAW 8500.01 and DoDI 8510.01.

Information Assurance Vulnerability Alert (IAVA) for LT2 CPM:

The contractor shall implement processes and ensure compliance to the IAVA requirements throughout the life cycle of the LT2 CPM.

1. The contractor shall track and record the implementation of the IAVA requirements.

2. The contractor shall acknowledge IAVAs within five days of an alert and comply with IAVAs within thirty days of alert.

Information Assurance Vulnerability Alert for Components:

The contractor shall implement processes to monitor and track the IAVA requirements as related to individual components, services and assets within the LT2 Product Line and Framework. The contractor shall implement processes to alert, monitor, track, update, and deploy as necessary owners of components potentially impacted by individual IAVA requirements. The contractor shall, design, develop, integrate and verify CS fulfills the TaaS philosophy to include remote or distributed CS management capabilities. The contractor shall identify, collect, analyze, and present technical CS related metrics to aid in reducing CS sustainment costs by providing visibility into the CS posture of the LT2 product line.

Cybersecurity Training:

The contractor shall develop and provide operator and maintenance training with respect to the nature, personnel, and criticality of…