Section_L_PDGU_2Nov2015.pdf

PDGU, Section L For Official Use Only 3 November 2015

SECTION L

L-III - INFORMATION TO OFFERORS (ITO) and INSTRUCTIONS FOR

PROPOSAL PREPARATION

1.0 Program Structure and Objectives

The F-16 System Program Office’s (SPO) objective is to upgrade or replace the current United States Air Force (USAF) F-16 Blocks 40/42/50/52 Programmable Display Generator (PDG).

This shall be a 10-year contract. Contract type will be FAR Part 15 Single Award, Definite Delivery Contract, under Best Value Trade-Off Source Selection.

NOTE: FOREIGN PARTICIPATION AND FOREIGN COMPANIES ARE PROHIBITED

FROM SUBMITTING RESPONSES TO THIS SOLICITATION (NOFORN) AS A

POTENTIAL PRIME CONTRACTOR; HOWEVER, THIS DOES NOT PROHBIT FOREIGN-

OWNED COMPANIES FROM PARTICIPATING AS A POTENTIAL SUBCONTRACTOR.

NOTE: OFFERORS ARE ADVISED THAT THE COSTS OF ANY RESPONSE TO, OR

OTHER COSTS INCURRED AS A RESULT OF RESPONDING TO THIS SOLICITATION

ARE AT THE OFFEROR’S OWN RISK. ANY COSTS INCURRED IN PREPARING A

RESPONSE TO THIS SOLICTATION MAY BE ATRIBUTABLE TO BID AND PROPOSAL

(B&P) OVERHEAD COSTS, BUT MAY NOT BE DIRECTLY CHARGED TO ANY

RESULTING AWARDED CONTRACT. B&P COSTS FOR THIS SOLICITATION ARE

COSTS COVERED BY CAS 420/FAR 31.205-18.

The Government’s solicitation provides the offeror with the following elements: Model Contract (Sections A - K), Section L, Section M, Statement of Objectives (SOO), Applicable Documents, Subsystem Requirements Document (SSRD), and Contract Data Requirements List (CDRL).

In Accordance With (IAW) the detailed proposal preparation instructions found in this solicitation, the Offeror shall submit a proposal containing: a completed Model Contract, Contract Work Breakdown Structure (CWBS), Contract Statement of Work (CSOW), Integrated Master Plan (IMP), Integrated Master Schedule (IMS), Small Business Participation Plan, draft Software Development Plan (SDP), Anti-Tamper Concept Plan (ATP), draft Program Management Plan (PMP) and draft Systems Engineering Management Plan (SEMP).

2.0 General Instructions

(a) The offeror's proposal must include all data and information requested by this ITO and must be submitted IAW these instructions. The offer shall be compliant with the requirements as stated in the SOO, SSRD, System Specification, CDRLs, and Model Contract. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation.

(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 and will base its evaluation on the information presented in the offeror's proposal.

(c) Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired. Similarly, elaborate productions are unnecessary and not desired.

(d) The proposal acceptance period is specified in Section A of the model contract/solicitation. The offeror shall make a clear statement in Section A of the proposal documentation volume five that the proposal is valid through December 2016.

(e) IAW Federal Acquisition Regulation (FAR) Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals. Unless the offeror requests otherwise, the Government will destroy extra copies of such unsuccessful proposals.

2.1 General Information

2.1.1. Point of Contact

The Contracting Officer (CO) is the sole point of contact for this acquisition. Address any questions or concerns you may have to the CO. Written requests for clarification may be sent to the CO at the address located below. In the event of conflict between answers to questions/clarifications and the RFP, including any amendments, the RFP shall take precedence.

AFLCMC/WWMK

ATTN: Richard Porter 6072 Fir Ave, Bldg 1233 Hill AFB, UT 84056-5820

2.1.2. Debriefings

The CO will promptly notify offerors of any decision to exclude them from the competitive range; whereupon, they may request and receive a debriefing IAW FAR 15.505. Offerors excluded from the competitive range may request a preaward debriefing or they may choose to wait until after the source selection decision to request a postaward debriefing. However, offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The CO will notify unsuccessful offerors in the competitive range of the source selection decision IAW FAR 15.506. Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request IAW the requirements of FAR 15.505 or 15.506, as applicable.

2.1.3. 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 CO in writing with supporting rationale as well as the remedies the offeror is asking the CO to consider as related to the omission or error.

The offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion. This reservation includes matters of additional or substitute pages of the initial proposal.

2.1.4. Electronic Reference Documents

For access to any documentation referenced in this RFP, encrypted (ATTACHMENT L-EIGHT, Encryption Methodology) e-mail request to the CO, Richard Porter, at Richard.Porter.12@us.af.mil. All referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) website at http://www.fedbizopps.gov. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

2.1.5. Oral Presentations

Oral presentations will not be allowed.

2.1.6 Communications

Exchanges of source selection information between Government and offerors will be controlled by the CO. Email may be used to transmit such information to/from offerors only if the email can be sent and received encrypted (ATTACHMENT L-EIGHT, Encryption Methodology) and includes “Source Selection Information – See FAR 2.101 & 3.104” in the Subject line.

Otherwise, source selection information will be transmitted via certified US Postal Service, FedEx or equivalent mail service.

2.2 Organization/Number of Copies/Page Limits

The offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 1 below). The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified in Table 1. The attachments identified in the table shall be included in the designated volume three-ring, loose-leaf binders. If needed, volume II attachments can be submitted in a separate three-ring, loose-leaf binder. Each subfactor within the Technical factor shall be separately tabbed. The contents of each proposal volume are described in the ITO paragraph as noted in the table below.

mailto:Richard.Porter.12@us.af.mil http://www.fedbizopps.gov/

Table 1 - Proposal Organization

VOLUME ITO

Paragraph Number

VOLUME TITLE Hard (H) and Electronic

(E) COPIES

PAGE LIMIT

I 3.0 Executive Summary to include

ATTACHMENT L-ONE

3-E 10-H

15 (not including attachment L-

ONE)

II 4.0 Technical/Technical Risk Systems Engineering Management Plan Integrated Master Plan Integrated Master Schedule Program Management Plan Contractor Work Breakdown Structure Software Development Plan Anti-Tamper Concept Plan Hardware Qualification Plan Manufacturing Plan Draft SRTM

3-E 10-H 200 plus 30 pages per plan/schedule (not included in 200 page count)

III 5.0

**Submitted 25 calendar days after

RFP release**

Past Performance to include

ATTACHMENT L-TWO,

ATTACHMENT L-FIVE,

ATTACHMENT L-SIX

3-E 8-H

5 pages per contract

IV 6.0 Cost/Price 3-E 3-H

Unlimited

V 7.0 Contract Documentation 3-E 3-H Unlimited

2.2.1 Page Limitations

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal and excess paper copies will be returned to the offeror as soon as practicable. Page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors. Please take note of the page limitation after each subfactor in Volume II – Technical. Each page shall be counted except the following: cover, table of contents, glossary, acronym glossaries, and index.

2.2.1.1. Page Size and Format

(a) 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, the font shall be Times New Roman and 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 ¾-inch side margins. Pages shall be numbered sequentially by volume (and subfactor for Technical Volume II). These page size and format restrictions shall apply to responses to ENs, and shall apply to both electronic and hard copies of proposals submitted.

(b) 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 inch surface of a foldout shall be counted as a separate page (i.e. one 11 x 17 inch foldout equals 2 proposed pages. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics not for pages of text. For tables, charts, graphs and figures, the text shall be no smaller than 9 point. These limitations shall apply to both electronic and hard copies of proposals submitted.

2.2.2 Cost or Pricing Related Data

All cost or pricing data shall be addressed ONLY in the Cost/Price Proposal and Contract Documentation Volumes. Cost trade-off information, work hour estimates, and material kinds and quantities may be used in other volumes only as appropriate for presenting rationale for alternatives or design and trade-off decisions.

2.2.3 Classified Information

If classified information is required in the offeror’s response, it shall be provided as a written classified supplement and bound in a single classified addendum to the offeror’s solicitation and shall be compliant with security classification provided by DD Form 254. Each entry in the classified addendum shall be referenced to the proposal volume, page number, and paragraph number to which it applies. Similarly, a reference shall be placed in the unclassified volume where the classified insert applies, giving the page and paragraph numbers within the addendum where it can be found. Binding shall conform to the same directions as those given in this ITO for unclassified portions. The classified addendum shall be separately bound and conform to the marking and transfer requirements of the National Industrial Security Program Operating Manual (NISPOM), IAW the DD Form 254. Pages in a classified addendum will be included in the page count for the applicable volume. Classified information must be properly packaged and mailed into the following address:

ATTN: Doug Johnson and Lindsey Giles 801-775-5707 6137 Wardleigh Rd (Bldg 1515, Rm 220) Hill AFB, UT 84056-5843

2.2.4 Cross-Referencing

To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross referencing to other volumes of the proposal.

Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity.

2.2.5 Indexing

Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections in the hard copies. Table of Contents do not count against the page limitations for their respective volumes.

2.2.6 Glossary of Abbreviations and Acronyms

Each volume shall contain a glossary of all abbreviations and acronyms used, and with an explanation for each. Glossaries do not count against the page limitations for their respective volumes.

2.2.7 Binding and Labeling

Each volume of the proposal should be separately bound in a three-ring, loose leaf binder permitting 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. 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 IAW 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. Each page within a volume shall be numbered consecutively. Each page that contains proprietary information shall be marked inside the header and footer of each page with the following statement “SOURCE SELECTION INFORMATION (FAR 3.104) FOR

OFFICIAL USE ONLY.”

2.3 Electronic Offers

The content and page size of electronic copies must be identical to the hard copies. For electronic copies use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any. The offeror shall submit using a recordable CD.

Each volume shall be in a different directory on a CD, except volume III. Volume III, Past Performance, will be on a separate CD for early delivery. If files are compressed, the necessary decompression program must be included. The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Office Word 2010, MS Office Excel 2010, MS Office Project 2010, and MS Office Power Point 2010, as applicable. Electronic storage media shall be submitted in Prerecorded (pressed) CD-ROM or CD-R. Submit PDF documents that are compatible with Adobe Acrobat XI Pro. Do NOT submit any documents in PDF format that are copied as “images.” When creating PDF and Microsoft Office files, always create to enable textual search and copy functions. In the event that hard copies and electronic copies of a proposal are submitted and if there are any discrepancies between the hard copies and the electronic copies of the proposal, the hard copies will be used for evaluation.

2.4 Distribution

The "original" proposal shall be identified. Proposals shall be addressed to the CO and mailed or hand carried to:

AFLCMC/WWMK

ATTN: Richard Porter 6072 Fir Ave, Bldg 1233 Hill AFB, UT 84056-5820

Be sure to advise the Administrative Contracting Officer (ACO) and the Defense Contract Audit Agency (DCAA) for prime and subcontractors that the proposal is "For Official Use Only" and "Source Selection Information--See FAR 2.101 and FAR 3.104". Electronic submittals will not be accepted.

3.0 Volume I - Executive Summary

In the executive summary volume, the offeror shall provide the following information:

3.1 Narrative Summary

The narrative summary of the entire proposal should be concise, to include addressing the significant risks, and highlighting any key or unique features, excluding cost/price. The salient features should tie in with Section M evaluation factors/subfactors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

3.2 Table of Contents

Include a master table of contents of the entire proposal.

3.3 Cross Reference Matrix (CRM)

The offeror shall fill out the CRM that assures all requirements are addressed and easily accessible to the evaluators. All references to a requirement shall be accounted for in the matrix.

The CRM must provide a single integrated index for the entire proposal. The Government has provided a preliminary CRM (ATTACHMENT L-ONE, Sample Cross Reference Matrix) to assist the offeror in correlating Section L instructions with Section M evaluation factors. The CRM shall reference the Proposal Reference, Section L, Section M, SOO, SSRD, Data Item Description (DID), and Contract Line Item Numbers (CLINs). The CRM is included in the Executive Summary but is not included in the volume page count.

4.0 Volume II - Technical Volume

4.1 General

The Technical Volume should be specific and complete. Legibility, clarity, and coherence are very important. Your responses will be evaluated against the Technical subfactors defined in Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying these subfactors. All the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing that your firm will perform all the requirements specified in the solicitation. It is not necessary or desirable for you to tell us so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

4.2 Format and Specific Content

4.2.1 Volume Organization

The Technical volume shall be organized according to the following general outline:

(1) Table of Contents

(2) List of Table and Drawings

(3) Glossary

(4) Subfactor One – Technical Requirements

(5) Subfactor Two – Data Rights and Sustainment

(6) Subfactor Three – Organic Software Development Support

4.2.2 Technical

In the Technical volume, address your technical solution for meeting or exceeding the Government’s minimum performance or capability requirements for each Technical subfactor.

4.2.2.1 Technical Risk

Address Technical Risk associated with those aspects of your proposed CSOW you consider to have the potential for disruption of schedule, increased costs, degradation of performance, the need for increased Government oversight, or the likelihood of unsuccessful contract performance. Classify each risk IAW DoD Source Selection Procedures Table 3, Technical Risk Rating (link provided at end of document). Provide the rationale for each risk and its rating, including quantitative estimates of the impact on cost, schedule, and performance. Describe the impact of each identified risk in terms of its potential to interfere with or prevent the successful accomplishment of other contract requirements (for example: SOO or specification requirements), whether or not those requirements are identified as subfactors. Propose realistic risk mitigation for identified risks that will eliminate or reduce risk to an acceptable level.

Identify and classify any new risks introduced by such risk mitigation. The Government will not be bound by the offeror’s proposed acceptable level of risk mitigation or proposed risk rating determination and the Government will make the final determination of the Technical Risk Rating assigned in the evaluation.

4.2.3 Subfactor One – Technical Requirements

Proposals will provide narrative to address each of the following paragraphs to demonstrate the offeror’s capability to meet or exceed all requirements outlined in the F-16 PDGU SSRD and SOO. Particular emphasis will be placed on the offeror’s ability to develop, document, and qualify the product as well as provide proper security standards, as described in the SSRD.

a) Demonstrate a thorough understanding and approach to accomplishing all applicable SOO and SSRD elements.

b) Plan a comprehensive approach to achieve all technical requirements of the SRD no later than the planned Critical Design Review and support this approach in a detailed Systems Engineering Management Plan (SEMP).

c) Provide a detailed Integrated Master Plan (IMP) and Integrated Master Schedule (IMS) and explain the approach to plan, implement, update throughout the life of the contract

d) Provide a detailed and comprehensive Program Management Plan that addresses configuration management, logistics support and safety assurance. The plan must reflect the PDGU CSOW and relate to the proposed work break down structure in the Integrated Master Plan.

e) Explain the proposed system architecture, how it will integrate the hardware and software architecture and meet the requirements established in the SOO and SSRD.

f) Detail proposed software architecture that that will be used to generate a compiled Operational Flight Program (OFP) capable of executing all PDGU functions. Reflect this approach in a Software Development Plan to include a detailed discussion of planned development tools, environment, and staff and supported Real Time Operating Systems

(RTOS).

g) Utilize a proven process and provide a plan for the hardware qualification of the proposed PDGU. Detail previous experience with hardware qualification and specify all qualifications that are anticipated to be approved by similarity

h) Provide a manufacturing plan which details: 1) how the proposed manufacturing management system meets the requirements of AS6500. The submitted production transition approach, quality assurance program approach, and current ISO certifications must support the proposed manufacturing approach; 2) provides a detailed facility requirements and layouts and plans to provide the needed manpower, facilities, and equipment for expected delivery rates; 3) include information regarding the major assembly sequence and manufacturing process flows to include an integrated, achievable schedule incorporating design, tooling, supplier, fabrication, assembly, and delivery milestones. Incorporate these elements into the IMS.

i) Provide an approach to an Anti-Tamper Concept Plan and demonstrate the ability to meet all mandated Cyber Security (CS) controls. Detail past CS experience, current CS staffing and certifications and relate them to Department of Defense (DoD) 8570.01-M, Change 3 compliance. Identify CS vulnerabilities and mitigation for the proposed solution.

j) Detail the man-power, training and technical support that will be provided to aid the Government with integration and testing of the offeror’s re-hosted PDGU OFP.

k) Provide a detailed concept for accomplishing Software Safety and Assurance throughout the program.

l) Specify program risk anticipated in supporting the PDGU program and provide an anticipated mitigation for each identified risk.

m) Provide a detailed description of the PDGU RTOS characteristics.

n) Provide Program Management Support to address Small Business Participation Plan.

4.2.4 Subfactor Two – Data Rights and Sustainment

offeror’s ability to design a product with sustainment as a focus. This subfactor will evaluate sustainment planning, contractor supported repair, the offeror’s approach to meeting the required Mean Time Between Failure, and the transfer of sustainment related knowledge through the technical data package and the related data rights.

a) Provide the contractor’s approach and all products necessary to enable the Government to stand up organic repair to the Shop Replaceable Unit (SRU) component level and specifically address depot maintenance standup support.

b) Provide a detailed explanation of the technical data package, how it will be managed, and include specific information on how SOO requirements for drawings and data rights will be met.

c) Clearly define the anticipated data rights associated with both software and firmware deliverables.

d) Detail your approach to providing contract supported sustainment of pre and post production PDGU systems

e) Explain the calculations used to establish your calculated Mean Time Between Failure

(MTBF).

f) Detail the effects of the proposed MTBF on the long term sustainment of the PDGU.

4.2.5 Subfactor Three – Organic Software Development Support

offeror’s approach to supporting the On-Site OFP Software Development. This complete approach to PDGU software knowledge transfer should address: all tools needed, compliance processes, licensing details, and anticipated staffing.

a) Specify the man-power, training and technical support required to assist the Government in enhancing, maintaining, integrating, and testing a Government developed version of the re-hosted PDGU OFP.

b) Address all planned software development tools, anticipated licensing agreements, and special hardware requirements essential to support the Government modification of the re-hosted OFP.

c) Clearly explain how the proposed software architecture, coding standards and development environment supports transition of efficient software maintenance to the Government.

d) Specify all proprietary software development tools, firmware, drivers, and software.

e) Describe in detail the proposed PDGU emulation. Address: I/O interfaces supported, performance anticipated, and anticipated interfaces to SW development stations.

5.0 Volume III - Past Performance

5.1 General

Each offeror shall electronically submit a past performance volume 25 calendar days after RFP release, containing past performance information IAW the both formats contained in Attachment L-TWO. This information is required on the offeror and all subcontractors, teaming partners, and/or joint venture partners who are proposed to perform 20 percent or more of the proposed effort based on the total proposed price or perform aspects of the effort the offeror considers critical to overall successful performance. Offerors are cautioned that the Government will use data provided by each offeror in this volume and data obtained from other sources in the evaluation of past performance.

Along with the information required in this paragraph, the offeror shall submit a consent letter (ATTACHMENT L-FIVE) executed by each subcontractor, teaming partner, and/or joint venture partner, authorizing release of adverse past performance information to the offeror so the offeror can respond to such information. For each identified effort for a commercial customer, the offeror shall also submit a client authorization letter (ATTACHMENT L-SIX), authorizing release to the Government of requested information on the offeror's performance.

As soon as possible, Offerors shall e-mail Section J Attachments: Past Performance Questionnaire Cover Sheet (ATTACHMENT L-THREE), Past Performance Questionnaire

(ATTACHMENT L-FOUR) and the Questionnaire Cover Letter Template (ATTACHMENT L- SEVEN) to all points of contact the Offeror has listed in the Past Performance Information Sheets (ATTACHMENT L-TWO).

RESPONDENTS TO THE QUESTIONNAIRES SHALL SEND THE COMPLETED

INFORMATION TO THE CO AS OUTLINED IN ATTACHMENT L-THREE, PAST

PERFORMANCE QUESTIONNAIRE COVER SHEET. THE QUESTIONNAIRES SHALL

NOT BE SENT BACK TO THE OFFEROR.

5.2 Early Proposal Information

Each offeror is requested to submit the information shown in ATTACHMENT L-TWO for each relevant contract 25 days after the RFP is released. Failure to submit early proposal information will not result in offeror disqualification.

5.3 Relevant Contracts

Submit information IAW ATTACHMENT L-Two: Past Performance Information on three recent contracts, within the last five years, that you consider most relevant in demonstrating your ability to perform the proposed effort. Also include information on three recent contracts, within the last five years, performed by each of your teaming partners and significant subcontractors that you consider most relevant in demonstrating their ability to perform the proposed effort. Include rationale supporting your assertion of relevance. For a description of the characteristics or aspects the Government will consider in determining recency and relevance, see Section M, Section 2.0 for Evaluation Factors and Section 2.3 for Past Performance Factor.

5.3.1 Specific Content

Offerors are required to explain what aspects of the contracts are deemed relevant to the proposed effort and to what aspects of the proposed effort they relate. This may include a discussion of efforts accomplished by the offeror to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. Merely having problems does not automatically equate to a limited or no confidence rating, since the problems encountered may have been on a more complex program, or an offeror may have subsequently demonstrated the ability to overcome the problems encountered. The offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions in terms of improvements achieved or problems rectified. This may allow the offeror to be considered a higher confidence candidate. For example, submittal of quality performance indicators or other management indicators that clearly support that an offeror has overcome past problems is required. Categorize the relevant information into the specific Technical subfactors and Cost/Price factor used to evaluate the proposal.

5.3.2 Organizational Structure Change History

Many companies have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant past efforts or between conclusion of recent past efforts and this source selection. As a result, it is sometimes difficult to determine what past performance is relevant to this acquisition. To facilitate this relevancy determination, include in this proposal volume a "roadmap" describing all such changes in the organization of your company. A pamphlet or other commercial document describing such reorganizations may suffice. As part of this explanation, show how these changes impact the relevance of any efforts you identify for past performance evaluation/performance confidence assessment. Since the Government intends to consider past performance information provided by other sources as well as that provided by the offeror(s), your "roadmap" should be both specifically applicable to the efforts you identify and general enough to apply to efforts on which the Government receives information from other sources.

6.0 Volume IV - Cost/Price

6.1 General Instructions

6.1.1 Cost/Price Reasonableness and Realism

This section is to assist the offeror in submitting data other than certified cost or pricing data that is required to evaluate the reasonableness, balance, affordability, realism (where identified), and Total Evaluated Price (TEP) of the offeror’s proposed cost and price. Compliance with these requirements is mandatory and failure to comply may result in rejection of the offerors proposal.

Offers shall be sufficiently detailed to demonstrate their acceptability in all of the above criteria.

The burden of proof for credibility of proposed costs and prices rests with the offeror.

6.1.2 Estimating Techniques and Methods

When responding to the Cost/Price Volume requirements in the solicitation, the offeror and associated subcontractors may use any generally accepted estimating technique, including contemporary estimating methods (such as Cost-to-Cost and Cost-to-Non-Cost Estimating Relationships (CER)), commercially available parametric cost models, in-house developed parametric cost models, etc.), to develop their estimates. If necessary, reasonable and supportable allocation techniques may be used to spread hours and/or costs to lower levels of the Work Breakdown Structure (WBS).

6.1.3 Cost/Price Data

Data beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your cost/price position. All data relating to the proposed price, including all required supporting documentation, must be included in the section of the proposal designated as the Cost/Price volume. Under no circumstances shall this data and documentation be included elsewhere in the proposal.

6.1.4 Cost or Pricing Data Requirements

IAW FAR 15.403-1(b) and 15.403-3(a), information other than cost or pricing data may be required to support price reasonableness, balance, and/or realism (where identified). Information shall be provided IAW these instructions and IAW FAR 15.403-5. If, after receipt of proposals, the PCO determines that there is insufficient information available to determine price reasonableness, balance, and/or realism and none of the exceptions in FAR 15.403-1 apply, the offeror shall be required to submit cost or pricing data.

6.1.5 Rounding

All dollar amounts provided shall be rounded to the nearest dollar. All loaded labor rates shall be rounded to the nearest penny.

6.1.6 Total Evaluated Price Table

Refer to Section J Attachment, TEP Table. Offerors shall populate the pricing and cost cells as appropriate. Recognize that the prices the offeror submits on the TEP Table will be contractually binding. The TEP Table will be identical to the pricing in section B of the RFP. The Government will use this worksheet to calculate the TEP. Do not propose an amount for Cost Reimbursable No fee (CRNF) CLINs. Actual costs incurred under these CLINs will be reimbursed to the contractor to include general and administrative expenses as approved by the

ACO.

6.1.7 Submission Requirements

Submit the price proposal on virus-free CD-R in Microsoft Word and Microsoft Excel worksheets as appropriate. Word documents and Excel spreadsheets must be editable and not password protected. Each disc shall be properly labeled. The paper and electronic copies shall be identical in all respects. Scanned documents in PDF files are NOT acceptable for the Cost- Price Proposal Volume.

6.1.8 “Subcontractor” Definition

For purposes of this RFP sections L & M Volume III – Price Proposal “Subcontractor” shall refer to any Subcontractor, Teaming Partner, Interdivisional Transfer, or other separate internal or external entity the offeror is including in their cost-price proposal.

6.1.9 “Fully Burdened” Definition

”Fully Burdened” means direct cost plus any applicable burdens (i.e. Overhead, Fringe, General and Administrative, Cost of Money) including profit/fee.

6.2 Volume Organization

The Cost/Price volume shall consist of the following sections:

SECTION 1 The Cost/Price volume shall be prefaced by a Table of Contents and shall specify, by page number, the location of information requested in these instructions. Also include a summary description of estimating, purchasing, and accounting systems; changes to estimating, accounting practices, and Cost Accounting Standards (CAS) Disclosure Statement (if available).

SECTION 2 Summarize all significant pricing assumptions, scope limitations and/or qualifications of the cost proposal. Provide complete rationale for any exceptions.

SECTION 3 All other Cost/Pricing information as detailed below

6.3 Other Required Cost/Pricing Information

6.3.1 Accounting System

Indicate whether the offeror and all subcontractors who will be issued other-than fixed price work under other than fixed price CLINs have Government approval of the Offerors accounting system and if so, provide evidence of such approval.

6.3.2 Software Engineering Support Build-Up Sheet

Complete the CLIN X015 Tab in Section J Attachment (TEP Spreadsheet) IAW the instructions contained therein. Include all fully-burdened labor rates and proposed hours and ensure the price corresponds to the proposed price on CLIN X015 in section B and the TEP Table. Recognize that the rates proposed in this section shall be contractually binding and fixed during performance.

6.3.3 Labor Rate Matrix

Complete Section J Attachment (Labor Rate Matrix) and Section J Attachment (Labor Category Mapping Worksheet) IAW the instructions contained thereon respectively. Include fully burdened labor rates for all specified categories.

6.3.4 Production Asset Quantity Discount Pricing Sheet

Complete the CLIN X020 and X021 Tabs in Section J Attachment (TEP Spreadsheet) IAW the instruction contained thereon. Include fully burdened prices for each quantity and year.

6.3.5 Total Evaluated Price Sheet

The offeror shall submit populate all requested pricing attachments (Section J Attachment, Total Evaluated Price (TEP) Table). Refer to Section M for discussion of the TEP and how each CLIN shall be populated/evaluated.

6.3.6 Basis of Estimate

The Offeror shall provide a priced BOE for Cost-Plus Fixed Fee (CPFF) line items X007. The offeror shall show base labor rate, direct labor hours, direct labor mix, direct material (if applicable), a breakout of all indirect rates applied including their bases, escalation and fee.

Also, indicate the basis and rationale for all these items and include (if applicable) any outside documents that form the basis for these items (Forward Priced Rate Proposals, audits, vendor quotes, etc). This shall include, but is not limited to:

a. Direct material with an extended. Value (unit cost multiplied by the number of units) exceeding $3,000. Include also the actual copies of quotes, bids, or equivalent documents provided by vendors.

b. Submit a Price/Cost Analysis including basis for ‘Fair & Reasonable’ for all subcontractors including justification for any exceptions or adjustments made to the subcontractor’s proposed price. Also submit (in table form) a list of the proposed probable subcontractors and interdivisional transfers showing as appropriate (a) the supplier, (b) description of effort, (c) type of contract, (d) price and hours proposed by each, (e) price and hours included in prime’s proposal to the Government, and (f) commercial item and service determination support, if applicable.

c. In support of the Offeror’s basis of estimate for Cost-Plus Fixed Fee (CPFF) line items

X007 the Offeror shall provide a spreadsheet with content substantially the same as ATTACHMENT L-NINE, Sample BOE Summary, in support of the proposed price for the prime Offeror. The Offeror shall also request that major subcontractors who will be issued cost-type subcontracts under a Cost-Plus Fixed Fee (CPFF) line item (X007) with a total dollar value above $750,000 to submit a spreadsheet substantially the same as ATTACHMENT L-NINE, Sample BOE Summary, (with all above requirements) in support of their proposal (the subcontractors may submit their information directly to the government if they so desire). The Offeror/subcontractor may tailor the spreadsheet as needs be to fit the Offeror’s/subcontractor’s standard practices and proposal, but shall provide as much information as possible. The Offeror shall also reference where in the Offeror’s cost and price proposal the basis for these elements are found. Any cost and price model submitted must be consistent with the Offerors approved estimating system and must duplicate the logic and mathematical formulas reflected in the paper copy of the Offerors proposal. Cost and price models data file shall be in MS-Excel format with calculation formulas intact.

7.0 Volume V - Contract Documentation

7.1 Model Contract/Representations and Certifications

The purpose of this volume 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.

7.1.1 Section A - Solicitation/Contract Form

Completed blocks 13 and 15 and signed and dated block 27. Completing block 27, including the signature and date, constitutes an offer, which the Government may accept.

7.1.2 Section B - Supplies or Services and Costs/Prices

Completed pricing information in Section B of the model contract.

7.1.3 Section F - Deliveries or Performance

Proposed Delivery Schedule. The offeror shall propose the lead time delivery schedule in Section F of the model contract for out-year production assets.

7.1.4 Section G - Contract Administrative Data

See Section G of Model Contract.

7.1.5 Section I - Contract Clauses

See Section I of Model Contract.

7.1.6 Section J – List of Documents, Exhibits and Other Attachments

See Section J of Model Contract.

7.1.7 Section K - Representations, Certifications, and other Statements of Offerors

Completed representations, certifications, acknowledgments, and statements.

7.2 Exceptions to Solicitation Requirements

Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. 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. However, failure to meet a requirement may result in an offer being ineligible for award. This information shall be provided in the format and content of Table 2.

Table 2 - Solicitation Exceptions

Solicitation Document

Page/ Paragraph

Requirement/ Portion Rationale

SSRD, SOO, Model Contract, ITO, etc.

Applicable Page and Paragraph Numbers

Identify the requirement or portion to which exception is taken

Describe why the requirement can/will not be met

7.3 Other Information Required

7.3.1 Authorized Offeror Personnel

Provide the name, title, and telephone number of the company/division point of contact regarding decisions made with respect to your proposal and who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government.

7.3.2 Government Offices

Provide the mailing address, telephone and fax numbers and facility codes for the cognizant Contract Administration Office, Defense Contract Audit Agency (DCAA), and Government Paying Office. Also, provide the name and telephone and fax number for the ACO.

7.3.3 Company/Division Address, Identifying Codes, and Applicable Designations

Provide company/division's street address, county and facility code; Commercial and Government Entity (CAGE) code; Data Universal Numbering System (DUNS) code; Tax Identification Number (TIN); size of business (large or small); and labor surplus area designation. This same information must be provided if the work for this contract will be performed at any other location(s). List all locations where work is to be performed and indicate whether such facility is a division, affiliate, or subcontractor, and the percentage of work to be performed at each location.

7.3.4 Attachments to the Model Contract

The offeror shall provide the following as attachments to the model contract:

7.3.4.1 Subcontracting Plan Participation of Small Businesses (SB), Veteran-Owned Small Business (VOSB), Service Disabled Veteran-Owned Small Business (SDVOSB), HUBZone Small Business (HUBZone), Small Disadvantaged Business (SDB), and with Women-Owned Small Business (WOSB)

If the offeror is other than a small business, the offeror shall submit a Small Business Subcontracting Plan IAW FAR 52-219-9, Small Business Subcontracting Plan that separately addresses and specifies the extent of the offeror’s commitment to the participation of SB, VOSB, SDVOSB, HubZone, SDB, and WOSB concerns. If the offeror is submitting an individual contract plan, the plan must separately address subcontracting with SB, VOSB, SDVOB, HUBZone, SDB, and WOSB concerns with a separate part for the basic contract and separate part for each option (if any). The plan shall be included in and made a part of the resultant contract. Failure to submit and negotiate the subcontracting plan shall make the offeror ineligible for award of a contract. If applicable, submit a copy of your approved Master Plan. In the event the offeror has negotiated a comprehensive subcontracting plan pursuant to Defense Federal Acquisition Regulation Supplement (DFARS) 219.702, The Small Business Contracting Program, Statutory requirements, the offeror must submit the information that identifies and specifies the extent of their commitment to the participation of SB, VOSB, SDVOB, HUBZone, SDB, and WOSB. These targets will be provided in the Small Business Subcontracting Plan IAW FAR 52.219-9, and submitted under the Technical Requirements Subfactor One in the Technical Volume of the proposal and shall count towards the page count of that section.

Source Selection Procedures Address www.acq.osd.mil/dpap/policy/policyvault/USA007183-10-DPAP.pdf

ANNEX A

ACRONYM LIST

ACO – Administrative Contracting Officer

ATP - Anti-Tamper Plan

BOE - Basis of Estimates

CAGE - Commercial and Government Entity

CAS - Cost Accounting Standards

CDRL - Contract Data Requirements List

CER - Cost-to-Non-Cost Estimating Relationship

CLIN - Contract Line Item Number

CO - Contracting Officer

CRM - Cross Reference Matrix

CRNF - Cost Reimbursable No Fee

CS - Cyber Security

CSOW – Contract Statement of Work

CWBS - Contract Work Breakdown Structure

DCAA - Defense Contract Audit Agency

DFARS – Defense Federal Acquisition Regulation Supplement

DoD - Department of Defense

DUNS - Data Universal Numbering System

EN - Evaluation Notice

FAR - Federal Acquisition Regulation

IAW - In Accordance With

IMP - Integrated Master Plan

IMS - Integrated Master Schedule

ITO - Information to Offerors

MS - Microsoft

MTBF - Mean Time Between Failure

OFP - Operational Flight Program

PDG - Programmable Display Generator

PMP - Program Management Plan

RTOS - Real Time Operating System

SB - Small Business

SDB - Small Disadvantaged Business

SDP - Software Development Plan

SDVOSB - Service Disabled Veteran-Owned Small Business

SEMP - Systems Engineering Management Plan

SOO- Statement of Objectives

SPO - System Program Office

SSRD - Subsystem Requirements Document

SRU - Shop Replaceable Unit

TEP - Total Evaluated Price

TIN - Tax Identification Number

USAF - United States Air Force

VOSB - Veteran-Owned Small Business

WBS - Work Breakdown Structure

WOSB - Women-Owned Small Business