InspectorSat_RFI_-_21Jun19.pdf

REQUEST FOR INFORMATION

Local Asset Space Domain Awareness and Custody

Technical POC: Mr. Jason Guarnieri

Contracting POC: Mr. Peter Nicasio

OFFICE: AFRL/RVE

LOCATION: Kirtland AFB

1 OVERVIEW

The Air Force Research Laboratory (AFRL) is seeking information to understand: 1) the industrial base for autonomous Rendezvous and Proximity Operations (RPO) and InspectorSat capabilities and 2) the limits of current commercial technologies in this area.

This is a Request for Information (RFI), as defined in FAR 15.201(e). This RFI is not a request for competitive proposals; therefore, responses to this notice are not considered offers and cannot be accepted by the Government to form a binding contract. Responses should include information identifying whether the offer is a small or large business to NAICs Code 541715. Companies that respond will NOT be paid for the information submitted. No telephone calls will be accepted requesting a bid package or solicitation. There is NO bid package or solicitation.

2 BACKGROUND INFORMATION

The purpose of this RFI is to seek information as AFRL is interested in continuing research and development efforts into autonomous RPO and inspection capabilities previously investigated under the ANGELS and Mycroft space experiments. AFRL seeks to extend these experiments into a system for self-inspection and local area clearing around U.S. High Value Assets (HVAs). In recent years, the GEO belt has become cluttered with spent stages, dead satellites, and other orbital debris. This debris has the potential to not only collide with and threaten operational assets, but there is a potential for drift collisions between debris objects creating a larger debris field. The Air Force Space Surveillance Network has difficulty tracking very small objects at GEO and alternative solutions to augment its mission are being evaluated.

The challenge is to insert one or two small satellites into orbits around the HVA that are dedicated to monitoring the operational asset and its local area. It is anticipated that these satellites would be inexpensive ($10-50M each with NRE<$100M), small (<0.5x0.5x0.5 meter), and host enough sensing and processing capability to safely operate in proximity to national assets at reasonable ranges.

The envisioned operational architecture includes two InspectorSats in continuous proximity orbits around approximately 25 HVAs at GEO and HEO as well as hosting two InspectorSats with each future HVA launched. The architecture includes a reconstitution CONOPS for failed and end-of-life (EOL) InspectorSats. The space-segment will be controlled from a dedicated Mission Operations Center (MOC) independent from the various HVA MOCs, but will push warning messages and anomaly resolution data to the HVA MOCs.

2.1 ANTICIPATED CAPABILITIES:

• RPO capable satellite system

• Autonomous RPO for nominal operations

• Sensing payload capable of local-area threat detection

• Sensing payload capable of collecting resolved imagery of the HVA with quality sufficient to support anomaly resolution and change-detection

• On-board processing of local-area threat detection and change-detection algorithms

• On-orbit reprogrammable satellite operations and mission operations software

• Interoperability between the system software (space-based and ground-based) and other USAF

SSA capabilities for supporting threat identification and characterization

• Communications system that includes space-to-ground TT&C and Mission Data links and cross-link communications between sister satellites

• Cyber-hardened spacecraft and ground system

• Individual satellites have a minimum 3 year design life (5 year preferred)

2.2 COMMUNICATION BETWEEN PROSPECTIVE OFFERORS AND GOVERNMENT

REPRESENTATIVES: Dialogue between prospective Offerors and Government representatives is strongly encouraged. Prospective Offerors are welcomed to request sit-downs and provide demonstrations of firm’s capabilities. Discussions shall not constitute a commitment by the Government to subsequently fund or award any proposed effort. No guidance related to technical approach will be given. However, questions related to the objectives of the effort or prior similar efforts may be answered.

Offerors are advised that only Contracting Officers are legally authorized to contractually bind or otherwise commit the Government.

THIS IS A REQUEST FOR INFORMATION ONLY. This RFI is issued solely for information and planning purposes. It does NOT constitute a solicitation (Request for Proposal or Request for Quotations) or a promise to issue a solicitation in the future. This RFI does not commit the US Government (USG) to contract for any supply or service whatsoever. Furthermore, the USG is NOT, at this time, seeking proposals. Responders are advised that the USG will not pay for any information or administrative costs incurred in response to the RFI. All costs associated with responding to this RFI will be solely at the responding party's expense. All information received in response to this RFI that is marked PROPRIETARY will be handled accordingly. The USG shall not be liable for or suffer any consequential damages for any proprietary information not properly identified. Proprietary information will be safeguarded in accordance with the applicable Government regulations. Proprietary Information and Trade Secrets should be clearly identified.

Responses to this notice are not offers and cannot be accepted by the USG to form a binding contract or agreement. The Air Force will not be obligated to pursue any particular acquisition alternative as a result of this RFI. Responses to this RFI will not be returned. The USG is under no obligation to acknowledge receipt of the information received, or provide feedback to respondents with respect to any information submitted under this RFI. Responders to this RFI will have no competitive advantage in receiving any awards related to the submitted topic area. Not responding to this RFI does not preclude participation in any future solicitation, if one is issued.

The information gathered from this RFI may contribute to future program acquisition technology development strategies and frame future solicitations, if issued. The USG will not use any proprietary information submitted to establish the capability, requirements, approach, or solution so as to not inadvertently restrict competition.

3 SAMPLE RESPONSE OUTLINE

There is a suggested total page count limit of 15 pages for topic response. The following is a suggested outline for a response to this RFI. The page limitation and outline to this RFI is intended to minimize the effort of the respondent. Nevertheless, respondents are free to develop their responses as they see fit.

AFRL is interested in responses that address entire envisioned architecture. Responders are encouraged to adjust the envisioned architecture as they judge necessary with the following exceptions. First, the MOC will be independent of the HVA. Second, the InspectorSats will be able to collect resolved imagery of the subject HVA.

3.1 SECTION 1: CORPORATE EXPERTISE

Briefly describe your company, your products and services, history, ownership, financial information, and other relevant information. As part of your corporate expertise, please highlight critical elements in the envisioned architecture. Also, discuss your ability to perform work in a classified environment. It is expected that Section 1 is less than 10% of the response.

3.2 SECTION 2: TECHNICAL SOLUTIONS

Describe your company’s concept for the envisioned architecture (or modified architecture). The concept should address all system elements (e.g. space segment, ground segment, launch, interoperability, etc.).

The concept should discuss deployment to HVAs currently on-orbit, hosting on future HVAs, and reconstitution.

Describe your notional InspectorSat spacecraft bus and sensor suite and discuss your approach to nominal operations including RPO maneuvers, ranges, and required delta-V. Assess manufacturability and the ability to produce 25-30 units per year.

Describe any technologies in your current product line, as well as, products currently under development that meet the capabilities identified in Section 2. Provide performance and physical specifications for each product, as well as anticipated performance for products under development.

Suggest an experiment to demonstrate your company’s architecture concept. The experiment should include at least two InspectorSats, a command and control system, incorporate autonomous RPO and elements of interoperability with existing SSA systems.

3.3 SECTION 3 - COST AND SCHEDULE ESTIMATES

Provide Rough Order of Magnitude (ROM) cost and schedule estimates for design/build to properly scope a USG acquisition strategy.

3.4 SECTION 4 - ADDITIONAL MATERIALS

Please provide any other materials, suggestions, and discussions you deem appropriate. Include any recommended structure of the requirements in the event the government decides to issue a request for proposal.

4 SUBMISSION OF RESPONSES:

There is a recommended total page count limit of 15 pages for topic response. This page count does not include coversheet. The page limitation to the RFI is intended to minimize the effort of the respondent.

Responses to the RFI should be submitted in MS Word format in 12 point font, double-spaced with one-inch margins, and use standard letter size (8.5'' x 11") paper. Responses are due no later than 1 July 2019.

Responses to all or part of this RFI will be accepted. Contact Mr. Jason Guarnieri at 505-948-8318 or 877- 225-6157 to coordinate classified submissions.

Responses to this RFI must be submitted to AFRL. Responders shall provide one electronic copy (Microsoft Word or PDF) of their unclassified response via AMRDEC SAFE (instructions ae attached below). DO NOT send via email. Submission of marketing information, existing commercial documentation and product literature is NOT an acceptable response. Responses to this notice may be classified. Contact the POC for classified submission options prior to submitting a response.

Responders are advised that employees of commercial firms under contract to the USG may be used to administratively process responses or perform other administrative duties requiring access to other contractors' proprietary information. These support contracts include nondisclosure agreements prohibiting their contractor employees from disclosing any information submitted by other contractors or using such information for any purpose other than that for which it was furnished.

In order to complete its review, AFRL must be able to share the information within the Government and with its support contractors; therefore, any responses marked in a manner that will not permit such internal government review will be deleted without being assessed/considered.

Any response to this RFI may be subject to review by non-government personnel. The role of these advisory and assistance services (A&AS) contractors, University Affiliated Research Center (UARC) employees, and Federally Funded Research and Development Center (FFRDC) employees are to function as technical advisors to the programmatic decision making.

4.1 . FORMAT: The responses shall be formatted as follows:

4.1.1 SECTION A. COVER SHEET: Offerors shall submit the following information on the cover sheet:

a.) Title of Technical Proposed Approach b.) Name of Company c.) Mailing Address d.) Company website e.) Business Size to NAICS 541715 f.) Company's Commercial and Government Entity (CAGE) number g.) Dun & Bradstreet (D&B) Data Universal Numbering System (DUNS) number h.) Contracting POC and Technical POC with appropriate telephone numbers, and email addresses for the POCs i.) Classified level at which company is cleared (Facility & Key Personnel) j.) Mailing address for forwarding classified material (name, address, zip code) k.) Cognizant security office (name, address, zip code), and Offeror's security officer's name and telephone number) l.) Proposed Schedule (# of Months) m.) Total ROM cost estimate n.) Proposed Contract/Agreement/OTA Type o.) Proposed Government Furnished Property/Base Support p.) Proposed Data Rights q.) Teaming Arrangement or Subcontractors/consultants, including Cage codes

4.1.2 SECTION B. NARRATIVE: The narrative should include but not be limited to the following:

a.) Discussion of the nature and scope of the research; the problem statement; the Offeror’s proposed objectives and technical approach/solution; all relevant assumption; an overview of tasks and methods to achieve each objective; and expected results b.) Evidence of current Technology Readiness Level (TRL) and a description of state-of-the-art knowledge or methods to be employed, along with a clear strategy, resources and schedule for maturing the technology to the proposed level c.) Description of final products to be delivered (prototypes, demos, software, etc.)

d.) Mapping of effort to specific need(s) outlined in the topic area description, with a strategy for transition of deliverables to a Government acquisition program. Transitions can be specific to an existing/future system or have broad application to several existing/future systems e.) Any restrictions on Government use, release, or disclosure of technical data f.) Key personnel, consultants or subcontractors to support the effort and evidence of expertise and experience to accomplish the proposed tasks

NOTE: Resumes, descriptions of facilities and equipment, and proposed Statement of Work are not required at this point.

4.1.1.3 SECTION C. ROM COST: Provide a ROM cost estimate for planning purposes. The ROM should provide top-level details on major cost items such as labor (# of FTEs), special equipment that will need to be purchased, materials, and any subcontracts or other organizations’ costs (to include government furnished facilities, equipment, or personnel) for the proposed effort.

5 TIMELINE

The following is a notional timeline for the RFI and follow-on activities.

• 21 June 2019: RFI is published

• 22 July 2019: RFI responses are due

• 29 July 2019: Targeted date for asking for any follow up information the team may require to develop the Acquisition Strategy

6 SUMMARY

Local-area threat detection, anomaly resolution, and change-detection are difficult problems and innovative, cost effective solutions are required. One option is Local Asset Space Domain Awareness and Custody to augment the Air Force Space Surveillance Network. To encourage competition and guide potential future acquisitions, the Air Force Research Laboratory Space Vehicles Directorate (AFRL/RV) is seeking information to understand: 1) the industrial base for autonomous Rendezvous and Proximity Operations (RPO) and InspectorSat capabilities and 2) the limits of current commercial technologies in this area.

The questions listed in this RFI are not all-inclusive and we strongly encourage each respondent to provide any additional information that you think may be vital to support our efforts in accurately scoping the technological thresholds and objectives, realistic schedule estimations, and budgetary programming for this key, high-interest mission area.

1 Attachment: AMERDEC Safe Submission Instructions

AMRDEC SAFE FILE SUBMISSION INSTRUCTIONS

1. Navigate to the AMRDEC SAFE website at https://safe.amrdec.army.mil/safe/.

2. If you have a CAC, click the large blue “Click Here” button under “CAC Users”.

a. When prompted, select your CAC certificate and enter your PIN if required.

3. If you do not have a CAC, click the large blue “Click Here” button under “Non-CAC Users”.

a. Enter your name and email address in the indicated boxes within the “Personal

Information” section.

https://safe.amrdec.army.mil/safe/

4. Under “File Information”, browse to and select your proposal document.

a. Repeat this step for each file. (Selecting multiple files is not supported, but you may individually upload multiple files.)

5. Check the “Privacy Act Data” box for any files that contain proprietary information.

6. In the “Description of File(s)” box, enter your organization’s name and the text, “ Insert Company

Name” and Document Name: RFI - Local Asset Space Domain Awareness and Custody

7. Under “Recipient Information”, enter the following email addresses. Each address must be entered separately by typing it into the “Email Address” box and clicking “Add”.

a. peter.nicasio@us.af.mil

b. jason.guarnieri.1@us.af.mil

8. Under “Email Settings”, check the following options:

a. “Encrypt email messages when possible”

b. “Notify me when files(s) downloads are COMPLETED”

c. “FOUO” (radio button on the right)

9. Click “Upload”, then “I Agree”.

10. After the upload is complete you will receive an email with the following subject: “AMRDEC Safe

Access File Exchange Submittal Notice” which you should keep. The email message will contain the submitted package ID link and SAFE password.

mailto:peter.nicasio@us.af.mil