Attachment_1_SOW_03FEB16.docx

Draft Statement of Work (SOW) For Intelligence and Electronic Warfare Tactical Proficiency Trainer

(IEWTPT)

U.S. Army Program Executive Office for Simulation, Training, and Instrumentation (PEO STRI) 12350 Research Parkway Orlando, FL 32826-3276

Rick Jimenez Bob Dixon IEWTPT Lead Engineer PdM STS Chief Engineer

LTC Paul Weizer, PdM STS

TABLE OF CONTENTS

UNCLASSIFIED (U) // FOR OFFICIAL USE ONLY (FOUO)

Source Selection Information -- See FAR 2.101 and 3.104// UNCLASSIFIED (U) // For Official Use Only (FOUO)

1. SCOPE

This Statement of Work (SOW) defines the overall work to be performed as part of the Intelligence & Electronic Warfare Tactical Proficiency Trainer (IEWTPT) System, Block 2, Full Operational Capability (FOC) analysis, design, development, integration, testing, delivery, and exercise technical support. The purpose of this SOW is to define the tasks, products, equipment, supplies, facilities, data items and required labor hours to accomplish the tasks associated with this contract. FOC is attained when all units and/or organizations in the force structure scheduled to receive a system: 1) have received it and 2) have the ability to employ it and maintain the system as intended.

BACKGROUND

IEWTPT is an incrementally developed and deployed Military Intelligence (MI) software-intensive training capability. The U.S. Army Program Executive Office (PEO) Simulation, Training, and Instrumentation (STRI) has a requirement to produce MI training capabilities through analysis, design, development, integration, testing, delivery, and exercise technical support of the baseline (Block 1) IEWTPT and follow-on capabilities (Block 2). The IEWTPT provides warfighting Commanders at all echelons the ability to train the Intelligence Warfighting Function (IWF) while training on real world, organic MI assets used by multiple MI Military Occupational Specialties (MOS). IEWTPT is a training system and tool set that simulates and/ or stimulates MI warfighting equipment and tools to replicate the necessary environment required to provide proficiency and sustainment training for MI personnel, battlestaff, system operators, analyst and collectors, and allows Commanders to synchronize, task, manage, efficiently utilize, and fuse/ exploit information from multiple intelligence assets.

The Block 1 IEWTPT consists of two major functional components:

The Technical Control Cell (TCC). The TCC is a dual-enclave system which provides the capability for developing, managing/ controlling, and enabling training events by creating a simulated data environment supporting All Source, Signal Intelligence (SIGINT), and Geospatial Intelligence (GEOINT) training requirements. The two enclaves support interfacing with a constructive simulation training environment and can provide multi-level training capabilities [Secret Collateral and Top Secret (TS)/ Sensitive Compartmented Information (SCI)], as well as exercise control, play-back, and after action review (AAR).

The Human Intelligence Control Cell (HCC). The HCC provides sustainment training for HUMINT/ Counter Intelligence (CI) collectors in an immersive, life-like virtual training environment. The HCC utilizes avatars and speech recognition software to support Soldiers and HUMINT/CI collectors in refining and sustaining skills in tactical questioning, interrogation, screening, and use of an interpreter through free-flowing conversation with human-like characters.

IEWTPT Sub Components include:

The Enclave Bridge (EB) is the IEWTPT Cross-domain Solution (CDS) that allows one-way passage of data from low to high (Secret TCC to TS/SCI TCC) on a dual enclave TCC.

Target Signature Arrays (TSA’s) are simulation interfaces to complementary Intelligence system tactical platforms.

The starting point of this effort relies on an existing IEWTPT (Block 1) product baseline and seeks to produce additional (Block 2) MI training capabilities through further analysis, design, development, integration, testing, delivery, and exercise technical support of the baseline IEWTPT to augment, enhance, and/or improve the current IEWTPT MI training capabilities.

1. APPLICABLE DOCUMENTS

Applicable documents supporting work to be performed under this SOW are listed below. In the event of a conflict between documents referenced herein and the contents of this SOW, the SOW shall be the governing requirement.

DEPARTMENT OF DEFENSE DOCUMENTS

Earned Value Management (EVM) System ( May 2011)

AVAILABILITY OF DEPARTMENT OF DEFENSE DOCUMENTS

Copies are available on the WWW at URL: https://assist.dla.mil/online/start/ Copies are available on the WWW at URL: http://www.dtic.mil/whs/directives/

OTHER GOVERNMENT DOCUMENTS

AVAILABILITY OF GOVERNMENT DOCUMENTS

Copies of the other documents are available from PEO STRI (PM ITTS / PdM STS), 12350 Research Parkway, Orlando, FL 32826-3275. ATTN: wesley.m.whisner.civ@mail.mil

2. REQUIREMENTS

The IEWTPT System development work extends, augments, enhances, and builds on existing capabilities towards an FOC end state. The Contractor shall perform the work as described in the following areas.

PROGRAM MANAGEMENT

The Contractor shall provide the overall management and administrative effort necessary to ensure the requirements of this contract are accomplished. The Contractor shall use an integrated project management approach for the overall management and execution of this contract. The Contractor shall provide a management structure which supports providing MI training for the US Army. The Contractor shall provide key personnel, staff, and team members with required skills and domain experience in All-Source, SIGINT, HUMINT, and GEOINT MI disciplines. The Contractor shall provide an organizational structure which supports a working relationship with stakeholders such as PEO Intelligence, Electronic Warfare and Sensors (IEW&S) and other MI stakeholders to ensure the IEWTPT program remains closely aligned with the ISR system platforms and plans to co-develop and integrate additional emerging ISR system sensor training requirements into the IEWTPT baseline. The Contractor shall track program progress utilizing metrics. The Contractor shall provide a team to manage the program throughout the lifecycle of the program. The Contractor shall plan, implement, and maintain a life cycle cost (LCC) management process to minimize the system cost and use LCC to conduct trade studies, evaluate design and support alternatives, and select the resource support requirements. The Contractor shall define and monitor metrics and technical performance measures (TPMs) to evaluate the performance of each critical technical and management task and evaluate conformance of the evolving products with performance requirements and cost constraints. The Contractor shall facilitate Government insight into contract activities. The Contractor shall provide real-time, user-friendly, persistent electronic remote access to all appropriate Program Management and development/ technical data, including fielding plans and schedules to enable periodic review of contract actions and progressively demonstrate readiness to complete significant events. The Contractor shall conduct Program Management Reviews and Design Reviews. The Contractor shall provide all agendas, meeting minutes, and presentation material.

REF: CDRL B006 (DI-MGMT-81334D) Contract Work Breakdown Structure (CWBS) REF: CDRL B003 (DI-MGT- 80227) Contractors Progress, Status and Management Report

INTEGRATED MASTER PLAN (IMP)

The Contractor shall implement, manage in accordance with, update, and maintain the contract IMP. The Contractor shall develop the system in accordance with the IMP. The IMP shall be used throughout the contract as a management tool to assess progress and determine success in achieving program requirements. The Contractor shall report on work in progress in accordance with the IMP at each program review, at selected technical reviews and at Government discretion. The IMP shall depict and provide traceability to the CWBS.

INTEGRATED MASTER SCHEDULE (IMS)

The Contractor shall develop, implement, manage in accordance with, update, and maintain the contract IMS. All contract schedule information delivered or presented at program reviews shall originate from the IMS, shall be traceable to the IMP, and shall contain all critical events and exit criteria, accomplishments, predecessors and successors events, and their dependencies. The IMS shall address total program activities including activities performed by major subcontractors. The Contractor shall develop the logic resource loaded network that accurately portrays the sequence and relationship of activities defining the total development and production program. These activities shall be keyed to the CWBS. The activities’ time and cost data shall be updated to reflect accomplished tasks and any changes in activity time and cost estimates. The Contractor shall conduct critical path analysis of the tasks and identify problem areas and corrective actions required to eliminate or reduce schedule impacts.

REF: CDRL B005 (DI-MGMT-81650) Integrated Master Schedule (IMS)

FINANCIAL MANAGEMENT

The Contractor shall plan, budget, schedule, and control the resources allocated to meet the requirements of the contract. The Contractor shall document and track the status of all appropriated funds associated with the contract to include payments, cancellations and invoices against each contract line item and subline item. The Contractor shall extend the Government-provided Program Work Breakdown Structure to lower levels in the Contractor’s CWBS that define the lower level components of what is to be procured and includes all the product elements (hardware, software, data, or services), which are defined by the Contractor and the Contractor’s responsibility.

The extended CWBS shall serve as the framework for contract planning, budgeting, and reporting of cost and schedule status. The Contractor shall identify major elements of subcontracted work in the extended CWBS. The Contractor may propose changes to the CWBS to enhance its effectiveness in satisfying program objectives. The Contractor shall continually update an integrated database during contract performance with pertinent records and data that underlie and support the cost and schedule data reported.

REF: CDRL B004 (DI-MGMT-81468) Contract Funds Status Report (CFSR)

EARNED VALUE MANAGEMENT (EVM)

The Contractor shall integrate cost, schedule, and performance management information. The Contractor shall implement, maintain, and use an EVM process to monitor project execution effectiveness and forecast trends in cost and schedule performance in compliance with guidelines in the American National Standards Institute/Electronic Industries Alliance Standard 748 (ANSI/EIA-748), Earned Value Management Systems (EVMS), and meets contractual requirements. The Contractor shall document the integrated cost and schedule status of work progress on the contract and relate technical performance with cost and schedule accomplishment using procedures for planning work, controlling costs, and measuring performance based on ANSI/EIA-748. The Contractor shall establish technical, schedule, and cost targets to perform the Cost Plus Fixed Fee (CPFF) portions of this contract within the available budget.

REF: CDRL B002 (DI-MGMT-81861) Integrated Program Management Report (IPMR)

SUBCONTRACTOR MANAGEMENT

The Contractor shall manage and have agreements with subcontractors and partners as required. Contractor shall integrate subcontractors into program Integrated Product Teams (IPT’s) and incorporate subcontractors performance in program management and tracking systems such as remote access management information and reporting systems. The Contractor shall ensure the requirements of this contract are applied to all subcontracts and associate contracts.

INTEGRATED BASELINE REVIEW

The Contractor shall engage jointly with the Government’s Program Management and Technical Teams in Integrated Baseline Reviews (IBRs) to evaluate the risks inherent in the contract’s planned performance measurement baseline. An IBR shall occur as soon as feasible but not later than six months after contract award, and subsequently following major changes to the program baseline. Each IBR shall verify that the Contractor is using a reliable performance measurement baseline, which includes the entire contract scope of work, is consistent with contract schedule requirements, and has adequate resources assigned.

The Contractor shall participate with the Government in the assessment of program risk and the degree to which the following have been established:

INTEGRATED PRODUCT TEAMS (IPTs) Contractor shall implement and maintain an IPT structure for the duration of the contract. The IPT shall bring together functions that have a stake in the performance of a product or process and the IPT shall concurrently make recommendations for decisions affecting that product or process (e.g., Requirements Analysis, Market Research, Design, Development, Integration, Test, Evaluation, and Peer Reviews). Contractor shall apply IPT’s at various levels ranging from the overall project structure to specific groups functioning across existing project units. Each IPT shall consist of Government and Contractor personnel and have Government and Contractor co-chairs. With Government input, Contractor shall define and document composition, structure, roles, and responsibilities of each IPT. Each IPT shall develop a governing charter and maintain a membership list. Each IPT shall be empowered to make critical life cycle decision recommendations regarding each product or process within their assigned areas in compliance with their defined charter authority. Conference Agenda and Conference Minutes shall be available through user-friendly, remotely accessible information system. IPT decision recommendations shall be processed and dispositioned by the Government Project Director (PD).

IPT MEETINGS

Contractor shall coordinate and host or participate in IPT meetings to be conducted throughout the contract period of performance. IPT meetings shall provide a forum for maintaining a continuous interchange of ideas and issues including snapshot data of Deficiency Reports (DR’s) status (open, closed, working, etc.) for current requirement analysis; design and test events, as agreed to by the Contractor and Government; and to identify and resolve potential problem areas. Each IPT shall publish an agenda before each meeting. Each IPT shall record and maintain meeting minutes. Meeting minutes shall be shared across IPTs. Conference Agendas and Conference Minutes shall be available through electronic remote access means.

CONFIGURATION MANAGEMENT (CM)

The Contractor shall use an automated internal CM process to monitor, update and control all configuration documentation, physical media, and physical parts representing or comprising the system Configuration Items (CIs). The Contractor shall also plan and implement an automated CM function to perform configuration control, configuration identification, audits, and status accounting in a system-engineering guided environment. The Contractor shall develop, maintain and update CM procedures and processes for control of all hardware and software baselines. The CM process must handle all levels of product and process integration to build and support the product as well as manage the sequence of significant production events. The Government will maintain control of the functional baseline (FBL) defined by the System/ Sub-system Specification (SSS), Interface Control Documents (ICDs), and Software Requirement Specifications (SRS).

The Contractor shall identify, manage, and maintain version control of all developed project artifacts. The Contractor shall establish processes, procedures and tools, and use these to maintain hardware, software and data, system configuration information, and all relevant information about the system.

The Contractor shall recommend changes or improvements where appropriate to improve the effectiveness and efficiency of those processes. The Contractor shall participate in a program level Configuration Control Board (CCB) to evaluate recommended changes, deviations or waivers.

CONFIGURATION CHANGE MANAGEMENT

The Contractor shall establish a systematic and measurable configuration change management process for managing product configuration changes and variances. Once the system requirements have been approved by an authorized project management representative, the Contractor shall effect changes to the baseline requirements only after the proposed change has been approved using the change process. The Contractor shall

1. document and uniquely identify each change.

1. classify requested changes to aid in determining the levels of review and approval.

1. clearly and completely document request for change.

1. consider the technical, support, schedule, and cost impacts of a requested change before making a judgment to approve the change for implementation and incorporation in the system and its documentation.

1. determine potential effects of a change and coordinate impacts with the impacted areas of responsibility.

1. determine the effectivity for each change and identify which units of the system are to be changed and which units will be included in a retrofit.

1. verify implementation of a change to ensure consistency between the system, its documentation, and its support elements.

1. document variances, when authorized by the appropriate level of authority.

CONFIGURATION VERIFICATION AND AUDIT

The Contractor shall verify and audit the system configuration information to ensure that requirement are met and accurately documented. The Contractor shall

a. verify the system attributes through a systematic comparison with the associated results of system tests, analyses, inspections, demonstrations or simulation models.

b. maintain surveillance over the configuration management process to ensure it is being followed and remains in compliance with requirements.

Contractor Internal Hardware Build-Up Audit Concurrent with manufacture of piece parts and incoming inspection of procured parts, a 100% audit shall be conducted by personnel approved by the QA Manager to verify the as built configuration matches the design documentation prior to use of each part in production. During this process each product definition document shall also be examined for proper format (compliance with ANSI Y14 series standards), completeness, currency of material references, accuracy of piece part identification, and adequacy of manufacturing instructions and any other information critical to acquire a like part.

Government Audit to Verify Product Baseline After completion of acceptance testing and any required design modifications, but prior to formal acceptance, the final product baseline shall be verified via Physical Configuration Audit (PCA) by the Government by reviewing a representative number of drawings, associated technical manuals, Logistics Management Information and manufacturing instructions to determine their accuracy in accordance with the final product configuration design.

REF: CDRL C006 (DI-CMAN-81022D) Configuration Audit and Summary Report

SOFTWARE CONFIGURATION MANAGEMENT

The Contractor shall establish and document a software CM process.

RISK MANAGEMENT

The Contractor shall develop, implement, and maintain a risk management process that at a minimum includes risk identification, analysis, mitigation planning, mitigation plan implementation, and tracking. The Contractor’s risk management process shall be documented in the Contractors Risk Management Plan and shall measure future uncertainties in achieving program goals within defined cost, schedule, and performance constraints. The Contractor shall execute Risk Management in accordance with (IAW) the Risk Management Plan. The Contractor shall

a. identify and document moderate and high-risk items for each risk assessment area.

b. identify and implement risk handling approaches and track over time each moderate and high-risk item.

c. develop risk tree with risk triggers and mitigation paths for each high risk item.

d. document risk issues that have been successfully resolved and schedule each open item into the program IMS.

The Contractor shall develop risk mitigation plans to identify the recommended critical path for contract completion and the appropriate risk handling approach to lower the level of uncertainty identified.

REF: CDRL B001 (DI-MGMT-81808) Contractors Risk Management Plan

MANAGEMENT AND TECHNICAL REVIEWS

The Contractor shall conduct an initial program review within 90 days after contract award, and an additional program review three months prior to the base contract and each option year end dates at a location to be determined by the Government. The Contractor shall provide visibility on significant aspects of the contract execution plans, progress, performance, and status of major subcontractors. The Contractor shall document, coordinate resolution and track action items until closure. The Contractor shall generate and distribute minutes of all meetings/ reviews.

POST AWARD CONFERENCE

The Contractor shall conduct a post award conference within 30 days after contract award. The Contractor shall present an IMS showing all critical milestones and supporting events leading to these milestones. The conference shall introduce key participants with emphasis on demonstrating functional availability of required facilities, key program personnel, understanding of the scope of work, agreement on metrics that will be used as program management indicators, identification of key partners, and other issues relevant to ensuring early success on the program.

PROGRAM MANAGEMENT REVIEWS (PMRs) The Contractor shall conduct PMRs at its facility on a monthly basis. Conference support provided shall include facilities, office equipment and clerical personnel. An agenda shall be coordinated with Government personnel two weeks prior to hosting the reviews. The PMRs shall provide a formal forum to assess the aggregate programmatic status, specific issues and on-going actions. The content of the PMR shall be mutually agreed upon by the Government and the Contractor.

TECHNICAL REVIEWS

The Contractor shall conduct and participate in technical reviews for the purpose of planning and assessing technical progress. Trade-off analysis and verification results should be available during technical reviews in order to substantiate technical decisions.

TECHNICAL INTERCHANGE MEETINGS (TIMs) The Contractor shall conduct and participate in TIMs to be held at Contractor or Government designated facilities. The meetings shall be co-chaired by a Government and Contractor representative. The Contractor shall be prepared to explain the reasoning, assumptions, and methodologies used in arriving at particular conclusions, recommendations, or alternatives in the accomplishment of the tasks required by the contract. The Contractor shall develop and prepare all appropriate data required to aid in the evaluation of alternative proposed. The Contractor shall ensure all required personnel and resources are available. The Contractor shall prepare the meeting agenda and document the meeting results. Except where noted, meetings shall be considered fulfilled when all of the following items are completed:

a. All action items requiring Contractor response have been documented and is accessible through user-friendly electronic remote access.

CYBERSECURITY ACCREDITATION

The Contractor shall produce all required components of the Certification and Accreditation (C&A) package relevant to the IEWTPT system (including related artifacts that may be fielded location specific. The Contractor shall comply with the cybersecurity process in accordance with DCID 6/3, ICD 503, DoDI 8500.01 & DoDI 8500.02 (DIACAP) and/ or DoDI 8510.01 (RMF). The Contractor shall ensure the security requirements and procedures are met in accordance with all required DoD and Army regulations per the Mission Assurance Category (MAC III) and Confidentially Level (CL) agreed upon for the network(s).

REF: CDRL A007 (DI-MISC-80508B) Technical Report – Study/Services (Security Accreditation Package)

ANTITERRORISM (AT)/OPERATIONS SECURITY (OPSEC)

AT LEVEL 1 TRAINING

All Prime Contractor and subcontractor employees requiring access to Army installations, facilities, and/ or controlled access areas shall complete AT Level I awareness training in accordance with AR 381-12 within 60 calendar days of contract start date or date of employment, whichever comes first, and annually thereafter for the life of the contract. The Contractor shall submit certificates of completion for each affected Contractor employee and subcontractor employee to the COR, or the Contracting Officer if a COR is not assigned, within thirty (30) calendar days after completion of training AT level I awareness training is available at the following website: https://atlevel1.dtic.mil/at.

ACCESS AND GENERAL PROTECTION POLICY AND PROCEDURES FOR CONTRACTOR REQUIREING COMMON ACCESS CARD (CAC) Contractor and all associated sub-contractors 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 at any individual facility or installation change, the Government may require changes in Contractor security matters or processes.

Before CAC issuance, the Contractor employee requires, at a minimum, a favorably adjudicated National Agency Check with Inquiries (NACI) or an equivalent or higher investigation in accordance with Army Directive 2014-05. The Contractor employee will be issued a CAC only if duties involve one of the following: (1) Both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely; (2) Remote access, via logon, to a DoD network using DoD-approved remote access procedures; or (3) 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 six (6) months or more. 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.

AT AWARENESS TRAINING FOR US BASED CONTRACTOR PERSONNEL TRAVELING OVERSEAS

All US-based Prime Contractor employees and associated sub-contractor employees must take Government-provided Area Of Responsibility (AOR) specific AT awareness training as directed by AR 525-13. Specific AOR training content is directed by the combatant commander with the unit Anti-Terrorism Officer (ATO) being the local point of contact.

iWATCH TRAINING The Prime Contractor and all associated sub-contractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity ATO). This locally-developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within 60 calendar days of contract award, employment, or assignment to the contract, whichever comes first, with the results reported to the COR not later than 30 calendar days after completion of training.

ARMY TRAINING CERTIFICATION TRACKING SYSTEM (ATCTS) REGISTRATION FOR CONTRACTOR EMPLOYEES WHO REQUIRE ACCESS TO GOVERNMENT INFORMATION SYSTEMS (IS) All Contractor employees with access to a Government information system must be registered in the ATCTS at commencement of services, and must successfully complete the DOD cybersecurity Awareness within 10 calendar days of contract award prior to access to the IS and then annually thereafter.

OPSEC PROGRAM

The Contractor shall develop an OPSEC Standing Operating Procedure (SOP)/ Plan within ninety (90) calendar days of contract award, to be reviewed and approved by the responsible Government OPSEC officer. This plan will include at a minimum, a process to identify critical information, where it is located, who is responsible for it, how to protect it and why it needs to be protected. The Contractor shall implement OPSEC measures as ordered by the Commander. In addition, the Contractor shall have an identified, certified Level II OPSEC responsible coordinator per AR 530-1, Operations Security.

REQUIREMENT FOR OPSEC TRAINING

Per AR 530-1, new Contractor employees must complete Level I OPSEC training within thirty (30) calendar days of contract award, employment, or assignment to this contract, whichever comes first, and annually thereafter. Confirmation of training shall be provided to the COR not later than 30 calendar days following completion of training.

CYBERSECURITY/INFORMATION TECHNOLOGY (IT) TRAINING

All Contractor employees and associated sub-contractor employees must complete the DoD Cybersecurity Awareness Training before issuance of network access and annually thereafter. Confirmation of training shall be provided to the COR not later than 30 calendar days following completion of training All Contractor employees working cybersecurity /IT functions must comply with DoD and Army training requirements in DoD 8570.01, DoD 8570.01-M and AR 25-2 within six (6) months of employment.

IA/IT CERTIFICATION

Per DoD 8570.01-M, DFARS 252.239.7001 and AR 25-2, the Contractor employees supporting cybersecurity/ IT functions shall be appropriately certified upon contract award. Confirmation certification shall be provided to the COR within 30 calendar days of certification.

PERFORMANCE OR DELIVERY IN A FOREIGN COUNTRY

The Contractor shall comply with DFARS clause 252.225-7043, Antiterrorism/Force Protection for Defense Contractors Outside the US.

HANDLING OR ACCESS TO CLASSIFIED INFORMATION

The Contractor shall comply with FAR 52.204-2, Security Requirements. This clause involves access to information classified “Confidential,” “Secret,” or “Top Secret”. The Contractor shall comply with The Security Agreement (DD Form 441), the National Industrial Security Program Operating Manual (DoD 5220.22-M), and any revisions to either.

THREAT AWARENESS REPORTING PROGRAM

For all Contractors with security clearances, per AR 381-12 Threat Awareness and Reporting Program (TARP), all Contractor employees must receive annual TARP training by a counterintelligence agent or other trainer as specified in paragraph 2-4b of the AR within (180) calendar days after contract award. Confirmation of training completion shall be provided to the COR within 30 calendar days of completion of training.

SYSTEMS ENGINEERING

The Contractor shall establish and follow a comprehensive system engineering process that will transform all system requirements into a set of lower level requirements that define the system’s performance. The system engineering effort shall integrate all elements of a multifunctional engineering effort to develop a system that provides Military Intelligence (MI) training for US Army MI personnel to sustain individual, crew, and/or collective MI skills including collection, analysis, and fusion for MI Series Military Occupational Specialties (MOS) including All Source, GEOINT, SIGINT, HUMINT, OSINT, and emerging tactical CYBER Ops in Unified Land Operations (ULO), Counter Insurgency (COIN), Hybrid, and Decisive Action Training Environments (DATE) while operating standalone, federated, or in distributed mode across multiple security enclaves in support of Army, Joint and/or multi-agency environment. The Contractor shall ensure the properly sequenced, timely integration of all engineering specialties as required. As part of the systems engineering effort, the Contractor shall develop, update and maintain a Systems Engineering Management Plan (SEMP). The Contractor shall use the SEMP to define, identify and exercise control of the overall technical management process.

The Contractor shall ensure the system architecture supports system interoperability and provide support for multiple simulation interfaces. The Contractor shall identify, develop and integrate new technologies.

The Contractor shall translate the operational needs, requirements, performance objectives, interfaces and other design constraints, including cost, into preliminary verifiable functional requirements and objectives and conduct cost-benefit trade-offs to support refinement of functional requirements. The Contractor shall complete a system analysis balancing performance, cost, schedule, and risk, to meet systems requirements. As part of the system analysis and component selection process, cybersecurity shall be considered as a key requirement for all systems used to enter, process, store, display, or transmit information.

The Contractor shall conduct knowledge acquisition, requirements analysis, technical reviews, and other activities as required to ensure efficient system development and production. The Contractor shall follow DoD compliant systems engineering processes for representing requirements, and conducting design, code, and testing activities. Traceability shall be maintained between requirements and design, through developmental testing, integration events, operational testing, and validation events. The Contractor shall establish a system baseline and conduct appropriate technical reviews to manage that baseline.

SYSTEM DESIGN

The Contractor shall derive, decompose, and develop lower level requirements from top level system requirements. The Contractor shall perform trade off studies in support of system design concept evaluations. The Contractor shall use a design approach that maximizes the use of modular components, consider the use of commercial standards where feasible, and leverages the use of emerging technologies where appropriate. The contractor shall maximize the use of non-proprietary design features and incorporate open systems attributes into the design for selection of system interfaces, products, and tools. The contractor shall optimize IEWTPT design and operational features for ease of integration and operation with other training systems when configured in an Integrated Training Environment (ITE), as a member of a Family of Systems (FoS), System Of Systems (SoS), or Federation, or when integrated in full or in part as a component of a larger mission command configuration, and/ or ground or aerial operations intelligence training system.

REF: CDRL A008 (DI-IPSC-81432A) System/Subsystem Design Description (SSDD)

SOFTWARE ENGINEERING

The Contractor shall develop the system software and firmware following disciplined, enforceable, and auditable standards and internally documented organizational software development practices. The Contractor shall go through the Computer Hardware, Enterprise Software and Solutions (CHESS) Information Technology (IT) system for all non-developmental software. Any software not procured through the CHESS process must have an approved waiver. The Contractor shall maintain a Controlled Development Environment for all Software development related activities. The Contractor shall develop software requirements and shall define and record the software requirements to be met by each software item, the methods to be used to ensure that each requirement has been met, and the traceability between the software item requirements and system requirements. The Contractor shall define and record the software architecture of the system (identifying the software components of the system, their interfaces, and relationships amongst them) and the traceability between the system components, system requirements, and software requirements. Traceability shall be maintained between levels of requirements, between requirements and design, between design and the software that implements it, between requirements and qualification test information, and as a measured of computer hardware resource utilization. The Contractor shall conduct analysis to determine if existing commercially available, open source software products are capable of meeting any required operational capabilities, and shall document the results of the analysis and any recommendations that might result from the analysis.

The contractor shall provide Software Resources Data Reports (SRDR) that adequately reflect the development status, resource expenditures, and estimated characteristics of a software product and its development process. These reports shall describe the methods and rules used to perform the data measurement or estimation and shall include an associated Data Dictionary. These data shall be of sufficient fidelity to allow analysis of estimated and/ or actual software product sizes, schedules, and corresponding spent effort.

REF: CDRL A006 (DI-IPSC-81430A) Operational Concept Description (OCD)

HARDWARE ENGINEERING

The Contractor shall procure the necessary hardware and software, to include licenses, for IEWTPT products development, integration, test, fielding and exercise technical support activities. The Contractor shall communicate and coordinate any projected material purchasing activities within the appropriate IPT(s). All computer related hardware or hardware related services shall be purchased through the CHESS schedules in performing this contract. Any hardware not procured through the CHESS process must have an approved waiver.

A complete list of CHESS contracts and the on-line waiver process can be found at https://chess.army.mil.

The Contractor shall deliver all required hardware, software, supplies and/ or materiel to designated sites. The Contractor shall assist site personnel with the inventory and transfer of property to the assigned site Property Book Officer (PBO).

The Contractor shall conduct analyses of the impact of software baseline performance and/ or hardware footprint changes resulting from functional modifications and/ or for optimizing system performance. The Contractor shall recommend hardware improvements to realize operational efficiencies.

PRODUCT DEFINITION DATA (PDD)

During the systems engineering and design, and in accordance with MIL-STD-31000C, The Contractor shall develop, produce, and maintain product definition data (PDD) that accurately depicts the final product. The PDD is the technical description of items adequate for informing an acquisition strategy, supporting production, engineering, cybersecurity and life-cycle needs. The PDD shall disclose complete design, cybersecurity, logistics, and manufacturing requirements, and the means of measuring compliance with the requirements. Piece part information (drawings, computer aided design files and meta data) and associated lists shall include the necessary design, engineering, cybersecurity, manufacturing, and quality assurance requirements information necessary to enable the procurement or manufacture of an interchangeable item that duplicates the performance characteristics of the original product, without additional design engineering effort or recourse to the original design activity. The Contractor shall produce and maintain documentation for all electrical assemblies and subassemblies in such a manner to ensure their functional integration without recourse to special test equipment (STE) or installation of the assemblies or subassemblies into a next higher assembly. Utilizing the established logistic repair procedures, The Contractor shall identify the higher level components and assemblies to be repetitively procured as spare components and assemblies which may be procured independently. For each higher level component or assembly, the Contractor shall determine and document the functional requirements for the item, the environment in which it must operate, interface and interchangeability characteristics, and criteria for verifying logistics support criteria. The Contractor shall define quantitative and qualitative supportability design guidelines. The Contractor shall conduct trade studies, evaluate design and support alternatives, and establish system supportability preliminary design configurations consistent with system readiness and availability and life cycle cost goals. The Contractor shall coordinate fielding plans for the system with life cycle support activities to verify that the maintenance actions and support structure are aligned with any proposed maintenance concept.

REF: CDRL C00B (DI-SESS-81003E) Commercial Drawings and Associated List REF: CDRL C00C (DI-SESS-81000E) Product Drawings Models and Associated List

SOFTWARE REQUIREMENTS DEVELOPMENT AND REVIEW

The Contractor shall develop software requirements in accordance with industry software development best practices and standards.

The Contractor is encouraged to suggest revisions to Government requirements where such revisions would result in cost or schedule reduction or performance improvements.

The Contractor shall define and document the operational concept for the system, and define and document the of the system (identifying the components of the system, their interfaces, including logical and physical views) and the traceability between the software requirements, system components and system requirements.

Based upon analysis of system requirements, system design, and other considerations, the Contractor shall derive, define and document the software requirements to be met by each software item, the methods to be used to ensure that each requirement has been met, and the traceability between the software item requirements and system requirements. The Contractor shall evaluate the cybersecurity requirements to assess any impacts on defined software requirements and provide potential solutions as applicable. The Contractor shall use modeling and simulation as appropriate for architecture analysis and validation.

REF: CDRL A001 (DI-IPSC-81433A) Software Requirements Specification (SRS)

SOFTWARE DESIGN AND IMPLEMENTATION

The Contractor shall design software, develop code, perform software testing, and integrate software components (with each other and with hardware components) to meet system requirements. Products that perform information assurance functions are considered cybersecurity or cybersecurity-enabled IT products and shall be selected from the DoD Unified Capabilities Approved Product List and configured in accordance with DoD-approved security configuration guidelines.