N6833517R0096.docx

DOCX document 90 KB Posted Mar 30, 2017

Attached to: Ordnance Loading Platform Adapters Federal contract opportunity
Solicitation number: N6833517R0096
Issued by: Department of the Navy Naval Air Systems Command Naval Air Warfare Center

About this file

From the source

Request For Proposals

View the file

Other files for this federal contract opportunity

Other files attached to Ordnance Loading Platform Adapters, newest first.
File	Type	Posted
Q&A_5-2-17.docx	DOCX document	May 2, 2017
N6833517R0096_Amendment_1.docx	DOCX document	May 1, 2017
Questions_and_Answers.docx	DOCX document	Apr 27, 2017

On GovTribe

Work with this file on GovTribe

Download the original file
Contacts named in this file
Similar government files
Ask GovTribe AI about this file

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

N6833517R0096

Section A - Solicitation/Contract Form

POINTS OF CONTACT

Government Point of Contact:

Frances Marigliano Contract Specialist Email: frances.marigliano@navy.mil

Section B - Supplies or Services and Prices

ITEM NO

SUPPLIES/SERVICES

QUANTITY

UNIT

UNIT PRICE

AMOUNT

Each

Ordnance Loading Platform Adapters

FFP

Ordnance Loading Platform Adapters P/N 3958AS350-1 built and delivered in accordance with the Statement of Work and Technical Drawing Package FOB: Destination

NET AMT

Section C - Descriptions and Specifications

STATEMENT OF WORK

Statement of Work for Harvest HAWK Plus KC-130J Program Ordnance Loading Platform

1.1 Introduction

This Statement of Work (SOW) defines the effort to manufacture and deliver the following Support Equipment (SE):

1.2 Scope

Ordnance Loading Platform Adapter- P/N 3958AS350-1: The Harvest HAWK Plus KC-130J aircraft has a requirement to procure 3 (three) assets in direct support of VMGR-252, VMGR-352 and Pax Test and Evaluation.

2.1 Delivery

The SE items in paragraph 1.2 shall be delivered no more than 90 days (or sooner) after contract award to Lakehurst, NJ.

Ship to: NAVAIR Lakehurst Support Equipment Staging Facility Naval Air Warfare Center Aircraft Division Rte 547 Bldg 195/Hangar 6 Lakehurst, NJ 08733 Mark for: KC-130J Harvest HAWK Plus Program

3.1 Inspection / Acceptance

Inspection and Acceptance for units shall be at Origin by Government (DCMA).

3.2 Inspection / Acceptance Elements

Capability, process, and procedure to Proof Load Test (3,000 lbs.)

Process to Anodize Process to Passivate Capability to Weld Aluminum Capability and process for Welding Vibratory Stress Relief e.g. Meta-lax Capability and process to engrave and/or etch Capability and process to Prime and Paint Capability and process to apply corrosion resistant finish to steel

4. CLIN Structure

CLIN

Nomenclature

Quantity

0001

Ordnance Loading Platform Adapter P/N 3958AS350-1

Section D - Packaging and Marking

CLAUSES INCORPORATED BY FULL TEXT

5252.247-9508	PROHIBITED PACKING MATERIALS (NAVAIR)(JUN 1998)
	The use of asbestos, excelsior, newspaper or shredded paper (all types including waxed paper, computer paper and similar hydroscopic or non-neutral material) is prohibited. In addition, loose fill polystyrene is prohibited for shipboard use.

5252.247-9509	PRESERVATION, PACKAGING, PACKING AND MARKING (NAVAIR)(JUL 1998)
	(a) Preservation, packaging and packing shall conform to prevailing industry standards for the type of commodity purchased under this contract.
	(b) All packages will be clearly marked with applicable contract number/delivery order number, and will contain appropriate packing slip. All deliveries will be marked for and/or consigned as follows:

*See Ship To Address

(c) In the event of any discrepancy in material shipped (overage, technical rejection, damage), the contractor shall, immediately upon request of the Contracting Officer, furnish disposition instructions. Normally, such disposition instruction shall be a properly completed Commercial Bill of Lading, which includes, but is not limited to, the mode of shipment, routing, special handling, and so forth.

(d) If the contractor is required to install equipment upon delivery, then the contractor shall inform the Government of the date of shipment from the contractor's facilities and the anticipated date of arrival at the site. This report shall be made no later than the actual date that the shipment is made from the contractor’s facilities. The report may be made by facsimile or e-mail, to the point of contact listed in Section G. All transportation, rigging, drayage, packing, unpacking, and handling necessary to accomplish the installation shall be the responsibility of the contractor.

Section E - Inspection and Acceptance

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

CLIN

INSPECT AT

INSPECT BY

ACCEPT AT

ACCEPT BY

0001

Origin

Government

Origin

Government

CLAUSES INCORPORATED BY REFERENCE

52.246-2

Inspection Of Supplies--Fixed Price

AUG 1996

52.246-16

Responsibility For Supplies

APR 1984

252.246-7000

Material Inspection And Receiving Report

MAR 2008

Section F - Deliveries or Performance

DELIVERY INFORMATION

CLIN

DELIVERY DATE

QUANTITY

SHIP TO ADDRESS

DODAAC / CAGE

0001

90 dys. ADC

NAVAIR LAKEHURST STAGING FACILITY

BRADLEY SMITH

NAVAL AIR WARFARE CTR AD

RT 547 BLDG 195 HANGAR 6

LAKEHURST NJ 08733

732-323-1205 FOB: Destination

DIP007

52.242-15

Stop-Work Order

AUG 1989

52.242-17

Government Delay Of Work

APR 1984

52.247-34

F.O.B. Destination

NOV 1991

Section G - Contract Administration Data

252.232-7003

Electronic Submission of Payment Requests and Receiving Reports

JUN 2012

252.232-7006	WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (MAY 2013)
	(a) Definitions, as used in this clause--
	"Department of Defense Activity Address Code (DoDAAC)" is a six position code that uniquely identifies a unit, activity, or organization.
	"Document type" means the type of payment request or receiving report available for creation in Wide Area WorkFlow (WAWF).
	"Local processing office (LPO)" is the office responsible for payment certification when payment certification is done external to the entitlement system.
	(b) Electronic invoicing. The WAWF system is the method to electronically process vendor payment requests and receiving reports, as authorized by DFARS 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.
	(c) WAWF access. To access WAWF, the Contractor shall--
		(1) Have a designated electronic business point of contact in the System for Award Management at https://www.acquisition.gov; and
		(2) Be registered to use WAWF at https://wawf.eb.mil/ following the step-by-step procedures for self-registration available at this Web site.
	(d) WAWF training. The Contractor should follow the training instructions of the WAWF Web-Based Training Course and use the Practice Training Site before submitting payment requests through WAWF. Both can be accessed by selecting the "Web Based Training" link on the WAWF home page at https://wawf.eb.mil/.
	(e) WAWF methods of document submission. Document submissions may be via Web entry, Electronic Data Interchange, or File Transfer Protocol.
	(f) WAWF payment instructions. The Contractor must use the following information when submitting payment requests and receiving reports in WAWF for this contract/order:
		(1) Document type. The Contractor shall use the following document type(s).
	________________________**___________________________________________________
	(Contracting Officer: Insert applicable document type(s). Note: If a "Combo" document type is identified but not supportable by the Contractor's business systems, an "Invoice" (stand-alone) and "Receiving Report" (stand-alone) document type may be used instead.)
		(2) Inspection/acceptance location. The Contractor shall select the following inspection/acceptance location(s) in WAWF, as specified by the contracting officer.
	__________________________Origin/Origin________________________________________________
	(Contracting Officer: Insert inspection and acceptance locations or "Not applicable.")
		(3) Document routing. The Contractor shall use the information in the Routing Data Table below only to fill in applicable fields in WAWF when creating payment requests and receiving reports in the system.

Routing Data Table*
Field Name in WAWF			Data to be entered in WAWF
Pay Official DoDAAC:			____**_____________________
Issue By DoDAAC:			____N68335_____________________
Admin DoDAAC:			____**_____________________
Inspect By DoDAAC:			____**_____________________
Ship To Code:				____N68335____________________
Ship From Code:			_________________________
Mark For Code:			_________________________
Service Approver (DoDAAC):		_________________________
Service Acceptor (DoDAAC):		_________________________
Accept at Other DoDAAC:		_________________________
LPO DoDAAC:			_________________________
DCAA Auditor DoDAAC:		_________________________
Other DoDAAC(s):			_________________________
(*Contracting Officer: Insert applicable DoDAAC information or "See schedule" if multiple ship to/acceptance locations apply, or "Not applicable.")
	(4) Payment request and supporting documentation. The Contractor shall ensure a payment request includes appropriate contract line item and subline item descriptions of the work performed or supplies delivered, unit price/cost per unit, fee (if applicable), and all relevant back-up documentation, as defined in DFARS Appendix F, (e.g. timesheets) in support of each payment request.
	(5) WAWF email notifications. The Contractor shall enter the email address identified below in the "Send Additional Email Notifications" field of WAWF once a document is submitted in the system.

(Contracting Officer: Insert applicable email addresses or "Not applicable.")

(g) WAWF point of contact. (1) The Contractor may obtain clarification regarding invoicing in WAWF from the following contracting activity's WAWF point of contact. For Navy WAWF questions call DFAS Customer Care 1-800-756-4571 option 6
	(2) For technical WAWF help, contact the WAWF helpdesk at 866-618-5988.

**To Be Completed At Time of AWARD**

Section H - Special Contract Requirements

5252.211- 9510	CONTRACTOR EMPLOYEES (NAVAIR)(MAY 2011)
	(a) In all situations where contractor personnel status is not obvious, all contractor personnel are required to identify themselves to avoid creating an impression to the public, agency officials, or Congress that such contractor personnel are Government officials. This can occur during meeting attendance, through written (letter or email) correspondence or verbal discussions (in person or telephonic), when making presentations, or in other situations where their contractor status is not obvious to third parties. This list is not exhaustive. Therefore, the contractor employee(s) shall:
		(1) Not by word or deed give the impression or appearance of being a Government employee;
		(2) Wear appropriate badges visible above the waist that identify them as contractor employees when in Government spaces, at a Government-sponsored event, or an event outside normal work spaces in support of the contract/order;
		(3) Clearly identify themselves as contractor employees in telephone conversations and in all formal and informal written and electronic correspondence. Identification shall include the name of the company for whom they work;
		(4) Identify themselves by name, their company name, if they are a subcontractor the name of the prime contractor their company is supporting, as well as the Government office they are supporting when participating in meetings, conferences, and other interactions in which all parties are not in daily contact with the individual contractor employee; and
		(5) Be able to provide, when asked, the full number of the contract/order under which they are performing, and the name of the Contracting Officer’s Representative.
	(b) If wearing a badge is a risk to safety and/or security, then an alternative means of identification maybe utilized if endorsed by the Contracting Officer’s Representative and approved by the Contracting Officer.
	(c) The Contracting Officer will make final determination of compliance with regulations with regard to proper identification of contractor employees.

Section I - Contract Clauses

52.203-5

Covenant Against Contingent Fees

MAY 2014

52.203-6

Restrictions On Subcontractor Sales To The Government

SEP 2006

52.203-7

Anti-Kickback Procedures

MAY 2014

52.203-8

Cancellation, Rescission, and Recovery of Funds for Illegal or Improper Activity

MAY 2014

52.203-10

Price Or Fee Adjustment For Illegal Or Improper Activity

MAY 2014

52.203-12

Limitation On Payments To Influence Certain Federal Transactions

OCT 2010

52.204-2

Security Requirements

AUG 1996

52.204-4

Printed or Copied Double-Sided on Postconsumer Fiber Content Paper

MAY 2011

52.204-7

System for Award Management

OCT 2016

52.204-13

System for Award Management Maintenance

OCT 2016

52.209-10

Prohibition on Contracting With Inverted Domestic Corporations

NOV 2015

52.211-5

Material Requirements

AUG 2000

52.215-20

Requirements for Certified Cost or Pricing Data or Information Other Than Certified Cost or Pricing Data

OCT 2010

52.216-1

Type Of Contract

APR 1984

52.219-6

Notice Of Total Small Business Set-Aside

NOV 2011

52.219-28

Post-Award Small Business Program Rerepresentation

JUL 2013

52.222-50

Combating Trafficking in Persons

MAR 2015

52.223-6

Drug-Free Workplace

MAY 2001

52.223-6

Drug-Free Workplace

MAY 2001

52.223-18

Encouraging Contractor Policies To Ban Text Messaging While Driving

AUG 2011

52.227-1

Authorization and Consent

DEC 2007

52.229-3

Federal, State And Local Taxes

FEB 2013

52.243-1

Changes--Fixed Price

AUG 1987

52.246-23

Limitation Of Liability

FEB 1997

52.249-2

Termination For Convenience Of The Government (Fixed-Price)

APR 2012

52.249-8

Default (Fixed-Price Supply & Service)

APR 1984

252.203-7000

Requirements Relating to Compensation of Former DoD Officials

SEP 2011

252.203-7002

Requirement to Inform Employees of Whistleblower Rights

SEP 2013

252.204-7003

Control Of Government Personnel Work Product

APR 1992

252.223-7008

Prohibition of Hexavalent Chromium

JUN 2013

252.225-7001

Buy American And Balance Of Payments Program-- Basic (Dec 2016)

DEC 2016

252.225-7002

Qualifying Country Sources As Subcontractors

DEC 2016

252.225-7008

Restriction on Acquisition of Specialty Metals

MAR 2013

252.225-7016

Restriction On Acquisition Of Ball and Roller Bearings

JUN 2011

252.232-7010

Levies on Contract Payments

DEC 2006

252.243-7001

Pricing Of Contract Modifications

DEC 1991

252.247-7023

Transportation of Supplies by Sea

APR 2014

252.204-7012	SAFEGUARDING COVERED DEFENSE INFORMATION AND CYBER INCIDENT INFORMATION (OCT 2016)
	(a) Definitions. As used in this clause --
	"Adequate security" means protective measures that are commensurate with the consequences and probability of loss, misuse, or unauthorized access to, or modification of information.
	"Compromise" means disclosure of information to unauthorized persons, or a violation of the security policy of a system, in which unauthorized intentional or unintentional disclosure, modification, destruction, or loss of an object, or the copying of information to unauthorized media may have occurred.
	"Contractor attributional/proprietary information" means information that identifies the contractor(s), whether directly or indirectly, by the grouping of information that can be traced back to the contractor(s) (e.g., program description, facility locations), personally identifiable information, as well as trade secrets, commercial or financial information, or other commercially sensitive information that is not customarily shared outside of the company.
	"Controlled technical information" means technical information with military or space application that is subject to controls on the access, use, reproduction, modification, performance, display, release, disclosure, or dissemination. Controlled technical information would meet the criteria, if disseminated, for distribution statements B through F using the criteria set forth in DoD Instruction 5230.24, Distribution Statements on Technical Documents. The term does not include information that is lawfully publicly available without restrictions.
	"Covered contractor information system" means an unclassified information system that is owned, or operated by or for, a contractor and that processes, stores, or transmits covered defense information.
	"Covered defense information" means unclassified controlled technical information or other information, as described in the Controlled Unclassified Information (CUI) Registry at http://www.wrchives.gov/cui/registry/category-list.html, that requires safeguarding or dissemination controls pursuant to and consistent with law, regulations, and Governmentwide policies, and is --
		(1) Marked or otherwise identified in the contract, task order, or delivery order and provided to the contractor by or on behalf of DoD in support of the performance of the contract; or
		(2) Collected, developed, received, transmitted, used, or stored by or on behalf of the contractor in support of the performance of the contract.
	"Cyber incident" means actions taken through the use of computer networks that result in a compromise or an actual or potentially adverse effect on an information system and/or the information residing therein.
	"Forensic analysis" means the practice of gathering, retaining, and analyzing computer-related data for investigative purposes in a manner that maintains the integrity of the data.
	"Information system" means a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information.
	"Malicious software" means computer software or firmware intended to perform an unauthorized process that will have adverse impact on the confidentiality, integrity, or availability of an information system. This definition includes a virus, worm, Trojan horse, or other code-based entity that infects a host, as well as spyware and some forms of adware.
	"Media" means physical devices or writing surfaces including, but not limited to, magnetic tapes, optical disks, magnetic disks, large-scale integration memory chips, and printouts onto which covered defense information is recorded, stored, or printed within a covered contractor information system.
	"Operationally critical support" means supplies or services designated by the Government as critical for airlift, sealift, intermodal transportation services, or logistical support that is essential to the mobilization, deployment, or sustainment of the Armed Forces in a contingency operation.
	"Rapidly report" means within 72 hours of discovery of any cyber incident.
	"Technical information" means technical data or computer software, as those terms are defined in the clause at DFARS 252.227-7013, Rights in Technical Data - Non Commercial Items, regardless of whether or not the clause is incorporated in this solicitation or contract. Examples of technical information include research and engineering date, engineering drawings, and associated lists, specifications, standards, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code.
	(b) Adequate security. The Contractor shall provide adequate security for all covered contractor information systems. To provide adequate security, the Contractor shall implement, at a minimum, the following information security protections:
		(1) For covered contractor information systems that are part of an information technology (IT) service or system operated on behalf of the Government, the following security requirements apply:
			(i) Cloud computing services shall be subject to the security requirements specified in the clause 252.239-7010, Cloud Computing Services, of this contract.
			(ii) Any other such IT service or system (i.e., other than cloud computing) shall be subject to the security requirements specified elsewhere in this contract.
		(2) For covered contractor information systems that are not part of an IT service or system operated on behalf of the Government and therefore are not subject to the security requirement specified at paragraph (b)(1) of this clause, the following security requirements apply:
			(i) Except as provided in paragraph (b)(2)(ii) of this clause, the covered contractor information system shall be subject to the National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171, "Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations," (available via the internet at http://dx.doi.org/10.6028/NIST.SP.800-171) that is in effect at the time the solicitation is issued or as authorized by the Contracting Officer.
			(ii)(A) The Contractor shall submit requests to vary from NIST SP 800-171, as soon as practical, but not later than December 31, 2017. For all contracts awarded prior to October 1, 2017, the Contractor shall notify the DoD Chief Information Officer (CIO), via email at osd.dibcsia@mail.mil, within 30 days of contract award, of any security requirements specified by NIST SP 800-171 not implemented at the time of contract award.
				(B) The Contractor shall submit requests to vary from NIST SP 800-171 in writing to the Contracting Officer, for consideration by the DoD CIO. The Contractor need not implement any security requirement adjudicated by an authorized representative of the DoD CIO to be nonapplicable or to have an alternative but equally effective, security measure that may be implemented in its place.
				(C) If the DoD CIO has previously adjudicated the contractor's requests indicating that a requirement is not applicable or that an alternative security measure is equally effective, a copy of that approval shall be provided to the Contracting Officer when requesting its recognition under this contract.
				(D) If the Contractor intends to use an external cloud service provider to store, process, or transmit any covered defense information in performance of this contract, the Contractor shall require and ensure that the cloud service provided meets security requirements equivalent to those established by the Government for the Federal Risk and Authorization Management Program (FedRAMP) Moderate baseline (https://www.fedramp.gov/resources/documents/) and that the cloud service provider complies with requirements in paragraphs (c) through (g) of this clause for cyber incident reporting, malicious software, media preservation and protection, access to additional information and equipment necessary for forensic analysis, and cyber incident damage assessment.
		(3) Apply other information systems security measures when the Contractor reasonably determines that information systems security measures, in addition to those identified in paragraph (b)(1) and (2) of this clause, may be required to provide adequate security in a dynamic environment or to accommodate special circumstances (e.g., medical devices) and any individual, isolated, or temporary deficiencies based on an assessed risk or vulnerability. These measures may be addressed in a system security plan.
	(c) Cyber incident reporting requirement.
		(1) When the Contractor discovers a cyber incident that affects a covered contractor information system or the covered defense information residing therein, or that affects the contractor's ability to perform the requirements of the contract that are designated as operationally critical support, the Contractor shall --
			(i) Conduct a review for evidence of compromise of covered defense information, including, but not limited to, identifying compromised computers, servers, specific data, and user accounts. This review shall also include analyzing covered contractor information system(s) that were part of the cyber incident, as well as other information systems on the Contractor's network(s), that may have been accessed as a result of the incident in order to identify compromised covered defense information, or that affect the Contractor's ability to provide operationally critical support; and
			(ii) Rapidly report cyber incidents to DoD at http://dibnet.dod.mil.
		(2) Cyber incident report. The cyber incident report shall be treated as information created by or for DoD and shall include, at a minimum, the required elements at http://dibnet.dod.mil.
		(3) Medium assurance certificate requirement. In order to report cyber incidents in accordance with this clause, the Contractor or subcontractor shall have or acquire a DoD-approved medium assurance certificate to report cyber incidents. For information on obtaining a DoD-approved medium assurance certificate, see http://iase.disa.mil/pki/eca/Pages/index.aspx.
	(d) Malicious software. When the Contractor or subcontractors discover and isolate malicious software in connection with a reported cyber incident, submit the malicious software to DoD Cyber Crime Center (DC#) in accordance with instructions provided by DC3 or the Contracting Officer. Do not send the malicious software to the Contracting Officer.
	(e) Media preservation and protection. When a Contractor discovers a cyber incident has occurred, the Contractor shall preserve and protect images of all known affected information systems identified in paragraph (c)(1)(i) of this clause and all relevant monitoring/packet capture data for at least 90 days from the submission of the cyber incident report to allow DoD to request the media or decline interest.
	(f) Access to additional information or equipment necessary for forensic analysis. Upon request by DoD, the Contractor shall provide DoD with access to additional information or equipment that is necessary to conduct a forensic analysis.
	(g) Cyber incident damage assessment activities. If DoD elects to conduct a damage assessment, the Contracting Officer will request that the Contractor provide all of the damage assessment information gathered in accordance with paragraph (e) of this clause.
	(h) DoD safeguarding and use of contractor attributional/proprietary information. The Government shall protect against the unauthorized use or release of information obtained from the contractor (or derived from information obtained from the contractor) under this clause that includes contractor attributional/proprietary information, including such information submitted in accordance with paragraph (c). To the maximum extent practicable, the Contractor shall identify and mark attributional/proprietary information. In making an authorized release of such information, the Government will implement appropriate procedures to minimize the contractor attributional/proprietary information that is included in such authorized release, seeking to include only that information that is necessary for the authorized purpose(s) for which the information is being released.
	(i) Use and release of contractor attributional/proprietary information not created by or for DoD. Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is not created by or for DoD is authorized to be released outside of DoD--
		(1) To entities with missions that may be affected by such information;
		(2) To entities that may be called upon to assist in the diagnosis, detection, or mitigation of cyber incidents;
		(3) To Government entities that conduct counterintelligence or law enforcement investigations;
		(4) For national security purposes, including cyber situational awareness and defense purposes (including with Defense Industrial Base (DIB) participants in the program at 32 CFR part 236); or
		(5) To a support services contractor ("recipient") that is directly supporting Government activities under a contract that includes the clause at 252.204-7009, Limitations on the Use or Disclosure of Third-Party Contractor Reported Cyber Incident Information.
	(j) Use and release of contractor attributional/proprietary information created by or for DoD. Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is created by or for DoD (including the information submitted pursuant to paragraph (c) of this clause) is authorized to be used and released outside of DoD for purposes and activities authorized by paragraph (i) of this clause, and for any other lawful Government purposes or activity, subject to all applicable statutory, regulatory, and policy based restrictions on the Government's use and release of such information.
	(k) The Contractor shall conduct activities under this clause in accordance with applicable laws and regulations on the interception, monitoring, access, use, and disclosure of electronic communications and data.
	(l) Other safeguarding or reporting requirements. The safeguarding and cyber incident reporting required by this clause in no way abrogates the Contractor's responsibility for other safeguarding or cyber incident reporting pertaining to its unclassified information systems as required by other applicable clauses of this contract, or as a result of other applicable U.S. Government statutory or regulatory requirements.
	(m) Subcontracts. The Contractor shall --
		(1) Include this clause, including this paragraph (m), in subcontracts, or similar contractual instruments, for operationally critical support, or for which subcontract performance will involve covered defense information, including subcontracts for commercial items, without alteration, except to identify the parties. The Contractor shall determine if the information required for subcontractor performance retains its identity as covered defense information and will require protection under this clause, and if necessary, consult with the Contracting Officer; and
		(2) Require subcontractor to--
			(i) Notify the prime Contractor (or next higher-tier subcontractor) when submitting a request to vary from a NIST SP 800-171 security requirement to the Contracting Officer, in accordance with paragraph (b)(2)(ii)(B) of this clause; and
				(ii) Provide the incident report number, automatically assigned by DoD, to the prime Contractor (or next higher-tier subcontractor) as soon as practicable, when reporting a cyber incident to DoD as required in paragraph (c) of this clause.

252.211-7003	ITEM UNIQUE IDENTIFICATION AND VALUATION (MAR 2016)
	(a) Definitions. As used in this clause--
	“Automatic identification device” means a device, such as a reader or interrogator, used to retrieve data encoded on machine-readable media.
	“Concatenated unique item identifier” means--
		(1) For items that are serialized within the enterprise identifier, the linking together of the unique identifier data elements in order of the issuing agency code, enterprise identifier, and unique serial number within the enterprise identifier; or
		(2) For items that are serialized within the original part, lot, or batch number, the linking together of the unique identifier data elements in order of the issuing agency code; enterprise identifier; original part, lot, or batch number; and serial number within the original part, lot, or batch number.
	“Data matrix” means a two-dimensional matrix symbology, which is made up of square or, in some cases, round modules arranged within a perimeter finder pattern and uses the Error Checking and Correction 200(ECC200) specification found within International Standards Organization (ISO)/ International Electrotechnical Commission (IEC) 16022.
	“Data qualifier” means a specified character (or string of characters) that immediately precedes a data field that defines the general category or intended use of the data that follows.
	“DoD recognized unique identification equivalent” means a unique identification method that is in commercial use and has been recognized by DoD. All DoD recognized unique identification equivalents are listed at http://www.acq.osd.mil/dpap/pdi/uid/iuid_equivalents.html.
	“DoD item unique identification” means a system of marking items delivered to DoD with unique item identifiers that have machine-readable data elements to distinguish an item from all other like and unlike items. For items that are serialized within the enterprise identifier, the unique item identifier shall include the data elements of the enterprise identifier and a unique serial number. For items that are serialized within the part, lot, or batch number within the enterprise identifier, the unique item identifier shall include the data elements of the enterprise identifier; the original part, lot, or batch number; and the serial number.
	“Enterprise” means the entity (e.g., a manufacturer or vendor) responsible for assigning unique item identifiers to items.
	“Enterprise identifier” means a code that is uniquely assigned to an enterprise by an issuing agency.
	“Government's unit acquisition cost” means--
		(1) For fixed-price type line, subline, or exhibit line items, the unit price identified in the contract at the time of delivery;
		(2) For cost-type or undefinitized line, subline, or exhibit line items, the Contractor’s estimated fully burdened unit cost to the Government at the time of delivery; and
		(3) For items produced under a time-and-materials contract, the Contractor’s estimated fully burdened unit cost to the Government at the time of delivery.
	“Issuing agency” means an organization responsible for assigning a globally unique identifier to an enterprise, as indicated in the Register of Issuing Agency Codes for ISO/IEC 15459, located at http://www.aimglobal.org/?Reg_Authority15459.
	“Issuing agency code” means a code that designates the registration (or controlling) authority for the enterprise identifier.
	“Item” means a single hardware article or a single unit formed by a grouping of subassemblies, components, or constituent parts.
	“Lot or batch number” means an identifying number assigned by the enterprise to a designated group of items, usually referred to as either a lot or a batch, all of which were manufactured under identical conditions.
	“Machine-readable” means an automatic identification technology media, such as bar codes, contact memory buttons, radio frequency identification, or optical memory cards.
	“Original part number” means a combination of numbers or letters assigned by the enterprise at item creation to a class of items with the same form, fit, function, and interface.
	“Parent item” means the item assembly, intermediate component, or subassembly that has an embedded item with a unique item identifier or DoD recognized unique identification equivalent.
	“Serial number within the enterprise identifier” means a combination of numbers, letters, or symbols assigned by the enterprise to an item that provides for the differentiation of that item from any other like and unlike item and is never used again within the enterprise.
	“Serial number within the part, lot, or batch number” means a combination of numbers or letters assigned by the enterprise to an item that provides for the differentiation of that item from any other like item within a part, lot, or batch number assignment.
	“Serialization within the enterprise identifier” means each item produced is assigned a serial number that is unique among all the tangible items produced by the enterprise and is never used again. The enterprise is responsible for ensuring unique serialization within the enterprise identifier.
	“Serialization within the part, lot, or batch number” means each item of a particular part, lot, or batch number is assigned a unique serial number within that part, lot, or batch number assignment. The enterprise is responsible for ensuring unique serialization within the part, lot, or batch number within the enterprise identifier.
	“Type designation” means a combination of letters and numerals assigned by the Government to a major end item, assembly or subassembly, as appropriate, to provide a convenient means of differentiating between items having the same basic name and to indicate modifications and changes thereto.
	“Unique item identifier” means a set of data elements marked on items that is globally unique and unambiguous. The term includes a concatenated unique item identifier or a DoD recognized unique identification equivalent.
	“Unique item identifier type” means a designator to indicate which method of uniquely identifying a part has been used. The current list of accepted unique item identifier types is maintained at http://www.acq.osd.mil/dpap/pdi/uid/uii_types.html.
	(b) The Contractor shall deliver all items under a contract line, subline, or exhibit line item.
	(c) Unique item identifier.
		(1) The Contractor shall provide a unique item identifier for the following:
			(i) Delivered items for which the Government's unit acquisition cost is $5,000 or more, except for the following line items:
				Contract Line, Subline, or Exhibit Line Item Number Item Description
				________________________________________________________________________________
				________________________________________________________________________________
				________________________________________________________________________________
			(ii) Items for which the Government's unit acquisition cost is less than $5,000 that are identified in the Schedule or the following table:
				Contract Line, Subline, or Exhibit Line Item Number Item Description
				__________________________________________________________________________________
				__________________________________________________________________________________
				__________________________________________________________________________________
					(If items as identified in the Schedule, insert "See Schedule" in this table.)
			(iii) Subassemblies, components, and parts embedded within delivered items, items with warranty requirements, DoD serially managed reparables and DoD serially managed nonreparables as specified in Attachment Number ______.
			(iv) Any item of special tooling or special test equipment as defined in FAR 2.101 that have been designated for preservation and storage for a Major Defense Acquisition Program as specified in Attachment Number ______.
			(v) Any item not included in (i), (ii), (iii), or (iv) for which the contractor creates and marks a unique item identified for traceability.
		(2) The unique item identifier assignment and its component data element combination shall not be duplicated on any other item marked or registered in the DoD Item Unique Identification Registry by the contractor.
		(3) The unique item identified component data elements shall be marked on an item using two dimensional data matrix symbology that complies with ISO/IEC International Standard 16022, Information technology - International symbology specification - Data matrix; ECC200 data matrix specification.
		(4) Data syntax and semantics of unique item identifiers. The Contractor shall ensure that--
			(i) The data elements (except issuing agency code) of the unique item identifier are encoded within the data matrix symbol that is marked on the item using one of the following three types of data qualifiers, as determined by the Contractor:
				(A) Application Identifiers (AIs) (Format Indicator 05 of ISO/IEC International Standard 15434), in accordance with ISO/IEC International Standard 15418, Information Technology--EAN/UCC Application Identifiers and Fact Data Identifiers and Maintenance and ANSI MH 10.8.2 Data Identifier and Application Identifier Standard.
				(B) Data Identifiers (DIs) (Format Indicator 06 of ISO/IEC International Standard 15434), in accordance with ISO/IEC International Standard 15418, Information Technology--EAN/UCC Application Identifiers and Fact Data Identifiers and Maintenance and ANSI MH 10.8.2 Data Identifier and Application Identifier Standard.
				(C) Text Element Identifiers (TEIs) (Format Indicator 12 of ISO/IEC International Standard 15434), in accordance with the Air Transport Association Common Support Data Dictionary; and
			(ii) The encoded data elements of the unique item identifier conform to the transfer structure, syntax, and coding of messages and data formats specified for Format Indicators 05, 06, and 12 in ISO/IEC International Standard 15434, Information Technology--Transfer Syntax for High Capacity Automatic Data Capture Media.
		(5) Unique item identifier.
			(i) The Contractor shall--
				(A) Determine whether to--
					(1) Serialize within the enterprise identifier;
					(2) Serialize within the part, lot, or batch number; or
					(3) Use a DoD recognized unique identification equivalent (e.g. Vehicle Identification Number); and
				(B) Place the data elements of the unique item identifier (enterprise identifier; serial number; DoD recognized unique identification equivalent; and for serialization within the part, lot, or batch number only: original part, lot, or batch number) on items requiring marking by paragraph (c)(1) of this clause, based on the criteria provided in MIL-STD-130, Identification Marking of U.S. Military Property, latest version;
				(C) Label shipments, storage containers and packages that contain uniquely identified items in accordance with the requirements of MIL-STD-129, Military Marking for Shipment and Storage, latest version; and
				(D) Verify that the marks on items and labels on shipments, storage containers, and packages are machine readable and conform to the applicable standards. The contractor shall use an automatic identification technology device for this verification that has been programmed to the requirements of Appendix A, MIL-STD-130, latest version.
			(ii) The issuing agency code--
				(A) Shall not be placed on the item; and
				(B) Shall be derived from the data qualifier for the enterprise identifier.
	(d) For each item that requires item unique identification under paragraph (c)(1)(i), (ii), or (iv) of this clause or when item unique identification is provided under paragraph (c)(1)(v), in addition to the information provided as part of the Material Inspection and Receiving Report specified elsewhere in this contract, the Contractor shall report at the time of delivery, either as part of the Material Inspection and Receiving Report, the following information:
		(1) Unique item identifier.
		(2) Unique item identifier type.
		(3) Issuing agency code (if concatenated unique item identifier is used).
		(4) Enterprise identifier (if concatenated unique item identifier is used).
		(5) Original part number (if there is serialization within the original part number).
		(6) Lot or batch number (if there is serialization within the lot or batch number).
		(7) Current part number (optional and only if not the same as the original part number).
		(8) Current part number effective date (optional and only if current part number is used).
		(9) Serial number (if concatenated unique item identifier is used).
		(10) Government's unit acquisition cost.
		(11) Unit of measure.
		(12) Type designation of the item as specified in the contract schedule, if any.
		(13) Whether the item is an item of Special Tooling or Special Test Equipment.
		(14) Whether the item is covered by a warranty.
	(e) For embedded subassemblies, components, and parts that require DoD unique item identification under paragraph (c)(1)(iii) of this clause or when item unique identification is provided under paragraph (c)(1)(v), the Contractor shall report as part of the Material Inspection and Receiving Report specified elsewhere in this contract, the following information:
		(1) Unique item identifier of the parent item under paragraph (c)(1) of this clause that contains the embedded subassembly, component, or part.
		(2) Unique item identifier of the embedded subassembly, component, or part.
		(3) Unique item identifier type.**
		(4) Issuing agency code (if concatenated unique item identifier is used).**
		(5) Enterprise identifier (if concatenated unique item identifier is used).**
		(6) Original part number (if there is serialization within the original part number).**
		(7) Lot or batch number (if there is serialization within the lot or batch number).**
		(8) Current part number (optional and only if not the same as the original part number).**
		(9) Current part number effective date (optional and only if current part number is used).**
		(10) Serial number (if concatenated unique item identifier is used).**
		(11) Description.
			** Once per item.
	(f) The Contractor shall submit the information required by paragraphs (d) and (e) of this clause as follows:
		(1) End items shall be reported using the receiving report capability in Wide Area WorkFlow (WAWF) in accordance with the clause at 252.232-7003. If WAWF is not required by this contract, and the contractor is not using WAWF, follow the procedures at http://dodprocurementtoolbox.com/site/uidregistry/.
		(2) Embedded items shall be reported by one of the following methods--
			(i) Use of the embedded items capability in WAWF;
			(ii) Direct data submission to the IUID Registry following the procedures and formats at http://dodprocurementtoolbox.com/site/uidregistry/; or
			(iii) Via WAWF as a deliverable attachment for exhibit line item number (fill in) _____, Unique Item Identified Report for Embedded Items, Contract Data Requirements List, DD Form 1423.
	(g) Subcontracts. If the Contractor acquires by subcontract, any item(s) for which item unique identification is required in accordance with paragraph (c)(1) of this clause, the Contractor shall include this clause, including this paragraph (g), in the applicable subcontract(s), including subcontracts for commercial items.

252.225-7048	EXPORT CONTROLLED ITEMS (JUN 2013)
	(a) Definition. “Export-controlled items,” as used in this clause, means items subject to the Export Administration Regulations (EAR)(15 CFR Parts 730-774) or the International Traffic in Arms Regulations (ITAR)(22 CFR Parts 120-130). The term includes -- “Defense items,” defined in the Arms Export Control Act. 22 U.S.C. 2778(j)(4)(A), as defense articles, defense services, and related technical data, and further defined in the ITAR, 22 CFR Part 120; and
		“Items,” defined in the EAR as "commodities". "software", and "technology," terms that are also defined in the EAR, 15 CFR 772.1.
	(b) The Contractor shall comply with all applicable laws and regulations regarding export-controlled items, including, but not limited to, the requirement for contractors to register with the Department of State in accordance with the ITAR. The Contractor shall consult with the Department of State regarding any questions relating to compliance with the ITAR and shall consult with the Department of Commerce regarding any questions relating to compliance with the EAR.
	(c) The Contractor's responsibility to comply with all applicable laws and regulations regarding export-controlled items exists independent of, and is not established or limited by, the information provided by this clause.
	(d) Nothing in the terms of this contract adds, changes, supersedes, or waives any of the requirements of applicable Federal laws, Executive orders, and regulations, including but not limited to --
		(1) The Export Administration Act of 1979, as amended (50 U.S.C. App. 2401, et seq.);
		(2) The Arms Export Control Act (22 U.S.C. 2751, et seq.);
		(3) The International Emergency Economic Powers Act (50 U.S.C. 1701, et seq.);
		(4) The Export Administration Regulations (15 CFR Parts 730-774);
		(5) The International Traffic in Arms Regulations (22 CFR Parts 120-130); and
		(6) Executive Order 13222, as extended.
	(e) The Contractor shall include the substance of this clause, including this paragraph (e), in all subcontracts.

Section J - List of Documents, Exhibits and Other Attachments

Exhibit/Attachment Table of Contents

DOCUMENT TYPE

DESCRIPTION

PAGES

DATE

Attachment 1

Drawing Package

Section K - Representations, Certifications and Other Statements of Offerors

52.204-8

Annual Representations and Certifications

JAN 2017

52.209-2

Prohibition on Contracting with Inverted Domestic Corporations--Representation

NOV 2015

52.219-1 Alt I

Small Business Program Representations (Sept 2015) Alternate I

SEP 2015

52.225-25

Prohibition on Contracting with Entities Engaging in Certain Activities or Transactions Relating to Iran-- Representation and Certifications.

OCT 2015

252.203-7005

Representation Relating to Compensation of Former DoD Officials

NOV 2011

252.204-7007

Alternate A, Annual Representations and Certifications

JAN 2015

Section L - Instructions, Conditions and Notices to Bidders

INSTRUCTIONS

L. CONTENT OF PROPOSALS (SUPPLIES OR SERVICES)

PART A. GENERAL INSTRUCTIONS

1.0 GENERAL

Offerors are required to submit sufficient information concerning all evaluation factors to enable Government personnel to fully ascertain the capabilities of the Offeror to perform the requirements. The proposal must be sufficient in detail and scope to permit evaluation and provide evaluators a clear understanding of the Offeror’s capability to meet the defined elements as required by the solicitation. All proposals must clearly and convincingly demonstrate that the Offeror has a thorough understanding of the requirements and is able, willing and competent to devote the resources necessary to meet the requirements, and that the Offeror has valid and practical solutions for all requirements. The Offeror must respond to all requirements of the solicitation and not alter or rearrange the solicitation. The Offeror has the burden of proof to demonstrate compliance with all the evaluation factors identified in this solicitation. Offerors are advised that the Government may incorporate any part of the Offeror’s proposal deemed beneficial to the Government into the final contract. With the exception of the Price volume, no cost or pricing information should appear in any volume. In addition to submitting a proposal which is fully compliant to the solicitation, alternate proposals are acceptable; however, the proposal must meet all requirements of the solicitation.

In presenting material in the proposal, the Offeror is advised that quality of information is more important than quantity. Clarity, brevity, and logical organization should be emphasized during proposal preparation. It is the responsibility of the offeror to present enough information to allow the various work efforts and price to be meaningfully evaluated without discussions. Unsubstantiated statements that the prospective Offeror understands, can or will comply with the requirements, or paraphrasing the requirements or parts thereof are considered inadequate and may render a rating of unacceptable.

The Offeror shall…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated Nov 14, 2017.