SEI Section L - 19 Apr 2022.pdf

FA8629-22-R-5031

Section L

11 April 2022

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 tradeoff methodology using FAR Part 15. The contracting activity conducting the SE&I source selection is AFLCMC/WISK, Wright-Patterson AFB, OH. Initial contract award (Basic IDIQ and first IDIQ Task Order for the Post-Award Conference) will include program management support, software development, systems engineering and related support, training support, and support for exercises and demonstrations.

Procurement of limited quantities of hardware may be accomplished under future task/delivery orders. Contract Line Item Number (CLIN) types are noted in the Model Contract.

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

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.

11 April 2022

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. Anne Kelly, ( anne.kelly.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.

11 April 2022

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 Offerors’ 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

VOLUME

ITO

Paragraph

VOLUME

TITLE

PAGE LIMIT (EACH)

I 4.1 Executive Summary Volume

5, excluding Proposal Cross Reference Matrix

II

4.2

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

III

4.3

Cost/Price Unlimited

IV

4.4

Past Performance

Unlimited

V 4.5

Contract Documentation

Unlimited

* Integrated Master Schedule (IMS), Small Business Participation Commitment Document (SBPCD) and résumés do not count against the technical volume page limit.

11 April 2022

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 Microsoft (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 electronic 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 equal’s 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 an Adobe PDF format with Predecessors/successors, duration, and critical path displayed. If necessary, Offerors should show individual SWAK releases as separate schedules to establish critical path, but must also annotate carry-over tasks from previous release cycles. Start and End dates are notional for Source Selection purposes.

3.2 Pricing Related Data

All pricing information shall be addressed in the Cost / Price Volume and in Section L, Attachment 5, Cost Formats.

See Section 4.3 for Volume III – Cost / Price Guidance

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

11 April 2022 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,” Volumes 1-3, Incorporating Changes through July 28, 2020, 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 Electronic Offers

The Government requires that the proposal be submitted via DoD SAFE https://safe.apps.mil/ no later than 3:00 PM on 1 June 2022. 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 classification markings such as CUI for “Controlled Unclassified Information” and 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 "Source Selection Information--See FAR 2.101 and FAR 3.104" on all distributed materials.

11 April 2022

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.8 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

WPAFB, OH 45433

natalie.norlock@us.af.mil

Contract Negotiator:

Ms. Anne Kelly AFLCMC/WIS

WPAFB, OH 45433

anne.kelly.1@us.af.mil

Identify "Source Selection Information – FAR 2.101 and FAR 3.104” on all distributed matter

4.0 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 Reference 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.

11 April 2022

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

4.2.1 General

The Technical 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 or capability requirements in a way that will be advantageous to the Government during contract performance. 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 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 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) Résumés and Narrative

11 April 2022

(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

4.2.4.1 Evaluation gate

4.2.4.1.1 The Offeror shall provide a narrative that describes how the Offeror has demonstrated at least six months of recent experience on a single development effort (within last five years) developing interfaces and applications to provide DACAS capability and Joint interoperability standards.

4.2.4.1.1.1 The Offeror 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. Offerors shall provide reference(s) for contracts where relevant work was performed (Contract name, number and Government POC).

4.2.5 Factor 1 – Technical

4.2.5.1 Subfactor 1: Sample SWAK Task

The Offeror shall provide the following information using the Sample SWAK releases outlined in Attachment 9.

4.2.5.1.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 The Offeror shall provide an 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 of order award. The IMS shall outline tasks down to the Project Working Level Schedule (Level 1 through Level 4).

4.2.5.1.2.1 The 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/stakeholders Offeror shall describe their understanding of the TAK environment/stakeholders, roles and responsibility.

11 April 2022

4.2.5.2.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 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. The Offeror shall propose appropriate labor categories for these positions. The Government does not intend to dictate the composition of the ideal team to perform this task order.

4.2.5.3.1 The Offeror shall provide a résumé 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 The Offeror shall provide a résumé 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 The Offeror shall provide résumé (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 The Offeror shall provide a résumé 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. (PWS 3.3, 3.4, 3.6, 3.7, 3.8, 3.9)

4.2.5.4.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 shall 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 The Offeror shall provide a narrative that identifies what attributes they would assess, for ensuring potential new SWAK improvements are operationally suitable and effective for body-worn equipment used in dismounted environments.” (PWS paragraph 3.4.2)

4.2.5.6 Subfactor 6: Small Business Participation

4.2.5.6.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, sub-paragraphs 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

4.3.1 General Instructions

The Cost/Price volume contains no page limitations Cost/Price information shall not be submitted in any other volume other than the Cost/Price volume, or as applicable, the Contracts Volume (i.e. model contract). Offerors must make certain that the Cost/Price volumes are freestanding and are concisely written and 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.

All pricing information shall be addressed in the Cost/Price Volume and in Section L, Attachment 5 Cost Formats.

The Offeror shall prepare and submit the cost/price proposal in Word format (proposal) and Microsoft Excel 2010 (cost 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.

11 April 2022

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.

These instructions are to assist the Offeror in preparing and submitting Data Other Than Certified Cost or Pricing Data as requested by the Contracting Officer in accordance with FAR 15.403-3. The Government needs this information in order to properly evaluate the reasonableness and balance of the Offeror's proposed Cost/Price. Additionally, this information will be used to properly evaluate the realism of the Cost Plus Fixed Fee and Cost Reimbursable CLINs. Compliance with these instructions is mandatory and failure to do so could result in the rejection of the proposal. Offers should be sufficiently detailed to demonstrate their reasonableness, realism, and balance. The burden of proof for credibility rests with the Offeror.

Information beyond that required by these instructions shall not be submitted, unless the Offeror considers it essential to support their proposed Cost/Price

Under no circumstances shall any cost or pricing documentation be included elsewhere in the proposal. The exception to this statement is in filling out the Model Contract in the Contracts Volume.

The Offeror shall also submit a sanitized Cost/Price volume including Cost Formats (Attachment 5), showing the labor hours proposed, bill of materials, other direct costs, and travel without any cost information. If there is discrepancy the unsanitized will take precedence.

The ground rules and assumptions (e.g., contract type, contract items, delivery schedule, GFI/GFE/GFP, etc.) of the prospective contract are provided in the appropriate sections of this RFP. Any subcontractor or interdivisional transfer (IDT) that will be responsible for 10% or more of the proposed price must submit separate Cost/Price volumes and Attachment 5 (Cost Formats) in accordance with the guidelines given to the prime contractor/Offeror below. The Offeror shall provide cost documentation and supporting rationale for all years in the schedule.

Offeror Price for all CLINS (to include Prime and all subs and interdivisional transfers) shall be clearly annotated and highlighted in Cost / Price Volume II for the Government in order to facilitate an accurate and fair assessment of all proposals. The Base Period and Options will be evaluated inclusively as part of the Total Evaluated Price (TEP) per FAR 17.203 (b). See Example below:

Total Price Amount Base Period $ Total X Option Year 1 $ Total X Option Year 2 $ Total X

11 April 2022

Option Year 3 $ Total X Option Year 4 $ Total X Option Year 5 $ Total X Total Price for Proposal All CLINS All Years $ Total X

4.3.1.1 Cost and Pricing Information

All cost and pricing information shall be addressed only in the Cost/Price Volume. The exception to this would be the Contract Volumes as applicable (i.e. Model Contract) Cost/Price information shall not be included in any technical or past performance volumes. Cost tradeoff information, work-hour estimates, and material kinds and quantities may be used in other volumes only as appropriate for presenting rationale for alternatives or design and tradeoff decisions. Basis of Estimate (BOE) information submitted shall be provided in a separate section of the Cost/Price volume that can be removed from the binder. As a reminder, the BOEs are only for the CPFF CLINs and CR CLIN X001, X002, X003, X006, X010, X011, and X012 (i.e. not to include the FFP CLINS and the rest of CR and CPFF Plug CLINS)

4.3.2 Preliminary Determination of Adequate Price Competition The PCO has determined 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 PCO’s opinion, adequate price competition exists no additional cost information will be requested and certification under FAR 15.406-2 will not be required. IAW FAR 15.403-1(b) and 15.403-3(a), information other than cost or pricing data may be required to support price reasonableness. Information shall be provided IAW FAR 15.403-5. 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 apply, the Offeror shall be required to submit certified cost or pricing data.

4.3.3 Ground Rules and Assumptions

The Offeror shall include a general discussion of the ground rules and assumptions (e.g., contract type, contract items, delivery schedule, GFI/GFE/GFP, etc.) used to develop the proposed prices.

All assumptions, scope limitations and/or qualifications of the cost/price proposal shall be addressed and explained. The Offeror shall list each exception to the instructions provided in the solicitation and each qualification of the Cost/Price Volumes, if any. The Offeror shall provide complete rationale for any exceptions. Other ground rules and assumptions of the prospective contract shall be provided in the appropriate sections of the proposal. Offerors are cautioned that any noncompliance with the terms and conditions of the RFP may cause their proposal to be determined not eligible for award.

4.3.4 Estimating Techniques and Methods

When responding to the Cost/Price Volume requirements in the solicitation, the Offeror and major subcontractors may use any generally accepted estimating technique, including contemporary estimating methods (such as Cost-to-Cost and Cost-to-Non-Cost Estimating Relationships (CERs), commercially available parametric cost models, in-house developed parametric cost models, etc.), to develop their estimates. Estimating techniques/methods must be in accordance with their Cost Accounting Standards (CAS) Disclosure Statement, if applicable. If necessary, reasonable and supportable allocation techniques may be used to spread hours and/or cost to lower levels of the Offeror’s CWBS. The Offeror shall identify all ground rules and assumptions used in developing the cost documentation.

4.3.5 CWBS and CWBS Dictionary

The CWBS and CWBS Dictionary, Attachment 8, shall serve as the Offeror’s framework for organizing and estimating for this effort. The Contractor shall extend the CWBS to the appropriate level required to provide adequate internal earned-value management (if applicable), surveillance, and performance measurement, regardless of the reporting level stipulated in the contract for Government visibility.

4.3.6 Subcontractor/Interdivisional Transfer Cost Proposals

Any subcontractor or interdivisional transfer (IDT) that will be responsible for 10% or more the proposed price must submit separate Cost/Price volumes (Cost/Price Volume and cost formats) in accordance with the guidelines given to the prime contractor/Offeror. All other subcontractor proposals should be integrated into the overall proposal by CWBS and CLIN. If a subcontractor considers any portion of cost documentation “proprietary,” preventing that portion from being fully integrated, that documentation shall be submitted under separate cover directly to the PCO.

This documentation must be submitted by the same date and time that the prime contractor/Offeror’s proposal is due to the PCO. This shall include a complete separate Cost/Price volume, to include cost formats. The quote submission shall be clearly marked as a subcontractor quote and shall identify the prime contractor under whom the submission is made.

The Offeror is responsible for the consistency of the cost data between the Offeror’s submission and the Subcontractor/IDT submission. Note: If the BOE for a subcontractor or IDT exceeds the 10% threshold that are included in the prime’s consolidated BOE, the subcontractor’s proposal need not include a separate BOE submission as long as there is a one-to-one match between BOEs and the subcontractor’s/IDT’s proposal.

The Offeror’s proposal shall uniquely identify major subcontractors, IDTs, and other subcontractor labor hours, material prices, and total burdened costs. The prime contractor/Offeror is responsible for the consistency of the cost data between the prime contractor/Offeror submission and the subcontractor/IDT submission. The prime contractor/Offeror shall provide a cost/price evaluation for all subcontractors. The evaluation must articulate the evaluation rationale that leads to the prime’s conclusion that the subcontract price is realistic and reasonable. Any price adjustments to all subcontractor/IDT submissions that are included in the prime proposal submission, including discounting or expected decreases to be achieved in negotiations, shall be fully identified and explained. All subcontractor, IDT, and vendor costs presented in the prime contractor/Offeror’s proposal shall include the prime’s indirect burden (e.g., General and Administrative (G&A) or handling burden).

4.3.7 Rounding

All dollar amounts provided shall be rounded to the nearest dollar, except that all labor rates shall be rounded to the nearest penny.

4.3.8 Cost/Price using Fiscal Years

Proposals shall be based on the Contractor Fiscal Year (CFY). The Contractors shall identify their CFY start and end dates, and the CFY placeholders in the cost formats should be replaced with the actual CFY designation (CFY20, CFY21, etc.). In addition, where instructed in the cost formats, quotes should be based on the Government Fiscal Year (1 October through 30 September).

If the period of performance of the CLIN will cross the Offeror’s accounting periods, the cost model will include a breakout of amount of hours and labor rates used in each accounting period of the CLIN. Blended rates will not be accepted in the cost model.

4.3.9 Cost / Volume

The Cost/Price volume shall provide comprehensive narrative support for the cost proposals. The Offeror shall provide a summary description of the standard estimating system and methods used. The summary description shall cover separately each major cost element (i.e., Materials, Engineering Labor, Manufacturing Labor, Indirect Costs and Other Direct Costs). The Offeror shall identify any deviations from these standard estimating procedures in preparing this proposal. The Offeror shall provide rationale to support cost realism and explain the methodology used to estimate the cost Offeror shall follow Cost / Price Volume III formatting layout

4.3.10 Cost / Price Volume Organization

The Cost/Price volume shall specify, by page number, where each cost format and each piece of narrative data is located. The Cost/Price volume shall consist of the following sections:

SECTION 1: Introduction SECTION 2: Materials/Services/Subcontracts Summary SECTION 3: Basis of Estimate SECTION 4: Other Information SECTION 5: Cost Formats - Submission of Cost Formats

4.3.10.1 Section 1: Introduction

The Offeror shall prepare a proposal summary that includes an introduction, table of contents, overview, summary descriptions of estimating, purchasing, and accounting systems, and, if applicable, changes to approved/disclosed purchasing, estimating, accounting systems or CAS Disclosure Statement. The Offeror shall provide a CLIN summary. Estimating techniques/ methods must be in accordance with their CAS Disclosure Statement, if applicable.

4.3.10.1.1 Estimating System Summary

The Offeror shall provide a summary description of its standard Estimating System and 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, G&A, etc.). The Offeror shall identify any deviations from its standard estimating procedures in preparing this Cost/Price volume. The Offeror shall indicate whether the Government has approved the system and, if so, provide evidence of such approval

4.3.10.1.2 Purchasing System Summary

The Offeror shall provide a summary description of its Purchasing System and 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). The Offeror shall identify any deviations from its standard procedures in preparing this proposal. The Offeror shall indicate whether the Government has approved the system and, if so, provide evidence of such approval.

4.3.10.1.3 Accounting System Summary

The Offeror shall provide a summary description of its Accounting System and methods.

The Offeror shall identify any deviations from its standard procedures in preparing this proposal.

The Offeror shall indicate whether the Government has approved the accounting system and, if so, provide evidence of such approval. The Offeror shall provide a current (within 12 months from date of proposal submittal) audit report, finding, or letter from the Offeror’s cognizant Administrative Contracting Officer or DCAA office stating that the Offeror’s Accounting System has been approved and/or is adequate for cost-type contracts. If it has been over 12 months since the Accounting System was reviewed, the Offeror shall provide a statement that the Accounting System has not changed since being reviewed. If the Accounting System has changed, a certification shall be provided indicating that the changes have not impacted the approval or adequacy of the Accounting System. If the cost accounting system is not approved, the Offeror shall so state and shall provide a plan for obtaining approval. In accordance with FAR 16.306(c), no cost-type contract may be awarded unless the limitations in FAR 16.301-3 are met. These clauses establish limitations that the contractor’s Accounting System be adequate for determining costs. No award of the SE&I task order with cost-type and/or cost CLINs can be made to an Offeror who’s Accounting System has not been determined to be adequate for cost-type. This impacts all team members/subcontractors/IDTs if the prime anticipates awarding cost-type to them. If no cost- type subcontracts are to be awarded, the Offeror shall so state. If cost-type and/or subcontracts/IDTs are to be awarded, the Offeror shall provide the necessary information from them.

4.3.10.1.4 Adequate Disclosure Statements

The Offeror shall provide a current (within 12 months from date of proposal submittal) audit report, finding, or letter from the Offeror’s cognizant ACO or DCAA office stating that the Offeror’s Disclosure Statement is adequate. If it has been over 12 months since the Disclosure Statement has been reviewed, the Offeror shall provide a statement that the Disclosure Statement has not changed since being reviewed. If the Disclosure Statement has changed, a certification shall be provided indicating that the changes have not impacted the approval or adequacy of the

Disclosure Statement. In accordance with FAR 30.202-6, a contracting officer shall not award a CAS covered contract until the Cognizant Federal Agency Official (CFAO) has made a written determination that a required Disclosure Statement is adequate. This impacts all team members/subcontractors/IDTs.

NOTE: In accordance with FAR Appendix 9903.201-1(b)(3), small businesses are exempt from all CAS requirements.

4.3.10.1.5 Earned Value Management (EVM) System Summary

Earned Value Management (EVM) is not required for SE&I

4.3.10.1.6 Explanation of Estimating Methods Used

The Offeror shall explain the methodology used to estimate each cost element and describe why it is a good estimating methodology. The Offeror shall illustrate whether it is analogous to another program, labor hour buildup, parametric estimating relationship, extrapolation from actual costs, or a particular cost tool.

4.3.10.1.7 Analogous/Historical Data

If historical data of comparable projects is used, the analogy of the projects shall be described and the following shall be provided: program name, contract number, specific phase of the program from which the historical data was extracted, and all activities (e.g., development, documentation, code development, test, training, etc.) that are included in the historical data used in the estimate. The Offeror shall provide rationale for any adjustments in the metrics being used.

The Government may request, and the Offeror shall provide, all referenced historical data and any other information used as the basis for any estimate. Where cost estimates are based upon past experience, the Offeror shall identify the past experience, explain how the past experience relates to the current effort, including similarities and differences, and how cost data available from the past experiences was adapted to the current effort.

4.3.10.1.8 Cost Tools

If cost tools are utilized (e.g., Software Evaluation and Estimation of Resources - Software Estimating Model (SEER-SEM), PRICE-H, etc.), the Offeror shall provide all copies of the files used as additional documentation for the BOEs. Justification for all inputs shall be included in the BOEs.

4.3.10.1.9 Productivity Rates

The Offeror shall identify any specific areas subject productivity rates. Also, the Offeror shall identify the data used to develop the rates and explain how this data related to current efforts.

4.3.10.1.10 Labor

A breakdown should be provided as Cost / Price Volume which shows the provided labor categories, labor rates and position descriptions. Contractor shall list man year hours on monthly and yearly basis.

Contractor shall provide Person Loading Schedule by CFY in a table expressed in Full Time Equivalent Format.

4.3.10.1.10.1 Labor Hours

If labor hours have been estimated based upon other than past experience and/or learning curve application, the Offeror shall provide detailed rationale on how they have been estimated. If standards were used, the Offeror shall identify and explain how they were derived and state whether or not they have been used on other programs. If other than normal procedures were used to estimate hours, the Offeror shall explain.

A breakdown should be provided which shows the provided labor categories, labor rates and position descriptions

4.3.10.1.10.2 Labor Skill Mix

The Offeror shall explain how the proposed labor hour skill mix has been derived and how the skill mix on this quote compares with the overall plant skill mix. The Offeror shall explain why the cost element requires an average, higher, or lower than average skill mix, as applicable. If the Offeror’s normal Estimating System uses a plant wide average for quote purposes, the Offeror shall so state.

4.3.10.1.11 Supporting Rationale for Fee

The Offeror shall provide supporting rationale for the Offeror’s proposed fee rates for CPFF

CLINS.

4.3.10.2 Section 2: Materials/Services/Subcontracts Summary

4.3.10.2.1 Materials

All materials, equipment, and licenses listed in the BOEs shall also be listed in the cost formats Bill of Material (BOM) table. See Section 4.3.13.8 Bill of Materials for specifics.

4.3.10.2.2 Other Direct Costs

All other direct costs (ODCs) listed in the BOEs shall be fully described and supporting rationale shall be provided.

4.3.10.2.3 Subcontract Analysis

4.3.10.2.3.1 Major Subcontractor/IDT Analysis

Any subcontractor or interdivisional transfer (IDT) that will be responsible for 10% or more the proposed price must submit separate Cost/Price volumes (Cost/Price Volume and cost formats) in accordance with the guidelines given to the prime contractor/Offeror. The Offeror shall provide a cost/price evaluation for major Subcontractors/IDTs. The evaluation must explain how the major Subcontractor/IDT effort relates to the overall effort and corroborate the justification that leads to the prime’s conclusion that the major Subcontractor/IDT price is reasonable and realistic.

4.3.10.2.3.2 Subcontractor/IDT Summary

The Offeror’s quote shall uniquely identify major Subcontractors/IDTs and other Subcontractors/IDTs for the entire effort. To support the identified costs of Subcontractors/IDTs, the Offeror shall include a summary in Section 2 of the Cost/Price Volume that identifies the following: name of Subcontractor/IDT, method of selection (i.e., competitive, non-competitive method, etc.), description of effort, type of subcontract, Subcontractor/IDT proposed price, and the Offeror’s adjusted price, if applicable. Any price adjustment made to Subcontractor/IDT submissions, including discounting or expected decreases to be achieved in negotiations, shall be fully identified and explained. An illustration of this summary can be found in the table below.

Subcontractor/

IDT

Method of

Selection

Description of

Effort

Type of Subcontract

Subcontractor

/IDT

Proposed Price

Offeror’s Adjusted

Price

Explanation of

Adjustment

4.3.10.2.3.3 Probable Subcontractors

The Offeror shall submit a list of the proposed probable subcontractors and IDTs showing the following: the supplier, description of effort, type of contract, price and hours proposed by each, price and hours…