20230130 RCC Tour for SFRC Contractors - Roles and Responsibilities of RE and CTR.pdf

PDF 60 KB Posted

Attached to
Space Force Range Contract (SFRC) Bidder's Library
Solicitation number
Not on record
Issued by

View the file

Other files

File Type Posted
SFRC Bidders Library 15 May 23.xlsx XLSX spreadsheet
SMC-Standard-012_16JAN2015.pdf PDF
Final CDRL Number Tracking.xlsx XLSX spreadsheet
SFRC Bidders Library 20 Apr 23.xlsx XLSX spreadsheet
How to Access Data Item Descriptions.docx DOCX document
SFRC Bidders Library 28 Mar 23.xlsx XLSX spreadsheet
WRIH Wiki Requirements Document.docx DOCX document
SLD 30 Org Chart.pdf PDF
T.O. 00-20-1.PDF PDF
T.O. 00-20-2.PDF PDF
T.O. 00-5-1.PDF PDF
SFRC Bidders Library 7 Mar 2023.xlsx XLSX spreadsheet
T.O. 00-5-3.PDF PDF
T.O. 00-20-14.PDF PDF
T.O. 00-20-3.PDF PDF
SFRC Bidders Library 17 Feb 2023.xlsx XLSX spreadsheet
StarGateUsersGuide.zip ZIP file
Q13_Supply_Point_Listing_DOL - Spares List.xlsx XLSX spreadsheet
SFRC Bidders Library 10 Feb 2023.xlsx XLSX spreadsheet
Radar 19.39 Transmitter Heat Exchanger LTA-24.pdf PDF
SFRC Bidders Library 1 Feb 2023.xlsx XLSX spreadsheet
TWU Combined CBA 2019_recd 03AUG2021.pdf PDF
Final IAM CBA 2019_recd 03AUG2021.pdf PDF
SFRC Bidders Library 26 Jan 2023.xlsx XLSX spreadsheet
IBEW CBA LU 413 2019-2023 IO Approved_recd 03AUG2021.pdf PDF
SLD 30 Hazardous Waste Management Plan - Final.pdf PDF
AFSSI 7702.pdf PDF
FINAL IBEW TPC 2021 2025_Final Executed Agreement.pdf PDF
00-35D-54.pdf PDF
SLD 45 HWMP - SLD 45 2021.pdf PDF
Vandenberg AFB Risk Management Plan_June 2020.pdf PDF
SLD 45-CCSFS SPCC Plan_June2014 Reviewed 2022.pdf PDF
CCSFS MSGP Stormwater Pollution Prevention Plan 2022sm.pdf PDF
Vandenberg AFB Refrigerant Management Plan June 2020.pdf PDF
00-20-14.PDF PDF
00-25-108.PDF PDF
00-32-1-101.PDF PDF
LTRS SSG Charter FINAL June2015.pdf PDF
EWR 127-1 1999.pdf PDF
UFGS 01 57 19.pdf PDF
afgm2018-90-01.pdf PDF
RCC319-19_FTS_Commonality.pdf PDF
SFRC Bidders Library 11 Jan 2023.xlsx XLSX spreadsheet
PSFB_SWMP.pdf PDF
Vandenberg AFB Halon Management Plan June 2020.pdf PDF
00-25-234.PDF PDF
AFSSI 7700.pdf PDF
SLD 45 Facility Response Plan - December 2020.pdf PDF
EMS_Consolidated_Playbook(Guide).pdf PDF
RCC501-12 Universal Documentation System.pdf PDF
Show 40 more

Latest 50 of 65 listed here. See the rest on GovTribe.

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

RCC Tour for SFRC Contractors/Bidders

Before on console support

Before day of launch the contractor is responsible for Operations, Maintenance and Sustainment of ground supporting equipment. This includes readiness checks to verify equipment is setup correctly, can flow data, and is in launch configuration. Any outages must be reported to RE as pre-count events.

During on console support

RE is part of the team that ensures we launch on time mission assurance (redundancy) and that we launch safely (meeting requirements). When there is an issue or an outage the contractor reports to the

RE. RE is responsible for taking Systems Capability status and interpreting outages and failures into

Operational Capability status to relay information to the User via the ROC or to Range Safety via the

MFCO/RSM. RE relies on accurate and expedient reporting from contractor. Reporting is made easier when site tech or site supervisor understands the operational impact of specific outages, but at a minimum the contractors need to have knowledge of system requirements, troubleshooting, and reporting.

Requirements come from UDS documentation. OR from user is responded to by OD from contractor.

The OD is then used to build out the range configuration.

Troubleshooting is done by Technical Orders (TOs) and experience working on various systems.

Updating TOs and drawings is a contractor responsibility.

Reporting is done via the PICAR method for Problem, Impact, Cause, Action, Recommendation.

Abbreviated reporting takes place within the last 15 minutes before T-0. Govt relies on contractor to make go/no-go statements associated with each anomaly.

In addition to day-of-launch operations there is also Training (which can be used for certification).

During rehearsals, the contractor drops cards based on either recurring issues that need to be practiced and new issues that haven’t occurred yet. Normally the training is split between Trusted Agents and new people getting trained/certified. Trusted Agents help determine which anomalies will be highlighted during a given rehearsal.

After on console support

After launch operations and after training rehearsals, contractors should support after action debriefs/hotwashes. Ctrs gather lessons learned and bring up opportunities for efficiency. Ctrs make changes and modifications for future launch support and future rehearsals/training.

Contractor is responsible for long term tracking of anomalies and resolving root cause.

File details come from the government source that posted it. Updated .