DRAFT_BAT_Section_L_-_As_of_5_Feb_16.pdf

DRAFT – BAT SECTION L

INSTRUCTIONS TO OFFERORS

As of 5 Feb 16

A. Proposal Instructions The following instructions cover the preparation and submittal of the offeror’s proposal for this solicitation. To assure 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 shall submit only one (1) proposal for the proposed effort. 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:

VOLUME PAGE LIMTS NUMBER OF COPIES DESCRIPTION

I N/A 2 Paper/1 Electronic* Completed RFP and Clauses Including Cross Reference Matrix (CRM)

II 50 2 Paper/2 Electronic* Written Technical Proposal

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

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

V N/A 2 Paper/1 Electronic* Cost/Price Proposal

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.

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

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

(2) Proposals shall be submitted in five (5) 3” 3-ring notebooks with each of the volumes, or sections, separately tabbed and identified. Note: The paper copies required of each volume within the proposal are stated in Paragraph A above. The electronic copy of the volumes shall be submitted in Microsoft Windows ® 7. All documents shall be submitted in Microsoft Office Suite ®2010 (Word, Excel, Project, PowerPoint, Access, etc.) formats.

(3) Print shall be no smaller than a font size of 12 with single line spacing and should be on 8 1/2 x 11 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 shall be numbered consecutively. This applies to written and electronic copies of the proposal. Do not include elaborate formats, bindings or color presentations.

(4) 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 the cover page, table of contents or list of acronyms (if utilized). 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. Volumes I, III, IV and V do not have page limitations. 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. The aforementioned legend format requirements shall apply to both electronic copies and ENs, if issued.

(5) Limitation for Volume II, 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 10-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 is included as part of the 50-page written technical proposal.

(6) 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

(7) Submit PDF documents using only Adobe Acrobat X (10.0 or later). DO NOT SUBMIT any documents in PDF format that are copied as “images”. When creating PDF files, always create to enable textual search and copy functions.

NOTE: DO NOT SUBMIT documents using file suppression software, including (but not limited to) .zip format.

(8) Volume III, Past Performance: To permit the Past Performance Team to conduct its assessment more efficiently, we request that offerors submit their Volume III, Past Performance Information 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. Offerors are requested to submit Volume III, Past Performance Information, so that it is received (15) calendar days prior to the required due date for proposals. Failure to submit Volume III by the earlier date will not result in offeror disqualification.

Offerors are cautioned that Warner Robins Air Logistics Complex 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 or Philip Earthly PRIOR to the time specified for receipt of proposals. Contact Sandra Harvey (478) 926-0156 or Philip Earthly (478) 222-8330 to coordinate all hand-delivered proposals.

B. Communications Exchanges of source selection information after submission of the initial proposal packages between the Government and offerors will be controlled by the Contracting Officer. E-mail may be used to transmit such information only if the e-mail can be 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 and Clauses (including Cross Reference Matrix)

(1) Volume I shall consist of the completed 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 unacceptable and therefore not considered eligible for award. Offerors shall ensure that all clauses and provisions that require “fill-in” information are appropriately completed including the proposed prices associated with the Contract Line Item Number (CLINs) or Sub-Contract Line Item Number (Sub-CLINs) in the Schedule of the RFP. All CLINs shall be either completed with a price or designated as Not Separately Priced (NSP).

(2) The offeror shall fill out the cross reference at RFP Attachment X indicating where in their proposal the information can be found. The Cross Reference Matrix will be utilized as a tool to show critical interrelationships and dependencies among the requirements document Section L (Instructions to Offerors), Section M (Evaluation Basis for Award), the Statement of Work (SOW), the Performance Specification, the Contract Line Item Number (CLIN), and the Contract Data Requirements List (CDRL). 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.

D. Volume II, Technical Proposal

The 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 (which includes the consideration of technical risk) 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.

1. Technical Factor

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

Unit Under Test (UUT) Analysis Risk Mitigation Plan. The offeror’s 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 Cluster Bomb Rack (CBR) (B-52H)

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

Functional Allocation & UUT Utilization Matrix. The offeror’s 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 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) IAW SOW Paragraph 3.8.2.2 for the Increment 1 EMD phase per SOW 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 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 proposed IMS shall address two levels for each activity; additional levels are allowable for higher risk activities on the critical path. The proposed IMS shall not exceed 300 lines overall length, via in Gantt format and shall be provided in hardcopy and Microsoft Project 2010 format.

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

Reliability Tasks. The offeror’ s 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 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 technical proposal shall provide detailed narrative with supporting documentation, such as (but not limited to) charts, diagrams, figures, graphs, and illustrations to demonstrate that the offeror’s technical approach will meet the Performance Specification and Statement of Work paragraphs.

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

Cyber-Secure Development Environment. The offeror’s 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, submit an e-mail request to Sandra Harvey and Philip Earthly 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. For further information, see: http://www.dlis.dla.mil/jcp

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

E. Volume III - Past Performance:

(1) The offeror shall submit Present and Past Performance Information for itself in accordance with the format contained in the “FACTS Sheet” (See RFP Attachment #) and the following paragraphs. The evaluation of the offeror’s present and past performance will not include the present or past performance of any subcontractor(s), vendors or suppliers, even though they may perform major or critical aspects of this requirement.

(2) The requested present and past performance information shall be provided in a separate volume (i.e., 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 nature of work; and 3) if applicable, a Client Authorization Letter for commercial contracts.

b.) Each offeror shall complete a separate FACTS Sheet for each active or completed contract with preferably at least one year of performance history, going back no further than the past ten (10) years, that the offeror considers relevant in demonstrating its ability to perform the proposed effort. If the total number of such contracts exceeds three (3), each offeror shall address its three (3) most recent and relevant contracts.

c.) Each offeror shall submit three (3) contracts of separate efforts in the areas of design, development, and production, of at least one (1) Mission Design Series (MDS). Each submitted contractual effort shall be considered a separate effort unless information is provided indicating the contract is for an additional area of scope of design, development and/or production, and such can be verified by the user/customer. Each contract will be counted in aggregate for evaluation purposes. For all submittals, the performance on separate aggregate efforts identified shall be restricted to those completed or ongoing during the past ten (10) years from the issuance date of this

RFP.

d.) The offeror's present and 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 past performance volume demonstrates the company, affiliate, or division will provide the offeror 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 FACTS Sheets shall clearly indicate the division or corporate organization that performed or is presently performing the contract. Contracts listed may include those with the Federal Government, state and local governments or their agencies, and commercial customers.

e.) 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 does performance occur. 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 a follow-on or 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. 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.

f.) On the three (3) contracts submitted in Volume III, Past Performance, include relevant information in the FACTS Sheet concerning the offeror’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, 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 and teaming contractors’ 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, if applicable, shall focus their FACTS Sheet responses so that they clearly correlate present and past performance with the requirements of this RFP. The FACTS Sheet responses must clearly describe the relevance of the effort to the work proposed. The answering space on the FACTS Sheet may be expanded so that the filled-in FACTS Sheet for each relevant contract covers no more than both sides of three (3) 8 ½ x 11 inch pages. (See paragraph fill-in of the FACTS Sheet.) Provide the most current information for the points of contact (POCs) identified on the FACTS Sheets.

(4) If problems were encountered during the performance of the identified contracts, provide evidence of the ability to isolate the root causes of problems and include in the FACTS Sheet a description of programs or actions taken to resolve those causes. Problems not addressed in the FACTS Sheet, 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 them here.

(5) The Present/Past Performance Questionnaire (see RFP Attachment #) will be one means used by the Government to obtain present/past performance information. The Government reserves the right to change, alter, and/or supplement the questionnaire without further notice to the offeror(s). The offeror shall send out – and track the completion of - the Present/Past Performance Questionnaires to each of the offeror’s, POCs identified in each FACTS Sheet. The responsibility to send out and track the completion of the Present/Past Performance Questionnaires rests solely with the offeror/joint venture and teaming contractor - i.e., it shall not be delegated to any other entity. The Transmittal Letter (see RFP Attachment #) shall be used by the offeror in sending out the Present/Past Performance Questionnaires. The offeror shall exert its best effort to ensure that at least two POCs per relevant contract submit a completed Present/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 POCs may submit their completed Present/Past Performance Questionnaire either electronically or by mail. If sending electronically, follow the procedures outlined in Paragraph (f) 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:

Support Equipment – Major Programs

AFLCMC/WNKABB

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

FOR OFFICIAL USE ONLY

Once the Present/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. Therefore, any exchange/contact between the offeror 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 your FACTS Sheet)

(6) In the event commercial contracts are presented as present/past performance sources of information, a client authorization letter shall be issued to those commercial POCs requesting/authorizing them to complete a Present/Past Performance Questionnaire. A sample client authorization letter is attached to this RFP (see RFP Attachment #). The offeror is required to send a client authorization letter with the Present/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 Present/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 FACTS Sheets or in the offeror’s Present/Past Performance Volume. The Government may obtain other information by sending out additional questionnaires or through other sources.

(8) RFP Attachments # and #, the FACTS Sheet and Present/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.104FOR OFFICIAL USE ONLY

RFP attachments X, X, and X do not require the legend as the forms comprise internal documents between the offerors and its customers.

E. Volume V- Small Business Concern Utilization Plan The offeror 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, 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 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 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 socio-economic entities, provide rationale for such. Offerors 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.

F. Volume V, Cost/Price

To Be Determined.