Attachment 14 - Section L- Instructions to Offerors 27 Nov 24.pdf

FA945325RX002

Section L - Instructions, Conditions, & Notices to Offerors or Quoters L-I INFORMATION TO OFFERORS (ITO) and INSTRUCTIONS FOR PROPOSAL PREPARATION

1.0 Program Structure and Objectives

1.1 The objective of this contract is to provide required research, engineering, and technical management for performing space technology analysis, development, integration, experimentation, demonstration, and evaluation in support of the AFRL/RVE mission. AFRL/RVE, working with the other technical divisions within the directorate, conducts innovative research and development of ground, high-altitude balloon, near-space, and spaceflight experiments from the mission analyses, systems engineering, integration and testing of components and subsystems through system-level integration and test, and to the execution of experiment mission operations.

1.1.2 The contractor shall perform work supporting the development of space technology, and functional areas defined in the basic contract Statement of Work.

1.1.3 Table 1, below, provides an anticipated number of space technology programs the SSHINE contract will execute over the base five

(5) year effort. This information is for proposal purposes, only to give offerors a consistent workload indicator, and uses the definitions of large and small scale from the basic contract Statement of Work.

1.1.3.1 Table 1 is inclusive of flight experiments that predate the award of SSHINE.

1.1.3.2 Table 1 inherently accounts for the flow of programs from one stage of their respective lifecycles to the next.

1.1.4 Offerors should note that two key focus areas of SSHINE are not reflected Table 1- Workload Indicator: assembly, integration, and testing (AI&T) development and ground system development. Efforts in these areas will be continuous and ongoing, independent of the RVE program cadence.

1.1.5 Table 2, below, provides an anticipated government staffing matrix required to support anticipated work volume at the initial award of SSHINE.

Table 1 - Workload Indicator

SSHINE Deliberate/Expected Space Technology Programs

Functional Area

Year 1

Year 2

Year 3

Year 4

Year 5

Mission/System Dev (Large Scale*)

Mission/System Dev (Small Scale*)

Prototyping/AI+T (Large Scale*)

Prototyping/AI+T (Small Scale*)

Flight Operations (Large Scale*)

Flight Operations (Small Scale*) 3 3 3 3 3

*Large and Small Scale as defined in the Basic Contract Statement of work.

Table 2 - Government Reference Staffing Matrix

Requirement*

RVEP

RVEN

RVEX

Total FTE

Support (security, IT, purchasing, PM)

Engineering (mechanical, electrical, systems, network, aerospace, etc.)

Technicians (EGSE/cabling, building/vehicle ops, etc.)

Total

*Does not include contract management/administration

1.2 Budget/Funding Information:

1.2.1 The Government anticipates award of a single award IDIQ contract with a ceiling of $499M.

1.2.2 Notice to Offerors: Funds are not presently available for this effort. No award will be made under this solicitation until funds are available. The Government reserves the right to cancel this solicitation, either before or after the closing date. In the event the Government cancels this solicitation, the Government has no obligation to reimburse an Offeror for any costs.

1.2.3 Funding for SSHINE Task Orders is subject to Government fiscal year budgetary constraints and priorities. Due to volatile, uncertain and complex budgetary constraints at the Department of the Air Force level and possible impact to the SSHINE contract, the Government reserves the right to award none, some (at or above the guaranteed minimum), or all of the task orders set forth in this solicitation.

1.3 Contract Historical Background:

1.3.1 The work performed under similar contracts has historically consisted of numerous concurrent task orders organized by research topic area. SSHINE has adjusted this to align more closely to AFRL/RVE organization structure.

1.3.2 These requirements have historically been set aside for small business; likewise, this acquisition is also planned to be a total small business set-aside.

1.3.3 The Government intends to award a cost-plus fixed fee contract as a total small business set-aside. The North American Industry Classifications (NAICS) Code is 541715 and the small business size standard is 1,000 employees.

1.4 General Instructions:

1.4.1 This section of the Instructions to Offer (ITO) provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. Offerors are required to meet all solicitation requirements including terms and conditions, representations and certifications, Statement of Work requirements, Contract Data Requirements List (CDRL) requirements, DD254 requirements, as well as those identified as evaluation factors or subfactors. For each proposal submitted, the Offeror's proposal must include all data and information requested by this ITO and must be submitted in accordance with these instructions. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Non-conformance with the instructions provided in this ITO may result in an offeror being deemed non-responsive and ineligible for award. The Offeror shall clearly state in its contract documentation volume that the proposal is valid for 340 calendar days from the proposal due date.

Proposals not received by the closing date/time for the solicitation will not be considered. The proposal acceptance period is specified on Standard Form 33, Block 9 of the solicitation.

1.4.2 Submission instructions. Offerors are responsible for submitting proposals (including any revisions, and amendments) to the Government POC by the proposal due date specified in the solicitation. One (1) proposal package shall be submitted through DoDSafe (https://safe.apps.mil/). The proposal must be valid for a minimum of 340 days. The offeror may request a DoDSafe link from the Government POC listed in the solicitation. A drop-off request is valid for 14 days. You will receive an automated e-mail for your drop-off request within 2 business days, please follow-up with the Government POC. It is the offerors responsibility to confirm a complete proposal is received by the Government POC listed in the solicitation by the proposal due date.

1.4.2.1 The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government's requirements but rather shall provide convincing rationale to address how the Offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their experience and will base its evaluation on the information presented in the Offeror's proposal. Elaborate brochures or documentation, binding, detailed artwork, or other embellishments are unnecessary and are not desired.

1.4.2.2 This is an all-electronic solicitation release. Hard copies are not available. The Government will post all information pertaining to the solicitation and award of this requirement on the Contracting Opportunities website at https://sam.gov. The Government reserves the right to revise or amend the solicitation prior to the proposal closing time. Such revisions or amendments will be communicated by amendments to the Request for Proposal (RFP) and posted to the aforementioned website

1.4.2.3 The offeror's proposal must include all data and information requested in Section L and must be submitted in accordance with these instructions. Non- conformance with the instructions provided in this Section L and/or failure to meet a requirement may result in an offer being non-responsive and ineligible for award.

1.4.2.4 Offerors shall submit only one proposal as the Government will review only one proposal per offeror. Offerors MUST acknowledge all amendments in their proposal, either by completing SF 33 Block 14, providing signed copies of the amendments with their proposal, or by separate letter which includes a reference to the solicitation and amendment numbers. Furthermore, the Government reserves the right to cancel this solicitation at any point before contract award. In the event this solicitation is cancelled, the Government has no obligation to reimburse offerors for any costs incurred.

1.4.2.5 Proposals, modifications, and/or revisions received after the proposal due date/time will be "late" and will not be considered unless the Contracting Officer determines the criteria set forth in FAR 15.208 exists.

1.4.3 In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals.

2.0 General Information

2.1 Point of Contact. The Contracting Officer (CO) is the sole point of contact for this acquisition and may be reached at brittney.santiago@us.af.

mil.

2.2 Discrepancies. The Government is committed to ensuring the solicitation requirements are accurate, complete, and fair. If an offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, it is the offeror's responsibility to immediately notify the Point of Contact (POC) identified in Section L-2.1 of this solicitation in writing.

2.2.1 The notification shall include:

2.2.1.1 A clear description and location of the perceived error, omission, or unsound requirement.

2.2.1.2 Supporting rationale.

2.2.1.3 A specific description of the remedies the offeror is asking the Contracting Officer to consider, including any proposed changes to the solicitation requirements.

2.2.2 The notification shall be submitted via email to the POC at brittney.santiago@us.af.mil, by the date and time identified in the final RFP released at a later date. The Contracting Officer will review the offeror's rationale and may, at their discretion, consider the proposed remedies.

2.2.3 Please note that failure to notify the Government of a perceived error, omission, or unsound requirement may result in the offeror's proposal being evaluated based on the solicitation requirements as written. Therefore, it is essential that offerors carefully review the solicitation requirements and notify the Government promptly of any concerns.

2.3 Clarifications. IAW FAR 15.306(a)(2), If award will be made without conducting discussions, offerors may be given the opportunity to clarify certain aspects of proposals or to resolve minor or clerical errors. Offerors are not given an opportunity to respond to any identified weaknesses or deficiencies or revise their proposals. Clarifications shall be documented on, and conducted via transmittal of, Evaluation Notices (EN) to the applicable offeror. Each EN shall clearly indicate that the type of exchange being conducted is "Clarification."

mailto:brittney.santiago@us.af mailto:brittney.santiago@us.af.mil

2.4 Discussions. IAW FAR52.215-1(f)(4), the Government intends to evaluate proposals and award the contract without discussions with offerors.

Therefore, the offeror's initial proposal should contain the offeror's best terms from a cost or price and technical standpoint. The Government reserves the right to conduct discussions if the Contracting Officer later determines them to be necessary. If the Contracting Officer determines that the number of proposals that would otherwise be in the competitive range exceeds the number at which an efficient competition can be conducted, the Contracting Officer may limit the number of proposals in the competitive range to the greatest number that will permit an efficient competition among the most highly rated proposals.

2.5 Competitive Range. If the Government holds discussions, the CO will establish a competitive range IAW FAR15.306(c)(1) procedures and this solicitation. IAW FAR15.306(c)(2), the Government also reserves the right to limit the number of proposals in the competitive range to the greatest number that will permit efficient competition among the most highly rated proposals. If the contracting officer, after complying with paragraph (d)(3) of the aforementioned FAR section, decides that an offeror's proposal should no longer be included in the competitive range, the proposal shall be eliminated from consideration for award. Written notice of this decision shall be provided to unsuccessful offerors IAW 15.503.

2.6 Evaluation Notices. If during the evaluation period, it is determined to be in the best interest of the Government to hold discussions, offeror responses to Evaluation Notices and the Final Proposal Revision will be considered in making the source selection decision.

2.7 Debriefings. The CO will promptly notify Offerors of any decision to exclude them from the competitive range, whereupon Offerors may request and receive a debriefing in accordance with FAR 15.505 or 15.506, as applicable.

2.8 Electronic Reference Documents. All referenced documents for this solicitation are available on the System for Award Management (SAM.gov) website at http://www.SAM.gov. Offerors are encouraged to register for real-time e-mail notifications when information has been posted to the website for this solicitation.

2.9 Oral Presentations. The Government shall not accept oral presentations in response to this solicitation.

2.10 Communications. During the source selection, exchanges of source selection information between Government and Offerors shall be controlled by the CO. The CO has determined that the use of electronic communication is appropriate. Email may be used to transfer information between the Government and the Offerors, only if the email can be sent encrypted and includes "Source Selection Information - See FAR 2.101 & 3.104" in the Subject line.

2.11 System for Award Management (SAM) Registration. To be eligible for award, offerors must be registered in the SAM database with the purpose of registration reflecting "all awards" prior to submitting a proposal. Additionally, offerors shall be registered as a small business under the appropriate NAICS for this acquisition. Offerors can register at www.sam.gov. The Government will not consider proposals from offerors that are not registered in SAM.

2.12 Security Classification. A DoD Contract Security Classification Specification, DD Form 254, will be incorporated as part of the contract. The Offeror shall have the ability to administratively process up to TS/SCI eligible personnel to perform the work required on this contract. Key personnel shall possess a current DoD Top Secret/SCI clearance on day one of contract award. All other personnel will be required to have security clearance as identified in the DD254. Please refer to paragraph 2.16 below for instruction on how to request information on security billets required for each task order.

2.13 Cybersecurity Requirement: NIST SP 800-171 DoD ASSESSMENT. In accordance with the National Defense Authorization Act (NDAA) for Fiscal Year 2020, Section 889, and the DoD's implementation of the Cybersecurity Maturity Model Certification (CMMC), offerors must meet the requirements of the National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171, "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations". To be eligible for award, offerors must have completed a DoD Assessment, as described in the NIST SP 800-171 DoD Assessment Methodology, to determine their compliance with the NIST SP 800-171 security requirements. Assessment requirements are outlined in DFARS provision 252.204-7019.

2.14 Contract Limitations. The Government intends to award one single award IDIQ contract and up to three (3) initial Task Orders (TO) under the SSHINE Request for Proposal (RFP).

2.14.1 TO 0001: Prototypes and Flight Experiments (RVEP).

2.14.2 TO 0002: Small Satellite Portfolio (RVEN).

2.14.3 TO 0003: Rapid Architecture Prototyping and Development (RVEX).

2.15 Offerors shall assume that all work identified in the task order SOWs is to be performed concurrently.

2.16 Controlled Documents. Copies of the following SSHINE documents may only be obtained through special request to the Contracting Officer via email. Requested items will be provided via SAM.gov.

- Base Support List (Controlled Attachment in Section J)

- Staffing Plan Template (Controlled Attachment in Section J)

- Security Billets Information per Task Order (Controlled attachment in Section J) http://www.sam.gov/ http://www.sam.gov/

2.17 The Offeror shall prepare the proposal as set forth in Table 3- Proposal Organization. The titles and contents of the volumes shall be as defined in Table 3, all of which shall be within the stated page limits as specified. The contents of each proposal volume are described in the ITO paragraph as noted in the Table-3.

Table 3 - Proposal Organization

Volume

Title

Attachments

Page Limit

Due Date/Time

I

Executive Summary

No Requirement

TBD

II

Technical

SSHINE Staffing Plan Spreadsheet

III

Cost/Price

Unlimited

IV

Contract Documentation

Solicitation/Model Contract

V

Compliance Documentation

2.18 Page Limitation, Size, and Format. Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read and will not be considered in the evaluation of the proposal. Page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the notices of ENs to the Offerors. The following will not be counted towards total page count limitations: cover pages, tables of contents, glossaries, acronym lists, list of tables and drawings.

2.18.1 A page is defined as US Letter (8.5"x11") no less than single-spaced as defined in paragraph settings/spacing in Microsoft Word and character spacing shall be Microsoft Word default setting, "Normal." Except for the reproduced sections of the solicitation document, the text size shall be no less than 12 point; font shall be Times New Roman.

Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1-inch margins on the top and bottom and 3/4-inch side margins. Pages shall be numbered sequentially by volume. These page size and format restrictions shall apply to responses to ENs.

2.18.2 Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. For tables, charts, graphs and figures, the text shall be no smaller than 8 points. These restrictions shall apply to responses to ENs. Provide formulas used in all spreadsheets.

2.19 Cost or Pricing Related Data. All cost or pricing data shall be addressed ONLY in the Cost/Price Proposal (Volume III) and Contract Documentation (Volume IV). 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 trade off decisions.

2.20 Classified Information. The Government anticipates that proposals will be unclassified. However, if an Offeror determines that the submission of classified information is necessary, the Offeror, prior to the submission of its proposal, shall contact the Contracting Officer listed in this solicitation. The Contracting Officer will determine the applicability of the information and, if necessary, coordinate the appropriate means of its submission. Offerors shall notify the Government as early as possible to allow for adequate processing. Any information shall be provided as an addendum to the technical proposal and shall be held to the same time and date proposal submission requirements.

2.21 Indexing. Each proposal volume shall contain a detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections. Each proposal 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. Each proposal volume shall contain a detailed table of contents to delineate the subparagraphs within that volume.

2.22 Glossary of Abbreviations and Acronyms. Each proposal volume shall contain a list of tables and drawings included in each volume. The list of tables and drawings do not count against the page limitations for their respective volumes.

2.23 List of Tables and Drawings. A cover sheet shall be included in each volume, clearly marked as to volume number, title, copy number, solicitation identification, and the Offeror's name. This will not be counted towards page count limitations. 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.

2.24 Cross Referencing. To the greatest extent possible, each proposal 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. Cross referencing within a proposal volume is permitted where its use would conserve space without impairing clarity. The contractor shall incorporate a Cross-Reference Matrix as outlined in Section 3.1.2.

2.25 Proposals shall be marked "Controlled Unclassified Information" and "Source Selection Information (See FAR2.101 and FAR 3.104"), addressed to the CO.

3.0 Volume I- Executive Summary

3.1 Provide a concise narrative summary of the entire proposal, highlighting key or unique technical features and addressing any significant risks.

The salient features discussed in the executive summary shall tie to the evaluation factors and subfactors identified in Section M. No cost/price information shall be discussed in the Executive Summary. Any summary material presented is intended for overview purposes only and shall not be evaluated or considered as meeting the requirements for any portions of other volumes of the proposal. The Executive Summary shall not exceed three (3) pages in length.

3.1.1 The executive summary will include a master Table of Contents of the entire proposal. This will not be counted towards page count limitations.

3.1.2 The Offeror shall submit a Cross Reference Matrix indicating the proposal reference information as it relates to the Information to Offerors, SOW, CLIN numbers, and CDRL references, with the corresponding proposal paragraph(s) in that section which addresses the reference item. This will not be counted towards page count limitations.

4.0 Volume II - Technical Volume

4.1 The Technical Volume should be specific and complete. Legibility, clarity, and coherence are 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, provide as specifically as possible the actual methods and experience you will draw on for meeting the requirements of each subfactor. All the requirements specified in the solicitation are mandatory. By submitting this 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 to state so in the proposal. The Offeror shall critically analyze the Government’s requirements and not merely reiterate the objectives or reformulate the requirements specified in the solicitation. The Offeror shall not include any Cost/Price information within the Technical Volume.

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

4.2.1 Table of Contents

4.2.2 List of Tables and Drawings

4.2.3 Glossary of Abbreviations and Acronyms

4.2.4 Factor 1: Basic Statement of Work Narrative

4.2.4.1 Subfactor 1: Corporate Management

4.2.4.2 Subfactor 2: Overarching Technical Approach

4.2.5 Factor 2: Scenario Response

4.2.5.1 Subfactor 3: FALSESat Scenario

4.2.5.2 Subfactor 4: RVESat Scenario

4.2.5.3 Subfactor 5: HWIL/SWIL Scenario

4.2.6 Factor 3: Staffing Plan

4.2.6.1 Subfactor 6: Overview Matrix

4.2.6.2 Subfactor 7: Staffing Plan for TO 0001 RVEP

4.2.6.3 Subfactor 8: Staffing Plan for TO 0002 RVEN

4.2.6.4 Subfactor 9: Staffing Plan for TO 0003 RVEX

4.2.6.5 Subfactor 10: Cross-Utilization Matrix

4.3 Page Limits, Format, and Specific Content:

4.3.1 The narrative aspect of the Technical Volume shall not exceed one hundred (100) pages total.

4.3.1.1 Factor 1 has a page limit of seventy-five (75) pages.

4.3.1.1.1 Subfactor 1 has a maximum page limit of fifteen (15) pages.

4.3.1.1.2 Subfactor 2 has a maximum limit of sixty (60) pages.

4.3.1.2 Factor 2 has a page limit of twenty (20) pages.

4.3.1.2.1 No Subfactor for Factor 2 may exceed ten (10) pages in total.

4.3.1.3 Factor 3 consists of a spreadsheet, template provided as Attachment 9, and optional explanation.

4.3.1.3.1 Subfactors 6-10 will each require a separate tab in the spreadsheet. The spreadsheet does not count towards the proposal page limits.

4.3.1.3.2 Factor 3 and related subfactors may have an accompanying narrative description/explanation that has a maximum limit of five (5) pages.

4.3.2 In addition to the narratives, the Offeror may substantiate any prime, subcontractor, and/or teaming partner experience referenced in the technical proposal by providing corroborating documentation. Some examples of corroborating documentation are listed below, and can be tailored to address the specific approach captured in the proposal:

4.3.2.1 Test Plans/Procedures.

4.3.2.2 Systems Engineering Management Plan and/or Processes.

4.3.2.3 Relevant sections of technical reports.

4.3.2.4 Abstracts of articles and with relevant citation, if available.

4.3.2.5 The provided corroborating documentation shall not exceed a combined page count of fifteen (15) pages and must be cross-referenced within the proposal.

4.3.2.5.1 The provided corroborating documentation will be counted toward the overall sixty (60) page limit of the subfactor 2 overarching technical approach.

4.4 Factor 1: Basic Statement of Work Narrative

4.4.1 Subfactor 1: Corporate Management

4.4.1.1 The Offeror shall provide a narrative that describes an overarching corporate management approach.

4.4.1.1.1 The narrative shall describe how the Offeror plans to manage the full scope of the contract performance (including schedule, and technical performance).

4.4.1.1.2 The narrative shall describe effective utilization of proposed subcontractors and/or teaming partners throughout contract performance.

4.4.1.1.3 The narrative shall describe how the offeror will recruit and retain experienced personnel, including key personnel, necessary for accomplishing the contract requirements from contract start through transition and the full period of performance.

4.4.1.1.4 The Offeror's corporate organizational structure and corporate management approach (to include subcontractors and/or teaming partners, as applicable) and its application to the SSHINE organizational structure and SSHINE management approach (this shall include an organizational chart delineating positions/roles/responsibilities)

4.4.1.1.5 The Offeror's approach for meeting scalable surge requirements while maintaining contract performance in accordance with Government priorities across multiple, concurrent Task Orders.

4.4.1.1.6 The Offeror shall provide an organizational conflict of interest mitigation plan in accordance with section

6.12 and FAR Subpart 9.5 Organization and Consultant Conflicts of Interest.

4.4.2 Subfactor 2: Overarching Technical Approach

4.4.2.1 The Offeror shall provide a narrative description of the overarching technical approach (which may be augmented by diagrams, flow charts, drawings, pictures, etc.) that:

4.4.2.1.1 Shows the offeror meets the requirements as specified in basic contract Statement of Work.

4.4.2.1.2 Demonstrates the Offeror's plan to apply cradle-to-grave space systems engineering processes, utilizing documented, and proven systems engineering standards and practices for space flight/ground systems, subsystems, and components.

4.4.2.1.3 Demonstrates the Offeror's experience in tailoring space systems engineering processes to accommodate small-scale and large-scale missions as defined in the basic contract Statement of Work.

4.4.2.1.4 Provides a narrative description of their technical approach for performing the requirements outlined in the Task Order 0001 RVEP SOW which may be augmented by diagrams, flow charts, drawings, pictures, etc.

4.4.2.1.5 Provides a narrative description of their technical approach for performing the requirements outlined in the Task Order 0002 RVEN SOW which may be augmented by diagrams, flow charts, drawings, pictures, etc.

4.4.2.1.6 Provides a narrative description of their technical approach for performing the requirements outlined in the Task Order 0003 RVEX SOW which may be augmented by diagrams, flow charts, drawings, pictures, etc.

4.5 Factor 2: Scenario Responses.

4.5.1 Subfactor 3: The offeror will provide a technical approach narrative describing how they would respond to a notional program task order. This notional program does not reflect a specific current or anticipated requirement of SSHINE but is considered in character with a plausible surge requirement and program task order.

4.5.1.1 The task order concerns the notional development of the Functional Assessment of a Labor Surge Example Satellite (FALSESat) and is titled TO 0005 FALSESat.

4.5.1.2 The offeror received initial notice of TO 0005 FALSESat six (6) months after the initial award of the basic contract and the three initial task orders.

4.5.1.3 TO 0005 FALSESat is being awarded seven (7) months after the initial award of the basic contract and the three initial task orders, and one (1) month after initial notice.

4.5.1.4 FALSESat is a large-scale program and has a government program management office in RVE, which includes a government Program Manager, Chief Engineer, and Lead Systems Engineer.

4.5.1.5 FALSESat has an approved technical baseline and has completed its critical design review.

4.5.1.6 FALSESat has a complex experimental payload, primarily developed by notional company: Incomplete Aerospace. The payload development contract originally awarded to Incomplete Aerospace has a technical period of performance that expires at the same time TO 0005 FALSESat is awarded, with the payload in an incomplete state.

4.5.1.6.1 The remaining tasks to complete the payload are related to fabrication, assembly, integration, and environmental testing. There is no known requirement for design or redesign work.

4.5.1.7 There is a spacecraft bus intended as government furnished equipment for the original Incomplete Aerospace contract.

During this scenario, that bus is housed in RVE facilities on Kirtland AFB.

4.5.1.8 FALSESat has had Mission and Space System Development work performed under TO 0001 RVEP, amounting to 0.5 FTE from a SSHINE systems engineer and two (2) weeks of support from six (6) other engineers (varying specialties) supporting Critical Design Review.

4.5.1.9 The government program team has determined the lowest risk course of action for the program is to finish development of the Incomplete Aerospace payload and integrate the payload with the vehicle using RVE's government facilities, with the support of SSHINE.

4.5.1.10 It is anticipated that FALSESat will launch two (2) years from the award of TO 0005 FALSESat.

4.5.1.11 TO 0005 FALSESat is expected to have the following scope:

4.5.1.11.1 Transitioning current and future Mission and Space System Development work from TO 0001 RVEP.

4.5.1.11.2 Completing payload development and integration.

4.5.1.11.3 Completing vehicle assembly, integration and testing.

4.5.1.11.4 Conducting FALSESat launch and early operations.

4.5.1.11.5 An addition to the key personnel list: FALSESat Payload Lead Engineer.

4.5.2 Subfactor 4: The offeror will provide a technical approach narrative describing how they would respond to a notional program task order. This notional program reflects an anticipated requirement of SSHINE. It reflects a program already within the scope defined by the workload indicator table. The scenario is in character with how a requirement would transition from one of the three (3) initial task orders, and onto a specific program task order.

4.5.2.1 The task order concerns the notional development of the Requirement Verification Experimental Satellite (RVESat) and is titled TO 0006 RVESat.

4.5.2.2 The offeror was informed one (1) month after initial award of the basic contract and the three initial task orders that RVESat is an RVE flight experiment and will be moving to Systems Requirement Review within the first year of the award period.

4.5.2.3 Work leading up to RVESat's Preliminary Design Review is covered under the scope of TO 0001 RVEP.

4.5.2.4 A dedicated task order (TO 0006 RVESat) will be awarded eighteen (18) months after initial award of the basic contract and the three initial task orders.

4.5.2.5 RVESat has a government program management office in RVE, which includes a government Program Manager, Chief Engineer, and Lead Systems Engineer, and a Principal Investigator within another Space Vehicles Directorate Technical Division.

4.5.2.6 RVESat does not have an approved technical or programmatic baseline, but recently received approval on its architecture and acquisitions strategy, as identified by the following:

4.5.2.6.1 The architecture selected is to leverage an ESPA-Grande class satellite that was recently transferred to RVE from another US Government partner and is build-to-print of fully qualified space vehicle design. It is assembled but has not gone through an environmental testing campaign and has an empty payload bay.

4.5.2.6.2 RVE does not have existing expertise with this satellite bus but has a full data package and some reach back support from the government partner supplying it.

4.5.2.6.3 The RVESat mission payload is a first-of-a-kind sensor that has a completed designed developed by a University Affiliated Research Center and has been highly ranked by the Space Experimental Review Board and has an anticipated launch date of four (4) years after award.

4.5.2.6.4 The payload is expected to fill 50% of the available payload mass and volume. It has specific pointing requirements that require upgrades to the existing bus attitude determination and control subsystem to improve pointing knowledge and control to nearly an order of magnitude.

4.5.2.6.5 The payload is anticipated to produce a large amount of raw data (150 GB/day) and will have an on-board data processing architecture as part of the payload to test novel automation processing techniques to limit the downlink requirements for standard operations. These data processing techniques are government-furnished by another technical division of AFRL; however, they have not been implemented on the payload of spacecraft bus. The raw data will need to be passed to the data processing architecture during checkout of the payload, and processed data will need to be demonstrated as compatible with downlink requirements.

4.5.2.6.6 The mission orbit is expected to be a polar Low-Earth Orbit with a desire to leverage onboard propulsion to modify the orbit to a more elliptical orbit (progressively higher apogee) with a controlled re-entry at the end of a two-year lifetime.

4.5.2.7 Management of the UARC will be performed by the government outside of SSHINE, but SSHINE will be used to support mission development and system engineering activities in a base task order and transition to a dedicated task order (TO 0006) upon an approved PDR for the complete system design, spacecraft modifications, payload integration to bus, spacecraft environmental testing, ground system development, launch support, and flight operations.

4.5.2.8 TO 0006 RVESat is expected to have the following scope:

4.5.2.8.1 Transitioning work from TO 0001 RVEP to the program task order.

4.5.2.8.2 Performing System Engineering tasks throughout program lifecycle and supporting the government program manager and chief engineer.

4.5.2.8.3 Completing RVESat system design (CDR)

4.5.2.8.4 Modifying spacecraft as needed to meet mission requirements (ADCS modifications, payload integration challenges, and any other payload additions).

4.5.2.8.5 Receive and integrate UARC-delivered payload to spacecraft

4.5.2.8.6 Performing integrated system functional and environmental testing

4.5.2.8.7 Completing ground system development leveraging RVE-organic ground capabilities. RVE's existing ground system infrastructure is mature, and has flown spacecraft in prior efforts; however, the government expects further development, and upgrade will be necessary for a successful RVESat mission

4.5.2.8.8 Conducting/supporting RVESat launch and early operations.

4.5.2.8.9 An addition to the key personnel list: RVESat Lead Systems Engineer.

4.5.3 Subfactor 5: The offeror will provide a technical approach narrative describing how they would respond to a focused requirement to support Hardware in the Loop and Software In the Loop (HWIL/SWIL) experiment within the routine scope of TO 0003 (RVEX). This notional effort reflects an anticipated requirement of SSHINE support to RVEX with test engineers to setup, execute, and document test execution and experimentation events.

4.5.3.1 The offeror is informed three (3) months after award that five (5) different Satellite Communications (SATCOM) devices will be delivered to RVEX within the next five months, one device delivered per month.

4.5.3.1.1 The devices are of differing types, and vary in maturity, but only one (1) flight qualified hardware, with the remaining four (4) being functional prototypes.

4.5.3.1.2 The only device with a complete ICD is the flight qualified device.

4.5.3.1.3 Ground control commands for these devices are currently under development but not completed or tested.

4.5.3.1.4 The HWIL/SWIL testbed consists of multiple cross domain solutions for flowing data between different networks and classification levels, and one or more flatsats.

4.5.3.2 There is a major experimentation event nine (9) months after contract award with a minimum three (3) of the (5) devices needed to be successfully connected to the HWIL/SWIL testbed and functioning in order to demonstrate a successful experiment.

4.5.3.3 The RVEX team has a government test lead, and a government engineer, and is leveraging SSHINE TO 0003 expertise to build an integration plan, execute the SATCOM device integration into the existing HWIL/SWIL testbed.

4.6 Factor 3: Staffing Plan

4.6.1 Factor 3 requires the use of a spreadsheet. The spreadsheet should follow the format of the SSHINE_Staffing_Plan_Template.xlsx, included as Attachment 9 with the solicitation.

4.6.1.1 The spreadsheet does not count against the page totals for this portion of the technical volume.

4.6.2 Subfactor 6: The Offeror shall show the following using the Overview Matrix tab of the provided spreadsheet:

4.6.2.1 As many labor categories, including corresponding minimum qualifications, as determined necessary to meet all potential tasks called for under this contract.

4.6.2.1.1 Labor categories and qualifications shall be standardized between the offeror and any subcontractors.

4.6.2.2 Full description of key responsibilities to be performed by each labor category.

4.6.2.2.1 References should be made to specific entries in the basic or TO SOWs. References to high level entries in the SOWs will be considered inclusive of all sub-entries, unless specifically exempted by the offeror.

4.6.3 Subfactor 7: The Offeror shall provide the following in the TO 0001 RVEP tab of the spreadsheet:

4.6.3.1 The proposed workforce composition, including labor category and number of hours to meet each TO 0001 RVEP requirement;

including subcontractors, if applicable.

4.6.3.2 Full description of how each requirement of TO 0001 RVEP is met by the staffing plan.

4.6.4 Subfactor 8: The Offeror shall provide the following in the TO 0002 RVEN tab of the spreadsheet:

4.6.4.1 The proposed workforce composition, including labor category and number of hours to meet each TO 0002 RVEN requirement; including subcontractors, if applicable.

4.6.4.2 Full description of how each requirement of TO 0002 RVEN is met by the staffing plan.

4.6.5 Subfactor 9: The Offeror shall provide the following in the TO 0003 RVEX tab of the spreadsheet:

4.6.5.1 The proposed workforce composition, including labor category and number of hours to meet each TO 0003 RVEX requirement; including subcontractors, if applicable.

4.6.5.2 Full description of how each requirement of TO 0003 RVEX is met by the staffing plan.

4.6.6 Subfactor 10: The Offeror shall provide the following in the Cross Utilization Matrix tab of the spreadsheet:

4.6.6.1 A complete listing of any and all personnel that will support multiple task orders, including the relevant labor categories and split of their hours between task orders.

5.0 Volume III - Cost/Price

5.1 This section is to assist the Offeror in submitting data other than certified cost or pricing data that is required to evaluate the completeness, balance, reasonableness and cost realism of the proposed cost/price.

5.1.1 Compliance with these requirements is mandatory and failure to comply may result in rejection of Offeror's proposal.

5.1.2 Unrealistically low or unreasonably high proposed prices, initially or subsequently, may be grounds for eliminating a proposal from competition either on the basis that the Offeror does not understand the requirement or has submitted an unreasonable or unrealistic proposal.

5.1.3 Offers should be sufficiently detailed to demonstrate completeness, balance, reasonableness and cost realism.

5.1.4 The burden of proof for credibility of proposed costs/prices rests with the Offeror.

5.1.5 The Contracting Officer has determined there is a high probability of adequate price competition in this acquisition. Upon examination of the initial offers, the Contracting Officer will review this determination and if, in the Contracting Officer's opinion, adequate price competition exists, no additional data will be requested and certification under FAR 15.406-2 will not be required. However, if at any time during this competition the Contracting Officer determines that adequate price competition no longer exists, Offerors may be required to submit additional cost or pricing data for the Contracting Officer to determine if the price is fair and reasonable.

5.1.6 Data beyond that required by this instruction shall not be submitted, unless it is considered essential to document or substantiate completeness, balance, reasonableness and cost realism of the proposal. Under no circumstances shall Cost/Price data and documentation be included elsewhere in the proposal.

5.2 Offeror shall prepare and submit the cost/price proposal in Microsoft (MS) Office Word and MS Office 365 Excel compatible format. Files received in any other format or solely in MS Word 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. The electronic spreadsheet files (workbooks) shall include all formulas, functions, computations, or equations used to compute the proposed amounts in the Offerors own format. Electronic links are only permissible within the Cost/Price Volume. If files contain links, the links must be intact and maintained through all revisions. The Offeror shall not include in the Excel spreadsheets pivot tables or macros and shall not include cell references to data or files which are not included in the Cost/Price Volume. For each workbook, all rows, columns, cells, and worksheets are to be visible. Offerors shall not include zero height/zero width rows/columns in worksheets. Excel sheets may not have any hidden formulas or have access / visibility protected or hidden in any manner.

5.2.1 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 discouraged unless it is clearly referenced to a corresponding MS Excel file, or its derivation is unambiguous. The Offeror is responsible for ensuring 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.

5.3 Cost/ Price Data. When responding to the Cost/Price Volume requirements in the Request for Proposal (RFP), the Offeror and associated subcontractors/ interdivisional transfers (IDT)/ consultants (hereby referred to collectively as subcontractors) may use any generally accepted estimating techniques to develop estimates.

5.3.1 In accordance with FAR15.403-1(b) and 15.403-3(a), data other than certified cost or pricing data may be required to support a determination of completeness, balance, price reasonableness and cost realism. Data shall be provided in accordance with FAR 15.403- 5.

5.3.2 If, after receipt of proposals, the CO determines that there is insufficient data available to determine completeness, balance, price reasonableness or costs realism and none of the exceptions in FAR 15.403-1apply, the offeror shall be required to submit additional cost or pricing data in accordance with FAR 15.403-3 or FAR 15.403-4, respectively.

5.4 Rounding. All dollar amounts provided shall be rounded to the nearest dollar. All labor rates shall be rounded to the nearest penny.

5.5 Volume Organization. The Cost/Price volume will be organized according to the following outline:

5.5.1 Table of Contents

5.5.2 Summary page with the following information:

5.5.2.1 Solicitation number and applicable Task Order number

5.5.2.2 Name and address of Offeror

5.5.2.3 Name and telephone number of point of contact

5.5.2.4 Name, address and telephone number of the Cognizant DCMA and DCAA offices

5.5.2.5 Date of submission and expiration date of offer

5.5.2.6 Name, title, and signature of authorized representative

5.5.2.7 UEI number

5.5.2.8 Cage Code

5.5.2.9 Total Proposed Cost/Price

• Task Order 0001 Total Cost/Price

• Task Order 0002 Total Cost/ Price

• Task Order 0003 Total Cost/ Price

• Combined Total Cost/Price Task Orders 0001, 0002, and 0003

5.6 Estimating System. Offeror shall provide a summary description of its standard estimating system or methods (e.g., Engineering Labor, Manufacturing Labor, Indirect Costs, Other Direct Costs, Overhead, General & Administrative (G&A)). The summary description shall cover separately each major cost element. Identify any deviations from Offeror's standard estimating procedures in preparing this proposal volume. Fully explain any deviations from Offeror's established business practices. Indicate whether Offeror has Government approval of its estimating system and if so, provide evidence of such approval.

5.7 Purchasing System. Offeror shall provide a summary description of its 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 Offeror's standard procedures in preparing this proposal. Fully explain any deviations from Offeror's established business practices.

Indicate whether Offeror have Government approval of its purchasing system and if so, provide evidence of such approval.

5.8 Accounting System. Identify any deviations from Offeror's standard procedures in preparing this proposal. Fully explain any deviations from Offeror's established business practices.

5.9 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 cost-sharing arrangements and prime-subcontractor relationships.

5.9.1 Provide complete rationale for any exceptions taken to Section L, para 5.0 Cost/Price.

5.9.2 Task Order Pricing

5.9.3 Acknowledgement of Baselined Costs by Task Order

5.10 Task Order Pricing Instructions

5.10.1 For each Task Order (Task order 0001,0002, and 0003), submit a list of proposed probable subcontractors showing:

5.10.1.1 The supplier

5.10.1.2 Description of effort

5.10.1.3 Type of contract

5.10.1.4 Price proposed by each

5.10.1.5 Price included in prime's proposal to the Government

5.10.1.6 Degree of competition (include competitive pricing, if competed)

5.10.1.7 Percentage of effort

5.10.1.8 Commercial item/service determination support, if applicable.

5.10.2 In accordance with FAR 15.404-3, submit detailed results of cost or price analysis for each proposed subcontractor.

5.10.3 Submit the information required by FAR 52.215-22, Limitations on Pass-Through Charges --Identification of Subcontract Effort if subcontract effort exceeds 70% of the total cost of work to be performed by the prime under applicable task order. Given that this is an R&D effort, if a T&M subcontract is proposed, explain how such a contract benefits the Government.

5.10.4 IAW FAR 15.403-5(b)(2), the Contracting Officer has determined the use of a specific format is not required for the submission of data other than certified cost or pricing data. Therefore, Offerors may submit data other than certified cost or pricing data in their own unique format to support the proposed cost and fee associated with each Task Order.

5.10.4.1 Although not required for data other than certified cost or pricing data, the Government recommends Offerors utilize Table 15-2 -- Instructions for Submitting Cost/Price Proposals When Certified Cost or Pricing Data Are Required, located at FAR 15.408 and the Proposal Adequacy Checklist located at DFARS 252.215-7009 in the development of each Task Order cost proposal. In the event certified cost or pricing data becomes required, the Offeror shall conform to the Proposal Adequacy Checklist.

5.10.5 Cost Summery by Cost Elements (For Each Task Order)

5.10.5.1 Total Task Order Summary. Provide a cost summary of Labor…