FA8672-12-R-0168_Amend_0002.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

1. CONTRACT ID CODE

See Block #2

PAGE OF PAGES

2. AMENDMENT/MODIFICATION NO.

3. EFFECTIVE DATE

19 OCT 2012

4. REQUISITION/PURCHASE REQ.NO.

5. PROJECT NO. (If applicable)

6. ISSUED BY AFLCMC/EBMK/EBM CODE FA8672 7. ADMINISTERED BY (If other than Item 6) CODE

AF LIFE CYCLE MANAGEMENT CENTER

AFLCMC/EBMK

105 WEST D AVE, BLDG 11

EGLIN AFB, FL 32542

WESLEY D. MASON 882-8004

wesley.mason2@eglin.af.mil

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code) (X) 9A. AMENDMENT OF SOLICITATION NO.

FA8672-12-R-0168

X 9B. DATED (SEE ITEM 11)

14 SEP 2012

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 13)

CODE FACILITY CODE

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

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

(a) By completing Items 8 and 15, and returning 0 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER.

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

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATION OF CONTRACTS/ORDERS,

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

(X )

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

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

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

D. OTHER (Specify type of modification and authority)

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

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

SEE SCHEDULE

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

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

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

15B. CONTRACTOR/OFFEROR

15C. DATE SIGNED 16B. UNITED STATES OF AMERICA

16C. DATE SIGNED

(Signature of person authorized to sign)

BY________________________________________

(Signature of Contracting Officer)

NSN 7540-01-152-8070 30-105 STANDARD FORM 30 (REV.10-83)

PREVIOUS EDITION UNUSABLE Prescribed by GSA ConWrite Version 6.13.3 FAR (48 CFR) 53.243 Created 19 Oct 2012 9:46 AM

SCHEDULE OF CHANGES

FA8672-12-R-0168 0002

CONTINUATION OF BLOCK 14 DESCRIPTION OF AMENDMENT/MODIFICATION

The purpose of this amendment is to incorporate the following changes to the JMM BRU Request for Proposal posted to FedBizOpps on 14 Sep 12.

Description of Changes:

Section L

Page L-2, General Instructions, Paragraph 1 (B), is revised. See new Section L attached.

Page L-3, General Instructions, Paragraph 1 (H), is revised. See new Section L attached.

Page L-4, General Instructions, Paragraph 1 (K), is revised. See new Section L attached.

Page L-4, Table 1.1 - JMM BRU Proposal Breakdown is revised. See new Section L attached.

Page L-10, Book B - Technology Readiness Assessment & Maturation Plan, Paragraph 2 (B)(2)(a), is revised. See new Section L attached.

__________________________End of Continuation Page Block 14____________________________

PART IV – REPRESENTATIONS AND INSTRUCTIONS

SECTION L – INSTRUCTIONS, CONDITIONS AND NOTICES TO OFFERORS

SECTION L FA8672-12-R-0168

PAGE L - 1 of 17

I. NOTICE: The following solicitation provisions pertinent to this section are hereby incorporated by reference:

A. FEDERAL ACQUISITION REGULATION SOLICITATION PROVISIONS

52.211-2 AVAILABILITY OF SPECIFICATIONS, STANDARDS, AND DATA ITEM

DESCRIPTIONS LISTED IN THE ACQUISITION STREAMLINING AND

STANDARDIZATION INFORMATION SYSTEM (ASSIST) (JAN 2006)

52.211-14 NOTICE OF PRIORITY RATING FOR NATIONAL DEFENSE, EMERGENCY

PREPAREDNESS, AND ENERGY PROGRAM USE (APR 2008)

Contracting Officer indicates DX or DO Rated Order: 'DOA5'

52.215-1 INSTRUCTIONS TO OFFERORS--COMPETITIVE ACQUISITION (JAN 2004)

52.216-1 TYPE OF CONTRACT (APR 1984)

Types of contracts are: ‘Firm-Fixed-Price’ and ’Fixed-Price-Incentive (Firm) Target’

52.222-24 PREAWARD ON-SITE EQUAL OPPORTUNITY COMPLIANCE EVALUATION (FEB

1999)

52.232-13 NOTICE OF PROGRESS PAYMENTS (APR 1984)

52.232-38 SUBMISSION OF ELECTRONIC FUNDS TRANSFER INFORMATION WITH OFFER

(MAY 1999)

52.233-2 SERVICE OF PROTEST (SEP 2006)

Para (a) Official or location is AFLCMC/EBMK Attn: Catherine Gray 102 West D Avenue, Bldg 11 Eglin AFB, FL 32542-6810'

52.247-45 F.O.B. ORIGIN AND/OR F.O.B. DESTINATION EVALUATION (APR 1984)

B. DEFENSE FEDERAL ACQUISITION REGULATION SUPPLEMENT SOLICITATION PROVISIONS

252.211-7001 AVAILABILITY OF SPECIFICATIONS, STANDARDS, AND DATA ITEM

DESCRIPTIONS NOT LISTED IN THE ACQUISITION STREAMLINING AND

STANDARDIZATION INFORMATION SYSTEM (ASSIST), AND PLANS, DRAWINGS,

AND OTHER PERTINENT DOCUMENTS (MAY 2006)

Activity name is AFLCMC/EBMK Activity address is ‘Attn: Catherine Gray 102 West D Avenue, Bldg 11 Eglin AFB, FL 32542-6810'

252.227-7028 TECHNICAL DATA OR COMPUTER SOFTWARE PREVIOUSLY DELIVERED TO THE

GOVERNMENT (JUN 1995)

252.247-7026 EVALUATION PREFERENCE FOR USE OF DOMESTIC SHIPYARDS—

APPLICABLE TO ACQUISITION OF CARRIAGE BY VESSEL FOR DOD CARGO IN

THE COASTWISE OR NONCONTIGUOUS TRADE (NOV 2008)

C. AIR FORCE FEDERAL ACQUISITION REGULATION SUPPLEMENT SOLICITATION PROVISIONS

5352.215-9000 FACILITY CLEARANCE (MAY 1996)

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

PAGE L - 2 of 17

A. FEDERAL ACQUISITION REGULATION SOLICITATION PROVISIONS IN FULL TEXT

52.252-01 SOLICITATION PROVISIONS INCORPORATED BY REFERENCE (FEB 1998)

This solicitation incorporates one or more solicitation provisions by reference, with the same force and effect as if they were given in full text. Upon request, the Procuring Contracting Officer (PCO) will make their full text available. The Offeror is cautioned that the listed provisions may include blocks that must be completed by the Offeror and submitted with its quotation or offer. In lieu of submitting the full text of those provisions, the Offeror may identify the provision by paragraph identifier and provide the appropriate information with its quotation or offer. Also, the full text of a solicitation provision may be accessed electronically at this/these address(es): http://farsite.hill.af.mil/

52.252-05 AUTHORIZED DEVIATIONS IN PROVISIONS (APR 1984)

(a) The use in this solicitation of any Federal Acquisition Regulation (48 CFR Chapter 1) provision with an authorized deviation is indicated by the addition of "(DEVIATION)" after the date of the provision.

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

B. OTHER SOLICITATION PROVISIONS IN FULL TEXT

EGLIN-L001 INSTRUCTIONS TO OFFERORS AND PREPARATION OF PROPOSALS (JUL 2009)

1. GENERAL INSTRUCTIONS:

(A) This section provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. The Offeror's proposal must include all data and information requested and must be submitted in accordance with these instructions. The Offeror's proposal shall be compliant with Section L and shall meet all requirements as stated in the System Performance Specification (SPS), Performance Environments Criteria (PEC), Systems Engineering Plan (SEP), Statement of Work (SOW), and Model Contract. Non-conformance with the instructions will result in being found non-responsive.

(B) The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. 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 that the Government has no prior knowledge of their facilities and experience. The Government will not assume that an Offeror possesses any capability unless specifically addressed in the proposal. The Government will base its evaluation on only the information presented in the Offeror's written proposal. The Government will not assume the Offeror will do anything that is not expressly stated in their written proposal. Alternate proposals will not be accepted for this acquisition.

(C) Point of Contact: The Procuring Contracting Officer (PCO), Ms. Catherine Gray, (850) 883-2546 is the sole point of contact for this acquisition. Address any questions or concerns you may have to the PCO. Written requests for clarification may be sent to the PCO at the address located in Section A, Block 8 (SF33) of the model contract/solicitation. Any requests for clarifications should be submitted within ten (10) work days of the Request for Proposal (RFP) release. Answers to clarifications will be posted to the Federal Business Opportunities (FedBizOpps) or issued via an RFP amendment. In http://farsite.hill.af.mil/

PAGE L - 3 of 17 the event of any conflict between the response to clarifications and the RFP, the RFP (including any amendments) shall take precedence.

(D) The PCO will promptly notify Offerors of any decision to exclude them from the competitive range, whereupon they may request and receive a debriefing in accordance with FAR 15.505.

The PCO will notify unsuccessful Offerors in the competitive range of the source selection decision in accordance with FAR 15.506. Upon such notification, unsuccessful Offerors may request and receive a debriefing. Offerors desiring debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

(E) Discrepancies: If an Offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the Offeror shall immediately notify the PCO in writing with supporting rationale.

(F) Offerors shall provide their proposals in both hard copy and electronic format (compatible with Microsoft Office Edition 2007 Professional – Word, Excel, and PowerPoint; Microsoft Office Edition 2007 for Project and Dynamic Object Oriented Requirements System (DOORS)). DOORS is required to support the System Performance Verification Plan (SPVP) requirements flowdown. The electronic copies of the proposal shall be submitted on Virus-free CD-ROM (no read-write) only. The Offeror shall submit volumes (1 set) in electronic format. Each volume shall be in a different directory on a Compact Disc (CD). The proposal shall not contain compressed or password protected files. On each CD-ROM, indicate the proposal title, solicitation number, Offeror name, and volume number and title contained in the CD-ROM. In cases where the electronic media differs from the hard copy, the hard copy takes precedence. The content and page size of electronic copies must be identical to the hard copies. Use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any.

(G) It is the Offeror’s responsibility to ensure the proposal’s completeness. The proposal shall not merely offer to conduct an investigation or perform work in accordance with (IAW) the furnished model documents, but shall address the actual method of investigation or work to be performed; as well as the integrated traceability among the relative documents such as but not limited to the SPS, PEC, SOW, Systems Engineering Management Plan (SEMP), Integrated Master Plan (IMP), Integrated Master Schedule (IMS), Basis Of Estimates (BOEs), Contractor Work Breakdown Schedule (CWBS), and model contract.

(H) The supporting technical data in Book B shall be included and submitted on CD/DVDs (no paper copies required). The supporting technical data shall clearly substantiate an offeror’s assertion they possess the necessary level of maturation of the performance capability being assessed. The Government is not obligated to review all of the supporting technical data submitted. The Government is only obligated to review the supporting technical data specifically identified and referenced by the Offeror to substantiate their current Technology Readiness Level (TRL).

(I) During the source selection, exchanges with industry may include clarification, communications and discussions as defined in FAR 15.306 and AFFARS Mandatory Procedure Source Selection 5315.3 paragraph 3.4. All such exchanges with industry will be documented in the source selection file and conducted with appropriate process and controls in place. Upon receipt of proposal volumes, a competitive range determination will be made, thus allowing for discussion, if necessary, as defined by FAR 15.306(d).

(J) The Government intends to evaluate proposals and award a contract without discussions with Offerors (except clarifications as described in FAR 15.306(a)). Therefore, the Offeror’s initial proposal should contain the Offeror’s best terms from a cost or price and technical standpoint. The Government reserves the right to conduct discussions if the Contracting Officer later determines them to be necessary.

PAGE L - 4 of 17

(K) Document quantity and page limits: The proposal shall be submitted in two (2) volumes with Volume 1 and 2 divided into books as delineated in Table 1.1 below. The Offeror shall provide hard and soft copies of each volume in accordance with Table 1.1 below. Each volume shall be delivered in a separate binder/disc (CD/DVD). Pages in each volume shall be numbered sequentially (except the supporting technical data which is understood to be separate documents that are individually numbered).

Offerors must cross-reference and clearly explain the intended significance of information contained in the supporting technical data, tables, figures, pictures or other non-narrative data. Any classified portions shall be cross-referenced in the unclassified volume, segregated and included on separate pages/discs in a classified appendix to the volume marked appropriately. The Government shall have the right to load data on a secure server within an approved source selection facility. In the event ambiguities or conflicts exist between the written description and/or approach and the numeric data or figures, the numeric data or figures shall take precedence.

Table 1.1 – JMM BRU Proposal Breakdown

Volume Title Paper /

Electronic Pages*

1 Cost / Price / Proposal /Contract Data

Book A – Model Contract 6 / 2 As Req’d

Book B – Cost/Price Proposal 6 / 2 50

2 Mission Capability Documentation

Book A – Design Concept 6 / 2 75

Book B – Technical Readiness Assessment & Maturation Plan Supporting Technical Data

6 / 2 0 / 2

As Req’d

Book C – Systems Engineering Management Plan (SEMP) 6 / 2 As Req’d

Book D – Plans and Schedules (IMP/IMS) 6 / 2 As Req’d

Book E – System Performance Verification Plan (SPVP) 6 / 2 250

Book F – Cross Reference Matrix 6 / 2 As Req’d

Book G – Small Business Subcontracting Plan 6 / 2 As Req’d

*Not to Exceed

Page Limitations: The Government will not keep any pages in excess of the limit. Those pages in excess of the limit will be removed starting from the back of the proposal volume and will be destroyed by the PCO to ensure that they are not evaluated. The Offeror will be notified prior to the destruction of excess pages. If discussions are necessary, Evaluation Notices (ENs) will be forwarded and page limits will be placed on any responses. The specific page limits for responses to ENs will be identified in the letter forwarding ENs to an Offeror. If ENs are required, EN page limits will not be part of the original proposal page limitations.

(L) Page size and format: A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 x 11 inches, not including foldouts. Pages shall be single spaced. Except for the reproduced sections of the solicitation document (Section A-K), the text size shall be no less than 12 point. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1 inch margins on the top and bottom and 3/4 inch side margins. Pages shall be numbered sequentially by volume (and subfactor for Mission Capability & Non-

PAGE L - 5 of 17

Mandatory Technical Requirements Volume, Vol. 2). If Evaluation Notices are submitted, then these page format restrictions shall apply to the responses. These limitations shall apply to both electronic and hard copies of proposals submitted.

Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible and shall not exceed 11 x 17 inches in size. Foldout pages shall fold entirely within the volume and each 8.5 x 11 surface of a foldout shall be counted as a separate page (i.e. one 11 x 17 foldout equal’s 2 proposal pages). Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics, not for pages of text. For pre-existing documentation, text in tables, charts, graphs and figures, text shall be no smaller than 8 point when included in proposal. For other tables, text shall be no smaller than 10 point. These limitations shall apply to both electronic and hard copies of proposals submitted.

(M) Binding and Labeling: Each volume of the proposal should be separately bound in a three-ring loose leaf binder which shall permit the volume to lie flat when open. Staples shall not be used.

A cover sheet should be bound in each book, clearly marked as to volume number, title, copy number, solicitation identification and the Offeror's name. Where applicable, subfactors will be tabbed within the volume to allow separation and standalone review. The same identifying data should be placed on the spine of each binder. All unclassified document binders shall have a color other than red or other applicable security designation colors. Be sure to apply all appropriate markings including those prescribed in accordance with FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information. Attachments not included in the Volume page count (per Table 1.1) shall be separately bound from the applicable volumes.

(N) Offerors shall use the word “shall” as defined in FAR 2.101 to denote contractor contractual obligations in any documents prepared by the Offeror for incorporation into the contract. The Government will review Offeror asserted proprietary markings IAW DFARS 252.227-7017. Documents to be incorporated physically as attachments under Section J of the contract shall include a footer notation on the bottom right margin identifying the contract number, attachment number and total attachment pages (see example below):

RFP No: FA8672-12-R-0168 Attachment XX Page X of X

(O) The contract types specified in the RFP are mandatory. Alternative proposals will not be accepted.

(P) Glossary of Abbreviations and Acronyms: Each book shall contain a glossary of all abbreviations and acronyms used, with an explanation for each. Glossaries do not count against the page limitations for their respective books.

(Q) Adequate Price Competition. The PCO has determined there is a high probability of adequate price competition in this acquisition. Upon examination of the initial offers, the PCO will review this determination and if, in the PCO’s opinion, adequate price competition exists, no additional cost information will be requested, and certifications under FAR 15.406-2 will not be required. However, if at any time during this competition, the PCO determines that adequate price competition does not exist;

Offerors may be required to submit information to the extent necessary for the PCO to determine the reasonableness of the Cost/Price.

PAGE L - 6 of 17

(R) Proposal Delivery: Proposals are due no later than 14 Nov 2012, 1500 CST. Proposals shall be hand delivered or mailed to address identified below. The Offeror shall contact the PCO to establish a date for delivery to ensure personnel are available to receive the proposal.

AFLCMC/EBMK

Attn: Ms Catherine Gray, Procuring Contracting Officer Source Selection Facility 210 West D Avenue, Building 373 Eglin AFB, FL 32542 Comm: (850) 883-2546

2. SPECIFIC VOLUME INFORMATION:

(A) Volume 1 – Model Contract & Cost/Price Proposal

(1) Book A - Model Contract.

The purpose of this book is to provide information to the Government for preparing the contract document and supporting file. The Offeror’s proposal shall include a signed copy of the model contract and Sections A through K. This includes:

(a) All sections. Complete any model contract fill-in blanks.

(b) Section A - Solicitation/Contract Form. Completion of blocks 12-16 and signature and date for blocks 17 and 18 of the Standard Form (SF) 33. Signature by the Offeror on the SF 33 constitutes an offer, which the Government may accept. The “original” copy should be clearly marked under separate cover and should be provided without any punched holes. Any proposal updates, including Final Proposal Revision (FPR), must also follow these instructions. NOTE: The Offeror’s proposal validity period must extend to 300 calendar days after the proposal due date.

(c) Section B - Supplies or Services and Costs/Prices. For the basic Technology Development (TD) (CLIN 0001), Engineering and Manufacturing Development (EMD) JMM BRU Development (CLIN 0002), EMD JMM BRU F-35 Flight Test (CLIN 0003), JMM BRU Production Lot 1 (CLIN 0004) and Production Lot 2 (CLIN 0005), the Offeror shall fill-in the target price. For the JMM BRU Technical Data Package (TDP) with Government Purpose Rights (CLIN 0006), the Offeror shall fill-in the Firm Fixed Price (FFP). If the Offeror elects not to propose a FFP for the JMM BRU TDP with Government Purpose Rights (CLIN 0006), the Government will utilize an evaluation amount of $108M as the TDP value in the Total Evaluated Price (TEP) calculation. With the exception of CLIN 0006, Offerors must propose a price for all CLINs. Additionally, for TD, EMD JMM BRU Development and EMD JMM BRU F-35 Flight Test, the Offeror shall fill-in Section B clause B030 and for production, the production pricing tables located under Section L, Attachments 2-3. Whenever an Offeror proposes a contract dollar amount it is presumed to be at the “price” level, i.e., the total contract dollar amount. This amount includes all charges, direct or indirect, labor, material, overheads, administrative fees, cost of money, etc., and fee or profit. Dollar amounts and time-phased estimates at summary levels shall be presented in then-year dollars (TY$).

(d) Section H - Special Contract Requirements

(i) EGLIN-H006. Complete paragraph (f) under clause EGLIN- H006, Associate Contractor Agreements (ACAs) (add additional ACAs as required);

(ii) EGLIN-H008. For the option exercise period, the Offeror shall fill-in the exercise period (no less than a 180-day window for EMD JMM BRU Development, 180-day

PAGE L - 7 of 17 window for EMD JMM BRU F-35 Flight Test, 180-day window for JMM BRU Production Lot 1 and a 180-day window for JMM BRU Production Lot 2). NOTE: If the option exercise period begins in 3Q or 4Q of the fiscal (FY), the option exercise period must extend to 31 Jan of the following FY. For lead time, the Offeror shall fill-in a lead time not greater than (NGT) 15 months. For delivery time, the Offeror shall fill-in a delivery time NGT 12 months.

(e) Section I – Contract Clauses

(i) FAR clause 52.222-26 (Equal Opportunity). In accordance with FAR 52.222-24, the Offeror shall provide the below information for known first-tier subcontractors with anticipated subcontracts of $10 million (TY$) or more:

1.) Name of firm.

2.) Address of firm (including divisions if applicable).

3.) Point of contact.

4.) Date of last survey/clearance (if applicable).

(ii) FAR 52.223-03. The Offeror shall complete the fill-ins to identify any hazardous materials for inclusion in the clause.

(iii) DFARS 252.223-7007. The Offeror shall complete the fill-ins to provide the nomenclature, national stock number and sensitivity category.

(iv) DFARS 252.239-7016. The Offeror shall complete the fill-ins to identify the location where secure information and systems will be utilized, where a list of approved equipment may be obtained from, and location(s) of any telecommunications security equipment, device, technique, or service required for interoperability.

(f) Section J – Attachments.

(i) Instructions for filling out the JMM BRU production unit pricing tables (see Section L, Attachments 2-3). The Offeror will use TY$ for all unit prices provided in the JMM BRU production pricing tables for JMM BRU Production Lots 1 and 2. The Offeror shall fill-in the tables (Target Cost, Target Profit, Target Price, and Ceiling Price). For example, not to be included in the labor or material amounts are profit, depreciation, negotiated fixed-price subcontracts not subject to Economic Price Adjustment (EPA).

(g) Attachment 7 - Government Furnished Property (GFP)/Facilities (GFF)/Equipment (GFE)/Information (GFI). Offerors shall identify any Government furnished resources, data, or support required and the period the GFP/GFF/GFE/GFI is needed. The Offeror shall submit their request IAW DFARS PGI 245.201-71 titled “Government Furnished Property attachments to solicitations and awards”. If the Offeror proposes use of facilities under a Government facilities contract, the usage will be limited IAW the terms and conditions of the facilities contract, inclusive of any negotiated phase-out program. The Offeror shall identify by brief description all Government-owned facilities, industrial equipment, or special tooling intended to be used in the performance of the contract, the value thereof, the facilities contract number, rental provisions, property management plan, and other relevant information. A statement from the cognizant Government PCO shall also be included in the proposal indicating that such Government-owned property will be available for the timely completion of performance under an ensuing contract on a non-interference basis, whether or not the proposal is based on “No Charge for Use”, and whether or not the Offeror could perform the work in the event that the use of such facilities is not authorized or the facilities contract is phased out.

(h) Section K - Complete the representations, certifications and other statements identified.

PAGE L - 8 of 17

(i) Exceptions to Terms and Conditions - Exceptions taken to the terms and conditions of the model contract, to any of its formal attachments, or to other parts of the solicitation shall be identified. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. The Offeror shall provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, cost and specific requirements of the solicitation. Failure to comply with the terms and conditions of the solicitation may result in the Offeror being removed from consideration for award.

(2) Book B – Cost/Price Proposal

Since this is a competitive acquisition with adequate price competition anticipated, the cost documentation shall not be certified IAW FAR 15.406-2. Should adequate price competition not exist after receipt of proposals, the provisions of FAR 15.403-4 shall apply.

(a) Part 1: TD and EMD Spend Plan. Provide a separate TD, EMD JMM BRU Development and EMD JMM BRU F-35 Flight Test proposed monthly spend plan by Government fiscal year (GFY). The spend plan shall be completed at target cost, target profit, target price, open commitments and termination liability. (Section L, Attachment 1). Provide in electronic format as well as hardcopy.

(b) Part 2: Production Price.

(i) The Offeror’s proposal for production shall follow the criteria outlined in Section H contract clause EGLIN-H008. Pricing and Exercise of JMM BRU Production Option CLINS shall be submitted in Then Year dollars (TY$).

(ii) Description of what to include in calculating the unit price for JMM BRU Production Lots 1 and 2 is as follows: The unit price for the JMM BRU is the composite of recurring and non-recurring production costs including all fully burdened contractor production costs incurred in the manufacture of a usable end-item to satisfy the requirements contained under the JMM BRU SOW (see Section J, Attachment 1). Additionally, unit price for JMM BRU shall include the Offeror’s costs associated with the prime mission equipment (hardware and software), systems engineering, program management, Offeror’s transportation costs up through initial delivery location, special tooling/test equipment (which shall not be amortized), peculiar support equipment (PSE), Offeror initiated engineering change proposals and verification/validation (IAW EGLIN-H011). Costs that are specifically excluded from the unit price are: modifications to Government aircraft and non-Offeror unique support equipment, Government directed data; Government initiated engineering change orders and associated verification.

(iii) In accordance with the unit price definition in paragraph (ii) above, the Offeror shall include the price of the JMM BRU test assets, Offeror test support and data analysis (to include engineering analysis that may be required to obtain approval to conduct the test on Government test ranges). Additionally if the Offeror makes changes beyond those being verified under contract clause EGLIN-H011, the Offeror shall include all costs to verify the change in their costs.

(iv) Instructions for filling–out the JMM BRU production unit pricing tables (Section L Attachments 2-3). The Offeror shall use TY$ for all unit prices provided in the JMM BRU Production Pricing Tables for lots 1 and 2. The Offeror shall fill-in the tables (Target Cost, Target Profit, Target Price and Ceiling Price). The Offeror shall propose the entire quantity band which is defined as +/- 20% from the most probable quantity. The minimum to maximum quantity unit price(s) can be a single price for the entire quantity band (ex: propose a single unit price for all quantities that fall within the +/- 20% band) or the Offeror can provide multiple unit price(s) for the +/- 20% band.

Table 2.1 – JMM BRU Most Probable Production Quantities

PAGE L - 9 of 17

Assets

FY18 FY19 Total Lot 1 Lot 2

JMM BRU 40 90 130

Containers 40 90 130

(v) The Offeror shall provide a narrative for the JMM BRU Production Lots 1 and 2 at the quantity listed in Table 2.1 above. The narrative shall include the applicable ground rules and assumptions, the data sources and describe the estimating approach and methodology. The Offeror shall identify the analogous programs used to support their data and identify the adjustments applied to the data based on differences in complexities. If the described narrative is the same for Production Lots 1 and 2, then one narrative is acceptable and should be annotated in the narrative. The narrative shall include a description of any potential uncertainty.

(B) Volume 2 – Mission Capability Documentation

Volume 2 Cover Letter – The Offeror shall provide a signed letter (Section L Attachment 8) stating the Offeror’s design shall meet all system performance requirements as stated in the JMM BRU System Performance Specification (SPS) and Performance Environments Criteria (PEC) without exception, qualification, clarification and/or discussion.

(1) Book A – Design Concept

The Offeror shall provide their JMM BRU Design Concept that ensures compliance with the requirements defined in the referenced System Performance Specification and Performance Environments Criteria, and referenced documents in a document using Microsoft Word 2007 format. The document pages shall be numbered, and may be in black and white or in color. Book A, as a minimum, shall include the following elements:

(a) Design Concept Description. The Offeror shall describe: the JMM BRU internal/external interfaces and subsystems listed in Table 2.2; the subsystem development strategy that ensures compliance with the requirements of the SPS and PEC; the JMM BRU carriage integration and how the integrated carriage system ensures compliance with the SPS and PEC requirements.

Table 2.2. JMM BRU Key Subsystems and Interfaces

1 JMM BRU Primary Structure and Outer Moldline

2 Power Distribution Subsystem

3 System Control Electronics (SCE)

4 Stored Energy System (SES)

5 Suspension & Release Assemblies (S&RAs)

6 System Internal and External Interfaces (Physical, Electrical and Logical)

PAGE L - 10 of 17

(2) Book B – Technology Readiness Assessment & Maturation Plan

The Offeror’s Book B shall assess the current state of Technology Readiness of the subsystems and interface designs that are to be used in the JMM BRU system design concept. Book B shall also identify the technology maturation tasks to be accomplished to ensure each of the subsystems and interfaces achieve technology (system and subsystem) readiness level (TRL) of 6 at JMM BRU Preliminary Design Review (PDR) and TRL 8 at JMM BRU System Verification Review (SVR). Book B shall be in Microsoft Word 2007 format. Book B pages shall be numbered, and may be in black and white or in color. Book B shall, as a minimum, include the following elements:

(a) Technology Readiness Assessments (TRA). The Offeror’s TRA shall include readiness level definitions identified in paragraph 2.5 of the TRA Guidance dated April 2011.

TRAs shall be provided for the JMM BRU interfaces and subsystems identified in Table 2.2. Each assessment shall include supporting technical data such as records of tests, analyses, technical papers, reports, or presentations that substantiate the current level of maturation of the performance capability being assessed. Supporting technical data must be accurately referenced by specific document, page, and paragraph number allowing the Government to easily evaluate the Offeror’s assertion. Use of hyperlinks to the specific referenced locations in the Book B Supporting Technical Data is authorized.

The assessments shall identify the component, assembly, subsystem, or system design levels and associated employment environments for which each of the subsystem’s performance capabilities are being evaluated.

(b) Technology Maturation Plan. The Offeror shall identify the performance capability maturation tasks for each JMM BRU interface and subsystems identified in Table 2.2. The subsystem maturation tasks shall identify the Offeror’s plan to mature the current performance capabilities to the levels necessary to achieve TRL 6 (system and subsystem) at JMM BRU PDR and TRL 8 at JMM BRU SVR. The capability maturation tasks shall identify the component, assembly, subsystem, or system design levels and associated employment environments for which each of the subsystem’s performance capabilities are being evaluated.

(3) Book C – Systems Engineering Management Plan.

The Offeror shall provide their JMM BRU Systems Engineering Management Plan (SEMP) in Book C of this proposal. The Offeror shall develop and submit a SEMP using the Section L Attachment 4 outline and referencing the detailed content of the Government’s Systems Engineering Plan (SEP). The SEMP shall specifically describe the Offeror’s Systems Engineering processes, Systems Engineering organization and techniques as they will be applied to the JMM BRU Program. The Offeror shall include a Risk Assessment Matrix of all the risks associated with the JMM BRU Program and associated plans.

The risk assessment shall include risk mitigation plans for each identified risk substantiated by the BOEs.

The SEMP submitted with this proposal will include the following two appendices: Software Development Plan and Producibility Plan with detailed content that demonstrates the Offeror’s clear understanding of the Government’s requirements. All other appendices identified in the Section L Attachment 4 outline will be accomplished after contract award in accordance with the SOW and CDRLs.

Book C shall be in Microsoft Word 2007 format. Book C pages shall be numbered, and may be in black and white or in color. The Book C SEMP shall include the following appendices:

(a) Software Development Plan. The Offeror shall describe the Systems Engineering, Software Engineering, Integrated Product and Process Development, and Supplier Sourcing capability and processes for the organization and/or principle sub-contractors and/or critical sub-contractors and/or team members who are responsible for software development. As part of the Software Development Plan, the Offerors shall document that their software development capabilities and processes that actually are being used on the JMM BRU Program have been appraised at Level 3 of the Capability Maturity Model Integration (CMMI) by a Carnegie Mellon Software Engineering Institute (SEI)

PAGE L - 11 of 17 authorized Lead Appraiser. The Offeror shall provide a mapping (e.g., matrix, completed Practice Implementation Indicator Descriptions, etc.) showing how and where company standards and practices map to SEI CMMI for Development Version 1.2 practices, or the equivalent. Similar descriptions shall be supplied for all principal and critical sub-contractors related to the Offeror’s proposal that will perform software development. The Software Development Plan shall address the following areas:

(i) Identify the agency/company that performed the CMMI evaluation(s) and provide a point of contact’s name, telephone number, and e-mail address.

(ii) Identify the date that the evaluation was obtained and the appraisal level.

(iii) Identify the projects being performed at the level of appraisal and demonstrate the degree of relevancy that those projects have to those of the solicitation.

(iv) Identify any Capability Evaluations performed on your organization in sufficient detail to allow the Government to reuse them if it considers that appropriate.

(v) If the evaluation(s) is more than 2 years old, describe what steps you have taken to ensure that you have stayed current with the processes and procedures that are required to maintain the CMMI level or to advance to a higher level.

(vi) Detail the quality assurance processes/procedures and the methodology to be used for identifying and tracking software defects.

(vii) Describe the company’s experience in tracking critical software items.

(viii) Describe the degree to which the Offeror’s engineering management and development processes and capabilities comply with the Software Engineering Institute’s Software Capability Maturity Model Integration for Development, Version 1.2 or the equivalent.

(b) Producibility Plan. The Offeror shall develop a Producibility Plan that substantiates how its JMM BRU will be produced by the Prime Contractor and their suppliers. This Plan specifically describes the fabrication and manufacturing techniques, design and process parameters that enable the JMM BRU to be fabricated, assembled, inspected, and tested economically and with repeatable quality. The Offeror provides a summary of the manufacturing readiness assessment (MRA) of the JMM BRU manufacturing process and an associated manufacturing maturation plan to support achieving a manufacturing readiness level (MRL) of six (6) by PDR and MRL eight (8) by SVR. The contractor shall follow the MRL Deskbook guidance in performing the MRA. Key producibility activities and methods to be provided in the plan include the following:

(i) A means to define in-process and final test measurement plans.

Description of how key parameters will be identified, measured, monitored, interpreted and how the associated data will be analyzed, stored and acted upon.

(ii) Process and quality improvement plans and tools to be used by the contractor for needed process improvements (Process variability reduction methodology). Planned Statistical Process Control methods that are used with the process capability requirements stated in terms of the process performance index (Cpk) as a guide for all key production processes.

(iii) A description or organizational chart indicating the type of organizational structure and resources available to implement process and quality improvement plans and the means to ensure this methodology is flowed down to all subcontractors. A means to ensure that

PAGE L - 12 of 17 personnel who are knowledgeable in the areas of producibility and production are represented on sub-assembly and component hardware IPTs.

(iv) The type of analysis tools planned for use, such as JMP ®, Minitab ®, types of process and yield databases, etc.

(v) The training level and experience of personnel responsible for monitoring and improving the process. (e.g., Six Sigma Black Belts, Lean training, Continuous Improvement Methodology (CIM) training, Design for Manufacturability, Design for Producibility.)

(4) Book D - Plans and Schedule (IMP/IMS)

The Offeror shall provide their JMM BRU Contract Work Breakdown Structure (CWBS) utilizing, Integrated Master Plan (IMP), Integrated Master Schedule (IMS) and Basis of Estimates (BOE) in Book D of this proposal. Book D pages shall be numbered, and may be in black and white or in color.

For the purposes of IMP/IMS preparation, the Offeror shall, for proposal purpose, use 25 March 2013 as the IMP/IMS start date; however, the start date shall serve as “Day 1” with all following events and timelines linked accordingly. The actual contract effective date will ultimately serve as the IMP/IMS start date and all subsequent events/dates will be subject to a corresponding day-for-day adjustment (to be delivered under the first Integrated Program Management Report (IPMR) Contract Data Requirements List (CDRL) submission one month after contract award). The descriptive naming used in the IMP should be identical to those in the IMS. Each event, accomplishment, criterion, and task should be labeled with a brief descriptive title and should be numbered or coded to correlate to the IMP. For additional guidance in development of the IMP, the Offeror shall use the “Integrated Master Plan and Integrated Master Schedule Preparation and Use Guide” Version 0.9 dated 21 Oct 2005 (Section L, Attachment 5). The IMP will be reviewed and approved in source selection.

Offerors shall submit hard copies of the IMS IAW the general instructions outlined below. In addition, Offerors shall submit IMS data in electronic format compatible with Microsoft Project 2007 file format for proposal evaluation displaying the identification number, task name, start, finish, duration, predecessor, and successor columns.

(a) Contract Work Breakdown Structure (CWBS). Book D CWBS section shall be in Microsoft Word 2007 format. The Offeror shall include a CWBS and CWBS dictionary based on MIL-STD-881C and the Government WBS template as depicted in Section L Attachment 6.

(b) Integrated Master Plan (IMP). Book D IMP section shall contain the content and be in the format as defined below for each sub section. The IMP shall describe the total work effort necessary to accomplish the objectives outlined in the JMM BRU SOW, SPS, PEC, SEMP, CWBS, Technology Maturation Plan, SPVP and model contract. The IMP shall also identify events, accomplishments, and accomplishment criteria for the proposed effort. Each event, accomplishment, and criterion should be descriptive, concise, and specific to the program. The Offeror shall also provide a clear stand alone list of Government actions integral to the execution of the IMP. The Offeror shall submit the IMP as outlined below:

• Section I: Introduction (MS Word 2007) o Short overview of the IMP o Assumptions and ground rules of the IMP o Event and “Action Term” Dictionary o IPT Organization and responsibilities o Describe any unique or different features of the IMP

PAGE L - 13 of 17

• Section II: IMP o Description of the numbering system (MS Word 2007) o Events, Accomplishments, and Criteria (MS Excel 2007) o List of Government actions integral to the execution of the IMP (MS Word 2007)

• Section III: IMP Narratives (MS Word 2007) o Process Narratives (if applicable) o Task Narratives (if applicable)

• Section IV: Glossary of terms and acronyms (MS Word 2007)

(c) Integrated Master Schedule (IMS). The Offeror shall develop an integrated and networked multi-layered Gantt schedule that:

(i) Includes all tasks required by the SOW

(ii) Includes hours and resources for each IMS task

(iii) Is an extension of the information contained within the IMP

(iv) Reflects the overarching technical approach of the program

(v) Addresses risks identified with the proposal and activities identified within the risk mitigation plans

(vi) Identifies required resources, and shows minimum and maximum task duration with supporting rationale substantiated by the BOEs and CWBS

(vii) Achieves the criteria as outlined in Section L Attachment 7 utilizing Steelray Project Analyzer version 3.0.

(d) The Offeror shall submit a supporting IMS narrative as outlined below:

• Section I: Introduction (MS Word 2007) o Short overview of IMS o Assumptions and ground rules for the IMS (e.g. calendar used, holidays, etc) o Describe unique features

Description of the numbering system Description of additional data fields included in IMS Description of how the IMS will be managed

• Section II: Supporting schedule (MS Word 2007, MS Excel 2007, or MS Project 2007) o The Offeror shall provide the critical path to PDR, CDR and SVR (three separate paths).

• Section III: Key elements (MS Project 2007) o Hard copy of the program critical path with rationale o Identify the nearest alternative critical path of potential significance o Schedule Risk Assessment

Explain the overall schedule risk, including critical path analysis Discuss Statistical Schedule Risk Assessment performed to provide their minimum-maximum task duration with supporting rationale for tasks identified as moderate or high risk

PAGE L - 14 of 17

• Section IV: Glossary of terms and acronyms (MS Word 2007)

• Section V: Summary schedule (MS Word 2007 or MS Project 2007)

(e) Basis of Estimates (BOEs). The Book D BOE section shall be in Microsoft Word 2007 format. The BOE shall be developed IAW the WBS as depicted in Section L, Attachment 6. The Offeror shall provide a BOE without cost data for each CWBS for each phase by Government Fiscal Year (FY). The Government FY begins on 1 October and ends on 30 September.

Where possible, these BOEs shall include non-dollarized subcontractor effort. If not possible, dollarized material cost shall be included. The Offeror shall provide the same information for each CWBS production related element by lot for JMM BRU Production Lots 1 and 2 at the most probable quantity profile. (Table 2.1 - JMM BRU Most Probable Production Quantities)

(i) For TD, EMD JMM BRU Development and EMD JMM BRU F-35 Flight Test, the BOE shall provide a description of each element of the CWBS, including any relevant technical information. The BOE shall describe which CWBS elements are software development efforts.

The BOE shall include the applicable ground rules and assumptions, the data sources and describe the estimating approach and methodology for each element to the lowest levels indicated in the CWBS in order to permit the evaluator to readily identify the method and assess the validity of the buildup. The Offeror shall identify the analogous programs used to support their data and identify the adjustments applied to the data based on differences in complexities. The BOE shall identify any risk mitigation efforts associated with each CWBS to include a narrative description, the likelihood and timing of the risk mitigation efforts.

(ii) For JMM BRU Production Lots 1 and 2, the BOE shall provide a description of each element of the CWBS, including any relevant technical information. The BOE shall describe which CWBS elements are software efforts. The BOE shall include the applicable ground rules and assumptions, the data sources and describe the estimating approach and methodology for each element to the lowest levels indicated in the CWBS in order to permit the evaluator to readily identify the method and assess the validity of the buildup. The Offeror shall identify the analogous programs used to support their data and identify the adjustments applied to the data based on differences in complexities.

If the described BOE for a CWBS is the same for Production Lots 1 and 2, then one BOE for a CWBS is acceptable and should be annotated in the BOE. The BOE shall include a narrative description of any potential uncertainty.

(5) Book E – System Performance Verification Plan (SPVP)

The Offeror shall provide their JMM BRU SPVP using Section L, Attachment 9. The Offeror shall describe their verification approach and verification method to verify the JMM BRU can meet all requirements specified in the referenced JMM BRU SPS and PEC. Book E shall be in Microsoft Word 2007 format.

Book E pages shall be…