N6134018R0034_LCAC_SBC4BC7_Update_Solicitation.pdf

CODE

(Hour)

PAGE(S)

until 02:00 PM local time 05 Apr 2018

X

A

X B

X C X D

EX

X

G

F 33 - 36

37 - 43

X H 44 - 48 shannon.walyus@navy .mil

RATING PAGE OF PAGES

7. ISSUED BY

(Date)

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

Previous Edition is Unusable 33-134 STANDARD FORM 33 (REV. 9-97)

Prescribed by GSA

FAR (48 CFR) 53.214(c)

1 48

(If other than Item 7)

15A. NAME 16. NAME AND TITLE OF PERSON AUTHORIZED TO

AND

ADDRESS

SIGN OFFER (Type or print)

OF

OFFEROR

AMENDMENT NO. DATE

15B. TELEPHONE NO (Include area code) 17. SIGNATURE15C. CHECK IF REMITTANCE ADDRESS

IS DIFFERENT FROM ABOVE - ENTER

SUCH ADDRESS IN SCHEDULE.

18. OFFER DATE

1. THIS CONTRACT IS A RATED ORDER

UNDER DPAS (15 CFR 700)

2. CONTRACT NO.

N61340 8. ADDRESS OFFER TO

See Item 7

9. Sealed offers in original and copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if handcarried, in the depository located in

CAUTION - LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and conditions contained in this solicitation.

10. FOR INFORMATION

CALL:

A. NAME (NO COLLECT CALLS)

SHANNON WALYUS 407-380-4628

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

4 - 5

J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

7 - 8 X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 9 - 10 X

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror) 11 - 15 X M

L INSTRS., CONDS., AND NOTICES TO OFFERORS

EVALUATION FACTORS FOR AWARD

NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. DISCOUNT FOR PROMPT PAYMENT

(See Section I, Clause No. 52.232-8)

14. ACKNOWLEDGMENT OF AMENDMENTS

(The offeror acknowledges receipt of amendments

AMENDMENT NO. DATE

to the SOLICITATION for offerors and related documents numbered and dated):

FACILITY

12. In compliance with the above, the undersigned agrees, if this offer is accepted within calendar days (60 calendar days unless a different period

SOLICITATION, OFFER AND AWARD

X

(X) SEC. DESCRIPTION (X) SEC. DESCRIPTION PAGE(S)

PART I - THE SCHEDULE

26. NAME OF CONTRACTING OFFICER (Type or print) 27. UNITED STATES OF AMERICA 28. AWARD DATE

EMAIL:TEL: (Signature of Contracting Officer)

CODE CODE

B. TELEPHONE (Include area code) C. E-MAIL ADDRESS

AWARD (To be completed by Government)

19. ACCEPTED AS TO ITEMS NUMBERED 20. AMOUNT 21. ACCOUNTING AND APPROPRIATION

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

10 U.S.C. 2304(c)( ) 41 U.S.C. 253(c)( ) (4 copies unless otherwise specified)

23. SUBMIT INVOICES TO ADDRESS SHOWN IN ITEM

24. ADMINISTERED BY (If other than Item 7) CODE 25. PAYMENT WILL BE MADE BY CODE

PART IV - REPRESENTATIO NS AND INSTRUCTIO NS

PART III - LIST O F DO CUMENTS, EXHIBITS AND O THER ATTACHMENTS

16 - 31

PART II - CO NTRACT CLAUSES

NAWCTSD 253

12211 SCIENCE DRIVE (253)

ORLANDO FL 32826-3224

FAX:

TEL:

FAX:

TEL:

NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".

SOLICITATION

6. REQUISITION/PURCHASE NO.5. DATE ISSUED

27 Feb 2018

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

N6134018R0034

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

EWTGLANT & EWTGPAC LCAC System Baseline

FFP

EWTGLANT & EWTGPAC LCAC System Baseline Configuration (SBC)

4/Block Cycle (BC) 7 Upgrade of Operations and Maintenance Classrooms, Virtual Environment LCAC (VELCAC) and LCAC Full Mission Trainer (FMT)

IAW SOW Attachment 1

FOB: Destination

NET AMT

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

EWTGLANT & EWTGPAC Tech Data (NSP)

FFP

IAW Exhibits A-E

NET AMT

Section C - Descriptions and Specifications

SECTION C

SECTION C

Attachment 1, Statement of Work dated 08 January 2018, defines the requirements to be performed under this contract.

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 D - Packaging and Marking

5252.247-9507 PACKAGING AND MARKING OF REPORTS (NAVAIR)(OCT 2005)

(a) All unclassified data shall be prepared for shipment in accordance with best commercial practice. Classified reports, data and documentation, if any, shall be prepared for shipment in accordance with the National Industry

Security Program Operating Manual, DoD 5220.22-M.

(b) The contractor shall prominently display on the cover of each report the following information:

(1) Name and business address of contractor.

(2) Contract Number/Delivery/Task order number.

(3) Contract/Delivery/Task order dollar amount.

(4) Whether the contract was competitively or non-competitively awarded.

(5) Name of sponsoring individual.

(6) Name and address of requiring activity.

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:

[TBD]

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

5252.247-9514 TECHNICAL DATA PACKING INSTRUCTIONS (NAVAIR)(SEP 1999)

Technical Data and Information shall be packed and packaged for domestic shipment in accordance with best commercial practices. The package or envelope should be clearly marked with any special markings specified in this contract (or delivery/task order), e.g., Contract Number, CLIN, Device No., and document title must be on the outside of the package. Classified reports, data and documentation, if applicable, shall be prepared for shipment in accordance with Defense Industrial Manual for Safeguarding Classified Information, DoD 5220.22M.

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 Destination Government

0002 Destination Government Destination Government

CLAUSES INCORPORATED BY REFERENCE

52.246-2 Inspection Of Supplies--Fixed Price AUG 1996

5252.246-9512 INSPECTION AND ACCEPTANCE (NAVAIR)(OCT 2005)

(a) Inspection and acceptance of the supplies or services to be furnished hereunder shall be performed by

[N61340].

(b) Acceptance of all Contract Line Items/Sub Line Items (CLINs/SLINs) shall be made by signature of the accepting authority on a DD 250 submitted through the WAWF system. Acceptance will only occur when the accepting authority is sure that inspections performed demonstrate compliance with contract requirements.

5252.246-9514 INSPECTION AND ACCEPTANCE OF TECHNICAL DATA AND INFORMATION

(NAVAIR)(FEB 1995)

Inspection and acceptance of technical data and information will be performed by the Procuring Contracting

Officer (PCO) or his duly authorized representative. Inspection of technical data and information will be performed by ensuring successful completion of the requirements set forth in the DD Form 1423, Contract Data Requirements

List (CDRL) and incorporation/resolution of Government review comments on the data items. Acceptance will be evidenced by execution of an unconditional DD Form 250, Material Inspection and Receiving Report, as appropriate, and/or upon receipt of a second endorsement acceptance by the PCO on the attachment to this contract entitled [NAWCTSD 4330/60 Data Item Transmittal/Acceptance/ Rejection Form]. The attached form will not be used for high cost data such as drawings, specifications, and technical manuals.

Section F - Deliveries or Performance

DELIVERY INFORMATION

CLIN DELIVERY DATE QUANTITY SHIP TO ADDRESS DODAAC /

CAGE

0001 18-JAN-2019 NAWCTSD

BILBRUCK, JOHN

12211 SCIENCE DRIVE

ORLANDO FL 32826-3224

407.380.8017

N61340

0002 18-JAN-2019 (SAME AS PREVIOUS LOCATION)

N61340

52.242-15 Stop-Work Order AUG 1989

52.242-17 Government Delay Of Work APR 1984

52.246-2 Inspection Of Supplies--Fixed Price AUG 1996

52.247-34 F.O.B. Destination NOV 1991

5252.247-9505 TECHNICAL DATA AND INFORMATION (NAVAIR)(FEB 1995)

Technical Data and Information shall be delivered in accordance with the requirements of the Contract Data

Requirements List, DD Form 1423, Exhibits A-E, attached hereto, and the following:

(a) The contractor shall concurrently deliver technical data and information per DD Form 1423, Blocks 12 and 13

(date of first/subsequent submission) to all activities listed in Block 14 of the DD Form 1423 (distribution and addresses) for each item. Complete addresses for the abbreviations in Block 14 are shown in paragraph (g) below.

Additionally, the technical data shall be delivered to the following cognizant codes, who are listed in Block 6 of the

DD Form 1423.

(1) PCO, Code [2.5.3.6.2].

(2) ACO, Code [TBD].

(b) Partial delivery of data is not acceptable unless specifically authorized on the DD Form 1423, or unless approved in writing by the PCO.

(c) The Government review period provided on the DD Form 1423 for each item commences upon receipt of all required data by the technical activity designated in Block 6.

(d) A copy of all other correspondence addressed to the Contracting Officer relating to data item requirements

(i.e., status of delivery) shall also be provided to the codes reflected above and the technical activity responsible for the data item per Block 6, if not one of the activities listed above.

(e) The PCO reserves the right to issue unilateral modifications to change the destination codes and addresses for all technical data and information at no additional cost to the Government.

(f) Unless otherwise specified in writing, rejected data items shall be resubmitted within thirty (30) days after receipt of notice of rejection.

(g) DD Form 1423, Block 14 Mailing Addresses:

Block 14 Abbreviation Email Address Mailing Address

NAWCTSD PJM John.Bilbruck@navy.mil

Naval Air Warfare Center

Training Systems Division

Attn: TSD 1.3.1.3.4

12211 Science Drive

Orlando, Florida 32826-3224

NAWCTSD ENGR Kimberly.Settle@navy.mil

Naval Air Warfare Center

Attn: TSD 4.6.8.8

NAWCTSD COMPUTER ENGR Bruce.Riner@navy.mil Naval Air Warfare Center

Attn: TSD 4.6.2.5

NAWCTSD LOGISTICS TBD Naval Air Warfare Center

Attn: TSD 6.6.4.10

NAWCTSD/EWTGLANT ISEO Arthur.Schoner@navy.mil Naval Air Warfare Center

Art Schoner, Code 4982LC, 1575 Gator Blvd Suite 138

Norfolk Virginia 23521-2740

(757) 343-8143

NAWCTSD/EWTGPAC ISEO TBD EWTGPAC ISEO

3423 GUADALCANAL

ROAD

BLDG 207

SAN DIEGO CA 92155

(619) 437-3093

Section G - Contract Administration Data

52.232-1 Payments APR 1984

52.232-25 Prompt Payment JAN 2017

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.

_______TBD____________________________________________________________________

(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: _________________________

Admin DoDAAC: _________________________

Inspect By DoDAAC: _________________________

Ship To Code: _________________________

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.

__________TBD__________________________________________________________________

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

5252.242-9511 CONTRACT ADMINISTRATION DATA (NAVAIR)(NOV 2017)

(a) Contract Administration Office.

(1) Contract administration functions (see FAR 42.302(a) and DFARS 242.302(a)) are assigned to: See the

ADMINISTERED BY Block on the face page of the contract, modification, or order.

(b) Special Instructions (see FAR 42.202(b) and (c)):

(1) The following contract administration functions are retained (see FAR 42.302(a) and DFARS 242.302(a)):

Functions Retained Retained for Performance By:

FAR 42.302(a)(3) N61340 (NAWCTSD)

FAR 42.302(a)(4) N61340 (NAWCTSD)

FAR 42.302(a)(40), (42), (44), (46) N61340 (NAWCTSD)

FAR 42.302(a)(58) N61340 (NAWCTSD)

FAR 42.302(a)(59) N61340 (NAWCTSD)

(2) The following additional contract administration functions are assigned (see FAR 42.302(b)):

Additional Functions Retained for Performance By:

No additional functions assigned No additional functions assigned

(c) Inquiries regarding payment should be referred to: MyInvoice through the

Wide Area Workflow eBusiness Suite: https://wawf.eb.mil.

Section H - Special Contract Requirements

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

_CLIN 0001__________________________________________________________________________

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

5252.204-9505 SYSTEM AUTHORIZATION ACCESS REQUEST NAVY (SAAR-N) REQUIREMENTS

FOR INFORMATION TECHNOLOGY(IT) (NAVAIR)(NOV 2017)

(a) Contractor personnel assigned to perform work under this contract may require access to Navy Information

Technology (IT) resources (e.g., computers, laptops, personal electronic devices/personal digital assistants

(PEDs/PDAs), NMCI, RDT&E networks, websites such as MyNAVAIR, and Navy Web servers requiring Common

Access Card (CAC) Public Key Infrastructure (PKI)). Contractor personnel (prime, subcontractor, consultants, and temporary employees) requiring access to Navy IT resources (including those personnel who previously signed

SAAR DD Form 2875) shall submit a completed System Authorization Access Request Navy (SAAR-N), OPNAV

5239/14 (Jul 2008) form or latest version thereof, and have initiated the requisite background investigation (or provide proof of a current background investigation) prior to accessing any Navy IT resources. The form and instructions for processing the SAAR-N form are available at:

https://navalforms.documentservices.dla.mil/formsDir/_OPNAV_5239_14_7631.pdf. Instruction Note: SAAR-N forms are required to be downloaded and then completed. The "E-MAIL SUBMIT" button on the SAAR-N form is not to be used.

(b) SAAR-N forms will be submitted to the Government Sponsor or Technical Point of Contact (TPOC) via the contractor's Facility Security Officer (FSO). The designated SAAR-N Government Sponsor or TPCO for contractor employees requiring IT access, John Bilbruck shall be responsible for signing and processing the SAAR-N forms.

For those contractors that do not have a FSO, SAAR-N forms shall be submitted directly to the designated SAAR-N

Government Sponsor or TPOC. Copies of the approved SAAR-N forms may be obtained through the designated

SAAR-N Government Sponsor or TPOC. Requests for access should be routed through the

NAVAIR_SAAR.fct@navy.mil mailbox.

(c) In order to maintain access to Navy IT resources, the contractor shall ensure completion of initial and annual

IA training, monitor expiration of requisite background investigations, and initiate re-investigations as required. If requested, the contractor shall provide to the designated SAAR-N Government Sponsor or TPOC documentation sufficient to prove that it is monitoring/tracking the SAAR-N requirements for its employees who are accessing

Navy IT resources. For those contractor personnel not in compliance with the requirements of this clause, access to

Navy IT resources will be denied/revoked.

(d) The SAAR-N form remains valid throughout contractual performance, inclusive of performance extensions and option exercises where the contract number does not change. Contractor personnel are required to submit a new

SAAR-N form only when they begin work on a new or different contract.

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.202-1 Definitions NOV 2013

52.203-3 Gratuities APR 1984

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.203-17 Contractor Employee Whistleblower Rights and Requirement

To Inform Employees of Whistleblower Rights

APR 2014

52.203-19 Prohibition on Requiring Certain Internal Confidentiality

Agreements or Statements

JAN 2017

52.204-10 Reporting Executive Compensation and First-Tier

Subcontract Awards

OCT 2016

52.204-13 System for Award Management Maintenance OCT 2016

52.204-16 Commercial and Government Entity Code Reporting JUL 2016

52.209-6 Protecting the Government's Interest When Subcontracting

With Contractors Debarred, Suspended, or Proposed for

Debarment

OCT 2015

52.209-9 Updates of Publicly Available Information Regarding

Responsibility Matters

JUL 2013

52.209-10 Prohibition on Contracting With Inverted Domestic

Corporations

NOV 2015

52.215-2 Audit and Records--Negotiation OCT 2010

52.215-8 Order of Precedence--Uniform Contract Format OCT 1997

52.215-14 Integrity of Unit Prices OCT 2010

52.215-21 Alt IV Requirements for Certified Cost or Pricing Data and Data

Other Than Certified Cost or Pricing Data -- Modifications

(Oct 2010) - Alternate IV

OCT 2010

52.219-4 Notice of Price Evaluation Preference for HUBZone Small

Business Concerns

OCT 2014

52.219-8 Utilization of Small Business Concerns NOV 2016

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 OCT 2016

52.222-20 Contracts for Materials, Supplies, Articles, and Equipment

Exceeding $15,000

MAY 2014

52.222-21 Prohibition Of Segregated Facilities APR 2015

52.222-22 Previous Contracts And Compliance Reports FEB 1999

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-38 Compliance With Veterans' Employment Reporting

Requirements

FEB 2016

52.222-40 Notification of Employee Rights Under the National Labor

Relations Act

DEC 2010

52.222-50 Combating Trafficking in Persons MAR 2015

52.222-54 Employment Eligibility Verification OCT 2015

52.223-5 Pollution Prevention and Right-to-Know Information MAY 2011

52.223-6 Drug-Free Workplace MAY 2001

52.223-18 Encouraging Contractor Policies To Ban Text Messaging

While Driving

AUG 2011

52.225-13 Restrictions on Certain Foreign Purchases JUN 2008

52.229-3 Federal, State And Local Taxes FEB 2013

52.232-11 Extras APR 1984

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 Alt I Disputes (May 2014) - Alternate I DEC 1991

52.233-2 Service Of Protest SEP 2006

52.233-3 Protest After Award AUG 1996

52.233-4 Applicable Law for Breach of Contract Claim OCT 2004

52.242-13 Bankruptcy JUL 1995

52.244-6 Subcontracts for Commercial Items NOV 2017

52.245-1 Government Property JAN 2017

52.245-9 Use And Charges APR 2012

52.249-2 Termination For Convenience Of The Government (Fixed-

Price)

APR 2012

52.249-8 Default (Fixed-Price Supply & Service) APR 1984

52.253-1 Computer Generated Forms JAN 1991

252.203-7000 Requirements Relating to Compensation of Former DoD

Officials

SEP 2011

252.203-7001 Prohibition On Persons Convicted of Fraud or Other Defense-

Contract-Related Felonies

DEC 2008

252.203-7002 Requirement to Inform Employees of Whistleblower Rights SEP 2013

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-7004 Alt A System for Award Management Alternate A FEB 2014

252.204-7008 Compliance With Safeguarding Covered Defense Information

Controls

OCT 2016

252.204-7012 Safeguarding Covered Defense Information and Cyber

Incident Reporting

OCT 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-7007 Reporting of Government-Furnished Property AUG 2012

252.223-7006 Prohibition On Storage, Treatment, and Disposal of Toxic or

Hazardous Materials

SEP 2014

252.225-7002 Qualifying Country Sources As Subcontractors DEC 2017

252.225-7021 Trade Agreements--Basic DEC 2017

252.225-7048 Export-Controlled Items JUN 2013

252.226-7001 Utilization of Indian Organizations and Indian-Owned

Economic Enterprises, and Native Hawaiian Small Business

Concerns

SEP 2004

252.232-7003 Electronic Submission of Payment Requests and Receiving

Reports

JUN 2012

252.232-7010 Levies on Contract Payments DEC 2006

252.242-7004 Material Management And Accounting System MAY 2011

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

52.243-1 CHANGES--FIXED-PRICE (AUG 1987)

(a) The Contracting Officer may at any time, by written order, and without notice to the sureties, if any, make changes within the general scope of this contract in any one or more of the following:

(1) Drawings, designs, or specifications when the supplies to be furnished are to be specially manufactured for the Government in accordance with the drawings, designs, or specifications.

(2) Method of shipment or packing.

(3) Place of delivery.

(b) If any such change causes an increase or decrease in the cost of, or the time required for, performance of any part of the work under this contract, whether or not changed by the order, the Contracting Officer shall make an equitable adjustment in the contract price, the delivery schedule, or both, and shall modify the contract.

(c) The Contractor must assert its right to an adjustment under this clause within 30 days from the date of receipt of the written order. However, if the Contracting Officer decides that the facts justify it, the Contracting Officer may receive and act upon a proposal submitted before final payment of the contract.

(d) If the Contractor's proposal includes the cost of property made obsolete or excess by the change, the

Contracting Officer shall have the right to prescribe the manner of the disposition of the property.

(e) Failure to agree to any adjustment shall be a dispute under the Disputes clause. However, nothing in this clause shall excuse the Contractor from proceeding with the contract as changed.

52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)

This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text of a clause may be accessed electronically at this/these address(es): https://www.acquisition.gov/far/ or http://farsite.hill.af.mil.

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…