Inactive

This Sources Sought/Request for Information (RFI) is being issued solely for information and planning purposes and does not constitute an Invitation for Bids (IFB), a Request for Proposals (RFP), a Re... This Sources Sought/Request for Information (RFI) is being issued solely for information and planning purposes and does not constitute an Invitation for Bids (IFB), a Request for Proposals (RFP), a Request for Quotations (RFQ) or an indication that the Government will contract for any of the items and/or services contained in this notice. In accordance with FAR 52.215-3, Request for Information or Solicitation for Planning Purposes, the Government will not pay for any information/items submitted in response to the SS/RFI. No determination as to the viability of this potential requirement has been made at this point and there is not currently a solicitation for this effort. A. BACKGROUND The purpose of this effort is to contract for engineering services for tasks that are needed in support of Launch and Early Orbit, Anomaly Resolution, and Disposal Operations (LADO) software. LADO consists of three major functions: 1) Telemetry, Tracking and Commanding (TT&C), 2) Mission Planning, and 3) LADO Simulation. The TT&C provides the commanding of the satellite(s), sending and receiving telemetry as well as tracking data. Mission Planning is responsible for the planning and execution of satellite maneuvers during launch and early orbit (LEO), anomaly resolution and disposal activities. The LADO Simulator provides a simulation of telemetry, commanding and selected subsystems functionality for the different block type satellites forming the GPS constellation. It also provides simulation of specified maneuvers and anomalies, as well as ground facilities utilized for the LADO mission. The Government is currently using the software and hardware in the table below. The proposed follow-on contract requires contractor to work with the listed software and hardware. The Contractor shall support all LADO products that contribute to LADO systems that are both currently in place and any mission unique systems built into LADO. The software list includes, but is not limited to the following products: TT&C and Scheduling Core Application Bundle Front End Devices and Hardware • AceCP • AceVS • AceWLS • AceTWS • AceCPB • AceDBE • AceMenu • AceTS • AceAdmin • AceRM • AceFCM • AceCCT • AceCTK • AceSIU-Black • AceSIU-Red AceADE • Orbit Determination Simulation Software Front End Devices • AceSIM • IIR • AceSIU • AceTWG • IIF and ground control segment interface to STARSim (IIF flight code) • AceKS252 Table 1: AcePremier Applications B. PROGRAM REQUIREMENTS The purpose of this SS/RFI is to provide LADO sustainment support to include, but not limited to, software and hardware upgrades/modifications, documentation support, GPS II anomaly support, engineering/database administrator support, software and hardware integration, changes to the enterprise architecture, and test support for LADO. The contractor shall also purchase material required to sustain LADO until its replacement is fully operational. Material includes software/hardware licenses, hardware, maintenance agreements, and other material as required. 1. Provide engineering services in a government environment, including software development activities and system engineering for the LADO system. 2. Lead the development, program management, and processing of security related approvals to include the Authority to Operate processes on various Information Technology (IT) and mission related systems. 3. Analyze and evaluate cybersecurity aspects of the LADO system to identify, manage, and mitigate risk and vulnerabilities to Government procured/developed systems according to requirements dictated by the AFI17-101_DAFGM2024-01 Risk Management Framework (RMF) for Department of the Air Force Information Technology (IT). 4. Perform integration and testing services to identify and document system capabilities as well as mitigate risk. 5. Provide support on engineering studies on LADO up to four times a year. 6. Provide LADO education and training to meet mission requirements. C. INSTRUCTIONS FOR SOURCES SOUGHT/RFI RESPONSE Your response must include four sections as described below: Company Profile, Capability Statement, Proposed Approach, and Data Rights Assertions. You may choose to include an optional Additional Comments/Information section. Please submit your SS/RFI Response via email to Raquel Carillo at raquel.carrillo@us.af.mil, Ashlee Hawkins at Ashlee.Hawkins@us.af.mil, and Christa Phillips at christa.phillips.1@us.af.mil NLT 1200 MST on 07 MARCH 2025. Responses must be in 12 pt Times New Roman font and have 1-inch margins. Section 1: Company Profile (please limit this section to a no more than two (2) pages) 1. Please describe your company’s general experience providing Program Management. 2. Describe similar services offered to the Government or to commercial customers within the past three years. 3. What current access does your company have to government systems? 4. What is your business size and type (i.e., small, woman-owned, veteran-owned, etc.) Section 2: Capability Statement (please limit this section to no more than three (3) pages) 5. The Capability Statement must outline your capability in meeting the specific requirements outlined in the attached Performance Work Statement (PWS). 6. What experience does your company have providing software engineering to DoD organizations utilizing Agile & Waterfall approaches? 7. What experience does your company have with providing oversight management, Engineering and technical/test services, and education and training with DoD satellite Command and Control (C2) organizations? 8. Provide examples of integrating advanced technologies into new and legacy platforms/systems. 9. Please describe your company’s role in developing and leading Authority to Operate (ATO) processes on various Information Technology (IT) and mission related systems that your company has been developed and lead. 10. Please describe your company’s familiarity in working with Secret Programs. 11. How will your company overcome any possible software licensing restraints? Section 3: Proposed Approach (please limit this section to a single page) 12. Would you recommend a different NAICS Code than 541511? 13. In your company’s opinion, which “contract type” is applicable to this solution? 14. Please provide a simple outline and schedule for this effort. 15. Please identify if subcontracting will be part of the solution, and, if so, what percentage will be subcontracted? 16. Please provide a list of applicable labor categories and the rates associated with these labor categories. Section 4: Data Rights Assertions (No specific page limit) 17. Per DFARS 252.227-7017 IDENTIFICATION AND ASSERTION OF USE, RELEASE, OR DISCLOSURE RESTRICTIONS (JAN 2025), please provide Data Rights Assertions in accordance with the provision below: (a) Definitions. As used in this provision— “Computer software” is defined in— (1) The 252.227-7014, Rights in Other Than Commercial Computer Software and Other Than Commercial Computer Software Documentation, clause of this solicitation; or (2) If this solicitation contemplates a contract under the Small Business Innovation Research Program or Small Business Technology Transfer Program, the 252.227-7018, Rights in Other Than Commercial Technical Data and Computer Software—Small Business Innovation Research Program and Small Business Technology Transfer Program, clause of this solicitation. “SBIR/STTR data” is defined in the 252.227-7018, Rights in Other Than Commercial Technical Data and Computer Software—Small Business Innovation Research Program and Small Business Technology Transfer Program, clause of this solicitation. “Technical data” is defined in— (1) The 252.227-7013, Rights in Technical Data—Other Than Commercial Products and Commercial Services, clause of this solicitation; or (2) If this solicitation contemplates a contract under the Small Business Innovation Research Program or Small Business Technology Transfer Program, the 252.227-7018, Rights in Other Than Commercial Technical Data and Computer Software—Small Business Innovation Research Program and Small Business Technology Transfer Program, clause of this solicitation. (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 Business Innovation Research (SBIR) Program or Small Business Technology Transfer (STTR) Program, these Sources Sought/Request for Information Title: LADO Follow-On Posted: 05 Feb 2025 Responses Due: 07 March 2025 requirements apply to SBIR/STTR data that will be generated under the resulting contract and will be delivered with SBIR/STTR data rights and to any other data that will be delivered with other than unlimited rights. Notification and identification are 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 to be Furnished With Restrictions* [1] Basis for Assertion** [2] Asserted Rights Category*** [3] Name of Person Asserting Restrictions**** [4] (LIST)***** [5] (LIST) (LIST) (LIST) * [1] 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. ** [2] 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. *** [3] 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). **** [4] Corporation, individual, or other person, as appropriate. ***** [5] Enter “none” when all data or software will be submitted without restrictions. Date _________________________________ Printed Name and Title _________________________________ _________________________________ Signature _________________________________ (End of identification and assertion) (e) An offeror's failure to submit, complete, or sign the notification and identification required by paragraph (d) of this provision with its offer may render the offer ineligible for award. (f) If the Offeror is awarded a contract, the assertions identified in paragraph (d) of this provision shall be listed in an attachment to that contract. Upon request by the Contracting Officer, the Offeror shall provide sufficient information to enable the Contracting Officer to evaluate any listed assertion. (End of provision) Section 5: Additional Comments/Information (please limit this section to a single page) 18. Please provide any comments/questions regarding this effort. Please see the attached SS/RFI Instructions and PWS.