PEO-STRI-0

W900KK-

Version 1.0

DRAFT

STATEMENT OF WORK

FOR THE

LIVE TRAINING TRANSFORMATION (LT2)

COMMON TRAINING INSTRUMENTATION ARCHITECTURE (CTIA)

DELIVERY ORDER TBD

U.S. Army Program Executive Office for

Simulation, Training and Instrumentation (PEO STRI)

12350 Research Parkway

Orlando, FL 32826-3276

Engineering:

Prepared by: ______Concurrence: ______

Jeremy Lanman, Ph.D.James Grosse

Lead Systems Engineer / ArchitectChief Engineer, APM TRADE

Date: ______Date: ______

Acquisition Logistics:

Concurrence: ______

Robert Capote

Chief Acq Log, PM TRADE

Date: ______

Program Management:

Submitted by: ______Approved by: ______

Jeremy LanmanThomas Coffman

Systems ArchitectAPM TRADE

Date: ______Date: ______

TABLE OF CONTENTS

1.Scope:

1.1.Description:

2.Applicable Documents:

2.1.Department of Defense Directives:

2.2.Availability of Department of Defense Directives:

2.3.Other Government Assets, Documents, Drawings and Publications:

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

2.5.Order of Precedence:

3.Requirements:

3.1.CTIA Management, Organization and Processes:

3.1.1.CTIA Post Deployment Software/System Sustainment (PDSS):

3.1.2.CTIA Technology Insertion:

3.1.3.CTIA Software/System Test Engineering:

3.1.4.Software/Systems Engineering:

3.2.Program Management:

Appendix A: Definition of Terms

Appendix B: CTIA SOA Vision

Appendix C: CTIA SOA Roadmap

Appendix D: Training as a Service (TaaS) Roadmap

Glossary

REVISION LOG

Date / Version / Revision Description

1

PEO-STRI-

W900KK-

Version 1.0

STATEMENT OF WORK

FOR THE

LIVE TRAINING TRANSFORMATION (LT2)

COMMON TRAINING INSTRUMENTATION ARCHITECTURE (CTIA)

DELIVERY ORDER

1.Scope:

This Statement of Work (SOW) defines the work efforts for the continued support, development, and evolution of theCommon Training Instrumentation Architecture (CTIA) and all the facets necessary to support a product line architecture approach to fielding live training systems within the live training domain.

1.1.Description:

The CTIA is the foundation architecture of the Live Training Transformation Family of Training Systems (LT2-FTS) strategy. The CTIA is the software product-line architecture that provides commonality across live training instrumentation systems and interoperability with the LVC-ITE and joint training systems. CTIA is the Army’s live training instrumentation standard which enables asset reuse across the live training domain and defines a common live training instrumentation standard for interoperability across the LVC training domain. It consists of the architecture infrastructure, architecture services, software components, governance, standards, developmentenvironment, developmental and testing frameworks,and protocols to be used by system/product developers within the LT2 product line and is the core software component of the Army live-training instrumentation systems. The CTIA is a component-based, domain-specific, product-line architecture that enables the U.S. Army’s LT2 the ability to leverage common requirements among the U.S. Army’s instrumented ranges and homestations. With significant emphasis on reuse and commonality, the CTIA improves the quality of training while significantly reducing development, training, logistics, and sustainment costs. The CTIA and its family of product-line services and components are Army-owned and are managed by the PM TRADE Assistant Project Manager. The CTIA-based systems are fielded and fully operational at the Army’s Combat Training Centers (CTCs) and at numerous homestation training ranges. Additionally, CTIA-based systems are being fielded by the Marine Corps and Air Force. The CTIA-based systems are Information Assurance certified to operate at the secret classification level.

2.Applicable Documents:

The following documents form a part of this SOW 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.

2.1.Department of Defense Directives:

DOD 8570.01 MInformation Assurance Workforce Improvement

Program

DODD 8500.1Information Assurance

DODI 8500.2Information Assurance (IA) Implementation

DODI 8510.01DIACAP

2.2.Availability of Department of Defense Directives:

Copies are available on the WWW at URL:

2.3.Other Government Assets, Documents, Drawings and Publications:

AR25-2Information Assurance

CTIA Common Training Instrumentation Architecture

(

99-0008380LT2 CPM Operations Guide (

LT2-TRADE-PLAN-2013-00009CPM Configuration ManagementOperational Procedures Guide (

LT2-APM-TD-2013-000000LT2 CTIA Objective Architecture

LT2-APM-TD-2013-000001LT2 CTIA Architecture Vision

LT2-APM-TD-2013-000002LT2 CTIA Transition Architecture 1 (TA1)

LT2-APM-TD-2013-000003LT2 CTIA Transition Architecture 2 (TA2)

LT2-2006-0001CTIA Compliance Definition Document

(

MIL-DTL-31000 Technical Data Packages

MIL-STD-40051-2Preparation of Digital Technical Information for

Page-Based Technical Manuals

MIL-PRF-49506Logistics Management Information

MIL-STD-130Unique Identification (UID) of Tangible Items

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

Copies of the documents are available from PEO STRI, SFAE-STRI-KOL, 12350 Research Parkway, Orlando, FL 32826, or may be available at: or

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.Requirements:

The Contractor shall execute the functions of Post Deployment Software/System Sustainment (PDSS) within the LT2 CPM framework in accordance with PEO-STRI-XX-WXXX and synchronized with PEO-STRI-XX-WXXX for the CIS such as Program Management, Configuration Management, Data Management, and modifications and upgrades. The work tasks described in the SOW are intended to address the core functionalities of the CTIA

3.1.CTIA Management, Organization and Processes:

The contractor shall perform all of the required tasks necessary to protect the existing investment of the CTIA, and design, implement, evolve, maintain and govern the CTIA for the LT2 Product Line in accordance with LT2 CPM Operations Guide. The contractor shall ensure that the CTIA remains consistent with the LT2 strategy, PM TRADE Enterprise Architecture (business vision, goals, etc.), PM TRADE System of Systems (SoS) model-based systems engineering approach, Service Oriented Architecture (SOA) and Training as a Service (TaaS) philosophy, and LT2 CPM Construct.

All CTIA services, assets, digital information, and documentation shall reside on Government LT2 resources and support real-time access and updates. The contractor shall not remove, destroy, or deprecate any assets, digital information or documentation without explicit Government approval.

3.1.1.CTIA Post Deployment Software/System Sustainment (PDSS):

The contractor shall provide PDSS for all CTIA components, services and assets. The contractor shall utilize the currently defined LT2 processes (Core Asset Working Group (CAWG), PTR Review Board (PRB), etc.) in accordance with the LT2 CPM Operations Guide.

  1. The contractor shall provide engineering support for software design, development, integration, migration, maturation, verification and validation, and maintenance of all CTIA versions as required by LT2 products in accordance with the LT2 CPM Operations Guide.
  1. The contractor shall define, maintain, and integrate the allocated, functional, and production baselines for the CTIA to meet the requirements of the basic and delivery order contracts. The allocated, functional, and production baselines for CTIA shall be tracked to the system, subsystem, and component/service level/layer for each fielded location.
  1. The contractor shall track all requirements and baselines in an automated management tool from requirements development through final acceptance. The contractor 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. The contractor shall maintain and update the requirements traceability database throughout the basic and delivery order contract.
  1. The contractor shall support, design, develop, refine, evolve,modify and matureexisting and future CTIA services, components and assets (inclusive of documentation) to allow for technology refresh and insertion into the CTIA.
  1. The contractor shall design CTIA software, develop executable source code, perform unit, composition and integrationtesting, and integrate software components and services (with each other and with hardware components) to meet CTIA requirements.
  1. The contractor shall provide software licensing, subscription services, support agreements, warranties and extended maintenance agreements. The contractor shall identify software and software licensing agreements that can more affordably be purchased by the Government.
  1. The contractor shall distribute CTIA services and components software and documentation to the LT2 Portal upon completion of service/component verification or as required to support engineering releases. All submittals to the LT2 Portal shall be in accordance with the LT2 CPM Operations Guide.
  1. The contractor shall continue and sustain a CTIA Help Desk. The Help Desk shall act as a single point of entry into the CTIA for problem identification and support. The Help Desk shall be supported by the CM and management activities to synchronize sustainment and development efforts for architectural services. The contractor shall follow LT2 processes in accordance with the LT2 CPM Operations Guide for handling emergency/exception changes to services for post inclusion into the CTIA.
  1. The contractor shall develop and provide training and all training materials for the CTIA familiarization and component/service development and deployment as requested by the Government.
  1. The contractor shall document, and the Integrated Product Team (IPT) (e.g. Core Asset Working Group (CAWG)) shall review, all changes to the established CTIA baseline and all changes to the requirements including changes to the statement of work, Contract Data Requirements List (CDRL), and the delivery order contract schedule.
  1. The contractor shall support the transfer of the CTIA responsibility, assets, digital information, and documentation from the incumbent contractor to the new contractor and into the LT2 CPM Construct. These efforts shall reuse current assets, protect the existing investment, and ensure the effective and efficient transfer of responsibility as well as technical data. The contractor shall identify any potential shortfalls or missing data, processes, and tools.

3.1.2.CTIA Technology Insertion:

The contractor shall protect the existing investment and support new technology development and insertion into the CTIA, as well as technology refresh of existing CTIA services and componentsthrough modular design, the use of open standards and open interfaces in accordance with the LT2 CTIA Architecture Vision, LT2 CTIA Objective Architecture, and LT2 CTIA Transition Architecture documents and roadmaps (documents on LT2 Portal: LT2-APM-TD-2013-000000, LT2-APM-TD-2013-000001, LT2-APM-TD-2013-000002, LT2-APM-TD-2013-000003; and Appendices B, C and D found in this SOW). These efforts shall include all necessary activities to synchronize, deploy, maintain, and track the new/updated services of the CTIA. These activities, when exercised, must align with the core LT2 product line activities. These activities shall include software research and development, standards evolution development, hardware research and development, software integration, trade-off studies/analyses, prototype development, design of experiments, experimentation support, compliance testing, service level agreement development, service contract development, documentation, training, and facilitation/coordination.

  1. The contractor shall:
  2. Clearly define and describe all component, service and system interfaces
  3. Define and document all subsystem and configuration item (CI) level interfaces to provide full functional, logical, and physical specifications
  4. Identify processes for specifying the lowest level (i.e. subsystem or component) at and below which it intends to control and define interfaces by proprietary or vendor-unique standards and the impact of that upon its proposed logistics approach. Interfaces described shall include, but not be limited to software, firmware, and hardware interfaces
  5. Identify the interface and data exchange standards between the component, module, service, composition or system and the interconnectivity or underlying information exchange medium
  6. If applicable, select external interfaces from existing open or Government standards with an emphasis on enterprise-level interoperability. The contractor shall describe how its selection of interfaces will maximize the ability of the system to easily accommodate technology insertion (both hardware and software) and facilitate the insertion of alternative or reusable modular system elements
  7. Describe the extent that the change or configuration management process proposed will use “community of interest” teams in an integrated team approach to effectively identify how individual changes impact the system’s internal or external interfaces and information exchange standards
  1. The contractor shall ensure the technology insertion and obsolescence management applies appropriate Information Assurance (IA) considerations in the decision making process. Additionally, IA policy (and changes to these policies) shall be a driving consideration for potential technology insertion and obsolescence management methodologies.
  1. The contractor shall conduct a Technical Review (TR) to define and demonstrate the CTIA. The TR shall be a formal technical review of the allocated baseline and changes made to the allocated baseline.
  1. The contractor shall, as required, conduct a limited validation demonstration to validate the system’s ability to fulfill operational requirements.
  1. The contractor shall develop and provide training for the CTIA familiarization and component/service development and deployment as requested by the Government.
  1. The contractor shall document and model the CTIAcomponents and services (e.g., software, hardware, middleware) design information using industry standard formats, (e.g., UML, SysML, etc.). It shall also document and model how it will use tools that are capable of exporting model information in a standard format (e.g., Extensible Markup Language Metadata Interchange (XMI) and AP233/ISO 10303). The contractor shall identify the proposed standards and formats to be used. The contractor shall maintain the design information, including any models used, so that it is current with the as-built system.
  1. The contractor shall define the functional partitioning and the physical modularity of the CTIA to facilitate future replacement of specific subsystems and components without impacting other parts of the system and to encourage third-party vendor’s participation.
  1. The contractor shall consider use of COTS/NDI and open standards to enhance the CTIA life-cycle sustainability by implementing performance-based logistics (PBL) arrangements to sustain the components and services through their life cycle.
  1. The contractor shall describe the use of proprietary, vendor-unique or closed components or interfaces. If applicable, the contractor will define its process for identifying and justifying proprietary, vendor-unique or closed interfaces, code modules, hardware, firmware, or software to be used. When interfaces, hardware, firmware, or modules that are proprietary or vendor-unique are required, the contractor shall demonstrate to the Government that those proprietary elements do not preclude or hinder other component, service or module developers from interfacing with or otherwise developing, replacing, or upgrading open parts of the system.
  1. The contractor shall demonstrate that the modularity of the CTIA design promotes the identification of multiple sources of supply and/or repair, and supports flexible business strategies that enhance vendor competition.
  1. The contractor shall conduct market surveys and trade studies to identify candidate COTS, proprietary, open source software (OSS) and other reusable assets capable of achieving the performance requirements of solutions that it proposes to custom build. The survey results shall be provided to support each major review.
  1. The contractor shall re-use pre-existing or common items unless a determination is made to not re-use. Exceptions to reuse of pre-existing items must be accompanied by justification, such as cost (both of adoption and life cycle support), schedule, functional and non-functional performance, etc.
  1. The contractor shall address how it will provide to the Government information needed to support third-party development and delivery of competitive alternatives of designs for software or other components or modules on an ongoing basis. The contractor shall provide a list of those proprietary, vendor-unique elements that it requests be exempt from this review.
  1. The contractor shall provide for insertion of COTS into the CTIAwith Government approval and demonstrate that COTS, reusable NDI assets, and other components are logistically supported throughout the life cycle. The contractor shall describe and demonstrate the strategy for reducing product or system and associated supportability costs through insertion of COTS and other reusable COTS or NDI products. The contractor shall establish a process to logistically support COTS or NDI products. The contractor shall describe the availability of commercial repair parts and repair services, facilities and manpower required for life cycle support, and demonstrate that they are adequate to ensure long term support for COTS products. The contractor shall provide the proposed methodology for pass through of COTS warranties to the Government.

3.1.3.CTIA Software/System Test Engineering:

The contractor shall provide an overarching software and systems test, verification and validation assurance methodology for the CTIA. Test Engineering shall be initiated at the onset of the delivery order contract, and implemented throughout the entire period of execution for all components, services, and assets of the CTIA. Test Engineering shall be a proactive activity within the CTIA.

  1. The contractor shall test and evaluate the CTIA using innovative testing methodologies, processes and tools consistent with the SOA and TaaS philosophy to ensure it meets and fulfills the requirements of the CTIA, LT2 product line and core LT2 CPM environment/construct. The test efforts shall consist of a logical sequence of service, composition and system level tests to include a complete system re-initialization, and technical performance and Quality of Service (QoS) measurements.
  1. The contractor shalldesign, implement, and maintain an innovative system testability process satisfying all testability requirements of the CTIA components, services and assets throughout the system life cycle which is traceable throughout the design process, is integrated with other system engineering requirements, and is disseminated to design personnel and subcontractors.
  1. The contractor shall establish an automated interface test framework for CTIA Service Oriented Integration (SOI) type of interfaces. The contractor shall provide capabilities to manage test cases for unit testing of interfaces, ability to group or compose them, and generate metrics and reports after test execution.
  1. The contractor shall perform white box interface testing for service-oriented interfaces. The contractor shall establish, evolve, manage and maintain an innovative automated testing methodology to include—but not limited to—services, tools, applications, processes, governance, etc., that provides an environment for automated unit, service or component testing, automated web application testing, mobile computing application testing, message/protocol testing, performance and security testing, regression testing, automatic test case generation, and coding standard enforcement.
  1. The contractor shall define the means for demonstrating and validating that the diagnostic capability meets specified requirements, using QoS demonstrations, test program verification, and other demonstration methods. 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. The contractor shall establish a Test Engineering program that accomplishes the following:
  2. Establishment of sufficient, achievable and affordable state-of-the-art testing processes and tools
  3. Integration of testing into equipment and systems during the architecture and design process in coordination with the maintainability design process
  4. Evaluation of the extent to which the design meets testing requirements
  5. Inclusion of testing in the program review process
  1. The contractor shall develop and provide training for the CTIA familiarization and component/service test development and deployment as requested by the Government.

3.1.4.Software/Systems Engineering:

The contractor shall design, develop, test, integrate, configuration manage and maintain the CTIA system software and firmware in accordance with the LT2 CPM Operations Guide. The contractor shall follow formalindustry-accepted software development practices that are consistent with at least Level 3 of the Capability Maturity Model Integration for Development (CMMI-DEV).