SOURCES SOUGHT
R -- LAUNCH AND TEST RANGE SYSTEM (LTRS) INTEGRATED SUPPORT CONTRACT (LISC) FOLLOW ON CONTRACT
- Notice Date
- 6/4/2021 1:46:25 PM
- Notice Type
- Sources Sought
- NAICS
- 541330
— Engineering Services
- Contracting Office
- FA8823 SUSTAINMENT PKL PETERSON AFB CO 80914-2900 USA
- ZIP Code
- 80914-2900
- Solicitation Number
- FA8823-21-R-0009
- Response Due
- 7/16/2021 3:00:00 PM
- Archive Date
- 07/31/2021
- Point of Contact
- Kimberly S. McGough, Phone: 7195562919, Fax: 7195569464, Angela Eberhart, Phone: 7195560488, Fax: 7195562798
- E-Mail Address
-
kimberly.mcgough@spaceforce.af.mil, angela.eberhart.1@spaceforce.mil
(kimberly.mcgough@spaceforce.af.mil, angela.eberhart.1@spaceforce.mil)
- Description
- �������� LAUNCH AND TEST RANGE SYSTEM (LTRS) INTEGRATED SUPPORT CONTRACT (LISC) FOLLOW ON CONTRACT (LISC II) Description / Purpose 1.1 In partnership with Space Launch Delta (SLD) 30 and SLD 45, the Space Systems Command (SSC) Launch and Test Range System Program Office, Peterson Air Force Base, Colorado is seeking to identify qualified contractors for a long term, follow-on contract to the existing Launch and Test Range System (LTRS) Integrated Support Contract (LISC), which ends 30 September 2024.� The Government is contemplating the continuation of a combined Operations, Maintenance and Sustainment requirements of the Eastern Range (ER) and Western Range (WR) under LISC II to meet the HQ USSF Range of the Future (ROTF) vision and anticipated launch demands.� Modernizing range infrastructure to meet ROTF, improving LTRS efficiency and effectiveness, becoming more agile and responsive while enabling ER and WR mission success to include keeping the ranges �green� (operational) today and in the future.� The proposed LISC II effort is scheduled to commence in May 2024, and has an anticipated Period of Performance of one year base with up to nine one-year option periods. 1.2 The LTRS consists of the ER, headquarter at Patrick Space Force Base (PSFB) in Florida and the WR, headquartered at Vandenberg Air Force Base (VAFB) in California. The LTRS is comprised of a network of equipment providing range essential services to launch customers.� These services include: Communications, Vehicle performance & Assessment, Imaging, Positive Control, Surveillance, Weather, and Planning & Scheduling. ���LISC II is envisioned to be agile and responsive to a dynamic and increasing launch manifest, efficient in its ability to reconstitute, support parallel/concurrent operations, incorporate new concepts to rapidly upgrade systems, and incorporate commercial provisioning concepts. �The ROTF Vision focuses on a transformation of the current range architecture to leverage Autonomous Flight Safety Systems, and a smaller range footprint through virtualization and cloud-based range functions. The ROTF Vision prioritizes agility, responsiveness, equitable access, and resiliency. To implement these priorities, the LISC Follow On objectives are to 1) Award a contract(s) capable of maintaining operational mission assurance and customer demand through responsive, flexible, and efficient operations, maintenance, and sustainment (OM&S), and 2) Develop and acquisition structure that accelerates decision speed, maximizes budget execution, increases program capability, and accelerates contracting speed. The LISC II contemplates a contract structure that is immediately responsive to customer demands, including responsive range scheduling, rapid reallocation, commercial augmentation, and 3rd party provisioning at the lowest cost. 1.3 The contemplated LISC II requires a contract structure that is flexible to meet evolving launch user requirements, core operational range services, hardware and software maintenance and sustainment, as well as identify and execute modernization opportunities. Additionally of interest to the Government are industry�s innovative approaches and demonstration of capabilities or experience related to commercial augmentation of current or planned range services, 3rd party provisioning concepts that utilize a Plug and Play architecture approach, launch user Autonomous Flight Safety System (AFSS) enabled rockets in conjunction with other launch vehicles utilizing traditional ground-based flight safety, rocket body return concepts, and any experience supporting test operations for Major Range Test Facility Base (MRTFB) users (e.g. MDA, AFGSC, Navy, others). The Government is interested in industry�s ability to improve agility, resilience and flexibility of the Ranges, to include agile software development (e.g. Platform 1, DevSecOps, etc.), cloud-based data platforms, and streamlined data products and requirements generation.� Additionally, respondents should demonstrate their experience with innovative concepts that streamline pre-launch planning, execution or post-launch reconstitution in order to meet a rapid and dynamic launch cadence.� Requested Information 2.1 ��Qualified sources will submit an unclassified Statement of Capability (SOC) demonstrating their experience and capability in the task areas listed below. The SOC should provide specific examples of proficiency. Industry may provide responses to any or all of the areas specified below, depending on relevant past performance examples. Industry should not feel compelled to respond to areas outside of their expertise. Each subsection directs respondents to describe the contractor�s experience with areas within or related to the general scope of tasks. �� 2.1.1�� Range Operations The SOC should describe the contractor�s experience in the execution of operations of a DoD range function.� Specifically, the SOC should describe the contractor�s ability to provide this effort in an environment similar to the ER/WR (e.g. highly complex (system of systems) performing safety critical functions).� The following is a general description of the day-to-day scope involved in supporting range operations: Interfacing with Government to receive work requests, classify the work, task, and document the work Interfacing with launch, spacecraft, aircraft, and other support contractors Integration with the Universal Documentation System (UDS) to include reviewing, creating, tracking, storing and maintaining of UDS documentation to include, but not limited to, Program Introductions, Statements of Capabilities, Program Support Plans, and Operational Directives Range operations planning including lead range and non-lead roles Cost estimating, segregating, and tracking for multiple billing accounts/customers, including interfacing with standard DAF systems, such as Job Order Cost Accounting System (JOCAS) Range scheduling, to include asset identification, schedule creation/maintenance, and asset deconfliction Operations and maintenance coordination which facilitates the coordination of range activities including emergency support, resource deconfliction, and status tracking Mission preparation to include document preparation and mission briefings Operation of mission equipment to include metric radars, telemetry, command destruct, optics, surveillance (air, land, sea), weather, communications, range safety (in support of Flight Termination System (FTS) customers), data handling (recording, processing, storage), and timing systems Classified and Special Access Program support Operator training to include training preparation, training documentation and presentation Maximize ability to execute concurrent operations Maximize use of commercial augmented range capabilities (e.g. Radars, Telemetry, Optics, etc.) to meet user requirements Post mission analysis and anomaly reporting Range Organizational (Level 1) Maintenance The SOC should describe the contractor�s experience in providing organizational maintenance activities (consistent with DAF & USSF 2-level maintenance policies) for highly complex and safety critical systems. The following is a general description of range organizational (level 1) maintenance type tasks: Maintenance control to include status and maintenance briefing Executing a maintenance program to include corrosion control, maintenance management, maintenance analysis (metrics tracking and analysis), equipment maintenance support, system assessments (capability assessment and performance assessment and testing), equipment repair and servicing Using and/or interfacing with the Government maintenance data collection systems (e.g. Integrated Maintenance Data Systems (IMDS)/Core Automated Maintenance System (CAMS), for recording maintenance actions and status, and Standard Base Supply System (SBSS) for maintenance supply support Use of commercial augmented range capabilities (i.e., radars, Telemetry, Optics) to meet range user requirements Providing logistics management to include forward supply point accountability and technical library functions Production of expected mission coverage plans to include updates and equipment configuration requirements Configuration control of the operational system Range Hardware Depot (Level 2) Maintenance The SOC should describe the contractor�s experience in providing Hardware Depot Maintenance consistent with DAF & USSF 2-level maintenance policies. This should address at a minimum the contractor�s ability to provide depot maintenance at a system level, including management, on-site and off-site activities, operations support, urgent and emergency depot support, and periodic depot maintenance (PDMs). The following is a general description of range hardware depot level maintenance type tasks: Responding to customer mission requirements including responding to requests for urgent and emergency depot support Providing timely depot maintenance support given changing operational schedules Executing processes which optimize repair of Line Replaceable Units (LRU) utilizing in- house organic, Government logistic repair centers and OEM facilities while expediting turn- around times Executing processes to support storage, maintenance, spare parts, packaging, handling and transportation Determining initial depot maintenance intervals Performing emergency and unscheduled hardware maintenance Capturing and applying metrics to adjust depot maintenance intervals Planning for and performing PMDs for complex systems Range Software Depot Level Maintenance The SOC should describe the contractor�s experience in functioning as a software depot consistent with DAF & USSF 2-level maintenance policies.� It should include the contractor�s capabilities in terms of software maintenance processes.� The following is a general description of software depot level maintenance type tasks: Managing and controlling software engineering to ensure all software activities are conducted following a standard (e.g. CMMI) software process Planning and controlling the technical, business, and project management efforts necessary to accomplish software maintenance objectives in accordance with an established schedule Performing emergency and unscheduled software maintenance Maintaining and modifying the software product baseline as directed by the Government configuration control process Developing and maintaining software related Technical Data Conducting Functional Configuration Audits and Physical Configuration Audits (FCA/PCA) to verify the functional and physical baselines of software products and demonstrate they have met the technical requirements of the product specifications Implementing DevSecOps and/or other rapid/responsive SW development approaches Range Logistics Management The SOC should describe the contractor�s experience in providing logistics management services.� The following is a general description of range logistics management type tasks: Acting as the Source of Repair (SOR) to include the management of both warranties and Depot repair actions Stocking, storing, and issuing items at the wholesale level using an automated inventory and maintenance data management system Acting as the Inventory Control Point (ICP) Providing supply support to include �pipeline spares� to correctly stock forward supply points and bench stocks Acting as the source of supply for peculiar spare parts through the SBSS Providing Interim Supply Support (ISS) spares requirements inputs to support Government programming Interfacing with Government organic depot repair centers for �common� item repair and contracted depot repair centers for �other depot� repair items Interfacing with the Military Standard Transportation and Movement Procedures (MILSTAMP) to provide the most economical shipment Implementation Air Force Toral Asset Visibility (TAV) requirements and applying Item Unique Identification (IUID) principles Range Sustainment Engineering The SOC should describe the contractor�s experience in performing sustainment engineering efforts on range systems, products or materials required to resolve technical or supportability deficiencies revealed in operational service. This includes all associated efforts such as; engineering and technical data, modeling, simulation, and testing, which are integral to the completion of the overall sustainment engineering task. The following is a general description of range sustainment engineering type tasks: Assessing Reliability, Maintainability, and Availability (RMA) deficiency indicators; defining the characteristics and cause of such deficiencies Performing obsolescence/replacement engineering and vanishing vendor analysis to include maintaining a Diminishing Manufacturing Sources and Material Shortages (DMSMS) program Determining the impact on the affected product/system; identifying and evaluating alternative solutions Determining the preferred solution; and designing, integrating and validating the solution Preserving comprehensive cybersecurity/Risk Management Framework (RMF) attributes as an objective Range Modifications/Project Management The SOC should describe the contractor�s experience in implementing modifications to in- service, configuration-managed USSF assets. The following is a general description of types of processes followed in performing range modifications type tasks: Scalable processes for modification management, modification engineering and modification test and integration (Processes typically cover from the receipt of direction, requirements and concept for operations (CONOPS) through final testing and operational acceptance by the government using a Configuration Control Board (CCB) process) Cybersecurity processes (e.g. RMF) and associated certification requirements The identification of interfaces with other processes such as the Integration Management and Testing and Sustainment Engineering processes Software engineering processes as defined within the overall process of modification engineering and design Comprehensive program management approaches to maintaining cost, schedule, and performance baselines Perform Earned Value Management (EVM) analysis on projects and/or Range modifications Rapid and responsive contracting processes Provide cost estimates for both annual support to range users, operational support to range users and for additive work in support of user or Government requirements Range Integration Management, Test and Evaluation The SOC should describe the contractor�s experience in performing integration management and testing functions which would integrate all major activities: operations, maintenance, sustainment and modifications. The SOC should describe how this function should interface with a government System Engineering Plan and Systems Engineering, Integration and Test (SEIT) functions. The following is a general description of range integration management and testing type tasks: Baseline configuration management to include requirements management Data management to include a data repository Technical data management Technical manual development, production and maintenance Development and implementation of a robust quality management program Integrated master schedule management Integration and test management Development of test materials, test planning and execution Assess test data and evaluate results Post test data products and architecture updates Assess total ownership cost impacts of modification recommendations Interfacing with launch, spacecraft, and other support contractors, including external development contractors Operational Acceptance (OA) The SOC should describe the contractor�s experience in performing OA and integration of new projects onto a technical baseline. Describe the functions which are required to coordinate, integrate and execute successful OA (e.g. Development Testing, Operational Testing, Technical Orders, Training, etc.).� Cybersecurity The SOC should describe the contractor�s experience in performing cybersecurity across the entire spectrum of OM&S activities. The following is a general description of cybersecurity activities: RMF package development, coordination and approvals Authority to Operate coordination and approvals to include strategies for continuous ATOs Coordinate cybersecurity controls embedded within projects and modernization efforts Interfacing with other support contractors in the management of the cybersecurity posture 3.0 Responses 3.1 The SOC shall be organized into two sections. Section 1 of the SOC shall provide administrative information, and shall include the following as a minimum: 3.1.1. Name, mailing address, contractor CAGE code, overnight delivery address (if different from mailing address), phone number, fax number, and e-mail of designated point of contact. 3.1.2.� Business type (large business, small business, small disadvantaged business, 8(a)-certified small disadvantaged business, HUBZone small business, woman-owned small business, very small business, veteran-owned small business, service-disabled veteran-owned small business) based upon North American Industry Classification System (NAICS) code 541330 - Engineering Services, with a size standard of $41.5 M in average annual receipts.� Responses from Small and Small-Disadvantaged business are highly encouraged.� Responses from small business and small, disadvantaged business firms are highly encouraged. Interested parties shall state the size of their business. Each SOC must include a cover page and table of contents. The number of pages in Section 1 of the white paper shall not be included in the 35-page limitation, electronic submission, i.e., the 35-page limitation applies only to Section 2 of the SOC. 3.2. �Section 2 of the SOC shall include the contractor�s responses to any or all of the areas from Section 2 of this Sources Sought. Contractor�s should clearly state its capabilities for any particular section in a logical numbering schema and provide clear alignment to one of the areas in Section 2 of this Sources Sought. 3.3. Section 2 of the SOC shall not exceed 35 pages, electronic submission, in total length. The Government is interested in qualified sources that can meet any portion, or all of the services and concepts discussed in Section 2 of this Sources Sought. All responses must conform to 8.5x11 inch pages, with font no smaller than 12 point. This sources sought synopsis is for informational market research only and in no way obligates the government. 3.4 The SOC shall be delivered in Microsoft Word format or PDF format, electronic submission only, and are due no later than 16 Jul 2021, 16:00 MST.� Responses shall be limited to 35 pages, electronic submission, for Section 2 and submitted via e-mail to the Primary Point of Contact (POC), Ms. Kim McGough, Procurement Contracting Officer (PCO), at kimberly.mcgough@spaceforce.mil and the Secondary POC, Ms. Angie Eberhart, Contract Specialist, at angela.eberhart.1@spaceforce.mil. Proprietary information, if any, should be minimized and MUST BE CLEARLY MARKED.� To aid the Government, please segregate proprietary information.� Please be advised that all submissions become Government property and will not be returned.� 4.0 Questions Questions regarding this announcement shall only be submitted in writing by e-mail to the Contracting Officer, kimberly.mcgough@spaceforce.mil with a courtesy copy to the Contract Specialist, angela.eberhart.1@spaceforce.mil.� Verbal questions will NOT be accepted.� Questions will be answered by posting answers the betaSAM.gov website; accordingly, questions shall NOT contain proprietary or classified information. The Government does not guarantee that questions received after 1 Jul 2021, 1600 MST will be answered.�
- Web Link
-
SAM.gov Permalink
(https://beta.sam.gov/opp/cd75f9ffd9fc4c8db968b472be3b4f54/view)
- Place of Performance
- Address: Colorado Springs, CO 80914, USA
- Zip Code: 80914
- Country: USA
- Zip Code: 80914
- Record
- SN06022428-F 20210606/210604230120 (samdaily.us)
- Source
-
SAM.gov Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's SAM Daily Index Page |