DRAFT_BAT_Section_L.pdf

DRAFT – BAT SECTION L

INSTRUCTIONS TO OFFERORS

14 Apr 16

A. Proposal Instructions The following instructions cover the preparation and submittal of the offeror’s proposal for this solicitation. To ensure timely and equitable evaluation of proposals, offerors must follow the instructions contained herein. Offerors are cautioned that any noncompliance with the terms and conditions of the RFP may cause their proposal to be determined unacceptable and therefore not eligible for award. Offerors/Joint Ventures shall submit only one (1) proposal for the proposed effort. If a joint venture arrangement exists for this acquisition, the offeror shall provide a copy of the joint venture agreement that is signed and dated by all joint venture members as part of the proposal submission. No additional proposals (i.e., one offeror submitting two proposals based on differing approaches) shall be submitted. The Government will review only one proposal per offeror. Submission of the initial proposal via electronic mail will not be accepted. Initial proposal packages shall either be mailed or hand-delivered to Contracting Officer/Buyer.

Proposals shall be submitted to the Government in five (5) separate volumes as set forth below:

VOL PAGE LIMTS NUMBER OF COPIES DESCRIPTION

I N/A 1 Paper/1 Electronic* Completed RFP (excluding Section B of the Schedule) (Including RFP Attachment 1, Cross Reference Matrix (CRM), and copy of Joint Venture Agreement (if applicable))

II 50 2 Paper/2 Electronic* Written Technical Proposal

III N/A 2 Paper/2 Electronic* Past Performance

IV N/A 1 Paper/1 Electronic* Small Business Concern Utilization Plan

V N/A 2 Paper/2 Electronic** Cost/Price Proposal (Cost Volume with completed RFP Attachment 9, Excel Price Model, and RFP Attachment 12, Excel Cost Model)

* Electronic copies shall be submitted in accordance with RFP Attachment 2, Electronic Format for All Proposal Volumes.

Proposals shall be submitted in written form (paper) and digital form (CD-R or DVD-R)*(write once/read only) that is “closed” so that no further writes can be made to the media. CD-R/W or DVD-R/W media types are not acceptable. Media must be virus scanned by the offeror prior to submitting to the Government. For electronic copies, indicate on each CD-ROM the volume number and title. Each volume must be stored on a separate CD-ROM. Offerors shall utilize the instructions set forth in RFP Attachment 3, Past Performance Information (PPI) for Offerors, to use the PPI Tool to electronically submit the past performance information.

**Cost/Price proposal information (Completed Excel Price Model, RFP Attachment 9) shall be submitted in written form (2 copies) and CD-R or DVD-R (write once/read only) (2 copies). Completed Excel Cost Model (RFP Attachment 12) shall be submitted in CD-R or DVD-R (write one/read only) (2 copies). The information submitted via CD-R or DVD-R shall be in .xls file format; PDF format will not be accepted.

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

(1) The RFP proposal package used to submit the proposal must show the time and date specified for receipt. Proposals shall be submitted in a 3-ring binder with each of the volumes separately tabbed and identified. Each volume shall be marked with the RFP number, the offeror’s name and address, and the number of the Volume, i.e. I, II, III, IV or V. Proposals shall be in the English language and all monies shall be proposed in United States whole dollars.

(2) Print shall be no smaller than a font size of 12 with single line spacing. Paper size shall be on 8 1/2 x 11 inch paper, excluding any drawings, diagrams, supporting illustrations, charts, graphs, or spreadsheets which shall be on 8 ½ x 17 inch paper. Double-sided printing shall count as two (2) pages. Charts, graphs, drawings, diagrams, supporting illustrations, or spreadsheets may be on fold-out pages, but must fold with the page size specified and will count as one page and shall not be greater than 11” x 17”. Margins shall be no smaller than 1 inch and each page within a volume (written and electronic copies) shall be numbered consecutively. Do not include elaborate formats, bindings or color presentations.

(3) The page limitation for Volume II, Written Technical Proposal, is fifty (50) pages. The page limitation includes any charts, graphs, drawings, diagrams, supporting illustrations, spreadsheets, etc. but excludes any cover page, table of contents or list of acronyms (if utilized). 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. Offerors are cautioned that any pages that exceed the page limitation shall not be read but shall be removed and either retained in the contract file without being considered in the evaluation or sent back to the offeror. Page limitations may be placed on responses to Evaluation Notices (ENs), if issued. The specified page limits for EN responses will be identified in the letters forwarding the ENs to offerors or on the EN form itself.

(4) Limitation for Volume II (Written Technical Proposal), Subfactor One: System Engineering, Integrated Master Schedule (IMS) with rationale submitted in Microsoft Project 2010 Gantt Chart format shall not exceed 300 lines (landscape orientation), in no less than 8-point font, and not printed double-sided. The IMS Gantt Chart is not counted as part of the Written Technical Proposal’s 50 pages. No page limitation is defined for the IMS Gantt Chart. All rationale IMS narrative shall be included as part of the 50-page written technical proposal.

(5) Each page containing proprietary information should be so marked. Each page should contain the following legend at the bottom of each sheet:

SOURCE SELECTION INFORMATION -- SEE FAR 2.101 and 3.104

FOR OFFICIAL USE ONLY

(6) Volume III, Past Performance: To permit the Past Performance Evaluation Team to conduct its assessment more efficiently, we request that offerors submit their Volume III, Past Performance information so that it is received fifteen (15) calendar days prior to the required due date for proposals referenced in Block 9 on the face page of the RFP by mail to:

AFLCMC/WNKABB, ATTN: Sandra Harvey or Philip Earthly, 235 Byron Street, Ste 19A, Bldg. 300, Robins AFB, GA 31098-1670. Past Performance Information may be hand-delivered directly to Contracting Officer/Buyer. Failure to submit Volume III by the earlier date will not result in offeror disqualification.

Offerors are cautioned that Robins Air Force Base has visitor control procedures requiring individuals not affiliated with the installation to obtain a visitor pass prior to entrance. Some delay should be anticipated when hand-delivering proposal packages. Offerors should allow for sufficient time to obtain a visitor’s pass and arrive at the specified office that has been coordinated with Sandra Harvey, Philip Earthly, or Crystal Crawford PRIOR to the time specified for receipt of proposals.

Contact Sandra Harvey (478) 926-0156, Philip Earthly (478) 222-8330, or Crystal Crawford (478) 327-7467 to coordinate all hand-delivered proposals.

B. Communications Exchanges of source selection information between the Government and offerors after submission of the initial proposal packages will be controlled by the Contracting Officer. E-mail may be used to transmit such information preferably with the e-mail being sent encrypted, and must include the statement “Source Selection Information – See FAR 2.101 and 3.104” in the subject line of the e-mail. Otherwise, source selection information may be transmitted via direct mailing. In order to facilitate the sending and receiving of encrypted e-mails, offerors must use MS Outlook e-mail configured to support encryption or a different e-mail product that is S/MIME compatible and configured to support encryption. If you intend to submit your source selection information via encrypted e-mail, you will need to contact the PCO/Buyer indicated on the face page of the solicitation prior to that first submittal to coordinate the exchange of certificates used for encryption. To ensure the process is working correctly, send a test encrypted message first (without including any source selection information). If an offeror’s computer system cannot support encryption technology, the offeror shall send the Contracting Officer correspondence at the time that they submit their proposal stating they accept the risk of sending and receiving unencrypted electronic mail if they choose to utilize unencrypted e-mail as a channel of communication.

C. Volume I, Completed RFP (including RFP Attachment 1, Cross Reference Matrix)

(1) Volume I shall consist of the completed (excluding Section B of the Schedule) and signed RFP with a cover letter delineating any exceptions taken to the RFP terms and conditions with accompanying rationale. However, offerors are cautioned that any noncompliance with the terms and conditions of the RFP may cause their proposal to be determined noncompliant and therefore not considered eligible for award. Offerors shall ensure that all clauses and provisions that require “fill-in” information are appropriately completed. Proposed unit costs (to included target cost and target cost of money) and unit prices associated with the applicable contract line items and sub-line items shall not be entered in the Schedule of the RFP; rather, they shall be entered in RFP Attachment 9, Excel Price Model (see paragraph G for instructions). Any costs/prices entered in Schedule B will not be considered, and only those costs/prices entered in RFP Attachment 9, Excel Price Model shall be considered.

(2) The offeror shall fill out the Cross Reference Matrix at RFP Attachment 1 indicating where in their proposal the information can be found as it relates to the RFP. The Cross Reference Matrix will be utilized as a tool to show critical interrelationships and dependencies among Section L (Instructions to Offerors), Section M (Evaluation Basis for Award), the Statement of Work (SOW), the Performance Specification, the CLINs or Sub-CLINs, and the Contract Data Requirements Lists (CDRLs). The Cross Reference Matrix will help an offeror ensure they have responded to all of the evaluation criteria and proposal submittal requirements identified in the solicitation. If the matrix conflicts with any other requirement, direction, or provision of this solicitation, the other reference shall take precedence over the matrix. Additionally, to the extent the matrix discloses details as to the manner by which the Government intends to evaluate the offeror’s proposals for award, Section M references in the matrix are for informational purposes only, and the Government shall be obligated to evaluate proposals solely in conformance with Section M of the solicitation.

(3) The Government intends to award without discussions, but reserves the right to conduct discussions if determined necessary. Any discussions will be conducted in accordance with FAR 15.306. Proposals must be received by AFLCMC/WNKABB: Attention: Sandra Harvey or Philip Earthly or Crystal Crawford, no later than 4 P.M. Eastern Standard Time on DATE (will be filled in at Final RFP)

D. Volume II, Written Technical Proposal

The written technical proposal shall be clear, concise, and include all the information required by this provision in sufficient detail for effective evaluation. Offerors shall 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 are advised that the Government will base its evaluation of the technical proposals on the information presented herein; offeror’s shall not assume that the Government has prior knowledge of their capabilities, work processes, facilities or experience.

The following information shall be provided in the written technical proposal and will be evaluated to assess technical acceptability in accordance with Section M - Evaluation Basis for Award.

(a) The technical proposal shall address each of the following subfactors describing the offeror’s proposed approach to performing the requirements set forth in the Performance Specification and Statement of Work.

(b) For each subfactor, the offeror shall identify any risks associated with the proposed approach and actions the offeror will take to mitigate the identified risks. If no risks or mitigation actions are identified in the offeror’s technical proposal, the Government will interpret such to mean that the offeror does not consider that there are any risks associated with its proposed approach.

Subfactor One: SYSTEMS ENGINEERING The offeror’s written technical proposal shall provide detailed narrative with supporting documentation, such as (but not limited to) charts, diagrams, figures, graphs, and supporting illustrations to demonstrate that the offeror’s technical approach will meet the Performance Specification and Statement of Work paragraph requirements as follows:

Unit Under Test (UUT) Analysis Risk Mitigation Plan. The offeror’s written technical proposal shall provide a detailed narrative with supporting documentation to provide a risk mitigation plan to address the analysis of data in the development of the UUT Test Requirements Analysis Report required by Statement of Work, Paragraph 4.1.1(a). The risk mitigation plan shall address the following UUTs:

a) Multi-Purpose Rotary Launcher (MPRL) (B-1B)

b) Conventional Bomb Module (CBM) 28-Station (B-1B)

c) 1760 Enhanced Conventional Bomb Module (SECBM) 10-Station (B-1B)

d) Common Weapons Interface Unit (CWIU) (B-1B)

e) B-1B On-Aircraft SMS testing (B-1B)

f) SUU-67/A Pylon Disconnect On-Aircraft (part of on-aircraft SMS testing) (B-52H)

g) Pylon Assy., B-52 Conventional Weapons Integration (B-52H)

h) Conventional Rotary Launcher (CRL) 1760 (B-52H)

i) Cluster Bomber Rack (CBR) (B-52H)

j) On-Aircraft SMS testing (B-52H)

Functional Allocation & UUT Utilization Matrix. The offeror’s written technical proposal shall provide a functional allocation of BAT Core Tester hardware and software Configuration Items (CIs) IAW Performance Specification, Paragraph 3.1.2, identification of non-developmental and developmental CIs, and potential impact to operating temperature requirements IAW MIL-PRF-28800F invoked by paragraph 3.1.16 of the BAT system performance specification, and a UUT Utilization Matrix of the identified CIs. The UUT Utilization Matrix is not required to cover the UUTs listed in the previous bullet.

Integrated Master Schedule with Rationale. The offeror shall submit a detailed preliminary Integrated Master

Schedule (IMS) for the Increment 1 Engineering and Manufacturing Development (EMD) phase per Statement of Work paragraph 4.1, to include all subparagraphs. The proposed IMS shall communicate how the contractor shall meet the Increment 1 Production Readiness Review within 27 months after contract award. The offeror shall identify and define those assumptions used when constructing the IMS. The proposed IMS shall include the start date, duration, dependencies, and the end date for schedule activities, events, and milestones. Additionally, the proposed IMS shall identify the critical path for Increment 1 EMD and provide a schedule rationale narrative identifying, explaining, and providing mitigation plans for moderate and high risk activities and events along the critical path. The schedule rationale narrative shall be part of the 50-page written technical proposal. The proposed IMS shall address two levels for each of these activities; additional levels are allowable for higher risk activities on the critical path for Increment 1 EMD. The proposed IMS shall include top level schedule activities, events and milestones for Increments 2 and 3 with the duration of days from exercise of contract option to Critical Design Review (CDR) and Production Readiness Review (PRR) IAW SOW paragraphs 5.1.2, 5.1.7, 6.1.2, and 6.1.7, respectively. The proposed IMS is for all 3 increments and shall not exceed 300 lines overall length, shall be depicted in Gantt format and provided in hardcopy and Microsoft Project 2010 format.

Subfactor Two: RELIABILITY The offeror’s written technical proposal shall provide detailed narrative with supporting documentation, such as (but not limited to) charts, diagrams, figures, graphs, and supporting illustrations to demonstrate the offeror’s technical approach will meet the reliability requirements in Performance Specification, Paragraph 3.2.2.2.1. Specifically, the technical proposal shall address the following:

Reliability Tasks. The offeror’ s written technical proposal shall identify reliability tasks and activities to be conducted and methods to be used, with rationale behind why those tasks, activities, and methods were chosen, and the key resources required to perform the tasks and activities as required in Statement of Work, Paragraph 3.4(d).

Configuration Item Reliability Risk Mitigation. The offeror’s written technical proposal shall identify a minimum of five (5) configuration items that pose the greatest reliability risk, with rationale to explain why it is a risk and how design for reliability will be applied to mitigate that risk, in accordance with the Statement of Work, Paragraph 3.4(f).

Subfactor Three: CYBERSECURITY The offeror’s written technical proposal shall provide detailed narrative with supporting documentation, such as (but not limited to) charts, diagrams, figures, graphs, and supporting illustrations to demonstrate that the offeror’s technical approach will meet the Performance Specification and Statement of Work paragraphs as follows:

Cyber-Secure Design. The offeror’s written technical proposal shall address how the offeror’s proposed BAT System architectural design will meet the requirements in Performance Specification Paragraphs 3.1.20.1 through

3.1.20.9 and 3.20(c).

Cyber-Secure Development Environment. The offeror’s written technical proposal shall address how the offeror’s proposed approach will ensure a cyber-secure development environment, in accordance with the Statement of Work, Paragraph 3.5.3.5.

BAT Bidder’s Data Library: A set of technical data documents, referred to as the BAT Bidder’s Data Library, will be made available to each offeror. The data library contains weapon system UUT technical orders, drawings, parts lists, and test requirements and procedures as reference material for review, analysis, and proposal development. To request the BAT Bidder’s Data Library, offerors shall submit an e-mail request to Sandra Harvey, Philip Earthly, or Crystal Crawford with a completed DD FORM 2345, Militarily Critical Technical Data Agreement. To receive the BAT Bidder’s Data Library, all interested companies must be on the DoD Certified Contractor Access List. BAT Data Library CDs will only be shipped via Fed-Ex to the physical address of the Data Custodian identified on the approved DD Form 2345. For further information, see:

http://www.dlis.dla.mil/jcp

Email: Sandra.Harvey.2.@us.af.mil Email: Philip.Earthly.1@us.af.mil Email: Crystal.Crawford.1@us.af.mil

E. Volume III - Past Performance:

(1) The offeror shall utilize the Past Performance Information (PPI) Tool in order to submit Volume III, Past Performance.

The offeror/joint venture members shall submit past performance information in accordance with the format contained in the RFP Attachment 3 and the following paragraphs. The evaluation of the offeror’s/joint venture members past performance will not include the past performance of any subcontractor(s), vendors or suppliers, even though they may perform major or critical aspects of this requirement. In considering past performance, the Government will not consider “Key Personnel” of the offeror.

(2) The requested past performance information shall be provided in a separate volume (3-ring binder) labeled "Volume III - Past Performance.”

a.) Volume III – Past Performance shall contain: 1) A table of contents; 2) a summary page describing the proposed offeror’s nature of work; and 3) if applicable, a Client Authorization Letter for commercial contracts (see RFP Attachment 4).

b.) Each offeror/joint venture member shall utilize the PPI Tool to complete information for up to three (3) active or completed efforts with preferably at least one year of performance history, going back no further than the past ten (10) years, from the issuance date of the RFP, that the offeror considers relevant in demonstrating its ability to perform the proposed effort. If the total number of such efforts exceeds three (3), each offeror/joint venture member shall address its three (3) most recent and relevant efforts.

c.) The offeror's/joint venture member’s past performance information may include data on efforts performed by other predecessor companies, affiliates, other divisions or corporate management if such was provided for evaluation and if the offeror’s/joint venture member’s past performance volume demonstrates the company, affiliate, or division will provide the offeror/joint venture member with resources for the instant proposed effort, such as workforce, management, facilities, or other capabilities demonstrating direct and meaningful involvement in the performance of the instant proposed effort. The information provided in the PPI Tool shall clearly indicate the division or corporate organization that performed or is presently performing the effort. Efforts listed may include those with the Federal Government, state and local governments or their agencies, and commercial customers.

d.) If the contract you are submitting is an ordering type contractual vehicle (e.g., an Indefinite Delivery “D” type contract per FAR 16.5), only after issuance of a delivery/task order is performance considered to have occurred. Given this, an individual order (or orders) under the basic ordering contract shall be submitted in lieu of just the basic ordering contract itself.

Each submitted order shall be considered a separate effort unless information is provided indicating follow-on or a series of orders for continued performance of the same scope and such can be verified by the user/customer. In this event, such submitted multiple orders shall be considered as a single effort for evaluation purposes. Absent this information and verification, each submitted order shall be considered a separate effort. Basic ordering contracts will not be evaluated. For all submittals, the performance on efforts identified shall be restricted to those completed or ongoing during the past ten (10) years from the issuance date of this RFP. It is recognized for this effort that design, development and production may have been accomplished via separate efforts to include delivery or task type orders and Definite-Quantity “C” type contracts. Each submitted C-type contract shall be considered a single effort unless information is received indicating the effort is for a phase of design, development or production.

e.) On the three (3) associated contracts submitted in Volume III, Past Performance, include relevant information in the PPI Tool concerning the offeror’s/joint venture member’s compliance with FAR 52.219-8, Utilization of Small Business Concerns, or FAR 52.219-9, Small Business Subcontracting Plan, if these clauses are or were contained in the contract.

(Please note that FAR 52.219-8 applies to ALL businesses, whereas FAR 52.219-9 only applies to large businesses.) When subcontracting possibilities existed on the contracts submitted by the offeror/joint venture member, address whether or not the offeror/joint venture member awarded subcontracts to small business concerns, veteran-owned small business concerns, service-disabled veteran-owned small business concerns, HUBZone small business concerns, small disadvantaged business concerns, and women-owned small business concerns to the fullest extent consistent with efficient contract performance. If none of the submitted contracts included these clauses, whenever subcontracting possibilities existed in the performance of these contracts, address whether or not it was the offeror’s/joint venture member’s policy to utilize small business concerns, veteran-owned small business concerns, service-disabled veteran-owned small business concerns, HUBZone small business concerns, small disadvantaged business concerns, and women-owned small business concerns to the fullest extent consistent with efficient contract performance.

(3) The offeror/joint venture member shall focus its information in the PPI Tool so that it clearly correlates past performance with the requirements of this RFP. The information must clearly describe the relevance of the effort to the work proposed.

Provide the most current information for the POCs identified in the PPI tool. In addition to the information in the PPI Tool, each offeror/joint venture member shall complete a separate Relevancy Assessment (RFP Attachment 8) for each effort identified in the PPI tool for evaluation.

(4) If problems were encountered during the performance of the identified efforts, provide evidence of the ability to isolate the root causes of problems and include in the PPI Tool a description of programs or actions taken to resolve those causes.

Problems not addressed in the information provided in the PPI Tool, but found by the Government during the evaluation of the information in this volume, will be assumed to still exist. Note: In the case of Contractor Performance Assessment Report System (CPARS), if your input has already been provided and the rationale/circumstances have not changed, DO NOT repeat the information here.

(5) The Past Performance Questionnaire (see RFP Attachment 7) will be one means used by the Government to obtain past performance information. The Government reserves the right to change, alter, and/or supplement the questionnaire without further notice to the offeror(s)/joint venture member(s). The offeror/joint venture member shall send out - and track the completion - of the Past Performance Questionnaires to each of the offeror’s/joint venture member’s, POCs identified in the PPI Tool. The responsibility to send out and track the completion of the Past Performance Questionnaires rests solely with the offeror/joint venture member - i.e., it shall not be delegated to any other entity. The Transmittal Letter (see RFP Attachment

6) shall be used by the offeror/joint venture member in sending out the Past Performance Questionnaires. The offeror/joint venture member shall exert its best effort to ensure that at least two POCs per relevant effort submit a completed Past Performance Questionnaire directly to the Government not later than the date established in the RFP for receipt of proposals. Each of the offeror’s/joint venture member’s POCs may submit their completed Past Performance Questionnaire either electronically or by mail. If sending electronically, follow the procedures outlined in Paragraph (B) above, and e-mail to: Sandra.Harvey.2@us.af.mil or Philip.Earthly.1@us.af.mil. If mailing, the POCs may return the completed questionnaires via mail directly to:

AFLCMC/WNKABB

ATS and SE&V Division Major Programs Contracting Office Attn: Sandra Harvey or Philip Earthly 235 Byron Street Suite 19A Robins AFB, GA 31098-1813

If mailing, the outside envelope must be marked as follows:

NOTE: TO BE OPENED BY ADDRESSEE ONLY

The completed questionnaires should be contained in a second envelope marked with the mailing address and the following legend:

SOURCE SELECTION INFORMATION - See FAR 2.101 and 3.104

Once the Past Performance Questionnaires are completed by your POCs, the information contained therein shall be considered source selection sensitive and shall not be released to you, the offeror/joint venture member. Therefore, any exchange/contact between the offeror/joint venture member and its own POCs in regards to comments made on the questionnaire is not permitted. Questionnaires shall be sent, and best efforts made, to ensure timely completion and submission directly back to the Government from at least two of the following (in descending order of availability):

(a) Procuring Contracting Officer/Contract Negotiator or equivalent

(b) Program/Project Manager, or equivalent

(c) Administrative Contracting Officer/Contract Administrator or equivalent

(d) Other (As specified in the PPI Tool)

(6) In the event commercial contracts are presented as past performance sources of information, a client authorization letter shall be issued to those commercial POCs requesting/authorizing them to complete a Past Performance Questionnaire. A sample client authorization letter is attached to this RFP (see RFP Attachment 4). The offeror/joint venture member is required to send a client authorization letter with the Past Performance Questionnaire(s) to each POC on commercial contracts. A separate copy of client authorization letter(s) for each commercial contract shall be included in the offeror’s Past Performance submission for the Government’s use in case additional questionnaires need to be sent by the Government after RFP due date.

(7) The Government may conduct follow-up discussions with any of the people identified in the PPI Tool or in the offeror’s joint venture member’s Past Performance Volume. The Government is not limited to review of the information provided in the offeror’s/joint venture member’s Past Performance Volume. The Government may obtain other information by sending out additional questionnaires or through other sources. Past performance information shall be obtained from the Government’s Federal Awardee Performance and Integrity Information System (FAPIIS) and may be obtained from the Past Performance Information Retrieval system (PPIRS). The Government reserves the right to use past performance from other sources such as the Defense Contract Management Agency (DCMA), Fee Determining Officials, or commercial sources.

(8) RFP Attachments 8 and 7, the Relevancy Assessment and Past Performance Questionnaires, respectively, shall include the following legend at the top and bottom of the pages:

SOURCE SELECTION INFORMATION - See FAR 2.101 and 3.104

F. Volume IV- Small Business Concern Utilization Plan The offeror/joint venture member shall submit a Small Business Concern Utilization Plan in a separate volume (i.e., 3-ring binder) labeled "Volume IV – Small Business Concern Utilization Plan.” The Small Business Concern Utilization Plan is required from all offerors/joint venture members, including small businesses and companies with master, individual, commercial, and/or comprehensive subcontracting plans. The offeror/joint venture member shall include only the first tier of subcontractors for this effort. Offerors/joint venture members are advised that the Small Business Utilization Plan is not the same as the Small Business Subcontracting Plan required by FAR 52.219-9.

Large business offerors shall not utilize the Small Business Subcontracting Plan in the place of the Small Business Utilization Plan. In the performance of this resultant contract, identify the following:

i) The extent of participation of proposed Small Businesses to include service-disabled veteran-owned small business concerns, HUBZone small business concerns, small disadvantaged business concerns, and woman-owned small business concerns, when subcontracting possibilities exist; and,

ii) The description of the subcontracted work these proposed firms are to perform, the company names/CAGE codes planned for use in the performance of this resultant contract along with the associated goals expressed in terms of percentages of the total planned subcontracted dollars.

iii) If limited or no subcontracting possibilities exist for these Small Businesses and socio-economic entities, provide rationale for such. Offerors/joint venture members are cautioned against only acknowledging a goal is not met, if applicable. Rather, adequate rationale includes specific reasons why a goal is unmet and any actions being taken to increase any unmet goals. Additionally, if the offeror/joint venture member is a small business concern, it should include the work it will be performing when calculating the goals for your Small Business Concern Utilization information.

G. Volume V, Cost/Price Proposal The Offeror shall submit the following with its Volume V, Cost/Price Proposal:

1) Table of Contents, Glossary, Definitions and Points of Contact

A detailed table of contents A glossary of all abbreviations and acryonyms used, with an explaination for each Definitions as necessary List of Major/Minor Subcontractors and Vendors and their estimated total price The name, addresses, telephone number, and email address of the Offeror’s (and the offeror’s subcontractors and teaming partners) cognizant Defence Contract Management Agency (DCMA) Administrative Contracting Officers (ACO) and cognizant Defense Contract Audit Agency (DCAA) offices

Date of current Forward Pricing Rate Agreement (FPRA) / Forward Pricing Rate Recommendation (FPRR) for Prime and Major Subcontractors

Rates and factors for Prime and Major Subcontractors valued more than $750,000 (for the entire effort to include options)

2) Synopsis of current Estimating, Purchasing, and Accounting Systems and Adequacy Determination

The Offeror shall provide a summary description of the Offeror’s standard estimating system or methods, current policies, and/or new policies. The Offeror shall state whether the estimating system and new policies have been reviewed by the Government and shall provide evidence of review and/or Administrative Contracting Officer approval. The Offeror shall provide any known/cited estimating system deficiencies and identify any deviations from the Offeror’s established/standard estimating procedures used in preparing this proposal. For known/cited estimating system or methods non-compliances, provide a schedule and description of corrective actions the offeror is taking to eliminate the non-compliance issues.

The Offeror shall provide a summary description of the Offeror’s purchasing system or methods. The Offeror shall state whether the purchasing system has been reviewed by the Government and provide evidence of review and/or Administrative Contracting Officer approval. The Offeror shall provide any known/cited purchasing system deficiencies and identify any deviations from the Offeror’s established/standard purchasing procedures used in preparing this proposal. For known/cited purchasing system or methods non-compliances, provide a schedule and description of corrective actions the Offeror is taking to eliminate the non-compliance issues.

In accordance with FAR 16.301-3(a) (3) and 9.104-1(e), the Offeror shall utilize an accounting system that is adequate for determining costs applicable to the contract. The Offeror shall provide a summary description of the Offeror’s accounting system and state whether it is compliant with Generally Accepted Accounting Principles. The Offeror shall also state whether the accounting system has been reviewed and approved by the Government and provide evidence of the review and approval by DCAA / DCMA. The Offeror shall provide any known/cited accounting system deficiencies and identify any deviations from the Offeror’s standard procedures in preparing this proposal. For known/cited accounting system or methods non-compliances, provide a schedule and description of corrective actions the Offeror is taking to eliminate the non-compliance issues.

3) Synopsis of Current Cost Accounting Standards Disclosure statement and Adequacy Determination

The Offeror shall provide a summary description of the Offeror’s current Cost Accounting Standards disclosure statement.

The Offeror shall state whether the current Cost Accounting Standards disclosure statement has been reviewed by the Government and provide evidence of review and/or Administrative Contracting Officer approval. The Offeror shall provide any currently known/cited Cost Accounting Standards non-compliances and identify any deviations from the Offeror’s Cost Accounting Standards disclosure statement used in preparing this proposal. For known/cited Cost Accounting Standards non-compliances provide a schedule and description of corrective actions the Offeror is taking to eliminate the non-compliance issues.

4) Cost or Pricing Data Requirements It is anticipated that pricing of this action will be based on adequate price competition; therefore, offerors are not required to submit certified cost or pricing data. However, if after receipt of proposals it is determined that adequate price competition does not exist, certified cost or pricing data (see FAR 15.406-2, Certificate of Current Cost or Pricing Data) shall be required.

Elemental Cost Breakouts: Breakouts by individual cost elements shall be provided for proposed unit costs applicable to CLINs 0001, 1001, and 2001 for the Prime offeror, and all subcontractors whose contract effort is valued at or above $750,000 (hereinafter referred to as Major Subcontractors), to assist in the determination of realism. Elemental cost breakouts shall be provided as part of the offeror’s proposal, and shall be in .xls file format with live working formulas as provided in RFP Attachment 12, Excel Cost Model; PDF format will not be accepted. Offerors should refer to the format indicated in Table 15-2 of FAR 15.408 for instructions on submitting acceptable elemental cost breakouts.

NOTE: Certified Cost or Pricing Data Is Not Required unless it is determined that adequate price competition does not exist.

In support of the elemental cost breakouts, all offerors (Prime and Major Subcontractors) who have neither a FPRA nor a FPRR shall submit the following items/information as part of their proposal. If any of the items/information are not available for a particular offeror, it shall be noted in the offeror’s response to the RFP.

1) Previous three years’ actual historical rates for each individual cost element used in developing the proposed unit costs

2) Breakout of actual expenses included in the indirect cost pools and the respective bases, from the previous three years

3) Breakout of the budgeted forecasts for the indirect pools and bases used in developing the proposed unit costs covering the entire contract period (Basic and Options)

4) Certified payroll verification, to include employee name and current labor rate, shall be provided in support of the proposed direct labor rates for year one. If year one proposed rates are not supported by current labor, offeror shall provide assumptions for hiring individuals, and labor rates that will be offered.

All information submitted in support of items 1-3 above shall be in .xls file format with live working formulas: PDF format will not be accepted.

It is the offeror’s/joint venture member’s responsibility to review all proposals submitted by any major subcontractor for accuracy and format. It is also the offeror’s/joint venture member’s responsibility to submit all major subcontractor proposed unit costs, major subcontractor elemental cost breakouts, and major subcontractor documentation in support of the elemental cost breakouts, as part of the offeror’s/joint venture member’s proposal. For any of the above-referenced information that a major subcontractor may not be willing to provide directly to the offeror/joint venture member, the offeror/joint venture member shall instruct the major subcontractor to provide that information directly to the Government in accordance with the terms and conditions of this solicitation. It is also the offeror’s/joint venture member’s responsibility to ensure that the offeror’s/joint venture member’s RFP Attachment 11, Total Resources Volume (WBS Breakdown) and RFP Attachment 12, Excel Cost Model, have corresponding hours, and that no discrepancies exist.

In accordance with (IAW) FAR 15.404-1(d), cost realism analysis shall be performed on cost reimbursement contracts such as CPIF. All offerors and subcontractors valued at equal to or more than $750,000 (for the entire effort to include Options) shall provide data other than certified cost and pricing data using spreadsheet Cost Formats A, B, and C (see RFP Attachment 12, Excel Cost Model) along with accompanying schedules, lists and narratives to substantiate the cost realism for all CPIF CLINs. Note for any subcontractors, to include minor subcontractors (with less than $750,000 in total costs), offerors shall include roll-up cost data on Cost Format A and C. If necessary, AFLCMC/WNKABB may request additional minor subcontractor cost data during discussions.

The Offeror’s cost proposal shall contain the proposed cost to the Government for performing the work described in the Statement of Work, the attached CDRLs, and additional CDRLs/data the Offeror proposes and references from the SOW for effective management of the program as proposed in the Offeror’s engineering volume. The Offeror’s proposal is presumed to represent its best effort in response to the solicitation. Any inconsistency, whether real or apparent, between promised performance and cost shall be explained in the proposal. Any significant inconsistency, if unexplained, raises a fundamental issue with the Offeror’s understanding of the nature and scope of the work required and ability to perform the contract and may be grounds for rejection of the proposal. The burden of proof as to the credibility of the cost proposal rests with the Offeror.

Price Reasonableness and Cost Realism The Offeror shall provide sufficiently detailed proposals to demonstrate price reasonableness and cost realism. The burden of proof for cost realism of proposed costs rests with the Offeror. The Offeror is responsible for ensuring that all Attachments contain no discrepancies and mirror each other (i.e. the Attachment 9 and Attachment 12 CLIN prices match and Attachment 12 and the Attachment 11 hours correspond).

Cost Formats A, B and C The Cost Formats (see RFP Attachment12, Excel Cost Model) contain the required set of Cost Format A’s linked to a Cost Format B and to a Total Cost Format C.

Cost Format A: Format A is a detailed cost breakdown by cost element showing the details of the proposed labor hours, labor rates, indirect rates and costs, and proposed fee/profit by GFY as shown in RFP Attachment 12. The offeror must show a summary of labor hours by labor categories, costs by each major cost element, and proposed fee/profit. All Format A worksheets shall be linked to the rates worksheet (Format B). All Format A worksheets shall be linked to the Cost Format A Total worksheet for the respective type CLIN, i.e. FFP, CPIF, and FPIS.

Cost Format B: A single worksheet (using the example format provided) shall be the source document for direct and indirect rates, and shall be linked into all worksheets involving computations of costs entailing rates and factors. This worksheet will include all proposed direct and indirect rates, estimating factors, etc. for each GFY. The purpose for linking a single Format B worksheet to all Format A worksheets is to facilitate the government’s evaluation of the proposed rates and to make Most Probable Cost (MPC) adjustments more straightforward.

Cost Format C: Format C is for Subcontractor/Vendor Cost/Price Summary Information. This information shall be provided by all Offerors in the format provided. If there are differences between costs/prices quoted by Subcontractor/Vendor to the Offeror and costs/prices proposed by the Offeror, the offeror shall provide a complete justification and explanation of the amount proposed by the offeror. Specifically address why the Offeror’s amount should be considered by AFLCMC/WNKABB to be more realistic than the amount of the Subcontractor/Vendor quote. Major/Minor Subcontractors over $750,000 are required to provide an Attachment 12 for their proposed costs.

To substantiate the Cost Formats the offeror shall, in an accompanying narrative (Word Doc), provide supporting data and the contractor’s rationale for the cost proposed, including subcontractor/vendor costs. The information should be sufficiently detailed to demonstrate the realism (CPIF CLINs) and reasonableness of proposed costs. This information shall at a minimum:

State whether proposed direct labor rates and indirect rates are covered by a FPRA. If covered by a FPRA provide the date of the agreement.

If an FPRA is not in place, provide the date of the applicable FPRP with supporting rationale addressing the basis for the proposed rates with your proposal. If there is no FPRA or FPRP applicable, provide the complete rationale addressing the basis for all proposed rates to include time sheets for each labor category bid and how the average rate is calculated, pool and base costs for each indirect rate or Cost Estimating Relationship (CER) showing how the rate was calculated. Each of these items shall be provided for the past three years and the forward projected average labor rates and pools/bases for FY16 – FY25. This information should also be provided for any subcontractors/vendors equal to or greater than $750,000 that do not have an FPRA or FPRP.

Address the rationale and approach to subcontracting and teaming arrangements.

5) Total Resources Volume (WBS Breakout)

Total Resources General Instructions This submission shall fully support all discreetly estimated resources proposed. It will be available to support the evaluations of proposals by the Technical and Cost/Price evaluators. This submission shall provide a clear depiction of all discreetly proposed resources regardless of whether these resources are provided by the Offeror or any tier of subcontractor. The Offeror is responsible for demonstrating in this submission that the appropriate resources are being proposed to meet the RFP requirements. The Offeror shall include proposed cost, by Government Fiscal Year (GFY, October – September) and detailed by Contract Line Item Number (CLIN) and Work Breakdown Structure (WBS) elements.

The electronic copy of this volume shall be in .xls file format to aid in the evaluation. PDF or other format will not be accepted. All formulas used in the worksheets shall be clearly visible in the individual cells and verifiable. The use of external links (to source data not provided to the BAT Program) of any kind is prohibited. This submission shall not contain macros or hidden cells. The BOE Summary shall not be locked/protected or secured by passwords. The offeror will be required to extend Attachment 11, Total Resource Volume (WBS Breakdown), to the point that the lowest level WBS element is less than 10,000 manhours, and cannot extend past five (5) levels. The offeror may insert additional rows to capture labor catagories.

Cost summary information is to be provided for each area as described below. The Offeror and each subcontractor with value in excess of $750,000 shall provide a breakout of proposed costs for all CWBS items for each element of cost. This breakout shall be provided in Then Year dollars (TY$) and sum to the total contract price.

Total Resources BOE Material Summary The Offeror shall complete this Exhibit using RFP Attachment 11, Total Resources Volume (WBS Breakdown). Offerors are required to provide a BOE Material Summary that clearly lists the Types and Quantities of Material resources proposed regardless of source (prime and subcontractors) by the SOW and CWBS time-phased by GFY. Clearly list the types & quantities of materials proposed. This summary should be an unburdened version of the Priced Bill of Material, which offerors shall provide separately in Volume IV Cost/Price as stated in paragraph (9). This summary shall be provided in .xls file format to facilitate manipulation of the data during evaluation; otherwise, contractor format is acceptable.

Total Resources BOE Labor Summary The Offeror shall complete this Exhibit using RFP Attachment 11, Total Resources Volume (WBS Breakdown), as the template. This Exhibit shall provide a clear depiction of all discreetly proposed resources regardless of whether these resources are provided by the Offeror or any tier of subcontractor. The Offeror is responsible for demonstrating that the appropriate resources are being proposed to meet the RFP requirements. On the BOE Labor Summary Exhibit provide the CWBS and CWBS dictionary to level 4, based on the MIL-STD-881C that corresponds to SOW paragraphs listed in the columns of the Exhibit. Then, list the total hours proposed on the table for each GFY. Hours for sublevels 4 through 6 should be totaled and entered into their parent level 3 row to reflect the cumulative number of hours for each level 3 task.

Similarly, hours for sublevels 3 through 6 should be totaled and entered into their parent level 2 row to reflect the cumulative number of hours for each level 2 task. The top table shall total all of the GFY tables below. Labor for CDRLs shall be categorized as follows:

Program Data: A001, A002, A004, A005, A006, A007, A008, A009, A00A, A00B, A00C, A00D, A00F, A00G, B001, B002, B008, B009, B00A, B00C, B010, B011, B012, B013, B014, B015, B016, B017, B018, B00J, B00M, B00N, B00P, B00Q, B00R, B00S, B00T, B00U, B00V, B00W, B00X, B00Y, B00Z, C001, C002, C003, C004, C005, C006, C007, C008

UUT TPS Data: B003, B004, B007, B00E, B00F, B00G, B00L Core Tester Data: B003, B004, B005, B006, B007, B00B, B00E, B00F, B00G, B00K, B00L

Contractor Labor Categories Offerors are required to provide a table of Labor Category descriptions that clearly lists the duties and qualifications of the proposed labor categories regardless of source (prime and subcontractors). The Offeror shall complete this Exhibit using RFP Attachment 11, Total Resources Volume (WBS Breakdown). Otherwise contractor data format is acceptable.

Narrative Basis of Estimate At a minimum, offerors shall describe the approaches for providing products and services defined in each SOW paragraph listed…