Amendment 0001_15R0005.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

SEE NEXT PAGE

1. CONTRACT ID CODE PAGE OF PAGES

U 1 64

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

16C. DATE SIGNED

BY 19-Jul-2016

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 N65236-15-R-0005

X 9B. DATED (SEE ITEM 11)

24-Jun-2016

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 is extended, X 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 1 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

19-Jul-2016

CODE

US NAVY SPAWARSYSCEN ATLANTIC CHARLESTON

PO BOX 190022 DIVISION 2.2.53

843-218-3556

ADAM.SOLIVAN@NAVY.MIL

NORTH CHARLESTON SC 29419-9022

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N65236-15-R-0005

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

NOTE: Page 1 should read Page 1 of 61

SUMMARY OF CHANGES

AMENDMENT 0001 NOTES

Solicitation N65236-15-R-0005 is hereby amended as follows:

1. PWS Paragraph 7.1.1 is revised to remove incorrect reference to PWS Paragraph 3.5. See revisions to PWS below.

2. The personnel qualification for the Management Analyst 3 labor category has been revised to require a “Bachelor’s degree in computer science, business, or other related fields from an accredited college or university.” See revisions to Clause 5252.237‐9600 below.

3. The “Small Business Subcontracting Plan” paragraph in Provision L‐317 is revised to require the submission of the Subcontracting Plan as a separate file. See revisions to Provision L‐317 below.

4. References to Historically Black Colleges and Universities (HBCU) and Minority Institutions (MI) have been removed from Provision L‐317, Factor C and Provision M‐307, Factor C. See revisions to Provisions L‐317 and M‐307 below.

5. Attachment 5A, Prime Pricing Model is revised to separate the hours for Engineer/Scientist 3 – General and Engineer/Scientist 3 – Systems/Software Engineer (See revised attachment).

6. Attachment 5B, Subcontractor Pricing Model is revised to correct a formula error on the “Labor Cost” tab (See revised attachment).

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

SECTION C – DESCRIPTION/SPECS/WORK STATEMENT

SPECIFICATIONS/STATEMENT OF WORK/PERFORMANCE WORK STATEMENT

Work under this performance-based contract shall be performed in accordance with the following description/ specifications/ statement of work (SOW) which herein shall be referred to as Performance Work Statement (PWS).

1.0 PURPOSE

1.1 BACKGROUND

The Joint Warfare Support Division (JWSD) is a SPAWARSYSCEN Atlantic Field Activity with offices located in Tampa FL, Fayetteville NC, and Charleston SC. The primary mission of the JWSD is to support the Joint Warfighters and their infrastructure. JWSD is engaged in work that includes integration, test and evaluation, fielding, training, certification, maintenance, life-cycle sustainment management support and field service technical support of Tagging, Tracking, and Locating (TTL) equipment for various Joint Warfighter customers. The TTL support requires that the government have the adaptability and flexibility to procure technical surveillance systems and sensors from multiple sources, field, and train these systems in near real-time. In many cases, the window of opportunity for success is less than 60 days from the time of the requirement notification. This means that SPAWAR must have the systems ordered, fielded, and personnel trained within 60 days of receipt of requirement.

1.2 SCOPE

This PWS covers the procurement and/or manufacture of Commercial-Off-The-Shelf (COTS) and Non- Developmental Item (NDI) TTL equipment. Also included will be logistic support from accountability to air time and specialized training and field service technical support for the TTL equipment.

NOTE: Work will be performed in Afghanistan.

2.0 APPLICABLE DOCUMENTS (AND DEFINITIONS)

All work shall be accomplished using the best commercial practices and current acceptable industry standards. The applicable references and standards invoked will vary within individual tasks and will be specifically called-out in each delivery/task order (DO/TO). In accordance with the Defense Acquisition Policy changes, maximum utilization of non-governmental standards will be made wherever practical. Where backward compatibility with existing systems is required, selected interoperability standards will be invoked. For purposes of bidding, the following documents are not exclusive; however, all contractors shall be able to meet those cited when applicable to the delivery/task order.

2.1 REQUIRED DOCUMENTS

The following instructional documents are mandatory for use. Unless otherwise specified, the document’s effective date of issue is the date on the request for proposal. Additional applicable documents may be included in specific delivery/task orders.

Document Number Title

a. DoD 5220.22-M DoD Manual – National Industrial Security Program

Operating Manual (NISPOM) dtd 28 Feb 06

b. DoDI 5220.22 DoD Instruction – National Industrial Security Program dtd

18 Mar 11

c. DoD 5200.2-R DoD Regulation – Personnel Security Program dtd Jan 87

d. DoDD 5205.02E DoD Directive – Operations Security (OPSEC) Program dtd 20 Jun 12

e. DoD 5205.02-M DoD Manual – Operations Security (OPSEC) Program

Manual dtd 3 Nov 08

f. DoDI 6205.4 Department of Defense Instruction, Immunization of Other

Than U.S. Forces (OTUSF) for Biological Warfare Defense

g. DoDI 8500.01 DoD Instruction – Cybersecurity dtd 14 Mar 14

h. DoDI 8510.01

DoD Instruction – Risk Management Framework (RMF) for DoD Information Technology (IT) dtd 12 Mar 14

i. DoDD 8570.01 DoD Directive – Information Assurance Training, Certification, and Workforce Management dtd 15 Aug 04

j. DoD 8570.01-M

Information Assurance Workforce Improvement Program dtd 19 Dec 05 with Change 3 dtd 24 Jan 12

k. SECNAV M-5239.2 DON Information Assurance Workforce Management Manual dtd May 2009

l. SECNAV M-5510.30 Secretary of the Navy Manual – DoN Personnel Security Program dtd Jun 2006

m. SECNAVINST 4440.34 Secretary of the Navy Instruction – Implementation of Item Unique Identification within the DoN, dtd 22 Dec 09

n. SECNAVINST 5239.3B DoN Information Assurance Policy, 17 Jun 09

o. SECNAVINST 5510.30 DoN Regulation – Personnel Security Program

p. SPAWARINST 3432.1 SPAWAR Instruction – Operations Security (OPSEC)

Policy dtd 2 Feb 05

q. SPAWARINST 4440.12 Management of Operating Materials and Supplies (OM&S), Government Furnished Property (GFP), Contractor Acquired Property (CAP), Property, Plant and Equipment (PP&E), and Inventory

r. SPAWARINST 5721.1B SPAWAR Section 508 Implementation Policy, 17 Nov 09

s. NAVSUP P-723 Navy Inventory Integrity Procedures, April 2012

t. NIST SP 800-Series National Institute of Standards and Technology Special

Publications 800 Series – Computer Security Policies, Procedures, and Guidelines

u. COMUSFLTFORCOM/COM

PACFLTINST 6320.3A

Commander US Fleet Forces Command/Commander US Pacific Fleet Instruction, Medical Screening For US Govt Civilian Employees, Contractor Personnel, and Guests prior to embarking Fleet Units, of 7 May 13

2.2 GUIDANCE DOCUMETNS

The following documents are to be used as guidance. Unless otherwise specified, the document’s effective date of issue is the date on the request for proposal. Additional applicable documents may be included in specific delivery/task orders.

a. MIL-HDBK-61A Configuration Management

b. MIL-STD-130N DoD Standard Practice – Identification Marking of US

Military Property

c. MIL-STD-881C Work Breakdown Structure for Defense Materiel Items

d. MIL-STD-1916 DoD Test Method Standard – DoD Preferred Methods for

Acceptance Of Product

e. DoDI 3020.41 DoD Instruction – Operational Contract Support (OCS), of

20 Dec 10

f. DoDI 4161.02 DoD Instruction – Accountability and Management of

Government Contract Property, Apr 27,2012

g. DoDD 5000.01 DoD Directive – The Defense Acquisition System

h. DoDI 5000.02 DoD Instruction – Operation of the Defense Acquisition

System

i. ISO 9001 (ANSI/ASQ Q9001) International Organization for Standardization (American

National Standard Institute/American Society for Quality) – Quality Management Systems, Requirements

j. ISO/IEC 12207 International Organization for Standardization/ International Electrotechnical Commission: Systems and Software Engineering – Software Life Cycle Processes

i. ISO/IEC 15288 International Organization for Standardization/ International Electrotechnical Commission: Systems and Software Engineering – System Life Cycle Processes

j. IEEE Std 12207-2008 Systems and Software Engineering – Software Life Cycle Processes

k. ANSI/EIA-748A America National Standards Institute/Electronic Industries Alliance Standard – Earned Value Management (EVM) Systems

l. HSPD-12 Homeland Security Presidential Directive – Policy for a Common Identification Standard for Federal Employees and Contractors, August 27, 2004

m. DoDM-1000.13-M-V1 DoD Manual – DoD Identification Cards: ID card Life-

Cycle dtd 23 Jan 14

n. FIPS PUB 201-2 Federal Information Processing Standards Publication 201-

2 – Personal Identity Verification (PIV) of Federal Employees and Contractors, August 2013

o. Form I-9, OMB No. 115-0136 US Department of Justice, Immigration and Naturalization Services, Form I-9, OMB No. 115-0136 – Employment Eligibility Verification

p. N/A SSC Atlantic Contractor Checkin portal – https://wiki.spawar.navy.mil/confluence/display/SSCACO G/Contractor+Checkin

q. N/A SSC Atlantic OCONUS Travel Guide portal – https://wiki.spawar.navy.mil/confluence/display/SSCACO G/OCONUS+Travel+Guide

r. SPAWARSYSCENLANTINS T 12910.1A

Deployment of Personnel and Contractor Employees to Specific Mission Destinations, of 28 Dec 09

2.3 SOURCE OF DOCUMENTS

The contractor shall obtain all applicable documents. Specifications and commercial/industrial documents may be obtained from the following sources:

Copies of Federal Specifications may be obtained from General Services Administration Offices in Washington, DC, Seattle, San Francisco, Denver, Kansas City, MO., Chicago, Atlanta, New York, Boston, Dallas and Los Angeles.

Copies of military specifications may be obtained from the Commanding Officer, Naval Supply Depot, 3801 Tabor Avenue, Philadelphia, PA 19120-5099. Application for copies of other Military Documents should be addressed to Commanding Officer, Naval Publications and Forms Center, 5801 Tabor Ave., Philadelphia, PA 19120-5099.

All other commercial and industrial documents can be obtained through the respective organization’s website.

3.0 PERFORMANCE REQUIREMENTS

The following paragraphs list all required support tasks that shall be required throughout the contract life. The contractor shall provide necessary resources and knowledge to support the listed tasks. Specific objectives shall be dependent on the basic contract and the DO/TO written against the basic contract. The contractor shall complete all required tasks while controlling and tracking performance and goals in terms of costs, schedules, and performance.

Note: In compliance with SPAWARINST 4720.1A – SPAWAR Modernization and Installation Policy, all contract installation work performed aboard Navy ships and Navy shore sites is under Installation Management Office supervision; otherwise, a formal exemption request has been approved. In accordance with the Fleet Readiness Directorate Standard Operating Procedure, COMSPAWARSYSCOM letter Ser FRD/235 dated 24 Apr 12, the contractor shall, ensure proper notification and status updates of installation work performed outside of SSC Atlantic respective Areas of Responsibilities are provided to the SPAWAR Officer in Charge or applicable Geographic Lead.

3.1 SYSTEMS AND EQUIPMENT

The contractor shall be responsible for the acquisition of TTL equipment in accordance with the specifications provided by the government. All items shall conform to applicable product validation, security, identification, and tracking requirements. Those contractors whose products do not meet the required validation, security, identification, and tracking requirements shall not be considered for award.

The contractor shall provide the equipment, accessories, and all associated documentation such as:

operator/maintenance manuals, technical specifications, parts lists, drawings, installation instructions, etc. (CDRL A001). Each DO request shall specify the specific equipment performance requirements or brand name product and the minimum delivery schedule for each item ordered. The contractor shall be required to establish purchasing agreements either directly with the OEMs or their distributors in order to provide rapid acquisition services for this equipment. Prime Contractors are prohibited from entering into and/or maintaining any exclusive teaming arrangements that will affect the SPAWARSYSCEN Atlantic TTL MAC contract (See PWS Para 3.1.7).The contractor shall obtain pricing information, prepare supporting documentation, and determine the expected delivery date for all procurement items. Government approval will be required prior to ordering the material.

3.1.1 TTL Categories

The following list provides a minimum representation of the TTL categories that shall be made available under this contract. The categories listed are NOT all inclusive, but provide a representation of the various types of TTL equipment that the Government anticipates requirements for under this contract.

(a) Sensitive Site Exploitation Systems Sensitive site exploitation systems are composed of dataloggers, beacons, audio surveillance systems and video surveillance systems. Depending on need, each device may be used by itself or as a component complimenting a system configuration for a particular mission. These devices are used in many applications such as tracking shipments, route navigation assistance, supervising prisoners, studying animal behavior and also serve as a tool for law enforcement.

(b) Dataloggers Dataloggers are electronic devices that record and store current/historic geographic locations by collecting GPS signals from Low Earth Orbit satellites. Typically, dataloggers are grouped into two categories: passive and active.

Data can be extracted from these devices by recovering and physically downloading (Passive data logger) or by preprogramming the device to send a communication signal via Radio Frequency (RF), satellite, or Internet Protocol (IP) with its historical data (active data logger). Both types of devices collect, receive, and store a large quantity of historical positional data.

Within the law enforcement community, dataloggers can be used in a concealed fashion on objects and vehicles or as body worn tags. The devices can be programmed to transmit its records via line of site transmission, cellular telephone networks, or satellite communications.

(c) Beacons Beacons are devices that transmit a characteristic signal either optically (Infra-red, Ultra violet or visible spectrum) or by radio to a direction finding device or operator. Similar to dataloggers, beacons can be concealed and can function as a passive or an active device. Beacons and their associated devices can be interrogated remotely to obtain its recorded location. Like dataloggers, beacons can be vehicle, aircraft, vessel or body worn.

(d) Audio Surveillance Systems Audio surveillance systems enable users to record conversations in either a self-contained manner or via wireless transmission configuration that involves a battery operated microphone and transmitter. These systems are small and can be either body worn or mounted and concealed in hard to detect locations. Typically, a system can be composed of a microphone, an analog or digital recorder/receiver, a wireless transmitter, as well as background noise filtering and speech extraction software.

(e) Video Surveillance Systems Video surveillance systems enable users to record, using small black and white or color cameras, in either a self-contained manner or via wireless transmission configuration that involves using a battery operated camera with and without audio capability, a transmitter/recorder and a video monitor. These systems are typically small and can be either body worn or mounted and concealed in hard to detect locations. Analog or digital recorded material can be securely transmitted wirelessly to a nearby receiver or can be hardwired to a recorder. Output formats are mainly MPEG 4 which is a common international standard. However, image processing, compressing and image enhancing software for exploiting recorded video and still images allows the system to meet technical surveillance capability.

(f) Secure Communications Secure communications systems for tactical applications to include voice, data, cellular, wireless, satellite, computer networks and other technical approaches.

(g) Computer Forensic Exploitation Systems Computer forensic exploitation systems for use in the field consist typically of small, portable equipment for use with notebook or personal data assistants. These devices allow recovering data stored on laptops or desktops by either bypassing passwords, transferring stored data to another computer system, or by obtaining passwords to computer systems in an effort to avoid data loss.

(h) Sensor Systems Sensor systems are switching systems that physically detect a change in its current working environment. Among these physical changes are motion detection, seismic detection, magnetic detection, acoustic detection, time lapse and still imaging. Upon detection, the sensor can serve as an interface to power up or down other systems connected to it; for example, unattended activation of the audio and video systems.

3.1.2 Quick Reaction Capability

Occasionally, the contractor shall be required to provide specialized TTL devices to take advantage of emergent requirements. Typically, these opportunities will require a small number of very specialized TTL devices. The contractor shall be responsible for identifying the technical solution that will meet the mission requirements, developing concealments, acquiring the devices, and providing it to the government on an accelerated basis. This quick reaction capability is not intended to be a Research and Development (R&D) effort; rather an opportunity to meet emergent requirements with existing COTS/NDI TTL devices.

3.1.3 Equipment and Material Support

As specified on DO/TOs, the contractor shall provide various equipment/material support that ranges from research, procurement, fabrication, integration, and delivery.

3.1.3.1 Equipment/Material Research

The contractor shall research specified equipment and/or material within the parameters outline at the DO/TO.

3.1.3.2 Equipment/Material Procurement

In accordance with SPAWARINST 4440.12, the contractor shall procure items listed under the Contractor Acquired Property (CAP) paragraph. Acquisition selection factors shall include price, availability, reliability, and supportability within current supply system. This information shall be tracked and available for government review as needed. The contractor shall provide all support data and cost estimates necessary to justify a fair and reasonable price per item procured. The contractor shall have an adequate accounting system to track all items and the delivery status per DO/TO and per item. After receipt, the contractor shall have an adequate property management system to track the item location per DO/TO per item. Unless otherwise noted, all items procured by the contractor shall be stored at the contractor’s facilities and integrated into a system or transported by the contractor as directed in each DO/TO. As required, the contractor shall be responsible for generating inventory tracking report(s) (CDRL A002) for the basic contract and/or each DO/TO summary report. Deliverable documentation shall vary and be specified in each DO/TO, if applicable.

Contractor shall recommend items that conform to applicable product validation, identification, and tracking requirements.

(a) Product Validation – The contractor shall certify that it purchases supplies from authorized resellers and/or distributers. Unless otherwise specified, the contractor shall warrant that the products are new, in their original box.

The contractor shall obtain all manufacturer products submitted in task/delivery order offers from authentic manufacturers or through legal distribution channels only, in accordance with all applicable laws and policies at the time of purchase. The contractor shall provide the Government with a copy of the End User license agreement, and shall warrant that all manufacturer software is licensed originally to Government as the original licensee authorized to use the manufacturer software. This information shall be tracked and available for government review as needed.

(b) Cybersecurity/Computer Security Requirements – The contractor shall ensure that all products recommended and/or procured that impact cybersecurity or Information Assurance (IA) shall be selected from the NIAP Validated Products List. The products chosen shall be based on the appropriate Evaluated Assurance Level (EAL) for the network involved, and utilized in accordance with latest Defense Information Systems Agency (DISA) policy at time of order. This information shall be tracked and available for government review as needed.

(c) Item Unique Identification (IUID) and Radio Frequency Identification (RFID) – In accordance with DFARS 252.211-7007 and SECNAVINST 4440.34, the contractor shall ensure that all items purchased with a unit cost equal to or exceeding $5,000 (or less if item is serially managed or if government specifies items on individual task/delivery orders) is labeled with an item unique identification number or Unique Item Identifier (UII). At time of delivery of the item to the Government, the contractor shall clearly mark and identify each applicable item based on the criteria provided in DoD MIL-STD-130N for those items not already marked. If specified in individual task/delivery orders, the contractor shall provide Radio Frequency Identification (RFID) in accordance with Under Secretary of Defense Memo Radio Frequency Identification (RFID), July 30, 2004. All IUID information shall be recorded and shall be subject to government review as needed. The contractor shall track IUID items and maintain information being recorded.

(i) Contractor shall enter all items with Unique Item Identifier (UII) in the IUID Registry. Data is either submitted via Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT) (formerly Wide Area Workflow (WAWF)) as part of the Material Inspection and Receiving Report.

(ii) Contractor shall be responsible maintaining and updating information in the IUID Registry. Contractor shall update custody status when items are designated as government furnished material, returned to government position, change physical location, or has been consumed, destroyed, scrapped, lost or abandoned during contract, DO/TO performance.

3.1.3.3 Property/Inventory Tracking

In accordance with FAR 52.245-1, the contractor shall create and maintain internal records of all government property accountable to the contract, DO/TO; including Government-furnished and Contractor-acquired property.

Each item delivered and/or ordered shall be recorded in an inventory tracking report (CDRL A002). At a minimum, the report shall track the following information: item description, order date, serial number, model number, lot number, delivery location, and the manufacturer warranty period and expiration date, if applicable. This information shall be tracked and available for government review as needed, and the information shall have the ability to be sorted and manipulated by any of the input fields. Separate from the government tracking system, the information in the contractor’s records is a backup to the government records; therefore, the government will own all data rights to the collected information.

3.1.4 Warranty Tracking of Serialized Items

As specified in DFARS 252.246-7006 and Instructions for Electronic Submission of Warranty Tracking and Administration Information for Serialized Items (see CDRL A003 Attachment 1), the contractor shall follow the requirements for any serialized item manufactured or acquired that come with a warranty:

3.1.4.1 For government specified warranty terms, the government will complete certain fields on the Warranty Tracking Information (WTI) form and Warranty Source of Repair Instructions (WSRI) form and electronically forwarded them to contractor. The contractor shall complete the remaining sections of the WTI and WSRI and forward the forms (CDRL A003) to the Contracting Officer and COR at time of delivery of the warranted serialized item(s).

3.1.4.2 For contractor/vendor specified warranty terms, the contractor shall complete all data elements for both the WTI and WSRI and shall forward the forms (CDRL A003) electronically to the tech code. The WTI shall be returned to the Contracting Officer and COR at contract/TO award. The WSRI shall be returned to the Contracting Officer and COR at contract/TO award or at time of delivery of the warranted serialized item(s).

3.1.4.3 For receipt and acceptance of items, the contractor shall comply with the following requirements:

(a) If the WTI and WSRI are submitted manually (as a PDF file), the contractor shall forward documents to COR for review. As required, contractor shall forward approved documents to government personnel responsible for posting the forms to Electronic Data Access (EDA).

(b) If utilizing Wide Area WorkFlow (WAWF), the contractor shall ensure that the required warranty data is electronically submitted using the Contract Data Requirements List (CDRL) exhibit line item number (ELIN) functionality for the WAWF Materiel Inspection and Receiving Report or WAWF Reparable Receiving Report, as applicable.

3.1.5 Warranty Management

The contractor shall serve as the warranty manager by tracking the applicable government acceptance dates/receipt dates against the serial number of equipment or the lowest replaceable unit of a system. As warranty manager, the contractor shall, unless otherwise directed, submit warranty data on Warranty Tracking Information form and Warranty Source of Repair Instructions as specified on the Warranty Tracking and Administration for Serialized Items (CDRL A003). As directed in the TO, the contractor shall upload data to the Wide Area WorkFlow Materiel Inspection and Receiving Report (or WAWF Reparable Receiving Report, if appropriate).

The contractor shall use a government owned or government approved data base to maintain and track warranty life spans for all items ordered. The warranty tracking log shall track items by serial numbers and shall be updated monthly to identify the time left on the original warranty. When an item has failed, the contractor shall determine if the item is still under warranty. If the item is under warranty, the contractor shall obtain a Return for Maintenance Authorization (RMA) number and instructions on how to get the product repaired or replaced. The contractor shall provide the government a copy of the warranty information tracking log as an attachment to the monthly status report (CDRL A004). The warranty tracking functions shall be included in the cost of the equipment. If an extended warranty is available as a purchase option the contractor shall notify the government of the added cost and must gain approval prior to obtaining the extended warranty. Items that are no longer covered by warranty will be returned to the contractor for repair under separate maintenance agreements or replacement.

When an item that is no longer under warranty fails, the contractor shall contact the Original Equipment Manufacturer (OEM) to determine the price for repair. The contractor shall provide the government with the cost estimate and, if the government decides that the repair is feasible, the government shall provide funding to cover the cost of shipping and item repair. The contractor shall provide an expected repair date and inform the government when the equipment will be back in service. The contractor shall also track software and firmware updates for equipment that needs to be upgraded or as recommended by the OEM. Procurement of these software and firmware upgrades shall require government authorization.

3.1.5.1 If there is no compatible government data base to maintain and track warranty life spans for the Government furnished property and/or Contractor acquired property under contract, the contractor shall internally track items by delivery/task order (if applicable), serial numbers, and the information shall be updated monthly to identify the time left on the original warranty. The contractor shall provide the government a copy of the warranty information in an inventory tracking report (CDRL A002).

3.1.5.2 When an item has failed, the contractor will determine if the item is still under warranty. If the item is under warranty, the contractor shall obtain a Return for Maintenance Authorization (RMA) number and instructions on how to get the product repaired or replaced from the manufacturer or authorized distributor. As required a Warranty and Non-Warranty Failure Status Repair Report (CDRL A003) shall be submitted to the COR on all warranty and non-warranty actions taken during the preceding quarter and collected cumulatively.

3.1.6 Maintenance

The contractor shall establish maintenance agreements with all of the product vendors to allow for repairable equipment that is out of warranty to be serviced or repaired. The contractor shall have maintenance agreements with all product vendors from which repairable equipment has been procured using this contract. The status of all items undergoing repair shall be provided as an attachment to the monthly status report (CDRL A004).

3.1.7 Exclusive Teaming Arrangement Prohibition

(a) Definition. An exclusive teaming arrangement is created when two or more companies agree, through understandings, or by any other means to team together to pursue the SPAWARSYSCEN Atlantic TTL MAC contract, and further agree not to team with other competitors under the contract.

(b) Prohibition. Prime Contractors are prohibited from entering into and/or maintaining any exclusive teaming arrangements that will affect the SPAWARSYSCEN Atlantic TTL MAC contract. SPAWARSYSCEN Atlantic has determined that such arrangements unduly limit competition and do not provide the best value to the Government.

Corporate or company capabilities below the prime contractor level that are essential to contract performance must be made available on fair and equitable terms to all competitors. The Government will direct the dissolution of any exclusive teaming arrangement which the Contracting Officer discovers, or prohibit the contractor from award consideration for future DO/TOs.

3.2 PROGRAM MANAGEMENT

The contractor shall work closely with the Government project manager (PM) and when applicable provide support at the sponsor level.

3.2.1 Program Support

Some programs shall require a contractor to work closely with the government PM and support the needs of the program at the sponsor level. As directed in delivery/task orders, coordination of meetings, preparing budget drills, developing agenda items, attending high-level meetings, generating minutes, and tracking action items may be required. Other support may require a contractor to recommend policies, doctrine, tactics, and procedures at the Federal, State, and Local level given their past expert opinion or using analysis of actual outcomes. Program support may require significant coordination and interface with various DOD and non-DOD activities located in and out of CONUS.

3.2.2 Program Support Documentation

The contractor shall draft and/or develop various PM documents (CDRL A001). At a minimum, the following documents are typical PM deliverables that the contractor shall have knowledge writing.

Statement of Work or Performance Work Statement Cost Estimation Meeting Agenda and Minutes Plans of Action and Milestone Work Breakdown Structure (WBS) Various Program Acquisition related documents: Mission Needs Statement (MNS), Capability Production

Documentation (CPD), Operational Requirements Document (ORD), etc.

3.3. SYSTEMS ENGINEERING SUPPORT

3.3.1 Systems Engineering Management

The contractor shall provide technical exploration for systems that are robust, reliable, high quality, supportable, cost-effective, and responsive to the needs of the government.

3.3.2 Research, Analysis, Planning and Preparation

The Contractor shall research, analyze and translate data into qualitative and quantitative technical requirements to allow for planning and project start-up, including site survey and analysis, identification of requirements, statement of existing systems/equipment/technologies, considerations and comparisons of candidate solutions, recommendations, scheduling and implementation schedule, work breakdown structures, logistics support, and cost.

The Contractor shall generate project management planning documents that will become the basis for further project management. Work also will involve restructuring computer databases for optimum access by the requiring agency as well as other government and non-government entities.

3.3.2.1 Research involves investigation of existing or proposed functions of a site, including mission requirements, existing capabilities, physical specifications/ limitations, problem areas, inter facility and intra facility requirements, environmental impacts, scientific research affects, and special considerations.

3.3.2.2 Analysis includes evaluation of requirements derived from data gathered during the site survey. It also includes considerations and comparisons of candidate solutions, discussing the advantages and disadvantages of the systems/equipment/technologies explained above. Based upon these considerations, the Contractor shall make recommendations for and report on the best solution.

3.3.2.3 Planning and preparation includes the implementation schedule; presenting a systematic and integrated approach to accomplishing new installations and/or upgrade existing equipment, including dates of procurement, shipment/transit, installation and checkout, methods of dual operations, and training. It also reflects the logistics support approach for training, maintenance, parts support, documentation, and other logistic needs as required. Cost data will provide the procuring activity with estimated budgetary information for planning purposes.

3.3.2.4 The Contractor shall prepare reports, plans, summaries and/or briefings that describe the topics described above. Unless otherwise specified in each TO, the Contractor's format is acceptable.

3.3.3 Technology Investigations

The Contractor shall investigate apparent solutions to problems in an assigned technology area and compare these solutions to the technical requirements determined under that task. The Contractor shall:

3.3.3.1 Obtain and review public, government, and privately held literature.

3.3.3.2 Obtain technical expertise and recommendations from experts, both inside and outside the government, including private industry, colleges and universities, and international experts.

3.3.3.3 Prove how the possible solutions fulfill the technical requirements and operational mission requirements.

3.3.3.4 The Contractor shall prepare a report that specifies the criteria used to select potential solutions. The report shall demonstrate the applicability and effectiveness of the criteria. The unacceptable solutions shall be identified, and how and why each solution failed to satisfy the specified criteria shall be discussed. The report shall include a list of solutions that satisfied the criteria and a recommended course of action. The remainder of the report shall then clearly show the correlation between each solution and the technical requirements. Unless otherwise specified in each TO, the Contractor's format is acceptable.

3.3.4 Research and Development (R&D)

As required by the government, the contractor shall support the development and application of scientific and analytical disciplines to conduct fundamental research; scientific study and experimentation directed toward advancing the state-of-the-art or increasing knowledge or understanding; concept formulation; assessment of system and subsystem requirements; development, analysis and evaluation of concepts, technologies, systems and subsystems; and development of operational concepts and tactics with the end goal being the application of results to developing new improving existing warfighting capabilities.

3.3.5 System Design & Documentation

The contractor shall be able to support the engineering effort required to prepare and assure that the detailed technical data documentation that is necessary to support system development reflects the latest design, configuration, integration, and installation concepts. Technical documentation shall be in a form of paper, electronic (digital) or interactive computer systems.

3.4. TECHNICAL SUPPORT

3.4.1 Site Surveys and Studies

The Contractor shall conduct site surveys to determine the optimum location and configuration for an equipment/system modifications or upgrades. The Contractor must be capable of gathering all pertinent environmental, engineering, configuration and design information relevant to site conditions, analyzing the collected data, performing necessary calculations to make technical recommendations, and preparing technical reports and documentation for a specific engineering change proposal, modification, or system upgrade.

3.4.2 LIFECYCLE LOGISTICS SUPPORT

The contractor shall be able to apply engineering and analytical disciplines required to implement life-cycle (acquisition) logistics as a multi-functional technical management discipline associated with the experimental development, design, development, test, production, fielding, sustainment, and improvement modifications of cost effective systems that achieve the warfighter’s peacetime and wartime readiness requirements. The principal objective of lifecycle (acquisition) logistics are to ensure that support considerations are an integral part of the system’s design requirements, that the system can be cost effectively supported through it life-cycle, and that the research and development facilities and infrastructure elements necessary to the design, development, initial fielding, and operational support of the system are identified, developed, acquired, and supported. Lifecycle Logistics is NOT to be confused with supply logistics which is a very general and non-technical term.

3.4.3 Training Services Support

The contractor shall be able to apply the engineering and analytical disciplines required to ensure that the warfighter and technical support community is provided with adequate instruction including applied exercises resulting in the attainment and retention of knowledge, skills, and attitudes regarding the platforms, systems, and warfighting capabilities they operate and maintain.

3.4.3.1 Training Support

Although training support will normally be provided at CONUS locations, the contractor shall occasionally be required to provide training support in hostile areas. The contractor shall customize and update as required a Program of Instruction (POI) on the use of the family of TTL devices with special emphasis on presenting the appropriate Training, Tactics and Procedures (TTPs) for the end user’s mission. Based upon the equipment needed to meet mission requirements, the contractor may be required to augment the training team with engineering support from the equipment manufacturer. The contractor shall develop a presentation and provide all training course documentation for Government approval required for each course

The POI will provide for three to five weeks of training for each class (up to twenty (20) personnel per class) either at the contractor’s facility or a government provided facility as specified within individual TOs. The training course will be tailored to meet the mission requirements and the end user’s schedule. The POI may require modification if the mission requirements or TTP changes. These changes will be brought to the contractor’s attention No Later Than (NLT) six weeks prior to the course start date. The training will include:

An overview of the TTL mission, systems and techniques Training in operation and maintenance of the TTL systems to be deployed Instruction of personnel in proper mission planning and TTPs Operational exercise scenarios to demonstrate real-world operation of these systems

At the conclusion of training, the student will be able to plan and conduct basic TTL operations using Government furnished equipment. Initial training customization will be accomplished prior to the first scheduled training session via consultation with the COR and end user leadership and training personnel with the contractor’s subject matter experts. On-going training customization will be accomplished via continual consultation with the above sources plus feedback from students, sponsors and operational results from deployed technical support personnel.

3.4.3.2 Training Support Execution

The contractor shall provide training teams skilled in the use of the TTL equipment to present the POI. Tentative training schedule dates will be provided in each TO. Specific locations and dates for each team will be agreed upon with the COR in a timely manner to allow adequate pre-course coordination.

Pre-course Preparation: Prior to the commencement of each course, the contractor shall carry out the necessary pre-course preparation activities. These activities will include, but are not limited to:

Travel planning and travel to the specified training location Coordination with host activities and survey of actual sites and training venues Preparation of student course materials, including COR approved POI modifications Coordination of rental cars leasing and/or use of government vehicles for training purposes Configuration and testing of the Government furnished equipment Coordination of use of any supplemental instruction aides Coordination of security requirements Operational exercise planning and rehearsal

The contractor shall conduct an initial site survey and direct coordination with end users and host facility managers at the specified locations as soon as possible after agreement with the government on the location and dates of the training. The expectation is that the contractor shall be able to accomplish the initial coordination no later than three

(3) weeks prior to the start of training. The necessary government personnel will be available for coordination during the initial site survey and during the week prior to training.

The contractor’s training team shall arrive on site one week prior to execution of a training block. The team shall execute all activities necessary to conduct training, including final coordination with host activities and end users receiving training, configuration and test of the TTL equipment, preparation of training support items (including vehicles), and exercise rehearsal(s).

The contractor shall arrange for suitable facilities for training either at the host activity, CONUS or OCONUS, or at the contractor’s facility as specified in the individual TO.

Post Course Evaluation and Logistics: Upon the completion of all courses within a training block, the contractor shall carry out a series of close out activities including, but not limited to:

Post-course evaluation with the COR, sponsor personnel and/or end user leadership Recommend POI modifications and provide other feedback as necessary Final configuration and test of TTL equipment before release to units Return of any sponsor provided equipment.

3.4.4 Direct Technical Support

To support the Sponsor’s in-theater requirements, the contractor shall provide Field Service Representatives (FSRs) for direct technical support to end users in hostile areas; including support within the Central Command Area of Responsibility (CENTCOM AOR), as coordinated with the COR and end user leadership and training personnel.

As required to support the Sponsor’s OCONUS requirements, the contractor shall provide FSRs for assignment to designated end users. The FSRs shall be required to travel OCONUS for specialized support. The FSRs shall be embedded within the supported unit for approximately 120 days per rotation; however, based on user demands and personnel availability, this assignment may be extended or the FSR may be scheduled for an additional OCONUS assignment at the completion of the initial assignment. The government will provide each deploying FSR with a kit that includes required test equipment and personal protective equipment. Upon their return from their OCONUS assignment(s), the FSR will return the kit to the government.

The contractor shall provide FSRs that are experienced with the TTL equipment and in other aspects of TTL operations; including operational planning, system enclosures and mounting, other TTL systems utilization, and quick reaction support. The contractors’ FSRs shall provide technical advice to end users and end user leadership, provide refresher training to end user personnel, assist in the planning of operations, and assist end users in maintaining and configuring TTL equipment. They shall also serve as a point of contact for the end user for capturing lessons learned. If resources are not available in forward deployed locations the FSR’s shall reach back to CONUS for spares, replacements, specialized systems and packaging, and technical support from the contractor and/or OEMs. The end user will provide Secret Internet Protocol Router Network (SIPRNET) access to the FSR personnel in-country to exchange sensitive information (e.g. lessons learned and technical support requirements) with contractor support personnel. The FSR shall not be used as an operational asset for emplacement, collection, or as an instructor for new equipment training.

3.4.5 General Technical Support

The contractor shall provide general technical support to the deployed FSRs and training teams. Specific support includes quick reaction technical assistance with emergent problems and opportunities, facilitating repair and return of equipment, facilitating minor product and TTP improvements in response to operational feedback and requirements, conducting tests and assessments, and facilitating distribution of software releases.

Special emphasis will be placed on those activities required to ensure overall quality of the effort; including POI currency and relevance, excellence in training presentation, and overall coherence between the training and feedback from FSR personnel.

Documentation such as training schedules, training materials, user manuals, lessons learned and other Government required documents will be hosted and maintained on Government provided controlled-access web sites. The contractor shall provide a monthly After Action Review (AAR) Summary Report and Bi-Weekly Situational Report from the FSRs to the COR.

The contractor shall identify/provide for the training needs of their personnel performing quality functions. The contractor shall provide qualified individuals at commencement of performance in accordance with the technical service requirements of this task as well as the personnel qualifications for the assigned labor categories.