Attachment_0004_Section_L.pdf

W58RGZ-17-R-0211

ATTACHMENT 0004

A. PROPOSAL SUBMISSION

1. INTRODUCTION:

To be considered for award, an offeror must submit a complete response to the Request for Proposal (RFP), including everything requested in this section. The offeror shall submit a proposal which is comprehensive enough to provide the basis for a sound evaluation by the Government.

Information provided must be precise, factual, and complete. Legibility, clarity, completeness, and responsiveness are of the utmost importance. Proposals shall be sufficiently detailed to enable the Government to determine the acceptability of the proposal solely from its contents. The Government will not assume or consider anything that is not specifically addressed in the proposal.

However, when evaluating the offeror's Past Performance, the Government reserves the right to evaluate outside data bases, sources, and contracts that may not be included in the offeror’s Past Performance Volume. Offerors are cautioned that “parroting” of the Technical requirements or the Statement of Work (SOW) with a statement of intent to perform does not reflect an understanding of the requirement or capability to perform. Offerors are responsible for including sufficient details to permit a complete and accurate evaluation of each proposal.

It is the offeror's responsibility to ensure the adequacy of the proposal in response to the RFP. The offeror shall include a requirements traceability matrix (requirements compliance matrix) that clearly identifies where the offeror’s proposal demonstrates each RFP requirement has been addressed.

2. PROPOSAL SUBMISSION REQUIREMENTS:

a. The proposal submitted in response to this RFP shall adhere to the format described herein.

Two (2) signed printed copies of the Standard Form (SF) 33 with all attachments shall be submitted. It is essential that all spaces and blocks on SF 33 and attached forms be completed and signed by a person authorized to enter into the proposed contract on behalf of the offeror. The offeror shall print or type the company's name on the schedule and each continuation sheet on which an entry is made. Two (2) signed printed copies of the entire proposal with original signature shall be provided to the contracting officer. Five (5) copies of the entire proposal shall also be submitted on individual Digital Video Disc Read-Only Memory (DVD-R). The original signed printed copy will be the official record copy and any amendments to the volumes must be submitted to the contracting officer in print along with the required DVD-R copies. Electronically embedded documents or videos or links to information outside the proposal shall not be considered. If a discrepancy exists between the original paper copy of the proposal and the disk copy, the paper copy will take precedence.

b. The offeror’s proposal shall consist of six (6) separately bound volumes and two (2) annexes.

Each volume and annex shall be submitted in a separate three-ring binder. Any pages that are changed (as a result of negotiations or proposal revisions) should be of a different color and have changed information clearly marked by a vertical line in the right margin of the page. The revised pages shall be dated. Each binder shall be clearly labeled with its Title and a copy number (e.g., copy 1 of 5).

All information shall be confined to the appropriate volume. Each volume of the proposal shall consist of: Cover Page with the RFP title, RFP number, Volume number and title; Table of Contents; Offerors' mailing address with Primary POC identified to include email address, phone number, and fax number (the “POC Page”); Summary Section; and the Narrative discussion. The Summary Section shall contain a brief abstract of the volume. The volumes and page limitations, including classified data, are as follows:

Table 1:

Volume Volume Title Page Limit I Executive Summary 5 II Technical Factor 125 III Past Performance 20 for Prime

*3 for each Major

Subcontractor IV Cost/Price Unlimited V Small Business Participation Plan 20 VI Contract Documentation Unlimited

Annex A Integrated Master Plan / Integrated Master Schedule

Annex B System Design and Effectiveness Requirements Compliance Matrix

*The pages allotted for Major Subcontractor past performance may not be used to increase the allotted pages for the Prime Contractor’s portion of the past performance volume. Past Performance Questionnaire Forms shall not be included in the page count for page limitation purposes.

c. Format: The submission shall be clearly indexed and logically assembled. Each volume shall be clearly identified and shall begin at the top of a page. All pages of each volume shall be appropriately numbered and identified by the complete company name, date and solicitation number in the header and/or footer. A Table of Contents should be created using the Table of Contents feature in MS Word 2003 or newer. MS Word (.doc) files shall use the following page set-up parameters:

Margins – Top, Bottom, Left, Right - 1” Gutter – 0” From Edge – Header, Footer - 0.5” Page Size, Width – 8.5” Page Size, Height – 11”

The proposal shall be submitted in single-spaced lines and proposal pages shall be double sided with each side counted as a page. Proposal pages shall be single column only. The font shall not be smaller than 12-point type. Arial or Times New Roman fonts are required. Tables and illustrations may use 11x17 pages with each side counted as two (2) pages, a reduced font size not less than 8-point, and may be landscape.

d. DVD-R: The volumes shall be provided to the Government on error free DVD-Rs. Each DVD-R shall have an external label attached indicating the name of the offeror, the RFP number, and a list of the files contained therein. Each volume shall be contained in a separate folder. No electronically compressed files shall be used.

e. Page Limitations: Page limitations shall be treated as maximums. If the pages exceed the page counts in Table 1 for each volume or attachment, the excess pages will not be read or considered in the evaluation of the proposal. The small business subcontracting plan is excluded from the page count. Any page shall be counted except the following: cover, table of contents, POC Page, glossary, acronyms, and index.

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

g. Markings: Be sure to apply all appropriate markings including those prescribed in accordance with FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

h. Classified Information: Where classified information is required in the offeror’s response, it shall be provided as a classified supplement and bound in a single classified addendum to the offeror’s solicitation and shall be limited to no higher than collateral Secret. 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 proposal instruction for unclassified portions. The classified addendum shall conform to the marking and transfer requirements of the National Industrial Security Program Operating Manual (NISPOM) and Army Regulation (AR) 380-5, as specified by the DD Form 254 (Attachment 004). Pages in a classified addendum will be included in the page count for the applicable volume. Classified addendum shall be delivered to the same address as unclassified data.

i. Disposition of Classified Material Not Received Under a Specific Contract: Offerors shall dispose of classified material in accordance with the National Industrial Security Program Operating Manual (NISPOM) and Army Regulation (AR) 380-5. Offerors shall comply with NISPOM paragraphs 10-202, Contract Security Provisions, and 2-102, Eligibility Requirements.

j. Proposal Crosswalk: All proposals must clearly and convincingly demonstrate that the prospective offerors have a thorough understanding of the requirements and associated risk to include a crosswalk between proposal, Statement of Work (SOW), LIMWS SPS, Interface Control Document (ICD), and the Contract Work Breakdown Structure (CWBS). Additionally the offeror must demonstrate ability, willingness, and competency to devote resources to meet the requirements. The offerors shall cross-reference their proposal to all evaluation criteria.

Statements that the prospective offerors understands, can, and will comply with the specifications, using general statements paraphrasing or restating the SOW requirements or parts thereof, with phrases such as "Standard procedures will be employed" or "Known techniques will be used" are inadequate and unsatisfactory. The proposals must clearly demonstrate the capability of the contractor to meet the requirements of the solicitation.

3. VOLUME I – EXECUTIVE SUMMARY:

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

a. Narrative Summary: The offerors shall provide a concise narrative summary of the entire proposal, including significant risks, and a highlight of any key or unique features, excluding cost/price. The salient features should tie in with Section M evaluation factors/sub-factors.

b. Table of Contents: A master table of contents of the entire proposal shall be provided.

4. VOLUME II – TECHNICAL

The offeror shall propose a design and describe a design approach for the LIMWS system that complies with the requirements of the LIMWS SPS. This portion of the proposal shall be a narrative description and includes detailed and concise description of the proposed LIMWS configuration. This Volume shall contain sections that address the offeror’s response to the Technical sub-factors.

A. DIGITAL SYSTEM MODEL (DSM)

The offeror shall provide a description of its proposed DSM used to model LIMWS performance against the requirements LIMWS SPS. The offeror shall provide a description of the DSM’s output data file contents. The offeror shall provide the following specific information:

- Evidence of the offeror’s DSM use of TMAP, EMSIG, and MODTRAN with version numbers of each;

- Evidence that the offeror’s proposed LIMWS sensor is modeled within the DSM using the offeror’s sensor characterization to include but not limited to the following attributes: Point Spread Function (PSF), Instantaneous Field of View (IFOV), Field of Regard (FoR), frame rate, spectral response, optical distortion, sensor fall-off, blur size and shape over the field of view, Non-uniformity Correction (NUC), and NUC stability.

- Evidence that the offeror’s DSM uses the offeror’s LIMWS sensor that was used to collect flight and ground testing imagery and that sensor imagery was incorporated within the DSM.

- Evidence that the offeror’s DSM can insert synthetic missile engagements in selected location or locate missile randomly throughout a scene.

- Evidence and video that the offeror’s DSM can play back both imagery and missile engagements collected during missile firing events.

- Evidence that the offeror’s DSM can integrate Digital Terrain Elevation Data (DTED)

B. SENSOR ALIGNMENT

The offeror shall provide evidence of its ability to design and achieve a non-tail specific system install (transfer alignment). The offeror shall provide transfer alignment data using the offeror’s system or a similar system to meet error tolerances provided in the SPS. The offeror shall provide the following specific information: (i) a detailed description of transfer alignment and mounting process; (ii) Test data and analysis showing the performance of offeror’s transfer alignment approach; (iii) all assumptions, limitations, and a discussion of the feasibility of offeror’s transfer alignment approach as installed on an aircraft.

C. SCHEDULE

The offeror shall provide an IMP/IMS, which will be incorporated into the resultant contract, reflecting the LIMWS program. In general, the IMP/IMS shall provide the information as described below:

(i) The offeror shall submit an IMP that is structured IAW the SOW. The IMP/IMS shall be submitted as Annex A. Technical design reviews shall be included as events. The IMP shall, at a minimum, include events, accomplishments that tie to these events, and completion criteria for each accomplishment for the LIMWS effort. The SOW defines a minimum set of technical events to be included in the proposed IMP. Criteria for entry into any technical event will be tied to the associated accomplishment completion criteria. The offeror may include additional technical events with associated accomplishments and completion criteria or more rigorous completion criteria as required.

(ii) The offeror shall identify the subcontractor’s/teaming arrangements to include the subcontractor’s responsibilities and the prime’s methodology for managing subcontractor activity.

The offeror shall describe the organizational structure of the proposed contractor team with emphasis on Integrated Product Teams (IPT) implementation; technical and budgetary responsibility; and the approach to communication and interface, including required Government participation and insight. Include identification of each specific organizational group and its roles/responsibilities. If subcontractors are to be utilized, identify what portion of the contract, or specific tasks, will be passed to the subcontractors to ensure compliance with contract technical performance, cost, and schedule requirements.

(iii) The offeror shall describe existing and future facilities required to perform engineering, manufacturing, and test activities for the LIMWS program at the system and subsystem level. The offeror shall provide a description of the planed approach for prototype development and to achieve full production capacity. Furthermore, the offeror shall provide a description of the planned approach for control and distribution of technical documentation.

(iv) The offeror shall provide an IMS submitted electronically via Microsoft Project 2003 or newer that delineates the offeror’s planned schedule for all activities, events, milestones, and critical paths associated with the LIMWS program contract traceable to the CWBS. The program’s critical path(s), based on critical path analyses, shall be identified in the IMS. The offeror shall develop the IMS in accordance with CDRL A002 identified in Exhibit A of the RFP. The offeror shall provide in the submitted IMS all contractors’ tasks, events, milestones which should be traceable to the CWBS and contractor’s cost management systems. For purposes of developing the IMS, the offeror shall use a contract award date of 01 December 2017. The offeror shall demonstrate the realism of the proposed IMS. All activity durations and resources must be substantiated using relevant historical data.

(v) The offeror is cautioned to use credible/realistic data and assumptions to produce a realistic IMS as well as an honest risk assessment of the schedule along with the offeror’s risk mitigation plan. The offeror shall identify risk associated, but not limited to, to the Manufacturing capacity, System Qualification, Availability of long lead items, Supply chain management, and Availability of prototypes and software to support contractor and U.S. Government (USG) testing. An unrealistic assessment or failure to address risk areas by the offerors may be viewed as risk due to a lack of understanding of the requirements or the effort required to perform the work.

(vi) The offeror shall describe their program management system including the organization and program execution methods, program performance metrics, integrated management system (to include Government team interface), and integrated digital environment. The offeror shall describe staffing approach and manpower ramp-up, level and functional type of manpower (including software, manufacturing, or other areas of anticipated manpower risk) required by Fiscal Year (FY) and by phase of the program. Include plans to assign or recruit manpower to meet requirements and to identify and mitigate anticipated critical skills gaps.

(vii) The offeror shall provide a manufacturing strategy and plan that describes the approach to manufacture production representative prototype units and production units. The offeror’s manufacturing plan shall include a detailed description of the facilities that will be used and the availability during the timeframe required to manufacture prototype and production units. The plan will describe the manufacturing processes required and will include a process flow chart. The plan will include the offeror’s self-assessment of manufacturing readiness level. The plan shall include significant detail describing the equipment, and fixtures that will be required. The offeror will provide the manufacturing test plan and a description of the test coverage provided by each test.

The offeror shall provide details on their teaming approach with any significant subcontractors and describe the design authority arrangement with each subcontractor. The offeror will describe their supply chain and the process used to evaluate or rate their suppliers. The offeror will describe their quality management system.

(viii) The offeror shall submit resumes of key/critical technical personnel responsible for the execution of the proposed contract. If the offeror or a subcontractor proposes an individual in a key personnel position who is not currently employed by the firm, then the proposal shall include a letter of commitment, signed by the firm and individual, indicating that the individual will become an employee if the offeror is awarded the contract. Resumes will address the overall qualifications, experience levels on efforts similar to those required under the contract SOW, and the general expertise of the offerors proposed key personnel. Resumes should provide the experience of key/critical technical personnel in the functional service areas. For each key personnel proposed, resumes shall also include the individuals present assignment, other solicitations for which the individual is proposed, and the individuals status as a key individual with the present assignment. Resumes shall normally not exceed one page in length. Under no circumstances shall they exceed two pages.

D. PERFORMANCE

The offeror is required to provide test data substantiating its technical proposal, including its design and its design approach to meeting LIMWS SPS requirements, both generally and specifically with regard to the following critical SPS performance parameters: Probability of Declaration (Pd), False Alarm Rate (FAR), Probability of Cue (Pcue) and False Cue Rate (FCR).

This substantiating test data must also be described in detail, including the following information at a minimum: 1) test environment 2) test scenarios 3) threats or threat representations 4) test location 5) sponsor 6) a summary of test results, and 7) analysis. Data obtained in a representative LIMWS operational environment may be deemed more relevant and accorded more weight than data obtained under other conditions or in other environments. U.S.

Government witnessed test data will be accorded more weight than third-party witnessed test data, contractor test data, and analysis. Third-party (non-U.S. Government) witnessed test data will be accorded more weight than contractor test data and analysis. Contractor test data will be accorded more weight than unsubstantiated analysis.

For all elements in the performance section, the offeror shall provide an editable Microsoft Excel file, hereon in referred to as Evaluation Matrix, which contains at a minimum, but not limited to, the following engagement parameters for each of the engagements used to assess performance:

engagement numerical identifier (e.g. 1, 2,3), missile type, ground range (Km) at time of launch, azimuth angle of launch point (in degrees) with respect to aircraft coordinate system, aircraft velocity (m/sec), aircraft altitude (ft AGL), clutter level (very low, low, medium, high, very high) around the launch point, atmospheric conditions and engagement time-of-flight (secs). The offeror shall provide, for each of the missile types listed in the LIMWS SPS, an editable Microsoft Excel file containing: missile type, missile flyout model (e.g. TMAP, DISAMS, ESAMS, Vendor Model) including version, missile plume model (e.g. E-MSIG, IRSIG, Vendor Model) including version, and atmospheric model (e.g. MODTRAN, Vendor Model) including version.

For each of the engagements in the Evaluation Matrix, the offeror shall provide an editable Microsoft Excel file containing at a minimum, but not limited to, the following performance metrics: engagement numerical identifier, launch range assessment at time of launch, time to go estimation at time of cue and declaration, cue time and declaration time measured in time lapsed after missile launch. The offeror shall provide plots of Pcue vs. Ground Range and Pd vs.

Ground Range for each missile type and clutter condition, where each plot is aggregated over all platform altitude, platform speeds and angle of launch. The plots shall include the total number of engagements used for each range bin. The offeror shall provide, for each missile type, plots of Pcue vs. Ground Range and Pd vs. Ground Range aggregated over all clutter levels, aircraft flight conditions, and angle of launch.

The offeror shall provide plots of Cue Time vs. Ground Range and Declaration Time vs. Ground Range for each missile type and clutter condition, where each plot is aggregated over all platform altitudes, platform speeds, and angle of launch.

(i) The offeror shall provide descriptions of the proposed sensor, processor, and algorithm design and implementation to substantiate the capability to meet or exceed SPS requirements. The offeror shall provide the sensor’s noise equivalent irradiance (NEI), signal-to-clutter threshold for detection, detection kernel size, clutter kernel size and pixel IFOV.

(ii) The offeror shall provide details of algorithm robustness to spectral, spatial, temporal, and plume radiant intensity variability and provide test data showing algorithm cue and declaration times for 1.5Km and 4km (ground range) engagements against a hovering aircraft at an altitude between 100 and 1000 ft AGL. for two assets identified in the SPS Section 3.2.4.3.4. The offeror shall identify each parameter that was varied and to what extent. The offeror shall provide details on the clutter metric selection, the clutter metric definition, the clutter metric thresholds and how each scene was divided into very low, low, medium, high and very high clutter. Using Environmental Protection Agency’s (EPA) land usage definitions set forth in the LIMWS SPS, the offeror will select a rural scene, an urban scene, and an industrial scene and for each scene superimpose a contour plot showing all localized clutter levels applicable to each scene. The offeror shall provide test data showing angle of arrival accuracy. The offeror shall provide substantiating data on the relevancy of the background scenes used to assess performance as it represents rotary wing’s operational flight envelope. The offeror shall provide its strategy to recover Pd in very high clutter environment.

(iii) The offeror shall provide a table containing the flight location, aircraft speed (m/sec), aircraft altitude (ft AGL) and total number of hours flown in all locations where the system was flown to assess FAR. For each location, the offeror will provide FCR and FAR performance as well as a plot of Instantaneous False Alarms (IFA) defined as the number of false alarms observed over a 15 minutes moving average window. The offeror shall provide clutter level for each location. The offeror shall include the aggregated FCR and FAR for all flight hours flown.

The offeror shall provide its spatial, spectral, and temporal strategies to reduce FAR while maintaining Pd performance.

(iv) The offeror shall provide the design approach to integrating with CIRCM and its strategy to reduce FCR while improving cue timelines.

(v) The offeror shall provide test data showing processor loading in various clutter environments.

The offeror shall provide impact to Pd, Pcue, FAR and PCR relative to processor loading.

(vi) The offeror shall provide performance impact of sensor alignment residual error to Pd, Pcue, FAR, and FCR.

(vii) The offeror shall provide a description of its approach to, and implementation of, open system architecture design principles. The offeror shall provide a plan to meet SPS objective requirements, improve system performance over time, and add additional capabilities and reduce size, weight and power requirements to support future mission requirements.

(viii) The offeror shall provide a description of the assessed risks and strategies to mitigate risk, to include the quality of the offeror's DSM, the inputs and assumptions behind model data to identify that the offeror's proposed system performance data is accurate and traceable to expected real-world performance.

5. VOLUME III – COST/PRICE:

A. General Instructions

(1) In order to expedite the evaluation, offerors (prime and subcontractors) shall provide a copy of their cost/price proposal, in the same format required by the solicitation, to their respective Defense Contract Audit Agency (DCAA) and Defense Contract Management Agency (DCMA) offices upon submission of the proposal to the Contracting Officer. In addition, offerors shall provide a disk or electronic copy of the spreadsheets used to develop the total estimated cost/price to DCMA, DCAA, and Procuring Contracting Officer. Cost/Price non re-writable digital versatile disks (DVD-R) requirements: Submit spreadsheets in Microsoft Excel format and in a live, unprotected file that includes all formulas and computations that calculate out to the proposed amounts. Files contained on the Volume IV Cost/Price DVD-R may not be password protected. If the Cost/Price Volume contains electronic links, the links must be intact and maintained through all revisions. If discrepancies are identified between the electronic proposal and the original hardcopy proposal, the original hardcopy proposal shall prevail. Electronic copies will not be password protected.

(2) The Cognizant DCMA and DCAA point of contacts (POCs) for the offeror and all major subcontractor(s), as defined below, shall be identified in the proposal, along with their respective e-mail addresses and telephone numbers. The prime contractor is required to fill out the Attachment entitled, "CAGE Code and Cognizant DCMA & DCAA Information" for themselves and all proposed major subcontractors.

(3) Failure to comply with RFP requirements for cost/price information may result in an adverse assessment of an offerors proposal and reduce or eliminate its chance of being selected for award.

(4) This volume shall consist of all information required to support proposed costs and prices to complete the evaluation. Proposals should be sufficiently detailed to demonstrate reasonableness.

(5) In accordance with FAR 15.402, 15.403-1 and 15.403(a) (1), certified cost or pricing data are not required based on the fact that adequate competition is expected for this procurement.

However, if after receipt of proposals the Contracting Officer (KO) determines that there is insufficient information available to determine price reasonableness and none of the exceptions at FAR 15.403-1 apply, the Government reserves the right to request such data prior to award. There are no page limitations for this volume. The cost/price proposal shall be clearly marked, "Cost/Price Proposal, RFP No. W58RGZ-17-R-0211 documents, Block 12 of Standard Form 33.

The information submitted in this volume shall comply with FAR 15.408, Table 15-2.

(6)The offeror’s proposal shall be submitted with any and all information reasonably required to explain the estimating process, including the judgmental factors applied and the mathematical or other methods used in the estimates, including those used in projecting from known data; and the nature and amount of any contingencies included in the proposed price. The offeror shall provide any other general or specific information that may be beneficial in evaluation of the offeror’s proposal. The offeror’s cost and price estimating practices shall be in accordance with the offeror’s established accounting practices for accumulating, allocating and recording cost to final cost objectives.

(7) The offeror shall also provide the most current compliance status and date of adequacy/inadequacy determination for the following systems; Accounting System and Purchasing System. If the offeror does not have an approved Accounting System, a Pre-Award Survey may be required.

In accordance with FAR 16.301-3(a)(3), the contractor must have an accounting system that is adequate for determining costs applicable to the contract. The offeror shall provide a summary description of their accounting system, including indirect rate structure, and state whether it is compliant with Generally Accepted Accounting Principles (GAAP). In addition, the offeror shall provide a copy of the DCAA Audit Report showing adequacy of the accounting system, and DCMA approval letter of the accounting system. The audit report or letter should be dated within four years of the offerors cost proposal. If DCAA has not audited the offeror or subcontractors' accounting system or DCMA has not approved the accounting system or DCAA has not determined adequacy, please indicate this in Pre-award Survey of Prospective Contractor Accounting System Checklist under RFP Attachment 0025. In order for the Army Contracting Command-Redstone to proceed with a request for a DCAA pre-award accounting system survey, completion of the Pre-award Survey of Prospective Contractor Accounting System Checklist by the offeror is required, included as RFP Attachment 0025. This completed form should be submitted with the offeror's proposal under the cost volume. The Contracting Officer will forward a copy to the cognizant DCAA office along with the request for audit. The offeror shall provide the same information for any subcontractor with which they intend to establish a cost type subcontract arrangement.

The offeror shall provide any known/cited accounting system deficiencies. The Contracting Officer will request an accounting system audit or follow up audit from DCAA. The offeror shall also identify any deviations from the offeror's standard procedures in preparing this proposal. If the offeror proposes to absorb a portion of costs, explain the reason and impact on cost and the specific accounting treatment that will be given to those absorbed costs. The offeror shall provide the same information for any subcontractor with which they intend to establish a cost type subcontract arrangement.

(8) For proposal preparation purposes, the expected or approximate date for initiation of contract performance is 1 December 2017.

(10) Offerors are reminded of the requirements of Section 39 of the Office of Federal Procurement Policy (OFPP) Act (41 U.S.C. 1127, formerly 41 U.S.C. 435), as amended, which limits allowable costs for senior executive personnel compensation.

(11) In accordance with FAR Provision 52.214-35 (Submission of Offers in U.S. Currency), all costs/prices must be in U.S. dollars only, including costs/prices for the Offeror and any potential subcontractors. If the basis for the proposal is any other currency, the

Offeror shall:

(a) State the exchange rate(s) being used to convert any currency to the U.S. dollars, and how the exchange rate was developed.

(b) Explain how the offeror intends to deal with the risk that fluctuation in exchange rates may impact this prospective contract.

(12) Table of Contents. The Offeror and each Major Cost Reimbursable (CR) Type subcontract, defined in Paragraph (3) below, shall provide a Table of Contents showing each file submitted as part of the Cost/Price Volume with a short description of the contents of the file. Each of these entries in the Table of Contents shall be hyperlinked to the respective files.

(13) The total proposed price shall include the summation of all Firm-Fixed Price (FFP), Cost Plus Fixed-Fee (CPFF), and CR Contract Line Item Number (CLINs) in Section B of the RFP.

B. CPFF CLINs

The offeror shall ensure that the information submitted in this volume is consistent with and fully supports the amounts set forth in the SF33 and continuation sheets. The offeror shall provide sufficient details for the Government to evaluate the proposed labor hours, applicable base labor rates, associated indirect rates, direct material costs, subcontracts, inter-organizational transfer costs (IOT), and Other Direct Costs (ODC) for each CLIN. For each individual CPFF CLIN in Section B of this RFP the Offeror shall include a spreadsheet in the Cost Volume in the format of Table 15-2, FAR 15.408. Please note that the offeror shall include a summary of the total proposed cost/price by cost element for the total contract and a cost element summary by contract year and by CLIN.

(1) Direct Labor: Support for costs related to direct labor shall include the following:

(a) The offeror shall submit a complete proposal including labor rates for each labor category that is identified for accomplishing the requirements of the SOW, and an annual time-phased breakout of the direct labor hours, by labor category, appropriate to the offeror’s accounting system. All direct labor hours and labor category descriptions in the Cost Volume must be directly traceable to the Technical Volume.

(b) Bid codes, if applicable, used to identify a labor category in the offeror's accounting system to support the proposed labor rates shall be provided and mapped to the labor categories.

(c) If the proposed direct labor rates are based on a current Forward Pricing Rate Agreement (FPRA), the offeror shall provide a copy of the FPRA and state whether or not the proposed FPRA rates include or have been adjusted for the impact of this proposal. Note further that the application of FPRA rates in an offerors proposal does not preclude the offeror from submitting the underlying support for subject rates if requested.

(d) Direct labor rates proposed from "letters of commitments" shall include the letter(s) that contain sufficient documentation to fully support proposed labor rates.

(e) If the proposed direct labor rates are based on surveys (i.e. personnel for that category are not currently employed by the offeror), then the offeror shall provide the applicable pages from the proposed surveys and show which rates were utilized (i.e. 50th percentile, median, etc.). The offeror shall provide a crosswalk that maps to the proposed labor hours, labor categories and labor rates for both the prime and subcontractor(s). Direct labor rates shall identify the baseline (takeoff point) plus projected escalation for all labor for resulting contract period of performance.

(f) A description and basis of estimate (BOE) of each labor hour category. This description shall include sufficient information to allow the reader to distinguish between the different labor categories used in the proposal. The BOEs shall include:

i. a narrative description of the tasks to be performed

ii. a description of the method used to estimate the hours (identifying assumptions used and any Cost Estimating Relationships)

iii. the calculations showing the computation of the direct labor hours for each specific task

iv. the labor function (i.e. Engineering, Logistics, Test, Production, etc) that the tasks within the BOE relate to, and

v. a description of each labor category used in the BOE.

(2) Inter-Organization Transfers (IOTs) The same type of cost/price information as instructed under Section L 6. VOLUME IV – COST/PRICE paragraphs A and B are applicable to all IOT submissions, regardless of dollar value, except the Prime Offeror need not provide an evaluation of such pricing data. Please indicate whether the IOT includes upward or downward adjustments for contingencies or negotiation challenges and the supporting rationale.

(3) Major Cost Reimbursable Type contracts (i.e. CPFF, Cost (no fee), etc.). Subcontractors are defined as members of an offeror’s overall team who are expected to perform on the proposed effort. A major CR subcontractor is defined a subcontractor whose total proposed CR value is greater than $750K for all CLINs. If the prime Offeror’s proposal includes any major CR subcontractors, the major subcontractor shall provide cost/price information equivalent to that required of the Prime Offeror under Section L 6. VOLUME IV – COST/PRICE paragraphs A and B. The prime contractor is required to provide the contract type arrangement proposed for each proposed subcontractor. The prime contractor shall assure that the proposed contract type arrangement for each subcontractor is the same arrangement provided in the subcontract proposals or shall provide an explanation for the difference.

(a)The prime Offeror shall include the evaluation of the major CR subcontractor's submission required by subcontract pricing considerations (FAR 15.404-3 (b)), and rationale for determining that the subcontract price/cost is fair and reasonable.

(b)For major CR subcontractors as defined above, if the subcontract is based on adequate price competition, cost information from the subcontractor is not required. Instead, provide copies of competitive subcontractor cost/price quotes.

(c) All major CR subcontractors shall submit an un-sanitized proposal to the CO. If the major CR subcontractor declines to provide complete unsanitized cost proposals to the Offeror or higher-tier subcontractor, then those subcontract proposals may be submitted by the subcontractor directly to the Procuring Contracting Officer (PCO) using the same submission instructions outlined in Section 2. Such submissions shall arrive at or prior to the due date for proposals as noted on the front page of this RFP.

(d) Subcontractors may submit a complete proposal including labor rates for each labor category to prime contractors; however, subcontractors' proprietary information (i.e., unsanitized, development of fully burdened rates) may be submitted directly to the Government. Information submitted directly to the Government shall clearly identify the prime contractor proposal/RFP to which the cost data applies. Each subcontractor shall clearly mark that the data is considered proprietary and not to be released to the prime contractor without consent.

(4) Firm-Fixed Priced (FFP) Type Subcontracts over $750K. If the Prime Offeror’s proposal includes any FFP subcontractors over $750K, the Prime Offeror shall provide the support documentation for the basis of the proposed subcontract prices (i.e. vendor quotes, purchase order history, long-term agreements, etc.). The Prime contractor is required to provide the contract type arrangement proposed for each proposed subcontractor. The prime contractor shall assure that the proposed contract type arrangement for each subcontractor is the same arrangement provided in the subcontract proposals or shall provide an explanation for the difference.

(5) Consolidated Bill of Material. The proposed Consolidated Bill of Material shall include narrative(s) and supporting price/cost analyses explaining the method used in developing the proposed Bill of Material costs for all material proposed under the CPFF CLINs that include the following:

a) Associated WBS and CLIN

b) National Stock Number (NSN) / NIIN, as applicable

c) Part Number

d) Item Name/Description

e) Vendor

f) Unit Cost (purchase price to Offeror)

g) Quantity used

h) Extended Cost (unit cost multiplied by quantity used)

i) Basis and support for unit cost (engineering estimate, vendor quote, purchase history, etc.) and any material factors (escalation, scrap, rework, etc.)

j) Indicate whether component is sole-source, competitive, or commercial

k) For material/subcontract costs based on engineering estimates, please provide rationale and methodology for how the estimate was developed

12) Identify the next higher assembly

(6) Other Direct Costs

ODCs may include costs such as computing charges, travel, special tooling etc. The Offeror shall identify each category of proposed ODC and the dollar amount for each category. The Offeror shall provide an explanation of what is included in each category and supporting documentation (invoices, vendor quotes, purchase order history, estimates, etc.). All proposed ODCs must be proposed using the Offerors current standard accounting practices. The Offeror shall provide a price/cost analysis for any individual ODC item or category over $100K.

(7) Travel

Travel shall be proposed in accordance with Joint Travel Regulation. For evaluation purposes only, offerors shall utilize estimated travel costs, which are inclusive of burdens, in the amount of $1M for the cost-reimbursable (no fee) CLIN 0004. The actual values for CLIN 0004 will be based on the allocable and allowable travel costs incurred in the performance of the resulting contract. For each proposed trip, please provide the purpose of the trip, the trip origin, the trip destination, the number of travelers, the number of days, and the proposed hotel cost, M&IE cost, rental car cost, and any other costs associated with the trip. The Offeror may use a Cost Estimating Relationship (CER) for Travel as an alternative estimating methodology. If a CER is used to estimate Travel, please provide a detailed explanation supporting how the CER was developed. Include information such as the programs used and associated Travel costs, amounts included in the base (i.e. number of labor hours, labor costs, etc), and the calculation showing how the CER factor was derived. In addition, please provide the calculation showing how the CER factor is applied to estimate the proposed Travel cost for this effort. Travel costs are incidental to the contracting effort, and considered minimal-risk cost elements. They are, therefore, to be proposed without the addition of fee.

(8) Indirect Rates

Provide a list of the direct and indirect rates in a table, by category and by Offerors fiscal year, used in the development of the proposal and include:

(a) The date of the current Cost Accounting Standards Board (CASB) Disclosure Statement.

b) The effective date of the rates or the data that formed the basis for the rates (the date of the burden study analysis or payroll run, etc.), and state whether or not the rate package has been submitted to Defense Contract Audit Agency (DCAA) for review.

(c) The ending month for the Offeror's fiscal year.

(d) A narrative explaining the basis for the estimated rates. And specifically identify any escalation factors used.

(e) State whether these rates represent a Forward Pricing Rate Proposal (FPRP) or a Forward Pricing Rate Agreement (FPRA) and note the date of the agreement.

(f) State whether or not the business volume that would be generated if a contract was awarded to your firm as a result of this RFP has been included in the proposed rate package.

(9) Facilities Capital Cost of Money (FCCOM)

The Offeror shall state the total amount estimated for FCCOM and identify the Treasury Rate used to develop the amount.

(10) For CLIN 0003 – Engineering Support only, if uncompensated overtime is proposed for employees who are exempt from the Fair Labor Standards Act, the offeror shall compute an estimated hourly rate for each employee based on the total compensated and uncompensated hours the employee is expected to work during the year and distribute salary costs to all projected tasks/efforts at the estimated hourly rate in accordance with FAR 52.237-10, Identification of Uncompensated Overtime. The offerors accounting practices used to estimate uncompensated overtime must be consistent with its cost accounting practices used to accumulate and report uncompensated overtime. If proposing uncompensated overtime, an offeror shall adjust the proposed labor rates to cover the extra hours proposed to be worked and submit the calculations. A copy of the offeror’s policy addressing uncompensated overtime shall be included in the proposal submission.

C. FFP CLINs

The offeror shall provide their proposed price for all Fixed Price CLINs, listed in Section B of the

RFP.

6. VOLUME IV - PAST PERFORMANCE.

This volume shall contain past performance information regarding contracts similar in scope, subject and magnitude to the effort described in the RFP. Offerors shall submit three (3) Government and/or commercial contracts for the prime offeror and one (1) contract for each major subcontractor in performance or awarded during the past three (3) years, from the issue date of this RFP, which are relevant to the efforts required by this solicitation. Data concerning the offeror shall be provided first, followed by each proposed major subcontractor, in alphabetical order. The Offeror shall also submit the written consent of its major subcontractors to allow the disclosure of its subcontractor’s past performance information to the Offeror. In addition, letters of commitment shall be included for all major subcontractors for their past performance to be considered. This volume shall be organized into the following sections:

a. Section 1 – Contract Descriptions. The offeror can submit at most three (3) contract descriptions. This section shall include the following information in the following format.

(1) Contractor/Subcontractor place of performance, CAGE Code and DUNS Number.

If the work was performed as a subcontractor, also provide the name of the prime contractor and

Point of Contact (POC) within the prime contractor organization (name, and current address, e-mail address, and telephone and fax numbers).

(2) Government contracting activity, and current address, Procuring Contracting Officer’s name, e-mail address, telephone and fax numbers.

(3) Government’s technical representative/Contracting Officer Representative (COR) and current email address, telephone and fax numbers.

(4) Government contract administration activity and the Administrative Contracting Officer’s name, and current e-mail address, telephone and fax number.

(5) Government contract administration activity’s Pre-Award Monitor’s name, and current e-mail address, telephone and fax numbers.

(6) Contract Number and, in the case of Indefinite Delivery type contracts, GSA contracts, and Blanket Purchase Agreements, include Delivery Order Numbers.

(7) Contract Type (specific type such as Fixed-Price (FP), Cost Reimbursement (CR), Time & Material (T&M), etc.). In the case of Indefinite Delivery contracts, indicate specific type (Requirements, Definite Quantity, and Indefinite Quantity) and secondary contract type (FP, CR, T&M, etc.).

(8) Awarded price/cost.

(9) Final or projected final price/cost.

(10) Original delivery schedule, including dates of start and completion or work.

(11) Final or projected final, delivery schedule, including dates of start and completion of work.

b. Section 2 – Performance. Offerors shall provide a specific narrative explanation of each contract listed in Section 1, Contract Description, describing the objectives achieved and detailing how the effort is relevant to the requirement of this RFP.

(1) For any contracts that did not/do not meet original schedule or technical performance requirements, provide a brief explanation of the reason(s) for the shortcomings and any corrective action(s) taken to avoid recurrence. The offerors shall list each time the delivery schedule was revised and provide an explanation of why the revision was necessary. All Requests for Deviation and Requests for Waiver shall be addressed with respect to causes and corrective actions. The offerors shall also provide copy of any Cure Notices or Show Cause Letters received on each contract listed and a description of any corrective action implemented by the offeror or proposed subcontractor. The offerors shall indicate if any of the contracts listed were terminated and the type and reasons for the termination.

(2) For all contracts, the offeror shall provide data on all manufacturing warranty returns.

Data shall delineate total number of warranty returns, number of Could Not Duplicate (CND), number of failures attributable to GFE component failures, and number and nature of failures attributable to the offeror’s delivered product.

c. Section 3 – Subcontracts. Offerors shall provide an outline of how the effort required by the RFP will be assigned for performance within the offeror’s corporate entity and among the proposed subcontractors. The information provided for the prime offeror and each proposed major subcontractor must include the entire company name, company address, CAGE Code, DUNS Number and type of work to be performed by citing the applicable Government SOW subparagraph number. This includes all subcontractors who will be providing critical hardware/services or whose subcontract is for more than $750K. This section will further include written consent of major subcontractors to allow the disclosure of their subcontractor’s past performance information to the Offeror. In addition, letters of commitment shall be included for all major subcontractors.

d. Section 4 – New Corporate Entities. New corporate entities may submit data on prior contracts involving its officers and employees. However, in addition to the other requirements in this section, the offeror shall discuss in detail the role performed by such persons in the prior contracts cited. Information should be included in the files described in the sections above.