Attachment_8_-_Draft_RISE_Section_L__26_Mar_18.pdf

Source Selection Sensitive – See FAR 2.101 and 3.104

R&D INTEGRATED SPACE EXPERIMENTS (RISE) CONTRACT

FA9453-18-R-0003, ATTACHMENT 7

SECTION L, INSTRUCTIONS, CONDITIONS, AND NOTICES TO

OFFERORS

26 MARCH 2018

L-I - SOLICITATION PROVISIONS INCORPORATED BY REFERENCE

NOTICE: Pursuant to FAR 52.252-1, "SOLICITATION PROVISIONS INCORPORATED BY REFERENCE," the following provisions are incorporated herein by reference:

A. FEDERAL ACQUISITION REGULATION (48 CFR CHAPTER 1) SOLICITATION

PROVISIONS:

REFERENCE TITLE DATE

52.204-7 SYSTEM FOR AWARD MANAGEMENT OCT 2016

52.204-18 COMMERCIAL AND GOVERNMENT ENTITY CODE

MAINTENANCE

JUL 2016

52.215-1 INSTRUCTIONS TO OFFERORS – COMPETITIVE JAN 2017

52.215-16 FACILITIES CAPITAL COST OF MONEY JUN 2003

52.215-20 REQUIREMENTS FOR CERTIFIED COST OR PRICING

DATA AND DATA OTHER THAN CERTIFIED COST

OR PRICING DATA

OCT 2010

52.215-22 LIMITATIONS ON PASS-THROUGH CHARGES –

IDENTIFICATION OF SUBCONTRACT EFFORT

OCT 2009

52.215-23 LIMITATIONS ON PASS-THROUGH CHARGES OCT 2009

52.222-24 PRE-AWARD ON-SITE EQUAL OPPORTUNITY

COMPLIANCE EVALUATION

FEB 1999

52.232-38 SUBMISSION OF ELECTRONIC FUNDS TRANSFER

INFORMATION WITH OFFER

JUL 2013

B. DEPARTMENT OF DEFENSE FEDERAL ACQUISITION REGULATION

SUPPLEMENT (48 CFR CHAPTER 2) SOLICITATION PROVISIONS:

file://periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR52.246.doc#b522521

REFERENCE TITLE

DATE

252.203-7005 REPRESENTATION RELATING TO COMPENSATION

OF FORMER DOD OFFICIALS

OCT 2016

252.204-7004 ALTERNATE A, SYSTEM FOR AWARD

MANAGEMENT

FEB 2014

252.204-7007 ALTERNATE A, ANNUAL REPRESENTATIONS AND

CERTIFICATIONS

JAN 2015

252.204-7008 COMPLIANCE WITH SAFEGUARDING COVERED

DEFENSE INFORMATION CONTROLS

OCT 2016

252.215-7008 ONLY ONE OFFER OCT 2013

252.219-7000 ADVANCING SMALL BUSINESS GROWTH SEP 2016

252.227-7028 TECHNICAL DATA OR COMPUTER SOFTWARE

PREVIOUSLY DELIVERED TO THE GOVERNMENT

JUN 1995

L-II - SOLICITATION PROVISIONS IN FULL TEXT

NOTICE: The following provisions are hereby incorporated in full text:

A. FEDERAL ACQUISITION REGULATION (48 CFR CHAPTER 1) SOLICITATION

PROVISIONS:

52.211-2 - Availability of Specifications, Standards, and Data Item Descriptions Listed in the Acquisition Streamlining and Standardization Information System (ASSIST) (Apr 2014)

(a) Most unclassified Defense specifications and standards may be downloaded from the following ASSIST websites:

(1) ASSIST (https://assist.dla.mil/online/start/ );

(2) Quick Search (http://quicksearch.dla.mil/ );

(3) ASSISTdocs.com (http://assistdocs.com).

(b) Documents not available from ASSIST may be ordered from the Department of Defense Single Stock Point (DoDSSP) by—

(1) Using the ASSIST Shopping Wizard (https://assist.dla.mil/wizard/index.cfm );

(2) Phoning the DoDSSP Customer Service Desk (215) 697-2197, Mon-Fri, 0730 to 1600 EST; or

(3) Ordering from DoDSSP, Building 4, Section D, 700 Robbins Avenue, Philadelphia, PA 19111-5094, Telephone (215) 697-2667/2179, Facsimile (215) 697-1462.

52.211-14 - Notice of Priority Rating for National Defense, Emergency Preparedness, and Energy Program Use (Apr 2008)

Any contract awarded as a result of this solicitation will be [ ] DX rated order; [X] DO rated order certified for national defense, emergency preparedness, and energy program use under the Defense Priorities and Allocations System (DPAS) (15 CFR 700), and the Contractor will be required to follow all of the requirements of this regulation.

52.216-1 - Type of Contract (Apr 1984)

The Government contemplates award of a single award Indefinite Delivery Indefinite Quantity (IDIQ) contract with Cost-Plus-Fixed-Fee (CPFF) completion task orders resulting from this solicitation.

52.233-2 - Service of Protest (Sep 2006)

(a) Protests, as defined in section 33.101 of the Federal Acquisition Regulation, that are filed directly with an agency, and copies of any protests that are filed with the Government Accountability Office (GAO), shall be served on the Contracting Officer (addressed as follows) by obtaining written and dated acknowledgment of receipt from:

Air Force Research Laboratory, AFRL/RVKVI, Contracting Officer 2251 Maxwell Avenue, Bldg 424 Kirtland AFB, NM 87117-5773 https://assist.dla.mil/online/start/ http://quicksearch.dla.mil/ http://assistdocs.com/ https://assist.dla.mil/wizard/index.cfm

(b) The copy of any protest shall be received in the office designated above within one day of filing a protest with the GAO.

52.252-1 - Solicitation Provisions Incorporated by Reference (Feb 1998)

This solicitation incorporates one or more solicitation provisions by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. The offeror is cautioned that the listed provisions may include blocks that must be completed by the offeror and submitted with its quotation or offer. In lieu of submitting the full text of those provisions, the offeror may identify the provision by paragraph identifier and provide the appropriate information with its quotation or offer. Also, the full text of a solicitation provision may be accessed electronically at this/these address(es):

http://farsite.hill.af.mil/ OR https://www.acquisition.gov/browsefar

B. DEPARTMENT OF DEFENSE FEDERAL ACQUISITION REGULATION

SUPPLEMENT (48 CFR CHAPTER 2) SOLICITATION PROVISIONS:

252.227-7017 – IDENTIFICATION AND ASSERTION OF USE, RELEASE, OR

DISCLOSURE RESTRICTIONS (JAN 2011)

(a) The terms used in this provision are defined in following clause or clauses contained in this solicitation—

(1) If a successful offeror will be required to deliver technical data, the Rights in Technical Data--Noncommercial Items clause, or, if this solicitation contemplates a contract under the Small Business Innovation Research Program, the Rights in Noncommercial Technical Data and Computer Software--Small Business Innovation Research (SBIR) Program clause.

(2) If a successful offeror will not be required to deliver technical data, the Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation clause, or, if this solicitation contemplates a contract under the Small Business Innovation Research Program, the Rights in Noncommercial Technical Data and Computer Software--Small Business Innovation Research (SBIR) Program clause.

(b) The identification and assertion requirements in this provision apply only to technical data, including computer software documentation, or computer software to be delivered with other than unlimited rights. For contracts to be awarded under the Small http://farsite.hill.af.mil/ https://www.acquisition.gov/browsefar

Business Innovation Research Program, the notification and identification requirements do not apply to technical data or computer software that will be generated under the resulting contract. Notification and identification is not required for restrictions based solely on copyright.

(c) Offers submitted in response to this solicitation shall identify, to the extent known at the time an offer is submitted to the Government, the technical data or computer software that the Offeror, its subcontractors or suppliers, or potential subcontractors or suppliers, assert should be furnished to the Government with restrictions on use, release, or disclosure.

(d) The Offeror's assertions, including the assertions of its subcontractors or suppliers or potential subcontractors or suppliers, shall be submitted as an attachment to its offer in the following format, dated and signed by an official authorized to contractually obligate the Offeror:

Identification and Assertion of Restrictions on the Government's Use, Release, or Disclosure of Technical Data or Computer Software.

The Offeror asserts for itself, or the persons identified below, that the Government's rights to use, release, or disclose the following technical data or computer software should be restricted:

Technical Data or Computer Software Name of Person to be Furnished Basis for Asserted Rights Asserting With Restrictions* Assertion** Category*** Restrictions****

(LIST)***** (LIST) (LIST) (LIST)

*For technical data (other than computer software documentation) pertaining to items, components, or processes developed at private expense, identify both the deliverable technical data and each such item, component, or process. For computer software or computer software documentation identify the software or documentation.

**Generally, development at private expense, either exclusively or partially, is the only basis for asserting restrictions. For technical data, other than computer software documentation, development refers to development of the item, component, or process to which the data pertain. The Government's rights in computer software documentation generally may not be restricted. For computer software, development refers to the software. Indicate whether development was accomplished exclusively or partially at private expense. If development was not accomplished at private expense, or for computer software documentation, enter the specific basis for asserting restrictions.

***Enter asserted rights category (e.g., government purpose license rights from a prior contract, rights in SBIR data generated under another contract, limited, restricted, or government purpose rights under this or a prior contract, or specially negotiated licenses).

****Corporation, individual, or other person, as appropriate.

*****Enter “none” when all data or software will be submitted without restrictions.

Date _________________________________ Printed Name and Title _________________________________ Signature _________________________________

C. AIR FORCE FEDERAL ACQUISITION REGULATION SUPPLEMENT

SOLICITATION PROVISIONS:

5352.209-9001 POTENTIAL ORGANIZATIONAL CONFLICT OF INTEREST (OCT

2010) – ALTERNATE I (OCT 2010)

(a) There is potential organizational conflict of interest (see FAR Subpart 9.5, Organizational and Consultant Conflicts of Interest) due to the performance of systems engineering activities and the possibility of the successful contractor gaining access to proprietary information of other companies during contract performance. The restrictions of this clause apply to all subcontracts, teaming arrangements, and other arrangements. Accordingly:

(1) Restrictions are needed to ensure that the offeror is not provided an unfair competitive advantage over other sources by performance of systems engineering activities or by access to proprietary information. To combat an unfair advantage due to performance of systems engineering activities, the offeror shall ensure objective, impartial, and independent judgment and recommendations, and shall ensure the requirements of the Organizational Conflict of Interest clause are included in all subcontracts, teaming arrangements and other arrangements.

To combat an unfair advantage due to access to proprietary information, the offeror agrees to enter into Associate Contractor Agreements to: (1) protect another company's information from unauthorized use or disclosure for as long as it is considered proprietary by the other company;

and, (2) to refrain from using the information for any purpose other than that for which it was furnished. These restrictions are for the life of the contract.

(2) As a part of the proposal, the offeror shall provide the Contracting Officer with complete information of previous or ongoing work that is in any way associated with the contemplated acquisition.

(b) If award is made to the offeror, the resulting contract may include an Organizational Conflict of Interest limitation applicable to subsequent Government work, at either a prime contract level, at any subcontract tier, or both. During evaluation of proposals, the Government may, after discussions with the offeror and consideration of ways to avoid the conflict of interest, insert a special provision in the resulting contract which shall disqualify the offeror from further consideration for award of future contracts.

(c) The organizational conflict of interest clause included in this solicitation may not be modified or deleted during negotiations.

L-III - INFORMATION TO OFFERORS (ITO) AND INSTRUCTIONS FOR

PROPOSAL PREPARATION

1.0 Program Structure and Objectives

The RISE contract will support the Air Force’s Space Superiority Service Core mission requirements and Space Enterprise Vision growth areas by providing concept design, development, integration, test and evaluation of new space technologies, innovative, engineering prototypes, and new employment concepts. The Air Force Research Laboratory's Space Vehicles Directorate, Integrated Experiments and Evaluation Division (AFRL/RVE, henceforth ‘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.

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/RV mission.

The contractor shall perform work in the following functional areas: integrated ground experiments, ground support equipment, spacecraft, high-altitude balloon flights, launch vehicles (e.g., orbital and suborbital rockets, space plane, International Space Station (ISS) deployments), platform and subsystem/component design, software design and development, analyses throughout the research and development system engineering process, design optimization and review, testing and evaluation, deployment of experimental assets, and transition phases. Concurrent with these functional areas, technical work is also required in the areas of information systems, information assurance and communications security (COMSEC) engineering in order to fully integrate and execute spacecraft, ground, or high altitude balloon experiment integration, test, and mission development.

Table 1 provides an anticipated number of flight experiments the RISE contract will execute over the five (5) year effort. This information is for proposal purposes only to give offerors a reference of the number and complexity of the experiments to be performed.

Table 1 - Anticipated Number of Flight Experiments FY19-FY24

Mission Assurance Class

Concept Development

Implementation AI&T through Tech Transfer

1 30 20 10 2 20 10 5 3 10 5 3

As depicted in the table above, not all programs and concepts will proceed through on-orbit experimentation.

1.1 Budget/Funding Information

The Government intends to award a single award IDIQ contract with a ceiling of $340M.

Budget estimates by fiscal year are estimated as follows:

FY19 - $25.9M; FY20 - $48.1M; FY21 - $51.8M; FY22 - $52.2M; FY23 - $49.0M; FY24 -

$46.6M; FY25 - $44.5M; FY26 - $21.9M

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.

Funding for RISE Task Orders is subject to Government fiscal year budgetary constraints and priorities. Due to volatile, uncertain and complex budgetary constraints at the Air Force level and possible impact to the RISE 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.2 Contract Historical Background

The work performed under the current contract has historically consisted of supporting fifteen concurrent task orders. During the most recent performance year under the current contract, the Government issued two new task orders with an average period of performance of twenty-four months. RISE requirements may include having to provide surge capability to meet unusually heavy workload demands caused by short-notice, high-priority projects. The current contract is a small business set-aside, and this acquisition is also planned to be a one hundred percent small business set-aside.

1.3 General Instructions

a. 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 shall result in an unfavorable proposal evaluation. The Offeror shall clearly state in its contract documentation volume that the proposal is valid for 180 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.

b. 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 facilities and experience and will base its evaluation on the information presented in the Offeror's proposal. Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired.

c. In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals. Unless the Offeror requests otherwise, the Government will destroy extra copies of such unsuccessful proposals.

d. Offerors shall assume that all work identified in the Task Order SOWs is to be performed concurrently.

e. 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 cost data to the extent necessary for the Contracting Officer to determine if the price is fair and reasonable.

file://periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/Content.Outlook/far/FAR15.DOC#b154062

2.1 General Information

2.1.1 Point of Contact

The Contracting Officer (CO) is the sole point of contact for this acquisition. Address any questions or concerns you may have about this solicitation to the CO. Written requests for clarification may be sent to the CO, Susan Heilman, at susan.heilman.1@us.af.mil.

2.1.2 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.1.3 Discrepancies

If an Offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the Offeror shall notify the CO in writing within ten (10) calendar days of issuance of the solicitation with supporting rationale, as well as the remedies the Offeror is asking the CO to consider as related to the omission or error. The Offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion.

2.1.4 Electronic Reference Documents

All referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) website at http://www.fedbizopps.gov. Offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

2.1.5 Oral Presentations

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

2.1.6 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 mailto:susan.heilman.1@us.af.mil http://www.fedbizopps.gov/

Selection Information – See FAR 2.101 & 3.104” in the Subject line. The Government will use the AMRDEC S.A.F.E. (https://safe.amrdedc.army.mil/SAFE2/) and/or AFRL Encryption Wizard (http://www.spi.dod.mil/ewizard.htm) tools to transmit/receive source selection information.

2.1.7 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. The Offeror shall provide the three (3) key personnel identified in the basic SOW as TS/SCI eligible on day one of contract award. All other personnel will be required to have security clearances as identified in the DD254. For proposal purposes, use the following estimate for planning purposes: [PLEASE

CONTACT CONTRACTING FOR BILLETING INFORMATION]

2.1.8 Contract Limitations

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

- TO 0001: Tactical Command, Control, and Communications (C3)

- TO 0002: Position Navigation and Timing (PN&T)

- TO 0003: Small Satellite Portfolio (SSP)

2.2 Organization/Number of Copies/Page Limits

The Offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 2.2.a below). The titles and contents of the volumes shall be as defined in this table, all of which shall be within the stated page limits and with the number of copies as specified in Table 2.2.a. The proposal volumes identified in the table shall be separately bound in three-ring, loose-leaf binders, as necessary. The contents of each proposal volume are described in the ITO paragraph as noted in the table below:

Table 2.2.a

VOLUME VOLUME

TITLE

ITO

Para

COPIES REQUIRED PAGE LIMIT DUE DATE/TIME

I Executive Summary

3.0 Original + 3 + CD-R, DVD-R

3 pages XX Jun 2018 12:00p.m. (noon) MDT

II Technical 4.0 Original + 3 + CD-R, DVD-R

100 pages XX Jun 2018 12:00p.m. (noon) MDT

III Cost/Price 5.0 Original + 3 + CD-R, DVD-R

Unlimited XX Jun 2018 12:00p.m. (noon) MDT

IV Contract Documentation

6.0 Original + 3 + CD-R, DVD-R

Unlimited XX Jun 2018 12:00p.m. (noon) MDT

V Compliance Documentation

7.0 Original + 3 + CD-R, DVD-R

Unlimited XX Jun 2018 12:00p.m. (noon) MDT

2.2.1 Page Limitations, 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, and excess paper copies will be returned to the Offeror as soon as practical. 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. The following will not be counted towards total page count limitations: cover pages, tables of contents, separator tabs, glossaries, acronym lists, list of figures, and resumes.

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 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 ¾-inch side margins. Pages shall be numbered sequentially by volume. These page size and format restrictions shall apply to responses to ENs.

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 shall count as two pages for each side; double sided shall count as four 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. These restrictions apply to both hardcopy and softcopy proposals as well as responses to ENs. Provide Microsoft Office Excel formulas in all spreadsheets.

2.2.2 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 trade-off 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.2.3 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.2.4 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.

2.2.5 Glossary of Abbreviations and Acronyms

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.

2.2.6 List of Tables and Drawings

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.2.7 Binding and Labeling

Each proposal volume shall be separately bound in a three-ring, loose leaf binder permitting the volume to lie flat when open. Staples shall not be used. A cover sheet shall be bound in each book, clearly marked as to volume number, title, copy number, solicitation identification, and the Offeror's name. The same identifying data shall be placed on the spine of each binder. All unclassified document binders shall have a color other than red or other applicable security designation colors. 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.2.8 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.

2.3 Electronic Offers and Digital Media Copies

Offerors shall not submit proposals by electronic-mail (email) or facsimile. Proposals shall be mailed or hand-carried and must be received at the address in Paragraph 2.4 by the time and date specified in this RFP. If hand carried, contact the Government personnel identified in paragraph 2.4, Distribution, below, to coordinate delivery. Offerors are cautioned that Kirtland AFB has visitor control procedures, which require individuals not affiliated with the installation to obtain a visitor pass prior to entrance. SOME DELAY SHOULD BE ANTICIPATED WHEN HAND-CARRYING PROPOSALS. Offerors are strongly encouraged to plan ahead regarding the time it may take to hand deliver a proposal. Kirtland AFB is a relatively large installation. Allow sufficient time to obtain a visitor pass and locate the building PRIOR to the response date and time specified in the RFP. A map or detailed instructions will be provided upon request. Proposals received after the date and time specified shall be treated in accordance with FAR 52.215-1. Ensure proposals are properly marked “For Official Use Only” and “Source Selection Information – See FAR 2.101 and FAR 3.104.”

The content and page size of electronic copies must be identical to the hard copies. For electronic copies, indicate on each CD-R, DVD-R the volume number and title. Use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any. The Offeror shall submit proposal volumes I through V in electronic format, using recordable compact disks (CD-R, DVD-R). Each volume shall be in a different directory on a CD-R, DVD-R. If files are compressed, the necessary decompression program must be included. The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Office Suite 2013, and Adobe Acrobat (searchable), as applicable. In the event that there are any discrepancies between the hard copies and the electronic copies of the proposal, the hard copies will be used for evaluation.

2.4 Distribution

For each proposal submitted, the "original" proposal shall be identified. Proposals shall be marked "For Official Use Only" and "Source Selection Information (See FAR 2.101 and FAR 3.104”), addressed to the CO as shown below, and mailed or hand-carried to the AFRL mailroom located at 3550 Aberdeen Ave SE, Kirtland AFB, NM 87117-5776.

DET 8 AFRL/RVKVI, Building 592 ATTN: Susan Heilman and John Griego

TO BE OPENED BY ADDRESSEE ONLY

Volume I - Executive Summary

In the Executive Summary, the Offeror shall provide the following information:

3.0 Executive Summary

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 Table of Contents

Include a master Table of Contents of the entire proposal. This will not be counted towards page count limitations.

3.2 Cross-Reference Matrix

The Offeror shall submit a Cross Reference Matrix using the format provided in Section L, Attachment 1, indicating the proposal reference information as it relates to the ITO, 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.

Volume II - Technical Volume

4.0 General

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.1 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. Basic Statement of Work Narrative

• Subfactor 1: Corporate Management

• Subfactor 2: Overarching Technical Approach

4. Task Orders Statement of Work Narrative (One per Task Order):

• Subfactor 3: Technical Approach for Tactical Command, Control, and

Communications (C3)

• Subfactor 4: Technical Approach for Position Navigation & Timing (PNT)

• Subfactor 5: Technical Approach for Small Satellites

5. Resumes for Key Personnel

6. Glossary

4.2 Page Limits, Format, and Specific Content

The Technical Volume shall not exceed one hundred (100) pages total.

Cover pages, tables of contents, separator tabs, glossaries, acronym lists, list of figures, and resumes for Key Personnel shall not be counted against prescribed page limits. Please submit an original, three (3) copies, and two (2) electronic copies via CD-R or DVD-R. The Offeror shall address its proposed approach to meeting the requirements of each factor and subfactor.

ITO

Para

Ref

SUBFACTOR/ITEM DESCRIPTION MAXIMUM PAGE LIMIT

4.5 Subfactor 1: Corporate

Approach and Staffing Effectiveness (Basic SOW)

Narrative Personnel and Staffing Plan

10 pages

4.5 Subfactor 1: Corporate

Approach and Staffing Effectiveness (Basic SOW)

Resumes of Key Personnel

Not Applicable (no page limitation)

4.6 Subfactor 2: Overarching

Technical Approach (Basic SOW)

Narrative 20 pages

4.7 Subfactor 3: Technical

Approach to Tactical Command, Control, and Communications (Task Order 0001)

Narrative 15 pages

4.8 Subfactor 4: Technical

Approach to Position Navigation and Timing (Task Order 0002)

Narrative 15 pages

4.9 Subfactor 5: Technical

Approach to Small Satellites (Task Order 0003)

Narrative 15 pages

4.4 All Subfactors (1, 2, 3, 4, and 5)

Corroborating Documentation

25 pages total

4.3 Technical Volume Definitions

Cradle-to-Grave/Life Cycle: The term “Cradle-to-Grave” as used in this contract refers to a systems engineering process that starts with requirements and mission analyses, goes through design, build, and test, shipping; then through on-orbit experiment operations, transition, transition support and data acquisition; and post-experiment analyses to produce the final technical R&D report that captures the scientific and technical knowledge gained from the mission. The term “Life Cycle” is synonymous with Cradle-to-Grave.

The cradle-to-grave processes and functions include scientific, technical and systems engineering activities associated with integrated space experiments from the initial concept development stage through the technology transition phase. This includes, but is not limited to, developing and refining requirements, conducting concept design, engineering analyses, trades, and modeling/simulation, and supporting systems engineering reviews (from Alternative Systems Reviews and Preliminary Design Reviews through Critical Design Reviews and System Verification Reviews), with particular emphasis on systems-level integration.

Small Satellites: For the purpose of this contract, RVE defines small satellites as an effort captured by Class 1 and Class 2 missions. This effort reflects space experiments with masses less than 50kg; however, Class 3 missions may overlap into this mass-class as well. (Class 1, 2, and 3 descriptions are defined in the Basic SOW).

Mission assurance/risk classes: This refers to the mission risk classification guidelines generally accepted and used for acquisitions in the National Security Space (NSS), Department of Defense (DoD), and NASA communities.

Scaled Mission Assurance: The ability to tailor practices and processes against various risk acceptances positions. This includes the historic model in the Basic SOW section 2.1.3, figure 2, as well as the evolving “new space” mission assurance paradigm.

New Space: New Space as defined in this RFP reflects the approach embodied by emerging commercial markets characterized by risk tolerance and the ability to trade requirements against constraints such as cost and schedule.

Complexity of experiments: The wide diversity of spacecraft configurations and/or science and military missions in flight experiment programs can range from single-mission nano/cubesats to multi-satellite, multi-payload, or multi-mission applications on an Evolved Expendable Launch Vehicle Secondary Payload Adapter (ESPA) or similar class of spacecraft (to include, but not be limited to ground systems and test beds).

4.4 Technical Factor Instructions

The Technical Proposal Volume shall consist of individual narrative for the Basic Statement of Work (SOW) and for each of the Task Order SOWs identified below. The Task Order SOWs represent actual work to be performed.

-TO 0001: Tactical Command, Control, and Communications (C3) -TO 0002: Positioning Navigation and Timing (PNT)

-TO 0003: Small Satellite Portfolio (SSP)

In addition to the narratives, the Offeror shall substantiate any experience referenced in the technical proposal by providing corroborating documentation. The documentation shall be provided in accordance with the Government-requested format in paragraph 2.2.1 above.

Examples of corroborating documentation are listed below, and can be tailored to address the specific approach captured in the proposal:

• Test Plans/Procedures

• Systems Engineering Management Plan and/or Processes

• Relevant sections of technical reports

• Abstracts of articles and with relevant citation, if available

The provided corroborating documentation shall not exceed a combined page count of twenty-five (25) pages, and must be cross-referenced within the proposal.

4.5 Subfactor 1: Corporate Management

The Offeror shall provide a narrative that describes an overarching corporate management approach. This narrative shall describe:

• How the Offeror plans to manage the full scope of the contract performance (including cost, schedule, and technical performance) including effective utilization of proposed subcontractors and/or teaming partners throughout contract performance

• How the Offeror will recruit, retain, and equip the necessary personnel to ensure performance of contract requirements from contract award through transition and throughout the period of performance. This includes providing a transition plan as part of the narrative (Basic SOW 5.2.3)

• The Offeror’s corporate organizational structure (to include teaming partners, as applicable)

• The Offeror’s approach for adjusting personnel to meet scaled surge requirements and changes in Government priorities across multiple, concurrent Task Orders

Additionally, the Offeror shall provide resumes for Key Personnel in accordance with the basic SOW section 5.2.2.

4.6 Subfactor 2: Overarching Technical Approach

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

• Meets the requirements as specified in section 4.0 of the Basic SOW

• Demonstrates the Offeror’s experience in applying cradle-to-grave engineering processes, utilizing documented, and proven systems engineering standards and practices

• Demonstrates how the Offeror plans to tailor engineering processes to accommodate missions of different risk classes and complexity

4.7 Subfactor 3: Technical Approach for Tactical Command, Control, and Communications (C3)

The Offeror shall provide a narrative description of their technical approach to the requirements outlined in the Task Order 0001 SOW which may be augmented by diagrams, flow charts, drawings, pictures, etc. The narrative description shall include the Offeror’s experience in analyzing, integrating, and testing Tactical Data Links (TDL) and networking architectures.

The Task Order 0001 SOW specifies the execution through Critical Design Review (CDR);

however, the Offeror’s narrative shall address the full life cycle, from concept design through tech transfer.

Information provided in the narratives of subfactor 1 and 2 will also be used to evaluate the offeror’s technical approach to the requirements detailed in Task Order 0001.

4.8 Subfactor 4: Technical Approach for Position Navigation and Timing (PNT)

The Offeror shall provide a narrative description of their technical approach to address the requirements outlined in the Task Order 0002 SOW which may be augmented by diagrams, flow charts, drawings, pictures, etc. The narrative description shall include the Offeror’s experience in implementing PNT advanced signal in: design, generation, broadcast, propagation and exploitation for a closed-loop, satellite navigation control systems and in analyzing, integrating and testing PNT payloads.

Information provided in the narratives of subfactor 1 and 2 will also be used to evaluate the offeror’s technical approach to the requirements detailed in Task Order 0002.

4.9 Subfactor 5: Technical Approach for Small Satellites

The Offeror shall provide a narrative description of their technical approach to address the requirements outlined in the Task Order 0003 SOW, utilizing the examples of Class 1 and Class 2 missions identified below as a guide. The narrative may be augmented by diagrams, flow charts, drawings, pictures, etc. The narrative shall include the Offeror’s approach to the full developmental life cycle (mission design, implementation, AI&T, on orbit operations, and technology transfer).

Class 1 Example:

A representative example of a Class 1 mission would be a highly cost and schedule constrained effort. The Globalstar Experiment and Risk Reduction (GEARRS) satellite is an example of this type of effort. In the GEARRS program, AFRL was notified of an empty launch slot with delivery in just over three (3) months. The Government and contractor team rapidly assessed payloads available, mission objectives, maturity of hardware, and staff available to scope and execute the program. Although this represents probably the extreme of this class, it demonstrates what can be achieved in this programmatic execution class. Class 1 missions are highly risk tolerant and programmatically scoped to take advantage of higher risk efforts resulting from highly constraint efforts. Although the GEARRS effort only cost ~$100K, Class 1 missions are typically binned as less than $1M and less than a year in duration. Heavy tailoring from the baseline satellite development process is fully expected.

Class 2 Example:

A representative example of a Class 2 mission would be a moderately cost and schedule constrained effort. The Satellite for High Accuracy Radar Calibration (SHARC) Satellite is an example of this type of effort. The SHARC mission did not require parts traceability and leveraged up-screened terrestrial components for much of its avionic system. This was an approximately 2-year effort with a full costing of less than $5M dollars. Like SHARC, Class 2 missions are fairly capable satellites with moderate to high bandwidth capability, precise attitude control, and higher power generation capability. Savings come from the acceptance of tailored practices from the baseline satellite development process and the removal of the parts traceability requirement resulting in the ability to fly terrestrial components that have been assessed for space suitability.

Information provided in the narratives of subfactor 1 and 2 will also be used to evaluate the offeror’s technical approach to the requirements detailed in Task Order 0003.

Volume III – Cost/Price

5.0 General Instructions

5.1 Price Reasonableness and Cost Realism

This section is to assist the Offeror in submitting data other than certified cost or pricing data that is required to evaluate the price reasonableness and cost realism of your proposed cost/price. Compliance with these requirements is mandatory and failure to comply may result in rejection of your proposal. Note that unrealistically low or 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. Offers should be sufficiently detailed to demonstrate price reasonableness and cost realism. The burden of proof for credibility of proposed costs/prices rests with the Offeror. The Offeror’s proposal shall contain sufficient data to substantiate both reasonableness and realism of the Offeror’s proposal.

5.1.1 Estimating Techniques and Methods

When responding to the Cost/Price Volume requirements in the Request for Proposal (RFP), the Offeror and associated subcontractors may use any generally accepted estimating techniques to develop its estimates.

5.1.2 Cost/Price Data

Data beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your cost/price position. All data relating to the proposed price, including all required supporting documentation, must be included in the section of the proposal designated as the Cost/Price volume. Under no circumstances shall Cost/Price data and documentation be included elsewhere in the proposal.

5.1.3 Cost or Pricing Data Requirements

In accordance with FAR 15.403-1(b) and 15.403-3(a), data other than certified cost or pricing data may be required to support a determination of price reasonableness. Data shall be provided in accordance with FAR 15.403-5. If, after receipt of proposals, the CO determines that there is insufficient data available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the offeror shall be required to submit additional cost or pricing data.

5.1.4 Rounding

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

5.2 Volume Organization

The Cost/Price volume for each Task Order shall consist of the following sections:

Provide a Table of Contents.

SECTION 1 – Submit the first page of the cost proposal with the following information:

(a) Solicitation number and applicable Task Order number

(b) Name and address of Offeror

(c) Name and telephone number of point of contact

(d) Name, address and telephone number of the Cognizant DCMA and DCAA offices

(e) Proposed cost, fee, COM, NMGRT (if applicable), and total by CLIN and Total

Task Order

(f) Period of Performance

(g) Offer Fiscal Year (OFY)

(h) Date of submission and expiration date of offer

(i) Name, title, and signature of authorized representative

(j) DUNS number

(k) CAGE Code

SECTION 2 – Data other than certified cost or pricing data. Narrative of estimating methodology/basis of estimates for each cost element; summary descriptions of estimating, purchasing, and accounting systems; and changes to estimating, accounting practices, or Cost Accounting Standards (CAS) Disclosure Statement. Provide Cost Summaries here.

SECTION 3 – List each exception to the ground rules and assumptions provided in the Request for Proposal and each qualification of the Cost/Price volume, if any. Provide complete rationale for any exceptions.

5.3 Estimating Methodology (Include in Section 2)

5.3.1 Estimating System

Provide a summary description of your standard estimating system or methods. The summary description shall cover separately each major cost element. Also, identify any deviations from your standard estimating procedures in preparing this proposal volume. Fully explain any deviations from your established business practices. Indicate whether you have Government approval of your system and if so, provide evidence of such approval.

5.3.2 Purchasing System

Provide a summary description of your 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). Also, identify any deviations from your standard procedures in preparing this proposal. Fully explain any deviations from your established business practices. Indicate whether you have Government approval of your system and if so, provide evidence of such approval.

5.3.3 Accounting System

Indicate whether you have Government approval of your accounting system and/or if your accounting system has been determined, by the Government, to be acceptable for accruing costs under a cost reimbursement contract. If so, provide evidence of such approval/acceptance.

Also, identify any deviations from your standard procedures in preparing this proposal. Fully explain any deviations from your established business practices.

5.3.