SOW_VCTS-ARCENT-Kuwait_1Oct2019.pdf

Statement of Work for

Virtual Clearance Training Suite (VCTS) Army Central (ARCENT) – Kuwait

Prepared by U.S. Army PEO Simulation, Training and Instrumentation (PEO STRI)

12350 Research Parkway Orlando, FL 32826-3276

Engineering

Prepared By: ____________________ Concurrence: ____________________

Kien Le Jeff Meister Lead Systems Engineer, VCTS Chief Engineer, PM VTS Date: _________ Date: __________

Acquisition Logistics

Prepared By: ____________________ Concurrence: ____________________

Iris Lloyd Matthew Brothers, Jr Lead Acquisition Logistician, VCTS Product Support Manager/ PM TRADE Date: __________ Date: __________

Program Management

Submitted By: ___________________ Approved By: ____________________

David J. Meyers LTC Edgar O. Santana Assistant Product Manager Product Manager Date: __________ Virtual Training Systems (VTS) Date: _________

DISTRIBUTION STATEMENT A: APPROVED FOR PUBLIC RELEASE;

DISTRIBUTION IS UNLIMITED.

Change History

Revision Date Section Description

Initial Version 10/01/2019 ALL ARCENT – Kuwait – Modified from VCTS – Phase II Baseline

SOW

Contents

1 SCOPE

1.1 BACKGROUND

2 APPLICABLE DOCUMENTS

2.1 DEPARTMENT OF DEFENSE DOCUMENTS

2.2 OTHER GOVERNMENT DOCUMENTS

3 REQUIREMENTS

3.1 PROGRAM MANAGEMENT

3.1.1 Integrated Master Schedule (IMS)

3.1.2 Configuration Management (CM)

3.1.3 Risk Management

3.1.4 Parts Management Plan

3.1.5 Program Management Reviews

3.1.6 Integrated Digital Environment (IDE)

3.1.7 Government Purpose Rights (GPR)

3.1.8 Visitor Support

3.1.9 Operational Security

3.1.10 Antiterrorism Training (AT)

3.1.11 Common Access Cards (CAC)

3.2 SYSTEMS ENGINEERING

3.2.1 Systems Design

3.2.2 Hardware Engineering

3.2.3 Cybersecurity

3.2.4 Specialty Engineering

3.2.5 Integration of Third Party Products

3.3 TECHNICAL INTERCHANGE MEETINGS (TIMS)

3.4 PRODUCT DEFINITION DATA (PDD)

3.4.1 PDD Updates

3.5 INTEGRATED LOGISTICS AND SUPPORTABILITY

3.5.1 Logistics Support Analysis

3.5.2 Supportability Analysis and Logistics Product Data (LPD)

3.5.3 Maintenance Concept

3.6 TECHNICAL PUBLICATIONS

3.6.1 Operator User Manual (OUM)

3.6.2 System Maintenance Manual (SMM)

3.6.3 Commercial Off-the-Shelf (COTS) Manuals and Associated Lists

3.6.4 Publications In Process Review's (IPR’s)

3.6.5 Technical Manual Validation

3.6.6 Technical Manual Verification

3.7 ITEM UNIQUE IDENTIFICATION (IUID)

3.8 TRAINING COURSES

3.8.1 New Equipment Training (NET) - Maintenance

3.8.2 Train the Trainer (TTT) Training

3.8.3 Crew Course Training

3.8.4 Language Requirement

3.8.5 Class Size

3.8.6 Location of Training

3.8.7 Training Facility and Equipment

3.8.8 Course Completion Criteria

3.8.9 Certificate of Completion

3.9 INTEGRATED TESTING

3.9.1 Contractor Verification Test (CVT)

3.9.2 Test Readiness Review (TRR)

3.9.3 In Plant Acceptance Test (IPAT)

3.9.4 On Site Acceptance Test (OSAT)

3.10 SITE SURVEY

3.11 INSTALLATION SUPPORT

3.11.1 Installation Tools and Test Equipment

3.11.2 Packaging, Handling, Storage, and Transportation (PHST)

3.11.3 Facility and Equipment Repairs

3.11.4 Safety

1 SCOPE

This Statement of Work (SOW) defines the Contractor effort required for designing, developing, producing, integrating, testing, managing, documenting, delivering and installing the Virtual Clearance Training Suite (VCTS) ARCENT in accordance with the System Requirements Document (SRD) PRF-PT-723.

1.1 Background

In Iraq and Afghanistan, a persistent insurgent force is planting a wide array of improvised explosive devices (IEDs) in and near roads and detonating them by both simple and sophisticated means. U.S. Forces have responded with an equally wide array of large and small technical devices, purpose-built mine-protected detection and clearing vehicles, and ever-evolving tactics, techniques, and procedures (TTPs). These devices include the Buffalo

- Mine Protected Clearance Vehicle (MPCV), Husky - Tractor Wheeled High Speed (TWHS), Medium Mine Protected Vehicle Type I and II (MMPV I and II), and Man Transportable Robotic System (MTRS). The wide array of Route Clearance devices responding to this urgent need for Route Clearance has created both an urgent and long term need for training Route Clearance operations. Route Clearance operations involve at least three skill sets:

a. Warfighters need to understand the enemy’s basic IED placement techniques, know IED indicators, and be able to identify IED components.

b. Warfighters need to be proficient at mounted and dismounted movement in an IED environment.

c. Warfighters need to know the capabilities and weaknesses of their route clearance equipment.

2 APPLICABLE DOCUMENTS

The following documents are applicable to this SOW to the extent specified herein. In the event of a conflict between documents referenced herein and the contents of this SOW, the contents of the SOW shall be the governing requirement.

2.1 Department of Defense Documents

MIL-STD-130 Identification Marking of U.S. Military Property

MIL-STD-31000A Technical Data Packages

2.2 Other Government Documents

PRF-PT-723 System Requirements Document (SRD) for the Virtual Clearance Training Suite (VCTS) ARCENT.

CNSSI 1253 Committee on National Security Systems Instruction (CNSSI)

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

AR 525-13 Antiterrorism

FAR clause 52.204-9 Personal Identity Verification of Contractor Personnel

Army Directive 2014-05 Policy and Implementation Procedures for CAC Credentialing and

Installation Access for Uncleared Contractors

AR 190-13 Army Physical Security Program

29CFR1910.1200 Occupational Safety and Health Standards Toxic and hazardous

Substances

EM-385-1-1 Department of Army Manuals, US Army Corp of Engineers Safety and Health Requirements Manual 2008 (Manual is downloadable from www.usace.army.mil/CESO/Pages/EM385-1-1.aspx).

29 CFR 1910 Code of Federal Regulations (CFR), 29 CFR 1910 Occupational

Safety and Health Standards (OSHA standards are downloadable from http://www.osha.gov)

NFPA 70 National Fire Protection Association (NFPA 70 National Electrical

Code, 2011 Edition (Copies of this document are available from http://www.nfpa.org/Catalog/ or National Fire Protection Association, 11 Tracy Drive, Avon, MA 02322)

OSHA 1910 Occupational Safety and Health Administration (OSHA)

Regulations OSHA 1910, Subpart S Electrical (Copies of the above regulations are available from http://www.osha.gov)

3 REQUIREMENTS

3.1 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 track program progress utilizing metrics. The Contractor shall define and monitor metrics and technical performance measures (TPMs) to evaluate each critical technical and management process and the conformance of evolving products with contract and cost requirements and objectives. The Contractor shall provide a monthly report identifying progress, issues and status of the program.

The Contractor shall identify problem areas and corrective actions required to eliminate or reduce schedule impacts. The Contractor shall deliver monthly progress reports containing at a minimum the following:

http://www.usace.army.mil/CESO/Pages/EM385-1-1.aspx http://www.osha.gov/ http://www.nfpa.org/Catalog/ http://www.osha.gov/

a. Problems and solutions.

b. Time-lines and schedules.

c. Plan of next month activities.

d. Development and fabrication progress.

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

3.1.1 Integrated Master Schedule (IMS)

The Contractor shall develop, implement, manage and update the contract Integrated Master Schedule (IMS). The IMS shall be presented at all program reviews and technical reviews, and shall contain all critical events and exit criteria, accomplishments, predecessors and successors events, and their dependencies. The IMS shall address and identify total program activities including activities performed by major subcontractors. The activities and event times shall be updated to reflect accomplished activities and any changes. The Contractor shall conduct critical path analysis of the tasks and identify problem areas and corrective actions required to eliminate or reduce schedule impacts.

DI-MGMT-81861A Integrated Program Management Report

3.1.2 Configuration Management (CM)

The Contractor shall use industry standard best practices, processes and tools to establish and maintain consistency between system requirements, system configuration information, and all other relevant information about the system. The CM process shall ensure the system conforms to the requirements; all requirements and components (both hardware and software) are identified and documented in sufficient detail to support the system life cycle; ensure component interchangeability; ensure accurate system information and facilitate system maintenance. The Contractor shall define the performance, functional, and physical attributes in configuration documentation. As the configuration information becomes more detailed and definitive throughout the life cycle, the Contractor shall define configuration baselines. The Contractor shall archive the defined attributes for each baseline in a CM integrated database. Both the system baseline and its associated information shall be verified for consistency. The Contractor shall identify and evaluate the impact of all proposed changes through the configuration change management process, including verification that the system baseline and all associated component information have been updated and continue to be consistent.

3.1.2.1 Configuration Management Planning and Management

The Contractor shall establish processes and tools to establish and maintain consistency between system requirements, system configuration information, and all relevant information about the system. The Contractor shall:

a. Plan implementation of the CM functions for the context and environment in which they are to be performed and then manage in accordance with the planning.

b. Determine the specific CM value-adding functions and levels of emphasis.

c. Document how the Contractor organization will implement CM functions to provide the consistency between the system’s attributes, system definition information and the system’s configuration information, throughout the applicable phases of the life cycle.

d. Identify resources required to implement the CM functions and ensure they are applied throughout the systems life cycle.

e. Continually assess the effectiveness of the CM plan implementation and performance of the configuration management functions with performance measurements.

f. Flow down responsibility for CM performance to subcontractors.

g. Ensure all data products transmitted to the Government are usable.

h. Ensure that the software and hardware configuration management plan is incorporated into a single or separate configuration management plan.

3.1.2.2 Configuration Identification

The Contractor shall create unique identifiers for each configuration item (CI) at the system, subsystem and component level and for both computer software configuration items (CSCI) and hardware configuration items (HWCI) at each level, i.e. system, subsystem and component. The Contractor shall be able to show the traceability between all levels of CIs, CSCIs and HWCIs.

All descriptions and documentation for each CI, CSCI and HWCI shall include the follow data, as applicable, to be used as the basis for configuration management:

a. Selected system/software/hardware attributes

b. System/software/hardware information and

c. Lower level components.

The Contractor shall:

a. Define the functional, performance, interface and physical attributes of the system, software and hardware components.

b. Determine system composition using its product definition information.

c. Assign unique identifiers to configuration items so that they can be distinguished from other items, one configuration of the system can be distinguished from another, the source of a component can be determined, and the correct system definition information can be retrieved.

d. Assign unique unit identifiers to selected individual components of the system.

e. Update component identifiers when a system is modified reflecting the new configuration without altering the system identifier and model identifier.

f. Uniquely identify information so that it can be correctly associated with the applicable system configuration.

g. Apply information identification rules to maintain representation and version relationships.

h. Maintain relationships between information, information requirements, and the related system to ensure accurate information retrieval.

i. Establish complete, valid, and suitable for use agreed-to descriptions of system attributes and components at a point in time, and provide a known configuration to which changes can be addressed.

j. Identify interfaces and establish mutually agreed-to control of common attributes for system or component boundaries that interface to or within the system.

3.1.2.3 Configuration Change Management & Configuration Control Board (CCB) The Contractor shall establish a systematic and measurable configuration change management process for managing product configuration changes and variances. Once the system design has been approved by the Government and the production baseline has been established, the Contractor shall effect changes to the baseline requirements only after the proposed change has been approved using the change process and approval by the Government. The Contractor shall:

a. Document and uniquely identify each change.

b. Classify requested changes to aid in determining the levels of review and approval.

c. Clearly and completely document each change request.

d. Consider the technical, support, schedule, and cost impacts of a requested change before making a judgment as to whether the change should be approved for implementation and incorporation in the system and its documentation.

e. Determine potential effects of a change and coordinate impacts with the impacted areas of responsibility.

f. Determine the effectivity for each change, identify which units of the system are to be changed, the point of production break-in, and which units will be included in a retrofit.

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

h. Document variances, when authorized by the appropriate level of authority.

The Contractor shall establish and maintain a single, unified configuration control board responsible for configuration control of all software and hardware configuration items and related products. The configuration control board will also be responsible for management of Government Off-The-Shelf (GOTS) and Commercial Off-The-Shelf (COTS) (including open source) configuration items including product and version identification. The Contractor shall obtain approval at the CCB prior to committing to use of any version of any COTS product. All GOTS and COTS software products shall be independently tracked as separate CSCIs. The Contractor shall ensure that all COTS products included in the system deliverable configuration are commercially supported.

3.1.2.4 Configuration Validation and Verification

The Contractor shall validate system configuration information to ensure that requirement attributes are met and accurately documented. The configuration validation shall be performed by comparing the hardware, at the lowest repairable unit (LRU) level, to the drawings of those items.

The Contractor shall provide necessary personnel to participate in the configuration verification with the Government. The Contractor shall be responsible for identifying opportune timeframes to the Government to witness the Contractor’s in-process validations of the documentation and hardware components. At different intervals throughout the build process the Contractor shall make the hardware available to the Government for their own reviews and verifications of all technical documentation, hardware and software. The Contractor shall be responsible for identifying recommended viewing times during the development process that allow components to be easily viewed prior to assembly. The Contractor shall ensure that the Integrated Digital Environment (IDE) contains the latest CM versions of all technical documentation. The Government will utilize the IDE technical documentation to perform their verifications by reviewing a representative number of drawings, associated technical manuals, software versions, logistics management information and manufacturing instructions to confirm the accuracy of the final product configuration design. At a minimum, the Contractor shall ensure the system configuration verification is scheduled for completion NLT 14 days prior to In Plant Acceptance Test (IPAT) and included in the Integrated Master Schedule (IMS). The Contractor shall:

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

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

c. Prepare and deliver to the Government team a completed configuration verification report.

3.1.2.5 Configuration Status Accounting

The Contractor shall provide access to accurate, timely information about the system and its documentation through the integrated digital environment. The Contractor shall correlate, store, maintain, and provide readily available views and information of system configuration information including pending, current, and historical data. The Contractor shall:

a. Systematically record, safeguard, validate, and disseminate system information.

b. Establish methods, processes, and procedures to provide controlled access to system information.

c. Capture configuration information as it evolves

3.1.2.6 Engineering Change Proposal (ECP) and Review

The Contractor shall document and the IPT shall review all changes to established baselines and all changes to the requirements (other than the functional baseline), including changes to the statement of work, contract data requirements list (CDRL), contract schedule, and general provisions of the contract.

In coordination with the Government, the Contractor shall hold a requirement review on all proposed routine changes prior to the submittal of the ECP to clarify requirements, format, and content. Depending upon the criticality of the proposed changes, this review may take the form of a teleconference, a video-teleconference, a formal meeting at a government facility or a formal meeting at the contractor facility. All appropriate parties shall be in attendance in order to conduct a thorough, effective review. Minutes shall be a historical record to allay any miscommunications.

DI-SESS-80639D Engineering Change Proposal (ECP)

3.1.2.7 Request for Variance (RFV)

After establishment of production baseline, the Contractor shall document the rationale and obtain the Government’s written approval before deviating from any Government approved baseline.

DI-SESS-80640D Request for Variance

3.1.3 Risk Management

The Contractor shall prepare, implement, and maintain a cost, technical and schedule risk management process. This shall include risk detection and identification, assignment of risk categories, action triggers, corrective action, tracking of compliance, reporting of status and planning for risk abatement. The Contractor shall:

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

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

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

d. Develop mitigation plans to identify the recommended critical path for contract completion and the appropriate risk handling approach to lower the level of uncertainty identified.

3.1.4 Parts Management Plan

The Contractor shall maintain a training system Obsolescence Management Program. The Contractor shall develop a plan for managing loss/impending loss of manufacturers and/or suppliers for training system spare/repairable items covered in this contract. The Obsolescence Management Plan shall minimize impact to contract performance metrics and/or additional costs being incurred by the Government due to obsolescence.

3.1.5 Program Management Reviews

The Contractor shall conduct program management reviews at the request of the Government with a minimum of one every quarter. The location of the review shall be mutually agreed upon with the Government. Program management reviews shall provide an accurate program overview and a detailed discussion of pre-selected topics. Status and information presented during the review shall reflect currency since the previous review.

3.1.5.1 Start of Work Meeting

The Contractor shall conduct a Start of Work Meeting at the Contractor’s facility within 20 working days after contract award. The purpose of the meeting shall be to establish the framework of the Contractor and Government interaction during the performance period of the contract. The Contractor shall place emphasis on the operating procedures, methodologies and processes to be used in the execution of the contract. The meeting shall include the Contractor’s key team members identified in the proposal with emphasis on top level management of the program, agreement on metrics that will be used as management indicators during the program and partnering approach to implement. The Contractor shall present the program Integrated Master Schedule, IPT structure, management concept, organizational structure, and the interfaces with the Government that are employed to perform the VCTS mission. The Contractor shall document action items, due dates and coordinate resolution and track action items until closure.

Action item closure shall require Contractor and Government approval.

DI-ADMN-81505 Report, Record of Meeting/Minutes

3.1.5.2 Program Management Reviews (PMR)

The Contractor shall conduct program management reviews on a quarterly basis in accordance with the IMS. The first PMR shall be no more than 90 calendar days after the Start of Work Meeting. The location of the PMRs shall be mutually agreed upon by the Procuring Contracting Officer (PCO) and the Contractor. The program management review shall provide a program overview and shall include as a minimum:

a. Hardware and software design status

b. Risk and problem identification

c. Subcontract management/progress

d. Data collection and modeling

e. GFE planning and status

f. Logistics planning

g. Test planning

h. Provisioning for training and technical publications status

i. Schedule status

j. Pre-selected topics of interest

k. I/A Security

l. Human Factors Engineering

Status and information at the review shall reflect currency since the previous review. Other program reviews such as technical reviews, technical manual reviews, etc. shall be combined into the PMR when possible. The Contractor shall also be responsible for generating minutes of the meetings and provide them to the Government for approval. The Contractor shall document action items, due dates, coordinate resolution and tracking of action items until closure. Action item closure shall require Contractor and Government approval.

DI-ADMN-81505 Report, Record of Meeting/Minutes

3.1.5.3 Integrated Product and Process Management (IPPM)

The Contractor shall establish and maintain a management technique that simultaneously integrates all essential acquisition activities through the use of multidisciplinary teams to optimize design, manufacturing, and supportability processes. The Contractor shall utilize systems engineering tools and overlay a management concept that encourages the use of IPTs.

The Contractor’s IPPM shall interact with the government in its role as a customer. The contractor’s IPPM shall establish performance requirements, monitor and manage total program progress, and evaluate product quality. The Contractor shall establish an IPT structure to address major areas of system development (e.g., systems engineering, hardware design, software design, integrated logistics support testing). The Contractor shall establish IPT charters and host regularly schedule IPT meetings or teleconferences. The IPT meetings/teleconferences shall be used to address systems development status of activities, questions and issues in a timely manner between management reviews. The Contractor shall document action items, due dates and coordinate resolution and track action items until closure. Action item closure shall require Contractor and Government approval.

DI-ADMN-81505 Report, Record of Meeting/Minutes

3.1.6 Integrated Digital Environment (IDE)

The Contractor shall establish, maintain and manage an interactive, online, protected, and access controlled IDE, such that the IPT members can contribute their ideas, comments and suggestions, exchange program information and collaborate in a distributed environment. The Contractor shall include software applications and database services for the generation, integration, storage, indexing, distribution and simultaneous on-line sharing of digital data among all authorized Government and Contractor team members. The IDE shall allow sharing and delivery of technical data products with associated Contractors, subcontractors and Government organizations. The Contractor shall maximize the use and capabilities of existing open source software products. Specifically, integrated automated databases are required which shall allow technical data sharing at the data base level, rather than at the physical file level, with multiple formats of the same data from a common, configuration-controlled source available to different users. The IDE shall provide program personnel complete visibility into the system at every stage of development, regardless of data location. The Contractor shall ensure that everyone associated with this project has access to information they need to properly perform their duties.

3.1.7 Government Purpose Rights (GPR)

The Government will acquire no less than Government Purpose Rights in any software or technical data developed under this contract with Government funding or partial Government funding. The Government will retain Government Purpose Rights for the life of this contract.

Upon expiration of the contract, the Government will have unlimited rights in any applicable technical data. The Contractor shall ensure that sufficient rights are procured with the addition of new software or hardware proposed for the VCTS. The rights shall be procured such that the Government can maintain and modify the system using Government personnel and third party contractors. Government approval is required for other than Government purpose rights.

3.1.8 Visitor Support

The Contractor shall host Very Important Person (VIP) visits and arrange for and provide demonstrations of system performance, program progress, and other system characteristics when notified by the Government as required.

3.1.9 Operational Security

The Contractor’s employees shall take the OPSEC training, as required, in the performance of tasks bounded by OPSEC requirements. Certifications of completion shall be attached to the Contractor’s Status Report. The Contractor shall identify a list of required personnel and their required training to be reviewed and approved by the Government. A status of this list and the required training shall be included in the Contractor’s Status Report.

3.1.10 Antiterrorism Training (AT)

All contractor employees, to include subcontractor employees, requiring access to Army installations, facilities and controlled access areas shall complete AT Level I awareness training prior to commencing work at the installation. The Contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee to the Contracting Officer Representative. AT level I awareness training is available at the following website:

http://jko.jten.mil. The 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. The 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.

3.1.10.1 AT Awareness for Overseas Travel

Additional training shall apply in the event of overseas travel required in the performance of this effort. The Contractor’s employees who travel overseas shall complete all required training and paperwork 45 days prior to the travel dates. The Contractor and associated sub-contractor employees shall receive Government provided area of responsibility (AOR) specific AT awareness training. The Contractor shall comply with theater clearance requirements and allow the combatant commander to exercise oversight to ensure the Contractor’s compliance with combatant commander and subordinate task force commander policies and directives in accordance with DFARS Clause 252.225-7043 and AR 525-13.

3.1.11 Common Access Cards (CAC)

The Contractor shall apply for Common Access Cards (CACs) for the necessary personnel involved with site visits to Government facilities to meet the requirements of this work effort.

The Contractor shall apply for the CAC with the Trusted Associate Sponsorship System Registration Request Form and provide it to the Government for review and approval.

For Contractors that do not require CAC, but require access to DoD facility or installation, the Contractor and all associated sub-contractors employees 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.

3.2 Systems Engineering

The Contractor shall translate the basic operational needs, requirements and objectives, interface and other design constraints including cost, into preliminary, verifiable, functional requirements and objectives, while conducting cost-benefit trades to support refinement of the preliminary functional requirements. The Contractor shall complete the VCTS design (balanced with respect to performance, cost, schedule, and risk) and verify it meets the systems requirements. The Contractor shall assess proposed changes in the functional architecture, physical hierarchy, and baselines and objectively trade alternatives to balance performance, cost, schedule, and risk prior to approval.

3.2.1 Systems Design

The Contractor shall use the specifications and requirements documents associated with the VCTS as the basis for development of all implementing specifications. Standards bodies or de facto standards (set by the market place) shall be used for products, practices and tools. Selected designs and specifications shall be based on performance, cost, industry acceptance, long term availability, supportability, and upgrade potential.

3.2.1.1 Fabrication, Assembly, Integration and Test Stage

The Contractor shall resolve product deficiencies when specifications for the system, product, subsystem, assembly, or component are not met, as determined by inspection, analysis, demonstration, or test. The Contractor shall verify that the products designed satisfy specifications. Functional configuration audits shall be completed to verify that products have achieved requirements; that they satisfy the characteristics as specified in specifications, and that test plans and procedures were complied with. The results of the audit shall be documented. The Contractor shall test the system and subsystems needed to verify that the products meet the performance requirements stated in the associated System Requirement Document(s) (SRD).

3.2.2 Hardware Engineering

The Contractor shall integrate and assemble VCTS system hardware that satisfies the performance requirements stated in the SRD. The Contractor shall conduct market surveillance and market investigations in order to maximize the use of commercial and non-developmental items. The Contractor shall apply the systems engineering process during each level of system development (system, subsystem, and component) to add value (additional detail) to the products defined in the prior application of the process. Through each of the following design stages, information generated shall be documented in the integrated database.

3.2.3 Cybersecurity

The system shall be identical to the existing VCTS Cybersecurity risk profile and shall be in all manner identical to those systems unless prior approval from the government is obtained. There will be no cybersecurity scan required. The VCTS scan would cover the same configuration for the ARCENT program.

3.2.4 Specialty Engineering

The Contractor shall provide Supportability Engineering, Reliability, Availability and Maintainability (RAM) Engineering, Safety Engineering, Quality Engineering, Human Factors Engineering, Electromagnetic Environment Effects Engineering, Containment and Corrosion Control and Standardization as defined in the sections below.

3.2.4.1 Supportability Engineering

The Contractor shall ensure the supportability of the system through planning, implementation, and verification of materials, services and resources required to satisfy the operational requirements. Supportability by third party Contractors for hardware, software and documentation for maintenance shall be a requirement. Readiness, availability, supportability and Life Cycle Cost shall be the primary design factors. The Contractor shall evaluate reliability, availability and maintainability factors in the design process. Design for supportability shall include the use of common fasteners and connectors, common commercial standards, and proven technology to the maximum extent possible. The system design shall minimize life-cycle costs and maximize life-cycle supportability by avoiding the use of proprietary items; components with limited sources for spare parts, support, or maintenance;

recurring usage or service fees; and the need for special tools or test equipment.

3.2.4.2 Reliability, Availability and Maintainability (RAM) Engineering The Contractor shall develop, implement and manage a process satisfying all RAM requirements and be completely integrated within the systems engineering process. RAM status shall be included as part of each program review. The Contractor shall conduct trade off studies to ensure quantitative issues such as stress levels, selection of parts, parts simplicity and redundancy are properly considered in the design trade off. The Contractor shall verify that reliability requirements are attained through analysis.

3.2.4.3 Safety Engineering

The Contractor shall develop and implement tasks and activities to identify, evaluate, and eliminate or control hazards throughout the program’s life cycle. The Contractor shall ensure the safety of the system’s design, operation, transportation, maintenance and support. The Contractor shall conduct safety analyses, hazard identification and classification and hazards tracking integral to the system design effort. A hazard risk index including hazard severity and hazard probability levels shall be developed for all hazards. The Contractor should update the current SAR to meet the final design specifications.

DI-SAFT-80102C Safety Assessment Report (SAR)

3.2.4.3.1 Health Hazard Assessment

The Contractor shall identify potential health hazards and recommend engineering controls, equipment and protective procedures to reduce the associated risk to an acceptable level. The Contractor shall assess system, facility, and personnel protective equipment design requirements to allow safe operation and maintenance. When feasible engineering designs are not available to reduce hazards to acceptable levels, the Contractor shall develop alternative protective measures.

The Contractor shall address the hazardous materials listed in the Environmental Protection Agency's (EPA) toxics release inventory and the list of Class I and Class II stratospheric ozone depleting substances (ODSs), as listed 29CFR1910.1200. The Contractor should update the current HHAR to meet the final design specifications.

DI-ADMN-80925A Revision to Existing Government Documents

3.2.4.4 Quality Engineering

The Contractor shall establish measurement system that will provide maximum visibility into new and prior processes to assure contractual requirements are being met. The Contractor shall select the proper methods to analyze these processes to continuously improve the system.

Metrics shall be developed to assist management visibility into an adequate process control system. The Contractor shall establish and maintain a computerized discrepancy tracking system within the IDE with the ability to produce complete permanent records of all discrepancies or a database listing. All discrepancy correction shall be documented and entered in the integrated database.

3.2.4.4.1 Test Discrepancies

The Contractor shall establish a suspense system to ensure timeliness of analysis and corrective action of each test discrepancy. The Contractor shall establish a process to receive test discrepancies and update the tracking system. A hardcopy discrepancy reporting system shall be established to document Contractor and Government verification of corrective actions. The Contractor shall be responsible for informing the Government of the status of each discrepancy.

Upon closeout of a discrepancy, the Contractor shall notify the Government designated test director that the discrepancy has been corrected and the tracking system has been updated. Final test reports shall include scanned copies of all test discrepancy sheets with signatures.

3.2.4.4.2 Discrepancy Processing

The Contractor shall document a detailed description defining the changes made to the equipment, hardware, and software to correct each discrepancy. Each discrepancy correction that modifies or changes any baseline shall be documented and entered in the Configuration Management system. Configuration items include but are not limited to hardware asset version, software asset version and system asset version. The CCB must approve the resolution of the test discrepancy before implementing the described resolution. All discrepancies shall be rechecked prior to completion of test.

3.2.4.4.3 Test Discrepancy Severity

The Contractor shall assign the priority of effort used to address test discrepancies based on the test discrepancy severity designated by the test team, in accordance with the ground rules established by the CCB. The following severities shall be assigned during or after the test, with the Government reserving the right to make the final determination of the severity of any test discrepancy. Severities shall be assigned as follows:

Severity 1 Safety issue or issue that prevents accomplishment of an operational or mission essential capability or requirement

Severity 2 Adversely affects the accomplishment of an operational or mission essential capability or requirement and there is no work-around solution acceptable to the Government

Severity 3 Adversely affects the accomplishment of an operational or mission essential capability or requirement but there is a work-around solution acceptable to the Government

Severity 4 Results in user/operator inconvenience or annoyance but does not affect a required operational or mission essential capability or requirement

Severity 5 Any other effect (e.g., documentation error)

3.2.4.5 Human Factors Engineering

The Contractor shall plan and implement a human factors engineering program to insure the satisfaction of system objectives and personnel safety of the trainees, operator and maintainer.

Identify and eliminate program risk associated with critical human factors that have a significant impact on readiness, usability, life cycle cost, schedule, performance, or safety. Ensure manpower, personnel, training, and logistics support information is derived from early human engineering analyses such that human factors engineering can be applied to influence the design effort. Verify through test and evaluation that trained personnel can safely, effectively and efficiently operate, maintain and control the system in its intended operational environment.

3.2.4.6 Electromagnetic Environmental Effects (E3)

The Contractor shall determine the criteria and verification method to ensure that the VCTS system’s electronics or electrical hardware configuration is not a source of electromagnetic interference (EMI) or a victim of E3 in the intended operational environment in which it is installed or at its operational locations. The Contractor shall include grounding and wire shielding for VCTS fixed and mobile sites from EMI. The Contractor shall establish and maintain a process to verify and assure the system operations functionality is not affected by E3.

3.2.4.7 Contaminate and Corrosion Control

The Contractor shall incorporate the latest state-of-the-art corrosion control into the system design process, manufacturing process, all levels of maintenance, supply and in the storage processes. Design concepts shall reflect realistic environments and resource availability as determined by logistic support analysis.

3.2.4.8 Standardization

The Contractor shall influence the system design to achieve maximum subsystem, component and repair parts commonality within the VCTS. The Contractor shall minimize equipment and parts proliferation through a standardization effort.

3.2.5 Integration of Third Party Products

The contractor shall support development, integration, configuration management, test and fielding of third party hardware and software as directed by the Government.

3.3 Technical Interchange Meetings (TIMs)

The Contractor shall conduct and participate in technical interchange meetings to be held at both contractor and Government facilities. The specific locations, dates, and duration of the meetings shall be as specified in the Integrated Master Schedule (IMS). The meetings shall be co-chaired by a Government and contractor representative. The Contractor shall be prepared to explain the reasoning, assumption, and methodologies in arriving at particular conclusions, recommendations, or alternatives in the accomplishment of the tasks required by the contract.

The Contractor shall prepare drawings and other data, as required, to aid in the presentations.

The Contractor shall have all the required personnel and resources present. The Contractor shall make available facilities for Government only meetings. These Government meeting facilities shall include direct internet access for Government personnel laptops. The Contractor shall ensure cell phone access throughout the contractors facility. The Contractor shall prepare the meeting agendas and document the meeting results. Except where noted herein, meetings shall be considered fulfilled when all of the following items are completed:

• A formal review meeting has been conducted.

• All action items requiring contractor response have been documented and posted.

• Submittal of TIM minutes.

The Contractor shall conduct design reviews at TIMs to include reviews of the system, subsystem, component, life cycle processes, test readiness, and production.

DI-ADMN-81505 Report, Record of Meeting/Minutes

3.4 Product Definition Data (PDD)

During the systems engineering and design, as applicable, and in accordance with MIL-STD- 31000A, the Contractor shall assess, update, and maintain Product Definition Data (PDD) that accurately depicts the final product. The PDD is the technical description of items adequate for supporting an acquisition strategy, production, engineering and logistics support. The PDD shall disclose complete design (level 3 drawings), logistics, manufacturing requirements, and the means of measuring compliance with the requirements. Piece part information (drawings, computer aided design files, models and meta data.) and associated lists shall provide the necessary design, engineering, manufacturing, and quality assurance requirements information necessary to enable, maintain and sustain the procurement or manufacture of an interchangeable item that duplicates the physical and 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 or 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 compliance. The Contractor shall include all electronic models for assemblies and subassemblies from the lowest level component to the top level system component. The Contractor shall provide as part of the Technical Data Package (TDP) Contract Data Requirements Lists (CDRL) a Government owned copy of each software program necessary to view the deliverables. The Contractor shall obtain document numbers from the Government for the PDD elements as required. The Contractor shall not add prefixes or suffixes to the numbers.

All unused numbers shall be returned upon completion of PDD preparation.

DI-EDRS-80918 Technical Data Package Index DI-SESS-81003E Commercial Drawings and Associated Lists DI-SESS-81000E Product Drawings and Associated Lists

3.4.1 PDD Updates

The Contractor shall maintain the PDD current. This shall include updates resulting from changes to the PDD baselines and the engineering release changes.

3.5 Integrated Logistics and Supportability

3.5.1 Logistics Support Analysis

Contractor shall ensure supportability of the VCTS through planning, implementation, and verification of materiel and services to meet operational requirements. Readiness, availability, and supportability shall be the primary design factors.

The Contractor shall evaluate reliability, maintainability, and availability factors in the design process. Updates to design for supportability shall include the use of common fasteners and connectors, common commercial standards, and proven technology. Updates to system design shall minimize life-cycle costs and maximize life-cycle supportability by avoiding the use of proprietary items; components with limited sources for spare parts, support, or maintenance;

recurring usage or service fees; and the need for special tools or test equipment.

3.5.2 Supportability Analysis and Logistics Product Data (LPD) The Contractor shall conduct repair level analyses, develop diagnostic, preventative maintenance and repair procedures, conduct facilities analyses, refine hardware/software maintenance and support concepts, and identify life cycle support resource requirements including required initial spares, repair part, consumables and support equipment. The Contractor shall update the VCTS GFE listing of items to be repaired, items to be discarded, and the level of maintenance at which the repair should be performed along with associated cost. The Contractor shall identify any/all post VCTS GFE support issues that may pose Life Cycle support risks.

DI-ADMN-80925A Revision to Existing Government Documents

3.5.3 Maintenance Concept

The Contractor shall update all VCTS logistics data, manuals, and training in accordance with the designated sustainment concept to maximize utility of delivered services, and data to the intended target audiences. After fielding, sustainment for the systems will be provided by a government contracted third-party Life-Cycle Contractor Support (LCCS) provider. The maintenance concept will consist of two levels of maintenance: Field and Sustainment.

3.5.3.1 Field Maintenance

Field level maintenance is defined as on-system maintenance including preventative maintenance, daily readiness checks and services, adjustments to controls and other maintenance that can be accomplished without removing the affected major assembly from its deployed location for extensive repair. Field maintenance is accomplished without the aid of special tools, support equipment, or additional training knowledge or skills. Field level mechanics will perform inspections, diagnose faults, and replace components on end items for return to the user.

3.5.3.2 Sustainment Maintenance

Sustainment Maintenance is defined as off-system maintenance to include troubleshooting and the removal and replacement of failed components that cannot be performed at the Field Maintenance level. Sustainment maintenance actions are beyond the capability of field level maintenance and include extended diagnostics, overhaul, refurbishment, rebuild, or other prolonged repair actions.