007000_Attch1_TAFB Outage Request Form.pdf
PDF 186 KB Posted
- Solicitation number
- FA813727R0002
About this file
This is a Tinker Air Force Base Outage Request Form template used to document and process service interruptions for utility and facility systems at the base.
The form establishes three classification categories for outages: Planned (Routine) outages, which must be submitted 60 calendar days in advance for roads/parking lots/sidewalks, 21 calendar days for utilities, and 10 calendar days for fire alarm testing; Limited Notice (Urgent) outages requiring 21 calendar days notice for roads/parking/sidewalks, 10 calendar days for utilities, and 7 calendar days for fire alarm testing; and Emergency outages that must be accomplished immediately to protect property or occupant health, submitted with less notice than Urgent timelines and requiring a completed form explaining the emergency circumstances. The form captures project information including project number, name, location, outage start/end dates and times, and description of work. Requesters must identify the type of outage or closure (Fire Suppression, Gas, Steam, Breathing Air, Sidewalk, Fire Alarm Outage, Fire Alarm Testing, Domestic Water, Chilled Water, Road, Electric, HVAC, Compressed Air, Parking Lot, or Gate(s)) and specify required operational support from shops including Plumbing, Electrical, HVAC, Alarms/Sprinkler, OG&E, Fire Department, Plant Maintenance, and Honeywell. The form requires contact information for the requestor and TAFB Contract Point of Contact (Inspector/PM/COR), with submissions directed to the Utility Outage Coordination Team at the provided email address. Routine or Urgent requests received after 1 p.m. will be processed the next business day, while emergency requests outside normal working hours (0700-1600 M-F) should call Customer Service Desk at 734-3117.
View the file
Other files
Show 40 more
50 files 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
All outages and service interruptions will be classified in one of three possible categories:
a. Planned (Routine) – An interruption in parking or utility services, which can be foreseen well in advance and/or is part of an existing schedule. Planned outages include all repair projects, with enough lead time to allow them to be accomplished on a non-emergency basis, and all capital and renovation projects which require outages during construction. Planned outages should be submitted to the Outage Coordinator prior to the requested outage using the following timelines:
• Roads/Parking Lots/Sidewalks – 60 calendar days
• Utilities (all) – 21 calendar days
• Fire Alarm Testing – 10 calendar days
b. Limited Notice (Urgent) – An interruption in parking or utility services that cannot reasonably be foreseen in advance to be considered a “routine” outage or which does not allow for extensive pre-planning or coordination prior to the interruption. A Limited Notice Outage may be required when repairs must be accomplished within a short time frame (which may not allow time for BCE to notify or meet with stakeholders) to safeguard property and occupant health.
Limited Notice or Urgent outages should be submitted to the Outage Coordinator prior to the requested outage using the following timelines:
• Roads/Parking Lots/Sidewalks – 21 calendar days
• Utilities (all) – 10 calendar days
• Fire Alarm Testing – 7 calendar days
c. Emergency Outage – An interruption in parking or utility services that must be accomplished immediately to safeguard property or occupant health. This may occur as the result of a natural or human-caused hazard. Examples of emergency outages may include, but are not limited to:
mechanical failure, flooding within buildings, water line breaks, electrical outages or “power blips”, or hazardous materials incidents. Outages requests are considered an Emergency Request if they are submitted to the Outage Coordinator in a time frame that is less than the Urgent timelines noted above. Emergency requests must still be supported with an outage request form explaining the situation and reason that the outage cannot be accomplished as a Routine or Urgent Outage. Emergency Requests outside of normal working hours (0700-1600 M-F) should call the Customer Service Desk at 734-3117 for immediate assistance.
| Form - Outage Request |
| Vance Gate Outage Request Form.pdf |
| Other or Remarks: |
| Gates specify which: |
| Primary_2: |
| Type1: Off |
| Type2: Off |
| Type3: Off |
| Reason: |
| Work Order #: |
| Project #: |
| Description of Work to be Performed: |
| Other Operational Support Required: |
| Impact of Outage: |
| Check Box19: Off |
| Check Box20: Off |
| Check Box21: Off |
| Check Box22: Off |
| Road_2: Vance Gate |
| Project Name: |
| Exact Location Bldg Post intersection etc: |
| Outage Start Date: |
| Outage End Date: |
| Outage StartTime: |
| Outage End Ti me: |
| Primary: |
| Position: |
| Phone: |
| Email: |
| Alternate: |
| Position_2: |
| Phone_2: |
| Email_2: |
| TAFB Contract Point of Contact lnspectorPMCOR: Darren Hulsey |
| Position_3: |
| Phone_3: |
| Email_3: |
| Alternate_2: |
| Position_4: |
| Phone_4: |
| Email_4: |
| Check Box1: Off |
| Check Box2: Off |
| Check Box3: Off |
| Check Box4: Off |
| Check Box5: Off |
| Check Box6: Off |
| Check Box7: Off |
| Check Box8: Off |
| Check Box9: Off |
| Check Box10: Off |
| Check Box11: Off |
| Check Box12: Off |
| Check Box13: Off |
| Check Box14: Off |
| Check Box15: Off |
| Check Box16: Off |
| Check Box17: Off |
| Check Box18: Off |
| Text19: |
| Text20: |
| Text21: |
| Text22: Preventive Maintenance on mechanical and electronic controls |
| Check Box23: Off |
| Check Box24: Off |
| Check Box25: Off |
| Check Box26: Yes |
| Check Box27: Off |
| Check Box28: Off |
| Check Box29: Off |
| Check Box30: Off |
| Check Box31: Off |
| Text32: |
| Text33: This gate is only open mornings and evenings. Mid day work will not impact traffic |
File details come from the government source that posted it. Updated .