SOFAST-E_Solicitation_SF33.doc

Section B - Supplies or Services and Prices

SOFAST-E

FFP

This CLIN is established for the Special Operations Forces Aviation Systems Trainers - Enhancements (SOFAST-E). This is an Indefinite Delivery, Indefinite Quantity contract (ID/IQC). All work to be performed under this contract shall be in accordance with the individual Delivery Order Statement of Work (SOW) and the base award SOW attached in Section J. The ordering period for this ID/IQC will be 60 months from contract award.

FOB: Destination

NET AMT

CMRA

Contractor Manpower Reporting Application, in accordance with H clause 5152.204-5002

NET AMT

UNDEFINED

Reserved

MAX

NET AMT

UNDEFINED

Reserved

MAX

UNDEFINED

Reserved

MAX

UNDEFINED

Reserved

MAX

Reserved

NET AMT

UNDEFINED

Reserved

MAX

Reserved

NET AMT

UNDEFINED

Reserved

MAX

UNDEFINED

Reserved

MAX

UNDEFINED

Reserved

MAX

UNDEFINED

Reserved

MAX

UNDEFINED

Reserved

MAX

UNDEFINED

Reserved

MAX

UNDEFINED

Reserved

MAX

UNDEFINED

Reserved

MAX

UNDEFINED

Reserved

MAX

UNDEFINED

Reserved

MAX

UNDEFINED

Reserved

MAX

CLIN DATA

THIS SOLICITATION IS FOR A SINGLE AWARD INDEFINITE DELIVERY/INDEFINITE QUANTITY (ID/IQ) CONTRACT

B.1 Contract Line Item Numbers 0003 through 0020 marked as Firm Fixed Price (FFP) may be utilized as FFP, Cost-Plus-Fixed-Fee (CPFF), Cost, and Time and Material (T&M) CLINs for Delivery/Task Orders issued under the resulting contract in accordance with Section H.1.

B.2 CLINs 0003 through 0020 marked as FFP in Section B are established for the sole purpose of facilitating administration of the contract in the Government’s contract writing system.

B.3 Based upon historical Special Operations Aviation efforts and forecasted requirements, it has been estimated that the preponderance of work to be handled under the SOFAST-E ID/IQ contract vehicle will be FFP.

B.4 The Not-to-Exceed (NTE) Ceiling Amount for this contract is $85,000,000.00.

B.5 The cumulative total for all delivery orders awarded as a result of solicitation number W900KK-13-R-0002 shall not exceed $85,000,000.00 over the life of the contract.

B.6 This Request for Proposal is a 100% small business set-aside.

CONTRACT MINIMUM/MAXIMUM QUANTITY AND CONTRACT VALUE

The minimum quantity and contract value for all orders issued against this contract shall not be less than the minimum quantity and contract value stated in the following table. The maximum quantity and contract value for all orders issued against this contract shall not exceed the maximum quantity and contract value stated in the following table.

MINIMUM

QUANTITY

MINIMUM

AMOUNT

MAXIMUM

QUANTITY

MAXIMUM

AMOUNT

$10,000.00

$85,000,000.00

CLIN DELIVERY/TASK ORDER MINIMUM/MAXIMUM QUANTITY AND CLIN ORDER VALUE

The minimum quantity and order value for the given Delivery/Task Order issued for this CLIN shall not be less than the minimum quantity and order value stated in the following table. The maximum quantity and order value for the given Delivery/Task Order issued for this CLIN shall not exceed the maximum quantity and order value stated in the following table.

QUANTITY

MINIMUM

AMOUNT

MAXIMUM

QUANTITY

MAXIMUM

AMOUNT

Section D - Packaging and Marking

CLAUSES INCORPORATED BY FULL TEXT

5152.247-5001

MARKING OF WARRANTED ITEMS (PEO-STRI) (SEP 2006)

(a) Each item covered by a warranty shall be stamped or marked in accordance with MIL-STD-129, Marking for Shipment and Storage, and MIL-STD-130, Identification Marking of U.S. Military Property, current at the date of award. Where this is impracticable, written notice shall be attached to or furnished with the warranted item.

(b) Each item covered by a warranty shall have a written notice attached to or furnished with the warranted item, and marked with the following:

(1) National stock number or manufacturer’s part number.

(2) Serial number or other item identifier (if the warranty applies to uniquely identified items).

(3) Contract number.

(4) Indication that a warranty applies.

(5) Manufacturer or entity (if other than the contractor) providing the warranty.

(6) Date or time when the warranty expires.

(7) Indication of whether or not attempted on-site repair by Government personnel will void the warranty.

(End of Clause)

Section E - Inspection and Acceptance

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

CLAUSES INCORPORATED BY REFERENCE

5152.246-5012

INSPECTION AND ACCEPTANCE (PEO STRI) (APR 2012)

(a) Inspection and acceptance of the supplies or services to be furnished hereunder shall be performed by the Procuring Contracting Officer (PCO) or his duly authorized representative, PCO

LOVISA D. PARKS

407-208-3476

Lovisa.parks@us,army.mil

COR

CARLOS HOMS

407-384-3986 Carlos.Homs@us.army.mil

(b) Acceptance of all Contract Line Item Numbers/Sub Line Item Numbers (CLIN/SLIN) shall be made by the accepting authority through Wide Area Work Flow (WAWF) Acceptance will only occur when the accepting authority is sure that inspections performed demonstrate compliance with contract requirements.

(End of Clause)

Section F - Deliveries or Performance

DELIVERY INFORMATION

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

CLAUSES INCORPORATED BY REFERENCE

252.211-7003 ITEM IDENTIFICATION AND VALUATION (JUN 2011)

(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 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 unique item 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 non-repeatable identifier to an enterprise (i.e., Dun & Bradstreet's Data Universal Numbering System (DUNS) Number, GS1 Company Prefix, or Defense Logistics Information System (DLIS) Commercial and Government Entity (CAGE) Code).

Issuing agency means an organization responsible for assigning a globally unique identifier to an enterprise (e.g., Dun & Bradstreet's Data Universal Numbering System (DUNS) Number, GS1 Company Prefix, Allied Committee 135 NATO Commercial and Government Entity (NCAGE)/Commercial and Government Entity (CAGE) Code, or the Coded Representation of the North American Telecommunications Industry Manufacturers, Suppliers, and Related Service Companies (ATIS-0322000) Number), European Health Industry Business Communication Council (EHIBCC) and Health Industry Business Communication Council (HIBCC)), as indicated in the Register of Issuing Agency Codes for ISO/IEC 15459, located at http://www.nen.nl/web/Normen-ontwikkelen/ISOIEC-15459-Issuing-Agency-Codes.htm.

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.

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) All delivered items for which the Government's unit acquisition cost is $5,000 or more.

(ii) The following items for which the Government's unit acquisition cost is less than $5,000:

Contract line, subline, or exhibit line item No. Item description

To be Defined at the Individual Delivery Order Level

(iii) Subassemblies, components, and parts embedded within delivered items as specified in Attachment Number ----.

(2) The unique item identifier and the component data elements of the DoD unique item identification shall not change over the life of the item.

(3) Data syntax and semantics of unique item identifiers. The Contractor shall ensure that--

(i) The encoded data elements (except issuing agency code) of the unique item identifier are 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.

(4) 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; 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 the version of MIL-STD-130, Identification Marking of U.S. Military Property, cited in the contract Schedule.

(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 unique item identification under paragraph (c)(1)(i) or (ii) of this clause, 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, or associated with, 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.

(e) For embedded subassemblies, components, and parts that require DoD unique item identification under paragraph (c)(1)(iii) of this clause, the Contractor shall report as part of, or associated with, 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 in accordance with the data submission procedures at http://www.acq.osd.mil/dpap/pdi/uid/data_ submission_information.html.

(g) Subcontracts. If the Contractor acquires by subcontract, any item(s) for which unique item 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).

(End of clause)

252.211-7006 PASSIVE RADIO FREQUENCY IDENTIFICATION (SEP 2011)

(a) Definitions. As used in this clause--

Advance shipment notice means an electronic notification used to list the contents of a shipment of goods as well as additional information relating to the shipment, such as passive radio frequency identification (RFID) or item unique identification (IUID) information, order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment.

Bulk commodities means the following commodities, when shipped in rail tank cars, tanker trucks, trailers, other bulk wheeled conveyances, or pipelines:

(1) Sand.

(2) Gravel.

(3) Bulk liquids (water, chemicals, or petroleum products).

(4) Ready-mix concrete or similar construction materials.

(5) Coal or combustibles such as firewood.

(6) Agricultural products such as seeds, grains, or animal feed.

Case means either a MIL-STD-129 defined exterior container within a palletized unit load or a MIL-STD-129 defined individual shipping container.

Electronic Product Code\TM\ (EPC[supreg]) means an identification scheme for universally identifying physical objects via RFID tags and other means. The standardized EPC\TM\ data consists of an EPC\TM\ (or EPC\TM\ identifier) that uniquely identifies an individual object, as well as an optional filter value when judged to be necessary to enable effective and efficient reading of the EPC\TM\ tags. In addition to this standardized data, certain classes of EPC\TM\ tags will allow user-defined data. The EPC\TM\ Tag Data Standards will define the length and position of this data, without defining its content.

EPCglobal[supreg] means a subscriber-driven organization comprised of industry leaders and organizations focused on creating global standards for the adoption of passive RFID technology.

Exterior container means a MIL-STD-129 defined container, bundle, or assembly that is sufficient by reason of material, design, and construction to protect unit packs and intermediate containers and their contents during shipment and storage. It can be a unit pack or a container with a combination of unit packs or intermediate containers. An exterior container may or may not be used as a shipping container.

Palletized unit load means a MIL-STD-129 defined quantity of items, packed or unpacked, arranged on a pallet in a specified manner and secured, strapped, or fastened on the pallet so that the whole palletized load is handled as a single unit. A palletized or skidded load is not considered to be a shipping container. A loaded 463L System pallet is not considered to be a palletized unit load. Refer to the Defense Transportation Regulation, DoD 4500.9-R, Part

II, Chapter 203, for marking of 463L System pallets.

Passive RFID tag means a tag that reflects energy from the reader/interrogator or that receives and temporarily stores a small amount of energy from the reader/interrogator signal in order to generate the tag response. The only acceptable tags are EPC Class 1 passive RFID tags that meet the EPCglobal\TM\ Class 1 Generation 2 standard.

Radio frequency identification (RFID) means an automatic identification and data capture technology comprising one or more reader/interrogators and one or more radio frequency transponders in which data transfer is achieved by means of suitably modulated inductive or radiating electromagnetic carriers.

Shipping container means a MIL-STD-129 defined exterior container that meets carrier regulations and is of sufficient strength, by reason of material, design, and construction, to be shipped safely without further packing (e.g., wooden boxes or crates, fiber and metal drums, and corrugated and solid fiberboard boxes).

(b)(1) Except as provided in paragraph (b)(2) of this clause, the Contractor shall affix passive RFID tags, at the case- and palletized- unit-load packaging levels, for shipments of items that--

(i) Are in any of the following classes of supply, as defined in DoD 4140.1-R, DoD Supply Chain Materiel Management Regulation, AP1.1.11:

(A) Subclass of Class I--Packaged operational rations.

(B) Class II--Clothing, individual equipment, tentage, organizational tool kits, hand tools, and administrative and housekeeping supplies and equipment.

(C) Class IIIP--Packaged petroleum, lubricants, oils, preservatives, chemicals, and additives.

(D) Class IV--Construction and barrier materials.

(E) Class VI--Personal demand items (non-military sales items).

(F) Subclass of Class VIII--Medical materials (excluding pharmaceuticals, biologicals, and reagents--suppliers should limit the mixing of excluded and non-excluded materials).

(G) Class IX--Repair parts and components including kits, assemblies and subassemblies, reparable and consumable items required for maintenance support of all equipment, excluding medical-peculiar repair parts; and

(ii) Are being shipped to one of the locations listed at http://www.acq.osd.mil/log/rfid/ or to--

(A) A location outside the contiguous United States when the shipment has been assigned Transportation Priority 1, or to--

(B) The following location(s) deemed necessary by the requiring activity:

Contract line, subline, or exhibit Location name City State DoDAAC line item number

To be Defined at the Individual Delivery Order Level

(2) The following are excluded from the requirements of paragraph (b)(1) of this clause:

(i) Shipments of bulk commodities.

(ii) Shipments to locations other than Defense Distribution Depots when the contract includes the clause at FAR 52.213-1, Fast Payment Procedures.

(c) The Contractor shall--

(1) Ensure that the data encoded on each passive RFID tag are globally unique (i.e., the tag ID is never repeated across two or more RFID tags) and conforms to the requirements in paragraph (d) of this clause;

(2) Use passive tags that are readable; and

(3) Ensure that the passive tag is affixed at the appropriate location on the specific level of packaging, in accordance with MIL-STD-129 (Section 4.9.2) tag placement specifications.

(d) Data syntax and standards. The Contractor shall encode an approved RFID tag using the instructions provided in the EPC\TM\ Tag Data Standards in effect at the time of contract award. The EPC\TM\ Tag Data Standards are available at http://www.epcglobalinc.org/standards/.

(1) If the Contractor is an EPCglobal\TM\ subscriber and possesses a unique EPC\TM\ company prefix, the Contractor may use any of the identifiers and encoding instructions described in the most recent EPC\TM\ Tag Data Standards document to encode tags.

(2) If the Contractor chooses to employ the DoD identifier, the Contractor shall use its previously assigned Commercial and overnment Entity (CAGE) code and shall encode the tags in accordance with the tag identifier details located at http://www.acq.osd.mil/log/rfid/tag_data.htm. If the Contractor uses a third-party packaging house to encode its tags, the CAGE code of the third-party packaging house is acceptable.

(3) Regardless of the selected encoding scheme, the Contractor with which the Department holds the contract is responsible for ensuring that the tag ID encoded on each passive RFID tag is globally unique, per the requirements in paragraph (c)(1) of this clause.

(e) Advance shipment notice. The Contractor shall use Wide Area WorkFlow (WAWF), as required by DFARS 252.232-7003, Electronic Submission of Payment Requests, to electronically submit advance shipment notice(s) with the RFID tag ID(s) (specified in paragraph (d) of this clause) in advance of the shipment in accordance with the procedures at https://wawf.eb.mil/.

(End of clause)

CLAUSES INCORPORATED BY FULL TEXT

5152.216-5004

MINIMUM AND MAXIMUM QUANTITIES (PEO STRI) (SEP 2006)

As referred to in paragraph (b) of FAR 52.216-22 "Indefinite Quantity" of this contract, the contract minimum quantity is $10,000; the maximum quantity is $85,000,000.

Section G - Contract Administration Data

CLAUSES INCORPORATED BY REFERENCE

252.204-0003 LINE ITEM SPECIFIC: CONTRACTING OFFICER SPECIFIED ACRN ORDER. (SEP 2009)

The payment office shall make payment within the line item in the sequence ACRN order specified below, exhausting all funds in the previous ACRN before paying from the next ACRN.

Line Item

ACRN Order

If Required, to be Defined at the Individual Delivery Order Level

(End of clause)

252.232-7006 WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (JUN 2012)

(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 Central Contractor Registration 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:

Invoice as 2-in-1 (FP Services Only – No DD250 Required)

Invoice Only

Receiving Report (DD 250) Destination Inspection / Destination Acceptance

Inspect and Accept at place of destination

Invoice and Receiving Report (Combo) - Destination Inspection / Destination Acceptance

Receiving Report (DD 250) Source Inspection / Source Acceptance

Inspection and Acceptance takes place at contractor's plant

Invoice and Receiving Report (Combo) - Source Inspection / Source Acceptance

Receiving Report (DD 250) Source Inspection / Destination Acceptance

Inspection at contractor's plant with Acceptance at destination

Invoice and Receiving Report (Combo) - Source Inspection / Destination Acceptance

(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

HQ0338

Issue By DoDAAC

W900KK

Admin DoDAAC

TBD at Award Inspect By DoDAAC

W906ZL

Ship To Code

W906ZL

Ship From Code

Mark For Code

Service Approver (DoDAAC)

Service Acceptor (DoDAAC)

W906ZL

Accept at Other DoDAAC

LPO DoDAAC

DCAA Auditor DoDAAC

Other DoDAAC(s)

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

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

Matt Sanders

Contract Specialist

Lovisa Parks

Contracting Officer

Carlos Homs

Program Director

Carlos Homs

Contracting Officer’s Representative (TBD)

MAJ Morales

Product Coordinator

ACO (TBD)

Acceptor of FINAL (Performance Based Payments) & all Cost Vouchers

(2) For technical WAWF help, contact the WAWF helpdesk at 866-618-5988.

(End of clause)

5152.201-5001

DESIGNATION OF CONTRACTING OFFICER’S REPRESENTATIVE (COR) (PEO-STRI) (SEP 2006)

(a) The Contracting Officer has designated Carlos Homs as the authorized Contracting Officer’s Representative (COR) for this contract.

(b) The duties of the COR are limited to the following:

1. Verify that the contractor performs the technical requirements of the contract in accordance with the contract terms, conditions and specifications. Specific emphasis should be placed on the quality provisions, for both adherences to the contract provisions and to the contractor’s own quality control program.

2. Perform, or cause to be performed, inspections necessary in connection with the JLCCTC Statement of Work and verify that the contractor has corrected all deficiencies. Perform acceptance for the Government of requirements performed under this contract.

3. Maintain liaison and direct communications with the contractor. Written communications with the contractor and other documents pertaining to the contract shall be signed as ―Contracting Officer’s Representative‖ and a copy shall be furnished to the contracting officer.

4. Monitor the contractor’s performance; notify the contractor of deficiencies observed during surveillance and direct appropriate action to effect correction. Record and report to the contracting officer incidents of faulty or nonconforming work, delays or problems. In addition, you are required to submit a monthly report concerning performance of services rendered under this contract.

5. If the performance of this contract requires contractor personnel access to a Government installation, you are responsible for ensuring such personnel adhere to the check-in and check-out procedures.

6. Ensure that any Government-furnished property/equipment is available when required.

7. In accomplishing your duties as COR, you are cautioned to ensure the contract/order does not become a personal services contract/order through your actions or the actions of other government personnel. You must notify the PCO of any noted technical deficiencies or deviations not specifically approved by the PCO. The PCO may seek your technical advice from time to time, especially concerning the technical qualifications of contractor key personnel. The contractor will furnish you a copy of the invoices and backup for your review and retention (via Wide Area Work Flow (WAWF) website at https://wawf.eb.mil); discrepancies should be brought to the PCO’s attention promptly. Pay particular attention to the timely review of invoices. The PCO will notify the contractor that you are the COR for this contract/order. You should have access to a copy of the contract and all modifications and be familiar with such things as contract type, cost limitations, deliverables, and any special contract requirements. You are required to read reference d and understand your role and responsibilities in the Contractor Performance Assessment Reporting Systems (CPARS) website at https://cpars.csd.disa.mil/cpars/app/home.do process. I am available to answer questions regarding the process and your participation in it.

8. You are not empowered to award, agree to or sign any contract (including delivery orders) or contract modification or in any way to obligate the payment of money by the Government. You may not take any action which may affect contract or delivery order schedules, funds or scope. All contractual agreements, commitments, or modifications which involve price, quantity, quality, delivery schedules, or other terms and conditions of the contract must be made by the contacting officer. You may be personally liable for unauthorized acts. You may not re-delegate your COR authority.

9. You must notify the PCO when you will be unavailable to perform your COR duties. The COR duties and responsibilities associated with this appointment cannot be delegated by you to any other person.

(End of Clause) 5152.242-5003

FUNDING TO BE PROVIDED ON TASK ORDERS (PEO-STRI) (SEP 2006)

All funding for this contract will be provided on the individual delivery/task orders. Delivery order 0001 issued concurrent to award of this contract meets the Government’s minimum requirement.

Section H - Special Contract Requirements

H.1 USE OF CONTRACT TYPES

The following contract types may be utilized for orders issued under this contract:

Firm-Fixed-Price (FFP)

Cost-Plus-Fixed-Fee (CPFF)

Cost

Time and Materials (T&M)

a. Individual orders may warrant the use of other contract types not identified above. If the Procuring Contracting Officer (PCO) determines this to be the case, then that order must incorporate all applicable clauses. The subject clauses shall pertain only to that order.

b. The PCO shall have discretion as to the mix of contract types to be utilized under each order.

H.2 SOFTWARE TRANSFER RIGHTS

Software License Transfer Rights and End User License Agreements (EULA)

The Department of Defense (DoD) shall have the right, without the prior written consent of the Publisher or its Authorized Resellers, to assign, reassign, or transfer software licenses or DoD’s rights in the Software to an “Affiliate” of DoD, to include any governmental organization or commercial entity that is managed, operated or controlled by the DoD. “Affiliates” means associated business concerns or individuals if, directly or indirectly--

(1) Either one controls or can control the other; or

(2) A third party controls or can control both.

Such authorization includes sublicensing, assignment or transfer among or between “Authorized Users”. In the event an Authorized User is reorganized or restructured such that its responsibilities and operations are transferred to another DoD agency, the agency shall have the right to assign the affected program licenses to a successor. The licensed agency and the successor agency agree to be bound to this EULA. The transferee shall be bound by the license metrics and limitations in this license. DoD shall complete any required Licensor documentation required to facilitate the transfer of license and continuation of support for the transferee.

The Contractor, whether it be the buyer, authorized reseller or publisher of the software in question, shall not accept, transfer or inact automatic renewal provisions related with the EULA of the associated software without prior determination and consent by the PCO.

H.3 USE OF CHESS

ACQUISITON OF COMPUTER HARDWARE, SOFTWARE, INFORMATION TECHNOLOGY, OR RELATED SERVICES

Use of CHESS under this contract is in accordance with AFARS Subpart 5108-7403(5)(iii), DFARS PGI 208-7403, and FAR 52.251-1, Government Supply Sources (APR 1984) for commercial off-the-shelf (COTS) computer and software available on subject contract. Waivers may be pursued via procedures delineated at the website https://chess.army.mil.

This requirement is only for the purchase of commercial Information Technology (IT) equipment that is intended to be standalone and not integrated into a system or subsystem.

The Enterprise Software Initiative (ESI) website may be accessed via the link: https://chess.army.mil/ascp/commerce/contract/ites2-h.jsp

H.4 TEAMING AGREEMENTS

UTILIZATION OF TEAMING AGREEMENTS AND ASSOCIATE CONTRACTOR AGREEMENTS (ACA)

The Government does not expect the utilization of agreements between parties to be binding for the entire length of the contract or Delivery Order (DO) performance period under which it is to be established. Agreements shall comply with the language contained herein only for the time period determined adequate to meet or exceed the requirements for which it is to be drafted. Each DO will stand alone and, given the unknown nature of future requirements under SOFAST-E, the Government acknowledges the unlikelihood that the Prime contractor will be able to satisfy these future requirements with the same subcontractor(s).

The Contractor shall enter into Teaming Agreements or ACAs for any portion of the contract requiring joint participation in the accomplishment of the Government’s requirement. The agreement(s) shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential for the successful completion of the subject SOFAST-E requirement(s) and which meet the terms of the contract. At a minimum each agreement shall include the following information:

(1) Specify the associate contractor and their relationships.

(2) Identify the program involved and the relevant Government contracts of the associate contractors.

(4) Specify the type of work to be performed by or information to be exchanged with the associate contractor.

(5) Include the expiration date (or event) of the ACA.

(6) Identify potential conflicts between relevant Government contracts and the ACA; include agreements on protection of proprietary data and restrictions on employees.

(a) A copy of such agreement shall be provided to the Contracting Officer for review before bilaterally signed execution of the document by the cooperating contractors.

(b) The Contractor is not relieved of any contract requirements or entitled to any adjustments to the contract terms because of a failure to resolve a disagreement with an associate contractor.

(c) Liability for the improper disclosure of any proprietary data contained in or referenced by any agreement shall rest with the parties to the agreement, and not the Government.

(d) All costs associated with the agreements are included in the negotiated cost of this contract. Agreements may be amended as required by the Government during the performance of this contract.

(e) Bilaterally signed copies of each agreement shall be provided to the Government prior to the associate contractors performance.

H.5 CLICKWRAP LICENSING CLAUSE

H.5 USE OF “CLICKWRAP” LICENSES

(a) Except with respect to commercial computer software as defined in DFARS 252.227-

7014(a)(1), no contractor, subcontractor, or third-party license or other restriction shall be included with or imposed on software delivered pursuant to this contract, the terms of which differ from or conflict with the terms of this contract, including, but not limited to, terms relating to rights in technical data, rights in noncommercial computer software and noncommercial computer software documentation, indemnification, and liability; unless such license(s) or restriction(s) are approved by the Contracting Officer in writing and expressly incorporated into the contract prior to the delivery of software subject to such license(s) or restriction(s). Such licenses or restrictions include, by way of illustration and not limitation, so-called “clickwrap” licenses.

(b) For any commercial computer software as defined in DFARS 252.227-7014(a)(1) that the contractor intends to incorporate into or deliver with any software to be delivered pursuant to this contract, the contractor shall identify such software or documentation to the Contracting

Officer or the Contracting Officer’s designated representative prior to delivery thereof. The contractor shall also supply to the Contracting Officer or the Contracting Officer’s designated representative a copy of any licenses applicable to such software at the time the software is identified. The contractor, in accordance with the Contracting Officer’s instructions, shall negotiate any changes to the license that are required to make the license consistent with

Federal procurement law and the Government’s needs regarding such software. No such software shall be incorporated into or delivered with other software delivered pursuant to the terms of this contract without the Contracting Officer’s express written permission.

(c) (1) For any open source software (as defined at Section 3.1 of the CENDI report at http://www.cendi.gov/publications/09-1FAQ_OpenSourceSoftware_FINAL_110109.pdf.)

that will be included in any deliverable item or part thereof under this contract, or will be used to create any deliverable item or part thereof under this contract, the contractor shall:

(i) identify the open source software;

(ii) provide, for each of the software identified in (i), copies of any and all licenses associated with such software;

(iii)ensure, for each of the licenses identified in (ii), that the Government’s rights under such licenses permit the Government to use the deliverable(s) for its intended purpose; and

(iv) ensure that the contractor has complied with any and all requirements of the licenses identified in (ii).

(2) Any licenses relating to open source software shall be subject to all the requirements of this clause.

(d) Notwithstanding the requirements of paragraphs (a) and (b) hereof, no software shall be delivered pursuant to this contract if the software or any part thereof is subject to any copyright, license, or other reservation of rights (hereafter “reservation”) that imposes any requirement of subsequent action by the Government, unless express written permission for such inclusion is obtained from the Contracting Officer prior to delivery of such software.

Such requirement of subsequent action includes by way of illustration and not limitation: a requirement that upon distribution the Government must make such software available in any form to any entity; a requirement that prior to a distribution of the software by the

Government the Government is obliged in any way to ensure that the entity to which it distributes the software abides by the terms of the reservation or acquires any license or other right; or any requirement that is inconsistent with Federal laws including but not limited to national security requirements, export control laws and regulations, or acquisition laws and regulations.

H.6 PROVISIONAL ITEM CLAUSE

H.6 - REOPENER CLAUSE FOR OPTION PRICE REDETERMINATION FOR FIRM-FIXED-PRICE (FFP) SPARE PART LINE ITEMS

The Government reserves the right to downward equitable adjustment for contract pricing involving Firm-fixed-price (FFP) spare part option line items. In accordance with The Office of the Secretary of Defense (OSD) Memorandum, Cost and Price Analysis of Spare Parts Required Before Exercising an Option, dated 15 December 2011, any FFP Option line items for Spare Parts awarded under this contract shall require a written determination of price reasonableness by the PCO prior to exercising. The purpose of this analysis is to ensure that the proposed costs associated with the aforementioned spare parts remains fair and reasonable based upon current market listings (i.e. catalog pricing, supplier quotes and volume discounts (if applicable)). This determination will be in conjunction with and does not preclude the requirements found under 52.217-8 Option to Extend the Term of the Contract and FAR 17.207 – Exercise of Options.

Upon receipt of the Government’s notice of intent to exercise any FFP Option, which falls under the auspices of this clause, the Contractor shall comply with the following:

(a) Within 10 business days from the notice of intent to exercise the subject Option, the Contractor shall submit a supplemental cost impact proposal to the procuring Contracting Officer for purposes of performing a cost/price analysis to determine reasonable substantiation for a downward equitable adjustment in the subject contract and Option price. The supplemental proposal shall, at a minimum, provide (i) a revised Bill of Material (BOM) for the subject line item, reflecting any downward cost differentials and (ii) include the effect of any potential accounting system changes and/or contract modifications which may impact the amount of the adjustment. This proposal shall also incorporate the degree of change (in U.S. dollars) from the original awarded price.

(b) If determined necessary by the Contracting Officer, the Contractor agrees to commence negotiations concerning the amount of the adjustment within 10 business days after receipt of the supplemental proposal by the Government.

(c) Should the Contractor fail to submit the information in part (a), or should there be no agreement as to the amount of the price adjustment contemplated by this clause, then the Contracting Officer may make a unilateral determination and modify the contract accordingly. Failure to agree with such change in the contract price shall be resolved in accordance with the Disputes clause of this contract.

(d) The Contractor warrants that the revised contract and Option pricing does not include any other allowances and represents, to the best of the Contractors knowledge, the current commercial/market costs.

(e) The Government reserves the right to, upon request, receive the Contractor's cost and pricing data supporting the supplemental cost proposal, in whole and in part.

(f) In no event will an upward adjustment be resultant…