N00421-13-T-0367_COSWORTH...doc

Section B - Supplies or Services and Prices

4.4 Upfront Engine Support

FFP

Upfront Engine Support

Provide technical data and developmental feedback through teleconference meetings and email correspondence. Technical information to include:

CAD models of the following areas of the engine (Pro/E, STEP, or IGES)

Engine surface model

Engine head and combustion chamber models

Interface for engine load & auxiliary drives

Engine Mounting Points

Fuel pump drive geometry/location

Harness and fuel line routing

Engine technical & operational data sheets

Starting provisions & procedures

Identification of safe operational zones & operational limits (speeds, temperatures, pressures)

Wiring diagram of engine harness & sensor list

PC communication interface for ECU, required software, controls methodology

Advice on dyno driveline design

FOB: Destination

PURCHASE REQUEST NUMBER:

NET AMT

4.4 Developmental Engineering Support

Developmental Engineering Support – ($13,600.00)

Review proposed KBEI Micro Injection hardware interface for Cosworth engine

Injector placement, mounting considerations, fuel trajectories, and delivery rate

Fuel pump placement, mounting, and drive considerations

Review of engine controls development

NET AMT

4.4 On-Site Test Support

On Site Test Support

Initial run of Cosworth engine using as-supplied fuel delivery & engine management system.

Check test setup and system connections

Initial startup & break-in

Baseline Engine testing

10 hours engine operational testing

1 week duration

First run of KBEI components on Cosworth engine

KBEI Injector & ECU

Lab based fuel pump & pressure regulation

Initial tuning of controls system

10 hours engine operational testing

1 week duration

Complete KBEI system integration on Cosworth engine

Final tuning of controls system

Engine/System Performance Testing

20 hours engine operational testing

2 week duration

Final Test Incorporating KBEI improvements

20 hours engine operational testing

2 week duration

NET AMT

4.4 Travel to support engine test

Travel to KBEI facility in Nunica, MI to support engine testing

NET AMT

4.4 AG-EFI UAV Diesel Engine

NET AMT

Section C - Descriptions and Specifications

STATEMENT OF WORK

Statement of Work - Engine Hardware/Engineering Support

Support Kinetic BEI Implementation of Micro Injection System on Cosworth AG-EFI Heavy Fuel Engine;

1. Cosworth Supplied Engine Hardware

· One (1) Cosworth AG-HFE heavy fuel engine including:

a. Engine ECU

b. Wiring harness

c. Engine sensors

d. Fuel pump/delivery system

2. Cosworth Engineering Support

· Up Front Engineering Support Provide technical data and developmental feedback through teleconference meetings and email correspondence. Technical information to include:

· CAD models of the following areas of the engine (Pro/E, STEP, or IGES)

· Engine surface model

· Engine head and combustion chamber models

· Interface for engine load & auxiliary drives

· Engine Mounting Points

· Fuel pump drive geometry/location

· Harness and fuel line routing

· Engine technical & operational data sheets

· Starting provisions & procedures

· Identification of safe operational zones & operational limits (speeds, temperatures, pressures)

· Wiring diagram of engine harness & sensor list

· PC communication interface for ECU, required software, controls methodology

· Advice on dyno driveline design

· Developmental Engineering Support

Review proposed KBEI Micro Injection hardware interface for Cosworth engine

· Injector placement, mounting considerations, fuel trajectories, and delivery rate

· Fuel pump placement, mounting, and drive considerations

· Review of engine controls development

· On Site Test Support Travel to KBEI facility in Nunica, MI to support engine testing

· Initial run of Cosworth engine using as-supplied fuel delivery & engine management system.

· Check test setup and system connections

· Initial startup & break-in

· Baseline Engine testing

· 10 hours engine operational testing

· 1 week duration

· First run of KBEI components on Cosworth engine

· KBEI Injector & ECU

· Lab based fuel pump & pressure regulation

· Initial tuning of controls system

· 10 hours engine operational testing

· 1 week duration

· Complete KBEI system integration on Cosworth engine

· Final tuning of controls system

· Engine/System Performance Testing

· 20 hours engine operational testing

· 2 week duration

· Final Test Incorporating KBEI improvements

· 20 hours engine operational testing

· 2 week duration

Section E - Inspection and Acceptance

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

Section F - Deliveries or Performance

DELIVERY INFORMATION

RECEIVING OFFICER

SUPPLY DEPARTMENT BLDG.665

SUITE 100

47179 VAUGHN RD

PATUXENT RIVER MD 20670-1614

301-342-0543

N00421

N00421

N00421

N00421

N00421

Section G - Contract Administration Data

CLAUSES INCORPORATED BY FULL TEXT

252.232-7003

ELECTRONIC SUBMISSION OF PAYMENT REQUESTS AND RECEIVING REPORTS (JUN 2012)

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

(1) Contract financing payment and invoice payment have the meanings given in section 32.001 of the Federal Acquisition Regulation.

(2) Electronic form means any automated system that transmits information electronically from the initiating system to all affected systems. Facsimile, e-mail, and scanned documents are not acceptable electronic forms for submission of payment requests. However, scanned documents are acceptable when they are part of a submission of a payment request made using Wide Area WorkFlow (WAWF) or another electronic form authorized by the Contracting Officer.

(3) Payment request means any request for contract financing payment or invoice payment submitted by the Contractor under this contract.

(4) Receiving report means the data required by the clause at 252.246-7000, Material Inspection and Receiving Report.

(b) Except as provided in paragraph (c) of this clause, the Contractor shall submit payment requests and receiving reports using WAWF, in one of the following electronic formats that WAWF accepts: Electronic Data Interchange, Secure File Transfer Protocol, or World Wide Web input. Information regarding WAWF is available on the Internet at https://wawf.eb.mil/ .

(c) The Contractor may submit a payment request and receiving report using other than WAWF only when--

(1) The Contracting Officer administering the contract for payment has determined, in writing, that electronic submission would be unduly burdensome to the Contractor. In such cases, the Contractor shall include a copy of the Contracting Officer's determination with each request for payment;

(2) DoD makes payment for commercial transportation services provided under a Government rate tender or a contract for transportation services using a DoD-approved electronic third party payment system or other exempted vendor payment/invoicing system (e.g., PowerTrack, Transportation Financial Management System, and Cargo and Billing System);

(3) DoD makes payment for rendered health care services using TRICARE Encounter Data System (TEDS) as the electronic format; or

(4) When the Governmentwide commercial purchase card is used as the method of payment, only submission of the receiving report in electronic form is required.

(d) The Contractor shall submit any non-electronic payment requests using the method or methods specified in Section G of the contract.

(e) In addition to the requirements of this clause, the Contractor shall meet the requirements of the appropriate payment clauses in this contract when submitting payments requests.

252.232-7006

WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (MAY 2013)

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

"Department of Defense Activity Address Code (DoDAAC)" is a six position code that uniquely identifies a unit, activity, or organization.

"Document type" means the type of payment request or receiving report available for creation in Wide Area WorkFlow (WAWF).

"Local processing office (LPO)" is the office responsible for payment certification when payment certification is done external to the entitlement system.

(b) Electronic invoicing. The WAWF system is the method to electronically process vendor payment requests and receiving reports, as authorized by DFARS 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.

(c) WAWF access. To access WAWF, the Contractor shall--

(1) Have a designated electronic business point of contact in the System for Award Management at https://www.acquisition.gov; and

(2) Be registered to use WAWF at https://wawf.eb.mil/ following the step-by-step procedures for self-registration available at this Web site.

(d) WAWF training. The Contractor should follow the training instructions of the WAWF Web-Based Training Course and use the Practice Training Site before submitting payment requests through WAWF. Both can be accessed by selecting the "Web Based Training" link on the WAWF home page at https://wawf.eb.mil/.

(e) WAWF methods of document submission. Document submissions may be via Web entry, Electronic Data Interchange, or File Transfer Protocol.

(f) WAWF payment instructions. The Contractor must use the following information when submitting payment requests and receiving reports in WAWF for this contract/order:

(1) Document type. The Contractor shall use the following document type(s).

_____combo______________________________________________________________________

(Contracting Officer: Insert applicable document type(s). Note: If a "Combo" document type is identified but not supportable by the Contractor's business systems, an "Invoice" (stand-alone) and "Receiving Report" (stand-alone) document type may be used instead.)

(2) Inspection/acceptance location. The Contractor shall select the following inspection/acceptance location(s) in WAWF, as specified by the contracting officer.

_____See Section E_____________________________________________________________________

(Contracting Officer: Insert inspection and acceptance locations or "Not applicable.")

(3) Document routing. The Contractor shall use the information in the Routing Data Table below only to fill in applicable fields in WAWF when creating payment requests and receiving reports in the system.

Routing Data Table*

Field Name in WAWF

Data to be entered in WAWF

Pay Official DoDAAC:

N64142 __________________

Issue By DoDAAC:

N00421__________________

Admin DoDAAC:

Inspect By DoDAAC:

Ship To Code:

Ship From Code:

Mark For Code:

Service Approver (DoDAAC):

Service Acceptor (DoDAAC):

Accept at Other DoDAAC:

LPO DoDAAC:

DCAA Auditor DoDAAC:

Other DoDAAC(s):

(*Contracting Officer: Insert applicable DoDAAC information or "See schedule" if multiple ship to/acceptance locations apply, or "Not applicable.")

(4) Payment request and supporting documentation. The Contractor shall ensure a payment request includes appropriate contract line item and subline item descriptions of the work performed or supplies delivered, unit price/cost per unit, fee (if applicable), and all relevant back-up documentation, as defined in DFARS Appendix F, (e.g. timesheets) in support of each payment request.

(5) WAWF email notifications. The Contractor shall enter the email address identified below in the "Send Additional Email Notifications" field of WAWF once a document is submitted in the system.

_MICHELLE.WATHEN@NAVY.MIL__________________________________________________________________________ (Contracting Officer: Insert applicable email addresses or "Not applicable.")

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

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

Section H - Special Contract Requirements

CLAUSES INCORPORATED BY FULL TEXT

5252.211- 9510

CONTRACTOR EMPLOYEES (NAVAIR)(MAY 2011)

(a) In all situations where contractor personnel status is not obvious, all contractor personnel are required to identify themselves to avoid creating an impression to the public, agency officials, or Congress that such contractor personnel are Government officials. This can occur during meeting attendance, through written (letter or email) correspondence or verbal discussions (in person or telephonic), when making presentations, or in other situations where their contractor status is not obvious to third parties. This list is not exhaustive. Therefore, the contractor employee(s) shall:

(1) Not by word or deed give the impression or appearance of being a Government employee;

(2) Wear appropriate badges visible above the waist that identify them as contractor employees when in Government spaces, at a Government-sponsored event, or an event outside normal work spaces in support of the contract/order;

(3) Clearly identify themselves as contractor employees in telephone conversations and in all formal and informal written and electronic correspondence. Identification shall include the name of the company for whom they work;

(4) Identify themselves by name, their company name, if they are a subcontractor the name of the prime contractor their company is supporting, as well as the Government office they are supporting when participating in meetings, conferences, and other interactions in which all parties are not in daily contact with the individual contractor employee; and

(5) Be able to provide, when asked, the full number of the contract/order under which they are performing, and the name of the Contracting Officer’s Representative.

(b) If wearing a badge is a risk to safety and/or security, then an alternative means of identification maybe utilized if endorsed by the Contracting Officer’s Representative and approved by the Contracting Officer.

(c) The Contracting Officer will make final determination of compliance with regulations with regard to proper identification of contractor employees.

Section I - Contract Clauses

CLAUSES INCORPORATED BY REFERENCE

CLAUSES INCORPORATED BY FULL TEXT

52.252-2

CLAUSES INCORPORATED BY REFERENCE (FEB 1998)

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

252.204-7000

DISCLOSURE OF INFORMATION (DEC 1991)

(a) The Contractor shall not release to anyone outside the Contractor's organization any unclassified information, regardless of medium (e.g., film, tape, document), pertaining to any part of this contract or any program related to this contract, unless--

(1) The Contracting Officer has given prior written approval; or

(2) The information is otherwise in the public domain before the date of release.

(b) Requests for approval shall identify the specific information to be released, the medium to be used, and the purpose for the release. The Contractor shall submit its request to the Contracting Officer at least 45 days before the proposed date for release.

(c) The Contractor agrees to include a similar requirement in each subcontract under this contract. Subcontractors shall submit requests for authorization to release through the prime contractor to the Contracting Officer.

NAVAL AIR WARFARE CENTER (PAX)---

RECEIVING OFFICER

SUPPLY DEPARTMENT BLDG.665

SUITE 100

47179 VAUGHN RD

PATUXENT RIVER MD 20670-1614

TEL: 301-342-0543 FAX:

REQUEST FOR QUOTATIONS

(THIS IS NOT AN ORDER)

PAGE OF PAGES

1. REQUEST NO.

2. DATE ISSUED

RATING

N00421-13-T-0367

27-Jun-2013

5a. ISSUED BY

8. TO: NAME AND ADDRESS, INCLUDING ZIP CODE

IMPORTANT:

This is a request for information, and quotations furnished are not offers. If you are unable to quote, please so indicate on this form and return it to the address in Block 5a. This request does not commit the Government to pay any costs incurred in the preparation of the submission of this quotation or to contract for supplies or services. Supplies are of domestic origin unless otherwise indicated by quoter. Any representations and/or certifications attached to this

Request for Quotations must be completed by the quoter.

11. SCHEDULE

(Include applicable Federal, State, and local taxes)

ITEM NO.

(a)

SUPPLIES/ SERVICES

(b)

QUANTITY

(c)

UNIT

(d)

UNIT PRICE

(e)

(f)

SEE SCHEDULE

AMOUNT

No.

NOTE: Additional provisions and representations [ ] are [ ] are not attached.

13. NAME AND ADDRESS OF QUOTER

(Street, City, County, State, and

ZIP Code)

14. SIGNATURE OF PERSON AUTHORIZED TO

SIGN QUOTATION

15. DATE OF

QUOTATION

16. NAME AND TITLE OF SIGNER

(Type or print)

(Include area code)

TELEPHONE NO.

AUTHORIZED FOR LOCAL REPRODUCTION

STANDARD FORM 18

(REV. 6-95)

PREVIOUS EDITION NOT USABLE

Prescribed by GSA

FAR (48 CFR) 53.215-1(a)

THIS RFQ

X

[ ] IS

[ ] IS NOT A SMALL BUSINESS SET-ASIDE

6. DELIVER BY

(Date)

SEE SCHEDULE

AND/OR DMS REG. 1

UNDER BDSA REG. 2

4. CERT. FOR NAT. DEF.

3. REQUISITION/PURCHASE

REQUEST NO.

NAVAL AIR WARFARE CENTER AD (PAX)

2.5.1 RAC, 21983 BUNDY ROAD, BLDG 441

PATUXENT RIVER MD 20670-1127

9. DESTINATION

(Consignee and address, including ZIP Code)

7. DELIVERY

X

FOB

DESTINATION

[ ] OTHER

(See Schedule)

15-Jul-2013

(Date)

PLEASE FURNISH QUOTATIONS TO THE ISSUING OFFICE IN BLOCK 5a ON OR BEFORE CLOSE OF BUSINESS:

10.

301-757-8940

JOANN M. FELIX

(Name and Telephone no.) (No collect calls)

5b. FOR INFORMATION CALL:

d. CALENDAR DAYS

c. 30 CALENDAR DAYS

b. 20 CALENDAR DAYS

12. DISCOUNT FOR PROMPT PAYMENT

a. 10 CALENDAR DAYS