SECTION_C_DRAFT.docx

C.1 General The Common Robotic System (Individual) (CRS(I)) is a modular system that consists of a robotic platform and a universal controller that provides a multitude of standoff capabilities (in accordance with (IAW) the Performance Specification, (ref. Attachment 0001) to support current and future missions through use of modular payloads and sensor suites for the Army. The universal controller is the Army solution to provide active and passive control for ground and air unmanned systems. Mission profiles include detect and confirm presence and identify disposition and counter hazards. Additionally, CRS(I) will support current and future payload missions for the Engineer's area clearance and route clearance platoons, Special Operational Forces (SOF) detachments, and CBRN (Chemical, Biological, Radiological, or Nuclear) units.

C.1.1 Introduction This CRS(I) Statement of Work (SOW) includes Engineering, Manufacturing and Development (EMD1 and EMD2), Production Verification & Low Rate Initial Production (LRIP), and Full Rate Production (FRP) IAW Integrated Master Plan (IMP) (ref. Attachment 0005). The requirements contained within sections C.1.2 through C.17 describe effort that shall be performed in each Task Order awarded.

C.1.1.1 Task Order 0001 applies to the EMD1 phase, which applies to the start of the Engineering and Manufacturing Development at Contract Award through the completion of the government Run-Off Test (ref. C.18).

C.1.1.2 Task Order 0002 applies to the EMD2 phase, which will begin after the award of the Task Order containing the EMD2 effort (ref. C.19).

C.1.1.3 Task Order 0003 applies to the Production Verification & LRIP Phase, which starts after the completion of EMD2 (ref. C.20).

C.1.1.4 Task Order 0004 applies to the Full Rate Production (FRP) that starts after the completion of Production Verification & LRIP (ref. C.21).

C.1.2 Product Management The Unmanned Ground Vehicles (UGV) PdM is responsible for managing and executing the CRS(I) program level responsibilities under Force Projection Program Management Office in Program Executive Office Combat Support/Combat Service Support (PEO CS&CSS).

C.1.3 Definitions The CRS(I) performance requirements are described in the Performance Specification (ref. Attachment 0001). In this SOW, the term “CRS(I) System” will refer to the Mobile Base Platform (MBP), the Operator Control Unit (OCU), and the module-based payloads to support a variety of missions.

C.1.3.1 CRS(I) Aspects C.1.3.1.1 The term “vehicle”, as identified throughout this document and support attachments and CDRLs, can be replaced with “system”.

C.1.3.1.2 Mobile Base Platform (MBP). The MBP consists of the basic robot/chassis integrated with the audio subsystem, controls, drive cameras and interfaces as standard payloads. Mission specific modular payloads are additions to the MBP. The term “mobile base platform”, as identified throughout this document, the Performance Specification and support attachments and CDRLs, can be replaced with “mobility base platform”.

C.1.3.1.3 Operator Control Unit (OCU). The OCU consists of a computational module, hand controller, display device, power sources and radio subsystems. The OCU shall be Universally defined as the capability to passively receive communications from CRS(I), non-CRS(I) robotic ground and air vehicles, actively control both ground and air vehicle types, and be a modular solution in accordance with Robotics and Autonomous Systems–Ground (RAS-G) Interopereablity Profile (IOP) (ref. Attachments 0035 - 0044) (ref C.8.1).

C.1.3.1.4 Mission Payloads. Mission specific payloads include Standard, Engineer and Explosive Ordinance Disposal (EOD), and CBRN which are based on the mission profile as described in the Operational Mode Summary/Mission Profile (OMS/MP) (ref. Attachment 0030).

C.1.3.1.5 Calendar Days. References to days are in calendar days unless otherwise specified. The government defines business days as Monday thru Friday except Federal Holidays.

C.1.3.1.6 Government Approval. Government Approval means approval by the Procuring Contracting Officer (PCO) unless otherwise specified.

C.1.3.1.7 Handheld-Ground Control Station (H-GCS). H-GCS is defined as the hardware, software, and associated components required to operate a RQ-11 Raven and RQ-20 Puma.

C.1.3.2 Component. A component is a subsystem, assembly, subassembly, or other major element of an end item.

C.1.3.2.1 Inter-Component Dependancy. An inter-component dependency are those components whose behavior or outputs are dependent on the behavior or output of another component.

C.1.3.3 Portability. Portability is the usability of the same software in different computing environments.

C.1.3.4 Scalability. Scalability is the capability of the software program, in whole or in part, to expand over time to support increasing workloads or requirements.

C.1.3.5 Standards-Based. Standards-Based means widely accepted and supported software development standards that are set by recognized standards organizations or the marketplace.

C.1.3.5.1 Interface. An Interface is the software languages and codes that the application or applications of the overall software solution uses to communicate with each other and with the hardware. It is the shared boundary across which two separate components of a computer system exchange information.

C.1.3.5.2 Standards-Based Interfaces. Standards-Based Interfaces are those Interfaces defined by Standards-Based organizations.

C.1.3.6 Service-Oriented Architecture. Service-Oriented Architecture is a software design pattern where in services are provided to the other components by application components, through a communication protocol over a network. Unmanned Control Segment (UCS) is an example of a service-oriented architecture.

C.1.4 Applicable Documents

The Applicable Documents List is available in the SOW Applicable Documents (ref. Attachment 0003).

C.1.5 Requirements

C.1.5.1 CRS(I) System. The contractor shall deliver a CRS(I) System that meets all the performance requirements of the CRS(I) Performance Specification (ref. Attachment 0001) and this SOW. The contractor shall over-pack a printed copy and a Digital Video Disc (DVD) of the technical manual (ref. C.15.4) with each CRS(I) System.

C.1.5.1.1 Basic Issue Items (BII). The contractor shall provide BII for each production CRS(I) System. The BII shall consist of all items essential for an operator or crew to place the CRS(I) System into operation and to accomplish its intended functions as defined in AR 700-18 paragraph 8-5. The contractor shall over-pack the BII with the CRS(I) System. The contractor shall list BII IAW MIL-STD 40051-2 in the technical manual. The contractor shall deliver the BII List IAW (ref. CDRL A091).

C.1.5.1.2 Initial Service Package (ISP). The contractor shall provide an ISP (ref. CDRL A098) for each CRS(I) System. The contractor shall over-pack the ISP List and components with the production system. The ISP shall consist of all service parts required to meet the warranty service interval and to perform the first scheduled maintenance. The contractor shall mark each item with nomenclature, part number, and, if applicable, national stock number (NSN) . The NSNs will be provided to the contractor by the government when marking of the NSN is required.

C.1.5.1.3 Mobile Base Platform (MBP). The contractor shall provide the Mobile Base Platform (MBP), as part of the CRS(I) System, which consists of the basic robot/chassis integrated with the audio subsystem, controls, drive cameras and interfaces as standard payloads per the requirements of the CRS(I) Performance Specification (ref. Attachment 0001). Mission specific modular payloads are additions to the MBP.

C.1.5.1.4 Operator Control Unit (OCU). The contractor shall provide the OCU, as part of the CRS(I) System, which consists of a computational module, hand controller, display device, power sources and radio subsystems in the quantities specified in the task order and per the requirements of the CRS(I) Performance Specification (ref. Attachment 0001).

C.1.5.2 Payload Integration Kits. The contractor shall manufacture and deliver the following Payload Integration Kits:

C.1.5.2.1 Standard Payload Mounting Kit. The contractor shall deliver Standard Payload Mounting Kits that include all brackets, screws, cables, and other hardware necessary to install the Standard Payload Mission Equipment on the CRS(I) System in the quantities specified in the task order and per the requirements of the CRS(I) Performance Specification (ref. Attachment 0001).

C.1.5.2.2 Engineer and Explosive Ordinance Disposal (EOD) Payload Mounting Kit. The contractor shall deliver EOD Payload Mounting Kits that include all brackets, screws, cables, and other hardware necessary to install the EOD Payload Mission Equipment on the CRS(I) System in the quantities specified in the task order and per the requirements of the CRS(I) Performance Specification (ref. Attachment 0001).

C.1.5.2.3 Chemical Biological Radiological Nuclear (CBRN) Sensor Mounting Kit. The contractor shall deliver CBRN Sensor Mounting Kits that include all brackets, screws, cables, and other hardware necessary to install the below listed CBRN Sensors on the CRS(I) System in the quantities specified in the task order and per the requirements of the CRS(I) Performance Specification (ref. Attachment 0001).

The CBRN Sensor are listed below:

JCAD, M4A1 NSN 6665-01-586-8286

TIC Vapor Detector, Part Number MCB3-0RC178E-DS1 Gas Monitor (CWA), Part Number MCB3-A3C136E-DS1 Radiac Dosimeter GY, Part Number RGU-100-GO

C.1.5.3 Authorized Stockage List (ASL). The contractor shall provide as ASL (ref. CDRL A103) package for each production CRS(I) System, unless otherwise specified in the task order. The contractor shall over-pack the ASL with each production system. The ASL package shall be comprised of parts that have a production lead time of at least eight months, or are mission essential, to keep the system operational for three months. The contractor shall mark each item with nomenclature, part number, and NSN.

C.1.5.4 Special Tools Kit. The contractor shall provide a Special Tools Kit in the quantities specified in the task order. The Special Tools Kit shall contain all government approved special tools for the CRS(I) System (ref. CDRL A098, STTE). The contractor shall provide a unique part number that encompasses all tools within the Special Tools Kit.

C.2 Program Management and Structure The contractor shall define and ensure Key Roles (e.g. Program Management (PM) and Integrated Product Team (IPT) leads) are staffed with personnel of commensurate education, training, work experience, and technical training necessary to effectively and efficiently perform required tasks. The contractor shall present their organizational Key Roles at the Start of Work Meetings (SOWM1 (C.18) and SOWM2 (C.19)) and shall discuss the plan for communicating and transitioning personnel changes. When the contractor intends to change the personnel working in Key Roles, the contractor shall to the maximum extent possible, provide 14 days notice to the Contracting Officer Representative (COR) prior to the personnel transition. To the maximum extent possible and practical, the contractor shall conduct a transition meeting with the government within seven days of the anticipated transition date to discuss all key issues related to such a transition. The contractor shall provide Minutes (ref. CDRL A002), reporting on any government concerns or issues discussed in the transition meeting, and providing analysis of actions that the contractor will take to ensure a seamless transition.

C.2.1 Integrated Product Teams (IPTs) For purposes of this contract, any formal or informal title, (e.g., "Working Group," "Integrated Design Team", etc.) shall be considered an Integrated Product (or Process) Team, or "IPT". IPTs shall be established to serve as the primary contract management tool and key method of communication for this contract. The first IPT meetings shall be held concurrently with the Start of Work Meeting (SOWM). Subsequent IPT meetings shall be held monthly or as mutually agreed between the government and contractor. The contractor shall be responsible for developing all IPT agendas (ref. CDRL A001, Conference Agenda) and meeting minutes (ref. CDRL A002). The IPT meeting minutes shall be made available to the government and discussed at subsequent IPT meetings. The contractor shall allow physical and dial-in access to the government for all contractor IPT meetings and any contractor design reviews following the SOWMs, in order to allow mutual understanding and maintain the program direction.

C.2.1.1 IPT Structure. The IPT structure may include the following teams: Program Management, Business Management, Acquisition, Systems Engineering, and Supportability & Logistics. Systems Engineering IPT should incorporate the following disciplines: Environmental, Safety, and Occupational Health (ESOH); Human Systems Integration (HSI); Reliability, Availability, Maintainability, and Test (RAM-T); Risk; Transportability; Corrosion; Software; Quality Assurance; Cybersecurity; and Information Assurance. IPT Leaders shall be identified no later than the SOWMs. The contractor may propose new or modified IPT or changes to the number, composition, functionality, and responsibilities of IPTs at the SOWMs for government consideration. Proposed changes will be jointly determined thereafter. Throughout the life of this contract, both contractor and government IPT members have the responsibility to propose new or modified IPTs when needed to focus efforts or improve effectiveness.

C.2.2 Integrated Master Schedule (IMS) The contractor shall develop and maintain an Integrated Master Schedule (ref. CDRL A003) interoperable with Microsoft Project v2013 by logically networking detailed program activities using the government provided IMP (ref. Attachment 0005). The IMP outlines the program's major reviews that shall be satisfied to accomplish the work under this contract. The contractor shall report on program progress at each Program Management Review (PMR), Technical Review, and Audit. The contractor shall utilize the IMP and contract deliverable dates to develop their IMS baseline.

C.2.3 Internet-Based Collaboration The CRS(I) Integrated Data Environment (IDE) is the PdM UGV SharePoint portal, that consists of internet-based collaboration tools (defined below) that shall be used to facilitate information sharing and collaboration within a secure government server environment that provides controlled, distributed access to CRS(I) program information, both released and in-work. Types of information that shall be processed and maintained within the IDE will include CRS(I) program documents, reports, program management data, meeting-related information, modeling and simulation/analysis data, manufacturing information, and test data, consistent with the Unmanned Ground Vehicle Security Classification Guide (ref. Attachment 0006). Any posting to the IDE is considered a data deliverable in the context of DFARS Data Rights clauses including 252.227-7013 and 252.227-7014. The IDE shall only be used for sharing unclassified/FOUO information. Information regarding the handling of all classified information will be provided at the SOWM1. To access the CRS(I) IDE, contractor associates shall have a DoD approved Public Key Infrastructure credential, obtainable through the DoD External Certification Authority (ECA) program: http://iase.disa.mil/pki/eca/Pages/certificate.aspx.

C.2.3.1 IDE Notification. The contractor shall notify appropriate government personnel, Contracting Officer Representative (COR) via e-mail when new or updated documents are posted to the IDE or Sharepoint site. The notification email shall include a hyperlink to the location of the posted content.

C.2.3.2 IDE Collaboration Tools. The contractor shall use the CRS(I) SharePoint server to facilitate unclassified, secure internet-based information sharing between CRS(I) program participants. SharePoint will also serve as the primary means of submitting unclassified/FOUO CDRL items, unless otherwise stated within a specific CDRL item. The contractor shall conduct contractor-government internet conferencing (web meetings) using government approved systems such as the Defense Connect Online (DCO) conferencing tool. Details on specific IDE tools, requirements for access, and approach for use will be discussed at the SOWM1.

C.2.3.3 AKO Sponsor. The government will sponsor Army Knowledge Online (AKO), SharePoint, DCO and other required accounts. Details will be provided at the SOWM1. The government can only sponsor accounts for U.S. Citizens. The contractor shall provide names, contact information, level of access (upload or download), and training required for personnel requiring access to these tools no later than (NLT) SOWM1 meeting. A Non-Disclosure Agreement must also be provided (ref. Attachment 0002).

C.2.3.4 VISION Digital Library System (VDLS). The contractor shall use Versatile Information Systems Integrated On-Line Nationwide (VISION), VISION Digital Library System (VDLS) to access data from government testing. Details on specific tools, requirements for access, and approach for use will be discussed at the SOWM1. The contractor shall provide all names, contact information, and level of access (upload or download) IAW VDLS Account Access (ref. Attachment 0004). The list of contractor personnel requiring VDLS access shall be provided to the government no later than 50 calendar days prior to the Run-Off Test Readiness Review (TRR).

C.2.3.5 External Certification Authority (ECA) Certificates. In order to access these systems, the contractor shall have or obtain External Certification Authority (ECA) Certificates or DoD Common Access Cards (CAC) as defined in Section C.7.2.1.3.

C.2.4 Data Accessions

The contractor shall identify internal data, which the contractor generates in compliance with the work effort described in this SOW IAW Data Accessions List (ref. CDRL A029).

C.2.5 Earned Value Management System (EVMS)

In the performance of this contract, the contractor shall use an Earned Value Management System (EVMS) that complies with Table 5 (Earned Value Management (EVM) Implementation Policy) in DoDI 5000.02 (Operation of the Defense Acquisition System), the American National Standards Institute/Electronic Industries Alliance Standard 748 (ANSI/EIA-748), DFARS Clauses 252.234-7001, 252.234-7002, 252.234-7003, and 252.234-7004, and the contractor’s own documented EVMS Description. The contractor shall deliver a monthly Integrated Program Management Report (IPMR) (ref. CDRL A085).

C.2.5.1 Over-Target Baseline (OTB) or Over-Target Schedule (OTS). In exceptional circumstances indicated by contract performance (per the Contractor's EVMS Description), the contractor shall submit a written request to the PCO for approval to initiate an Over-Target Baseline (OTB) or Over-Target Schedule (OTS). The request shall include a top-level projection of cost or schedule growth, a recommendation of whether or not performance variances should be retained on record, and a schedule for implementing a new baseline. The contractor shall not implement the OTB or OTS restructuring prior to receiving written approval from the PCO.

C.2.5.2 Application to Subcontractors. The contractor shall flow-down EVM requirements to subcontractors meeting the applicable thresholds per DFARS clauses 252.234-7001, 252.234-7002, 252.234-7003, and 252.234-7004. The performance information reported by the subcontractors shall be incorporated and integrated into the contractor's management system. The contractor shall conduct Integrated Baseline Reviews (IBRs) on any subcontractors with contracts requiring EVM. Although the government may attend these IBRs, the actual event shall be the contractor's responsibility.

C.2.6 Bill of Materials (BOM)

The contractor shall deliver a CRS(I) System Bill of Material (BOM) (ref. CDRL A007). The information used to create this CDRL shall be available to the government and discussed at IPT meetings as well as major reviews IAW the government provided IMP (ref. Attachment 0005).

C.2.7 Contract Work Breakdown Structure (CWBS)

The contractor shall use the CRS(I) Work Breakdown Structure (WBS) (ref. Attachment 0032) as a departure point for preparation of the CWBS (ref. CDRL A008). The CWBS shall be developed using the latest version of MIL-STD-881 (WBS) as guidance and continue the WBS numbering scheme to decompose the CWBS to level 5 or lower. The information used to create CWBS (ref. CDRL A008) shall be available to the government and discussed at IPT meetings as well as major reviews IAW the government provided IMP (ref. Attachment 0005).

C.2.8 Contract Funds Status Report (CFSR)

The contractor shall prepare, update, and submit the Contract Funds Status Report (CFSR) (ref. CDRL A006).

C.3 Meetings, Audits, Assessments, and Reviews

C.3.1 Participation/Administration

The contractor shall host, unless otherwise specified in the paragraphs below, all meetings, audits, assessments, and reviews. When agreed upon by the government, the contractor shall schedule face-to-face meetings for multiple topics to minimize personnel resources and travel expenses. The contractor's hosting duties and responsibilities shall include sending invitations and providing the necessary facilities, media resources, security, minutes, and hard copy materials related to the preparation and execution of the meetings, audits, assessments, and reviews. The contractor shall provide teleconference and Defense Collaboration Services (DCS) access to the government for all meetings, audits, assessments, and reviews. The government will have the discretion on scheduling of meetings.

C.3.1.1 Meeting Agenda and Read-Ahead Packages. The contractor shall submit an agenda with a read-ahead package (CDRL Data Item A001) in contractor format for all meetings, audits, assessments, and reviews in this section C.3 for the government to review and approve. Each agenda shall include presentation of all items for that specific event. Cost & IMS information may be included as an agenda item at meetings, conferences, and reviews to include discussion of contract progress and issues (performance goals, exit criteria, schedule progress, risks and mitigation, and cost impact).

C.3.1.2 Meeting Minutes

The contractor shall record and provide meeting minutes (ref. CDRL A002) for all meetings, audits, assessments, and reviews. The contractor's recorder shall be identified at the beginning of each event and shall record all action items as part of the Meeting Minutes.

C.3.1.3 Meeting Invitations

Government participants will be identified by the government program office. The contractor shall send invitations for all meetings not less than 14 days prior to the event.

C.3.1.4 Program Information

Information developed on this contract including data used to develop or delivered with each CDRL shall be made available by the contractor to the government for discussion during all meetings including program reviews and meetings, technical reviews and audits, and IPT meetings IAW C.3.1.1.

C.3.2 Leadership Program Management Meetings

The contractor shall conduct at a minimum, a monthly Program Management (PM) Meetings. The meetings shall commence the month following the SOWMs and can be a face to face meeting or a teleconference. The meetings shall include leadership level contractor program management personnel that shall address cost, schedule, performance, risk status, and the contractor shall be prepared for detailed discussion with the government.

C.3.3 Integrated Product Team (IPT)/Meetings C.3.3.1 System Engineering IPT Meetings The contractor shall conduct weekly System Engineering (SE) IPT meetings via teleconferences to discuss the technical planning and execution of CRS(I) System analysis, design, development, and integration activities.

C.3.3.2 Logistics Guidance IPT Meetings The contractor shall conduct weekly Logistics Guidance IPT meetings via teleconferences to discuss logistics data and products.

C.3.3.3 Software IPT Meetings The contractor shall conduct weekly Software IPT meetings via teleconferences to discuss the design and development of the CRS(I) System software.

C.3.3.4 Human Systems Integration (HSI) IPT Meetings The contractor shall conduct a monthly HSI IPT meetings (Ref. C.14) in conjuction with the System Engineering IPT meetings via teleconferences. HSI IPT meetings will be held jointly with the System Safety and Environmental Working Group (IAW C.13.11) with government participation and oversight, providing HSI integration system status, issues, database updates, recommendations, and design data. The contractor shall be prepared for detailed discussion of these topics. The meetings shall include contractor HSI personnel and working level IPT personnel. The contractor shall address HSI domains of safety, health hazards, human factors engineering, Soldier survivability, manpower, and personnel and training. The contractor shall address HSI database issues in terms of risk assessment, mitigation, cost, and identification of organization and personnel responsible for a resource schedule to resolve issues (ref. C.14).

C.3.3.5 Corrosion Prevention Advisory Team (CPAT) Meetings The contractor shall address Corrosion Prevention, complete assigned action items, and inform the CPAT of corrosion issues and their impact on the corrosion prevention and control of the CRS(I) System. CPAT subject matter will be covered as part of System Engineering IPT meetings.

C.3.3.6 Contractor Test and Evaluation Support to the Working-level Integrated Product Team (T&E WIPT) The contractor shall provide support with an engineering representative available to the government-lead of the T&E WIPT and participate in the CRS(I) T&E WIPT teleconference only if requested by government Test Lead. The primary purpose of CRS(I) T&E WIPT is to optimize the use of T&E expertise, instrumentation, facilities, Modeling and Simulation (M&S), and the collected resources of the represented agencies and organizations to integrate the collective T&E efforts. The T&E WIPT will collectively plan, budget, resource, execute, and continuously evaluate the CRS(I) T&E program as a principal risk management agent for the Product Manager. The primary product of the T&E WIPT is the program test strategy.

C.3.3.7 Program Protection Working Group (PPWG) The contractor shall host and conduct a PPWG quarterly until the start of Full Rate Production and bi-annually throughout the remaining period of performance of the contract. The contractor shall hold the first PPWG as part of SOWM1. A government systems engineer will chair each PPWG and the contractor’s system security engineer will co-chair each PPWG. The contractor shall host the PPWG at the contractor’s site once per year, and provide the means for the government to participate via teleconference for all other PPWGs. The contractor shall ensure any updated assumptions, rationale, and results related to criticality analysis, vulnerability assessments, and risk evaluations, supply chain risk information, and mitigation are made available for government review at PPWGs.

C.4 Government Furnished Property (GFP)

C.4.1 GFP Delivery The GFP will be provided IAW the schedule outlined in the Government Furnished Property (GFP) List (ref Attachment 0028). At the SOWM1, the government will provide the technical integration data or required point of contacts (POCs) to receive information and data related to the GFP.

C.5 System Engineering (SE)

C.5.1 Systems Engineering Management Plan (SEMP)

The contractor shall prepare, execute, and provide a SEMP (ref. CDRL A009) detailing the systems engineering process for developing the CRS(I) System. The SEMP shall also include the approach for Open Systems Architecture, Cybersecurity Implementation Plan, Configuration Management, and Risk Management. The information used to create this CDRL shall be available to the government and discussed at IPT meetings as well as major reviews IAW the government provided IMP (ref. Attachment 0005).

C.5.2 System/Subsystem Specification (SSS)

The contractor shall develop and deliver the System/SubsystemSpecification (SSS) (ref. CDRL A080) for the CRS(I) System. The SSS shall be derived from and trace to the CRS(I) System P-Spec (ref. Attachment 0001). The SSS shall also address those areas where future growth is expected due to tech refresh, and where re-use is envisioned.

C.5.3 Requirements Compliance Matrix

The contractor shall provide a Requirements Compliance Matrix (ref. CDRL A004) that tracks achievement of all CRS(I) Performance Specification (ref. Attachment 0001) threshold requirements. All performance specified shall comply with the threshold level of performance in Attachment 0001. Any performance proposed above the Attachment 0001 thresholds shall become the minimum required performance of the CRS (I) System. The Requirements Compliance Matrix shall include P-Spec ID, P-Spec Requirement, Compliance Assessment (Meets Requirement, Partially Meets Requirement, Does Not Meet Requirement), and Compliance Rationale to include supporting data that describes the analysis that has been done to support the assessment. This contractor compliance verification is informational only and does not in any way supersede the verification requirements detailed in the CRS(I) Performance Specification (ref. Attachment 0001). The information used to create this CDRL shall be available to the government and discussed at IPT meetings as well as major reviews IAW the government provided IMP. The first Requirements Compliance Matrix Review will occur in conjuction with the SOWM1.

C.5.4 System/Subsystem Design Description (SSDD)

The contractor shall develop and deliver a System/Subsystem Design Description (SSDD) (ref. CDRL A079) for the CRS(I) System. The SSDD shall break down the system into relevant Hardware and Computer Software Configuration Items and how those components interface with each other to meet the system level requirements as defined in the SSS IAW C.5.2.

C.5.5 Interface Control Documents (ICDs)

The contractor shall prepare, deliver and update Interface Control Documents (ICDs) (ref. CDRL A073) that identify the interface requirements between: Hardware Configuration Items (HWCI) (HWCI to HWCI); Computer Software Configuration Items (CSCI) and hardware configuration items (CSCI to HWCI); and HWCI and CSCI to systems external to the CRS(I) System.

C.5.6 Unmanned Ground Vehicle (UGV) Interoperability Profile (IOP)

The contractor shall utilize the Unmanned Ground Vehicle (UGV) Interoperability Profile (IOP) (ref. Attachments 0035 - 0044) and shall be compliant with the CRS(I) IOP Instantiation (ref. Attachment 0018) in the design and implementation of the CRS(I) System. If the use of the UGV IOP and CRS(I) Instantiation, in whole or in part, does not support the contractor's implementation, the contractor shall provide a non-proprietary interface description with electrical, signal, mechanical, connector, and digital message protocol information in contractor format (ref. CDRL A094, IOP Contractor Standards) to describe the implementation of all interfaces identified in the CRS (I) IOP Instantiation, including rationale for the changes, for government approval. Government approval of any IOP Contractor Standards will fulfill the non-compliance section of the RAS-G IOP Overarching Profile document, section 4.9 Non-Compliance requirement. The contractor shall present its IOP approach and supporting information at major program reviews IAW C.3.2.

C.5.6.1 Contractor Support for government IOP Conformance Testing

The contractor shall provide 10 days, during each phase (EMD1, EMD2, and LRIP) of onsite software engineering technical support at TARDEC in Warren, MI for IOP conformance testing. The COR will provide the results from the Conformance Validation Tool and the contractor after reviewing the results, shall update their system to resolve all conformance issues. The conformance test will be repeated until all conformance issues have been resolved.

C.5.7 Application for Equipment Frequency Allocation (DD 1494)

The contractor shall deliver a completed Directives Division (DD) Form 1494 (DD 1494), Application for Equipment Frequency Allocation (ref. CDRL A022) for any radio spectrum dependent subsystems not on file with the Army Spectrum Management Office (ASMO). The contractor shall also provide technical information including drawings that identifies antenna type and placement on the CRS(I) System IAW Preparation of DD Form 1494, Application for Equipment Frequency Allocation (ref. CDRL A022). The contractor shall conduct the necessary coordination with the government to complete the DD 1494 data entries prior to submittal and shall respond to any inquiries regarding the requested frequency allocation as the application is staffed throughout the goverment. The DD 1494 form can be found in Attachment 0013 and instructions are available Attachments 0012.

C.5.8 Military (MIL) Grade Connector Waivers

In the design and fabrication of the CRS(I) System and its components, the contractor shall use all MIL Grade connectors. For connectors that do not meet military specifications, the contractor shall submit a Military (MIL) Grade Connector Waiver Request (ref. CDRL A030) and MIL Grade Connector Waiver Form (ref. Attachment 0019). All non-MIL grade connector waivers shall be submitted to the COR by SOWM1. Waivers are intended to be dispositioned (approved or rejected) by the government PCO by PDR. If necessary, additional waivers will be considered up to CDR. This information shall be available to the government and discussed at IPT meetings as well as major reviews IAW the government provided IMP (ref. Attachment 0005).

C.5.9 Requirements Verification C.5.9.1 Certification The contractor shall provide copies of certifications for all requirements specified in the CRS(I) P-Spec (ref. Attachment 0001) to be verified by certification IAW Certifications (ref. CDRL A056). The information used to justify the certifications shall be available to the government and discussed at IPT meetings.

C.5.9.2 Analysis The contractor shall deliver an Analysis Report (ref. CDRL A055) for all requirements in the CRS(I) P-Spec (ref. Attachment 0001) that indicate “Analysis” as the method of requirement verification. This supplied data shall consist of technical or mathematical evaluations, mathematical models, simulations, algorithms, charts, diagrams, representative data, and other appropriate means to demonstrate compliance with the requirement. The information used to conduct the analysis and generated by the analysis shall be discussed at IPT meetings, technical reviews, major program reviews, TRRs, and Audits.

C.5.9.2.1 Optics Field of View (FoV) Analysis The contractor shall prepare an Optics Field of View (FoV) analysis (ref. CDRL A099) throughout EMD1 and EMD2 phases with draft reports submitted prior to PDR, updated for CDR, and a final report provided prior Functional Configuration Audit (FCA) (ref. CDRL A099). Additional updates due to design changes (approved by the government) as a result of the FCA or other reviews will be made to the final report and re-submitted to the government. The Optics FoV Analysis shall depict the full field of view of all of the cameras integrated on the CRS(I) System for each of the payloads, highlighting any obstructions or blindspots. A plan to mitigate the view from an obstruction or blindspot shall also be included in the report. The report shall also include a description of any areas of the CRS(I) System that do not meet the Optics requirements in the performance specification as well as a mitigation plan.

C.5.9.2.2 Manipulator Arm Range of Motion Analysis The contractor shall prepare a Manipulator Arm Range of Motion Analysis (ref. CDRL A100) throughout EMD1 and EMD2 phases with draft reports submitted prior to PDR, updated for CDR, and a final report provided prior Functional Configuration Audit (FCA) (ref. CDRL A100). Additional updates due to design changes (approved by the government) as a result of the FCA or other reviews shall be made to the final report and re-submitted to the government. The Manipulator Arm Range of Motion Analysis shall depict the full range of motion of the manipulator arm along all planes in accordance with the performance specification. The Manipulator Arm Range of Motion Analysis shall also include an analysis of the arm while holding a weight for the full range of motion in accordance with the performance specification. This analysis shall be shown for each of the configurations of payloads and shall highlight any obstructions or No Reach zones. A plan to mitigate an obstruction or No Reach zone shall be included in the report. The report shall also include a description of any areas of the CRS(I) System that do not meet the manipulator arm requirements in the performance specification as well as a mitigation plan.

C.5.9.2.3 Weight Analysis The contractor shall prepare a Weight Analysis (ref. CDRL A101) throughout EMD1 and EMD2 phases with draft reports submitted prior to PDR, updated for CDR, and a final report provided prior Functional Configuration Audit (FCA) (ref. CDRL A101). Additional updates due to design changes (approved by the government) as a result of the FCA or other reviews shall be made to the final report and re-submitted to the government. A plan to mitigate weight related risks shall also be included in the report. The report shall also include a description of any areas of the CRS(I) System that do not meet the weight requirements in the performance specification as well as a mitigation plan.

C.5.9.2.3.1 The contractor shall update and maintain the weight estimates throughout the duration of this contract IAW Weight Analysis Report (ref. CDRL A101). The contractor shall validate weight estimates for CRS(I) System by using tracking and monitoring activities during design and production of the first deliverable system for each configuration. Weight estimates shall be under configuration control consistent with design configuration management requirements (ref. Section C.11). The contractor shall organize and format weight estimates in accordance with the BOM (ref. CDRL A007) and WBS (ref. CDRL A008). Weight estimates may include additional configurations or unique subsystem configurations as deemed necessary by the contractor. Weight estimates shall provide the center of gravity location for all configurations as defined in the Preliminary Design and compare it against the limits developed by the contractor for compliance to performance requirements. Note the use of the word “vehicle” in the following references is defined as “Mobile Base Platform (MBP)”. Weight estimates shall include the following: Curb Weight (MBP without Batteries), Gross Vehicle Weight (GVW) (MBP without Payloads), and Gross Vehicle Weight Rating (GVWR) (includes MBP with a minimum of 5 lbs. of additional mass). As part of the PDR presentation, the contractor shall provide a study of vehicle stability and payload range of motion, and identify performance limitations in accordance with the Performance Specification (ref. Attachment 0001). All vehicle weights shall be available to the government and discussed at IPT meetings as well as major reviews IAW the government provided IMP (ref. Attachment 0005).

C.5.10 Corrosion Prevention and Control

C.5.10.1 Corrosion Prevention and Control Plan (CPCP) and Finish Specification Report

The contractor shall implement Corrosion Prevention and Control. The contractor shall provide a CPCP with a Finish Specification Report (ref. CDRL A012). The information used to create this CDRL shall be available to the government and discussed at IPT meetings as well as major reviews IAW the government provided IMP (ref. Attachment 0005).

C.5.10.2 Corrosion Prevention IPT

The contractor subject matter experts shall address Corrosion Prevention and Issues during the Systems Engineering IPT meetings to ensure all corrosion issues are identified and addressed. The contractor shall brief at all major reviews identified in the IMP. During Engineering IPT meetings the contractor shall present the status of the CPCP (ref. CDRL A012).

C.5.11 Specification Sheet

The contractor shall deliver two system specification sheets for each CRS(I) System configuration (ref. CDRL A017). One sheet shall be in metric units and one sheet shall be in U.S. English units. The information used to create this CDRL shall be available to the government and discussed at IPT meetings as well as major reviews IAW the government provided IMP (ref. Attachment 0005).

C.5.11 Transportability Report

C.5.11.1 The contractor shall complete and submit a Transportability Report (ref. CDRL A018). The information used to create this CDRL shall be available to the government and discussed at IPT meetings as well as major reviews IAW the government provided IMP (ref Attachment 0005).

C.5.11.2 The contractor shall include in their overall CRS(I) System design, a shipping container that will include storage of all base platform hardware, payloads, and accessory kits with appropriate safety lifting labels IAW the Performance Specification (ref. Attachment 0001) and MIL STD 1472.

C.6 RESERVED

C.7 Command, Control, Communications, Computers, Intelligence, Surveillance, Reconnaissance, and Electronic Warfare (C4ISR/EW) Subsystems

C.7.1 Environmental Survivability and Reliability

C.7.1.1 Electromagnetic Environmental Effects (E3)

The contractor shall perform analyses, studies, inspections, and tests to verify that the CRS(I) System is designed to comply with the applicable E3 standards identified in the CRS(I) Performance Specification (ref Attachment 0001). The analyses, studies, inspections, and tests shall also be sufficient to characterize the E3 performance of the integrated system including spectrum-dependent subsystems.

C.7.1.1.1 Electromagnetic Environmental Effects (E3) Performance Report

The contractor shall provide an E3 Performance Report (ref. CDRL A021) that details the E3 performance described above. The contractor shall certify the system is designed to comply with the applicable Department of Defense (DoD), National, and International spectrum management and E3 control policies and regulations. The contractor’s system shall comply with the applicable DoD, National, and International spectrum management and E3 control policies and regulations. Additionally, it is highly desired that the robotic wireless communications system support operation on multiple frequencies bands allowing for worldwide operation and is certified to operate in a wide range of countries including; United States, Canada, European Union, Japan, and Korea. The information used to create this CDRL shall be available to the government and discussed at IPT meetings as well as major reviews IAW the government provided IMP (ref. Attachment 0005).

C.7.1.2 Frequency Allocation Data

The contractor shall deliver a completed Directives Division (DD) Form 1494 (DD 1494), Application for Equipment Frequency Allocation (ref. CDRL A022) for any radio spectrum dependent subsystems not on file with the Army Spectrum Management Office (ASMO). The contractor shall also provide technical information including drawings that identifies antenna type and placement on the CRS(I) System (ref. CDRL A022). The contractor shall conduct the necessary coordination with the government to complete the DD 1494 data entries prior to submittal and shall respond to any inquiries regarding the requested frequency allocation as the application is staffed throughout the goverment The DD 1494 form can be found in Attachment 0013 and instructions are available Attachments 0012.

C.7.1.3 MIL Grade Connector Waivers

In the design and fabrication of the CRS(I) System and its components, the contractor shall use all MIL Grade connectors. For connectors that do not meet military specifications, the contractor shall submit a Military (MIL) Grade Connector Waiver Request (ref. CDRL A030) and MIL Grade Connector Waiver Form (ref Attachment 0019). All non-MIL grade connector waivers shall be submitted to the COR by SOWM1. Waivers are intended to be dispositioned (approved or rejected) by the government PCO by PDR. If necessary, additional waivers will be considered up to CDR. This information shall be available to the government and discussed at IPT meetings as well as major reviews IAW the government provided IMP (ref. Attachment 0005).

C.7.2 Cybersecurity

C.7.2.1 Cybersecurity Implementation Plan

The contractor shall develop and implement a Cybersecurity Implementation Plan as part of their SEMP (ref. CDRL A009) that addresses the Contractors Software Development, Software Assurance, Hardware Validation, Supply Chain Risk Management, Testing (Architecture and Configuration), Product Certifications (IA and IA enabled, cryptographic), Vulnerability Management, Patch Management, Release Management and Configuration Management efforts for the CRS(I) System.

C.7.2.1.1 Data Protection

The contractor shall establish administrative, technical, and physical safeguards to protect all government data, to ensure the confidentiality, integrity, and availability of government data in accordance with Department of Defense Instruction (DoDI) 8582.01 Security of Unclassified DoD Information on Non-DoD Information Systems. The contractor shall encrypt all unclassified CRS(I) data (including Controlled Unclassified Information (CUI) and For Official Use Only (FOUO)) stored electronically using Federal Information Processing Standard (FIPS) 140-2 validated encryption, IAW DoDI 8582.01 and the Security Classification Guide (ref. Attachment 0006).

C.7.2.1.2 Cybersecurity Policies

The contractor shall comply with Cybersecurity requirements in accordance with DoDI 8510.01 Risk Management Framework (RMF) for DoD Information Technology (IT), DoD 8500.01 Cybersecurity, NIST SP 800-37 Guide for Applying the Risk Management Framework to Federal Information Systems: A Security Lifecycle Approach, NIST SP 800-53 Recommended Security Controls for Federal Information Systems and Organizations, Chairman of the Joint Chiefs of Staff Manual (CJCSM) 6510.01IA, Chairman of the Joint Chiefs of Staff Instruction (CJCSI) 6212.01E Interoperability and Supportability of Information Technology and National Security Systems, DoD 5220.22-M National Industrial Security Program Operating Manual (NISPOM), DoDI 8551.1 Ports, Protocols and Services Management (PPSM), AR 380-5 Department of The Army Information Security Program, and AR 25-2, Information Assurance.

C.7.2.1.3 External Certification Authority (ECA) In order to access the government information systems, such as the RMF Knowledge service and VDLS, the contractor shall have or obtain an AKO account. An External Certificate Authority (ECA), a DoD Common Access Card (CAC) or Federal Bridge Certificate Authority (FBCA) is required for all personnel requiring access to government information systems. The contractor shall work with PdM UGV and the government Information Systems Security Manager (ISSM) in order to obtain and implement usage of the ECA and CAC program in compliance with DoD Directive 8190.3 Smart Card Technology, and DoD Instruction 8520.2, Public Key Infrastructure (PKI) and Public Key (PK) Enabling. Contractors can find details on the ECA program and find authorized ECA vendors at http://iase.disa.mil/pki/eca/ and the Federated bridge program at http://iase.disa.mil/pki-pke/interoperability/Pages/index.aspx.

C.7.2.1.4 Cyberspace Workforce Training The contractor shall provide cybersecurity support for all tasks identified in Section C.7 in accordance with Department of Defense Directive (DoDD) 8140.01 Cyberspace Workforce Management. This support shall include compliance with training requirements and certifications for Information Assurance Technical (IAT) Level III.

The contractor shall further ensure that all personnel assigned with cybersecurity roles and functions are identified and have all necessary certifications and completed background checks. The contractor shall make this information available to the government upon request. Current DoD Approved 8140 Baseline Certifications can be found at: http://iase.disa.mil/iawip/Pages/iabaseline.aspx.

C.7.2.1.5 Cybersecurity Annual Training

Contractor personnel with access to government Information Systems are required to have annual DoD Cyber Awareness Training (https://ia.signal.army.mil/DoDiaa/) and a favorable National Agency Check with Inquiries (NACI) per Army Regulation (AR) 25-2 to access the CRS(I) IDE.

C.7.2.1.6 Use of Army BBPs, DISA SRGs and STIGs

The contractor shall use the Army Best Business Practices (BBPs) (https://login.milsuite.mil/?goto=https%3A%2F%2Fwww.milsuite.mil%3A443%2Fwiki%2FPortal%3AArmy_Information_Assurance), Defense Information Systems Agency (DISA), Security Readiness Guides (SRGs), and Security Technical Implementation Guides (STIGs) to define specific standards, measures, practices, or procedures necessary to meet Cybersecurity requirements in support of AR 25-2 Information Assurance. DISA STIGs are located at http://iase.disa.mil/stigs/Pages/index.aspx.

C.7.2.2 Cybersecurity Accreditation Artifact Package

The contractor shall provide a Cybersecurity Accreditation Artifact Package (ref. CDRL A024). The information shall be available to the government and discussed at IPT meetings and technical reviews.

C.7.2.3 Systems Integration Lab (SIL)

The contractor shall develop and use a SIL to integrate and test the CRS(I) System. The SIL(s) shall contain all CRS(I) System production-intent electrical and electronic components (modules, displays, controls, clusters, cabling and harnesses) and GFE electronic hardware and software to enable the replication of fully integrated vehicles.