SEI Section L.pdf

FA8629-22-R-5031

Section L

19 November 2021

This document contains CONTROLLED UNCLASSIFIED INFORMATION (CUI) which must be protected under the Freedom of Information Act (5 U.S.C. 552) and/or the Privacy Act of 1974 (5 U.S.C. 552a). Unauthorized disclosure or misuse of this Source Selection Material and its attachments may result in disciplinary action, criminal and/or civil penalties.

Further distribution is prohibited without the approval of the Contracting Officer of this message unless the recipient has a need to know in the performance of official duties.

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS OR RESPONDENTS

1 PROGRAM INFORMATION

1.1 Program Structure and Objectives

The purpose of this contract is to modernize and sustain the Special Warfare (SW) Assault Kit (SWAK), a collection of body-worn equipment providing mission-specific and common information management capabilities. The System Engineering & Integration (SE&I) contract is needed to continue and combine the work accomplished under an existing Machine-to-Machine (M2M) software development contract. The SE&I contract will establish a Prime System Integrator to assist the Government in managing and modernizing SWAK in support of approximately 3,500 United States Air Force (USAF) SW operators. The USAF SW operators are assigned to Air Combat Command (ACC)/ Guardian Angel (GA), ACC/Tactical Air Control Party (TACP), Air Force Special Operations Command (AFSOC)/Special Tactics (ST) and Air Education & Training Command (AETC)/353rd Special Warfare Training Wing (SWTW). The contract will also provide support to SW Branch Foreign Military Sales (FMS) cases.

The Government intends to award one Indefinite Delivery/Indefinite Quantity (IDIQ) contract and intends to evaluate proposals using the Subjective Tradeoff methodology. The contracting activity conducting the SE&I source selection is AFLCMC/WISK, Wright-Patterson AFB, OH.

Initial contract award (Basic IDIQ and IDIQ Task Orders 0001 through 0006) will include program management support, systems engineering and related support, training support, and support for exercises and demonstrations. Procurement of software and limited quantities of hardware may be accomplished under additional task orders. Contract Line Item Number (CLIN) types are noted in the Model Contract. The Government reserves the right to not award a contract as a result of this solicitation.

2 GENERAL INSTRUCTIONS

The offeror's proposal must include all data and information requested by this Instruction to Offerors (ITO) and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the Performance Work Statement (PWS), Contract Data Requirements List (CDRL), and Model Contract. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation (see section 4.5.2 for proposal exceptions).

19 November 2021

The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal shall not simply rephrase or restate the Government's requirements, but shall provide convincing rationale to address how the offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their facilities or capabilities and will base its evaluation on the information presented in the offeror's proposal.

Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired.

The proposal validity period is specified in Section A of the model contract/solicitation. The offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid through this date.

In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals. The Government will destroy extra copies of such unsuccessful proposals, unless the offeror requests otherwise within 90 days of contract award.

2.1 Point of Contact

The Contracting Officer (CO), Capt Natalie Norlock, (natalie.norlock@us.af.mil) and the Contract Negotiator, Ms. Sarah Cooley, (sarah.cooley.1@us.af.mil) are the sole points of contact for this acquisition. Address any questions or concerns to the CO and Contract Negotiator.

Written requests for clarification may be sent to the CO and Contract Negotiator by email. Any questions shall be submitted prior to proposal due date. Answers to any such questions/clarifications will be provided on sam.gov and/or via RFP amendment.

2.2 Debriefings

The CO will promptly notify offerors of any decision to exclude them from the competitive range; whereupon, they may request and receive a debriefing in accordance with FAR 15.505.

Offerors excluded from the competitive range may request a pre-award debriefing or may choose to wait until after the source selection decision to request a post-award debriefing. However, offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The CO will notify unsuccessful offerors in the competitive range of the source selection decision in accordance with FAR 15.506. Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

2.3 Discrepancies

If an offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the CO in writing with supporting rationale as well as the remedies the offeror requests the CO consider as related to the omission or error. The Offeror is reminded that the Government intends to award this effort based on the initial proposal, as received, but reserves the right to conduct discussions if necessary. Electronic submittal of such notification is allowable.

2.4 Electronic Reference Documents

All referenced documents for this solicitation are available on the System for Award Management website at https://www.sam.gov/. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

2.5 Communications

Exchanges of Controlled Unclassified Information (CUI)/Source Selection Information (SSI) between Government and Offerors will be controlled by the CO, utilizing the DoD Secure Access File Exchange (DoD SAFE) to ensure proper encryption at https://safe.apps.mil/. If the Offeror needs to communicate with the CO regarding non-CUI/SSI information or to request a DoD SAFE-generated access code and hyperlink to drop-off (upload) non-CUI/SSI information regarding this solicitation, send an email to the points of contact in paragraph 2.1 of this document.

2.6 Bid and Proposal Costs

Offerors are advised that costs of any response to, or other costs incurred as a result of responding to this solicitation, are at the Offeror’s own risk. Any costs incurred in preparing a response to this solicitation may be attributable to bid and proposal (B&P) overhead costs, but may not be charged to any resulting awarded contract. B&P costs are indirect costs covered by CAS 420/FAR 31.205-18.

3 PROPOSAL PREPARATION INSTRUCTIONS

3.1 Volume Organization

The offeror shall prepare the proposal as set forth in Table 1. The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified in Table 1. The contents of each proposal volume are described in the ITO paragraph as noted in the table below:

TABLE 1 – PROPOSAL ORGANIZATION BY VOLUME

VOLUM

E

ITO

Paragrap h

VOLUME

TITLE

HARDCOPIES

(See Section L, para 3.8 for electronic submission)

PAGE LIMIT (EACH)

I

4.1 Executive Summary Volume

1 Hardcopy & Electronic

Submission

5, excluding Proposal Cross Reference Matrix

II

4.2 Technical and Technical Risk

1 Hardcopy & Electronic

Submission

Gate: 5 pages. Subfactors 1-6: 30 pages*

III

4.3 Cost/Price

1 Hardcopy &

Electronic Submission

Unlimited

IV

4.4 Past Performance

1 Hardcopy &

Electronic Submission

Unlimited

V

4.5 Contract

Documentation

1 Hardcopy & Electronic

Submission Unlimited

* The Integrated Master Plan/Integrated Master Schedule (IMP/IMS) and resumes do not count against the technical and technical risk volume page limit.

3.1.1 Page Limitations

Page limitations shall be treated as maximums. Each page shall be counted except the following:

cover, table of contents, glossary, acronyms, and index. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal and excess paper copies will be returned to the offeror as soon as practicable. Page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors.

3.1.2 Page Size and Format

A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 x 11 inches, not including foldouts. Pages shall be single spaced. Except for the reproduced sections of the solicitation document, the font shall be Times New Roman and the text size shall be no less than 12 point. Tracking, kerning, and leading values shall not be changed from the default values of the MS Word 2016 or later word processing or page layout software. Use at least 1-inch margins on the top and bottom and ¾-inch side margins. Pages shall be numbered sequentially by volume. These page size and format restrictions shall also apply to EN responses.

These limitations shall apply to both electronic and hard copy proposals.

Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible, and shall not exceed 11 by 17 inches in size. Foldout pages shall fold entirely within the volume, and 8.5 x 11 surface of a foldout shall be counted as a separate page (i.e. one 11 x 17 foldout equals 2 proposal pages). Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics not for pages of text. For tables, charts, graphs and figures, the text shall be no smaller than 8 point.

Integrated Master Schedules (subfactor 1) shall be provided in non-editable format with Predecessors/successors, duration, and critical path (if applicable) displayed. Start and End dates are notional for Source Selection purposes.

3.2 Pricing Related Data

All pricing information shall be addressed in the Pricing Volume and in Section L, Attachment 5, Pricing Matrix.

The offeror shall prepare and submit the cost/price proposal in PDF format and Excel 2016 formats. Format Files received in a format other than requested are unacceptable.

The offeror is encouraged to provide narrative substantiation and rationale in MS Word and any numerical source data, cost summaries, tables, calculations, or similar detailed information in MS Excel. For information submitted in MS Excel, the offeror should use formulas and functions to the maximum extent practical and avoid using output type “value only” cells. If links are utilized, the offeror shall provide those reference files. Spreadsheets and cells within spreadsheets shall not be protected. Worksheets within spreadsheets shall not be hidden. Offerors should make every attempt to make their quantitative data methodologies traceable and apparent.

Numerical data presented in the MS Word narrative that corresponds to a MS Excel submission must be clearly referenced. Numerical data pasted into MS Word as a picture out of another file is highly discouraged unless it is clearly referenced to a corresponding MS Excel file or its derivation is unambiguous. The offeror is responsible for ensuring that the information provided, whether in MS Word, or MS Excel is traceable throughout the Cost/Price Volume and the remainder of the proposal, as applicable.

3.3 Classified Information

Where classified information is required in the response, it shall be provided as a classified supplement and bound in a single classified volume. Each entry in the classified volume shall be referenced to the unclassified 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 volume where it can be found.

Binding shall conform to the same directions as those given in this ITO for unclassified portions.

The classified volume shall be separately bound with an applicable security designation color cover, conforming to DoD Manual 5200.01, “DoD Information Security Program,” February 24, 2012 the DD Form 254, and the Security Classification Guide provided in this solicitation.

3.4 Cross-Referencing

To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross referencing to other volumes of the proposal. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal. Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity.

The offeror shall fill out the Proposal Cross Reference Matrix in Section L, Attachment 1, indicating the proposal reference information as it relates to the ITO, PWS, CLIN numbers, and CDRL references found therein.

3.5 Indexing

Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume.

3.6 Glossary of Abbreviations and Acronyms

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

3.7 Binding and Labeling

Each volume of the proposal shall be separately bound in a three-ring, loose leaf binder permitting the volume to lie flat when open. Staples shall not be used. A cover sheet shall be bound in each book, clearly marked as to volume number, title, copy number, solicitation identification, and the offeror's name. The same identifying data shall be placed on the spine of each binder. 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 FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information. Identify "Controlled Unclassified Information" and "Source Selection Information--See FAR 2.101 and FAR 3.104" on all distributed materials.

3.8 Electronic Offers

The Government requests that the Past Performance Information utilizing the PPI Tool and the Past Performance Volume be submitted via DoD SAFE https://safe.apps.mil/ by XXX PM EST on XX Month 2021 to facilitate the work of the Past Performance Evaluation Team. The remainder of the proposal shall be submitted via DoD SAFE https://safe.apps.mil/ no later than XXX PM EST on XX Month 2021. In order to submit via DoD SAFE, a drop-off request is required. In order to receive a DoD SAFE drop-off, email both the CO and Contract Negotiator listed in Section

3.9 no more than 14 days and no less than 3 days prior to proposal submittal date. DoD SAFE is limited to a single drop-off with a limitation of 8 GB and 25 files. If proposal submission exceeds the DoD SAFE limitations additional submissions are allowed with email notification to both the CO and Contract Negotiator listed in Section 3.9.

Electronic submissions should be clearly marked as to volume number, title, solicitation identification, the Offeror's name, and the Commercial and Government Entity (CAGE) code. The same identifying data shall be marked in the electronic document footer. Use separate files to permit rapid location of all volumes, including subfactors within each volume, exhibits, annexes, and attachments, if any. 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 FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information. Identify "Controlled Unclassified Information" and "Source Selection Information--See FAR 2.101 and FAR 3.104" on all distributed materials.

The electronic proposal shall be submitted in a format readable by Microsoft (MS) Office. All MS- Excel attachments shall be submitted in the MS-Excel format (unaltered) in which they are provided by this Request for Proposal (RFP). The Offeror shall not include any formulas or links beyond what is included in the provided format. Macros or other embedded objects or features will be disabled as part of regular security precautions. Electronic files must be unlocked in order to export the winning Offeror’s information into Government contract writing system.

3.9 Distribution

Proposals shall be addressed to the CO and Contract Negotiator listed below and delivered to via DoD SAFE according to the instructions in Section 3.8.

CO:

Capt Natalie Norlock AFLCMC/WIS

XXXXXXXXXX

WPAFB, OH 45433

natalie.norlock@us.af.mil

Contract Negotiator:

Ms. Sarah Cooley AFLCMC/WIS

XXXXXXXXXXXXXXX

WPAFB, OH 45433

sarah.cooley.1@us.af.mil

Identify "Controlled Unclassified Information" and "Source Selection Information – FAR 2.101 and FAR 3.104” on all distributed mater

4 PROPOSAL ORGANIZATION

4.1 VOLUME I - Executive Summary

The offeror shall provide the following information in the Executive Summary volume:

a. Cover page

b. Narrative Summary

c. Table of Contents

d. Proposal Cross Referene Matrix

4.1.1 Narrative Summary

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

4.1.2 Table of Contents

Include a master table of contents of the entire proposal.

4.1.3 Proposal Cross Reference Matrix

Include a Proposal Cross Reference Matrix that provides traceability from RFP requirements to proposal volumes. Use Section L, Attachment 1, to complete the Proposal Cross Reference Matrix.

4.2 VOLUME II - Technical and Technical Risk

4.2.1 General

The Technical and Technical Risk Volume should be specific and complete. Legibility, clarity, and coherence are very important. The offeror’s response will be evaluated against the Technical subfactors defined in Section M, Evaluation Factors for Award. Using the instructions provided below, the offeror shall provide, as specifically as possible, the actual methodology proposed to be used for accomplishing/satisfying these subfactors. All threshold requirements specified in the solicitation are mandatory. By submitting a proposal the offeror is representing that the offeror’s firm will perform all the requirements specified in the solicitation. It is not necessary or desirable for offeror to tell the Government so in the proposal. Do not merely reiterate or reformulate the requirements specified in the solicitation.

4.2.2 Strengths

Strengths will be contractually binding upon contract award. A strength is defined as an aspect of an Offeror’s proposal that has merit or exceeds specified performance in excess of minimum PWS requirements in a way that will be beneficial to the Government. To incorporate strengths, the Offeror shall identify any strength it is attempting to obtain, substantiate any claim that the proposed approach is eligible for a strength, and make recommendations in the appropriate contractual document(s) to include Section J Attachments with change bars. The Government reserves the right to assess and award strengths, with or without discussions, and determine the final contract language to incorporate strengths into the contract. Simply repeating Section L, Section M, or PWS language as substantiation will not justify the Government’s evaluation of an approach as a strength.

4.2.3 Volume Organization

The Technical and Technical Risk Volume shall be organized according to the following general outline:

(1) Table of Contents

(2) List of Tables and Drawings

(3) Glossary

(4) Evaluation Gate (This shall be on separate pages from the following portions of the Technical and Technical Risk Volume to allow the materials to be separated during Source Selection).

(5) Subfactor 1 : Sample SWAK Task

a) Narrative and Integrated Master Schedule (IMS)

(6) Subfactor 2 : Understanding of the TAK environment/stakeholders

a) Narrative

(7) Subfactor 3: Staffing – Key personnel

b) Resumes and narrative

(8) Subfactor 4: Software Development Process

a) Narrative

(9) Subfactor 5: Developing Capabilities for dismounted operations

a) Narrative

(10) Subfactor 6: Small Business Participation

a) Narrative / Small Business Participation Commitment Document (SBPCD)

4.2.4 Technical and Technical Risk

In the Technical and Technical Risk Volume, the offeror shall address a technical solution for meeting the Government’s minimum performance or capability requirements of each technical subfactor.

4.2.4.1 Evaluation gate

4.2.4.1.1 The offeror shall provide a narrative that describes how the offeror has developed interfaces and applications to provide DACAS capability and Joint interoperability standards.

4.2.4.1.1.1 Measure of Merit: Shall describe the system supported, and specific waveform(s) and radio(s) that were integrated during development efforts, the interoperability standards that were applicable to the effort, and how those align to SWAK interoperability requirements. SWAK DACAS interoperability standards are IAW Attachment 3 - SE&I Primary DACAS Tactical Data Networks. Oferrors shall provide reference(s) for contracts where relevant work was performed (Contract name, number and Government POC). This gate is a pass/fail gate used to determine whether an offeror’s proposal will be evaluated.

4.2.5 Factor 1 – Technical and Technical Risk

4.2.5.1 Subfactor 1: Sample SWAK Task

This subfactor will evaluate the Offeror’s proposed approach to developing and delivering SWAK capability releases. (PWS 3.2)

4.2.5.1.1 Measure of Merit 1: The Offeror shall provide a detailed narrative showing a comprehensive understanding of the processes required to develop and integrate software and hardware into SWAK.

4.2.5.1.2 Measure of Merit 2: The Offeror shall provide an IMP/IMS showing all the required activities associated with a SWAK development/release cycle incorporating two ATAK plugins and replacement of an existing NSA-certified type one (crypto) DACAS radio (requiring integration of a new radio) within six months.

4.2.5.1.2.1 Measure of Merit 3: The IMP/IMS shall also show engineering releases IAW PWS paragraph 3.3.2, to include Minimally Viable Products and Deficiency Report fixes at the three month point.

4.2.5.2 Subfactor 2: Understanding of the TAK environment/stakeholderst

Offeror shall describe its approach to understanding of the TAK environment/stakeholders, roles and responsibility. (PWS 3.1.1.2., 3.2.1, 3.3.1)

4.2.5.2.1 Measure of Merit 1: The Offeror shall provide a narrative describing the key processes, procedures and interaction with members of the TAK Product Center. The Offeror shall also be able to describe the TAK variants, development products/tools, development procedures and necessary steps to deliver releasable MIL-TAK products to the Government.

4.2.5.3 Subfactor 3: Staffing Key Personnel

Offeror shall describe its approach to staffing key personnel.

4.2.5.3.1 Measure of Merit 1, provide a resume for proposed candidate and a narrative demonstrating proposed candidate meets the requirements and is capable of performing the tasks in PWS paragraph 3.1.1.1

4.2.5.3.2 Measure of Merit 2, provide a resume for proposed candidate and a narrative demonstrating proposed candidate meets the requirements and is capable of performing the tasks in PWS paragraph 3.1.1.2.

4.2.5.3.2 Measure of Merit 3, provide resume(s) for proposed candidate(s) demonstrating that the proposed candidate (s) meets the requirements per PWS paragraph 3.10.4, and is capable of providing all required training events as specified in PWS section 3.10 IAW applicable government standards.

4.2.5.3.3 Measure of Merit 4, provide a resume for proposed candidate demonstrating that the candidate meets the requirements in PWS paragraph 3.1.1.4 and is capable of accomplishing/leading the tasks in PWS paragraph 3.7.

4.2.5.4 Subfactor 4 Software Development Process

Offeror shall describe its approach to software development process

4.2.5.4.1 Measure of Merit 1: The offeror shall provide a narrative that describes the offerors approach to software development that is relevant to the five (5) main Special Warfare Mission Areas (Fires, Personnel Recovery, Assault Zones, Special Reconnaissance and Enabling Capabilities). The proposal should identify processes and procedures that align with current TAK Enterprise development standards and common/best practices, utilizing common software repositories and collaboration tools, such as Git and Slack, respectively. The narrative shall provide details of the proposed processes and procedures that enable a Continuous Integration/Continuous Delivery (CI/CD) DevSecOps pipeline.

4.2.5.5 Subfactor 5 Developing Capabilities for Dismounted Operations

Offeror shall describe its approach to developing capabilities for dismounted operations

4.2.5.5.1 Meaure of Merit 1: The Offeror shall provide a narrative that describes the offerors approach to implement Human Systems Integration principles throughout the systems engineering process to ensure SWAK remains operationally suitable and effective for dismounted operations. The proposal should identify specific focus areas that are uniquely applicable to dismounted operations. (PWS paragraph 3.4.2)

4.2.5.6 Subfactor 6: Small Business Participation

4.2.5.6.1 Measure of Merit 1: The offeror shall submit a Small Business Participation Commitment Document (SBPCD) which specifies the offeror’s level of commitment to small business utilization for effort to be performed against the attached model Task Orders. A SBPCD is required from all offerors, including small businesses. This also includes companies with commercial plans and comprehensive subcontracting plans. The winning offeror’s SBPCD will be incorporated as an attachment into the awarded contract. The SBPCD is separate from the Subcontracting Plan required by FAR 19.704. The SBPCD must address the following:

a. The extent to which the offeror will utilize small business, small disadvantaged business, women-owned small business, Historically Underutilized Business Zone small business, veteran-owned small business, and service-disabled-veteran-owned small business.

b. Level of commitment to use such firms identified above to include strength and specificity of commitment (commitment type, legal binding of commitment, and specificity of commitment in relation to SE&I).

c. Types of work to be performed by small business.

d. Statement of quantitative degree to which small businesses (including small business in all identified socio-economic categories) will participate in SE&I. Small business prime performance will count against proposed quantitative degree of small business participation.

e. Additionally, all offerors must submit the supporting documentation that will be excluded from the page count. This supporting documentation will NOT be incorporated into any resulting contract.

a. Past performance information to demonstrate compliance with the requirements of FAR 52.219-8, Utilization of Small Business Concerns, including the extent to which small business performance objectives/requirements were met for the contracts that required submission of a Small Business Participation Plan or other small business participation/utilization document. Copies of contractual reports may be submitted to validate compliance with requirements of FAR 52.219-8.

Explanation of efforts where minimum quantitative requirements and/or goals were not met should be provided. Supporting documentation shall be relevant to the requirements of this solicitation and shall be within the past five years. As mentioned previously, this documentation is excluded from the page count.

b. Past performance information to demonstrate compliance with the requirements of FAR 52.219-9 (DEVIATION 2016-O0009) Small Business Subcontracting Plan (when applicable), including extent to which applicable goals and other small business performance objectives/requirements were met for the contracts submitted to demonstrate compliance. Explanation of efforts where goals were not met should be provided. Supporting documentation shall be relevant to the requirements of this solicitation and shall be within the past five years. As mentioned previously, all supporting documentation is excluded from the page count.

f. The work to be performed directly by a small business prime offeror shall be evaluated as Small Business Participation. Small business prime offerors shall include their information in the above requested section 4.2.5.6, subparagraphs , a-d as required.

g. SBPCD enforceable, contractual requirements shall require periodic progress reporting to facilitate government monitoring in the event of an award. Offerors are to propose quarterly reporting for the requirements in section 4.2.5.6, subparagraphs , a-d.

h. Prime Offeror’s Size: Identify the applicable size and applicable socioeconomic categories for the PRIME offeror only when submitting your proposed SBPCD. Include this information within the initial section of the proposed SBPCD and check all applicable boxes:

a. Prime Offeror’s Size { } Other than Small Business or

b. { } Small Business also categorized as a

c. { } Small Disadvantaged Business (SDB)

d. { } Woman-Owned Small Business (WOSB)

e. { } Historically Underutilized Business Zone (HUBZone) Small Business

f. { } Service Disabled Veteran Owned Small Business (SDVOSB)

4.3 VOLUME III – Cost/Price

The Cost/Price volume contains no page limitations. However, all information provided must relate to Cost/Price. Cost/Price information submitted outside of the Cost/Price proposal volume or the model contract will not be evaluated in either the Cost/Price evaluation or the technical evaluation. The Cost/Price evaluations will be completely independent of the technical evaluations, so offerors must make certain that the Cost/Price volumes are freestanding and are concisely well-organized. Data beyond what is required by this instruction shall not be submitted, unless offerors consider it essential to document or support price positions. The Government Cost/Price evaluation team shall exercise its judgment to determine this information’s essentiality and reserves the right to exclude this information in its Cost/Price evaluation.

4.3.1 Determination of Adequate Price Competition

The PCO determines there is a high probability of adequate price competition in this acquisition.

Upon examination of the initial offers, the PCO will review this determination and if, in the Contracting Officer’s opinion, adequate price competition exists, no additional pricing information will be requested and certification under FAR 15.406-2 Certificate of Current Cost or Pricing Data, will not be required. However, if after receipt of proposals, the PCO determines that there is insufficient information available to determine price reasonableness and none of the exceptions in FAR 15.403-1, Prohibition on Obtaining Certified Cost or Pricing Data (10 U.S.C. 2306a and 41 U.S.C. Chapter 35) apply, at the CO’s request, the offeror shall be required to submit cost or pricing data as defined under FAR 2.101 (which may include other than certified cost and pricing data).

4.3.2 Cost/Price Structure

The Cost/Price volume shall consist of the sections detailed below. Each effort/task/deliverable identified in the PWS is identified with relevant CLINs.

4.3.2.1 General Information

(1) Table of Contents

(2) Costs/Price/Hours – The offeror shall propose costs/price/hours by Government Fiscal year, in Then Year dollars. The offeror should provide basis of escalation (if applied) and the methodology utilized for escalation. All prices are to be displayed by Contract Line Item Number (CLIN).

(3) Estimating System – The offeror shall provide a summary description of standard estimating system or methods. The summary description shall cover separately each major cost element (e.g., Direct Material, Engineering Labor, Manufacturing Labor, Indirect Costs, Other Direct Costs, Overhead, General & Administrative (G&A)).

Identify any deviations from stated standard estimating procedures in preparing this Cost/Price proposal volume. Indicate whether Government approval of stated system was obtained and, if so, provide evidence of such approval.

(4) The Offeror shall include any Forward Pricing Rate Agreements (FPRAs) by which the offeror and/or Government are bound. In the absence of the existence of an FPRA, offerors should submit adequate information for the Government to assess Indirect Costs, Overhead, G&A, and other indirect costs. This can be in the form of a Provisional Rate Approvement letter (or equivalent document).

(5) Purchasing System – The offeror shall provide a summary description of standard purchasing system or methods (e.g., how material requirements are determined, how sources are selected, when firm quotes are obtained, what provision is made to ensure quantity and other discounts). Identify any deviations from stated standard procedures in preparing this proposal. Indicate whether Government approval of stated system was obtained and, if so, provide evidence of such approval.

(6) Accounting System – The offeror shall indicate whether Government approval of accounting system was obtained and, if so, provide evidence of such approval. Identify any deviations from standard procedures in preparing this proposal. Also provide the name and contact information of the cognizant DCAA and DCMA field offices for purposes of verifying the approval, if such information is not already included in the Accounting System approval letter received from the cognizant agency.

(7) Changes to estimating, accounting practices, or Cost Accounting Standards (CAS) Disclosure Statement.

(8) Subcontractor Information - The offeror shall provide a list of all subcontractors, teaming partners, and/or venture partners performing work against all CLINs. The list shall provide the name, the contract value, whether the contract value is based on estimates, quotes, or negotiated subcontracts, contract type (i.e. Cost Plus Incentive Fee, Cost Plus Fixed Fee, Time & Materials (T&M), Cost Reimbursable (CR), Fixed Price Incentive Firm, or Firm Fixed Price), and the subcontractor’s Defense Contract Management Agency (DCMA) and Defense Contract Audit Agency (DCAA) POC.

(9) The Offeror shall provide the following additional information within its price proposal:

a. Cognizant Defense Contract Management Agency (DCMA) Office and POC

Information.

b. Cognizant Defense Contract Audit Agency (DCAA) Office and POC information.

(10) The offeror shall provide an explanation of ground rules and assumptions necessary to fully understand the cost estimates. Topics to be addressed should include, but are not limited to: technical and programmatic requirements (consistent with government requirements and proposal Technical and Technical Risk Volume), business base, labor and overhead rates, investments, cost-sharing arrangements, make or buy decisions, prime-subcontractor relationships, and price escalation. General information shall be provided in this section, with specifics addressed in the appropriate Basis of Estimate

(BOE).

(11) Integrated Master Schedule (IMS) - to support attainability of contract objectives, progress towards meeting program objectives, and integrate program schedule activities with related components. The IMS shall be free of any cost/price values. The IMS shall be consistent with the offeror’s CSOW, IMP, and WBS.

4.3.2.2 Pricing Matrix Workbook

(1) The offeror (prime only) shall complete the Pricing Matrix workbook found in Section L, Attachment 5 – using MS Excel format. Instructions are included in the Pricing Matrix workbook. The offeror is responsible for ensuring all formulas are correct and the Pricing Matrix reflects its proposed price.

(2) The offeror shall identify in the Pricing Matrix workbook any proposed Government Furnished Property (GFP). GFP means property in the possession of, or directly acquired by, the Government and subsequently furnished to the contractor for performance of a contract. GFP also includes contractor-acquired property if the contractor acquired property as a deliverable under a cost contract when accepted by the Government for continued use under the contract. Per FAR 45.0, GFP does not include intellectual property, software, or Government property that is incidental to the place of performance (when the contract requires contractor personnel to be located on a Government site, and when the property used by the contractor within the location remains accountable to the Government). GFP incidental to the place of performance includes, but is not limited to, Development Test/Operational Test ranges and equipment, and System Integration Laboratories (SILs).

(3) If the offeror require use of GFP beyond that listed in Attachment 2, the offeror shall provide a listing that addresses the required GFP. The offeror shall supply this information in the format shown below. The information shall be entered in Section L, Attachment 5, Pricing Matrix, of this RFP.

(4) To assist the offerors in completing their proposals, the following GFP clarifications are provided:

a) National Stock Number: The stock number of the item, as recorded in the Government’s supply system

b) Part Number: The item’s unique part identifier

c) Accountable Contract Under Which Item is Held: The contract number of the contract which currently holds title to the GFP item being requested

d) Name of the Item: The official name/descriptor of the asset

e) Quantity Required: The number of assets required

f) Need Start Date: The calendar date that the asset is first needed by the offeror

g) Need End Date: The calendar date that the asset is no longer needed by the offeror

h) Duration of Need: The amount of time that the asset is needed, measured in calendar days, from start date to end date of the use of the asset. The Pricing Matrix workbook will calculate this value

i) Unit Acquisition Value: For GFP, the then year dollar value assigned by the Government and identified in the accountable contract. The Offeror may use the latest Government Contract that is available as the basis for Unit Acquisition Value. For contractor acquired property, it is the cost of the asset derived from the Contractors records that reflects consistently applied, general accounting principles

j) Rental Equivalent Value: The then year value calculated by the Pricing Matrix Workbook IAW FAR 52.245-9 that will be added to the offeror’s Pricing Matrix (for evaluation purposes only), as an adjustment to minimize potential competitive advantage associated with the offeror’s proposed use of GFP.

Generally, the rate is approximately 2% of the unit acquisition value per month of use, the value not to exceed 100% of the unit acquisition cost.

k) Reason for Need: Explain how the asset will support the offerors’ program

(5) Additionally, in order to obtain use of GFP, the offeror shall provide written authorization from the cognizant Administrative Contracting Officer (ACO), where applicable, for each item requested, stating that the asset is available for the duration of need on a rent free, non-interference basis IAW FAR 45.301(e). If the offeror cannot support its GFP request with authorization from the cognizant ACO or PCO, then the offeror assumes responsibility for obtaining the asset commercially and the cost of that asset shall be included in their Cost/Price proposal.

4.4 VOLUME IV Past Performance

4.4.1 PastPerformance Information (PPI) Tool

Each offeror shall submit a PPI Volume with its proposal, containing past performance information IAW the format contained in Attachment 6.

4.4.2 Early Proposal Information

Offerors shall send Past Performance Questionnaire (PPQ), Attachment 7 directly to the points of contact for the past efforts identified. Offerors shall not fill out the PPQ prior to providing it to the points of contact mentioned above. All respondents shall be instructed that all responses are to be provided directly to the Government CO and Contract Negotiator identified in paragraph

3.9 not later than 15 calendar days prior to proposal due date. Offerors shall provide a listing of the individuals to whom the questionnaires were sent, with contact information (name, phone, email, etc.). This is needed in case the Government has to follow-up with any POCs for questionnaires not received. The evaluation team may conduct follow-up discussions with any of the POCs and reserves the right to send out additional questionnaires. This listing shall not be included in the volume page count. Failure to submit early proposal information will not result in offeror disqualification.

4.4.3 Recent and Relevant Contracts

Submit from one up to five recent contracts that you consider most relevant in demonstrating your ability to perform the proposed effort within the past 5 years from the date of issuance of this solicitation. Also include information on up to two of the five recent contracts performed by each of your teaming partners and significant subcontractors that you consider most relevant in deomonstrating their ability to perform the proposed effort. Each effort must have had at least six months of performance elapsed. Include rationale supporting your assertion of relevance. For a description of the characteristics or aspects the Government will consider in determining recency and relevance, see Section M, paragraph 2.3.2.1 –Recency Assessment, paragraph 2.3.2.2 – RelevancyAssessment.

4.4.3.1 Specific Content

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

4.4.3.2 Organizational Structure Change History

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

4.5 VOLUME V - Contract Documentation

4.5.1 Model Contract/Representations and Certifications

The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file. The offeror's proposal shall include a signed copy of the Model Contract, and Sections A through K as detailed below. Section J of the model contract is addressed in Paragraph 4.5.1.7.

4.5.1.1 Section A - Solicitation/Contract Form

The offeror shall complete blocks 12, 15a, 15b, 16 and provide signature and date in blocks 17 and 18 of the SF 33. Signature by the offeror on the model contract constitutes an offer, which the Government may accept. The "original" copy should be clearly marked under separate cover and should be provided without any punched holes.

4.5.1.2 Section B - Supplies or Services and Prices

Provide pricing information in Section B of the model contract, where applicable. Please note, quantity band pricing will be included in the attached Pricing Matrix, which will be attached to the awarded contract, without Total Evaluated Price (TEP) information.

4.5.1.3 Section F - Deliveries or Performance

Proposed Delivery Schedule. The offeror shall propose the delivery schedule by completing the blanks in Section F of the model contract.

4.5.1.4 Section G - Contract Administrative Data

The offeror shall supply information as applicable and as detailed in the Model Contract.

4.5.1.5 Section H - Special Contract Requirements

In the event an offeror proposes special terms and conditions determined to be beneficial to the Government, such terms and conditions may be captured in Section H. Note: the Government does not anticipate utilization of an H Clause at this time.

4.5.1.6 Section I - Contract Clauses

The offeror shall supply information, to include completion of all clause fill-ins, as applicable and as detailed in the Model Contract.

4.5.1.7 Section J – Attachments/Exhibits to the Model Contract

The offeror shall provide the following as attachments to the model contract pursuant to applicable FAR and DFARS provisions and guidance included in the model contract. Please see each corresponding attachment located within the Model Contract PDF for additional guidance.

All attachment identified below and submitted by the offeror will be incorporated into the awarded contract as contractually binding documents. Attachments are as follows:

4.5.1.7.1 Subcontracting Plan - Participation of Small Businesses (SB), Historically Black Colleges and Universities, or Minority Institutions (HBCU/MI)

If the offeror is other than a small business, the offeror shall submit a Small Business Subcontracting Plan (SBSP) in accordance with FAR 52.219-9 that also identifies and specifies the extent of offeror's commitment to the participation of small businesses (SB), historically black colleges or universities (HBCU) and minority institutions (MI), whether as joint venture members, teaming arrangement partners, or subcontractors. If applicable, submit a copy of an approved Master Plan. In the event the offeror has negotiated a comprehensive subcontracting plan pursuant to DFARS 219.702, the offeror must submit the information that identifies and specifies the extent of its commitment to the participation of SB, HBCU and MI. Proposed subcontracting plans will be evaluated by the contracting officer prior to acceptance in accordance with FAR Part 19, as supplemented. All information submitted towards the fulfillment of this paragraph must be consistent with information provided for Technical and Technical Risk Subfactor 4, “Small Business Participation”.

4.5.1.7.2 GFP List

The Government plans to provide the items listed in Section L, Attachment 2 as GFP. The proposed use of any additional GFP must be identified by the offeror in accordance with the requirements of Section L, Attachment 2. A list of approved GFP will be incorporated into the contract at award.

4.5.1.7.3 Performance Work Statement (PWS)

A PWS is provided as Attachment X to the model contract. The offeror shall use the PWS to propose to expand upon these minimum objectives to the extent necessary to fulfill the SWAK requirement. The proposed PWS shall define the tasks required for SE&I contract ensuring all minimum requirements of the Government provided PWS are addressed. The proposed PWS shall consist of tasking statements. Each tasking statement shall reference the CDRL items which will be delivered by that task. The proposed PWS shall not contain informational notes, as the Technical and Technical Risk volume provides ample opportunity for discussion and description of the offeror's approach, and the IMP and IMS provide the mechanisms for describing specific details of the offeror's approach. The tasking statements in the PWS and the IMP and IMS sections shall use a common numbering system. The proposed PWS shall follow the format of the Government provided PWS. The proposed PWS, when accepted by the Government, will be incorporated into the contract at award.

Offerors shall provide requirements language in the PWS for all strengths being attempted as part of this solicitation.