Att_05.1_CTIA_PWS.docx

PEO STRI

PWS-2018-068

20 Nov 2018 Version 1.1

PERFORMANCE WORK STATEMENT

FOR THE

LIVE TRAINING TRANSFORMATION (LT2)

COMMON TRAINING INSTRUMENTATION ARCHITECTURE (CTIA)

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

Engineering

Concurrence: ____________________ Dr. Jeremy Lanman Chief Engineer, PD DT Date: __________

Concurrence: ____________________ Mike Dillon Chief Engineer, PdM CTIS Date: __________

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

Program Management

TABLE OF CONTENTS

REVISION LOG

PEO STRI

20 Nov 2018 Version 1.1 i i

PERFORMANCE WORK STATEMENT

FOR THE

LIVE TRAINING TRANSFORMATION (LT2)

COMMON TRAINING INSTRUMENTATION ARCHITECTURE (CTIA)

DELIVERY ORDER

Scope:

This Performance Work Statement (PWS) defines the work efforts for the continued support, development, and evolution of the Common 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.

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 Live and Synthetic Training Environment (STE) 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 live and STE training domains. It consists of the architecture infrastructure, architecture services, software components, governance, standards, development environment, 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 home stations. 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 Product Lead office. The CTIA-based systems are fielded and fully operational at the Army’s Combat Training Centers (CTCs) and at numerous home station 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.

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.

Department of Defense Directives:

DOD 8570.01 M Information Assurance Workforce Improvement Program DODD 8570.1 Information Assurance Training, Certification and Workforce Management

DODI 8500.1 Cyber Security

Availability of Department of Defense Directives:

Copies are available on the WWW at URL: http://www.dtic.mil/whs/directives/ Other Government Assets, Documents, Drawings and Publications:

CNSSI 1253 Committee on National Security Systems Instruction (CNSSI) 1253

NIST SP 800-53 National Institute of Standards and Technology (NIST) Special Publication (SP) 800-53: Security and Privacy Controls for Federal Information Systems and Organizations

AR25-2 Information Assurance

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

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

LT2-TRADE-PLAN-2013-00009 LT2 Configuration Management Guide (www.lt2portal.mil)

SOW-2018-007 CPM Plus Base SOW

PWS-2018-067 CPM Plus Construct PWS

SOW-2018-010 CTC-IS PDSS SOW

ANSI/EIA-748 Standard for Earned Value Management Systems Intent Guide

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 SOW and the references cited herein, the text of the PWS shall take precedence.

Requirements:

The contractor shall execute the functions of Post Deployment Software/System Sustainment (PDSS) within the LT2 CPM framework in accordance with PWS-2018-067 and synchronized with SOW-2018-010 for the Instrumentation System and SOW-2017-033 Statement of Work for LT2 Hardware Product Line such as Program Management, Configuration Management, Data Management, and modifications and upgrades. The work tasks described in the PWS are intended to address the core functionalities of the CTIA.

CTIA Management, Organization and Processes:

The contractor shall perform all of the required tasks necessary to protect the existing investment of the CTIA, design, implement, maintain and govern the CTIA for the LT2 Product Line in accordance with LT2 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 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. The contractor shall not use or release any assets, digital information or documentation for commercial purposes without Government approval.

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

The contractor shall provide PDSS with all CTIA components, services and assets. The contractor shall utilize the currently defined LT2 processes (Shared Asset Working Group (SAWG), Problem Tracking Report (PTR) Review Board (PRB), etc.) in accordance with the LT2 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 Operations Guide.

2. The contractor shall adopt an agile development methodology in the development, sustainment and modernization of LT2 software assets. The contractor shall ensure close collaboration between the development team and stakeholders include but not limited to product fielding teams and user community

3. The contractor shall define, maintain, and integrate the allocated, functional, and product 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.

4. 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 such as DOORS. The contractor shall maintain and update the requirements traceability database throughout the base and delivery orders contract.

5. The contractor shall support, design, develop, refine, evolve, modify and mature existing and future CTIA services, components and assets (inclusive of documentation) to allow for technology refresh and insertion into the CTIA.

6. The contractor shall design CTIA software, develop executable source code, perform unit, composition and integration testing, and integrate software components and services (with each other and with hardware components) to meet CTIA requirements.

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

8. 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 Operations Guide.

9. The contractor shall continue and sustain a 24/7 CTIA Help Desk. The Help Desk shall act as a single point of entry into the CTIA for problem identification and support. The CTIA Help Desk shall assist the products fielding teams, on site and off site support teams. The Help Desk shall be supported by the Configuration Management (CM) and management activities to synchronize sustainment and development efforts for architectural services. The contractor shall follow LT2 processes in accordance with the LT2 Operations Guide for handling emergency/exception changes to services for post inclusion into the CTIA.

10. The contractor shall develop interactive user training using intelligent agent tutoring system and provide all training materials for the CTIA familiarization and component/service development and deployment as requested by Government. The contractor shall leverage LT2 initiatives (i.e. Lighthouse TDP initiative) in developing, storing and ensuring that training material is updated and accurate prior to each the delivery. The training content shall be embedded in the LT2 enterprise and easily accessible through variances of platforms and networks (i.e. Workstation, Mobile handheld, local access, cloud access)

11. The contractor shall document and participate in Integrated Product Teams (IPT) (e.g. Shared Asset Working Group (SAWG)). The contractor shall review all changes to the established CTIA baseline, and all changes to the requirements including changes to the PWS, Contract Data Requirements List (CDRL), and the delivery order contract schedule.

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

0. 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 components through 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-000189 CTIA Strategic SOA Roadmap and Specification; and Appendices B, C and D found in this PWS). 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:

a. Clearly define and describe all component, service and system interfaces.

b. Define and document all subsystem and configuration item (CI) level interfaces to provide full functional, logical, and physical specifications.

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

d. Identify the interface and data exchange standards between the component, module, service, composition or system and the interconnectivity or underlying information exchange medium.

e. Identify component and services development criteria. Criteria shall be derived from industry best practices.

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

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

2. The contractor shall ensure the technology insertion and obsolescence management applies appropriate Cybersecurity (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. The contractor shall maintain a CS process to guide management and design actions, document decisions, specify and track CS requirements, document certification efforts, and identify possible solutions for CTIA. The contractor shall ensure CTIA components and services (e.g., software, hardware, middleware) meets all DOD and Army Regulations relating to and required for CS. The contractor shall integrate CS into their management processes, document decisions, specify and track CS requirements, document certification efforts, identify possible solutions, and maintain operational systems security in accordance with (IAW) DoDI 8500.01, DoDI 8510.01 (RMF), CNSSI 1253, NIST SP 800-53, DoDI 8582.01and AR 25-2.

3. The contractor shall conduct a Technical Review (TR) to define and demonstrate CTIA core functions to include new capabilities, external interfaces and baseline resiliency . The TR shall be a formal technical review of the allocated baseline and changes made to the allocated baseline. TR shall be conducted for each new CTIA version release.

4. The contractor shall, as required, conduct a limited validation demonstration to validate the system’s ability to fulfill operational requirements. The contractor shall replicate the operational conditions to conduct this event. The conditions shall include but not limited to, data throughput, external systems interoperability and infrastructure.

5. The contractor shall develop and provide interactive training using intelligent tutoring agent for the CTIA familiarization and component/service development and deployment as requested by the Government. CTIA familiarization shall be easily accessible through different platforms and networks (i.e. thick client, mobile handheld, local network, cloud enabled).The contractor shall leverage LT2 initiatives (i.e., Lighthouse TDP initiative).

6. The contractor shall document and model the CTIA components 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) or JavaScript Object Notation (JSON). 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. The contractor shall provide CTIA architecture traceability to DoDAF live training architecture views.

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

8. The contractor shall consider use of Commercial Off The Shelf / Non-Developmental Items 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.

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

10. 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. The contractor shall develop failsafe capabilities to gracefully handle system and software service failures to minimize overall system downtime and ensure seamless system recovery.

11. The contractor shall demonstrate that all CTIA software components, modules and services are instrumented to capture performance and training data.

12. The contractor shall implement a data analytic solution to mine and analyze in real time large volumes of data captured in CTIA software components, modules and services. The data analytic solutions shall intelligently predict CTIA software component, modules and services performance degradation and failures in operational environment.

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

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

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

16. The contractor shall provide for insertion of COTS into the CTIA with 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. All COTS CS products and CS-enabled products shall be certified compliant with 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 CTIA components, services, and product line assets.

0. 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 Service Oriented Architecture (SOA) and Training as a Service (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.

2. The contractor shall design, 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. The contractor shall develop a software test plan. The contractor is required to ensure that this document is current on the LT2 Portal on a bi-annual basis. 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.

3. The contractor shall sustain and maintain Automated Test Framework (ATF) 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.

4. The contractor shall perform white box interface testing for service-oriented interfaces for each baseline release. The contractor shall evolve, manage and maintain LT2 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.

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

a. Establishment of sufficient, achievable and affordable state-of-the-art testing processes and tools

b. Integration of testing into equipment and systems during the architecture and design process in coordination with the maintainability design process

c. Evaluation of the extent to which the design meets testing requirements

d. Inclusion of testing in the program review process

6. The contractor shall develop and provide training for the CTIA familiarization and component/service test development and deployment as requested by the Government.

7. The contractor shall run continuous full system test and report result summary to the Government.

DI-IPSC-81438A: Software Test Plan

0. 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 formal industry-accepted software development practices that are consistent with at least Level 3 of the Capability Maturity Model Integration for Development (CMMI-DEV).

1. The contractor shall design CTIA software, develop executable source code, perform unit and composition testing, and integrate software components and services (with each other and with hardware components) to meet CTIA requirements. The contractor shall develop and update a Software Design Description document and ensure that this document is current on the LT2 Portal on a bi-annual basis. 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.

2. The contractor shall design, develop, integrate and verify the CTIA to fulfill the objective architecture, architectural goals and PM TRADE business goals in accordance with the SOA and TaaS philosophy, core LT2 capabilities and core LT2 activities. The contractor shall describe their governance methodology/approach, processes, and tools for CTIA SOA and testing of services to include the assets and technologies involved in the entire SOA and software services life cycle.

3. The contractor shall perform architecture verification and validation of the CTIA. During development of the CTIA, the architecture shall be verified through a combination of the following:

a. Formal and informal reviews

b. Analysis of architecture

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

d. Application of static and dynamic modeling

4. The contractor shall ensure that the CTIA is consistent with all applicable CS requirements, and if required, support the obtainment of appropriate CS certifications and approvals. 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.

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

6. The contractor shall design, develop, test, integrate, configuration manage and maintain any enhancements required to establish an interface between CTIA and external systems. The contractor shall ensure that the interface support conversions of the data and that no fidelity is lost in the conversion. The contractor shall ensure that the design supports the E simulation interoperability.

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

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

9. The contractor shall document, and the Integrated Product Team (IPT) (e.g. Shared Asset Working Group (SAWG)) shall review, all changes to established CTIA baseline and all changes to the requirements including changes to the PWS, to the CDRL, and to the delivery order contract schedule

DI-IPSC-81435A: Software Design Description

Hardware and Software Integration:

During LT2 CTIA development, the contractor shall leverage Hardware Product Line managed by LCPM to determine the hardware infrastructure specification the CTIA baseline will require to fully function as integrated system. The contractor shall conduct system level approval reviews with the Government and the LT2 SAWG to demonstrate that the total system has been considered in order to satisfy specification and baseline requirements for each system level, and to confirm readiness for production, distribution, operations, support, training, continuing improvement, and disposal.

Systematic Quality:

The contractor shall implement an overarching Quality of Service Assurance (QoSA) program to ensure that CTIA requirements are met. The contractor shall implement and maintain a QoSA program using industry accepted best practices and subject to Government program approval. The contractor shall develop, track, document and provide to the Government the metrics necessary to determine the Government’s Return on Investment (ROI) for the development, implementation, synchronization, and maintenance of CTIA services. In addition to ROI, the contractor shall collect, analyze, synthesize and interpret CTIA service performance data to report on metrics that demonstrate baseline stability and resilience. Metrics shall include but not limited to number of software defects per service, service downtime, and data analytics result. The contractor shall provide these metrics to the Government through dashboards on the LT2 repository. Metrics shall be developed to assist management visibility into an adequate process control system.

The Contractor’s quality program shall demonstrate its prevention-based outlook by meeting the objectives stated in the PWS throughout all areas of performance. The Quality Assurance Program Plan shall be developed to specify the Contractor’s responsibility for management and quality control actions to meet the terms of the contract. The Quality Assurance Program Plan as a minimum shall address continuous process improvement; procedures for scheduling, conducting and documentation of inspection; discrepancy identification and correction; corrective action procedures to include procedures for addressing Government discovered non-conformances; procedures for root cause analysis to identify the root cause and root cause corrective action to prevent re-occurrence of discrepancies; procedures for trend analysis; procedures for collecting and addressing customer feedback/complaints.

The contractor shall develop, maintain and keep current a Quality Assurance Program Plan document. The contractor is required to ensure that this document is current on the LT2 Portal on a bi-annual basis. 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-QCIC-81794: Quality Assurance Program Plan

The Contractor’s Qulaity Assurance Program Plan shall be incorporated into and become part of this contract after the plan has been accepted by the KO. Proposed changes made after KO acceptance shall be submitted in writing through the COR to the KO for review and acceptance prior to implementing any revision. The Contractor’s QCP shall be maintained throughout the life of the contract and shall include the Contractor’s procedures to routinely evaluate the effectiveness of the plan to ensure the Contractor is meeting the performance standards and requirements of the contract.

Software Quality:

The contractor shall achieve and maintain the following Software product baseline quality objectives. The contractor shall report status of the below quality objectives during engineering IPTs.

1. Reliability and Resiliency : Product baseline shall

a. Include fail over solutions

b. Be able to withstand and recover from failures

c. Be free of single point of failure

d. Be scalable

2. Stability and Functionality: Product baseline shall

a. Reach maturity within short of period of time

b. Number of discovered software defects should align with industry standard for the same level of complexity

3. Usability: Product baseline functions shall

a. Be easily understood and operated by user community in a given operational environment

b. Meet user requirement

c. Be operated from different platforms and networks

4. Agility and Testability: Product baseline shall

a. Be able to adjust to new specifications and/or operating environments

b. Adaptive to new technologies without significant architecture impact

c. Modules, components and services are easily replaceable in specific operation environment

d. Compliant with SOA design principals to include but not limited to loose coupling, stateless, reusable

5. Supportable: Product baseline shall

a. Consist of simple code and up to LT2 coding standard

b. Easy to identify root cause of failure (debug)

c. Includes common (commercial/open source) tools to troubleshoot

d. Modules, components and services are instrumented to autonomously report performance feedback

e. Able to test and certify that system changes doesn’t negatively impact the quality objective characteristics Program Management:

The contractor shall provide overall program management and administrative support to ensure the requirements of the delivery order contract are accomplished. The contractor shall develop, maintain, and integrate an overall integrated master plan for the execution of the CTIA. The contractor 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 CTIA. The contractor shall track and maintain resources to ensure overall programmatic performance.

1. The contractor shall implement proactive partnering processes with the Government concerning all aspects of the CTIA design, implementation and sustainment.

2. The contractor shall materially participate, provide membership, and assume leadership/management roles (as coordinated with the Government) throughout the various IPTs required for the CTIA execution.

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

4. The contractor shall conduct upon request by the Government programmatic management reviews to provide the Government a “state of the CTIA” status and update. These reviews shall include the entirety of the CTIA activities being completed, assessment as to the effectiveness and utilization of the CTIA, and status reviews for cost, schedule and performance of all affiliated CTIA activities. These reviews shall provide updates to the risk management planning, obsolescence planning and execution, earned value management, and cost accounting. The contractor shall provide visibility on the progress, performance, and status of major subcontractors.

DI-MGMT-80227: Contractor’s Progress, Status and Management Report

5. The contractor shall establish, maintain, and use in the performance of this delivery order, an integrated performance management system. Central to this integrated system shall be a validated Earned Value Management System (EVMS) in accordance with contract clauses and the EVMS guidelines contained in ANSI/EIA-748. To establish the integrated performance management system, the EVMS shall be linked to and supported by the contractor’s management processes and systems to include the Integrated Master Schedule (IMS), contract work breakdown structure, change management, material management, procurement, cost estimating, and accounting. The correlation and integration of these systems and processes shall provide for early indication of cost and schedule problems, and their relation to technical achievement.

DI-MGMT-81468: Contract Funds Status Report

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

7. The contractor shall support and attend various exhibitions and conferences as appropriate (e.g. AUSA, Capitol Hill, I/ITSEC, etc.). The contractor shall provide program management and technical support to these conferences. The contractor shall provide, as required, technical solutions and representations that demonstrate the performance and capabilities of the CTIA and components/services in support of the LT2 product line and LT2 products.

8. The contractor shall develop and maintain a schedule that shows planned efforts to achieve each significant accomplishment, CTIA program synchronization relative to service/component and baseline releases, and events relating to the program. The contractor shall generate and maintain an IMS, to include schedules of the core and non-core activities required to execute CTIA. 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-MGMT-81861A: Integrated Program Management Report (IPMR)

9. The contractor shall initiate and implement Associate Contractor Agreements (ACAs) as needed to instantiate CTIA collaboration efforts and to maintain CTIA with emerging requirements/systems.

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

11. The contractor shall prepare, implement, and maintain a Work Breakdown Structure (WBS) to address the core functionalities and efforts associated with CTIA, and the additional product tasks added to the overall effort into a cohesive WBS. The contractor shall align with the Government WBS provided in the base PWS for CPM. The WBS shall be maintained and synchronized with the IMS and Integrated Master Plan (IMP). 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-MGMT-81334D: Contract Work Breakdown Structure

12. Contractor Manpower Reporting: The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services under this contract for the LCPM via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address: http://www.ecmra.mil/. Reporting inputs will be for labor executed during the period of performance during each Government Fiscal Year (FY) which runs October 1 through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors can find User Guides, Frequently Asked Questions and may direct questions to the help desk at http://www.ecmra.mil/.

Cybersecurity:

0. Access to Government Information Systems:

All contractor employees with access to a Government information system shall be registered in the Army Training Certification Tracking System (ATCTS) at commencement of services, and must successfully complete the DOD Cyber Awareness Training prior to assess to the Information System and then annually thereafter.

0. Cybersecurity/Information Technology Training:

All contractor employees and associated sub-contractor employees shall complete the DOD Cyber Awareness Training before issuance of network access and annually thereafter. All contractor employees working CS/IT functions must comply with DOD and Army training requirements in DODD 8570.01, DOD 8570.01-M and AR 25-2. 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.

General Protection and Credentialing:

Access and General Protection:

The Contractor and all associated subcontractor employees shall provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) as directed by DOD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

Credentialing:

The Common Access Card (CAC) shall be the principal identity credential only for those contractor employees supporting and requiring access to DoD installations, Government leased facilities, buildings and government information systems per FAR 52.204-9.

The prime and subcontractor shall coordinate with their government sponsor and complete DD Form 1172-2 in order to obtain a CAC. The prime and subcontractor employee will be issued a CAC only if duties involve one of the following:

· Require both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely;

· Remote access, via logon, to a DoD network using DoD-approved remote access procedures; or

· Physical access to multiple DoD facilities or multiple non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more.

The prime and subcontractor employees must, at a minimum, have a favorably adjudicated National Agency Check with Inquiries (NACI) or an equivalent or higher investigation in accordance with Army Directive 2014-05. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled NACI at the Office of Personnel Management.

The contractor shall ensure that all employees clearly display the prescribed identification at all times while they are working within government facilities and performing official duties in execution of contract requirements.

Contractor shall account for all forms of U.S Government-provided identification credentials issued to Contractor (or their employees including subcontractor employees in connection with performance) under the contract. Contractor shall return such identification credentials to the issuing agency at the earliest of any of the circumstances listed below, unless otherwise determined by the U.S. Government. The contracting officer may delay final payment under an individual DO if Contractor or subcontractor fails to comply with these requirements. The contractor shall return all identification credentials when;

1. No longer needed for contract performance.

2. Completion of Contractor employee’s employment.

3. Contract completion or termination.

Non-Credentialing:

For contractors and all associated subcontractor employees that do not require CAC, but require access to a DoD facility or installation, shall comply with adjudication standards and procedures using the National Crime Information Center Interstate Identification Index (NCIC-III) and Terrorist Screening Database (TSDB) (Army Directive 2014-05/AR 190-13), applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative), or, at OCONUS locations, in accordance with status of forces agreements and other theater regulations.

Disclosure of Information:

The contractor shall comply with the protection standards and guidance described in DoD Manual 5200.1 and AR 380-10 to prevent foreign intelligence collection and/or the unauthorized disclosure of information to foreign nationals.

Security The Contractor shall comply with the security regulations listed in the reference section of this document and the security requirements specified in Contracts Security Classification Specifications, DD Form 254 and addendums sheets.

The Contractor will be required to have a SECRET facility clearance with no storage requirements. Based on various task orders the Contractor could require access to a combination of collateral SECRET information, communications-security (COMSEC) information, Controlled Unclassified Information (CUI), Technical Information/Documents and For Official Use Only (FOUO) information only. If the security requirements of the contract or task order exceeds the requirements listed above, the GCA must have the SOW base DD 254 updated by the Cognizant Security Authority (CSA).

In performing this contract, the Contractor could have access to classified materials and information within the United States and overseas.

Performance of this contract will be worldwide as designated by individual Task Orders. Individual Task Orders will specify security clearance and security requirements within each PWS. Individual DD Form 254s will not be issued for each classified Task Order as the base DD 254 will be used.

Personnel Security:

The contractor shall issue security clearances only to those contractors who will have access to classified information. Some positions/duties may not require a clearance but all positions/duties will require investigation for duties and access to U.S. Government systems and technical information. The Contractor shall ensure that employees performing under this contract have the appropriate clearance not to exceed the requirements supported.

The contractor shall appoint a security officer who shall (1) be responsible for handling all security aspects of the work performed under this contract; (2) assure compliance with all DOD and US Army regulations regarding security listed in the reference section of this SOW. (3) shall establish and maintain an Insider Threat Program per DoDM 5220.22M para 1-202.

Security Training.

All contractor personnel have an individual and official responsibility for safeguarding national security information and controlled…