USCG_CS_Solicitation.docx

DOCX document 108 KB Posted Aug 23, 2018

Attached to: award of Coast Guard Minotaur Crewstations
Solicitation number: N6134018R0081
Issued by: Department of the Navy Naval Air Systems Command Naval Air Warfare Center

View the file

Other files

File	Type	Posted
Technical_Evaluation_Matrix-CG_Crewstations.docx	DOCX document	Aug 23, 2018
Coast_Guard_Crewman_Station_SOW_20_Aug_2018.docx	DOCX document	Aug 23, 2018
solicitation_cover_page_-_Coast_Guard_Crewstations.pdf	PDF	Aug 23, 2018
N6134018R0081_Coast_Guard_Crewman_Station_SOW_21_June_2018.docx	DOCX document	Jul 31, 2018

On GovTribe

Work with this file

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.

N6134018R0081

Section B - Supplies or Services and Prices

ITEM NO

SUPPLIES/SERVICES

QUANTITY

UNIT

UNIT PRICE

AMOUNT

Each

CG Student Station Hardware

FFP

Procure CG Student Station Hardware-Prototype NOTE: The requirements in DFARS 252.211-7003, Item Identification and Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

FOB: Destination

NSN: 70501019947721

PURCHASE REQUEST NUMBER: 1300707290

NET AMT

PSC Code 7050

ITEM NO

SUPPLIES/SERVICES

QUANTITY

UNIT

UNIT PRICE

AMOUNT

Each

Crewman Station Modifications

Modifications to the Crewstation Trainers- To Be Negotiated FOB: Destination

NET AMT

PSC Code 7050

ITEM NO

SUPPLIES/SERVICES

QUANTITY

UNIT

UNIT PRICE

AMOUNT

CDRLS-Not Separately Priced

Crewstation CDRLS- Not Separately Priced

NET AMT

Section C - Descriptions and Specifications

CLAUSES INCORPORATED BY FULL TEXT

5252.211-9509

INCORPORATION OF THE CONTRACTOR'S TECHNICAL PROPOSAL (NAVAIR)(OCT 2005)

The Contractor's Technical Proposal Number [Enter technical proposal number], dated [Enter document date], and any amendments/addendums thereof, is incorporated herein by reference, unless otherwise specified, with the same force and effect as if set forth in full text. Nothing in the Contractor's proposal shall constitute a waiver of any of the provisions of the contract, including the Statement(s) of Work and Specification. For purposes of FAR Clause 52.215-8, “Order of Precedence”, the Contractor's technical proposal shall be considered a "Specification" but the Government's Specification shall take precedence over the Contractor's technical proposal.

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

Destination

Government

Origin

Government

0002

N/A

Government

0003

N/A

CLAUSES INCORPORATED BY REFERENCE

52.246-15

Certificate of Conformance

APR 1984

5252.246-9513

INSPECTION AND ACCEPTANCE OF TRAINING DEVICES (NAVAIR) (OCT 2007)

Inspection of Device [Crewstation Trainer] shall be accomplished in accordance with the Specification/Statement of Work entitled [Crewstation SOW], dated [20 August 2018], and the Government approved Contract Data Requirements List (CDRL), DD Form 1423, data item entitled Test Procedures and Test/Inspection Reports (TP and TIR). Any Government inspection/acceptance to be conducted in the contractor's facility, will be performed by the Administrative Contracting Officer's quality assurance representative with support of [NAWCTSD.] technical personnel. Final inspection to be performed at the device delivery site will be directed and witnessed by the technical representative of the Procuring Contracting Officer (PCO). Final acceptance of this Contract Line Item will be evidenced by signature of the PCO or his duly authorized representative on a DD Form 250, Material Inspection and Receiving Report.

Section F - Deliveries or Performance

DELIVERY INFORMATION

CLIN

DELIVERY DATE

QUANTITY

SHIP TO ADDRESS

DODAAC / CAGE

0001

04-JAN-2019

N/A

0002

POP 04-JAN-2019 TO

04-APR-2019

N/A

NAWCTSD

HOLMES, ROB

12211 SCIENCE DR

CROSS WARFARE

ORLANDO FL 32826-3224

407-380-4448

N61340

0003

N/A

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.204-7006

Billing Instructions

OCT 2005

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: N61340

(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		N64142
Issue By DoDAAC		N61340
Admin DoDAAC			N61340
Inspect By DoDAAC		N61340
Ship To Code			N61340
Ship From Code			Leave Blank
Mark For Code			Leave Blank
Service Approver (DoDAAC)	Leave Blank
Service Acceptor (DoDAAC)	Leave Blank
Accept at Other DoDAAC	Leave Blank
LPO DoDAAC			Leave Blank
DCAA Auditor DoDAAC		Leave Blank
Other DoDAAC(s)		Leave Blank

(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.

POC:eric.estepp@navy.mil (viewer); robb.holmes@navy.mil (approver); sharon.alicia@navy.mil (viewer) ALT POC:____________________________________________________________________________

(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: N/A
	(2) For technical WAWF help, contact the WAWF helpdesk at 866-618-5988.

5252.201-9500	TECHNICAL POINT OF CONTACT (TPOC)(NAVAIR)(SEP 2012)
	(a) The Technical Point of Contact (TPOC) for this contract is:[Robb Holmes 12211 Science Drive, Orlando FL 32826, (407) 380-4448]
	(b) This individual is not a Contracting Officer nor a Contracting Officer's Representative (COR)/Task Order COR (TOCOR) and has no authority to make changes, verbally or otherwise, to the existing contract or order. Further, no authority has been delegated to this individual by the Procuring Contracting Officer (PCO).
	(c) The contractor may use this technical POC for technical questions related to the existing contract or order. Also, as a representative of the requiring activity, the TPOC may perform or assist in such areas as: base access forms, security related issues, IT access requirements, Contractor Performance Assessment Reporting System (CPARS), clarification of technical requirements, and statement of work inquires.
	(d) The contractor shall immediately notify the Procuring Contracting Officer in writing if the contractor interprets any action by the TPOC to be a change to the existing contract.

G-TXT-PAY	PAYMENT INSTRUCTIONS (APR 2018)
	FOR GOVERNMENT USE ONLY

Contract/Order Payment Clause

Type of Payment Request

Supply

Service

Construction

Payment Office

Allocation Method

52.212-4 (Alt I), Contract Terms and Conditions—Commercial Items 52.216-7, Allowable Cost and Payment 52.232-7, Payments under Time-and-Materials and Labor-Hour Contracts

Cost Voucher

N/A

Line item specific proration. If there is more than one ACRN within a deliverable line or deliverable subline item, the funds will be allocated in the same proportion as the amount of funding currently unliquidated for each ACRN on the deliverable line or deliverable subline item for which payment is requested.

52.232-1, Payments

Navy Shipbuilding Invoice (Fixed Price)

N/A

Line Item specific by fiscal year. If there is more than one ACRN within a deliverable line or deliverable subline item, the funds will be allocated using the oldest funds. In the event of a deliverable line or deliverable subline item with two ACRNs with the same fiscal year, those amounts will be prorated to the available unliquidated funds for that year.

52.232-1, Payments;

52.232-2, Payments under Fixed-Price Research and Development Contracts;

52.232-3, Payments under Personal Services Contracts;

52.232-4, Payments under Transportation Contracts and Transportation-Related Services Contracts; and 52.232-6, Payments under Communication Service Contracts with Common Carriers

Invoice

N/A

Line Item Specific proration. If there is more than one ACRN within a deliverable line or deliverable subline item, the funds will be allocated in the same proportion as the amount of funding currently unliquidated for each ACRN on the deliverable line or deliverable subline item for which payment is requested.

52.232-5, Payments Under Fixed-Price Construction Contracts

Construction Payment Invoice

N/A

52.232-16, Progress Payments

Progress Payment*

N/A

Contract-wide proration. Funds shall be allocated in the same proportion as the amount of funding currently unliquidated for each ACRN. Progress Payments are considered contract level financing, and the “contract price” shall reflect the fixed price portion of the contract per FAR 32.501-3.

52.232-29, Terms for Financing of Purchases of Commercial Items;

52.232-30, Installment Payments for Commercial Items

Commercial Item Financing*

N/A

Specified in approved payment. The contracting officer shall specify the amount to be paid and the account(s) to be charged for each payment approval in accordance with FAR 32.207(b)(2) and 32.1007(b)(2).

52.232-32, Performance-Based Payments

Performance-Based Payments*

N/A

252.232-7002, Progress Payments for Foreign Military Sales Acquisitions

Progress Payment*

N/A

Allocate costs among line items and countries in a manner acceptable to the Administrative Contracting Officer.

*Liquidation of Financing Payments. Liquidation will be applied by the payment office against those ACRNs which are identified by the payment instructions for the delivery payment and in keeping with the liquidation provision of the applicable contract financing clause (i.e., progress payment, performance-based payment, or commercial item financing).

Section H - Special Contract Requirements

5252.227-9501	INVENTION DISCLOSURES AND REPORTS (NAVAIR) (MAY 1998)
	(a) In accordance with the requirements of the Patent Rights clause of this contract, the contractor shall submit "Report of Inventions and Subcontracts" (DD Form 882) along with written disclosure of inventions to the designated Contract Administrator.
	(b) The Contract Administrator will forward such reports and disclosures directly to the appropriate Patent Counsel, designated below, for review and recommendations, after which the reports will be returned to the Contract Administrator.

Name and address of Patent Counsel:

Office of Counsel, Code K00000D

Naval Air Warfare Center Weapons Division

1 Administration Circle, Stop 1009

China Lake, California 93555-6100

(c) The above designated Patent Counsel will represent the Procurement Contracting Officer with regard to invention reporting matters arising under this contract.

(d) A copy of each report and disclosure shall be forwarded to the Procuring Contracting Officer.

(e) The contractor shall furnish the Contracting Officer a final report within three (3) months after completion of the contracted work listing all subject inventions or certifying that there were no such inventions, and listing all subcontracts at any tier containing a patent rights clause or certifying that there were no such subcontracts.

5252.239-9504	SYSTEM CONFIGURATION: INFORMATION TECHNOLOGY MAINTENANCE CONTRACTS (NAVAIR) (OCT 2005)
	(a) The Government reserves the right, throughout the performance period, to change equipment/software to be maintained under the contract (1) as a result of upgrades, deletions, or substitutions of equipment/software covered by this contract, or (2) through requirements for additional hardware/software capacity due to resource expansion. Changes to system configuration will be accomplished as follows:
		(1) Additions and deletions of equipment/software identical to Contract Line Items listed in Section B may be effected by a Change Order, and the contract price adjusted by the unit prices listed in Section B. These additions and deletions to be effected by Change Order shall pertain only to those items specifically make and model version number in Section B.
		(2) Additions of equipment/software similar to those listed in Section B shall be effected by a Supplemental Agreement, after negotiation of price for maintenance of the additional equipment/software. Similar items are defined as those that achieve the same system capability or have the same functionality as the items intended for use in Section B, but may be different model numbers or be manufactured by firms other than those shown in Section B.
	(b) The cumulative effect of the above additions and deletions will not increase the contract price by an amount exceeding [insert percentage] of the total contract value for the base period and each option period.

5252.242-9502	TECHNICAL DIRECTION (NAVAIR) (MAY 2011)
	(a) Definition. Technical Direction Letters (TDLs) are a means of communication between the Contracting Officer’s Representative (COR) or Task Order Manager (TOM), and the contractor to answer technical questions, provide technical clarification, and give technical direction regarding the content of the Statement of Work (SOW) of a Contract, Order, or Agreement; herein after referred to as contract.
		(i) "Technical Direction" means clarification of contractual requirements or direction of a technical nature, within the context of the SOW of the contract.
	(b) Scope. The Defense Federal Acquisition Regulation Supplement (DFARS) 201.602-2 states that the Contracting Officer may designate qualified personnel as a COR. In this capacity, the COR or TOM may provide Technical Direction to the contractor, so long as the Technical Direction does not make any commitment or change that affects price, quality, quantity, delivery, or other terms and conditions of the contract. This Technical Direction shall be provided consistent with the limitations specified below.
	(c) Limitations. When necessary, Technical Direction concerning details of requirements set forth in the contract, shall be given through issuance of TDLs prepared by the COR or TOM subject to the following limitations.
		(i) The TDL, and any subsequent amendments to the TDL, shall be in writing and signed by both the COR or TOM, and the Contracting Officer prior to issuance of the TDL to the contractor. Written TDLs are the only medium permitted for use when technical direction communication is required. Any other means of communication (including such things as Contractor Service Request Letters, Authorization Letters, or Material Budget Letters) are not permissible means of communicating technical direction during contract performance.
		(ii) In the event of an urgent situation, the COR/TOM may issue the TDL directly to the contractor prior to obtaining the Contracting Officer's signature.
		(iii) Each TDL issued is subject to the terms and conditions of the contract and shall not be used to assign new work, direct a change to the quality or quantity of supplies and/or services delivered, change the delivery date(s) or period of performance of the contract, or change any other conditions of the contract. TDLs shall only provide additional clarification and direction regarding technical issues. In the event of a conflict between a TDL and the contract, the contract shall take precedence.
		(iv) Issuance of TDLs shall not incur an increase or decrease to the contract price, estimated contract amount (including fee), or contract funding, as applicable. Additionally, TDLs shall not provide clarification or direction of a technical nature that would require the use of existing funds on the contract beyond the period of performance or delivery date for which the funds were obligated.
		(v) TDLs shall provide specific Technical Direction to the contractor only for work specified in the SOW and previously negotiated in the contract. TDLs shall not require new contract deliverables that may cause the contractor to incur additional costs.
		(vi) When, in the opinion of the contractor, a TDL calls for effort outside the terms and conditions of the contract or available funding, the contractor shall notify the Contracting Officer in writing, with a copy to the COR or TOM, within two (2) working days of having received the Technical Direction. The contractor shall undertake no performance to comply with the TDL until the matter has been resolved by the Contracting Officer through a contract modification or other appropriate action.
		(vii) If the contractor undertakes work associated with a TDL that is considered to be outside the scope of the contract, the contractor does so at its own risk and is not subject to recover any costs and fee or profit associated with the scope of effort.

Section I - Contract Clauses

52.202-1

Definitions

NOV 2013

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-9

Personal Identity Verification of Contractor Personnel

JAN 2011

52.204-10

Reporting Executive Compensation and First-Tier Subcontract Awards

OCT 2016

52.204-12

Unique Entity Identifier Maintenance

OCT 2016

52.204-13

System for Award Management Maintenance

OCT 2016

52.204-19

Incorporation by Reference of Representations and Certifications.

DEC 2014

52.204-21

Basic Safeguarding of Covered Contractor Information Systems

JUN 2016

52.209-6

Protecting the Government's Interest When Subcontracting With Contractors Debarred, Suspended, or Proposed for Debarment

OCT 2015

52.209-10

Prohibition on Contracting With Inverted Domestic Corporations

NOV 2015

52.211-5

Material Requirements

AUG 2000

52.219-6

Notice Of Total Small Business Set-Aside

NOV 2011

52.219-14

Limitations On Subcontracting

JAN 2017

52.219-27

Notice of Service-Disabled Veteran-Owned Small Business Set-Aside

NOV 2011

52.219-28

Post-Award Small Business Program Rerepresentation

JUL 2013

52.222-3

Convict Labor

JUN 2003

52.222-19

Child Labor -- Cooperation with Authorities and Remedies

JAN 2018

52.222-21

Prohibition Of Segregated Facilities

APR 2015

52.222-26

Equal Opportunity

SEP 2016

52.222-35

Equal Opportunity for Veterans

OCT 2015

52.222-36

Equal Opportunity for Workers with Disabilities

JUL 2014

52.222-37

Employment Reports on Veterans

FEB 2016

52.222-50

Combating Trafficking in Persons

MAR 2015

52.222-54

Employment Eligibility Verification

OCT 2015

52.223-6

Drug-Free Workplace

MAY 2001

52.223-15

Energy Efficiency in Energy-Consuming Products

DEC 2007

52.223-18

Encouraging Contractor Policies To Ban Text Messaging While Driving

AUG 2011

52.224-1

Privacy Act Notification

APR 1984

52.224-2

Privacy Act

APR 1984

52.224-3

Privacy Training

JAN 2017

52.227-1

Authorization and Consent

DEC 2007

52.227-2

Notice And Assistance Regarding Patent And Copyright Infringement

DEC 2007

52.227-11

Patent Rights--Ownership By The Contractor

MAY 2014

52.229-3

Federal, State And Local Taxes

FEB 2013

52.232-1

Payments

APR 1984

52.232-8

Discounts For Prompt Payment

FEB 2002

52.232-9

Limitation On Withholding Of Payments

APR 1984

52.232-11

Extras

APR 1984

52.232-23

Assignment Of Claims

MAY 2014

52.232-25

Prompt Payment

JAN 2017

52.232-33

Payment by Electronic Funds Transfer--System for Award Management

JUL 2013

52.232-39

Unenforceability of Unauthorized Obligations

JUN 2013

52.232-40

Providing Accelerated Payments to Small Business Subcontractors

DEC 2013

52.233-1

Disputes

MAY 2014

52.233-3

Protest After Award

AUG 1996

52.233-4

Applicable Law for Breach of Contract Claim

OCT 2004

52.237-11

Accepting and Dispensing of $1 Coin

SEP 2008

52.239-1

Privacy or Security Safeguards

AUG 1996

52.242-13

Bankruptcy

JUL 1995

52.243-1

Changes--Fixed Price

AUG 1987

52.244-6

Subcontracts for Commercial Items

NOV 2017

52.245-1

Government Property

JAN 2017

52.246-23

Limitation Of Liability

FEB 1997

52.249-1

Termination For Convenience Of The Government (Fixed Price) (Short Form)

APR 1984

52.249-8

Default (Fixed-Price Supply & Service)

APR 1984

52.253-1

Computer Generated Forms

JAN 1991

252.201-7000

Contracting Officer's Representative

DEC 1991

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.203-7003

Agency Office of the Inspector General

DEC 2012

252.204-7000

Disclosure Of Information

OCT 2016

252.204-7002

Payment For Subline Items Not Separately Priced

DEC 1991

252.204-7003

Control Of Government Personnel Work Product

APR 1992

252.204-7005

Oral Attestation of Security Responsibilities

NOV 2001

252.204-7012

Safeguarding Covered Defense Information and Cyber Incident Reporting

OCT 2016

252.204-7014

Limitations on the Use or Disclosure of Information by Litigation Support Contractors

MAY 2016

252.204-7015

Notice of Authorized Disclosure of Information for Litigation Support

MAY 2016

252.209-7004

Subcontracting With Firms That Are Owned or Controlled By The Government of a Country that is a State Sponsor of Terrorism

OCT 2015

252.211-7008

Use of Government-Assigned Serial Numbers

SEP 2010

252.223-7004

Drug Free Work Force

SEP 1988

252.225-7001

Buy American And Balance Of Payments Program-- Basic

DEC 2017

252.225-7048

Export-Controlled Items

JUN 2013

252.227-7014

Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation

FEB 2014

252.227-7015

Technical Data--Commercial Items

FEB 2014

252.227-7016

Rights in Bid or Proposal Information

JAN 2011

252.227-7019

Validation of Asserted Restrictions--Computer Software

SEP 2016

252.227-7020

Rights In Special Works

JUN 1995

252.227-7026

Deferred Delivery Of Technical Data Or Computer Software

APR 1988

252.227-7027

Deferred Ordering Of Technical Data Or Computer Software

APR 1988

252.227-7039

Patents--Reporting Of Subject Inventions

APR 1990

252.231-7000

Supplemental Cost Principles

DEC 1991

252.232-7003

Electronic Submission of Payment Requests and Receiving Reports

JUN 2012

252.232-7003

Electronic Submission of Payment Requests and Receiving Reports

JUN 2012

252.232-7010

Levies on Contract Payments

DEC 2006

252.239-7001

Information Assurance Contractor Training and Certification

JAN 2008

252.239-7010

Cloud Computing Services

OCT 2016

252.241-7001

Government Access

DEC 1991

252.243-7001

Pricing Of Contract Modifications

DEC 1991

252.243-7002

Requests for Equitable Adjustment

DEC 2012

252.244-7000

Subcontracts for Commercial Items

JUN 2013

252.245-7001

Tagging, Labeling, and Marking of Government-Furnished Property

APR 2012

252.245-7002

Reporting Loss of Government Property

DEC 2017

252.245-7003

Contractor Property Management System Administration

APR 2012

252.245-7004

Reporting, Reutilization, and Disposal

DEC 2017

252.246-7000

Material Inspection And Receiving Report

MAR 2008

252.246-7001

Warranty Of Data

MAR 2014

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
				_N/A_______________________________________________________________________________
				________________________________________________________________________________
				________________________________________________________________________________
			(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
				__N/A________________________________________________________________________________
				__________________________________________________________________________________
				__________________________________________________________________________________
					(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.227-7013	RIGHTS IN TECHNICAL DATA--NONCOMMERCIAL ITEMS (FEB 2014)
	(a) Definitions. As used in this clause:
		(1) “Computer data base” means a collection of data recorded in a form capable of being processed by a computer. The term does not include computer software.
		(2) “Computer program” means a set of instructions, rules, or routines recorded in a form that is capable of causing a computer to perform a specific operation or series of operations.
		(3) “Computer software” means computer programs, source code, source code listings, object code listings, design details, algorithms, processes, flow charts, formulae and related material that would enable the software to be reproduced, recreated, or recompiled. Computer software does not include computer data bases or computer software documentation.
		(4) “Computer software documentation” means owner's manuals, user's manuals, installation instructions, operating instructions, and other similar items, regardless of storage medium, that explain the capabilities of the computer software or provide instructions for using the software.
		(5) “Covered Government support contractor” means a contractor (other than a litigation support contractor covered by 252.204-7014) under a contract, the primary purpose of which is to furnish independent and impartial advice or technical assistance directly to the Government in support of the Government's management and oversight of a program or effort (rather than to directly furnish an end item or service to accomplish a program or effort), provided that the contractor—
			(i) Is not affiliated with the prime contractor or a first-tier subcontractor on the program or effort, or with any direct competitor of such prime contractor or any such first-tier subcontractor in furnishing end items or services of the type developed or produced on the program or effort; and
			(ii) Receives access to technical data or computer software for performance of a Government contract that contains the clause at 252.227-7025, Limitations on the Use or Disclosure of Government-Furnished Information Marked with Restrictive Legends.
		(6) “Detailed manufacturing or process data” means technical data that describe the steps, sequences, and conditions of manufacturing, processing or assembly used by the manufacturer to produce an item or component or to perform a process.
		(7) “Developed” means that an item, component, or process exists and is workable. Thus, the item or component must have been constructed or the process practiced. Workability is generally established when the item, component, or process has been analyzed or tested sufficiently to demonstrate to reasonable people skilled in the applicable art that there is a high probability that it will operate as intended. Whether, how much, and what type of analysis or testing is required to establish workability depends on the nature of the item, component, or process, and the state of the art. To be considered “developed”, the item, component, or process need not be at the stage where it could be offered for sale or sold on the commercial market, nor must the item, component, or process be actually reduced to practice within the meaning of Title 35 of the United States Code.
		(8) “Developed exclusively at private expense” means development was accomplished entirely with costs charged to indirect cost pools, costs not allocated to a government contract, or any combination thereof.
			(i) Private expense determinations should be made at the lowest practicable level.
			(ii) Under fixed-price contracts, when total costs are greater than the firm-fixed-price or ceiling price of the contract, the additional development costs necessary to complete development shall not be considered when determining whether development was at government, private, or mixed expense.
		(9) “Developed exclusively with government funds” means development was not accomplished exclusively or partially at private expense.
		(10) “Developed with mixed funding” means development was accomplished partially with costs charged to indirect cost pools and/or costs not allocated to a government contract, and partially with costs charged directly to a government contract.
		(11) “Form, fit, and function data” means technical data that describes the required overall physical, functional, and performance characteristics (along with the qualification requirements, if applicable) of an item, component, or process to the extent necessary to permit identification of physically and functionally interchangeable items.
		(12) “Government purpose” means any activity in which the United States Government is a party, including cooperative agreements with international or multi-national defense organizations, or sales or transfers by the United States Government to foreign governments or international organizations. Government purposes include competitive procurement, but do not include the rights to use, modify, reproduce, release, perform, display, or disclose technical data for commercial purposes or authorize others to do so.
		(13) “Government purpose rights” means the rights to--
			(i) Use, modify, reproduce, release, perform, display, or disclose technical data within the Government without restriction; and
			(ii) Release or disclose technical data outside the Government and authorize persons to whom release or disclosure has been made to use, modify, reproduce, release, perform, display, or disclose that data for United States government purposes.
		(14) “Limited rights” means the rights to use, modify, reproduce, release, perform, display, or disclose technical data, in whole or in part, within the Government. The Government may not, without the written permission of the party asserting limited rights, release or disclose the technical data outside the Government, use the technical data for manufacture, or authorize the technical data to be used by another party, except that the Government may reproduce, release, or disclose such data or authorize the use or reproduction of the data by persons outside the Government if--
			(i) The reproduction, release, disclosure, or use is--
				(A) Necessary for emergency repair and overhaul; or
				(B) A release or disclosure to--
					(1) A covered Government support contractor in performance of its covered Government support contract for use, modification, reproduction, performance, display, or release or disclosure to a person authorized to receive limited rights technical data; or
					(2) A foreign government, of technical data other than detailed manufacturing or process data, when use of such data by the foreign government is in the interest of the Government and is required for evaluational or informational purposes;
			(ii) The recipient of the technical data is subject to a prohibition on the further reproduction, release, disclosure, or use of the technical data; and
			(iii) The contractor or subcontractor asserting the restriction is notified of such reproduction, release, disclosure, or use.
		(15) “Technical data” means recorded information, regardless of the form or method of the recording, of a scientific or technical nature (including computer software documentation). The term does not include computer software or data incidental to contract administration, such as financial and/or management information.
		(16) “Unlimited rights” means rights to use, modify, reproduce, perform, display, release, or disclose technical data in whole or in part, in any manner, and for any purpose whatsoever, and to have or authorize others to do so.
	(b) Rights in technical data. The Contractor grants or shall obtain for the Government the following royalty free, world-wide, nonexclusive, irrevocable license rights in technical data other than computer software documentation (see the Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation clause of this contract for rights in computer software documentation):
		(1) Unlimited rights. The Government shall have unlimited rights in technical data that are--
			(i) Data pertaining to an item, component, or process which has been or will be developed exclusively with Government funds;
			(ii) Studies, analyses, test data, or similar data produced for this contract, when the study, analysis, test, or similar work was specified as an element of performance;
			(iii) Created exclusively with Government funds in the performance of a contract that does not require the development, manufacture, construction, or production of items, components, or processes;
			(iv) Form, fit, and function data;
			(v) Necessary for installation, operation, maintenance, or training purposes (other than detailed manufacturing or process data);
			(vi) Corrections or changes to technical data furnished to the Contractor by the Government;
			(vii) Otherwise publicly available or have been released or disclosed by the Contractor or subcontractor without restrictions on further use, release or disclosure, other than a release or disclosure resulting from the sale, transfer, or other assignment of interest in the technical data to another party or the sale or transfer of some or all of a business entity or its assets to another party;
			(viii) Data in which the Government has obtained unlimited rights under another Government contract or as a result of negotiations; or
			(ix) Data furnished to the Government, under this or any other Government contract or subcontract there under, with--

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.