N0017818R4017_REV2.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

To update question and answ er section Ddl-L40, J.2 delivery order action sheet, J.1 D.O. 0001 SOW, factor 1 and factor 4. Changes are show n in bold lettering. This action is also extending the closing date from 25 April 2018 to 02 May 2018.

1. CONTRACT ID CODE PAGE OF PAGES

1 36

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 19-Apr-2018

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N0017818R4017

X 9B. DATED (SEE ITEM 11)

01-Mar-2018

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer X is extended, is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

20-Apr-2018

CODE

NSWCDD 1

ATTN: CARMELL BEARD/024 CARMELL.BEARD@NAVY.MI

HLGREN RD..

DAHLGREN VA 22448

N00178 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N0017818R4017

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 25-Apr-2018 12:00 PM to 02-May-2018 12:00 PM.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF WORK

C.1 BACKGROUND

The Naval Surface Warfare Center Dahlgren Division (NSWCDD), Asymmetric Systems Division (H10) has a requirement to support a planned technology refresh for the Identity Dominance System (IDS) program. The IDS program is an Acquisition Category (ACAT) IV-T program of record (POR) currently in sustainment managed by

Naval Sea Systems Command (NAVSEA) PMS 408 and sponsored by OPNAV N96C4. The IDS program provides a means to collect and process identity information in the conduct of maritime and expeditionary operations. There are two key aspects of this capability: 1) enable forces to rapidly establish and verify the identity information of unknown individuals encountered during operations and 2) improve force capacity to update, manage, and share trusted information on such individuals. The fundamental purpose of the IDS program is to provide and sustain a materiel solution with both hardware and software components for a multi-modal biometric capability which collects, matches, stores, and shares biometric data of individuals. The current configuration of IDS includes a hand-held integrated base unit (IBU), a laptop, peripherals and ancillary equipment such as digital media and ten-print collection devices, and software applications. The IBU is primarily used for enrollments and the return of matching results against local watchlist(s) and databases. The laptop-based components may also be used for enrollments but are the primary node for ingesting and sharing collected biometrics and contextual data as well as the development and management of watchlists and access lists. IDS shall adhere to applicable technical standards and policies to include the Department of Defense (DoD) Electronic Biometric Transmission Specification (EBTS), the Privacy Act of 1974 (5 U.S.C. § 552a), cybersecurity and information assurance policy, and network accreditation requirements.

The IDS technology refresh effort is a refresh of the entire current configuration. However, the primary focus of this contract is the acquisition of a hand-held biometric hardware device for the IDS program to replace the current IBU.

The hand-held hardware device resulting from this effort will be used to biometrically enroll, verify, and identify individuals.

C.2 SCOPE

The purpose of this Statement of Work (SOW) is to refresh and support IDS technology through its intended life cycle under the current POR. At a minimum, the Contractor shall be responsible for the hardware components of the IDS system including required drivers, firmware, operating system, and native power management associated with the hardware platform. Software for IDS hand-held hardware devices will be designed for Android operating systems. Software may be developed by the Government team or by the Contractor as specified in individual

Delivery Orders. In the case of Government software development, the Government will work with the Contractor to load software version(s) onto the hardware platform(s) to some extent throughout the period of this contract. To facilitate this, the Contractor shall coordinate with the Government software development team, especially during development and testing efforts. Hardware devices and any software applications developed by the Contractor for

IDS are expected to be modifications of commercial off-the-shelf (COTS) system designs. Upon approval by the

Government to enter production, the Contractor shall kit, package, and deliver IDS hardware in accordance with

(IAW) Government-approved design(s) per Individual Delivery Orders. The Contractor shall deliver end products to the Technical Direction Agent (TDA), the ISEA, or other Government representatives as directed in individual

Delivery Orders. After all development and testing efforts are complete, Government-developed software will be loaded onto final configuration production hardware units and delivered to the end operators by the Government In-

Service Engineering Agent (ISEA) for the IDS Program. Any software developed by the Government will be

Government-owned and the Contractor shall have no rights to it.

C.3 APPLICABLE DOCUMENTS

Specific versions of standards, handbooks, and applicable interface documentation will be articulated in individual

Delivery Orders for the respective deliverables. 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/. Otherwise, documents will be available from the links provided in individual Delivery Orders or provided as Government Furnished Information (GFI).

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

Mechanical Engineers (ASME) applicable standards and practices. Any specific tailoring guidance will be provided in individual Delivery Orders.

C.4 REQUIREMENTS

C.4.1 Project Management Activities (Firm-Fixed-Price)

The Contractor shall be responsible for overseeing the design, development, production and engineering processes as defined by Contractor management plans. Work shall be conducted IAW this SOW and the specifics provided in individual Delivery Orders.

The Contractor shall organize, coordinate, and control all activities, including those assigned to subcontractors, to ensure the correct and timely delivery of all supplies and services.

The Contractor shall identify the individuals with whom the Government will interface in order to coordinate the management and technical activities.

The Contractor shall maintain and report on a contract work breakdown structure (CWBS) IAW the IDS program

Work Breakdown Structure (WBS) provided as Government furnished Information (GFI). (CDRL A001)

The Contractor shall maintain and report on an integrated master schedule (IMS) to identify and assess progress on all tasks. (CDRL A002)

C.4.2 IDS Design, Development, and Testing (Firm-Fixed-Price)

The Contractor shall design, develop, and test components of IDS. (CDRLs A003, A004, A005)

The Contractor shall design consolidated kit(s) for IDS hardware. The kit(s) shall be clearly labeled, provide protection for the hardware components, and take into account operator convenience.

The Contractor shall work with the Government engineering team and the Government software development team throughout the period of this contract. This shall include developing software to be integrated onto the hardware devices and minimizing technical risk as detailed in individual Delivery Orders.

The Contractor shall provide Software Development Kits (SDK) for sensors and matching algorithms.

The Contractor shall participate in the Government’s testing events. (CDRL A006)

The Contractor shall control the configuration and quality of components and systems delivered to the Government as required to implement and sustain IDS during and after technology refresh throughout the period of this contract.

The Contractor shall utilize quality control measures and quality assurance measures as part of a Quality

Management System (QMS) to ensure the quality of all hardware and production processes including inspection and test per a Contractor Quality Assurance Plan (QAP). (CDRLs A007, A008, A009, A010, A011, A012, A013, A014) https://assist.dla.mil/online/start/

The Contractor shall manage and communicate risk to the Government as a part of monthly reporting. This shall be

IAW the IDS Program Risk Management Plan (RMP) provided as GFI.

The Contractor shall provide technical support to the Government to evaluate issues occurring during testing, fielding, and operation of IDS devices. Support shall be onsite or via telephone during normal business hours.

Specifics will be included in individual Delivery Orders. (CDRL A015)

The Contractor shall minimize the use of hazardous materials (HAZMAT) to the highest extent possible.

In design and production of systems, the Contractor shall strictly adhere to Federal Occupational Safety and Health

Agency (OSHA) Regulations, Environmental Safety and Occupational Health (ESOH) requirements in Department of Defense Directive (DoDD) 5000.01 and in Department of Defense Instruction (DoDI) 5000.02, Environmental

Protection Agency (EPA) Regulations, and all applicable state and local laws, regulations, and policies. The

Contractor shall provide safety assessments of IDS hardware systems in various stages of system maturity throughout the period of this contract. (A016)

C.4.3 Production of Hardware Devices (Firm Fixed Price)

The Contractor shall produce and deliver IDS hardware components IAW individual Delivery Orders.

The Contractor shall deliver mature high-fidelity prototype multi-modal integrated biometric hand-held hardware devices.

The Contractor shall deliver First Article production representative multi-modal integrated biometric hand-held hardware devices.

The Contractor shall deliver final baselined configuration multi-modal integrated biometric hand-held hardware devices produced via a proven production process.

The Contractor shall assemble and deliver to the Government necessary equipment for the hardware refresh and sustainment IDS in addition to the hand-held hardware devices. This may include COTS computing devices (e.g.

laptops), storage media, peripheral biometric sensors, cameras, connectors, ancillary equipment, and supplies.

The Contractor shall test units prior to delivery to the Government to ensure that all systems from the production period conform to all of the requirements of this contract and individual Delivery Orders. The Contractor shall test

IAW a production acceptance test (PAT) plan included as a part of the Contractor's Quality Assurance Plan (QAP).

The Contractor shall provide results to the Government. For each item that fails during the PAT, the Contractor shall provide a failure analysis report. (CDRLs A012, A017, A018, A019)

The Contractor shall maintain the baseline and information for all non-consumable parts and systems delivered to the Government. The Contractor shall provide information for traceability and configuration status accounting

(CSA). (CDRLs A020, A021)

If requested by the Government, the Contractor shall develop software applications to be installed on hardware devices produced under this contract to collect, match, store, and share biometrics information IAW individual

Delivery Orders. (CDRLs A022, A023, A024, A025, A026)

C.4.4 Life Cycle Sustainment and Support (Firm-Fixed-Price)

The Contractor shall support the TDA and the ISEA in overseeing the technical maintenance of the system including the development of instruction manuals and training aides. (CDRLs A013, A027)

The Contractor shall provide a warranty for the hand-held hardware device to cover defects discovered within 1 year of delivery not including damage caused by the Government. The Contractor shall repair or replace the defective item under warranty coverage at the Contractor’s expense. The Contractor shall participate in integrated logistics and maintenance planning in coordination with the IDS Program TDA and ISEA throughout the period of this contract. (CDRLs A028, A029, A018)

The Government will maintain IDS under a three level concept: Contractor repair, ISEA level repair, and

Operational level (O-level) repair. The Government is responsible for ISEA level and O-level repair. The Contractor shall be responsible for Contractor repair level under C.4.5 of this SOW.

O-Level and ISEA level repair actions will be limited to those components identified by the Contractor in the

Provisioning Parts List (PPL). The Government performing O-level repair and replace actions shall not nullify existing warranties. (CDRL A030)

The Contractor shall furnish for delivery to the ISEA spare and repair parts as set forth in the PPL. Failure by the

Contractor to specific spare part determinations on the PPL for individual items does not preclude the Government from requiring the Contractor to update the PPL with additional components. The Government may issue Delivery

Orders for spare and replacement parts throughout the life of the contract. (CDRL A030)

The Contractor shall develop, maintain, and follow a Diminishing Manufacturing Sources and Material Shortages

(DMSMS) plan. (CDRL A031) Once the DMSMS plan is approved, the Contractor shall communicate DMSMS issues and anticipated issues to the Government (CDRL A028). To support logistics, supply chain, and DMSMS management, the Contractor shall provide a Bill of Materials (BOM) for hardware delivered under this contract.

(A032)

C.4.5 Repair (Cost-Plus-Fixed-Fee)

The Contractor shall have a mechanism in place to collect, analyze, and report on problems and failures and shall implement an effective cause and corrective action system. Failure data shall be isolated to the lowest replaceable unit (LRU) assembly or component. The Contractor shall provide a Failure Summary Analysis Report for each system repaired or replaced under warranty and non-warranty repairs. (CDRLs A028, A018)

Warranty Repairs - The Contractor shall receive, inspect, test, and perform failure analysis and isolate each hardware device as necessary to determine the specific work required to restore it to a serviceable condition. The

Contractor shall perform and report the results of a screening-level failure analysis to determine whether the repair falls under warranty within ten (10) calendar days after receipt of the failed device(s). Disassembly of the hardware device shall be limited to the minimum extent possible. Repair turnaround time shall not exceed fourteen (14) calendar days after receipt of determination of whether the repair falls under warranty. All failures returned to the

Contractor for repair will have a Return Material Authorization (RMA) number assigned by the Contractor. The

Contractor shall ship all repaired hardware devices to the ISEA for acceptance at the Contractor’s expense. (CDRL

A033)

Non-Warranty Repairs - The Contractor shall receive, inspect, test, and perform failure analysis and isolate each hardware device as necessary to determine the specific work required to restore it to a serviceable condition. The

Contractor shall repair the hardware that does not exceed fifty-percent (50%) of the replacement cost to the latest approved configuration. The Contractor shall perform failure analysis and submit a detailed cost proposal with direct and indirect cost, rates, and labor categories and hours to the Contracting Officer within ten (10) calendar days after receipt of the failed device(s) prior to commencement of work for any non-warranty repairs. Cost proposals submitted for work to be performed shall include all cost associated for evaluation and repair, itemized listing of parts required for those repairs, and timeframe required for the repair. The Contractor shall not perform any non-warranty repair on the failed device until receipt of the Delivery Order. Disassembly of the hardware device shall be limited to the minimum extent possible. If a unit has failed beyond economical repair, the Government may choose to replace the unit at its discretion. All failures returned to the Contractor for repair will have a Return Material

Authorization (RMA) number assigned by the Contractor. The Contractor shall ship all repaired hardware devices to the ISEA for acceptance. All non-warranty repairs performed on the hardware device by the Contractor shall be warranted for a minimum of 120 calendar days. This does not exclude any existing warranty remaining. (CDRL

A034)

C.4.6 Integration Support (Cost-Plus-Fixed-Fee)

The Contractor shall work with the Government engineering team and the Government software development team throughout the period of this contract to integrate Government-developed software onto hardware devices.

C.4.7 Delivery Order Management

For each Delivery Order, the Contractor shall deliver a Monthly Report, Contractor Work Breakdown Structure

(CWBS), and Integrated Master Schedule (IMS) (CDRLs A001, A002, A035)

The Contractor shall participate in both formal and informal In-Progress Reviews (IPRs) of work performed. The

Government may schedule formal reviews in Government spaces. At the time the review is scheduled, the

Government shall communicate the specific purpose of the review. (CDRL A036)

The Contractor shall participate in periodic Task Prioritization Meetings (with the COR and Subject Matter Experts

(SMEs). The purpose of these meetings is to convey the Government’s technical program schedules and priorities and to identify corresponding task priorities for this contract. (CDRL A036)

The Contractor shall participate in focused Technical Interchange Meetings (TIM). The Government shall communicate the specific purpose of each TIM at the time it is scheduled. TIMs may be held onsite at Contractor facilities, at Government facilities, or via telephone. (CDRL A036)

The Contractor shall document the minutes for IPRs, Task Prioritization meetings, TIMS, or other meetings at the

Government’s request. (CDRL A037)

C.5 OTHER DIRECT COSTS

C.5.1 Travel

The Contractor shall be required to travel in performance of this contract. The numbers of trips and types of personnel traveling shall be limited to the minimum required to accomplish work requirements and shall be coordinated with the COR. Travel to the following locations is anticipated: Washington DC metropolitan area including Washington DC; the TDA location (Dahlgren, Virginia); Fredericksburg, Virginia; Norfolk, Virginia and surrounding area; and the ISEA location (Crane, Indiana). Specific travel requirements will be specified in individual Delivery Orders.

C.6 GOVERNMENT FURNISHED EQUIPMENT, INFORMATION, AND MATERIALS

C.6.1 Government Furnished Materials

The Government will provide all GFI listed in this SOW upon award of the contract. Each DO issued by the

Government will specify and describe the Government furnished equipment, information, data, documentation, and facilities.

C.7 MANDATORY REQUIREMENT

The mandatory requirement must be maintained throughout the life of the Task Order. The mandatory requirement is as follows:

Requirement 1: Facility location

The Offeror’s primary facility must be located within the Continental United States of America (CONUS).

C.8 SECURITY

C.8.1 Information Security

Work performed under this contract shall be Unclassified. Personnel providing direct support to this effort will not be required to have a DoD clearance. Much of the IDS program information is considered Controlled Unclassified

Information (CUI). This is information that although unclassified is subject to access or distribution limitations in accordance with statute or regulation. Included is information exempt from mandatory release to the public under the Freedom of Information Act, or information that is subject to export control. The Contractor shall be appropriately trained and equipped to handle CUI.

C.8.2 Portable Electronic Devices (PEDs)

Non-government and/or personally owned portable electronic devices (PEDs) are prohibited in all NSWCDD buildings with the exception of personally owned cell phones which are authorized for use in spaces up to and including Controlled Access Areas. The Contractor shall ensure the onsite personnel remain compliant with this

PED policy. NSWCDD instruction defines PEDs as the following: any electronic device designed to be easily transported, with the capability to store, record, receive or transmit text, images, video, or audio data in any format via any transmission medium. PEDs include, but are not limited to, pagers, laptops, radios, compact discs and cassette players/recorders. In addition, this includes removable storage media such as flash memory, memory sticks, multimedia cards and secure digital cards, micro-drive modules, ZIP drives, ZIP disks, CD-RWs, DVD-RWs, MP3 players, iPads, digital picture frames, electronic book readers, kindle, nook, cameras, external hard dish drives, and floppy diskettes.

Personal Wearable Fitness Devices (PWFDs) marketed primarily as fitness or sleep devices are allowed in all Navy spaces where collateral non-Sensitive Compartmented Information (SCI), classified information is processed, stored, or discussed up to and including secret. User must ensure PWFD is compliant with all requirements in

NAVADMIN 216/15, Cyber Hygiene Authorization to use Personal Wearable Fitness Devices (e.g., FitBit, Jawbone

UP, etc.) in Navy Spaces, dated 14 September 2015 and register PWFD in the NSWCDD Fitness Device Tracker.

PEDs belonging to an external organization shall not be connected to NSWCDD networks or infrastructure without prior approval from the NSWCDD Information Assurance and Compliance Branch. This approval will be granted using the TARIS form and action tracker process.

Personally owned hardware or software shall not be connected or introduced to any NSWCDD hardware, network or information system infrastructure.

C.8.3 Visits by Foreign Nationals and Foreign Representatives

Contract performance may require that the Contractor host, at an off-base location, foreign nationals and/or foreign representatives. A foreign national is a person who is a citizen of a foreign nation, and who is not a citizen of the

United States. A foreign representative is a person who represents a foreign interest in dealings with the U.S.

Government, either directly or through dealings with a U.S. Government contractor. A foreign representative may be a United States citizen.

A Contractor-hosted visit of a foreign national or foreign representative may be either an “official” visit or an

“unofficial” visit. An official visit is a visit where the foreign national or foreign representative is representing a foreign government in an official capacity. An unofficial visit is a visit where the foreign national or foreign representative is not representing a foreign government.

A visit by a foreign national or a foreign representative may be either “DoD Sponsored” or “Non-DoD Sponsored”.

A DoD Sponsored visit is a visit that is coordinated by a DoD entity. A Non-DoD Sponsored visit is a visit that does not involve DoD coordination (A visit by either a foreign national or a foreign representative pursuant to performance by the Contractor under this contract is not considered to be, by itself, a sponsored visit).

The contractor hosting a visit by either a foreign national or a foreign representative is responsible for adherence to

Department of Defense and Department of the Navy directives, instructions, regulations, and manuals that govern foreign disclosure. “Foreign Disclosure” is defined as the disclosure of Classified Military Information (CMI) and

Controlled Unclassified Information (CUI) to foreign nationals and/or foreign representatives. Disclosure of such information may be accomplished orally, visually, in writing, or by any other medium.

Classified Military Information (CMI). This is information that is originated by or for the Department of Defense, or a Military Department, or an entity under its jurisdiction and control, and which requires protection in the interest of national security. Such information is designated as TOP SECRET, SECRET, or CONFIDENTIAL.

Controlled Unclassified Information (CUI). This is information that although unclassified is subject to access or distribution limitations in accordance with statute or regulation. Included is information exempt from mandatory release to the public under the Freedom of Information Act, or information that is subject to export control.

Naval Surface Warfare Center Dahlgren Division (NSWCDD) Foreign National Visitor and Foreign Disclosure

Application process. The NSWCDD has established a foreign national visitor approval and foreign disclosure process. Whenever, pursuant to the terms of this contract, a visit to a contractor facility or contractor workspace by a foreign national or foreign representative is anticipated, and one or more NSWCDD employees will be in attendance at this visit/meeting for the purpose of potential discussions, above the public release level, resulting in disclosure of either CMI or CUI, a completed “NSWCDD Foreign National Visitor and Foreign Disclosure

Application” e-form must be supplied to the Contractor’s Facility Security Officer (FSO). The accountable

NSWCDD personnel attending the meeting must ensure that the NSWCDD disclosure process has been complied with and an approved copy of the “NSWCDD Foreign National Visitor and Foreign Disclosure Application” generated e-form has been provided to the COR and the Contractor’s FSO. The Contractor’s FSO should ensure that approved copies of the e-form are maintained at their facility as a record of compliance with requirements set forth in the National Industrial Security Program Operating Manual (NISPOM) as well as the requirements set forth above.

C.9 ENTERPRISE-WIDE CONTRACTOR MANPOWER REPORTING APPLICATION (ECMRA)

The Contractor shall report ALL Contractor labor hours (including Subcontractor labor hours) required for performance of services provided under this contract for the Naval Surface Warfare Center Dahlgren Division via a secure data collection site. The Contractor is required to completely fill in all required data fields using the following web address https://doncmra.nmci.navy.mil.

Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year

(FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk, linked at https://doncmra.nmci.navy.mil.

C.10 DIGITAL DELIVERY OF DATA

(a) Delivery by the Contractor to the Government of certain technical data and other information is now frequently required to be made in digital form rather than in hardcopy form. The method of delivery of such data and/or information (i.e., electronic, digital, paper hardcopy, or other form) shall not be deemed to affect in any way either the identity of the information (i.e., as “technical data” or “computer software”) or the Government’s and the

Contractor’s respective rights therein.

(b) Whenever technical data and/or computer software deliverables required by this contract are to be delivered in digital form, any authorized, required, or permitted markings relating to the Government’s rights in and to such technical data and/or computer software must also be digitally included as part of the deliverable and on or in the same medium used to deliver the technical data and/or software. Such markings must be clearly associated with the corresponding technical data and/or computer software to which the markings relate and must be included in such a way that the marking(s) appear in human-readable form when the technical data and/or software is accessed and/or used. Such markings must also be applied in conspicuous human-readable form on a visible portion of any physical medium used to effect delivery of the technical data and/or computer software. Nothing in this paragraph shall replace or relieve the Contractor’s obligations with respect to requirements for marking technical data and/or computer software that are imposed by other applicable clauses such as, where applicable and without limitation, DFARS 252.227-7013 and/or DFARS 252.227-7014.

(c) Digital delivery means (such as internet tools, websites, shared networks, and the like) sometimes require, as a condition for access to and/or use of the means, an agreement by a user to certain terms, agreements, or other restrictions such as “Terms of Use,” licenses, or other restrictions intended to be applicable to the information being delivered via the digital delivery means. The Contractor expressly acknowledges that, with respect to deliverables made according to this contract, no such terms, agreements, or other restrictions shall be applicable to or enforceable with respect to such deliverables unless such terms, agreements, or other restrictions expressly have been accepted in writing by the Contracting Officer; otherwise, the Government’s rights in and to such deliverables shall be governed exclusively by the terms of this Task Order.

C.12 SENSITIVE, PROPRIETARY, AND PERSONAL INFORMATION

https://doncmra.nmci.navy.mil/

Work under this contract may require that personnel have access to Privacy Information. Contractor personnel shall adhere to the Privacy Act, Title 5 of the U.S. Code, Section 552a and applicable agency rules and regulations.

Access to and preparation of sensitive information subject to Privacy Act and Business Sensitive safeguarding and destruction may be required in the execution of Act and Business Sensitive safeguarding and destruction may be required in the execution of tasking associated with this contract. Administratively sensitive information/data must not be shared outside of the specific work areas. All personnel with access to privacy act data in support of this contract must sign a privacy act certification.

C.13 NON-DISCLOSURE AGREEMENTS (NDAs)

NDAs may be utilized to allow for access to company sensitive/proprietary data. For tasks requiring NDAs, the contractor shall obtain appropriate agreements for all of their employees that are associated with the task requiring such an agreement. Contractor personnel may be required, from time to time, to sign non-disclosure statements as applicable to specific Performance Work Statement tasking. The COR will notify the contractor of the number and type of personnel that will need to sign the Non-Disclosure agreements. The signed Non-Disclosure Agreements shall be executed prior to accessing data or providing support for information that must be safeguarded and returned to the COR for endorsement and retention. Copies of all executed NDAs shall be provided to the COR.

C.14 NON-PERSONAL SERVICES/INHERENTLY GOVERNMENTAL FUNCTIONS

(a) The Government will neither supervise contractor employees nor control the method by which the contractor performs the required tasks. The Government will not direct the hiring, dismissal or reassignment of contractor personnel. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual contractor employees. It shall be the responsibility of the contractor to manage its employees and to guard against any actions that are of the nature of personal services or give the perception that personal services are being provided. If the contactor feels that any actions constitute, or are perceived to constitute personal services, it shall be the contractor’s responsibility to notify the Contracting Officer immediately in accordance with the clause 52.243-7.

(b) Inherently-Governmental functions are not within the scope of this Task Order. Decisions relative to programs supported by the contractor shall be the sole responsibility of the Government. The contractor may be required to attend technical meetings for the Government; however, they are not, under any circumstances, authorized to represent the Government or give the appearance that they are doing so.

C.15 SUB-CONTRACTORS/CONSULTANTS

In addition to the information required by FAR 52.244-2 Alternate 1 (June 2007) , the contractor shall include the following information in requests to add subcontractors or consultants during performance, regardless of subcontract type or pricing arrangement.

(1) Clearly present the business case for the addition of the subcontractor/consultant,

(2) If applicable, the impact on subcontracting goals, and

(3) Impact on providing support at the contracted value.

C.16 SKILLS AND TRAINING

The Contractor shall provide capable personnel with qualifications, experience levels, security clearances, and necessary licenses, certifications, and training required by Federal, State and Local laws and regulations.

Information assurance functions require certifications specified in DFARS 252.239-7001 INFORMATION

ASSURANCE CONTRACTOR TRAINING AND CERTIFICATION. Training necessary to ensure that personnel performing under this task order maintain the knowledge and skills to successfully perform the required functions is the responsibility of the Contractor. Training necessary to maintain professional certification is the responsibility of the Contractor.

SECTION I - CONTRACT CLAUSES

The following have been added by reference:

252.227-7015

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

Ddl-J10 LIST OF ATTACHMENTS

Exhibit A – Contract Data Requirements List, DD1423

Exhibit B – Hardware Specification Achievability Analysis_Rev1

Attachment J.1 – RFQ 0001 – Delivery Order Action Sheet_Rev1

Attachment J.2 – RFQ 0001 – Statement of Work_Rev2

Attachment J.3 – RFQ 0001 – Contract Data Requirements List, DD1423

Attachment J.4 – Cost Summary Format

Attachment J.5 – Supporting Cost Data

Attachment J.6 – Staffing Matrix

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

Ddl-L25 TECHNICAL PROPOSAL – SPECIFIC REQUIREMENTS – TECHNICAL AND

MANAGEMENT UNDERSTANDING/CAPABILITY

WRITTEN PROPOSAL REQUIREMENTS – ORGANIZATION AND MINIMUM CONTENT

The written technical proposal shall consist of the following items:

Mandatory Requirements

Offerors must meet the requirement or provide a written plan detailing the necessary steps and the timeline to be taken in order to meet them by time of award. In addition, the mandatory requirement must be maintained throughout the life of the Task Order. The mandatory requirement is as follows:

Requirement 1: Facility location

The Offeror’s primary facility must be located within the Continental United States of America (CONUS).

Technical Understanding/Capability/Approach Factor 1

This factor addresses the capabilities of the Offerors. Offerors shall show a clear understanding of the effort required by the Government.

Sub-factor 1 Hand-held Hardware Device Design

Offerors shall demonstrate their understanding of the requirements of the IDS hand-held hardware system to be developed and produced under the SOW. Offerors shall convey how their skills and experience will be used to meet the Government’s requirements.

Offerors shall provide the following to NSWCDD:

1) Design drawings of the hand-held hardware device as described in the SOW for Delivery Order 0001 included in this solicitation. Drawings shall clearly show the location of all sensors, cameras, external interfaces, power inputs, touch screen, the computing platform, and all points where a human will physically interact with the device.

2) A matrix or table showing how the Offeror’s proposed design will meet the requirements for the hand-held hardware device as listed in the SOW for Delivery Order 0001 including those in Exhibit B, the hardware specification list. Offerors shall present a line-by-line listing of the requirements from the Government and a written explanation of how the Offeror will meet each requirement with the proposed design. These explanations shall make detailed reference to the submitted drawings where applicable.

Sub-factor 2 Technical Proposal to Delivery Order 0001

Offerors’ shall provide a technical proposal to complete all of the tasking and meet all of the requirements outlined in attachments J.1, J.2, and J.3 for Delivery Order 0001. If subcontracting or teaming is proposed, the Offeror shall state the specific requirements of the Delivery Order 0001 that each Sub-contractor or team member will perform.

The Offeror shall address the technical reason(s) for selecting each Sub-contractor/team member and highlight any previous working relationships. Offerors shall provide a cost/price proposal based on Delivery Order 0001 identified in Section J Attachment J.1, J.2, and J.3.

Sub-factor 3 Manufacturing Readiness

The Offeror shall address their readiness to produce and deliver a lot size of three hundred eighty five (385) and a lot size of six hundred seventy five (675) hand-held devices. The Offeror shall address the availability of all parts considered replaceable by the Offeror to support a 12-month sparing philosophy. The Offeror shall address their

Quality Assurance/Quality Control procedures related to manufacturing. Offerors shall provide evidence of their production and sales of Commercial Off-the-Shelf (COTS), modified commercial, or customized integrated multi-modal biometric mobile devices, preferably within the last 2 years but at least within the last 5 years. Specifically, the Offeror shall address their experience in producing and selling devices similar to the integrated hand-held hardware device to be designed and delivered under this contract. Offerors shall also discuss how information submitted under Sub-factor 1 and Sub-factor 2 relates to or builds upon the Offeror’s evidenced experience in the biometrics industry. Offerors shall include any relevant experience with integrating outside software applications onto their devices.

Sub-factor 4 Statement of Work

The Offeror shall address their technical approach and capability to support the requirements described in the SOW.

If subcontracting or teaming is proposed, the Offeror shall state the specific requirements of the SOW that each Sub-contractor or team member will perform. The Offeror shall address the technical reason(s) for selecting each Sub-contractor/team member and any previous working relationships.

Management Capability Factor 2

The Offeror shall demonstrate their approach and ability to effectively manage all efforts under this contract. This shall include the areas listed below. However, Offerors are strongly encouraged to address other aspects of their proposed management approach which they feel will convey their management expertise.

The Offeror shall describe their equipment and facilities and how these resources support the requirements of the

SOW. In addition, the Offeror shall address how work will be managed amongst multiple locations, if the use of multiple locations and facilities is proposed. The Offeror shall present its overall management approach, proposed organization, management structure, liaison with the Contracting Officer, COR, and IDS program technical representatives from the Technical Direction Agent (TDA) and the In-Service Engineering Agent (ISEA), and understanding of and ability to comply with the contract's business management aspects such as progress reporting, risks and risk mitigation, and invoicing. The Offeror shall describe the specific plans and processes that will be implemented to provide quality control over all deliverables, both formal and informal, including those provided by

Sub-contractors/team members/consultants. The Offeror shall include process flow charts and describe each part of the process as applicable. The overall effectiveness of these procedures will be judged by the quality of both the technical and cost proposals in terms of form (spelling, grammar, etc.) and responsiveness to solicitation requirements. Offerors shall describe their approach for increasing efficiency and reducing duplication during performance. Offerors shall describe their approach for controlling unit cost of hardware items and for achieving economies of scale on production lines.

If subcontracting or teaming is proposed, the Offeror shall state the specific requirements of the SOW that each Sub-contractor or team member will perform. The Offeror shall address the technical reason(s) for selecting each Sub-contractor/team member and any previous working relationships. A copy of any subcontracting/teaming/consulting agreements proposed to fulfill any direct charged part of the contract shall be provided. The document shall be signed by both the Offeror and the proposed Sub-contractor/team member/consultant and shall show agreement as to the specific technical work areas to be subcontracted, type of contracting pricing arrangement (FFP, CPIF, CPFF, etc.) and the level of effort to be provided over the contract period.

Past Performance Factor 3

Offerors shall also provide up to three (3) past performance references for work performed as Prime or Sub-

Contractor for the Government within the last five years that demonstrate the ability to handle the scope and breadth of the proposed contract. The following must be included for each past performance reference:

1) Contract /Task Order number

2) Contract type (e.g. CPFF-term; CPIF-completion; FFP, etc.)

3) Program name and Agency Supported (e.g. IDS Program/NAVSEA)

4) Total contract value. If performed as a Sub-contractor, also include the estimated value of support provided.

5) Brief description of work performed and how the work is relevant to this contract. Bullet format is preferred for this information.

6) Valid names and telephone numbers and e-mails for the Procuring Contracting Officer (PCO) and

Contracting Officer’s Representative (COR).

The Government may also use other information such as Award Fee data and CPARS/PPIRS data available from

Government sources to evaluate an Offeror’s past performance. The Government reserves the right to limit or expand the number of references it decides to contact and to contact references other than those provided by the

Offeror.

Cost and Price Factor 4

Offerors shall submit a cost proposal for Delivery Order 0001 to include the costs associated with all tasking in the

SOW for Delivery Order 0001. Cost proposals shall include the following:

1) A cost buildup

2) A supporting narrative rationale for the prices proposed, to include the following:

a. Direct Labor: Proposed hours, labor category, direct labor rates, and calculated amounts for each direct labor category by item. As part of the basis of estimate narrative, provide rationale for proposed hours and labor mix. For the direct labor rates, provide payrolls or rationale as to how the direct labor rates were derived.

b. Indirect Rates: Provide three (3) years of historical rates if the Offeror does not have a Forward

Pricing Rate Agreement (FPRA)

c. Other Direct Costs: A list of all materials proposed and the rationale for the proposed price.

Provide quotes or previous invoices of material purchased to prove price reasonableness.

3) All other costs and the reductions or rebates offered.

4) Offers shall submit a quote with the unit costs associated with producing and delivering hand-held hardware devices. Offeror’s quotes for five (5) prototype units as described in Delivery Order 0001 attachments J.1, J.2, and J.3

5) Offerors shall submit a quote for an order of 350 units, based upon the quote for step ladder pricing of one

(1) to over one thousand five hundred (1,500) production units.

6) Offerors shall submit a quote for step ladder pricing for quantities of one (1) to over one thousand five hundred (1,500) production units in FFP CLIN 0002 as shown in the table below.

Quantity(ies) 1-50 51-200 201-500 501-1000 1001-1500 1501+

Price

The Government will perform an analysis of the realism and completeness of the cost data and the traceability of the cost to the Offerors’ capability data in accordance with FAR 15.204-1(d)(3). Results of the analysis may be used in assessing performance risk and responsibility. Proposals shall not be adjusted as a result of the analysis. Proposals which are unrealistic in terms of technical or schedule commitments or unrealistically high or low in price may be deemed reflective of an inherent lack of technical competence, or indicative of a failure to comprehend the complexity and risks of the proposed work, and may be grounds for rejection of the proposal. Since the resulting contracts will require the delivery of data, the responsiveness and quality of organization and writing reflected in the proposal (both technical and price portions) will be considered to be an indication of the Offeror’s quality control processes that would be applied to deliverable data. Subjective judgment on the part of the Government evaluators is implicit in the entire process.

The Government anticipates a required product delivery within 90 days of award of a Delivery Order.

Pricing should be based upon a 90 day delivery schedule.

Ddl-L40 SUBMISSION OF QUESTIONS BY POTENTIAL OFFERORS

It is the offeror's responsibility to bring to the attention of the Contracting Officer at the earliest possible time, but prior to the closing date, any ambiguities, discrepancies, inconsistencies, or conflicts between the SOW and other solicitation documents attached hereto or incorporated by reference. All questions are requested in writing by 16:00

13 April 2018.

Contractor Questions and Answers:

Question 1:

RFP Reference: Page 8 of the RFP, section C4.3 references "mature high-fidelity prototype multi-modal integrated biometric hand-held hardware devices, First Article production representative multi-modal integrated biometric hand-held hardware devices and final baselined configuration multi-modal integrated biometric hand-held hardware devices produced via a proven production process."

Please provide the government's definitions for high-fidelity prototype, First Article and final baselined configuration devices.

ANSWER:

Mature high-fidelity prototype: Fully integrated computing platform, sensors, media storage, batteries, etc., per the requirements defined in the RFP, DO1 SOW and Hardware Specification list, with a technology readiness level

(TRL) of 6 or greater, as defined by the Defense Acquisition Guidebook (DAG). Ruggedization and Environmental implementations are not required but traceability should be provided for development prior to final baseline configuration, as required by the PMO.

First Article production representative: Improvement upon mature high-fidelity prototype to include modifications required through government evaluation, ruggedization and environmental, as required. This device will be used for interoperability certification and final government testing and is expected to meet TRL 8 requirements as defined by the DAG.

Final Baseline configuration: Improvements upon First Article production representative to include additional modifications required through government evaluation, as required. This device will be used as the final hardware product baseline for full rate production (FRP) and fielded to the user and is expected to meet TRL 9 requirements upon OT&E or system fielding.

Question 2:

RFP Reference: Page 10 of the RFP, C.7 MANDATORY REQUIREMENT states:

The mandatory requirement must be maintained throughout the life of the Task Order.