Attachment0001PWS.pdf

PERFORMANCE WORK STATEMENT (PWS)

FOR THE

DEFENSE ADVANCED GPS RECEIVER (DAGR) DISTRIBUTED DEVICE

(D3)

(With Integrated Contract Data Requirements List (CDRL) DD Form 1423)

Date:

23 August 2012

Prepared by:

Product Director

Positioning, Navigation and Timing (PD PNT)

THIS PAGE INTENTIONALLY LEFT BLANK

TABLE OF CONTENTS

PARAGRAPH PAGE

1. SCOPE

1.1 Background

1.2 Contract Type

1.3 Period of Performance

2. APPLICABLE DOCUMENTS

3. REQUIREMENTS

3.1 General Requirement – Description

3.1.1 Requirements – Technical Description

3.1.2 D3 Production Deliveries

3.1.2.1 Quality Control Testing (Production Items)

3.1.2.2 Acceptance Test Failure Correction

3.1.3 Program and Technical Reviews

3.1.3.1 Post Award Conference

3.1.3.2 Program Meetings

3.1.3.3 Integrated Product Team (IPT)

3.1.4 Deliverable Data

3.1.4.1 Digital Media

3.1.4.2 Information Access

3.1.5 Standard Commercial Warranty

3.1.6 Configuration Control

3.1.6.1 Configuration Manager

3.1.6.2 Configuration Baseline

3.1.6.3 Configuration Changes

3.1.6.3.1 Contractor-Initiated Changes

3.1.6.3.2 Government-Initiated Changes

3.1.6.3.3 Configuration Change Testing

3.1.7 Packaging, Handling, Storage and Transportation

3.1.7.1 Packaging

3.1.7.2 Handling

3.1.7.3 Storage

3.1.7.4 Transportation

3.1.8 Marking

3.1.9 Security

3.1.10 Antiterrorism (AT) and Operations Security (OPSEC)

3.1.10.1 AT Level I Training

3.1.10.2 OPSEC Standard Operating Procedure/Plan

3.1.10.3 OPSEC Training

3.1.10.4 Handling or Access to Classified Information

3.1.11 Technical Support

3.2 Test and Evaluation

3.2.1 First Article Testing (FAT) Support

3.2.2 Operational Assessment Support

3.3 Logistics

3.3.1 SAASM Account Custodian (SAC) Requirement

3.3.2 Supplemental Data for Provisioning (SDFP)

3.3.3 Support Equipment (SE)

3.3.4 Cyclic Maintenance/Repair

3.3.5 Software

3.3.6 Property Book Unit Supply Enhanced (PBUSE)

3.3.7 Level of Repair Analysis Input Data

3.3.7.1 Data Content

3.4 Installation Specification

3.5 Technical Manual

3.6 Safety Assessment

3.6.1 Safety Assessment Report (SAR)

3.6.2 Toxic Substances

3.6.3 Hazard Tracking

3.6.4 Safety Inspection/Verification

3.7 Contract Status Reporting

3.8 Integrated Master Schedule

3.9 Frequency Allocation Data

4. CONTRACT DATA REQUIREMENTS LIST (CDRL)

5. ACRONYMS

1. SCOPE

This Performance Work Statement (PWS) specifies the tasks and efforts required to procure and support the DAGR Distributed Device (D3) as the near-term first product in a Family of Solutions to satisfy current and emerging requirements for Positioning, Navigation and Timing (PNT) Capabilities (PNTCAP). This PWS includes requirements for testing, production deliveries, logistics, maintenance, and technical support of the D3.

1.1 Background

Product Director, Positioning, Navigation and Timing (PD PNT) is procuring and supporting an array of PNT sensors that go beyond just GPS in an incremental upgrade philosophy. The objective is to field a Family of Solutions using the best available current technologies to field products that reduce, minimize or eliminate Army investment costs while supporting current and emerging requirements for PNTCAP.

The PNT Family of Solutions is intended to serve as the PNTCAP foundation providing:

Scalable, Open Architecture Solutions Coordinated/Optimal Materiel Solutions Added Operational Utility Assured, Secure PNT Capability Lower Fielding and Sustainment Costs Lower Army Investment, and Greater Opportunity for Army Reinvestment Transition Path to M-Code Capabilities and Products

The D3 is a product within this Family of Solutions that distributes PNT on a platform. As a near-term solution, the D3 acquisition will provide a low-cost alternative to the AN/PSN-13 Defense Advanced GPS Receiver (DAGR) to meet platform mounted requirements for SAASM-based PNTCAP DAGR applications.

The program objectives for D3 include:

Implement D3 for mounted capability for continued operations and extension of existing capabilities

Reduce total package fielding (TPF) cost

1.2 Contract Type

The D3 procurement will utilize a Firm Fixed Price Indefinate Delivery/Indefinate Quantity (FFP IDIQ) contract.

1.3 Period of Performance

The period of performance for the D3 contract will be 2 years.

2. APPLICABLE DOCUMENTS

Document Number

Document Title

Revision Issue Date

SAASM Account Custodian Handbook H

Document Number

Document Title

Revision Issue Date

GPU-09-105 Security Approval Review Process Requirements Document (PRD) for the Global Positioning System Selective Availability Anti-Spoofing Module (SAASM) Host Application Equipment

(HAE)

24 Aug 2009

GPU-09-071 Process Requirements Document (PRD) for Authorization to Procure or Transfer Global Positioning Systems (GPS) Precise Positioning Service (PPS) Host Application Equipment (HAE)

24 Aug 2009

DoD 5220.22 National Industrial Security Program Operating Manual

M 28 Feb 2006

IS-GPS-153 GPS User Equipment Interface Specification for the GPS Standard Serial Interface Protocol (GSSIP) of DoD Standard GPS UE Radio Receivers

D 23 Jul 2007

IS-GPS-164 GPS User Equipment Interface Specification for Defense Advanced GPS Receiver (DAGR) Unique Interface Characteristics

23 Jul 2007

MIL-HDBK-

Configuration Management Guidance A 07 Feb 2001

MIL-PRF-

DAGRDD-

Performance Specification for the Defense Advanced GPS Receiver (DAGR) Distributed Device

MIL-STD-129 DoD Standard Practice, Military Marking for Shipment and Storage

P Change Notice 4

19 Sep 2007

MIL-STD-130 DoD Standard Practice, Identification Marking of U.S. Military Property

N 17 Dec 2007

NSTISSI No.

Operational Security Doctrine for the Navstar Global Positioning System (GPS) Precise Positioning Service (PPS) User Equipment

Aug 2001

GPS SCG Global Positioning System (GPS) Security Classification Guide (SCG)

30 Sep 2008

AR 530-1 Operations Security (OPSEC) 19 Apr 2007

FAR 52.204-2

3. REQUIREMENTS

3.1 General Requirement – Description

The D3 will provide a means of providing PNT data at the platform level using a single SAASM-based GPS receiver while avoiding the costs associated with integrating multiple AN/PSN-13s into individual systems. The D3 is a functional alternative to AN/PSN-13 when utilized in a platform-mounted application with no additional platform requirement for operator interface. The D3 shall route PNT data independently to a minimum of three (threshold) external devices reusing the AN/PSN-13 cabling. It shall mount within the same space as a mounted

AN/PSN-13 using the AN/PSN-13 mount, or using the same bolt holes as the AN/PSN-13 mount as specified in the IS-GPS-164.

3.1.1 Requirements – Technical Description

The MIL-PRF-DAGRDD-100, hereinafter referred to as the Performance Specification (PRF), is provided as a technical requirements document to define required functions/performance of the D3. The contractor shall develop a performance specification document as part of the proposal in accordance with (IAW) CDRL L001 that defines the exact performance of the proposed D3, and highlights any departures from PRF.

3.1.2 D3 Production Deliveries

The contractor shall produce the D3 in accordance with the PRF, as ordered by the Contract Line Item Numbers (CLINs) in Section B of the contract schedule. These deliveries shall include a basic Delivery Order (DO) that will include the First Article Test (FAT) quantity of D3s. All additional DOs are to be exercised or awarded at the discretion of the Government IAW the provisions of the contract.

The D3 shall be designed to utilize both the Type I and Type II SSI form factor IAW MIL-PRF- DAGRDD-100. This is required because D3 will be upgraded to Modernized (M-Code) GPS capability via insertion of a new card, and those devices will initially only be available in Type I form, but will subsequently transition to Type II. PD PNT will support this effort by offering Type II SSI cards as Government Furnished Equipment (GFE) for the production of the D3 should the design require the Type II SSI card.

3.1.2.1 Quality Control Testing (Production Items)

The contractor shall perform quality control testing including Environmental Stress Screening (ESS) on each production item prior to acceptance of the production unit by the government.

Each deliverable item shall be given a thorough visual and mechanical inspection to determine that the requirements for quality of material, workmanship and final item functionality are met.

The quality control test plan shall be delivered in the proposal as part of the Quality Control/Assurance Plan IAW CDRL A001.

3.1.2.2 Acceptance Test Failure Correction

Should a production unit fail any acceptance test, the contractor shall eliminate the cause of the failure and prevent the failure’s reccurrence. All contractor quality audit and final acceptance test failures shall be documented and verified by Defense Contract Management Agency (DCMA) before quality acceptance of the product item for shipment. If the contractor identifies a series of failures as possibly systemic in nature (a trend), the contractor shall perform failure analyses to identify the cause(s), extent of the problem and recommend appropriate corrective action. Units shall not be sold without final test data acceptance. If the Government identifies a series of failures as possibly being systemic in nature, the contractor shall provide failure analyses identifying the cause(s) and extent of the problem including identification of all affected units. The contractor shall document the results of the systemic failure analyses in a Failure Analysis Report IAW CDRL M002. If the Government determines the failure mode warrants a retrofit or replacement of affected equipments or components, whether already accepted or not, then the contractor shall perform the replacement or retrofit of the equipment or components.

The Government reserves the right to withhold acceptance of those units identified to contain a systemic problem until the corrective action is implemented. All costs associated with the correction of individual and systemic acceptance test failures shall be borne by the contractor.

3.1.3 Program and Technical Reviews

3.1.3.1 Post Award Conference

A Post Award Conference shall be conducted at the contractor’s facility no later than (NLT) 30 Days After Contract award (DAC). At the Post Award Conference the contractor shall introduce those individuals, including subcontractors, designated to participate in the joint Government/contractor program meetings. The dates for subsequent program meetings, consistent with this PWS and contract, shall be established at the Post Award Conference.

3.1.3.2 Program Meetings

Integrated Product Team (IPT) meetings shall be coordinated to promote efficient use of time and to reduce travel costs. The contractor, including designated subcontractors, shall participate in and support joint Government/contractor program meetings. The first program meeting shall be conducted at the contractor’s facility. The first program meeting shall be conducted NLT 90 DAC. Subsequent program meetings may alternate between the contractor’s facility and Aberdeen Proving Ground, MD. Program meetings shall be conducted quarterly for the remainder of the first contract year. During subsequent contract years, program meetings shall be held semi-annually. Program meetings may be conducted as Video-Teleconferences (VTC) or waived by mutual agreement. The use of VTC shall be maximized when mutually agreeable.

The contractor shall be responsible for providing agenda and presentation materials at least 10 working days in advance of meetings and minutes subsequent to all meetings held at the contractor or Government facilities, including the post award conference, and all meetings held via VTC. The contractor shall be responsible for providing meeting minutes IAW CDRL B001.

3.1.3.3 Integrated Product Team (IPT)

The Government shall chair the IPT. The IPT shall address all issues related to the performance of the contract and the D3 program. The IPT shall have unencumbered access to information as stated in paragraph 3.1.4.2.

3.1.4 Deliverable Data

Data deliverables required under this contract as set forth on the CDRL DD Form 1423s for draft and final submissions shall optimize the use of digital media. Only classified data shall be paper hardcopy and shall be handled IAW DoD 5220.22 “National Industrial Security Program Operating Manual.”

The contractor shall develop and deliver to the government computer based training for operators and unit level maintainers IAW CDRL M001.

3.1.4.1 Digital Media

Deliverable data for draft and final submissions shall be submitted electronically in both Office XP (or later) compatible formats and Adobe Acrobat Portable Document Format (PDF). Adobe

Acrobat Pro version 2.0 (or later) with Distiller shall be required to convert the document into the Acrobat PDF file format.

3.1.4.2 Information Access

The contractor and all subcontractors shall identify information to which Government access is restricted and why (e.g. proprietary process or software). The Government shall have access to all unrestricted technical and logistics data used in the performance of this contract including on-line access to standard commercial warranty and warranty repair data, entry to contractor or subcontractor plants facilities and factories.

3.1.5 Standard Commercial Warranty

The contractor shall provide individual (failure-free) and systemic warranty coverage for all D3 hardware delivered under this contract for a period of 12 months. Systemic software defects shall be repaired under warranty. The contractor shall repair defective D3’s that are under warranty and return them to the user or replace them with a serviceable D3 with no cost to the Government. If the contractor replaces a warrantied D3 with a new unit, that unit shall be provided from contractor resources with no additional cost to the government. In both cases, a responsive Turn-Around-Time (TAT) must be proposed. Details of the standard commercial warranty procedures, TAT, remedies, exclusions and reports shall be set forth in the Warranty Clause of the contract.

The Contractor shall de-militarize any D3’s that are returned and found to be beyond economical repair IAW NSA procedures. The contractor shall request DCMA concurrence for any determination of a device as beyond economical repair.

The Contractor shall prepare the Warranty Performance Report IAW CDRL N001 and this PWS.

3.1.6 Configuration Control

3.1.6.1 Configuration Manager

PD PNT is the Government Configuration Manager for D3. The Government is responsible for configuration control of D3 performance and critical interfaces as reflected in the PRF and IS- GPS-153 hereafter referred to as the ICD. The contractor is responsible for Configuration Item (CI), i.e., the D3 design and product baselines. After acceptance/ authentication by the Government Configuration Change Board (CCB), any changes to the Configuration Item (CI) require Government approval.

3.1.6.2 Configuration Baseline

The D3 Configuration Baseline is defined in the PRF. Subsequent to Government acceptance of any ECPs, the PRFshall continue to be the Configuration Baseline. Class II configuration changes shall be submitted to the local government representative (DCMA/Administrative Contracting Officer (ACO) office) for concurrence; any change in which DCMA non-concurs shall be resubmitted as a Class I ECP IAW CDRL J001 to the government Configuration manager for CCB review. Refer to MIL-HDBK-61A, table 6-2, for change classification definition. The D3 shall conform to Configuration Baseline except for changes or departures that are approved by the Government configuration manager and made effective by contract modification. The contractor shall place the hardware and software design documentation under configuration control prior to Government acceptance.

3.1.6.3 Configuration Changes

3.1.6.3.1 Contractor-Initiated Changes

Once the CI has been accepted by the Government, any changes to the CI shall require Government approval. The contractor shall submit all non-cost related change requests, including requests for waivers or deviations, to DCMA and Army Contracting Command Aberdeen Proving Ground (ACC-APG).

The DCMA is the authorized representative for Contractor non-cost related initiated changes of the configuration baseline. DCMA will forward all change requests to PD PNT to review and confirm whether the changes affect the PRF or ICD (Class I Changes). PD PNT will be responsible for seeking any other Government office concurrence deemed necessary on changes that affect the PRF or the ICD. DCMA will approve all other non-cost related changes designated as Class II Changes and will forward a request to the Contracting Officer (KO) to execute a non-cost related contract modification if the change affects the contract (i.e. changes the PWS or specification). All cost-related changes shall be approved by the KO after evaluation/negotiation via modification to the contract.

MIL-HDBK-61A, table 6-2 defines change classifications. Class II configuration changes (no CDRL needed) shall be submitted to the local government representative (DCMA/ACO office) for concurrence; any change in which DCMA non-concurs shall be resubmitted as a Class I Engineering Change Proposal (ECP) IAW CDRL J001 to the government Configuration manager for CCB review. The D3 shall conform to Configuration Baseline except for changes or departures that are approved by the Government configuration manager and made effective by contract modification. The contractor shall place the hardware and software design documentation under configuration control prior to Government acceptance.

3.1.6.3.2 Government-Initiated Changes

Any Government-initiated changes will require contract modification. The Aberdeen Proving Ground Army Contracting Command will submit to the contractor a request for proposal for the change. The contractor shall submit a proposal for the change to the Contracting Officer. The Contracting Officer will negotiate the change with the contractor and modify the contract appropriately.

3.1.6.3.3 Configuration Change Testing

Upon completion of any configuration change and prior to acceptance of production units, D3 testing shall be performed by the Contractor. Configuration Change Test Plans and Test Procedures shall be submitted to the Government as part of the Engineering Change Proposal (ECP) package.

3.1.7 Packaging, Handling, Storage and Transportation

3.1.7.1 Packaging

Each D3 shall be packaged using best commercial practices.

3.1.7.2 Handling

Handling of the D3 shall be IAW NSTISSI No. 3006.

3.1.7.3 Storage

The contractor shall handle and provide secure bonded storage appropriate for the D3 incorporating SAASM IAW GPU-09-071. D3 may be held in bonded storage at no additional cost for up to one year from date of acceptance. The D3 shall be storable for a minimum of 2 years without damage to the equipment or its packaging.

3.1.7.4 Transportation

D3 assets shall be transported by the fastest traceable means to the first destination. The contractor shall provide the Government with notice of each shipment by providing to the Government an Electronic DD 1149.

3.1.8 Marking

The following markings shall be applied to the D3 IAW MIL-STD-130: NSN, Contractor- Assigned Government Entity (CAGE) code, manufacturers serial number, and manufacturers part number. Other markings shall be applied IAW MIL-STD-130 subject to the availability of space. The SAASM component shall be marked IAW GPU 09-105.

The container for each D3 shall be marked IAW MIL-STD-129 including warranty markings.

Since the D3 will not be shipped to the Defense Distribution Depot or through the Defense Transportation System (DTS), it is not necessary to mark D3 packages/shipping containers with RFID tags. The D3 shall also be marked IAW requirements for DoD Item Unique Identification (IUID) as specified in MIL-STD-130.

3.1.9 Security

This contract is for the production of D3 containing a SAASM-based GPS receiver. The contractor is required to have a Secret facility clearance with a Secret safeguarding capability as stated in the DD 254. The completed D3 is required to be determined to be unclassified when keyed by a GPS Directorate Security Design Review IAW GPU-09-105; however, portions of the production process will be classified and the contractor will receive and generate classified material. The contractor will require access to Communications Security (COMSEC). The D3 is not a Cryptographic Controlled Item (CCI); however, the contractor will require access to GPS cryptographic material to test the D3. Contractor is authorized to use the Defense Courier Service. Additional Security Guidelines for COMSEC are attached to the DD 254.

The contractor shall require access to non-SCI intelligence and For Official Use Only (FOUO) information for the development and testing of the D3. Intelligence Materials Access Requirements and Guidelines for Safeguarding “For Official Use Only” Information are attached to the DD 254.

The contractor shall also require access to the NAVSTAR Global Positioning System (GPS) Security Classification Guide (SCG). The contractor shall follow the guidelines for handling SAASM: GPU 09-105A Security Approval Review Process Requirements for Selective Availability Anti-Spoofing Module Host Application Equipment; GPU 09-071, Process Requirements Document for Authorization to Procure or Transfer GPS PPS Host Application Equipment.

3.1.10 Antiterrorism (AT) and Operations Security (OPSEC)

3.1.10.1 AT Level I Training.

This provision/contract text is for contractor employees with an area of performance within an Army controlled installation, facility or area. The contractor shall submit a list of names from this project and reasons requiring access to Army installations for PM approval. Once approved, contractor employees, to include subcontractor employees, requiring access to Army installations, facilities and controlled access areas shall complete AT Level I awareness training within 30 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. The contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee IAW CDRL D002, to the Contracts Officer Representative (COR) or to the contracting officer, if a COR is not assigned, within 10 calendar days after completion of training by all employees and subcontractor personnel. AT level I awareness training is available at the following website:

https://atlevel1.dtic.mil/at.

3.1.10.2 OPSEC Standard Operating Procedure/Plan.

The contractor shall use the PM NAVSYS OPSEC plan and only update as required for their use IAW CDRL E002 within 90 calendar days of contract award, to be reviewed and approved by the responsible Government OPSEC officer, per AR 530-1, Operations Security. This SOP/Plan shall include the government's critical information, why it needs to be protected, where it is located, who is responsible for it, and how to protect it. In addition, the contractor shall identify an individual who will be an OPSEC Coordinator. The contractor shall ensure this individual becomes OPSEC Level II certified per AR 530-1.

3.1.10.3 OPSEC Training.

This provision/contract text is for contractor employees with an area of performance within an Army controlled installation, facility or area. The contractor shall submit a list of names and reasons requiring access to Army installations for PM approval. Once approved, Per AR 530-1, Operations Security, new contractor employees shall complete Level I OPSEC training within 30 calendar days of their reporting for duty. Approved contractor employees shall complete annual OPSEC awareness training and report training certificates IAW CDRL D002.

3.1.10.4 Handling or Access to Classified Information.

The Contractor shall comply with FAR 52.204-2, Security Requirements. This clause involves access to information classified “Confidential,” “Secret,” or “Top Secret” and requires contractors to comply with The Security Agreement (DD Form 441), including the National Industrial Security Program Operating Manual (DoD 5220.22); any revisions to DoD 5220.22, notice of which has been furnished to the contractor.

3.1.11 Technical Support

The contractor shall provide 100 hour blocks of time for phone technical support.

3.2 Test and Evaluation

Test and Evaluation (T&E) for D3 will be broken into two phases. These will consist of a First Article Test (FAT) and an Operational Assessment. All T&E effort will be managed by PD PNT Test and Evaluation Integrated Product Team (T&E IPT) in coordination with Army Test and evaluation Command (ATEC). The government test plan will lay out the specific tests being conducted in each of the phases, along with the responsible organizations. Efforts to integrate ATEC and contractor testing, where feasible, shall be pursued to eliminate duplication and maximize test efficiency.

3.2.1 First Article Testing (FAT) Support

A FAT will be conducted by the Government after receipt of the production level D3’s and prior to fielding of the initial units. The units tested will be production representative items. These tests will include, at a minimum, shock, vibration and temperature testing, along with EMI/EMC chamber testing. A Test Readiness Review (TRR) shall be held prior to any testing events.

Government Test Reports will be made available to the contractor.

The contractor shall provide technical services to support platform integration as required, up to four iterations of site visits (one week each) at Electronic Proving Ground (EPG) Fort Huachuca, AZ, Aberdeen Proving Ground (APG), MD, San Diego, CA, and Warner Robins AFB, GA. This is in addition to support of an operational assessment.

3.2.2 Operational Assessment Support

Network Integration Evaluation (NIE) is an operational assessment/evaluation event of Type I, II, and III systems. Type I systems are Systems Under Test (SUTs), testing primarily through execution of Initial Operational Tests (IOTs) or Limited User Tests (LUTs). Type II systems are Systems Under Evaluation (SUEs), evaluating quick reaction capabilities which are assessed in an operational context resulting in soldier recommendations on system/concept continuance and on DOTMLPF changes required to integrate systems/concepts into units and operations. Type III systems are Systems Under Demonstration (SUDs) which are at TRL 6 and below. There are two NIE events per year which are labeled as YY.1 and YY.2, where YY represents the two-digit year. These assessment results are used to update funding, fielding, and acquisition strategies. It is currently planned for D3 to participate in NIE 13.2 and all the events leading up to NIE 13.2 in 3Q13 (e.g. Network Integration Rehearsal (NIR)).

The contractor shall provide technical services to support demonstration and platform integration consisting of four iterations of site visits (one week each) for NIE at Fort Bliss, TX, White Sands Missile Range, NM, and Aberdeen Proving Ground, MD. An alternate operational assessment venue may be selected by ATEC.

3.3 Logistics

3.3.1 SAASM Account Custodian (SAC) Requirement

The contractor shall be responsible for appointing a SAC and an Assistant SAC (ASAC) that function as liaisons with the Key Data Processor (KDP) Loading and Installation Facility (KLIF) at Warner Robins Air Logistics Center (WRALC) Georgia. The SAC/ASAC is responsible for the transfer of D3s and configuration management, shipping and destruction information in support of serial number tracking of SAASMs by the KLIF. SAASMs shall be tracked by serial number after they are installed in the D3 until delivered to military End-User. The SAC/ASAC shall report the D3 serial number as well as the corresponding SAASM serial number to the KLIF prior to delivering the D3. If there is any change in a SAASM/D3 serial number association, the SAC/ASAC shall report that change to the KLIF. Full SAC/ASAC responsibilities are identified in the SAASM Account Custodian Handbook supplied by the

KLIF.

3.3.2 Supplemental Data for Provisioning (SDFP)

SDFP shall be provided IAW CDRL K001 for any parts that are identified as replaceable at organizational level maintenance.

3.3.3 Support Equipment (SE)

It is anticipated that there will be no peculiar SE needed for this procurement. However, if the contractor proposes SE for D3, the recommended SE shall be identified in the Installation Specification (paragraph 3.4).

3.3.4 Cyclic Maintenance/Repair

The contractor shall incorporate provisions in product design and installation specification to ensure access for periodic software updates.

3.3.5 Software

Periodic software updates are required to correct deficiencies and incorporate new functionality.

A robust software development and maintenance process is required. The Contractor shall provide a Software Development Plan (SDP) in the proposal as part of the Quality Control/Assurance Plan IAW CDRL G002.

The contractor shall provide all software updates in a package suitable for internet distribution (unclassified FOUO), and shall provide a software utility (as specified in MIL-PRF-DAGRDD-

100) to load new software to the D3. The Contractor shall deliver the Computer Software Product End Item IAW CDRL H001. Software Version Description shall be provided IAW CDRL G001 for each release.

The D3 design shall provide the ability to load new software on either the embedded GB-GRAM card or any other D3 internal processor without disassembly of the D3 (threshold) or removal of D3 from its vehicle mounting location (objective).

3.3.6 Property Book Unit Supply Enhanced (PBUSE)

Equipment to be fielded shall be placed into a PEO/PM PBUSE account at the time they are accepted by the Government and prepared for shipment to the gaining command or forward fielding sites.

3.3.7 Level of Repair Analysis Input Data

The Contractor shall provide Level of Repair Analysis Input Data as specified in section 3.3.7 and 3.3.7.1 IAW CDRL D003 to enable the Government to analyze maintenance and support costs of the proposed system. The source of data should be indicated. It should be noted that the following data definitions are specifically for application of the Computerized Optimization Model for Predicting and Analyzing Support Structures (COMPASS).

a. End Item. A final combination of end products, assemblies, materials which is ready for its intended use (e.g., ship, tank, mobile machine shop, aircraft). An end item need not all be within a common enclosure (case or shelter facility). Any equipment which has LRUs in common should be grouped in the same end item, if possible. LRUs and SRUs, which are common, need to be identified.

b. Line Replaceable Unit (LRU). Usually a subassembly, such as a receiver/transmitter unit, power supply, etc. Removal and replacement of LRUs results in the repair of the end item. A Circuit Card Assembly (CCA) may be considered a LRU if removal and replacement results in direct end item repair.

c. Shop Replaceable Unit (SRU). An example is a CCA. Removal and replacement of a SRU results in the repair of a LRU.

d. Piece Parts. Examples are: resistors, capacitors, transistors, integrated circuits, chips, etc.

Removal and replacement of piece parts results in the repair of a SRU.

3.3.7.1 LORA Data Content

The data content shall include:

All LRUs/SRUs shall be identified with the manufacturer part number, and if one exists, an National Stock Number (NSN). If the same LRU/SRU is used in different equipment, the same part number shall be used. Cabling, harnesses, miscellaneous mechanical controls, and other items which do not have a lower level of indenture shall be grouped together as units called miscellaneous LRUs or SRUs. Removal and replacement of miscellaneous throwaway LRUs results in end item repair. Removal and replacement of miscellaneous throwaway SRUs results in LRU repair.

It is necessary to identify LRUs, SRUs, throwaway LRUs, and throwaway SRUs. If the removal and replacement of an item results in repair of an end item, that item should be considered to be a LRU or a throwaway LRU. If the removal and replacement of an item results in repair of another item which has been labeled as a LRU, then that item is a SRU or a throwaway SRU. An item is considered to be a throwaway item (LRU or SRU) if it does not have a lower level of indenture and hence could not possibly be repaired. The lower level of indenture for a repairable LRU is a SRU. The lower level of indenture for a repairable SRU is a piece part. A tree structure diagram shall be completed for the end item. An example of a tree construct can be found in the User’s Manual under the paragraph entitled “Equipment Breakdown Overview”.

The following information shall be provided:

a. The end item unit price

b. The end item Mean Time Between Failure (MTBF) in hours

c. The end item Mean Time To Repair (MTTR) in labor hours

d. Test equipment/repairmen required to repair the end item every time it fails

e. Test equipment/repairmen required to repair the end item when specific LRUs fail

Specify the LRU and indicate how long the equipment/repairmen are required to accomplish each repair action. One example is test equipment used to realign or tune the end item when a specific LRU such as an antenna is replaced. Another example is a special tool used to remove and replace a specific LRU, but is not needed when other LRUs fail

f. The following for each test equipment not common to other end items:

1) Name

2) One-time development cost

3) Expected life

4) Lowest (most decentralized) maintenance echelon allowed

5) Unit price

6) Expected annual ownership cost

7) Is the equipment for diagnostic testing only or repair only or both diagnostic testing and repair?

8) One-time installation cost by maintenance echelon

g. The following shall be provided for each type of repairman:

1) Name

2) Is the repairman to perform diagnostic testing only or repair only or both diagnostic testing and repair?

3) Lowest maintenance echelon allowed

4) Is the repairman common or special (not common to other end items)? If the repairman is special, the following shall be provided:

i. Training cost

ii. Highest (most centralized) maintenance echelon where the repairman is special

5) Is the repairman military, Government civilian, or Contractor civilian? If the repairman is Contractor civilian, the following shall be provided:

i. Average fully loaded (indirect, G&A, and profit included) hourly labor rate

ii. Expected turnover period in years

h. The following shall be provided for each repairable LRU contained within the end item:

1) Identification

2) Unit price

3) Total number of this particular LRU within the end item

4) Packaged shipping weight

5) Is the item essential to the operation of the end item?

6) Does the item have an NSN?

7) Washout rate

8) False removal rate

9) MTBF in operating hours

10) MTTR in labor hours

11) Diagnostic time contained within MTTR

12) Number of pages of technical documentation required to perform repair

13) Test Program Set (TPS) software development cost

14) Expected annual TPS maintenance cost

15) Test equipment/repairmen required to perform repair, and the amount of time required by each

16) When the LRU is repaired at a Contractor facility, additionally provide the following:

i. Contractor Response Time (i.e., Turnaround Time)

ii. Contractor Washout Rate

iii. Contractor Set Up Cost - one time fixed cost

iv. Total Contractor Cost per Failure

v. Total Contractor Cost per False Pull

17) If the LRU is redundant within an end item, additionally provide the number of this LRU needed within the end item to be operable

i. The following shall be provided for each throwaway LRU contained within the end item:

1) Identification

2) Is the throwaway item essential to the operation of the end item?

3) False removal rate

4) Total number of items making up the throwaway item. A throwaway item may be a single item or it may be a group of miscellaneous items. For example, if an end item has 100 different throwaway cables, instead of entering 100 separate cables, the cables can be modeled as a single miscellaneous cable representing 100 individual cables.

5) The number of parts in paragraph (4) needing NSNs

6) The unit price of the throwaway item or the average unit price for the miscellaneous throwaway item

7) The weight of the throwaway item or the average weight for the miscellaneous throwaway item

8) The MTBF of the throwaway item or the total MTBF of all items making up a miscellaneous throwaway item

If MTBF(i) is the MTBF of item i, then the total MTBF, MTBF(t), is computed as follows:

MTBF(t) = 1 / [ 1/MTBF(1) + 1/MTBF(2) + ... + 1/MTBF(n)] - where n is the total number of items making up the throwaway item.

j. The following shall be provided for each repairable SRU contained within the end item:

1) The same data as for LRUs in paragraph h [omit 9) “MTBF in operating hours” which is requested separately in paragraph l]

2) Average price of piece parts used in each repair action of the SRU

3) Number of piece parts needing an NSN

k. The same information shall be provided for each miscellaneous throwaway SRU as for a miscellaneous throwaway LRU described in paragraph i, excluding 8) the MTBF which is requested separately in paragraph l.

l. The following information, known as an application, shall be given for each repairable and throwaway SRU.

1) SRU identification

2) Identification of the LRU it goes into

3) MTBF in operating hours of the SRU in the LRU

Note: An application is the specification of a LRU and a SRU contained within the LRU.

Since a given SRU may be part of different LRUs, it may appear in several applications.

The failure rate of the SRU depends not only on the SRU itself, but also on where it is installed or applied. However, multiple occurrences of a SRU in the same LRU should be entered as one application. The specified MTBF for this application should represent the combined MTBF of all occurrences of the SRU in the one LRU. Since each repairable LRU must contain at least one SRU, it must be listed with at least one application.

Similarly, since each SRU (whether repairable or not) must be part of a LRU, each SRU must be listed with at least one application.

m. If any LRU or SRU is to be screened for false removals before being either thrown away or repaired at a higher maintenance echelon, provide the following for each such item:

1) Identification

2) The lowest echelon at which screening can be done

3) Screening detection fraction (the fraction of false removals that are detected by screening)

4) The average amount of time required to screen the item

5) Development cost of software for a go/no-go (end-to-end) TPS. (This cost should be less than the cost for a full repair TPS because it is assumed that the go/no-go TPS is a subset of the repair TPS)

6) Expected annual TPS maintenance cost

7) Test equipment/repairmen required to screen the item, and the amount of time required by each

3.4 Installation Specification

The contractor shall prepare a D3 Installation Specification as part of the proposal IAW CDRL F001. The Installation Specification shall provide that information required by the host platform system integrator to integrate the D3 into the host platform. Information that is contained in the ICD is not required to be included in the Installation Specification. The Installation Specification shall include information concerning the requirement for periodic software updates, how to determine what version of software is loaded on the D3, how to determine what the appropriate version of the software is and how to obtain and install it. The Installation Specification shall also include a list of all proposed testing devices/equipment (if applicable) and where to obtain them or how to build them.

3.5 Technical Manual

The Contractor shall provide a technical manual IAW CDRL C001.

3.6 Safety Assessment

The D3 shall meet the safety specification requirements as defined in the PRF. The contractor shall identify precautions or specific controls to be followed when installing or integrating the D3 and shall identify, evaluate, track, and control to an acceptable level of risk the aspects of system safety, including software safety, associated with the set-up, testing, and operation of the D3.

The contractor shall evaluate any potential safety related issues reported by the host platform system integrator after delivery of the item and provide recommended corrective measures or implement corrective measures in the D3 as required under the contract. Safety issues shall be discussed and resolved at Safety Assessment WIPTs. Issues that cannot be resolved by the WIPT will be elevated to the Program IPT.

3.6.1 Safety Assessment Report (SAR)

The Offeror shall submit a safety statement as part of the proposal IAW P001 that describes the hardware safety features of the D3, identify any potential hazards, and specify any precautions to be taken by Government personnel during bid sample demonstration.

The contractor shall prepare a SAR IAW CDRL P001. The SAR shall document the safety risk being assumed prior to test or operation of the D3. Non-compliance of safety specification requirements shall be documented and justified. Justification for noncompliance is not to be construed as approval by the Government; noncompliance requires separate written approval by the Government. The SAR shall identify all safety features of the D3 hardware and software design, precautions or specific controls to be followed when installing or integrating the D3 into a weapons system, specific controls or precautions to be followed in the use of the sub-system;

and shall provide verification of compliance to safety requirements identified in the system specification. The contractor shall attach a completed System Safety Design Verification Checklist, the completed Software Hazard Analysis, and Material Safety Data Sheets (MSDS) for all hazardous materials.

3.6.2 Toxic Substances

The SAR shall identify toxic and environmentally unacceptable materials used in the D3, any possible alternative materials, and recommended actions to eliminate or reduce the use of hazardous materials. The SAR shall address any exposure concerns to personnel during operational or maintenance procedures to include fabrication, transportation, setup and tear down, or resulting from damage to the equipment. The contractor shall identify any material used in the D3 design that requires disposal as a hazardous waste.

3.6.3 Hazard Tracking

The contractor shall implement a suitable means of recording and tracking any safety hazards related to the operation and maintenance of the D3 to ensure that all hazards are identified, assessed, the proper program managers and personnel notified. All hazards shall be included in this hazard log and shall be tracked until final resolution. The hazard log shall be included in the SAR and shall contain the following information for each hazard as a minimum:

a. A description of the hazard.

b. Life cycle phases during which the hazard will be experienced (i.e., transportation, installation or preparation for use, training, operation or use, tear down or packing, maintenance, storage, disposal, etc.).

c. Initial hazard risk assessment code (hardware) or Software Hazard Criticality Matrix assessment code (software).

d. Status of actions taken to eliminate or control hazard.

e. Final actions on each hazard that reduces the level of risk to an acceptable level. These final actions shall be approved by the CECOM Safety Office.

f. Final hazard risk assessment code.

3.6.4 Safety Inspection/Verification

The contractor shall schedule sufficient time in the program schedule to permit a safety inspection of the D3 by the Government prior to developmental or soldier involved operational testing and associated training, or contract completion. The inspections will be used to verify the information contained in the SAR. The contractor must allow sufficient time to correct any unresolved high or medium risk hazards before testing or delivery of the D3 to the Government.

3.7 Contract Status Reporting

The contractor shall provide contract status reports IAW CDRL E003. The reports shall include all significant contract activities critical to contract performance. Each report shall be a summary of activities, accomplishments, problems and resolutions occurring during the reporting period. The report shall also include a summary of telephone support hours used/remaining.

Government acceptance of the reports does not assume Government concurrence with the report’s contents or an agreement to revise schedules or the terms of the contract.

3.8 Integrated Master Schedule

The contractor shall maintain an Integrated Master Schedule (IMS) IAW CDRL E001. This requirement shall include reports due within 30 days of receipt of each Delivery Order to provide the Government a schedule of planned deliveries for items or services procured on each DO.

Delivery updates to DO schedules may be provided as part of the Contract Status Report.

3.9 Frequency Allocation Data

The contractor shall provide data as part of the proposal IAW CDRL D001 to facilitate the Government’s development of the frequency allocation DD Form 1494.

4. CONTRACT DATA REQUIREMENTS LIST (CDRL)

CDRL NO. TITLE / SUBTITLE DID NO. PWS PARA

A001 Test Procedure / Product Acceptance

Testing

DI-NDTI-80603A 3.1.2.1

B001 Conference Minutes / Meeting Minutes DI-ADMN-81250A 3.1.3.2 C001 Commercial Off-the-Shelf (COTS) Manuals and Associated Supplemental Data

DI-TMSS-80527C 3.5

D001 Frequency Allocation Data DI-MISC-81174 3.9 D002 Technical Report – Study/Services /

Training Certificates

DI-MISC-80508B 3.1.10.1,

3.1.10.3 D003 Technical Report – Study/Services /

Level of Repair Analysis Input Data

DI-MISC-80508B 3.3.7

E001 Integrated Master Schedule (IMS) DI-MGMT-81650 3.8 E002 Operations Security (OPSEC) Plan DI-MGMT-80934C 3.1.10.2 E003 Status Report / Contract Status Report DI-MGMT-80368A 3.7 F001 Installation Specification DI-QCIC-80510 3.4 G001 Software Version Description (SVD) DI-IPSC-81442A 3.3.5 G002 Software Development Plan (SDP) DI-IPSC-81427A 3.3.5 H001 Computer Software Product End Items DI-MCCR-80700 3.3.5 J001 Engineering Change Proposal (ECP) DI-CMAN-80639C 3.1.6.2, 3.1.6.3.1

K001 Supplemental Data For Provisioning (SDFP) DI-ALSS-81557 3.3.2 L001 Performance Specification Documents DI-SDMP-81465A 3.1.1 M001 Instructional Media Package / Computer

Based Training

DI-SESS-81526B/T 3.1.4

M002 Failure Analysis and Corrective Action Report (FACAR)

DI-SESS-81315B 3.1.2.2

N001 Warranty Performance Report DI-MNTY-81217 3.1.5 P001 Safety Assessment Report (SAR) DI-SAFT-80102B 3.6.1

5. ACRONYMS

Acronym Description

ASAC Assistant SAASM Account Custodian

AT Antiterrorism

ATEC Army Test and Evaluation Command

CAGE Commercial and Government Entity

CDRL Contract Data Requirements List

CC

CCA

Contracting Command

Circuit Card Assembly

CCB Configuration Change Board

CCI Cryptographic Controlled Item

CI Configuration Item

CLA Core Logistics Analysis

CLIN Contract Line Item Number

COMPASS Computerized Optimization Model for Predicting and Analyzing Support Structures

COMSEC Communications Security

COR Contracts Officer Representative

CPM Computer Programming Manual

CSCI Computer Software Configuration Item

D3 DAGR Distributed Device

DAC Days After Contract award

DAGR Defense Advanced GPS Receiver

DCMA Defense Contract Management Agency

DO Delivery Order

DOTMLPF Doctrine, Organization, Training, Materiel, Leadership and Education, Personnel and Facilities

DTS Defense Transportation System

ECP Engineering Change Proposal

EMC Electromagnetic Compatibility

EMI Electromagnetic Interference

ESS Environmental Stress Screening

FACAR Failure Analysis and Corrective Action Report

FAT First Article Test

FOUO For Official Use Only

GB-GRAM Ground-Based GPS Receiver Application Module

GFE Government Furnished Equipment

GPS Global Positioning System

GSSIP GPS Standard Serial Interface Protocol

GTR ORD GPS Tactical Receiver Operational Requirements Document

HAE Host Application Equipment

IAW In Accordance With

ICD Interface Control Document

ICS Interim Contractor Support

IOT Initial Operation Test

IMS Integrated Master Schedule

IPT Integrated Product Team

IUID Item Unique Identification

KDP Key Data Processor

KLIF KDP Loading and Installation Facility

KO Contracts Officer

LORA

LRU

Level of Repair Analysis

Line Replaceable Unit

LUT Limited User Test

M-Code Modernized GPS Code

MGUE Military GPS User Equipment

MSDS

MTBF

MTTR

Material Safety Data Sheets

Mean Time Between Failure

Mean Time to Repair

NIE Network Integration Evaluation

NIR Network Integration Rehearsal

NLT No Later Than

NSN National Stock Number

NSPD National Security Presidential Directive

OPSEC Operations Security

PBUSE Property Book Unit Supply Enhanced

PD PNT Product Director Positioning Navigation and Timing

PDF Portable Document Format

PNT Positioning, Navigation and Timing

PNTCAP Positioning, Navigation and Timing Capabilities

PPS Precise Positioning Service

PRD Process Requirements Document

PRF Performance Specification

PWS Performance Work Statement

RFID Radio Frequency Identification

SAASM Selective Availability/Anti-Spoofing Module

SAC SAASM Account Custodian

SAR Safety Assessment Report

SCG Security Classification Guide

SDFP Supplemental Data for Provisioning

SDP Software Development Plan

SE Support Equipment

SOP Standard Operating Procedure

SPS

SRU

Software Product Specification

Shop Replaceable Unit

STrP Software Transition Plan

SUE System Under Evaluation

SUT System Under Test

SUD System Under Demonstration

T&E Test and Evaluation

TAT Turn Around Time

TBD To Be Determined

TPF

TPS

Total Package Fielding

Test Program Set

TRL Technology Readiness Level

TRR Test Readiness Review

VTC Video-Teleconference

WIPT Working Integrated Product Team

WRALC Warner Robins Air Logistics Center