Attachment_0005-_Sentinel_A4_Section_L_24_Jan.docx

Section L Instructions, Conditions, and Notices to Offerors For the Sentinel Increment A4 Program

24 January 2017

PREPARED FOR:

Army Contracting Command – Redstone Redstone Arsenal, AL 35898-5000

Coordination Page

Submitted by:

Concurrence:

Approval:

***** DRAFT *****

Contents

L. PROPOSAL SUBMISSION (SECTION L)

The offeror shall submit its proposal in hard-copy, with accompanying digital copies, as set forth below. The Request for Proposal (RFP) shall provide the Government address and receipt date for proposal submittal.

The requirements contained at Federal Acquisition Regulation (FAR) 52.215-1, Instructions to Offerors – Competitive Acquisition, apply in full to this solicitation.

The Government will use non-government advisors as listed in the RFP during the source selection process. The offeror’s proposal must clearly state that the offeror has entered into its own non-disclosure agreement with the nongovernment advisor, or with the company employing the nongovernment advisor (see FAR 9.505-4(b)). The offeror’s proposal must also state the offeror grants consent for the Government to provide access to its proprietary information to the nongovernment advisor or the company that employs the nongovernment advisor. Proposals that fail to comply with this requirement will not be eligible for award.

L.1. Submission Requirements The offeror’s proposal shall consist of a proposal Index and five volumes.

Proposal Index I – Technical (in two parts) II – Past Performance III – Small Business Participation IV – Cost/Price V – Contract Information (Solicitation, offer and award documents, Certifications / Representations, and other information as needed)

The Government cautions the offerors 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. The offeror will clearly mark proprietary information.

The offeror shall submit documentation illustrating its approach for satisfying the requirements of this solicitation. Proposals must be clear, coherent, and prepared in sufficient detail for effective evaluation of the offeror’s proposal against the evaluation criteria. In addition, this documentation shall cover all aspects of this solicitation and include the offeror’s approach for integration and program management activities. Proposals must clearly demonstrate how the offeror intends to accomplish the project and must include plausible rationale and substantiation of all claims. The Government does not desire unnecessarily elaborate brochures or other presentations beyond those sufficient to present a complete effective response to the solicitation.

The offeror shall describe its proposal with graphs, charts, diagrams, and narrative, in sufficient detail for the Government to understand and evaluate the approach. In its evaluation and confidence assessment, the Government will consider the degree of substantiation of the proposed approaches in the proposal volumes and in response to any discussions. Nonetheless, the Government is seeking substance, not gloss.

L.2. Cost or Pricing Data Address all cost or pricing information only in the Cost/Price and Contract Information volumes. The offeror may use cost trade off information, work hour estimates, material kinds and quantities, and other direct costs in other volumes or sections (e.g., in the Basis of Estimate) for rationale in meeting requirements, assessing alternatives, or to support design and trade off decisions.

L.3. Organization The proposal shall be accompanied by a cover letter (letter of transmittal) prepared on the company’s letterhead stationery. The cover letter (letter of transmittal) shall –

a. identify all enclosures being transmitted,

b. be used only to transmit the proposal, and

c. include no other information.

The first or title page shall be in accordance with FAR 52.215-1, paragraph (c)(2).

The offeror shall prepare the proposal as set forth in the following table. The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies specified. Attachments shall be included in, or accompany, the respective volumes. Specified attachments or appendices to the volumes do not count toward the volume page count. The contents of each proposal volume are as described in this document.

Volume

Paper Copies

Page Limit

Proposal Index

II Past Performance

III Small Business Participation

IV Cost/Price

V Contract Information

L.4. Page Limitations Page limitations are maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal and (for paper copies) will be returned to the offeror as soon as practicable. When both sides of a sheet display printed material (except for “page intentionally blank”), it counts as two (2) pages. The Government will count each page except for the following required items:

a. Cover pages

b. Title pages

c. Tables of Contents

d. Table of Figures

e. List of Tables

f. Glossaries

g. Abbreviations and Acronym Lists

h. Cross Reference Matrix and Compliance Matrix

i. Cost/Price Volume

j. Contract Information Volume

k. Contractor Work Breakdown Structure (CWBS) and Dictionary

l. Integrated Master Schedule (IMS)

m. Data Rights Assertions

n. Appendix with supporting information for the Small Business Participation Plan

o. Small Business Subcontracting Plan (for Large Business Only)

L.5. Format Text shall be single-spaced, on 8-1/2 x 11 inch paper (except as specifically noted), with a minimum one-inch margin all around. Number volume pages consecutively, with the first page counting against page count numbered as page one. Use dividers between the main text and appendices. Number each appendix separately (e.g., A-1). Dividers do not count as pages.

Pages shall be single-spaced. Submission as double-sided printing/copying on recycled paper is encouraged. Print shall be of a minimum 12-point Arial or Times New Roman font size. The offeror may use bolding, underlining, and italics to identify topic demarcations or points of emphasis. Foldout pages shall not exceed 11 x 17 inches in size. Foldout pages are printed one side only, fold entirely within the volume, count as a single page, and count as part of the total page count. However, the total number of these pages cannot exceed 5% of the total page limitation for that volume or sub-volume. Use foldout pages only for large tables, charts, graphs, diagrams and schematics, not for pages of text. For tables, charts, graphs, and figures, the text shall be no smaller than 8-point font and may be landscape. These limitations shall apply to both electronic and hard copy proposals.

Any pages that are changed (e.g., resulting from negotiations or proposal revisions) will 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.

Bind each volume separately in hard side, three-ring binders. Each volume in the proposal shall include a copy of the cover letter (letter of transmittal), title page, and table of contents. The table of contents shall list sections, subsections, and page numbers. Each volume shall contain a glossary of all abbreviations and acronyms used. Spell out each acronym used in the text the first time it appears in each proposal volume. Each volume will have its own attached acronym list. Offerors may bound large appendices as attachments. The Basis of Estimate, submitted as part of the cost/price submission, is separately bound to facilitate technical review.

In addition to the paper copies identified above, the offeror shall submit all proposal information in electronic format on Compact Disc (CD) or Digital Versatile Disc (DVD). Text and graphics portions of the electronic copies shall be in a format readable by Microsoft (MS) Office, MS Word. Data submitted in spreadsheet format shall be readable by MS Excel. Integrated Master Schedule information shall be readable in MS Project. The offeror must ensure that electronic proposals are free of computer viruses. Externally label each disc with the volume number, date, and the offeror’s name. Self-extracting exe files are not acceptable. If the hard copy proposal differs from the electronic version, the hard copy will govern.

Separately bound classified volumes and CDs with an applicable security designation and marked in accordance with (IAW) the Sentinel A4 Security Classification Guide.

L.6. Cross-Referencing The offeror shall write each volume, other than the Cost Volume, to the greatest extent possible on a stand-alone basis so that the evaluation team can evaluate its content with a minimum of cross-referencing to other volumes of the proposal. Information required for proposal evaluation not found in its designated volume may result in an unfavorable proposal evaluation. Cross-referencing within a proposal volume only where its use would conserve space without impairing clarity. The offeror shall provide a cross-reference matrix indicating the corresponding proposal paragraph that addresses each referenced item.

L.7. Proposal Index The offeror shall provide a master table of contents of the entire proposal, a master cross reference matrix, an overall proposal compliance matrix, and a full abbreviations and acronym list, none of which count against page limits.

L.8. VOLUME I: Technical

L.8.1. General The Technical Volume shall be specific and complete. Legibility, clarity, and coherence are very important. The Government will evaluate the responses against the Technical factors, as defined in Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology for accomplishing and satisfying these factors. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation. All responses in the Technical Volume shall be IAW the Sentinel A4 Security Classification Guide.

L.8.2. Format and Specific Content The Technical Factor will focus on two key areas and the offeror shall submit the response in two parts: Volume 1a) System Design and Performance, and Volume Ib) System Producibility. The offeror shall delineate as specifically as possible how its technical solution meets the requirements, is technically superior to other alternatives, is of acceptable risk, is producible and affordable, and has few or no limitations or restrictions on technical data and computer software.

L.8.3 System Design and Performance (Volume 1a) The offeror shall propose a Sentinel A4 hardware, firmware, software architecture, design, and functionality for an X-Band radar capable of performing the Sentinel A4 mission and achieving the requirements described in the System Specification (MIS-60990) and the Interface Design Description (IDD). The description of the radar design shall –

a. Trace System Specification (MIS-60990) requirements to the system and subsystem level

b. Demonstrate to the Government that the proposed design will meet all proposed requirements in the environments and mission scenarios provided

c. Include engineering design budgets and margins

d. Identify key risks and mitigation strategies associated with the proposed approach

L.8.3.1 Performance – The offeror shall present its proposed design in detail, including rationale, and with sufficient technical evidence of how the proposed design will meet the requirements outlined in the Sentinel A4 System Performance Specification.

The proposal shall substantiate the offeror’s design concept, using tables, charts, Blake charts, plots, and supporting data for derived solutions, and demonstrate how it achieves the sub-clutter visibility, operations in an Electronic Attack (EA) environment, and the Non-Cooperative Target Recognition (NCTR) classification performance requirements described in the Sentinel A4 System Performance Specification (MIS-60990).

The proposal shall substantiate the offeror’s approach, using tables, charts, Blake charts, plots, and supporting data for derived solutions, for achieving improved engagement support capabilities against cruise missile and unmanned aerial system threats as well as achieving engagement support for Counter-Rocket, Artillery, and Mortar (RAM) threats.

To assist in the evaluation of the Technical Volume 1a) System Design and Performance, the Government will release to the vendors a software simulation for assessing radar performance, called Benchmark+, as part of the RFP. The offeror shall input its proposed radar design into the Benchmark+ sensor model and perform simulation runs against a set of threat scenarios provided by the Government common to all vendors. To allow for Benchmark+ modeling, the vendor shall provide a proposed design at a level of maturity that includes specification of radar resource management (beam & waveform scheduling) and target track processing (discrimination, track filtering, and ballistic propagation). The offeror shall report the results in the proposal.

In order to prove that their proposed technical solution is at Technology Readiness Level (TRL) 6 or higher, the offeror shall identify all critical technology elements (CTEs) of the proposed design solution and provide the following:

a. Current TRL

b. Predicted TRL at contract award

c. The source of the ratings

d. Full substantiation with supporting data

L.8.3.2 Software Architecture – The offeror shall outline its integrated software development and management process, including the design, testing, integration, and qualification process, and outline how that process successfully supported similar programs. The offeror shall provide a detailed description of the software architecture to at least the Computer Software Configuration Item (CSCI) level across the Sentinel A4. The offeror shall express the software architecture using viewpoint and model syntax such as defined, for example, in the DoD Architecture Framework (DoDAF version 2.02).

The offeror shall provide predicted software performance estimates. The offeror shall provide software size and complexity estimates with supporting rationale and identification of reuse levels. The offeror shall outline its approach for planning for delivery of comprehensive Data Item Description compliant documentation, including DoDAF viewpoints and models, for software functional and performance requirements, software design, and software architecture. The offeror shall provide convincing rationale and evidence of how its proposed software design meets the requirements in the Sentinel A4 System Performance Specification (MIS-60990).

The description of each CSCI shall include identification of the developmental status (new, generative, modified, or use as is), and identify the programming languages and operating system used. The offeror shall identify software it plans to reuse from other programs or sources in the Sentinel A4 Radar. The offeror shall demonstrate the ability to successfully identify and reuse software source code or software execution elements from other programs similar to the Sentinel A4.

The proposal shall identify the correspondence of each CSCI to a Modular Open System Approach (MOSA) and document the Software Architecture Description using DoDAF syntax. The proposal shall identify the following:

a. Commercial Off-the-Shelf (COTS)

b. Government Furnished Property (GFP) Software

c. Army standard hardware and software support systems

d. Common software

e. Variation mechanisms used within the design of the Sentinel A4 software build(s)

f. Description of the offeror’s software design and documentation approach

g. Details on how the software design and processes meet the requirements and the program schedule

The offeror shall show how it will isolate critical program information (CPI) and critical technology elements in the software design.

The offeror shall identify all the prime contractor business unit(s), any other business unit(s) of the prime contractor and subcontractors developing software. For each identified team member, provide evidence of its Capability Maturity Model Integration (CMMI) Maturity Level Certification or Equivalency.

L.8.3.3 System Architecture and Integration The offeror shall present in detail its proposed system approach to convert a Sentinel A3 to a Sentinel A4. The proposal shall describe the System Architecture and Integration approach to achieve the interface requirements noted in the Sentinel A4 IDD. The proposal shall identify the architecture and substantiate the approach to achieving interfaces with the following:

a. Platform

b. Communications group

c. Prime power

d. Identification Friend or Foe

e. Remote Control Display Unit

f. Signal Data Processor (SDP)

Should the offeror choose not to use the GFP SDP, the offeror shall clearly present and substantiate its SDP solution and substantiate the approach for integration of the Composite Track/Classifier Processor into its design. The offeror shall identify reusing any additional Sentinel A3 components in its proposed design, outline how it will integrate those components into the design, and identify any integration risks incurred.

The proposal shall describe the offeror’s risk management approach to include the management structure and tools proposed to manage the risks. The approach shall substantiate the process the offeror will implement to manage contractor and subcontractor risks, issues, and opportunities. The proposal shall identify known risks associated with the proposed design and provide the mitigation plan associated with each identified risk. The offeror shall outline program tracking measures and metrics to monitor hardware and software development status and to retire risk.

The offeror shall provide the following for the offeror’s modular open systems approach:

a. Detailed description of the offeror’s modular open systems approach

b. Means for ensuring conformance to open standards and profiles throughout the development process

c. Description of how the technical approach ensures having access to mature as well as the latest technologies by establishing a robust, modular, and evolving architecture based on open standards that enhances interoperability and the ability to integrate new capabilities without redesign of entire systems or large portions thereof

d. Description of how the offeror will mitigate risks associated with reliance on a single source of supply over the life of the system to include, but not be limited to, technology obsolescence and dependence on proprietary or vendor unique technology

The offeror shall provide a detailed description of how the offeror’s proposed system architectural approach will allow for rapid and affordable technology insertion and refresh. The offeror shall describe how the proposed system will allow incremental system improvement through upgrades of individual hardware or software modules with newer modular components. The offer shall provide the outline of a cyclic software maintenance and refresh plan implementable after software delivery with predicted recurring engineering costs (in man-hours per year) of the sustainment cycle.

The offeror shall describe how it will employ hardware and software partitioning or other design techniques to isolate all proprietary, vendor-unique portions of interfaces, hardware, firmware and modules – at the lowest subsystem or component level. The proposal shall include documentation to support the rationale for a decision to integrate proprietary, vendor-unique or closed system hardware and/or software functions within the proposed system. This justification shall include documentation of the decision leading to the selection of specific solutions, e.g., with test results, architectural suitability, “best value” assessments, etc. The offeror shall describe how the integration of closed or proprietary, vendor-unique equipment, interfaces, data systems or functions due to a unique or specific system requirement will not preclude or hinder other component or module developers from interfacing with or otherwise developing, replacing, or upgrading open parts of the system. The offeror shall identify and propose steps to prevent the open elements of the system from intertwining with proprietary or vendor-unique elements in a manner that restricts or limits the ability to replace or upgrade the open elements using an open competitive selection process. The offeror shall describe and demonstrate that the modularity of the system design promotes identification of multiple sources of supply and/or repair, and supports flexible business strategies that enhance competition.

The offeror shall propose the extent to which the rights in Technical Data, computer software, computer software documentation, and inventions/patents offered to the Government ensure unimpeded, innovative, and cost effective production, operation, maintenance, and upgrade of the Sentinel A4 throughout its life cycle. The offeror shall outline how the Government’s rights allow for open and competitive procurement of Sentinel A4 production or enhancements and permit the transfer of the Sentinel A4 object code and source code to other contractors for use on other systems or platforms. The offeror shall identify subsystems and components that qualify for future full-and-open source of supply competitive procurements.

Offerors shall identify, to the extent known at the time of submittal, the Technical Data and computer software that the offeror, its subcontractors or suppliers, or potential subcontractors or suppliers, will furnish to the Government with restrictions on use, release, or disclosure. The offeror shall submit its data rights assertions and the basis of the assertions, including the assertions of its subcontractors or suppliers or potential subcontractors or suppliers, as a separate attachment to Volume 1a. These assertions do not count against the volume page limit.

L.8.3.4 System Security Engineering The offeror shall describe the use of its systems security engineering process in specifying and designing a system protected from loss of advanced technology, malicious insertion, tampering, and supply chain risks. The offer shall describe the offeror’s CPI identification, mission criticality analysis, vulnerability assessment, risk evaluation and countermeasure implementation in arriving at its system design. The offeror shall describe its secure design and coding practices.

L.8.3.5 Integrated Master Schedule The offeror shall propose a Sentinel A4 CWBS and CWBS dictionary developed IAW MIL-STD-881C. The CWBS shall be at Level 5 for hardware and software elements and Level 4 for all other elements. The offeror shall propose a detailed Integrated Master Schedule (IMS), utilizing the Department of Defense Integrated Program Management Report (IPMR) Implementation Guide, dated 05 February 2016, as guidance. The IMS shall link all critical processes and activities identified in the SOW. The IMS shall assume a contract start date of 01 May 2019 and be submitted in Microsoft Project and in Adobe Portable Document Format (PDF) formats. The IMS shall clearly indicate at least one unbroken critical path that reaches from contract award through the conclusion of Low Rate Initial Production and First Unit Equipped. The offeror shall submit the CWBS and IMS as an attachment to Volume 1a; they do not count against the volume page limitation.

L.8.4 System Producibility (Volume Ib)

L.8.4.1 Producibility and Maintainability Assessment The offeror shall present plausible evidence that the proposed design is producible and maintainable at an acceptable total ownership cost.

L.8.4.2 Manufacturing Approach The offeror shall propose the manufacturing build schedule. The offeror shall describe entry/exit criteria to assess manufacturing readiness points, and show how it will demonstrate through analysis or simulation the production capacity to meet the required delivery schedule. The offeror shall identify long-lead parts and materials required to meet the delivery schedule. The offeror shall detail its ability to provide all labor by skill, certification, and training. The offeror shall describe the program and operations management related to asset production. The offeror shall describe its manufacturing process for preparing for and producing the system. The offeror shall describe its approach to maintaining a quality system consistent with ISO 9001:2015, SAE AS6500, and MIL-HDBK-896A. The offeror shall propose its manufacturing and operating systems, product and process flow, facility requirements and selection criteria, site qualification plans, test planning, test equipment, expected yields, maximum production rate, and process control mechanisms. The offeror shall describe the tooling management approach from creation to delivery, and in-process documentation and procedures. The tooling management approach includes all special tooling.

L.8.4.3 Subcontracting and Supply Chain The offeror shall describe its subcontractor and supply chain management related to asset production. The offeror shall identify all key components supplied for integration and the related delivery schedules. The offeror shall describe the approach for all key components to maintain a quality system consistent with ISO 9001:2015, SAE AS6500, and MIL-HDBK-896A. The offeror shall identify any components to be manufactured or procured outside of the United States.

L.8.4.4 Assessment to Manufacturing Readiness Level (MRL) The offeror shall identify all critical manufacturing factors of the design solution. The offeror shall provide a MRL self-assessment using criteria within the current MRL Deskbook version. The offeror shall provide full substantiation with supporting data for all assessment criteria.

L.9. VOLUME II Past Performance This volume shall contain past performance information regarding similar contracts. This volume shall not exceed 25 pages plus five pages for each major subcontractor, excluding Past Performance Questionnaire Forms. Offerors shall submit all Government and commercial contracts for the prime offeror and each major subcontractor in performance or awarded during the past three years, from the issue date of this RFP, which are relevant to the efforts required by this solicitation. Relevant efforts are defined as services/efforts that are the same as or similar to the effort (as compared to the North American Industry Classification System, NAICS code 541712) required by the RFP. The offeror shall provide data concerning the offeror 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 that the Government will consider. Organize this volume into the following sections:

Section 1 – Contract Descriptions This section shall include the following information in the following format:

a. Contractor/subcontractor place of performance, Commercial and Government Entity (CAGE) Code, and Data Universal Numbering System (DUNS) Number. If the contractor 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)

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

c. Government’s technical representative/contracting officer representative and current email address, telephone, and fax numbers

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

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

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

g. 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.)

h. Awarded price/cost

i. Final or projected final price/cost

j. Original delivery schedule, including dates of start and completion or work

k. Final or projected final, delivery schedule, including dates of start and completion of work

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.

a. 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 delivery schedule revision and provide an explanation of why the revision was necessary. Address all Requests for Deviation and Requests for Waiver with respect to causes and corrective actions. The offerors shall also provide copies 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.

b. 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 GFP component failures, and number and nature of failures attributable to the offeror’s delivered product.

Section 3 – Subcontracts Offerors shall provide an outline of how the offeror will assign effort required by the RFP 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 10% of the total proposed cost/price. 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.

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. The offeror shall include Letters of Commitment in the proposal for these employees in order to be considered.

Past Performance Questionnaire. For all contracts identified in Section 1, Contract Descriptions, a Past Performance Questionnaire must be completed and submitted. The offeror shall complete Part I of the Past Performance Questionnaire and e-mail the questionnaire to both the Government contracting activity and technical representative responsible for the past/current contract. The POCs shall be instructed to electronically complete Part II of the questionnaire and e-mail the entire questionnaire to the Contracting Office no later than the proposal due date, to johnny.l.keith.civ@mail.mil. The offeror shall e-mail to the Contracting Officer a list of all the POC’s who were sent a questionnaire. The Government must receive this list no later than the proposal due date. The POC List shall be submitted in Word for Windows Table Format to include the following fields: Solicitation Number; Company Name; Contract Number; Government Agency; POC Last Name, First Name; POC Title; POC Telephone Number; POC E-mail Address; and Date E-Mail to POC (month/day).

Submissions. Offerors are discouraged from providing points of contact with another contractors’ facility, i.e., in case an offeror (or one of his/her team members) is in a subcontract with another contractor who has submitted a proposal on the same requirement. Offerors shall provide and submit the prime contract number and all Governmental agency POCs in lieu of subcontract numbers or prime contract POCs in situations as described above.

Small Business Participation Past Performance. All offerors shall submit information substantiating the offerors’ past performance in complying with FAR 52.219-8, “Utilization of Small Business”, maximizing opportunities for U.S. small business subcontractors. Offerors shall also provide a statement indicating whether any negative information has been reported in the past six years concerning the offerors’ past compliance with FAR 52.219-8. If any such negative information has been reported, the offeror may submit explanations or comments responding to such negative information. Offerors with no prior contracts containing FAR 52.219-8 shall certify the same.

L.10. VOLUME III Small Business Participation The offeror shall provide information for this factor to demonstrate and describe in detail the extent of participation of small businesses to include service-disabled veteran-owned small business concerns, HUBZone small business concerns, small disadvantaged business concerns, and women-owned small business concerns in performance of the contract. The offeror shall provide information to demonstrate and describe in detail the extent to which offerors identify and commit to small business performance of the contract, whether as a joint venture, teaming arrangement, or subcontractor.

Offerors shall propose a Small Business Participation Plan in accordance with the following format. The Small Business Participation Plan applies to both large and small businesses. The Government will incorporate the plan into any resultant contract.

The offeror shall submit the following to evidence small business participation:

a. Of the proposed TOTAL CONTRACT VALUE, not total subcontract value, identify the proposed dollar value and percentage of anticipated awards to small business. All percentages shall use TOTAL CONTRACT VALUE as a baseline. Include only first tier U.S. subcontractors.

Notes:

*Small business include the following: Small Business (SB), Small Disadvantaged Business (SDB), Women-Owned Small Business (WOSB), Historically Under-utilized Business Zone (HUBZone) small business, Veteran-Owned Small Business (VOSB), and Service-Disabled Veteran-Owned Small Business (SDVOSB).

**Include the prime offeror’s dollars and percentage. When combined, large and small business totals must equal 100%.

***Provide a chart for the basic contract period and each option period as well as a summary chart for the basic and all options.

If the prime offeror (to include any U.S. small business concerns who are proposing as part of a joint venture or teaming arrangement) is itself a U.S. small business concern under the NAICS, the offeror’s own participation as a SB, SDB, WOSB, HUBZone, VOSB, and SDVOSB will be considered small business participation to the extent it is qualified under the NAICS for the purpose of this evaluation.

b. All offerors, both small and large businesses, are required to submit Small Business Participation information in accordance with Defense Federal Acquisition Regulation Supplement (DFARS) 215.304 that shall include the following:

(1) Type of Business of Prime Contractor:

Check all applicable boxes

Large Business

OR

Small Business (also check type of Small Business below if applicable)

Small Disadvantaged Business (SDB)

Women-Owned Small Business (WOSB)

HUBZone Small Business (HUBZone)

Veteran-Owned Small Business (VOSB)

Service-Disabled Veteran –Owned Small Business (SDVOSB)

(2) Small Business Participation: Use the matrix below to propose your Small Business Participation. Indicate the total dollars and percentage of participation to be performed by large and small business and each type of small business subcategory. All percentages shall use TOTAL CONTRACT VALUE as a baseline. Count small businesses that qualify in multiple small business categories in each category. *Note: There is no minimum Small Business Participation goal for this requirement. This is a competitive requirement; therefore, the offeror should propose its best effort for all socioeconomic categories.

Note: Provide the information by base year, each option year, and a summary of the base and option years.

(3) Extent of Commitment: Describe the extent of commitment to use small businesses (for example: what types of commitments, if any, are in place for this specific acquisition either such as small business prime, written contract, verbal, enforceable, non-enforceable, joint venturing, mentor-protégé, etc.). Provide documentation regarding commitments for this effort including teaming agreements, commitment letters, etc. Provide copies of such agreements as an appendix to your Small Business Participation Plan. The appendix will not count against the page limitation for this volume.

(4) Intended subcontractors and principal supplies/services to be subcontracted: Identify the prime offeror and type of service/supply that the prime offeror will provide. Then list each of the intended subcontractors and principal supplies/services that the subcontractor will provide. Be as specific and detailed as possible (i.e., references to SOW) in describing the type of service or supply being provided by the prime and each subcontractor in order to demonstrate the variety and complexity of the work to be performed. Provide the CAGE code for the prime and each intended subcontractor. Also, provide the anticipated NAICS codes(s) that the prime offeror believes best describes the product or services being acquired by its subcontracts with each intended subcontractor. List small business primes and small business subcontractors that qualify as small businesses in multiple small business categories in each applicable small business category.

Large Business:

etc.

Small Business:

etc.

Small Disadvantaged:

etc.

Women-Owned Small:

etc.

HUBZone Small:

etc.

Veteran-Owned Small:

etc.

Service-Disabled

etc.

NOTES (1) and (2) above:

(1) Pursuant to Sections 8(d) of the Small Business Act, a concern is small for subcontracts which relate to Government procurements if it does not exceed the size standard for the NAICS code that the prime contractor believes best describes the product or services being acquired by the subcontract. In other words, the size of your subcontractors and suppliers is determined by the NAICS code of their subcontract, which may or may not be the same NAICS code as the one for your prime contract with the Government.

(2) Be as specific and detailed as possible in describing the type of service or supply being provided by the Prime and each subcontractor in order to demonstrate the variety and complexity of the work to be performed. Additional space other than this chart may be necessary to adequately address the required information.

c. Small Business Subcontracting Plan (for Large Business Only).

(1) Separate from the Small Business Participation Plan, other than U.S. Small Business, offerors must also submit a Small Business Subcontracting Plan meeting the requirements of FAR 52.219-9 and DFARS 252.219-7003 (DFARS 252.219-7004 for Comprehensive Subcontracting Plans). Large Businesses must submit an acceptable subcontracting plan to be eligible for award. Subcontracting Plans shall reflect and be consistent with the commitments offered in the Small Business Participation Plan.

(2) The Small Business Subcontracting Plan is not a requirement for evaluation (and will not be evaluated) in source selection, but rather, a requirement for award to a large business and will be incorporated into any resultant contract. The Government may hold negotiations or discussions regarding the Small Business Subcontracting Plan prior to contract award. Accordingly, the Small Business Subcontracting Plan should be submitted separately and is not be included as part of the Small Business Participation Volume. It will not count against the page limitation for the Small Business Participation Volume.

Important Note: Subcontracting plan goals are calculated as a percentage of total subcontracted dollars as opposed to small business participation plan goals that are calculated as a percentage of the total contract value.

L.11. VOLUME IV Cost/Price

L.11.1 Electronic Copy Cost/Price DVD-R requirements: Files contained on the Volume IV Cost/Price DVD-R may not be password protected. Electronic links are only permissible within the Cost/Price Volume. If files contain links, the links must be intact and maintained through all revisions. Do not include pivot tables in Excel spreadsheets. If the Government identifies discrepancies between the electronic proposal and the original hardcopy proposal, the original hardcopy proposal shall prevail.

L.11.2 Compliance Failure to comply with RFP requirements for cost/price information may result in an adverse assessment of an offeror’s proposal and reduce or eliminate its chance for award. Offerors shall ensure that the information presented in this volume is consistent and correlates with the information contained in the other proposal volumes. In addition, 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.

Proposals with unrealistically low or high costs or prices, initially or subsequently, may be grounds for eliminating a proposal from competition either on the basis that the offeror does not understand the requirement or has made an unrealistic offer. The offeror shall ensure that its proposal clearly demonstrates reasonableness with sufficient detail. The offeror is responsible for providing adequate evidence to prove credibility of proposed costs/prices.

L.11.3 General Instructions In accordance with FAR 15.402, 15.403-1 and 15.403-3(a) (1), certified cost or pricing data are not required because the Government expects adequate competition for this procurement. The offeror may provide information other than cost or pricing data in contractor format providing that additional information is required. The offeror shall submit information prepared following the instruction in FAR 15.403-5, Instructions for Submission of Certified Cost or Pricing Data and Data Other Than Certified Cost or Pricing Data. If after receipt of proposals the Contracting Officer determines that there is insufficient information available to determine price reasonableness and none of the exceptions at FAR 15.403-1 apply, the offeror may be required to submit additional cost or pricing data. Additionally, in the event that there is not adequate competition, the Contracting Officer may incorporate FAR 52.215-20 entitled, “Requirements for Cost or Pricing Data and Data Other Than Cost or Pricing Data,” into the solicitation and request a Certificate of Current Cost or Pricing Data.

The offeror shall base its cost/price proposal upon the offeror’s labor hours, labor rates and indirect rates/factors that are reasonable, realistic and achievable. The offeror shall provide sufficient details for the Government to evaluate the proposed skill mix, applicable base labor rates and the associated indirect rates for each Contract Line Item Number (CLIN). Direct labor rates shall identify the baseline (takeoff point) and projected escalation for each contract year. The offeror shall delineate direct labor hours and rates by labor category by contract year. The labor hour delineation must be directly traceable to the same information proposed in the Technical Volume.

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, Government Fiscal Year, and by CLIN, including fees and percentage.

Prime offerors are responsible for ensuring that the requirements of Section L.11, Cost/Price, are flowed down to each proposed subcontractor. Additionally, the prime offeror is required to fill out the RFP Attachment, "CAGE Code and Cognizant DCMA/DCAA Information", for itself and all proposed subcontractors. The prime offeror shall ensure that all Defense Contract Management Agency (DCMA) and Defense Contract Audit Agency (DCAA) information is current and provide the correct POC information. All proposed subcontractors with an aggregate total equal to or above $750,000 shall submit an un-sanitized proposal to the Contracting Officer. All proposal submission requirements in Section L.11 are applicable to the subcontractor submissions.

The offeror’s proposal shall include 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. 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.

If the proposed direct labor rates and indirect rates and factors 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. Application of FPRA rates and factors in an offeror’s proposal does not preclude the offeror from submitting the underlying support for subject rates if requested.

The offeror shall identify cognizant DCMA and DCAA POCs for the offeror and major subcontractor(s) in the proposal, along with their respective e-mail addresses and telephone numbers. An electronic copy of the cost/price proposal shall be submitted to these points of contact, no later than the proposal due date.

The offeror shall also provide the most current compliance status and date of adequacy/inadequacy determination for the following system: Accounting System and Purchasing System. If the offeror does not have an approved Accounting System, the Government may require a Pre-Award Survey.

In accordance with FAR 16.301-3(a)(3), Cost Reimbursement Contracts- Limitations, the offeror must have an accounting system that is adequate for determining costs applicable to the contract. The offeror shall provide a summary description of its accounting system, including indirect rate structure, and state whether it is compliant with Generally Accepted Accounting Principles (GAAP).