N6134019R0020_N6134019R0020_0002.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to accomplish the follow ing:

1)Incorporate Q&A Rev. 2 and make all changes noted w ithin the Q&A document;

2)Correct POCs to reflect new personnel taking over this requirement;

3)Remove section 1.5.2 in Section L, Part B;

4)Correct the numbering of the technical factors in Section M, Part B, 1.0;

5)\Address changes to Sub-factor 2: Small Business Utilization, in Section L and Section M.

6) Updated PPIF form (see Q&A 76).

7) Update Base IDIQ SOW 18005A;Update DO 001 SOW 19005A, PRF 190026A, and PRF 190027A.

8) Update all CDRLs to reflect new SOW number; Update CDRLs A00B and A00c to reflect Q&A response.

9) Extend proposal due date from 03 June 2019 to 17 June 2019.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 30

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

16C. DATE SIGNED

BY 17-May-2019

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N6134019R0020

X 9B. DATED (SEE ITEM 11)

19-Apr-2019

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer X is extended, is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

17-May-2019

CODE

NAWCTSD 253

CODE 2.5.3.6.1

12211 SCIENCE DRIVE

ORLANDO FL 32826-3224

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N6134019R0020

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 03-Jun-2019 04:00 PM to 17-Jun-2019 04:00 PM.

SECTION G - CONTRACT ADMINISTRATION DATA

The following have been modified:

252.232-7006 WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (DEC 2018)

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

“Payment request” and “receiving report” are defined in the clause at 252.232-7003, Electronic Submission of

Payment Requests and Receiving Reports.

(b) Electronic invoicing. The WAWF system provides the method to electronically process vendor payment requests and receiving reports, as authorized by Defense Federal Acquisition Regulation Supplement (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.sam.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 shall use the following information when submitting payment requests and receiving reports in WAWF for this contract or task or delivery order:

(1) Document type. The Contractor shall submit payment requests using the following document type(s):

https://www.sam.gov/ https://wawf.eb.mil/ https://wawf.eb.mil/

(i) For cost-type line items, including labor-hour or time-and-materials, submit a cost voucher.

(ii) For fixed price line items—

(A) That require shipment of a deliverable, submit the invoice and receiving report specified by the Contracting

Officer.

Combo

(Contracting Officer: Insert applicable invoice and receiving report document type(s) for fixed price line items that require shipment of a deliverable.)

(B) For services that do not require shipment of a deliverable, submit either the Invoice 2in1, which meets the requirements for the invoice and receiving report, or the applicable invoice and receiving report, as specified by the

Contracting Officer.

Invoice 2 in 1

(Contracting Officer: Insert either “Invoice 2in1” or the applicable invoice and receiving report document type(s) for fixed price line items for services.)

(iii) For customary progress payments based on costs incurred, submit a progress payment request.

(iv) For performance based payments, submit a performance based payment request.

(v) For commercial item financing, submit a commercial item financing request.

(2) Fast Pay requests are only permitted when Federal Acquisition Regulation (FAR) 52.213-1 is included in the contract.

[Note: The Contractor may use a WAWF “combo” document type to create some combinations of invoice and receiving report in one step.]

(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 To be completed at award

Issue By DoDAAC N61340

Admin DoDAAC** N61340

Inspect By DoDAAC To be completed at award

Ship To Code To be completed at award

Ship From Code To be completed at award

Mark For Code To be completed at award

Service Approver (DoDAAC) To be completed at award

Service Acceptor (DoDAAC) To be completed at award

Accept at Other DoDAAC To be completed at award

LPO DoDAAC To be completed at award

DCAA Auditor DoDAAC To be completed at award

Other DoDAAC(s) To be completed at award

(*Contracting Officer: Insert applicable DoDAAC information. If multiple ship to/acceptance locations apply, insert

“See Schedule” or “Not applicable.”)

(**Contracting Officer: If the contract provides for progress payments or performance-based payments, insert the

DoDAAC for the contract administration office assigned the functions under FAR 42.302(a)(13).)

(4) Payment request. The Contractor shall ensure a payment request includes documentation appropriate to the type of payment request in accordance with the payment clause, contract financing clause, or Federal Acquisition

Regulation 52.216-7, Allowable Cost and Payment, as applicable.

(5) Receiving report. The Contractor shall ensure a receiving report meets the requirements of DFARS Appendix F.

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

____N61340_____________________________________________________________

(Contracting Officer: Insert applicable information or “Not applicable.”)

(2) Contact the WAWF helpdesk at 866-618-5988, if assistance is needed.

(End of clause)

SECTION I - CONTRACT CLAUSES

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

See Schedule________________________________________________________________

(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

See Schedule__________________________________________________________________

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

The following have been deleted:

52.211-11 Liquidated Damages--Supplies, Services, or Research and

Development

SEP 2000

52.217-9 Option To Extend The Term Of The Contract MAR 2000

252.204-7005 Oral Attestation of Security Responsibilities NOV 2001

252.227-7022 Government Rights (Unlimited) MAR 1979

252.246-7000 Material Inspection And Receiving Report MAR 2008

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

Basic ID/IQ Contract Attachments

Attachment 1. Basic ID/IQ Statement of Work 180005A dated 10 May 2019

Attachment 2. Reserved

Attachment 3. Authorization to Operate Package Rev5 (Omnibus)

Attachment 4. Authorization to Operate Package Rev5 (L-L-L)

Attachment 5. List of Government Furnished Information 1 March 2019

Attachment 6. Reserved

Attachment 7. TDPCR 18-17 Dated 24 Oct 2018

Attachment 8. TMCR 18-20 Dated 24 Oct 2018

Attachment 9. TMCR 18-2 Dated 24 Oct 2018

Attachment 10. Program Security Classification Form DD-254

Solicitation Attachments (These are needed for solicitation purposes only and will not be incorporated into the final contract)

Attachment L1. Delivery Order 0001 (updated with Amendment 0002)

Attachment L2. Contractor Performance Assessment Questionnaire (CPAQ)

Attachment L3. STIGS Past Performance Information Form Rev1 (PPIF)

Attachment L4. STIGS RFP Question/Comment Form

Attachment L5. STIGS Export Controlled GF) Request and Non-Disclosure Agreement (NDA) Form

Attachment L6a. Small Business Participation Document (SBPD) – Contract Level

Attachment L6b. Small Business Participation Document (SBPD) – Delivery Order 0001

Attachment L7. STIGS Q&A (updated with Amendment 0001)

Attachment L8. STIGS Q&A (updated with Amendment 0002)

Basic ID/IQ CDRL Exhibits

TITLE DATE

EXHIBIT A

A001 Software Development Plan (SDP) 10 May 2019

A002 Operations Security (OPSEC) Plan 10 May 2019

A003 Test Plan, Trainer Test and Evaluation Plan (TTEP) 10 May 2019

A004 Engineering Change Proposal (ECP) 10 May 2019

A005 Request for Variance (RFV) 10 May 2019

A006 Requirements Traceability Verification Matrix (RTVM) 10 May 2019

A007 Scientific and Technical Report, Training System Analysis Report (TSAR) 10 May 2019

A008 A008 Safety Assessment Report (SAR) 10 May 2019

A009 System/Subsystem Design Description (SSDD) 10 May 2019

A00A Software Product Design (SPD) 10 May 2019

A00B DoD Risk Management Framework (RMF) Package Deliverables 10 May 2019

A00C DoD Risk Management Framework (RMF) Package Deliverables, Omnibus 10 May 2019

A00D Software Product Package (SPP) 10 May 2019

A00E Test Procedure (TP) 10 May 2019

A00F Test/Inspection Report (TIR) 10 May 2019

A00G Configuration Audit Summary Report and Certification 10 May 2019

EXHIBIT B

B001 Contractor’s Progress, Status, And Management Report (CPSMR) 10 May 2019

B002 Integrated Program Management Report (IPMR), Integrated Master Schedule (IMS) 10 May 2019

B003 Conference Agenda 10 May 2019

B004 Conference Minutes 10 May 2019

B005 Presentation Materials 10 May 2019

EXHIBIT C

C001 Source Data for Forecasting Diminishing Manufacturing Sources and Material

Shortages, DMSMS Report

10 May 2019

C002 Logistics Product Data, Initial Support Kit List (ISKL) 10 May 2019

EXHIBIT D

D001 Equipment Inventory Records (EIR) 10 May 2019

D002 Technical Directive, Training Equipment Change Directive (TECD) 10 May 2019

D003 Warranty Performance Report 10 May 2019

D004 Trainer Facilities Report (TFR) 10 May 2019

EXHIBIT E

E001 Operation and Maintenance (O&M) Manual 10 May 2019

E002 Maintenance Requirements Card Decks (MRCD) 10 May 2019

E003 Instructor/Operator Handbook (I/OH) 10 May 2019

E004 Commercial Off The Shelf (COTS) Documentation 10 May 2019

E005 Technical Manual Content and Product Plan 10 May 2019

E006 Technical Data Package (TDP), Product Drawings/Models and Associated Lists

(PDAL)

10 May 2019

E00A Operation and Maintenance, Operation and Maintenance (O&M) Manual/Systems

Interface Manual (SIM)

10 May 2019

E00B Preventative Maintenance System (PMS), Maintenance Requirements Cards

(MRCs)

E00C Instructor’s Manual, Instructor Utilization Handbook (IUH)/Training System

Support Document (TSSD)

10 May 2019

E00D Instructor’s Manual, Instructor Utilization Handbook (IUH)/Training System

Support Document (TSSD)

EXHIBIT F

F001 Instructional Performance Requirements Document, Job Task Analysis

(JTA)/Training Systems Requirements Analysis (TSRA)

10 May 2019

F002 Instructional Performance Requirements Document, Learning Objectives Analysis 10 May 2019

F003 Scientific and Technical Report, Training Device Decision Coordinating Paper

(TDDCP)

10 May 2019

F004 Scientific and Technical Report, Military Characteristics Document 10 May 2019

F005 Scientific and Technical Report, Course Design Strategy (CDS) 10 May 2019

F006 Instructional Media Design Package, Prototype Lesson 10 May 2019

F007 Scientific and Technical Report, Lesson Design Strategy 10 May 2019

F008 Instructional Media Design Package, Courseware Logic Flow Diagrams (LFD) 10 May 2019

F009 Instructional Media Package, Scripts/Storyboards 10 May 2019

F00A Test Package 10 May 2019

F00B Scientific and Technical Report, Training Project Plan (TPP) 10 May 2019

F00C Scientific and Technical Report, Course Training Task List (CTTL) 10 May 2019

F00D Scientific and Technical Report, Training Course Control Document (TCCD) 10 May 2019

F00E Training Conduct Support Document, Lesson Plan 10 May 2019

F00F Training Conduct Support Document, Trainee Guide 10 May 2019

F00G Training Conduct Support Document, Instructional Visual Aids 10 May 2019

F00H Instructional Media Package, Instructional Media Source 10 May 2019

F00J Scientific and Technical Report, Exercise Controller Guides (ECG) 10 May 2019

F00K Training Conduct Support Document, Instructor/Operator Training Course 10 May 2019

F00L Training Conduct Support Document, Maintainer Training Course 10 May 2019

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been added by full text:

5252.215-9503 ANTICIPATED AWARD DATE (NAVAIR)(FEB 1995)

The anticipated award date for this requirement is 20 September 2019. This information is provided for use as a basis for schedules and burden (labor, overheads, G&A, etc.) mid-point calculations.

INSTRUCTIONS

Section L - Instructions, Conditions and Notices to Bidders

PART A GENERAL INSTRUCTIONS

1.0 GENERAL

The Offeror must respond to all requirements of the solicitation and not alter or rearrange the solicitation. The

Offeror is advised that the Government may incorporate any portions of the Offeror’s proposal into the resulting contract.

In presenting material in the proposal, the Offeror is advised that quality of information is more important than quantity. Clarity, brevity, and logical organization shall be emphasized during proposal preparation. Statements that the prospective Offeror understands, can comply with, or will comply with, the specifications, and paraphrasing the requirements or parts thereof without supporting information are considered inadequate by the Government, and may result in assessing weaknesses and/or deficiencies.

The Offeror must include any data that illustrates the adequacy of the various assumptions, approaches, and solutions to problems. Failure to address a specific factor or subfactor clearly may be considered a deficiency.

Unnecessarily elaborate brochures or other presentation materials beyond that sufficient to present a complete and effective proposal is neither necessary nor desired.

The Government advises the Offeror that taking exception or deviating from any term or condition of the RFP may result in the assessment of a deficiency to the proposal.

Throughout these instructions, a “principal subcontractor” is defined as a subcontractor who provides at least

20% of the proposed total price. A “JV Team member” is defined as one of the entities that make up a joint venture

(JV) proposed as the prime contractor for this solicitation.

2.0 PROPOSAL FORMAT

Written proposals must be formatted using a Times New Roman 12 pt Normal font (no reduction permitted), single-spaced with 1-inch margins all around, and formatted for standard 8.5 x 11 inch paper. All pages should be numbered with section and page numbers. When foldout pages are used they must not exceed 11 x 17 inches and will be counted as 1 page. Drawings may be provided separately and may be any size but should be folded to approximately 8.5 x 11 inch standard size and will count as 1 page. Graphs and tables shall be presented in no smaller than a 10 pt font and should contain a grid, which allows values to be read directly from the graph. Graphic resolution, including such data as tables or charts, should be consistent with the purpose of the data presented.

The Offeror will provide one complete copy of the proposal to the Procuring Contracting Officer (PCO) as electronic files fully compatible with Microsoft Office 2010 and for information not supported by MS Office products, with the latest Adobe Acrobat reader on a CD-ROM. The Offeror will ensure that the Price/Cost Volume is provided on a separate CD-ROM. Each CD-ROM is to be labeled for content and the Offeror’s name. If a discrepancy exists between the original paper copy of the proposal and the disk copy, the paper copy will take precedence, with the exception of Volume 2, Past Performance. Due to restrictions on the number of characters Attachment L3 will print, the CD-ROM associated with Volume 2 will take precedence. Data stored on the media shall be unlocked.

3.0 PROPOSAL CONTENT AND VOLUMES

The Offeror must present proposal information in a manner that facilitates a one-to-one comparison between the information presented and this Proposal Instruction. Proposal information must be structured such that its

Volume/paragraph number matches the Proposal Instructions Volume/paragraph number provided in section “Part B

Specific Instructions” to which it is responding, although the Offeror may add lower tier subparagraphs. The

Offeror must provide reasons it will not provide information for a particular paragraph. The proposal information instructions are structured by paragraph numbers where first, second, third, and fourth parts correspond to the volume, section, and element, etc., in the Offeror’s proposal.

Each volume of the proposal shall be submitted as one original and additional copies as specified in the table below.

The table below supersedes the copies requested in Block 9 of the Standard Form (SF) 33. All volumes of the original proposal shall be delivered to the address provided in Section 4.0 prior to the closing date/time stated in this solicitation. Page limitations for each volume, if any, are also specified in the table below; title and table of contents pages do not count towards the page limit. Any pages submitted exceeding the page limit shall be disregarded and

NOT evaluated.

Information submitted as an Annex to the proposal includes manuals, specifications, plans, procedures, and policies that exist as an official document of the company or facility, as well as other information requested in Part B

Specific Instructions. Page limitations for Annexes, if any, are specified below.

Volume Number Volume Title Page Limit Copies Required

1.0 TECHNICAL 60 pages Paper Copies: 1

Original/2Copies

Electronic Copy: 1 Original

1.1 Common Baseline &

Initial Delivery Order

Design and Courseware

Included in 60 pg limit for Technical Volume

Paper Copies: 1

Original/2Copies

1.2 Small Business

Utilization***

As Needed

*Exempt from page count

Paper Copies: 1 Original 1 Copy

2 PAST PERFORMANCE As Needed Paper Copies: 1 Original 1

Copy

3 PRICE/Small Business As Needed Paper Copies: 1 Original 1

Copy

*Page limitation does not include front matter such as title page, table of contents, list of figures, etc., glossary (if used), personnel allocation matrix etc. When foldout pages are used, they must not exceed 11 x 17 inches and will be counted as 1 page. Drawings may be provided separately and may be any size, with font of any size, but should be folded to approximately 8.5 x 11 inch standard size and will count as 1 page. Graphs shall be presented in no smaller than a 10 point font. Drawings are included within the page count.

** Technical, Past Performance and Price volumes shall be submitted in separate binders.

***Offerors are to submit all information within Sub-factor 1.2, which is part of Volume 1 Technical, as part of

Volume 3 Price (in the same folder/binder, separated with a tab) and as a separate file in the CD Volume 3 copy.

All Offerors, please provide the Small Business Participation Documents (SBPDs) as a part of the Volume 3 Price

(in the same folder/binder, separated with a tab) and as a separate file in the CD Volume 3 copy. Large Business

Offerors should also submit their Subcontracting Plan IAW FAR 52.219-9 and DFARS 252.219-7003 (Dev 2018-

O0007) as a part of the Volume 3 Price (in the same folder/binder, separated with a tab). This is due to Small

Business UtlizationUtilization information containing elements of price information,.

Each volume shall contain the following information:

-Cover and title page

-Title of proposal and proposal number as applicable

-Offeror’s name, address, and POC

-RFP number

-Proposal volume number

-Copy number

-Table of Contents (The table of contents must provide sufficient detail to enable easy location of important elements)

-Use tabs and dividers

The Offeror shall submit a Cross Reference Matrix (CRM) for the Technical Volume, similar to the example below, to help ensure that all solicitation requirements are addressed and to facilitate the evaluators’ review of the

Offeror’s proposal. The CRM should be a single integrated matrix and cross-reference the proposal volumes and paragraphs to specific RFP requirements, as well as other parts of the proposal that contain relevant information.

The Offeror’s CRM may be identical to the example below or revised such as to add columns to indicate the page number on which information may be found, identify where other relevant information in the proposal is located, or provide other comments. The CRM does not count against any of the proposal page limitations.

EXAMPLE OF A CROSS REFERENCE MATRIX (CRM)

4.0 PROPOSAL SUBMISSION

Clearly mark all packages with the solicitation number. The submission date for all Volumes shall be no later than the date and time specified in Block 9 of the SF 33 of the RFP. It is requested that Volume 2 Past Performance information be submitted not later than 28 days (17 May 2019) after the final RFP release date.

Offeror shall submit proposals via United States Postal Service or through a commercial carrier using the address provided below. Offeror shall not submit proposals by facsimile or electronically via email.

Naval Air Warfare Center Training Systems Division (NAWCTSD)

Code: AIR-2.5.3.6

Lisa Mardin

12211 Science Dr.

Orlando, FL 32828

Solicitation Number: N61340-19-R-0020

Hand carried proposals may be delivered to the address above, attention (PCO) and/or (Specialist: Lisa Mardin).

Hand carried proposals may be delivered to the address above, attention Lisa Mardin. If an offeror chooses to hand carry a proposal, arrangements shall be made at least three (3) Government workdays in advance with Ms. Lisa

Mardin. Ms. Mardin may be contacted by phone at (407) 380-4842 or by email at Lisa.Mardin@navy.mil. The alternate point of contact is Mr. Sidney Galloway who may be reached at (407) 380-8331 or by email at sidney.galloway@navy.mil. Visitor request approval must be obtained prior to facility access.

Please note that center security personnel or other personnel (other than the PCO or CS) are not authorized to accept proposals. The CS will provide the offeror with documentation reflecting the date and time the proposal submission was received for the offeror’s records.

Late Proposals: See FAR provision 52.215-1.

Section L –

Proposal

Instructions

Government

SOW/PWS

Section M –

Evaluation

Factor Offeror’s Proposal Reference

CLIN

Reference

Volume 1

Technical

Example: Para 3.1

Note: This column shall address all paragraphs in

Sections xx and xy of the

SOW/PWS.

2.A Provide reference to Offeror’s

Proposal Volume I –

Technical. Example: Refer to appropriate page number in

Offeror’s written proposal

5.0 PROPOSAL PACKAGING:

The Offeror shall package the proposal volumes in cartons or equivalent packaging containers in the most efficient manner possible grouping like volumes to the maximum extent possible. Each container shall be single person portable. One container shall include all Original Proposal volumes including the original/signed documents submitted as part of Volume 3 Cost/Price.

Each box should include a packing slip detailing the contents to include the volume number, title, and copy number. Also, each box should be stamped or marked “For Official Use Only” and “Source Selection Information –

See FAR 2.101 and 3.104.”

5.1 Restriction on Disclosure and Use of Data: Offerors that include in their proposals data that they do not want disclosed to the public for any purpose, or used by the government except for evaluation purposes, shall—

(a) Mark the title page with the following legend:

“This proposal includes data that shall not be disclosed outside the government and shall not be duplicated, used, or disclosed—in whole or in part—for any purpose other than to evaluate this proposal. If, however, a task or delivery order is awarded to this offeror as a result of — or in connection with — the submission of this data, the government shall have the right to duplicate, use, or disclose the data to the extent provided in the resulting task or delivery order. This restriction does not limit the government's right to use information contained in this data if it is obtained from another source without restriction. The data subject to this restriction are contained in sheets [insert numbers or other identification of sheets]”; and

(b) Mark each sheet of data it wishes to restrict with the following legend:

“Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposal.”

6.0 CLASSIFIED DATA

All proposals shall be UNCLASSIFIED.

7.0 SOLICITATION CHANGES

For notice of any changes and additional information provided by the Government for the solicitation, please go to www.FedBizOpps.gov.

8.0 ACCESS TO GOVERNMENT FURNISHED INFORMATION (GFI):

GFI listed in the STIGS IDIQ SOW will be made available via CD/DVD or via https://safe.amrdec.army.mil to offerors. Offerors shall make their request for GFI no later than 5 working days after FINAL RFP release. Offerors shall contact Lisa Mardin, Lisa.Mardin@navy.mil to coordinate receipt of the media. It is the offerors’ responsibility to ensure they obtain all offered materials in time to complete their proposal before the submission deadline.

Instructions and requirements to obtain materials are located in Attachment L-5, STIGS Export Controlled

Government Furnished Information (GFI) Request and Non-Disclosure Agreement (NDA) Form. All personnel provided access to GFI shall be U.S. citizens.

9.0 SOLICITATION QUESTIONS

9.1 Questions regarding this solicitation shall be submitted in writing using the STIGS RFP Question and

Answer Form (Attachment L-4). The Government may answer questions prior to the deadline for proposal submission provided that those questions are received no later than 15 calendar days following the Final RFP release date.

http://www.fedbizopps.gov/

Any questions regarding this solicitation shall be submitted in writing by electronic mail to the following addresses:

Ms. Lisa Mardin, Contract Specialist, Lisa.mardin@navy.mil and

Mr. Sidney Galloway, PCO, Sidney.galloway@navy.mil

Each question shall reference the applicable document, paragraph, and page number. Questions, if answered, will be provided to all potential offerors via amendment to the solicitation; therefore, do not include proprietary information in your questions.

9.2 The Government reserves the right not to respond to any questions concerning this solicitation received after the time frame specified above. Accordingly, offerors are encouraged to carefully review all solicitation requirements and submit questions to the Government early in the proposal preparation cycle.

PART B SPECIFIC INSTRUCTIONS

Cost or pricing information shall only appear in the Price/Cost volume.

1.0 VOLUME 1: TECHNICAL

Subfactor 1: Common Baseline & Initial Delivery Order Design and Courseware

1.1 Common Baseline & Initial Delivery Order Design Approach

Common Baseline & Initial Delivery Order Design Approach, specifically address the following:

1.1.1 The offeror shall describe its overarching approach for the design, development, and establishment of a common baseline for the trainers, simulation products, and courseware delivered under the STIGS ID/IQC. The offeror shall identify each hardware and software configuration item and include a narrative describing the proposed design for the FADC LOCOP trainer and LCS-5 EPT courseware. The offeror’s overarching approach shall discuss how the FADC LOCOP trainer and LCS-5 EPT courseware are incorporated into the common baseline. Graphics such as block diagrams, conceptual training system arrangements, and interface diagrams may be used at the contractor’s discretion to supplement the overarching approach.

1.1.2 The offeror shall identify and discuss what the offeror believes to be the most critical design risks with its approach under section 1.1.1. For each risk identified, the offeror shall discuss its mitigation strategy.

1.2 Software Design and Development

Software Design and Development, specifically address the following:

1.2.1 The offeror shall describe its software engineering environment including the software toolset necessary to accomplish the complete software effort. The software toolset shall address requirement tool(s), design tool(s), verification tool(s), and software configuration management tool(s). The offeror shall provide rationale for the selection of the software engineering toolset and describe how it will be used to support the requirements analysis, design, configuration management, and verification processes.

1.2.2 The offeror shall describe its software reuse approach and provide a detailed description of the steps taken to reduce development of duplicative software. The offeror shall identify whether the reuse items will be “as-is” or

“modified” and the extent of modification. The offeror shall identify existing software and portions thereof that are

Open Source.

1.3 LCS-5 EPT Courseware Technical Performance Parameters

LCS-5 EPT Courseware Technical Performance Parameters, specifically address the following:

1.3.1 The offeror shall describe how its design from section 1.1.1 above for the LCS-5 EPT courseware addresses the technical performance parameters from section 3.1.5 of PRF 190026.

1.4 Computer Software Rights

Computer Software Rights, specifically address the following:

1.4.1 The offeror shall describe its proposed approach to rights in Computer Software (CS) and Technical Data, including Computer Software Documentation (CSD), for all elements including object code and source code of its

Common Baseline Solution. This description shall be consistent with the offeror’s assertions to DFARS 252.227-

7017. The offeror shall discuss how this approach supports future currency, deployment, and sustainment of the

Common Baseline. This discussion shall also explain how the approach affects the ability of third parties to maintain and modify the Common Baseline to include rationale for the use of proprietary or vendor unique

Computer Software or Technical Data. Specifically negotiated licenses associated with the Common Baseline solution shall be provided.

1.5 Trainer Component Selection and Management

Trainer Component Selection and Management, specifically address the following:

1.5.1 For each of the identified hardware and software configuration items from section 1.1.1, the offeror shall identify the items that are Commercial Items, Commercial-Off-The-Shelf (COTS) items, and Non-Developmental

Items (NDI), as defined in FAR 2.101, and provide rationale for using configuration items other than Commercial

Items, COTS, and NDI. The offeror shall provide rationale for the selection of each of the configuration items along with their forecasted end of support date.

1.6 Courseware Factors Approach

Courseware Factors Approach, specifically address the following:

1.6.1 The offeror shall describe its method for selecting instructional strategies that will be used to teach knowledge learning objectives within game-based courseware as well as the rationale for selecting specific instructional strategies.

1.6.2 The offeror shall describe its storyboarding toolset necessary to develop Scripts/Storyboards (SSBs), including design elements to describe and depict knowledge and performance content, student and instructor actions and interactions, and system actions and responses for game-based courseware with varying simulation complexity. The offeror shall provide rationale for the selection of the storyboarding toolset. The offeror shall describe how it will be used to support Government review of SSBs by multiple reviewers at multiple locations. The offer shall describe how each comment will be clearly linked to the specific lesson element being addressed in the comment as well as how those comments are ultimately tracked and adjudicated. The offeror shall describe how the output of the SSB toolset will be transitioned into On-Screen Lessons (OSLs).

1.6.3 The offeror shall describe its approach to execute and manage OSL incremental inspections and acceptance testing to support timely delivery. The offeror shall identify and discuss what the offeror believes to be the critical risks associated with OSL incremental inspections. For each risk identified, the offeror shall discuss its mitigation strategy.

Sub-factor 2: Small Business Utilization

2.1 The Large Business Offeror shall provide its Subcontracting Plan conforming to the requirements of FAR 19.7 and DFARS 219.7.