J1_DO1-S.PDF

Attachment J.2

STATEMENT OF WORK

SECTION C – DESCRIPTION/SPECIFICATION/WORK STATEMENT

C1. BACKGROUND

This Delivery Order requires the development and delivery of hand-held biometric hardware device high fidelity prototypes for the Identity Dominance System (IDS) program in accordance with the Contractor’s design as approved by the Government. The hand-held hardware device resulting from this effort will be used to biometrically enroll, verify, and identify individuals during Government testing in the same way as the current IDS integrated base unit (IBU). This effort will require an experienced Contractor to design, build, and deliver mature high-fidelity prototype hand-held hardware devices. Government-owned, Government-developed software will be integrated onto each of these prototypes. To enable this, the Contractor shall work with the Government software team throughout the period of this Delivery Order.

C2. SCOPE

The primary purpose of this SOW is to develop the hand-held hardware device and to design the associated hardware kit. The Government will work with the Contractor to load software version(s) onto the hardware platform(s). The Contractor shall coordinate with the Government software development team, especially during development and testing efforts.

Software for the hand-held hardware device will be developed by the Government for Android operating systems. This SOW does not include software development by the Contractor and the

Government will serve as lead software integrator during the period of this Delivery Order.

Hardware devices are expected to be modifications of commercial off-the-shelf (COTS) system designs, so development work to achieve the necessary hardware modifications is included in this SOW. Upon notice from the Contracting Officer Representative (COR), the Contractor shall build and deliver IDS hardware in accordance with (IAW) Government-approved designs.

C3. APPLICABLE DOCUMENTS

Applicable standards, practices, and procedures include the following:

IAFIS-DOC-01078-7.1, Electronic Fingerprint Transmission Specification, Federal

Bureau of Investigation (https://www.fbibiospecs.cjis.gov/)

DoD Electronic Biometric Transmission Specification v4.0 (DFBA-STD-EBTS-15-001)

(http://www.dfba.mil/References/Standards.aspx)

ISO 12234 Electronic still-picture imaging (https://www.iso.org/standard/29377.html)

Special Publication (NIST SP) 800-88 Rev. 1, Guidelines for Media Sanitization

(https://www.nist.gov/publications/nist-special-publication-800-88-revision-1-guidelines-media-sanitization)

ANSI C84.1 Electric Power Systems and Equipment – Voltage Ranges

(http://www.nema.org/Standards/pages/default.aspx)

MIL-STD-464, Electromagnetic Environmental Effects, Requirements for Systems

(http://everyspec.com/MIL-STD/) http://www.nema.org/Standards/pages/default.aspx

MIL-STD-461, Requirements for the Control of Electromagnetic Interference

Characteristics of Subsystems and Equipment (http://everyspec.com/MIL-STD/)

MIL-STD-1472, DoD Design Criteria Standard: Human Engineering

(http://everyspec.com/MIL-STD/)

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

(http://everyspec.com/MIL-STD/)

MIL-STD-2073-1E Department of Defense Standard Practice for Military Packaging

(http://everyspec.com/MIL-STD/)

MIL-STD-810G CHG-1, Environmental Engineering Considerations and Laboratory

Tests (http://everyspec.com/MIL-STD/)

MIL-STD-882E Department of Defense Standard Practice: System Safety

(http://everyspec.com/MIL-STD/)

MIL-STD-881C Department of Defense Standard: Work Breakdown Structures (WBS) for Defense Materiel Items (http://everyspec.com/MIL-STD/)

Army Regulation (AR) 70-38, Research, Development, Test and Evaluation of Materiel for Extreme Climatic Conditions (http://everyspec.com/ARMY/AR-Army-Regulation/)

Naval Sea Systems Command Instruction (NAVSEAINST) 9310.1C, Navy Lithium

Battery Safety

(https://dap.dau.mil/policy/Lists/Policy%20Documents/DispForm.aspx?ID=1879)

NAVSEA Technical (TECH) Manual (MAN) S9310-AQ-SAF-010, Technical Manual for Batteries, Navy Lithium Safety Program Responsibilities and Procedures

(http://everyspec.com/USN/NAVSEA/)

Title 49 Code of Federal Regulations Part 173 (https://www.ecfr.gov)

Also, copies of Government specifications, standards, handbooks and guidance data may be obtained from ASSIST website managed by the Defense Logistics Agency (DLA) Document

Services available at https://assist.dla.mil/online/start/.

Drawings shall be IAW American National Standards Institute (ANSI) / American Society of

Mechanical Engineers (ASME) applicable standards and practices.

http://everyspec.com/MIL-STD/ https://dap.dau.mil/policy/Lists/Policy%20Documents/DispForm.aspx?ID=1879 http://everyspec.com/USN/NAVSEA/ https://www.ecfr.gov/ https://assist.dla.mil/online/start/

C4. REQUIREMENTS

C4.1. Project Management Activities (Firm Fixed Price (FFP))

C4.1.1. The Contractor shall designate one individual with whom the Government will interface for management and reporting. Contact information shall be provided via E-mail to the Contracting Officer’s Representative (COR) within five (5) calendar days of this Delivery

Order award date.

C4.1.2. The Contractor shall designate appropriate individual(s) as technical representatives with whom the Government software development and systems engineering teams will interface. Contact information shall be provided via E-mail to the IDS Lead

Systems Engineer (LSE) within five (5) calendar days of this Delivery Order award date.

C4.2. Hand-held Hardware Device Design (Firm Fixed Price (FFP))

C4.2.1. The Contractor shall design and develop a hand-held hardware device to be hardware refresh to the current IDS IBU in accordance with (IAW) this SOW including

Exhibit B.

C4.2.2. The hand-held hardware device shall be designed and built to support an Android

Operating System (OS). All delivered hand-held hardware devices shall be capable of loading and running Government-developed, Government-owned software application(s) designed for Android platforms.

C4.2.4.1. The Contractor shall provide the Government software development team with a current Software Development Kit (SDK) for each biometric sensor included in the

Government-approved hand-held hardware design. Provision of the SDKs shall serve to enable the capture and templating of biometric data on each and every integrated device.

C4.2.4.2. The Contractor shall provide all product information typically available from the

SDK supplier to facilitate use of the SDK to the Government along with the SDK itself.

C4.2.3. The Contractor shall design the hand-held hardware device such that the primary computing platform with an Android operating system (OS), biometrics sensors, battery(ies), and camera(s) are integral to the device.

C4.2.4. The Contractor’s design shall meet all of the requirements listed in this section and in Exhibit B of this SOW.

C4.2.4.1. At Government discretion, a hand-held hardware device design that does not or may not meet requirements EV.01-EV.29 associated with MIL-STD-810G CHG1, MIL-

STD-464F, and MIL-STD-461G in Exhibit B may be accepted under this Delivery Order.

These requirements are related to system ruggedization/survivability. A detailed statement to this effect must be included in the design approval provided to the Contractor by the

Government as discussed in Section C4.5.

C4.2.5. The Contractor’s hardware design shall allow for use of the IDS hand-held device with standard issue gloves appearing on the Visit, Board, Search, and Seizure (VBSS)

Authorized Equipment List (AEL). One such example that IDS operators may wear are the

Camelbak MPCT05 Impact Ct Gloves. A design compatible with the Camelbak MPCT05 glove shall meet this requirement.

C4.2.6. The Contractor shall maximize the use of open architecture concepts including the employment of industry standards and the use of non-proprietary interfaces and connectors.

The Contractor is encouraged to use COTS sensors and camera(s) whenever possible.

C4.2.7. The Contractor shall design the hand-held hardware device to comply with the

Android Compatibility Definition Document (CDD) available at http://source.android.com/compatibility/overview.html

C4.2.8. The Government is responsible for IDS system compliance with Common Criteria

(CC). The IDS system will be compliant with the National Information Assurance

Partnership (NIAP)-approved Protection Profile (PP) for Mobile Device Fundamentals and the associated Department of Defense (DoD) Annex. The Contractor shall design the hardware components to facilitate such compliance. The Contractor shall not make hardware components or other selections that prevent such compliance. The PP and DoD Annex are available at https://www.niap-ccevs.org/.

C4.2.9. The Contractor shall deliver drawings of the hand-held hardware device to thoroughly describe the design to the Government. These drawings shall clearly depict and identify the layout of all sensors, exterior dimensions/footprint, and all points where the human operator is expected to physically interact with the device. The Contractor shall include at least one 3-dimensional (3-D) view to clearly show form factor and sensor layout.

(CDL A003)

C4.3. Hardware Kit Design (Firm Fixed Price (FFP))

C4.3.1. The Contractor shall design a consolidated hardware kit for IDS. The kit shall provide protection for the hand-held hardware device and take into account operator convenience.

C4.3.2. At a minimum, the kit shall include the hand-held hardware device, rechargeable batteries, power cords, necessary connectors, ancillary equipment, any peripherals, storage media, operator and maintenance manuals, quick reference sheets, maintenance/cleaning items, and a reusable container (case) for hardened packaging including necessary inserts to prevent damage to the kit contents. All items listed shall fit inside the case at the same time.

C4.3.3. The kit design shall include a reusable container (case) that must protect the hand-held hardware device and other kit components during shipping and transport over air, land, and sea. The case shall be reusable and serve as both the storage and shipping container.

C4.3.4. The kit shall maintain protection of the hand-held hardware device and other kit components during storage on land or at sea from -28 o F to 160 o F.

C4.3.5. The kit shall be packaged in a Level A pack IAW MIL-STD-2073-1E. For packaging of hazardous materials (HAZMAT), 49 CFR Part 173 shall be applied. All containers must comply with NAVSEAINST 9310.1C and TECHMAN S9310-AQ-SAF-010 if lithium batteries are included.

http://source.android.com/compatibility/overview.html https://www.niap-ccevs.org/

C4.3.6. The kit, including the case and all components inside it, shall weigh 30 lbs or less and be no larger than 21 inches x 17 inches x 9 inches.

C4.3.7. The kit itself shall be clearly labeled and components physically separated to minimize operator confusion. The kit shall include an inventory sheet and layout depiction, both protected from damage by liquids.

C4.3.8. The Contractor shall deliver drawings of the kit design to the Government. These drawings shall clearly depict and identify the layout, interior dimensions, and exterior dimensions/footprint. The Contractor shall include at least one 3-dimensional (3-D) view to clearly show how all the components fit inside the case. (CDRL A003)

C4.4. Technical Interchange Meeting (TIM) #1 (Firm Fixed Price (FFP))

C4.4.1. TIM #1 shall be held in person at the Contractor’s facility within 10 business days of the award of this Delivery Order. The Government will provide a teleconference line for remote attendees. TIM #1 may be coupled with a Contract Kick-Off meeting at the

Government’s discretion and the Government may elect to conduct this meeting remotely and entirely over the telephone.

C4.4.2. At TIM #1, the Contractor shall provide a presentation slide set (CDRL A036) of the proposed design for the hand-held hardware device IAW this SOW. The designs of the hand-held hardware device presented to the Government shall meet the requirements of

Section C4.2 of this SOW. The presentation at TIM#1 shall include the following content:

C4.4.2.1. Drawings as described in this SOW Sections C4.2.9 and C4.3.8. (CDRL

A003)

C4.4.2.2. A matrix of the requirements of Section C4.2 including Exhibit B including a description of how the Contractor’s design meets the requirements.

C4.4.2.3. Review of the scope of development work, manufacturing processes, and manufacturing readiness to deliver the hand-held device.

C4.4.2.4. Top-level discussion of the ruggedization and environmental survivability aspects of the proposed design with respect to MIL-STD-810G CHG1, MIL-STD-

464C, and MIL-STD-461G.

C4.4.2.5. Initial schedule including all tasks in this SOW and highlighting major milestones/deliveries.

C4.4.3. The Contractor shall provide a technical report detailing the discussions held and to supplement the information presented at TIM #1 no more than 15 working days after

TIM#1. (CDRL A004)

C4.5. Technical Interchange Meeting (TIM) #2 (Firm Fixed Price (FFP))

C4.5.1. TIM #2 shall be held at the Contractor’s facility approximately 80 business days after TIM #1. The Government will provide a teleconference line for remote attendees. The

Government will set the actual date of TIM #2 in coordination with the Contractor.

C4.5.2. At TIM#2, the Contractor shall request Government approval of their design for the hand-held hardware device and the kit configuration to be delivered under this Delivery

Order. The Government must approve the Contractor’s design prior to production of mature prototype units to be used in software integration and Government testing. If approval cannot be given, a follow-on TIM (designated TIM #3) on this topic may be held at the

Government’s discretion.

C4.5.3. No fewer than 15 business days prior to the TIM#2 meeting date, the Contractor shall provide a summary slide presentation and a technical report. The technical report

(CDRL A005) shall include detailed discussion to supplement and support the slide presentation. The presentation shall facilitate the TIM#2 meeting (CDRL A036). The

Contractor shall provide the following either as part of the TIM#2 technical report or as an attachment to it:

C4.5.3.1. Updates to all items delivered at TIM#1 or an explanation as to why no updates were required. (See Section C4.4).

C4.5.3.2. Detailed discussion of any safety concerns (or the lack thereof) and the ruggedization and environmental survivability aspects of the design with respect to MIL-

STD-810G CHG1, MIL-STD-464, and MIL-STD-461. Information delivered by the

Contractor shall include steps and design considerations to ruggedize the device, anticipated tradeoffs/limitations/constraints for meeting all related requirements in Exhibit B, related testing requirements, and a summary of existing data with sources.

C4.5.3.3. Repair and maintenance considerations as related to the Contractor’s design.

This shall include discussion of expected failures, Contractor recommendations for sparing strategies, and anticipated obsolesce issues. The Contractor shall identify which components are considered replaceable. This shall be IAW the Government’s maintenance concept for

IDS and include considerations related to Section C4.9.3 of this SOW.

C4.5.3.4. Top five (5) technical risks from the Contractor’s perspective including but not limited to integration with the Government’s software and hardware obsolescence concerns and Contractor-proposed risk handling strategies (e.g risk acceptance, risk mitigation steps, etc.).

C4.5.3.5. Mature draft versions (electronic copies) of documentation included in Section

C4.8 of this SOW. The specific documents required are the Contractor’s Configuration

Management Plan (CMP), Quality Assurance Plan (QAP), Hardware Requirements

Specification (HRS), Interface Requirements Specification (IRS), Hardware Design

Description (HDD), and the Contractor Work Breakdown Structure (CWBS).

C4.5.4. The Government will iteratively review all Contractor submissions during the 15 days between submission and TIM #2. The Contractor shall respond to Government requests for edits prior to the scheduled date for TIM#2.

C4.6. Integration Support (Cost Plus Fixed Fee (CPFF))

C4.6.1. The Contractor shall work with the Government software development team throughout the period of this Delivery Order to enable software integration onto the hand-held hardware devices. Dates and location of all joint Government-Contractor software integration activities will be coordinated with the Contractor and must be mutually agreed upon.

C4.6.2. Upon request from the government, the Contractor shall work with Government team member(s) to load software application(s) onto developing hardware for informal integration testing prior to delivery of prototype hardware as discussed in Section C4.7 of this SOW. The Government will provide informal hardware-related findings and observations to the Contractor via email within 10 days of any visit.

C4.6.2.1. Government support includes monthly teleconferences and participation and two trips to the Contractor’s facility for two Government software engineers.

C4.7. Production of Prototype Hand-Held Hardware Devices (Firm Fixed Price (FFP))

C4.7.1. This task shall be executed by the Contractor only after receipt of written approval from the COR. The COR will not issue this approval without concurrence from the

Government representatives at TIM #2 from PMS-408 (SOW Section C4.5). This approval

(or notice of disapproval) will be given to the Contractor either in-person at the meeting or via email approximately five (5) business days after the meeting.

C4.7.2. The Contractor shall build and deliver five (5) mature high-fidelity prototype hand-held hardware devices to be used in Government testing within four (4) months of receipt of approval for production. These prototypes shall be built IAW the design approved by the Government.

C4.7.3. The Contractor shall test all hardware units prior to delivery to the Government.

C4.7.3.1. Contractor testing shall be governed by and IAW the Contractor’s QAP. It shall include all basic function checks possible without running the Government-owned software application(s). Delivered hand-held hardware units shall be functional and conform by inspection to the design approved by the Government.

C4.7.3.2. The Contractor shall provide a digital copy of their Quality Assurance Plan (QAP) concurrently with the other document deliverables (SOW Section C4.5). (CDRL A012)

C4.7.3.3. The Contractor shall provide detailed test reporting to the Government. The report shall include detailed results including a summary of the production acceptance test

(PAT) procedure(s) used. (CDRL A017)

C4.7.4. The Contractor shall label and mark the prototype hand-held hardware devices

IAW MIL-STD-130N and Unique Identification (UID) Construct #2 prior to delivery to the

Government.

C4.7.4.1. Each delivered hand-held hardware device shall have an item unique identifier

(IUID) label that contains both the 2D barcode and human readable text.

C4.7.4.2. At a minimum, the readable text shall consist of Military Type Designation, Part

Number, Serial Number, Contractor CAGE Code, and Contract Number. The Contractor shall register and maintain all IUID information in the IUID Registry

(http://www.acq.osd.mil/dpap/pdi/uid/data_submission_information.html)

C4.7.4.3. All labeling and markings shall be designed to be legible and permanent for the entire life of the system.

C4.7.4.4. The Contractor shall provide a tabular list providing IUID marking activity, validation and verification data to ensure labeling and markings is acceptable. (CDRL A021)

C4.8. Configuration Management (Firm Fixed Price (FFP))

C4.8.1. The Contractor shall develop, maintain, and follow a Configuration Management

Plan (CMP) describing the Contractor’s processes for controlling the configuration of hardware including hardware baselines and processes for modifying these baselines. The

Contractor shall provide the Government with a copy of their CMP. (CDRL A010)

C4.8.1.1. Modifications to the Contractor’s CMP, QAP, any other delivered Contractor plan, and any delivered hardware baseline document shall be summarized by the Contractor in a Notice of Revision (NOR) provided to the Government. (CDRL A011)

C4.8.2. The Contractor shall control the configuration of the hand-held hardware device

IAW the Contractor CMP.

C4.8.2.1. The Contractor shall participate in a joint Government/Contractor effort to designate configuration items (CI) to be managed by the Government and those to be managed by the Contractor. This shall ensure that the Contractor CMP is coordinated with the IDS Program CMP and the relevant sections of the IDS Program CMP will be provided as GFI. The Contractor shall prepare by determining recommendations for Hardware

Configuration Items (HWCI) and Hardware Components (HWCs) with descriptions and rationale for the selection of each. HWCs are sub-components of an HWCI.

C4.8.3. The Contractor shall generate and maintain baseline documentation for the hand-held hardware device and all related hardware items IAW the Contractor’s CMP. The

Contractor shall include the kit in Section C4.3 as a part of the hardware product baseline.

C4.8.3.1. The Contractor shall provide a Product Baseline Index (PBLI) showing the current listing of documentation included in the baseline for all CIs managed by the

Contractor. The PBLI shall include the documents listed in C4.8.3.2 through C4.8.3.7 at a minimum. (CDRL A007)

C4.8.3.2. The Contractor shall list in the PBLI and provide a Hardware Requirements

Specification (HRS). The HRS shall list the requirements traceable to Hardware

Configuration Items (HWCIs) and Hardware Components (HWCs). The HRS shall include requirements to the derived technical level with traceability to Exhibit B (Section C4.2) and recommended verification method (test, demonstration, inspection, or analysis). (CDRL

A009)

C4.8.3.3. The Contractor shall list in the PBLI a Hardware Design Description (HDD). The

HDD shall describe the design and architecture of the handheld hardware device including all http://www.acq.osd.mil/dpap/pdi/uid/data_submission_information.html

HWCIs, HWCs, and interfaces. Included in the HDD shall be list of HWCIs and HWCs delivered in a top-down breakout format. (CDRL A014)

C4.8.3.4. The Contractor shall list in the PBLI and provide an Interface Requirements

Specification (IRS). The IRS shall list the requirements for critical interfaces traceable to

HWCIs. The IRS shall include requirements to the derived technical level with traceability to Exhibit B (Section C4.2) and recommended verification method (test, demonstration, inspection, or analysis). (CDRL A008)

C4.8.3.5. The Contractor shall list in the PBLI and provide a Hardware Operations &

Maintenance (O&M) Manual. See Section C4.9.2 of this SOW for details regarding the content of the O&M Manual. (CDRL A013)

C4.8.3.6. HWCIs and HWCs shall be included in a Contractor Work Breakdown Structure

(CWBS) developed IAW MIL-STD-881C. The Contractor shall provide the CWBS to the

Government. (CDRL A001)

C4.8.3.7. The Contractor shall list in the PBLI and provide a drawing package including up-to-date drawings from Sections C4.2.9 and C4.3.8 of this SOW. The drawing package shall include dimensions, connections, part numbers of HWCIs and HWCs, descriptions, and color pictures of the hand held hardware device and the kit. (CDRL A003)

C4.8.4. The Contractor shall establish a configuration status accounting (CSA) database that records and maintains the hardware configuration baseline documents. Digital copies of all current and historical versions of baseline documents generated or maintained by the

Contractor shall be made available to the Government upon request.

C4.8.5. The CSA database shall also record the serial numbers and license numbers for all non-consumable items and Software Development Kits (SDK) delivered to the Government.

C4.8.5.1. For any HWCI identified for Government control, the Contractor shall provide form, fit, function, and interface documentation necessary for CSA.

C4.8.6. Using the CSA database, the Contractor shall maintain information that allows traceability of vendor assigned serial numbers for all HWCIs and HWCs to the relevant

IUID. As an example, the vendor serial numbers of sensors integrated into a hand-held hardware device should be traceable to the IUID of the hand-held hardware device end product. The Contractor’s CSA database shall include the following hardware related data elements at a minimum:

Date of entry

USN serial number or IUID (as applicable)

Vendor part number/CAGE code

Vendor serial or license number

Serialized part nomenclature

Date installed (for components)

Relevant testing results or references (as applicable)

HAZMAT designation or considerations (as applicable)

C4.8.7. The Contractor shall provide a complete electronic accounting to the Government of each delivered hand-held hardware device IAW the Contractor’s CSA database. (CDRL

A020)

C4.9. Life Cycle Sustainment and Support (Firm Fixed Price (FFP))

C4.9.1. The Contractor shall perform, document, and provide to the Government the outcome of a Systems Hazard Analysis (SHA) to identify hazards and mitigation measures in the integrated system design including subsystems and human interfaces IAW Task 205 of

MIL-STD-882E. Specifically considered shall be human health hazards as determined through a Health Hazard Analysis (HHA) focused on but not limited to physical and ergonomic hazards IAW Task 207 of MIL-STD-882E. (CDRL A016)

C4.9.2. The Contractor shall provide an Operator’s and Maintenance Manual (O&M

Manual) for the hardware using MIL-PRF-32216A as guidance. The Government may incorporate this information into one or more IDS instruction manuals and training aides.

(CDRL A013)

C4.9.2.1. The O&M Manual at a minimum shall include Introduction, Preparation for use and installation, Principles of Operation, Maintenance and Servicing Instructions (preventive and corrective), Preparation for Shipment, Parts List, Operational and Maintenance

Illustrations, Safety Precautions (Warnings, Cautions, and Notes) and information on the functionality of the hand-held hardware device, its components/accessories including all contents in the kit, system operation from turn-on to system shut down including adjustments, and operator checks and services.

C4.9.2.2. The Contractor is not expected to include information related to the Government-developed software applications in the O&M Manual.

C4.9.2.3. The Contractor shall ensure all validated procedures work as written to accomplish the task described.

C4.9.2.4. The Contractor shall correct any non-workable procedures provided by the

Contractor within 2 weeks after notification by the Government of the non-workable procedure.

C4.9.3. The Contractor shall provide a Provisioning Parts List (PPL) to the Government.

The PPL must include all the parts that can be removed and replaced at the Operational-

Level (O-Level) and the In-Service Engineering Agent (ISEA) level. Examples (for illustrative purposes only) are a battery at the O-Level and the sensors or the primary computing platform in a hand-held hardware device at the ISEA level. (CDRL A030)

C4.9.3.1. The PPL shall be delivered in a top-down breakdown format and shall include replacement parts and long lead time items required to support repairs. Each item on the PPL that is repairable at either the O-level or ISEA level shall be priced and available for ordering.

C4.9.3.2. At a minimum, the PPL shall contain the part number, nomenclature, CAGE, Quantity and unit price. The PPL shall include the recommended spares based upon failure analysis to support a 12-month sparing philosophy.

C4.9.4. The Contractor shall develop, maintain, and follow a Diminishing Manufacturing

Sources and Material Shortages (DMSMS) plan describing the Contractor’s processes for handling hardware obsolescence. The Contractor shall provide a copy of their DMSMS plan to the Government. (CDRL A031).

C5. Period of Performance

The period of performance is ten (10) months after award.

C6. Travel No Contractor travel is anticipated to support this Delivery Order.

C7. Security Work performed under this Delivery Order is unclassified.