FA9101-18-R-0005_Burst_Diaphragm_Solicitation.pdf

SOLICITATION, OFFER AND AWARD

1. THIS CONTRACT IS A RATED ORDER

UNDER DPAS (15 CFR 350)

RATING

DO-C9

PAGE OF PAGES

1 19

2. CONTRACT NO. 3. SOLICITATION NO. 4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

5. DATE ISSUED

6. REQUISITION/PURCHASE NO.

FA9101-18-R-0005

7. ISSUED BY AFTC/PZI ARNOLD CODE FA9101 8. ADDRESS OFFER TO (If other than Item 7)

AFTC/PZI (ARNOLD)

100 KINDEL DRIVE, SUITE A-332

ARNOLD AFB, TN 37389-1332

ROBERT T. MOSLEY 9314546706

ROBERT.MOSLEY.3@US.AF.MIL

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

SOLICITATION

9.

10. FOR

INFORMATION

CALL:

A. NAME

See Block 7

B. TELEPHONE (Include area code)

(NO COLLECT CALLS)

C. E-MAIL ADDRESS

11. TABLE OF CONTENTS

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

PART I - THE SCHEDULE PART II - CONTRACT CLAUSES

A SOLICITATION/CONTRACT FORM 1 I CONTRACT CLAUSES 11

B SUPPLIES OR SERVICES AND PRICES/COSTS 2 PART III - LIST OF DOCUMENTS, EXHIBITS, AND OTHER ATTACH.

C DESCRIPTION/SPECS./WORK STATEMENT 4 J LIST OF ATTACHMENTS 19

D PACKAGING AND MARKING 5 PART IV - REPRESENTATIONS AND INSTRUCTIONS

E INSPECTION AND ACCEPTANCE 6 K REPRESENTATIONS, CERTIFICATIONS, K - 1

F DELIVERIES OR PERFORMANCE 7 AND OTHER STATEMENTS OF OFFERORS

G CONTRACT ADMINISTRATION DATA 8 L INSTRS, CONDS, AND NOTICES TO OFFERORS L - 1

H SPECIAL CONTRACT REQUIREMENTS 10 M EVALUATION FACTORS FOR AWARD M - 1

OFFER (Must be fully completed by offeror) NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

12. In compliance with the above, the undersigned agrees, if this offer is accepted within ____ ____ calendar days (60 calendar days unless a different period is inserted by the offeror) from the date of receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. DISCOUNT FOR PROMPT PAYMENT

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

10 CALENDAR DAYS

20 CALENDAR DAYS

30 CALENDAR DAYS

CALENDAR DAYS

14. ACKNOWLEDGEMENTS OF AMENDMENTS

(The offeror acknowledges receipt of amend-

AMENDMENT NO. DATE AMENDMENT NO. DATE

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

15A. NAME

AND

CODE FACILITY 16. NAME AND TITLE OF PERSON AUTHORIZED TO SIGN

OFFER (Type or print)

ADDRESS

OF

OFFEROR

15B. TELEPHONE NO. (Include area code)

15C. CHECK IF REMITTANCE ADDRESS

IS DIFFERENT FROM ABOVE - ENTER

SUCH ADDRESS IN SCHEDULE.

17. SIGNATURE 18. OFFER DATE

AWARD (To be completed by Government)

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

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETI-

TION: 23. SUBMIT INVOICES TO ADDRESS SHOWN IN

(4 copies unless otherwise specified)

ITEM

10 U.S.C. 2304(c) (6) 41 U.S.C. 253(c) ( )

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

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

(Signature of Contracting Officer)

28. AWARD DATE

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

AUTHORIZED FOR LOCAL REPRODUCTION STANDARD FORM 33 (REV. 9-97)

PREVIOUS EDITION IS UNUSABLE Prescribed by GSA ConWrite Version 6.15.4 FAR (48 CFR) 53.21(c) Created 02 Feb 2018 9:17 AM

PART I - THE SCHEDULE

SECTION B - SUPPLIES OR SERVICES AND PRICES/COSTS

SECTION B FA9101-18-R-0005

Qty Unit Price ITEM SUPPLIES OR SERVICES Purch Unit Total Item Amount

C-103 Mach 14 Burst Diaphragm

0001 200 __________ Each __________ Noun: C-103 MACH 14 BURST DIAPHRAGMS

PSC: 9535

NSN: N - Not Applicable Contract type: J - FIRM FIXED PRICE Inspection: DESTINATION Acceptance: DESTINATION

FOB: DESTINATION

Descriptive Data:

The purpose of the effort is to fabricate two hundred (200) C-103 Mach 14 burst diaphragms corresponding to drawing 77-1088-13 for the Arnold Engineering Development Complex (AEDC) Tunnel 9.

SECTION B - SUPPLIES OR SERVICES AND PRICES/COSTS

SECTION B FA9101-18-R-0005

NO CLAUSES OR PROVISIONS IN THIS SECTION

SECTION C - DESCRIPTION/SPECS./WORK STATEMENT

SECTION C FA9101-18-R-0005

SECTION D - PACKAGING AND MARKING

SECTION D FA9101-18-R-0005

SECTION E - INSPECTION AND ACCEPTANCE

SECTION E FA9101-18-R-0005

NOTICE: The following contract clauses pertinent to this section are hereby incorporated by reference:

FEDERAL ACQUISITION REGULATION CONTRACT CLAUSES

52.246-02 INSPECTION OF SUPPLIES -- FIXED-PRICE (AUG 1996)

52.246-15 CERTIFICATE OF CONFORMANCE (APR 1984)

52.246-16 RESPONSIBILITY FOR SUPPLIES (APR 1984)

SECTION F - DELIVERIES OR PERFORMANCE

SECTION F FA9101-18-R-0005

SHIP MARK TRANS

ITEM SUPPLIES SCHEDULE DATA QTY TO FOR PRI DATE

0001 200 U ASREQ

Noun: C-103 MACH 14 BURST DIAPHRAGMS

NOTICE: The following contract clauses pertinent to this section are hereby incorporated by reference:

FEDERAL ACQUISITION REGULATION CONTRACT CLAUSES

52.247-34 F.O.B. DESTINATION (NOV 1991)

SECTION G - CONTRACT ADMINISTRATION DATA

SECTION G FA9101-18-R-0005

NOTICE: The following contract clauses pertinent to this section are hereby incorporated in full text:

DEFENSE FAR SUPP CONTRACT CLAUSES IN FULL TEXT

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.

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.

F1EEDH

SECTION G - CONTRACT ADMINISTRATION DATA

SECTION G FA9101-18-R-0005

(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 F03000 Issue By DoDAAC F1EEDH Admin DoDAAC FA9101 Inspect By DoDAAC F1EEDH Ship To Code F1EEDH Ship From Code N/A Mark For Code F1EEDH Service Approver (DoDAAC) N/A Service Acceptor (DoDAAC) N/A Accept at Other DoDAAC N/A LPO DoDAAC N/A DCAA Auditor DoDAAC N/A Other DoDAAC(s) N/A

(*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 e-mail address identified below in the “Send Additional Email Notifications” field of WAWF once a document is submitted in the system.

robert.mosley.3@us.af.mil

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

Ms. Patricia Henderson, patricia.henderson.2@us.af.mil

Ms. Tyler Payne, tyler.payne.9@us.af.mil

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

SECTION H - SPECIAL CONTRACT REQUIREMENTS

SECTION H FA9101-18-R-0005

PART II - CONTRACT CLAUSES

SECTION I - CONTRACT CLAUSES

SECTION I FA9101-18-R-0005

Contract Clauses in this section are from the FAR, Defense FAR Sup, Air Force FAR Sup, and the Air Force Materiel Command FAR Sup, and are current through the following updates:

Database_Version: 6.15.x1100; Issued: 10/27/2017; FAR: FAC 2005-95; DFAR: DPN20161222; DL.: DL 98- 021; Class Deviations: CD 2017-O0002; AFFAR: 2002 Edition; AFAC: AFAC 2017-1003; IPN: 98-009

I. NOTICE: The following contract clauses pertinent to this section are hereby incorporated by reference:

A. FEDERAL ACQUISITION REGULATION CONTRACT CLAUSES

52.203-03 GRATUITIES (APR 1984)

52.203-10 PRICE OR FEE ADJUSTMENT FOR ILLEGAL OR IMPROPER ACTIVITY (MAY 2014)

52.203-12 LIMITATION ON PAYMENTS TO INFLUENCE CERTAIN FEDERAL TRANSACTIONS

(OCT 2010)

52.203-16 PREVENTING PERSONAL CONFLICTS OF INTEREST (DEC 2011)

52.203-17 CONTRACTOR EMPLOYEE WHISTLEBLOWER RIGHTS AND REQUIREMENT TO

INFORM EMPLOYEES OF WHISTLEBLOWER RIGHTS (APR 2014)

52.203-19 PROHIBITION ON REQUIRING CERTAIN INTERNAL CONFIDENTIALITY

AGREEMENTS OR STATEMENTS (JAN 2017)

52.204-04 PRINTED OR COPIED DOUBLE-SIDED ON POSTCONSUMER FIBER CONTENT

PAPER (MAY 2011)

52.204-09 PERSONAL IDENTITY VERIFICATION OF CONTRACTOR PERSONNEL (JAN 2011)

52.204-10 REPORTING EXECUTIVE COMPENSATION AND FIRST-TIER SUBCONTRACT

AWARDS (OCT 2016)

52.204-18 COMMERCIAL AND GOVERNMENT ENTITY CODE MAINTENANCE (JUL 2016)

52.204-21 BASIC SAFEGUARDING OF COVERED CONTRACTOR INFORMATION SYSTEMS

(JUN 2016)

52.209-06 PROTECTING THE GOVERNMENT'S INTEREST WHEN SUBCONTRACTING WITH

CONTRACTORS DEBARRED, SUSPENDED, OR PROPOSED FOR DEBARMENT

(OCT 2015)

52.209-10 PROHIBITION ON CONTRACTING WITH INVERTED DOMESTIC CORPORATIONS

(NOV 2015)

52.211-05 MATERIAL REQUIREMENTS (AUG 2000)

52.215-02 AUDIT AND RECORDS -- NEGOTIATION (OCT 2010)

52.215-08 ORDER OF PRECEDENCE--UNIFORM CONTRACT FORMAT (OCT 1997)

52.215-14 INTEGRITY OF UNIT PRICES (OCT 2010)

52.219-06 NOTICE OF TOTAL SMALL BUSINESS SET-ASIDE (NOV 2011)

52.219-08 UTILIZATION OF SMALL BUSINESS CONCERNS (NOV 2016)

52.219-14 LIMITATIONS ON SUBCONTRACTING (JAN 2017)

52.219-28 POST-AWARD SMALL BUSINESS PROGRAM REREPRESENTATION (JUL 2013)

52.222-03 CONVICT LABOR (JUN 2003)

52.222-19 CHILD LABOR--COOPERATION WITH AUTHORITIES AND REMEDIES (OCT 2016)

52.222-21 PROHIBITION OF SEGREGATED FACILITIES (APR 2015)

52.222-26 EQUAL OPPORTUNITY (SEP 2016)

52.222-35 EQUAL OPPORTUNITY FOR VETERANS (OCT 2015)

52.222-36 EQUAL OPPORTUNITY FOR WORKERS WITH DISABILITIES (JUL 2014)

52.222-37 EMPLOYMENT REPORTS ON VETERANS (FEB 2016)

52.222-50 COMBATING TRAFFICKING IN PERSONS (MAR 2015)

52.222-54 EMPLOYMENT ELIGIBILITY VERIFICATION (OCT 2015)

52.223-06 DRUG-FREE WORKPLACE (MAY 2001)

52.223-18 ENCOURAGING CONTRACTOR POLICIES TO BAN TEXT MESSAGING WHILE

DRIVING (AUG 2011)

52.225-13 RESTRICTIONS ON CERTAIN FOREIGN PURCHASES (JUN 2008)

52.227-01 AUTHORIZATION AND CONSENT (DEC 2007)

52.227-02 NOTICE AND ASSISTANCE REGARDING PATENT AND COPYRIGHT

INFRINGEMENT (DEC 2007)

52.232-33 PAYMENT BY ELECTRONIC FUNDS TRANSFER - SYSTEM FOR AWARD

MANAGEMENT (JUL 2013)

52.232-39 UNENFORCEABILITY OF UNAUTHORIZED OBLIGATIONS (JUN 2013)

52.232-40 PROVIDING ACCELERATED PAYMENTS TO SMALL BUSINESS

SUBCONTRACTORS (DEC 2013)

52.233-03 PROTEST AFTER AWARD (AUG 1996)

52.233-04 APPLICABLE LAW FOR BREACH OF CONTRACT CLAIM (OCT 2004)

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

52.249-02 TERMINATION FOR CONVENIENCE OF THE GOVERNMENT (FIXED-PRICE) (APR

2012)

52.249-08 DEFAULT (FIXED-PRICE SUPPLY AND SERVICE) (APR 1984)

52.253-01 COMPUTER GENERATED FORMS (JAN 1991)

B. DEFENSE FEDERAL ACQUISITION REGULATION SUPPLEMENT CONTRACT CLAUSES

252.203-7000 REQUIREMENTS RELATING TO COMPENSATION OF FORMER DOD OFFICIALS

(SEP 2011)

252.203-7001 PROHIBITION ON PERSONS CONVICTED OF FRAUD OR OTHER DEFENSE-

CONTRACT-RELATED FELONIES (DEC 2008)

252.203-7002 REQUIREMENT TO INFORM EMPLOYEES OF WHISTLEBLOWER RIGHTS (SEP

2013)

252.204-7003 CONTROL OF GOVERNMENT PERSONNEL WORK PRODUCT (APR 1992)

252.204-7008 COMPLIANCE WITH SAFEGUARDING COVERED DEFENSE INFORMATION

CONTROLS (OCT 2016)

252.204-7015 NOTICE OF AUTHORIZED DISCLOSURE OF INFORMATION TO LITIGATION

SUPPORT (MAY 2016)

252.211-7003 ITEM UNIQUE IDENTIFICATION AND VALUATION (MAR 2016)

Para (c)(1)(i). Insert Contract Line, Subline, or Exhibit Line Item Number and Item

Description or n/a. 'N/A' Para (c)(1)(ii). Identify Contract Line, Subline, or Exhibit Line Item Nr and Item

Description. If items are identified in the Schedule, insert "See Schedule" 'N/A' Para (c)(1)(iii). Attachment Nr. 'N/A' Para (c)(1)(iv). Attachment Nr. 'N/A' Para (f)(2)(iii). Line item number or n/a. 'N/A'

252.223-7008 PROHIBITION OF HEXAVALENT CHROMIUM (JUN 2013)

252.225-7001 BUY AMERICAN AND BALANCE OF PAYMENTS PROGRAM - BASIC (DEC 2016)

252.225-7002 QUALIFYING COUNTRY SOURCES AS SUBCONTRACTORS (DEC 2016)

252.225-7048 EXPORT-CONTROLLED ITEMS (JUN 2013)

252.232-7003 ELECTRONIC SUBMISSION OF PAYMENT REQUESTS AND RECEIVING REPORTS

(JUN 2012)

252.232-7010 LEVIES ON CONTRACT PAYMENTS (DEC 2006)

252.243-7001 PRICING OF CONTRACT MODIFICATIONS (DEC 1991)

252.243-7002 REQUESTS FOR EQUITABLE ADJUSTMENT (DEC 2012)

252.247-7023 TRANSPORTATION OF SUPPLIES BY SEA - BASIC (APR 2014)

C. AIR FORCE FEDERAL ACQUISITION REGULATION SUPPLEMENT CONTRACT CLAUSES

5352.201-9101 OMBUDSMAN (JUN 2016)

Para (c). Ombudsmen names, addresses, phone numbers, fax, and email addresses.

'The Center/MAJCOM or AFISRA Ombudsmen, Air Force Test Center Vice Commander, 1 South Rosamond Blvd, Edward AFB, CA 93524-3784, Phone Number (661) 2772810, Facsimile Number (661) 277-7593'

II. NOTICE: The following contract clauses pertinent to this section are hereby incorporated in full text:

A. FEDERAL ACQUISITION REGULATION CONTRACT CLAUSES IN FULL TEXT

52.252-02 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): http://farsite.hill.af.mil/

52.252-06 AUTHORIZED DEVIATIONS IN CLAUSES (APR 1984)

(a) The use in this solicitation or contract of any Federal Acquisition Regulation (48 CFR Chapter

1) clause with an authorized deviation is indicated by the addition of "(DEVIATION)" after the date of the clause.

(b) The use in this solicitation or contract of any Defense Federal Acquisition Regulation Supplement (48 CFR Chapter 2) clause with an authorized deviation is indicated by the addition of "(DEVIATION)" after the name of the regulation.

B. DEFENSE FAR SUPP CONTRACT CLAUSES IN FULL TEXT

252.204-7012 SAFEGUARDING COVERED DEFENSE INFORMATION AND CYBER INCIDENT

REPORTING (OCT 2016)

(a) Definitions. As used in this clause—

“Adequate security” means protective measures that are commensurate with the consequences and probability of loss, misuse, or unauthorized access to, or modification of information.

“Compromise” means disclosure of information to unauthorized persons, or a violation of the security policy of a system, in which unauthorized intentional or unintentional disclosure, modification, destruction, or loss of an object, or the copying of information to unauthorized media may have occurred.

“Contractor attributional/proprietary information” means information that identifies the contractor(s), whether directly or indirectly, by the grouping of information that can be traced back to the contractor(s) (e.g., program description, facility locations), personally identifiable information, as well as trade secrets, commercial or financial information, or other commercially sensitive information that is not customarily shared outside of the company.

“Contractor information system” means an unclassified information system that is owned, or operated by or for, a contractor and that processes, stores, or transmits covered defense information.

“Controlled technical information” means technical information with military or space application that is subject to controls on the access, use, reproduction, modification, performance, display, release, disclosure, or dissemination. Controlled technical information would meet the criteria, if disseminated, for distribution statements B through F using the criteria set forth in DoD Instruction 5230.24, Distribution Statements on Technical Documents. The term does not include information that is lawfully publicly available without restrictions.

“Covered contractor information system” means an information system that is owned, or operated by or for, a contractor and that processes, stores, or transmits covered defense information.

“Covered defense information” means unclassified controlled technical information or other information, as described in the Controlled Unclassified Information (CUI) Registry at http://www.archives.gov/cui/registry/category-list.html, that requires safeguarding or dissemination controls pursuant to and consistent with law, regulations, and Governmentwide policies, and is—

(1) Marked or otherwise identified in the contract, task order, or delivery order and provided to the contractor by or on behalf of DoD in support of the performance of the contract; or

(2) Collected, developed, received, transmitted, used, or stored by or on behalf of the contractor in support of the performance of the contract.

“Cyber incident” means actions taken through the use of computer networks that result in a compromise or an actual or potentially adverse effect on an information system and/or the information residing therein.

“Forensic analysis” means the practice of gathering, retaining, and analyzing computer-related data for investigative purposes in a manner that maintains the integrity of the data.

“Information system” means a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information.

“Malicious software” means computer software or firmware intended to perform an unauthorized process that will have adverse impact on the confidentiality, integrity, or availability of an information system. This definition includes a virus, worm, Trojan horse, or other code-based entity that infects a host, as well as spyware and some forms of adware.

“Media” means physical devices or writing surfaces including, but is not limited to, magnetic tapes, optical disks, magnetic disks, large-scale integration memory chips, and printouts onto which covered defense information is recorded, stored, or printed within a covered contractor information system.

‘‘Operationally critical support’’ means supplies or services designated by the Government as critical for airlift, sealift, intermodal transportation services, or logistical support that is essential to the mobilization, deployment, or sustainment of the Armed Forces in a contingency operation.

“Rapidly report” means within 72 hours of discovery of any cyber incident.

“Technical information” means technical data or computer software, as those terms are defined in the clause at DFARS 252.227-7013, Rights in Technical Data-Noncommercial Items, regardless of whether or not the clause is incorporated in this solicitation or contract. Examples of technical information include research and engineering data, engineering drawings, and associated lists, specifications, standards, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code.

(b) Adequate security. The Contractor shall provide adequate security on all covered contractor information systems. To provide adequate security, the Contractor shall implement, at a minimum, the following information security protections:

(1) For covered contractor information systems that are part of an Information Technology (IT) service or system operated on behalf of the Government, the following security requirements apply:

(i) Cloud computing services shall be subject to the security requirements specified in the clause 252.239-7010, Cloud Computing Services, of this contract.

(ii) Any other such IT service or system (i.e., other than cloud computing) shall be subject to the security requirements specified elsewhere in this contract.

(2) For covered contractor information systems that are not part of an IT service of system operated on behalf of the Government and therefore are not subject to the security requirement specified at paragraph (b)(1) of this clause, the following security requirements apply:

(i) Except as provided in paragraph (b)(2)(ii) of this clause, the covered contractor information system shall be subject to the security requirements in National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171, “Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations,” (available via the Internet at http://dx.doi.org/10.6028/NIST.SP.800-171) in effect at the time the solicitation is issued or as authorized by the Contracting Officer.

(ii)(A) The Contractor shall implement NIST SP 800-171, as soon as practical, but not later than December 31, 2017. For all contracts awarded prior to October 1, 2017, the Contractor shall notify the DoD Chief Information Officer (CIO), via email at osd.dibcsia@mail.mil, within 30 days of contract award, of any security requirements specified by NIST SP 800-171 not implemented at the time of contract award.

(B) The Contractor shall submit requests to vary from NIST SP 800-171 in writing to the Contracting Officer, for consideration by the DoD CIO. The Contractor need not implement any security requirement adjudicated by an authorized representative of the DoD CIO to be nonapplicable or to have an alternative, but equally effective, security measure that may be implemented in its place.

(C) If the DoD CIO has previously adjudicated the contractor’s requests indicating that a requirement is not applicable or that an alternative security measure is equally effective, a copy of that approval shall be provided to the Contracting Officer when requesting its recognition under this contract.

(D) If the Contractor intends to use an external cloud service provider to store, process, or transmit any covered defense information in performance of this contract, the Contractor shall require and ensure that the cloud service provider meets security requirements equivalent to those established by the Government for the Federal Risk and Authorization Management Program (FedRAMP) Moderate baseline https://www.fedramp.gov/resources/documents/) and that the cloud service provider complies with requirements in paragraphs (c) through (g) of this clause for cyber incident reporting, malicious software, media preservation and protection, access to additional information and equipment necessary for forensic analysis, and cyber incident damage assessment.

(3) Apply other information systems security measures when the Contractor reasonably determines that information systems security measures, in addition to those identified in paragraphs (b)(1) and (2) of this clause, may be required to provide adequate security in a dynamic environment or to accommodate special circumstances (e.g., medical devices) and any individual, isolated, or temporary deficiencies based on an assessed risk or vulnerability. These measures may be addressed in a system security plan.

(c) Cyber incident reporting requirement.

(1) When the Contractor discovers a cyber incident that affects a covered contractor information system or the covered defense information residing therein, or that affects the contractor’s ability to perform the requirements of the contract that are designated as operationally critical support and identified in the contrac, the Contractor shall—

(i) Conduct a review for evidence of compromise of covered defense information, including, but not limited to, identifying compromised computers, servers, specific data, and user accounts. This review shall also include analyzing covered contractor information system(s) that were part of the cyber incident, as well as other information systems on the Contractor’s network(s), that may have been accessed as a result of the incident in order to identify compromised covered defense information, or that affect the Contractor’s ability to provide operationally critical support; and

(ii) Rapidly report cyber incidents to DoD at http://dibnet.dod.mil.

(2) Cyber incident report. The cyber incident report shall be treated as information created by or for DoD and shall include, at a minimum, the required elements at http://dibnet.dod.mil.

(3) Medium assurance certificate requirement. In order to report cyber incidents in accordance with this clause, the Contractor or subcontractor shall have or acquire a DoD-approved medium assurance certificate to report cyber incidents. For information on obtaining a DoD-approved medium assurance certificate, see http://iase.disa.mil/pki/eca/Pages/index.aspx.

(d) Malicious software. When the Contractor or subcontractors discover and isolate malicious software in connection with a reported cyber incident, submit the malicious software to DoD Cyber Crime Center (DC3) in accordance with instructions provided by DC3 or the Contracting Officer. Do not send the malicious software to the Contracting Officer.

(e) Media preservation and protection. When a Contractor discovers a cyber incident has occurred, the Contractor shall preserve and protect images of all known affected information systems identified in paragraph (c)(1)(i) of this clause and all relevant monitoring/packet capture data for at least 90 days from the submission of the cyber incident report to allow DoD to request the media or decline interest.

(f) Access to additional information or equipment necessary for forensic analysis. Upon request by DoD, the Contractor shall provide DoD with access to additional information or equipment that is necessary to conduct a forensic analysis.

(g) Cyber incident damage assessment activities. If DoD elects to conduct a damage assessment, the Contracting Officer will request that the Contractor provide all of the damage assessment information gathered in accordance with paragraph (e) of this clause.

(h) DoD safeguarding and use of contractor attributional/proprietary information. The Government shall protect against the unauthorized use or release of information obtained from the contractor (or derived from information obtained from the contractor) under this clause that includes contractor attributional/proprietary information, including such information submitted in accordance with paragraph (c). To the maximum extent practicable, the Contractor shall identify and mark attributional/proprietary information. In making an authorized release of such information, the Government will implement appropriate procedures to minimize the contractor attributional/proprietary information that is included in such authorized release, seeking to include only that information that is necessary for the authorized purpose(s) for which the information is being released.

(i) Use and release of contractor attributional/proprietary information not created by or for DoD.

Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is not created by or for DoD is authorized to be released outside of DoD—

(1) To entities with missions that may be affected by such information;

(2) To entities that may be called upon to assist in the diagnosis, detection, or mitigation of cyber incidents;

(3) To Government entities that conduct counterintelligence or law enforcement investigations;

(4) For national security purposes, including cyber situational awareness and defense purposes (including with Defense Industrial Base (DIB) participants in the program at 32 CFR part 236);

or

(5) To a support services contractor (“recipient”) that is directly supporting Government activities under a contract that includes the clause at 252.204-7009, Limitations on the Use or Disclosure of Third-Party Contractor Reported Cyber Incident Information.

(j) Use and release of contractor attributional/proprietary information created by or for DoD.

Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is created by or for DoD (including the information submitted pursuant to paragraph

(c) of this clause) is authorized to be used and released outside of DoD for purposes and activities authorized by paragraph (i) of this clause, and for any other lawful Government purpose or activity, subject to all applicable statutory, regulatory, and policy based restrictions on the Government’s use and release of such information.

(k) The Contractor shall conduct activities under this clause in accordance with applicable laws and regulations on the interception, monitoring, access, use, and disclosure of electronic communications and data.

(l) Other safeguarding or reporting requirements. The safeguarding and cyber incident reporting required by this clause in no way abrogates the Contractor’s responsibility for other safeguarding or cyber incident reporting pertaining to its unclassified information systems as required by other applicable clauses of this contract, or as a result of other applicable U.S. Government statutory or regulatory requirements.

(m) Subcontracts. The Contractor shall—

(1) Include this clause, including this paragraph (m), in subcontracts, or similar contractual instruments, for operationally critical support, or for which subcontract performance will involve covered defense information, including subcontracts for commercial items, without alteration, except to identify the parties. The Contractor shall determine if the information required for subcontractor performance retains its identity as covered defense information and will require protection under this clause, and, if necessary, consult with the Contracting Officer; and

(2) Require subcontractors to—

(i) Notify the prime Contractor (or next higher-tier subcontractor) when submitting a request to vary from a NIST SP 800-171 security requirement to the Contracting Officer, in accordance with paragraph (b)(2)(ii)(B) of this clause; and

(ii) Provide the incident report number, automatically assigned by DoD, to the prime Contractor (or next higher-tier subcontractor) as soon as practicable, when reporting a cyber incident to DoD as required in paragraph (c) of this clause.

252.213-7000 NOTICE TO PROSPECTIVE SUPPLIERS ON USE OF PAST PEFORMANCE

INFORMATION RETRIEVAL SYSTEM—STATISTICAL REPORTING IN PAST PERFORMANCE

EVALUATIONS (JUN 2015)

(a) The Past Performance Information Retrieval System-Statistical Reporting (PPIRS-SR) application (http://www.ppirs.gov/) will be used in the evaluation of suppliers’ past performance in accordance with DFARS 213.106-2(b)(i).

(b) PPIRS-SR collects quality and delivery data on previously awarded contracts and orders from existing Department of Defense reporting systems to classify each supplier’s performance history by Federal supply class (FSC) and product or service code (PSC). The PPIRS-SR application provides the contracting officer quantifiable past performance information regarding a supplier's quality and delivery performance for the FSC and PSC of the supplies being purchased.

(c) The quality and delivery classifications identified for a supplier in PPIRS-SR will be used by the contracting officer to evaluate a supplier’s past performance in conjunction with the supplier’s references (if requested) and other provisions of this solicitation under the past performance evaluation factor. The Government reserves the right to award to the supplier whose quotation or offer represents the best value to the Government.

(d) PPIRS-SR classifications are generated monthly for each contractor and can be reviewed by following the access instructions in the PPIRS-SR User’s Manual found at https://www.ppirs.gov/pdf/PPIRS-SR_UserMan.pdf. Contractors are granted access to PPIRS-SR for their own classifications only. Suppliers are encouraged to review their own classifications, the PPIRS-SR reporting procedures and classification methodology detailed in the PPIRS-SR User's Manual, and PPIRS-SR Evaluation Criteria available from the references at https://www.ppirs.gov/pdf/PPIRS-SR_DataEvaluationCriteria.pdf. The method to challenge a rating generated by PPIRS-SR is provided in the User’s Manual.

PART III - LIST OF DOCUMENTS, EXHIBITS & ATTACHMENTS

SECTION J - LIST OF ATTACHMENTS

SECTION J FA9101-18-R-0005

DOCUMENT PGS DATE TITLE

ATTACHMENT 1 5 31 JAN 2018 SECTION L - INSTRUCTIONS TO OFFERORS

ATTACHMENT 2 2 31 JAN 2018 SECTION M - EVALUATION CRITERIA

ATTACHMENT 3 1 31 JAN 2018 MACH 14 BURST DIAPHRAGM STATEMENT OF

WORK

ATTACHMENT 4 1 31 JAN 2018 BURST DIAPHRAGM DRAWING 77-1088

ATTACHMENT 1

L-900. INSTRUCTIONS TO OFFERORS

I. Proposal Format

A. General: The following instructions cover the preparation and submittal of the offeror’s proposal for this solicitation. Offerors must follow the instructions contained herein. Offerors are cautioned that any noncompliance with the terms and conditions of the RFP may cause their proposal to be determined not eligible for award. If a joint venture arrangement exists for this acquisition, the offeror shall provide a copy of the joint venture agreement that is signed and dated by all joint venture members as part of the proposal submission. Offerors shall submit only one proposal for the Mach 14 Burst Diaphragm as the Government will review only one proposal per offeror. Proposals must be received electronically no later than the date and time specified in Block 8 on the face page of the RFP.

1. The Government intends to award one Firm-Fixed-Price contract for the acquisition of Mach 14 Burst Diaphragms. Therefore, to ensure timely and equitable evaluation of proposals, offerors must follow the instructions provided in this section. The offeror’s proposal shall include all data and information required by this solicitation and be submitted in accordance with the following instructions.

2. Failure to provide all required documentation may render offeror’s proposal noncompliant with the terms and conditions of the Request for Proposal and may cause their proposal to be determined ineligible for award.

(a). Offerors are required to meet all solicitation requirements, including terms and conditions;

representations and certifications; and technical requirements, factors and subfactors.

(b). Offerors must clearly identify any exception to the solicitation’s terms and conditions and provide rationale for the exception. Offerors are advised that taking an exception may render the offeror ineligible for award.

(c). Offerors are advised that progress payments are applicable to this acquisition.

(d). The offerors proposal shall consist of three separate parts: Part 1 – General Administrative Information, Part 2 – Price Proposal, and Part 3 – Technical Proposal. Each part shall be marked with the RFP number and offeror’s name and address, and the number of the part, I.e., Part 1, Part 2, and Part 3.

Proposals shall be in the English language and all monies shall be proposed in United States dollars.

B. Communications: Exchanges of source selection information between Government and offerors will be controlled by the Contracting Officer. Email may be used to transmit such information, only if the email can be sent encrypted, and must include “Source Selection Information – See FAR 2.101 and 3.104” in the subject line of the email. In order to facilitate the sending and receiving of encrypted emails, offerors must use MS Outlook email configured to support encryption or a different email product that is S/MIME compatible and configured to support encryption. If you intend to submit your source selection information via encrypted email, you will need to contact the Buyer/Contracting Officer indicated on the face page of the solicitation prior to that first submittal in order to exchange certificates used for encryption. To insure the process is working correctly, send a test encrypted message first (without including any source selection information). Offerors have the option to transmit source selection information via AMRDEC SAFE at https://safe.amrdec.army.mil/safe/guide.aspx .When submitting source selection information via email, file suppression utilities, to include but not limited to zip files, will not be accepted.

II. Volume Organization

A. General: Proposals shall be submitted to the Government in three separate volumes as set forth below:

PAGE NUMBER

VOLUME LIMITS OF COPIES DESCRIPTION

I N/A 1 Completed RFP II 22 1 Written Technical Proposal III N/A 1 Cost/Price Proposal https://safe.amrdec.army.mil/safe/guide.aspx

PCO Note: See Paragraph D, Volume III, Cost/Price, below for additional instructions on the Cost/Price Proposal

In addition to the page limitations set forth above, electronical proposal volumes shall comply with the following format:

1. Each volume shall be marked with the RFP number and the offeror’s name and address, and the number of the Volume, i.e. I, II, III, etc. Proposals shall be in the English language and all monies shall be proposed in United States dollars.

2. Print shall be no smaller than a font size of 12 and should be on 8 1/2 x 11 inch paper, excluding any charts, graphs, drawings, diagrams, supporting illustrations, or spreadsheets, etc. Charts, graphs, drawings, diagrams, supporting illustrations, spreadsheets, etc., shall not be greater than 11” x 17”. Each volume within the proposal shall be separately tabbed and identified. Margins shall be no smaller than 1 inch and each page within a volume shall be numbered consecutively. Elaborate formats, bindings, or color presentations are not desired or required. A page is defined as one face of a sheet of paper containing information.

3. The page limitation for Volume II, Written Technical Proposal, is 22 pages. The page limitation includes any charts, graphs, drawings, diagrams, supporting illustrations, spreadsheets, etc., tailor the information requested but excludes any cover page, table of contents or list of acronyms (if utilized). Offerors are cautioned that any pages that exceed the page limitations shall not be read but shall be removed and either retained in the contract file without being considered in the evaluation, or, sent back to the offeror.

4. Page limitations may be placed on Evaluation Notices (ENs), if issued. The specified limits for EN responses will be identified in the letters forwarding the ENs to the offerors or on the EN form itself.

5. Each page containing proprietary information should be so marked.

6. Each page should contain the following legend at the bottom of each sheet:

SOURCE SELECTION INFORMATION--SEE FAR 2.101 and 3.104

FOR OFFICIAL USE ONLY

7. Submission of the initial proposal packages via electronic mail/AMRDEC is authorized. Additionally, initial proposal packages can either be mailed or hand-delivered. Offerors are cautioned that Arnold Engineering Development Complex has visitor control procedures requiring individuals not affiliated with the installation to obtain a visitor pass prior to entrance. Delays should be anticipated when hand-delivering proposal packages. Offerors should allow for sufficient time to obtain a visitor pass and arrive at the specified office PRIOR to the time specified for receipt of proposals.

(a). For electronic submission, send proposal documents to Mr. Robert Mosley, robert.mosley.3@us.af.mil, no later than the due date and time listed on the RFP. Hard copies (i.e., mailed or hand-delivered) must be received at the designated location no later than the due date and time listed in block 9 of the SF 33.

(b). Offerors are cautioned that any pages that exceed the page limitations shall not be read but shall be removed and either retained in the contract file without being considered in the evaluation, or sent back to the offeror.

Proposal Submission Instructions:

(c). Offerors are responsible for submitting proposals, and any revisions, and modifications, so as to reach the designated Government office by the date and time specified in the solicitation. Proposals will be accepted electronically, mailed, or hand-delivered in accordance with FAR Part 15.208, Submission, Modification, Revision, and Withdrawal of Proposals. Proposals may be emailed to Mr. Robert Mosley at robert.mosley.3@us.af.mil, or delivered to the address listed in block 9 of the SF33. Proposal receipt time shall be no later than 2:00 P.M. Central Standard Time on the date provided on page one of the solicitation.

Due to equipment concerns, facsimiles will not be accepted.

mailto:robert.mosley.3@us.af.mil

(d). Offerors are cautioned that name of installation has visitor control procedures requiring individuals not affiliated with the installation to obtain a visitor pass prior to entrance. Some delay should be anticipated when hand-delivering proposal packages. Offerors should allow for sufficient time to obtain a visitor pass and arrive at the specified office PRIOR to the time specified for receipt of proposals.

(e). E-mailed proposals are subject to electronic firewall issues. Proposals packages greater than 8 MG and certain file formats have the potential of not passing through the firewall. If submitting a proposal via email, please call 931-454-6706 or separately e-mail robert.mosley.3@us.af.mil to verify that your proposal was received. E-mailed proposals will not be reviewed for solicitation conformance or evaluation criteria prior to the due date and time listed on the solicitation. Incomplete packages have the potential of being determined noncompliant.

(f). Offerors who choose to mail proposals shall address packages to:

AFTC/PZI (Arnold) ATTN: Mr. Robert Mosley 100 Kindel Dr, Ste A332 Arnold AFB TN 37389

8. Notice of Use of Non-Government Advisors: Offerors are advised that technical data submitted to the Government in response to this solicitation may be released to non-government advisors for review and analysis. The nongovernment advisor support will be provided by: National Aerospace Solutions (NAS).

(a). Offerors shall provide the following statement unless objecting to disclosure of technical to NAS:

“I understand technical data submitted to the government in response to this solicitation may be released to non-government advisors. I consent to release of any proprietary, confidential, or privileged commercial or financial data provided by the firm(s) named below in response to this solicitation, to non-government advisors for review and analysis:

Firm:

Name (individual authorized to commit firm):

Title:

Date of Execution:

(b). Offerors objecting to disclosure of information identified above shall provide the following: A complete list of objectionable areas along with a detailed statement of the basis for the objection. The detailed statement shall identify the specific portions of the proposal the offeror objects to regarding disclosure to non-government advisors.

(c). Objections shall be provided in writing to the contracting officer within 10 days of RFP issuance.

B. Volume I, Completed RFP (Submit one copy)

1. General: Volume I, completed RFP shall consist of the completed and signed RFP, to include any amendments issued, with a cover letter delineating any exceptions taken to the RFP terms and conditions with accompanying rationale. However, offerors are cautioned that any noncompliance with the terms and conditions of the RFP may cause their proposal to be determined not eligible for award. Offerors shall ensure that all clauses and provisions that require “fill-in” information are appropriately completed, including the proposed prices associated with the contract line items in the Schedule of the RFP.

(a). Exceptions shall be provided in the format below.

• Solicitation Document: Identify what aspect of the solicitation is addressed, i.e. CLIN Structure, Specification, Section L; Section M, etc.

• Page/Paragraph: Identify the applicable page and paragraph number.

• Requirement/Portion: Identify the requirement or portion to which the exception is taken.

• Rationale & Impact: Describe the rationale and impact of the exception.

(b). Note: Exceptions to the RFP may make an offeror’s proposal unacceptable for award.

2. Complete blocks 14 (if applicable), 15, 16, 17, and 18 of the solicitation document, SF33, Section A. In submitting a completed SF33, the offeror accedes to contract terms and conditions as written in Sections A through K, with amendments (unless excepted in writing). These sections constitute the model contract.

3. Representations and Certifications: In accordance with FAR 52.204-7, System for Award Management (SAM), registration online representation and certification is required. Offerors must be registered in SAM prior to contract award. If a business concern is not registered in SAM, complete the necessary fill-ins and certifications in Sections I through K and submit these sections with the offeror’s proposal package. SAM can be accessed via https://www.sam.gov.The offeror shall submit one copy of the System for Award Management Entity Overview, Representations and Certifications, and Active Exclusions (available at www.sam.gov).

C. Volume II, Written Technical Proposal (Submit One Copy)

1. General: The written technical proposal shall be clear, concise, and include all the information required by this provision in sufficient detail for effective evaluation. The proposal should not simply rephrase or restate the Government’s requirements, but rather shall provide convincing rationale to address how the offeror intends to meet these requirements. Offerors shall assume the Government has no prior knowledge of their capabilities, work processes, facilities, and experience and will base its evaluation on the information presented in the offeror’s technical proposal.

2. Format and Specific Content: The following information shall be provided in the written technical proposal and will be evaluated to assess technical acceptability in accordance with Section M-900, Evaluation Basis for Award. The written technical proposal shall address each of the following subfactors to describe the offeror’s proposed approach to performing the requirements set forth in the RFP specifications and drawings:

a. Factor 1: Technical Narrative.

(i) Subfactor One: Technical Approach. Not to exceed 20 pages; page count does not include graphs, charts, or other pictorials to demonstrate technical approach. The Government will evaluate the offeror’s technical approach and its ability to accomplish the Government’s requirements as set forth in the Specification.

(1) The Government shall evaluate the offeror’s proposed materials to verify the materials meet the specifications and supplied drawings.

(2) The Government shall evaluate the offeror’s material properties to verify the properties are in accordance with the Request for Proposal.

(3) The Government shall evaluate the offeror’s defined inspections to verify that the inspections meet the Request for Proposal.

(ii) Subfactor Two: Proposed Schedule. Not to exceed 2 pages.

(1). The Government shall evaluate the offeror’s proposed schedule to determine if the delivery requirement (180 Calendar Days after receipt of order) are met. The offeror shall address:

(2). The proposal schedule shall show the coordination for the material certifications.

(3). Shipping dates, start and finish from the Contractor’s location to the Government facility.

D. Volume III, Price Proposal (Submit one copy):

1. Factor 2 (Price Factor): The Price Factor will not be scored or rated. The offeror’s proposal will be evaluated in accordance with FAR 15.404-1. An offeror’s proposed prices will be determined by multiplying the quantities identified in Section B (page 2) of the RFP by the proposed unit price for each Contract Line Item Number (CLIN) to confirm the extended amount for each CLIN.

(a). Complete blocks 14 (if applicable), 15, 16, 17, and 18 of the solicitation document, SF33, Section A.

In submitting a completed SF33, the offeror accedes to contract terms and conditions as written in Sections A through K, with amendments. These sections constitute the model contract. Refer to paragraph three of this instruction if identifying an exception to any term, condition or requirement of the solicitation.

(i). The Government requires offerors to maintain prices for 60 calendar days after the due date/time indicated in block 9 of the SF33, Section A.

(ii). Insert the proposed unit prices in the RFP Section B for each Contract Line Item Number (CLIN). The extended amount must equal the whole dollar unit multiplied by the number of units.

ATTACHMENT 2

LOWEST PRICE TECHNICALLY ACCEPTABLE (LPTA) PROCESS

M-900. EVALUATION BASIS FOR AWARD

I. Basis for Contract Award

A. Source Selection Methodology: This acquisition will utilize the Lowest Price…