Attch 1 - Revised Performance Work Statement 28 Jun 10.doc

ATTACHMENT 1

PERFORMANCE WORK STATEMENT (PWS)

FOR

LAUNCH OPERATIONS SUPPORT CONTRACT

(LOSC)

Contract FA4610-08-R-0016

30TH SPACE WING - VANDENBERG AFB

Dated: 05 May 2009 Revised: 28 June 2010

THIS ATTACHMENT INCLUDING THE

TITLE PAGE CONSISTS OF 47 PAGES

LAUNCH OPERATION SUPPORT

Table of Contents

4I.

Description of Services

41.

INTRODUCTION

42.

SCOPE OF WORK

42.1.

GENERAL

42.2.

MAINTENANCE & REPAIR

132.3.

OPERATIONS

142.4.

OTHER SERVICES:

142.5.

MINOR FACILITY ALTERATION:

152.6.

SUPPORT:

223.

SUPPLEMENTAL CONTRACTOR RESPONSIBILITIES

223.1.

TRANSITION

233.2.

EMPLOYEES

243.3.

CONTRACTOR FURNISHED PROPERTY

263.4.

CONTINUATION OF MISSION ESSENTIAL FUNCTIONS

264.

FUNDING VEHICLES

264.1.

CONTRACT WORK REQUEST

264.2.

TASK ASSIGNMENT

275.

VANDENBERG AFB GENERAL REQUIREMENTS

275.1.

ENERGY CONSERVATION

275.2.

ENVIRONMENTAL:

275.3.

FINANCIAL

285.4.

QUALITY SYSTEM

285.5.

SAFETY

295.6.

SECURITY

31II.

Services Summary

311.

Services Summary Incentive Objectives

322.

Services Summary Performance Objectives Matrix

37III.

Government-Furnished Property and Services

371.

Government Furnished Property

372.

Government Furnished Resources and Services

372.1.

Civil Engineer Services

372.2.

Communications-Administrative Telephones

372.3.

Global Positioning System Units

372.4.

Medical

372.5.

Safety Support

372.6.

Security Police Services

372.7.

Supply Support

372.8.

USAF Training for Contractor Employee

382.9.

Vandenberg AFB Facilities

39IV.

General Information

391.

ACRONYMS

412.

DEFINITIONS

443.

HOURS OF OPERATIONS

443.1.

Non-Normal Hours

454.

PERFORMANCE OF SERVICES DURING CRISIS DECLARED BY THE NATIONAL COMMAND AUTHORITY OR OVERSEAS COMBATANT COMMANDER

455.

PROPERTY AND EQUIPMENT

455.1.

Alarms

455.2.

Cranes & Hoists

455.3.

Elevators

455.4.

Generators

455.5.

Mechanical Systems

455.6.

Other Property/Equipment

455.7.

Diesel Electric Unit (DEU)

455.8.

Pressure Vessels and Tanks

455.9.

Structural

455.10.

Towers

465.11.

Utility

466.

REIMBURSABLES:

467.

COMPLIANCE AND REFERENCE PUBLICATIONS:

467.1.

Compliance Publications and Documentation (Mandatory)

477.2.

Reference Publications (Advisory)

V.

Appendix Attachment 1A1 – Facility Responsibility List

Attachment 1A2A – Property/Equipment Responsibility List

Attachment 1A2B – Crane & Hoist Responsibility List

Attachment 1A2C – Pressure Vessel Responsibility List

Attachment 1A2D – Elevator Responsibility List

Attachment 1B – Government Furnished Property

Attachment 1C – Contract Data Requirements List/Data Item Descriptions Attachment 1D – Environmental Requirements

I. Description of Services

1. INTRODUCTION

The Launch Operations Support Contract (LOSC) program objective is to provide mission infrastructure support for the Launch and Test Range System (LTRS), Western Range operations, which is designated as a Major Range and Test Facility Base (MRTFB). The goal is to ensure the high performance confidence levels required for Range support of equipment and facilities is maintained for a variety of ballistic missile, space, guided weapon, and aircraft test and evaluation missions in support of Air Force, Navy, Army, National Reconnaissance Office, Missile Defense Agency, Federal Aviation Administration, Department of Energy, Defense Advanced Research Projects, National Aeronautics & Space Administration, and a variety of commercial, allied nations, and governmental agencies.

1.1. The LOSC provides maintenance, modification, and modernization for aging facilities, property, and Western Range support equipment to ensure successful performance during tests, operations, and launch. It is the role of LOSC to have the experience, resources, and agility to support the 30th Space Wings key role in assuring access to space.

1.2. The LOSC program will satisfy requirements for a rapid, reliable, economical, and secure maintenance and operation services. Services include periodic maintenance, operation, and repair of various infrastructure, and mandatory certification, maintenance, and operations of facility property and equipment, which support critical mission requirements. The Contractor understands the dynamics of services and provides a capability to the Government which requires shifting labor and schedules to meet Government requirements.

2. SCOPE OF WORK

The scope of this contract is to provide management and support, maintenance and repair, operations, Other Services, and minor facility alteration. The Contractor shall apply the services to the Western Range launch, operation and test facilities, Pillar Point, Anderson Peak, Hawaiian sites, Vandenberg Air Force Base (VAFB), VAFB surrounding areas and their infrastructure, property, and equipment, as listed in Attachments 1A1 and 1A2A thru 1A2D. Application of the services shall ensure that the Contractor’s positive performance and shall not result in threats to health, safety, or mission accomplishment nor the risk of substantial property damage.

2.1. GENERAL

2.1.1. The Contractor shall provide all resources necessary to accomplish all tasking as set forth herein. Supplied resources shall comply with all applicable regulatory/certification requirements (including Air Force specific security clearances and other regulations). Detailed description of Contractor provided resources are outlined in Section I.3, “Supplemental Contractor Responsibilities”.

2.1.2. The Government shall provide technical direction and clarification to the Contractor as required to further define requirements. Technical direction will be in writing and will originate from the Program Manager, Contracting Officer (CO), or their appointed technical direction representative.

2.2. MAINTENANCE & REPAIR

The Contractor shall maintain and repair all Real Property (RP), Real Property Installed Equipment (RPIE), Aerospace Ground Equipment (AGE), infrastructure, and equipment [Real Property & Equipment – hereafter “P&E”] that are part of the properties listed in Attachments 1A2A thru 1A2D, unless falling under the responsibility of other service providers. Maintenance & Repair (M&R) shall be subject to all applicable regulations. The outcome of M&R is to maintain and repair the P&E within manufacturer’s operating specifications and/or design/engineering specifications over the P&E design life [hereafter “Specifications”]. Design specifications, regulations imposed by agencies, and user requirements as with manufacturer’s specifications are subject to change, and it will be the responsibility of the Contractor to manage these changes to a level consistent with industrial uniform practices. System(s) boundaries of Contractor responsibility (and equipment within these boundaries, which are not specifically called out in Attachments 1A2A thru 1A2D, i.e. Cathodic Protection, Electrical, Fire Alarm/Detection, Fire Suppression, Fuel, Grounding, Infrastructure, Mechanical, Security, Structural, Waste, Water, etc.) are defined in Section IV.2 Definitions and IV.5 Property and Equipment.

2.2.1. M&R includes maintenance, repair, replacement, engineering, inspecting, testing, and certifying.

2.2.2. The Contractor shall perform various P&E level of M&R. The M&R level is either active or inactive as indicated in the Property/Equipment Responsibility List. P&E identified in an active status receives full M&R. The inactive P&E will be left in an as-is-condition. If the Government requires the activation of a P&E in inactive status which needs repair or minor facility alteration, a Task Assignment or Contract Work Request will be issued to the Contractor. The Contractor’s effort for P&E identified as “others” is limited to services as required by the various agreements listed herein and the delivery and return of Government-owned certified test weights for load tests of cranes, hoists, and lifting devices in support of their proof-load, inspection, and certification requirements.

2.2.3. Where Contractor responsible P&E is intermingled with facilities, infrastructure, property, and equipment that is the responsibility of others, the Contractor shall abide with all written maintenance agreements approved by the Government or agreed upon with other contractors residing or using these Government properties The Contractor shall interface (effectively coordinate, interact, communicate) with other contractors and government agencies who provide other maintenance and operation services as required. Contracts include the following:

1) Western Range Operations Communications and Information contract which provides maintenance and operation services to communication and information equipment,

2) other launch contractors which provide maintenance and operation services to launch equipment, property, and facilities,

3) energy saving contractors which provide maintenance on their installed energy saving devices,

4) Civil Engineer which provides services for facilities on Vandenberg Air Force Base, for roads and paving, fuel delivery, ground maintenance and vegetation removal at selected areas and sites, and application of exterior protective coating on RP buildings,

5) un-interruptible power supply (UPS) contractor which provides maintenance on selected three phase UPS, and

6) other similar contracts.

If there is an increase or decrease in costs which exceed $25K per year as a result of any maintenance agreement or interface changes, the Contractor shall inform the CO within 30 days.

2.2.4. Maintenance: The level of effort required to preserve P&E within Specifications.

2.2.4.1. Reliability Centered Maintenance Program: The Contractor shall develop, implement, and maintain a Reliability Centered Maintenance/Monitoring (RCM) program to improve reliability of P&E. The RCM program shall be based on a sound equipment specific maintenance/monitoring plan and weigh the cost and mission impact benefits of run to failure, preventative maintenance (PM), predictive maintenance (PdM), and reliability centered monitoring . (CDRL A025) The RCM program shall be capable of reporting the quantified status of equipment condition and relative facility condition (Condition Code) for the review of general confidence of critical P&E functionality.

2.2.4.1.1. RCM equipment condition identification codes shall determine condition (within or without Specifications) and any utilization or user changes and be able to identify unique and problematic subsystems or facilities’ equipment sub components. The RCM tracking system shall including unique identification markings for equipment that is repaired or replaced, and or as necessary. Condition assessments shall also be used to determine a predicted equipment life cycle that can be used as a cost model input to aid the Government efforts in the conducting “what if drills” and engineering forecasting estimates. The Contractor shall submit Equipment Readiness Reports indicating equipment level condition. (CDRL A002) Equipment categories shall be strategically created to capture groups of equipment by specific function for trending purposes.

2.2.4.2. Corrosion Control (CC): The Contractor shall inspect all RP, RPIE, AGE and selected equipment and infrastructure identified in Attachments 1A2A thru 1A2D, and prepare a corrosion control annual work plan derived from quarterly inspections and customer interviews/requirements. The total hours shall not be exceeded without Program Manager pre-approval. Task Assignments may be issued, with the mutual agreement of the Contractor, for work on RP, RPIE, AGE and selected equipment and infrastructures not identified in appendices Attachments 1A2A thru 1A2D.

2.2.4.3. Corrosion Prevention and Control Report: For Attachments 1A2A thru 1A2D, the Contractor shall provide a report identifying specifics of P&E (both ferrous and non-ferrous) requiring corrosion control (such as surfaces/parts/areas). The report shall provide both findings and recommendation on how to correct the corrosion. The plan shall state the Job Order Number associated with the task and estimated hours for completion. In consultation with the Program Manager and customer, the Contractor will prioritize/schedule in the Inspection Report the recommendations for corrosion control in descending order based on criticality and mission impact. (CDRL A001)

2.2.4.4. Corrosion control shall be in accordance with all applicable health, environmental and safety standards, the Society for Protective Coatings (SSPC), the National Association of Corrosion Engineers (NACE), and the American Society of Testing and Materials standards. The corrosion control effort includes: application of protective coating on ferrous and non-ferrous P&E; replacement and/or repair of the ablative coating, blast and heat resistant coating on launch transporters, flame buckets, and auxiliary equipment after each launch. The Contractor shall obtain Program Manager and customer prior approval on the type of ablative coating used.

2.2.4.5. The Contractor shall perform necessary vegetation removal (e.g. mowing) and earth moving services within defined boundaries of fenced P&E, towers (e.g. weather towers, Meteorological Data Acquisition Terminal huts, wind profilers, and Advanced Lightning Direction Finders), facilities, structures, fences, and roads to ensure they are not damaged or covered up and have the proper firebreak and wildfire control.

2.2.4.6. The Contractor shall perform annual inspection of roof/roofing integrity and document any deficiencies to CE on an industry standard roofing inspection reporting format. Inspection reports shall be documented and incorporated into CDRL A003 (Ref. I.2.2.6.4). The Contractor shall also perform yearly gutter cleaning.

2.2.4.7. The Contractor shall also provide response to mitigate leaking roofs as part of the Work Priority Classifications (Ref. I.2.2.4.12), providing Visqueen and sand bag repairs, but shall not perform any tarring of roofs or building penetrations without prior approval from CE.

2.2.4.8. The Contractor shall run generators and test switchgear at least monthly and assure that generator fuel tanks have adequate fuel for operation. Generators shall be tested under load IAW AFI 32-1063 and the Contractor shall develop and maintain a refueling plan IAW AFI 32-1063, para 1.8.8.

2.2.4.9. The Contractor shall inspect and provide preventative maintenance to roll up, hangar, and garage doors and their mechanisms on a yearly basis at a minimum.

2.2.4.10. Specific Demarcation Responsibilities for GMD/MDA (Ground-Based Midcourse Defense/ Missile Defense Agency) Facilities: For the following list of facilities, specific demarcations are identified in the Attachment 1A2A, Equipment List, and additional responsibilities as identified in subparagraphs below shall apply.

2.2.4.10.1. The Contractor shall also be responsible for the following at the facilities listed in I.2.2.4.10, and is still subject to systems boundaries definitions as described in Section I.2.2.

· Yearly fire extinguisher certification,

· Grounds maintenance, to include parking area and adjacent pavement,

· Foliage removal (i.e. mowing) inside the 30 foot security perimeter on the outside of the security fence,

· Door closures and hardware, including locks and keys,

· Building shell, structural, flooring, ceiling and roof maintenance, and exterior and interior walls.

· Corrosion control to include all exterior panels, enclosures, and card readers.

2.2.4.10.2. The Contractor shall plan for and coordinate access to facilities for preventative maintenance checks and services by presenting a schedule and coordinating with the facility manager and the Government Site Scheduler at least six months in advance for access.

2.2.4.10.3. Contractor’s personnel will be badged to enter GMD/MDA facilities IAW AFI 31-101 and all supplements there to. (Reference I.5.6)

2.2.4.10.4. The Contractor shall develop, implement and maintain the GMD Quality program at the Prime Contractor and for all mission critical suppliers in compliance with MDA-QS-001-MAP, MDA Assurance Provisions.

2.2.4.10.5. The contractor shall participate and provide project support for any contract required Facility Repair and/or Renovation. Contractor shall assist with configuration management with project work plans provided to the Government Lead Facility Engineer for review by the appropriate directorates within GMD. The Contractor shall provide assistance in project management. When applicable the Contractor shall upon project completion; update facility drawings and documentation.

2.2.4.10.6. Baseline Configuration Management: The Contractor shall identify and provide recommendations for updates to GMD documentation and drawings. The Contractor shall control the operational baseline through the following tasks:

a. Maintain the requirements baseline and publish updates as validated changes are approved through the configuration control process

b. Maintain the internal (System) and external (BMDS) interface baseline and publish updates as validated changes are approved through the configuration control process

c. Perform studies for opportunities for technology insertion to maintain or enhance facility system capability or reduce ownership cost

d. Conduct verification and validation whenever changes are implemented in the facility or facility operational system(s).

e.

Manage a document control system as the central repository and archive for specifications, procedures, technical data and manuals, and facility and facility equipment drawings. Documents shall be maintained in an electronic format mutually agreed to with the Government. Copies of revisions shall be provided to the Government when updated, and copies of older versions shall be delivered upon request by the PCO or COTR .

2.2.4.10.7. Where required by UFC, Code or Regulation, the Contractor shall conduct and perform inspection, test and certification of utilities systems; fire, lightning protection, facilities grounding systems, water, gas waste and electrical systems and HEMP systems to the standards as prescribed and provide the documentation to 30th CES, MDA/DPWF-V and the respective Facilities Manager.

2.2.4.10.8. Contractor shall submit all AF Form 1219s or other forms/formats used to the MDA/DPWF-V Facilities Engineer for approval/acceptance before any WOs are written and/or expensed. (Ref. I.2.2.6.1)

2.2.4.10.9. Contractor must have proficiency to maintain the DDC systems and associated computer systems (PCs, keyboard, mouse and monitor or laptops) controlling HVAC systems in all MDA facilities. The proficiency will include the ability to make software/coding changes, generate trend tracking, trouble shoot/repair/replace sensors and controls, change sequence of operation as may be required and maintain/update documentation in paper and electronic format

2.2.4.10.10. Mandatory Meeting and Coordination

a. Contractor is to attend, participate and provide written input to the weekly Vandenberg Site Facilities Working Group meetings (V-SFWG )

b. Design Charette and design reviews

c. Once a week BOSWAM scheduling Meeting

d. Management team will maintain secret clearances

2.2.4.10.11. The Contractor shall provide an electronic system which tracks all GMD facilities Work Orders and Task Assignment work. The contractor shall make at least a weekly delivery of the current work order status to the government in a mutually agreed upon format. (CDRL A026)

2.2.4.10.12. Work Order Project Transition: If a repair work determined to exceed the allowable value of a repair, then the contractor will:

a. Notify the MDA/DFWF-V Facility Engineer, explain the situation and make a recommendation for the path ahead.

b. If it is determined that the repair is to be accomplished as Minor Facility Alteration/Modification type project, the Contractor will immediately close out the existing Work Order with a remark to the effect that the repair work is being transitioned to project type work, open a new work order in which will be tracked the 332 and TA development coordination processing followed by detailed project status and actions through the completion of the project. The Contractor is responsible for accomplishing the initiation and coordination of all 332 and TA actions.

2.2.4.10.13. Contractor will report at least weekly repair data and costs by facility to the DPWF Lead Facility Engineer. (CDRL A026) Upon termination of the contract all facilities repair data will be turned over to 30th CES / MDA.

2.2.4.10.14. Work Order Submittal and Acceptance Notification

2.2.4.10.14.1. Submittal

a. MDA will submit telephonic work order requests normally through the Vandenberg Operations Support Center (VOSC) located within room 15, Bldg 1768.

b. The exceptions are that work order requests for MDA may, as circumstances require, be submitted directly to the Contractor or 30th CES by the following:

(1) MDA/DFWF-V representative

(2) 30th CES Customer Service on behalf of MDA

c. The Submitter will provide the following information as a minimum but will add to the listing additional information fields as the Contractor may require:

(1) Name of Caller

(2) Contact phone number

(3) Organization

(4) E-mail address

(5) Facility/site number/description, i. e., Bldg 1768, 980, RIDT (Bldg 1914), etc.

(6) Location within the facility/site where the problem exists

(7) Description of problem

(8) Priority for the work request (Emergency or Urgent [Note that Routine DSW requests are to be called in only by assigned MDA/GMD/OSG-V Facilities Engineer or Boeing Facilities Representative] and if there is a question the VOSC representative will contact the MDA/GMD/OSG-V Facilities Engineer or his/her representative).

(9) Name of person with technical knowledge of the facility/site problem if not the call

(10) Phone number of person with technical knowledge

(11) Organization of person with technical knowledge

(12) Other DSW Requester provided information or comments

(13) Name of person receiving DSW call from the VOSC

(14) Assigned DSW number

(15) When the 30th CES responder(s) may be expected to be on site.

(16) Date and Time of call to 30th CES

(17) Other VOSC Representative Comments

2.2.4.10.14.2. Acknowledgement

a.

The Contractor upon receipt of a MDA Work Order Request is to respond with and electronic acknowledgement that is to include the:

(1) Assigned Work Order number

(2) Preliminary Priority

(3) Estimated response date and time

(4) Restatement of the work request description b.

The electronic response is to be sent to the following (MDA is responsible for providing and updating e-mail address and phone numbers for the following positions :

(1) MDA/DWF-V Facility Engineer

(2) VOSC Watch Officer

(3) Building Facility Manager

(4) Boeing or other MDA contractor Facility Engineer

2.2.4.10.15. Work Order Reporting

2.2.4.10.15.1. Reporting

a.

Provide electronic access to work tracking system along with report generation. Access must be through the MDA fire wall. (CDRL A026) b.

At least weekly MS Excel reports that can be sorted as necessary for subsequent reporting by MDA. Reports to contain as a minimum the following information:

(1) Work Order Number (WO)

(2) Building/Facility Number

(3) Description of up to 100 characters

(4) Type of WO

(5) WO Status Code

(6) Shop

(7) Requested date

(8) Requested completion date

(9) Start Date

(10) Completion date

(11) Requestor’s name

(12) Work order tech comments to close out comments.

2.2.4.10.15.2. Opening and Closing of Work Orders:

a.

A Work order is to remain open until the work has been completed or terminated for as non-requirement.

b.

Work Orders will not be closed because of the lack of material, access or available personnel.

c.

Work Order status and remarks will explain the delay in completion of a work order.

2.2.4.11. Repair: The level of effort necessary to return out of Specification P&E to within Specification. A Task Assignment chargeable to the Reimbursable Contract Line Item Number (CLIN) will be issued for repair required for the following instances:

a) for damages to P&E caused by others or

b) repairs necessary to restore P&E that has exceeded its expected design life.

Task Assignment chargeable to the Other Service (Ref. I.2.4) CLIN will be issued for a P&E repair requiring both craftsman time and material costs exceeding $5K.

2.2.4.12. Work Priority Classification: The Contractor shall prioritize and accomplish repairs and or corrective actions as Emergency, Urgent, or Routine. If the work priority classifications are changed, the Contractor shall notify the Program Manager, Facility Manager, and the Government organizational representative. The Facility Manager or Designated Government representative may reclassify work and change completion times as necessary. The Contractor shall classify, document, and prioritize all requirements in the Contractor Computerized Management System (CCMS) and Civil Engineer database (e.g. Interim Work Information Management System (IWIMS)) within one business hour for emergencies and within one business day for all other work.

2.2.5.1.1 Emergency: Conditions imminently detrimental to the mission; situations that are currently reducing base operational effectiveness; an existing fire, health, or safety hazard; imminent substantial loss or damage to Government property; or similar situations. Response time - within two hours from receipt of call.

2.2.5.1.2 Urgent: Conditions foreseeable as detrimental to the mission and/or base operations; foreseeable fire, health, or safety hazards; or where there is foreseeable substantial loss/damage to Government property. Response time - within two work days.

2.2.5.1.3 Routine: All other situations requiring repair work not identified in the Emergency or Urgent priority classification. Response time - within 30 work days.

2.2.5. Engineering: The Contractor shall provide all engineering services necessary to support all work within the scope of this contract, to insure operability and maintainability of P&E, or the return of P&E to within Specification.

2.2.6. Inspections/Testing/Certification: The Contractor shall inspect at least annually (or more frequently as required or agreed upon) all P&E to determine condition (within or without Specifications) and any utilization or user changes. Inspection includes P&E and any cranes, hoists, elevators and pressure vessels maintained by others in facilities listed in Attachments 1A2A thru 1A2D. (CDRL A002)

2.2.6.1. The Contractor shall perform periodic facility maintenance inspections with the individual Facility Managers to identify maintenance and corrective action requirements using a process similar to Civil Engineer’s AF Form 1219 process.

2.2.6.2. The Contractor shall perform, where required by any regulation, certification of active P&E.

2.2.6.3. "Danger" Tag Log: The Contractor shall "Danger" tag any P&E that cannot meet certification requirements, following OSHA tag-out procedures, and notify the Program Manager and the Wing Safety Office (30 SW/SEAL) via e-mail within two workdays from the finding. In the case that the “Danger” Tagging carries mission or life safety implications, or immediate hazards to personnel in the work area, notification will be within 24 hours.

2.2.6.4. The Contractor shall prepare and submit a report for each P&E requiring testing, recertification, or certification. (CDRL A003)

2.2.6.5. The Contractor shall attend quarterly inspections and testing of all Vandenberg Electronic Security System (VESS) components with the 30 Security Force Squadron (30 SFS) representative to identify P&E requiring M&R, when invited by 30 RMS and/or WROCI contract managers.

2.2.6.6. Cranes and Hoists

2.2.6.6.1. The Contractor shall perform periodic inspections and functional validations, testing, and certification of cranes and hoists according to all applicable ANSI Standards, Air Force Space Command Manual (AFSPCMAN) 91-710 Volumes 3, 5 & 6, AFOSH 91-46, AFOSH 91-501 (to be replaced by AFI 91-203), CFR 29 1910 and 1926, State of California General Industry Safety Orders for Cranes & Hoists, and National Fire Protection Association Standard 70. Inspections, testing, validations and certifications shall be documented and incorporated as attachments into CDRL A003 (Ref. I.2.2.6.4).

2.2.6.6.2. The Contractor will prepare procedures for crane testing or certification in accordance with AFSPCMAN 91-710, Volume 6, Attachment 2. Procedures used during certification testing will require approval by Wing Safety (30 SW/SEAL) prior to use. All crane certification reports will be provided to the Wing Safety Office (30 SW/SEAL).

2.2.6.6.3. Cranes and hoist inspections shall be accomplished according to the inspection frequency identified by each crane’s comprehensive maintenance plan and/or AFSPCMAN 91-710, AFOSH 91-46, and AFOSH 91-501 (to be replaced by AFI 91-203), whichever is more stringent.

2.2.6.6.4. The Contractor shall perform non-destructive inspection (NDI) of hooks by an approved method at least annually and shall inspect handling fixtures and devices in accordance with all applicable ANSI standards, OSHA, AFOSH, and AFSCMAN 91-710. Inspections and testing shall be documented and incorporated as attachments into CDRL A003 (Ref. I.2.2.6.4).

2.2.6.6.5. Cranes and hoists located south of Honda Ridge Road on VAFB require the use of the California Department of Industrial Relations Form IS-162, NOTICE OF CRANE SAFETY DEFICIENCIES. Cranes and hoists north of Honda Ridge Road on VAFB may use any recognized form containing the same information as IS-162.

2.2.6.6.6. The Contractor shall label cranes and hoists with identification numbers and marking according to Air Force Space Manual (AFSPCMAN 91-710).

2.2.6.7. Pressure Vessels

2.2.6.7.1. The Contractor shall perform non-destructive inspection (NDI) on “Active” or “Caretaker” status pressure vessels requiring NDI by a Level II Inspector or above, qualified and certified in accordance with the American Society of Non-Destructive Testing, Non-Destructive Testing Recommended Practice, SNT-TC-1A, or under an American Petroleum Institute 510 certification. Inspections and testing shall be documented and incorporated as attachments into CDRL A003 (Ref. I.2.2.6.4).

2.2.6.7.2. The Contractor shall test and recertify pressure vessels IAW the AFSCMAN 91-710 Volumes 3 and 6, using recommended practices per NBIC/NB-23 and ASME Boiler & Pressure Vessel Code latest edition. Recertifications shall be documented and incorporated as attachments into CDRL A003 (Ref. I.2.2.6.4).

2.2.6.7.3. The Contractor shall test and inspect boilers and fired pressure vessels (if required) per selected sections of AFI 32-1068 (Ref. IV.7.1) and jurisdictional permits to operate. Inspections and testing shall be documented and incorporated into CDRL A003 (Ref. I.2.2.6.4).

2.2.6.7.4. The Contractor shall label pressure vessels with identification numbers and marking according to Air Force Space Manual (AFSPCMAN 91-710).

2.2.6.8. Elevators

2.2.6.8.1. The Contractor shall test, inspect and certify, maintain, and repair all elevators IAW the AFSCMAN 91-710 Volume 5, Chap 4 and applicable ANSI standards. Inspections and testing shall be documented and incorporated as attachments into CDRL A003 (Ref. I.2.2.6.4).

2.2.6.8.2. The Contractor shall maintain a work schedule outlining the preventive maintenance to be performed during the performance of the contract. The work schedule must describe which work efforts are required by the manufacturer, AFSCMAN 91-710, ANSI, or the Contractor.

2.2.6.9. Subcontracted Efforts and Cost Reduction Opportunities

2.2.6.9.1. The Contractor shall seek, promote and sustain effective subcontract and supplier competition throughout the course of the contract.

2.2.6.9.2. The Contractor shall identify and implement operational and system efficiencies so as to target cost reduction opportunities throughout the life of the contract. Cost reduction efforts shall be implemented with the Contractor and subcontractors or suppliers.

2.3. OPERATIONS

Operations include activating, monitoring, configuring, or standing by on-site to run equipment such that Operation Directive/user requirements, processing and launching operations, and technical and operational support for operating equipment are met.

2.3.1. South Vandenberg Power Plant (SVPP): After notification by the Program Manager or Designated Government Representative, the Contractor shall respond on site to perform and sustain power plant operations for the designated period required or until directed otherwise.

2.3.1.1. Operations support can start and stop at any time of the day or year, 24 hours a day, 7 days a week. Operations can last from a few hours to many weeks, with long dry periods between support. Support is subject to the number of launches within a fiscal year and when operations begin and end. The estimated operation hours for each pre to post-launch periods will vary each year.

2.3.1.2. Operation support is required during all launch periods, during Civil Engineer DCC and 30 SW Command Post response to natural disasters or exercises, and as required by the Program Manager or Designated Government Representative. The Contractor shall operate and ensure uninterrupted operational availability of the SVPP and associated systems within Specifications and according to any applicable requirements (Ref. IV.7).

2.3.1.3. The Contractor shall comply with all operational requirements of the Permit-to-Operate (PTO) issued by the Santa Barbara County Air Pollution Control District (SBCAPCD) with no violations. The Contractor shall configure or reconfigure the SVPP to fulfill operational requirements. Prior to commencing work, Contractor shall coordinate all configuration changes with the Program Manager or representative.

2.3.1.4. The SVPP is a permitted power plant. The Contractor shall submit information in accordance with SBCAPCD and California Regional Water Quality Control Board reporting requirements. The Contractor shall provide SVPP operation data. (CDRL A004, A005, A006)

2.3.2. Launch Support: After notification by the Program Manager or Designated Government Representative, the Contractor shall report on-site to provide operations, emergency corrective actions, and/or standby support during pre-launch, launch, and post-launch operations. The launch support may include one of the following:

· Launch Mode

· Countdown Standby

· L-1 Day Checkpoint

· Campaign Milestone (Wet Dress, Space craft mate, or other).

2.3.2.1. Launch support is required for the following P&E:

1) building 8510 generators and Heating, Ventilation, & Air Condition (HVAC) in support of launches controlled from this building, including the 100KW generator (i.e. Government or rental) installation into building 8510 electrical system to support communication system loads during power outages at building 8510 lasting for more than one hour,

2) generators and HVAC at various Communication Transmitter sites,

3) Attachments 1A2A thru 1A2D P&E responsible-for at SLC-3 and 6 to support launches from SLC-3 and 6,

4) Attachments 1A2A thru 1A2D P&E responsible-for at building 7000,

5) standby support in the Civil Engineer Disaster Control Center (DCC) to perform emergency corrective action for various facilities, property, and equipment,

6) SVPP, and

7) SLC-3 to walk down and inspect 4,200 Lft. of fencing, gates, and light poles (pre-launch and post-launch).

8) SLC-6 to walk down and inspect 7,000 Lft. of fencing, gates, and light poles (pre-launch and post-launch).

2.4. OTHER SERVICES:

The Contractor shall perform the following Other Services deemed necessary to support this contract upon receipt of a Task Assignment. These Other Services do not include services the Contractor provides as “support for others” (Ref. I.2.2) in order to meet M&R, Operations, and Support contract performance requirements.

2.4.1. If required under Other Services and upon receipt of a Task Assignment, the Contractor shall perform corrosion control services for Attachments 1A2A thru 1A2D P&E and other customers on VAFB (Ref. I.2.2.4.2).

2.4.2. The Contractor shall perform repair, replacement, testing, and/or certification efforts to return a caretaker or inactive P&E to active status, as required by Specifications.

2.4.3. The Contractor shall perform corrective maintenance requiring both craftsman time and material cost exceeding $5K per P&E.

2.5. MINOR FACILITY ALTERATION:

The Contractor shall perform minor alteration including upgrade, demolition, and renovation to facilities in support of mission requirements when required by the Government, upon receipt of a Task Assignment or Contract Work Request.

2.6. SUPPORT:

The Contractor shall provide adequate management and administrative resources to ensure that all planning, scheduling, and execution of the tasks identified in this PWS are accomplished and are within the expected performance thresholds identified in the Service Delivery Summary.

2.6.1. Attendance and Representation: The Contractor shall attend meetings to understand M&R work requirements, obtain and provide scheduling information (e.g. daily integrated meetings, weekly Civil Engineer scheduler meeting), coordinated work effort status, provide work effort information (e.g. Facility and Vandenberg Security Working Groups, Work Request Review Panel), and review and discuss financial information.

2.6.2. Coordination: The Contractor shall schedule all work with the customer (i.e. Facility Manager, occupants, organizational Facility Manager) and other affected parties (e.g. Civil Engineer, Environmental, Safety, Fire, Security Force, utility companies, contractors) to ensure coordination is obtained prior to start of any work activity.

2.6.2.1. The Contractor shall schedule and obtain approval to begin any work effort through all associated responsible parties (e.g. Civil Engineer, Facility Manager, operation centers) for work associated with the Launch and Western Range facilities. The Contractor shall notify the Program Manager via e-mail when access could not be obtained to facilities because the customer failed to be available at the scheduled time.

2.6.2.2. The Contractor shall coordinate with the responsible Facility Manager and ensure an approved Work Request form has been processed (when applicable) before initiating real property, facility alterations, or modifications. Any modification that may change the safe working configuration of the facility shall be routed through Wing Safety for review.

2.6.2.3. The Contractor shall provide 24 hour notice to the Facility Manger prior to the start of work and the Contractor shall also perform a walk down of work area with the Facility Manager prior to departing the facility, upon the completion of work request orders.

2.6.2.4. Utility Identification and Marking: The Contractor shall identify all utilities (water, sewage, electrical, natural gas, and communications) and mark prior to the commencement of the Contractor’s own work efforts (e.g. repair, digging) based on available Civil Engineer drawings, processed Work Request information, Contractor’s documentation, and knowledge. In addition, all mechanical distribution lines and electrical panels shall be properly marked according to directives in force at the time of the work.

2.6.2.5. Welding, Cutting & Brazing Permits (AF Form 592): The Contractor shall coordinate and obtain Hot Work permits through the Technical Services Section of the Fire Protection Office or the fire authority having jurisdiction, prior to the commencement of any hot work.

2.6.2.6. The Contractor will coordinate all installation, repair, and similar activities affecting VESS integrity and operability with the 30 SFS Senior Non-Commissioned Officer In Charge or the 30 SFS Physical Security Non-Commissioned Officer In Charge.

2.6.2.7. The Contractor shall identify all potential environmental hazards related to any work requirements and obtain proper coordination with VAFB environmental office prior to start of work.

2.6.2.8. The Contractor shall notify the appropriate Government personnel five business days prior to commencement of work for scheduled work involving disruption of any of the following:

· traffic flow,

· station utility services,

· fire alarms,

· fire sprinklers,

· intrusion alarm systems,

· oxygen (O2) deficiency sensing systems,

· nitrogen (GN2) purging systems,

· hazardous area warning light systems,

· emergency lighting systems,

· UPS systems,

· lightning protection systems,

· fuel or propellant systems,

· routine activities of the installation,

· work involving digging operations,

· and similar systems or operations.

Wing Safety (30 SW/SEAL) shall be notified of any disruptions involving the removal of Safety devices within launch-vehicle processing facilities or launch facilities.

2.6.2.9. Out-Of Service: The Contractor shall notify the Facility Manager 48 hours prior to removing any P&E from service. In the event that any item will be removed from service for more than 48-hours, the Program Manager shall be notified via e-mail. The Contractor shall notify VAFB Fire Department at the time any fire detection/suppression system is removed from service.

2.6.2.10. Scheduled Road/Area Closure: The Contractor shall schedule road and area closures for M&R so as not to delay mission schedules. Prior to commencement of work, the Contractor shall coordinate with Civil Engineer DCC, the customers, and Facility Managers who use the road for access or have P&E adjacent to the road. Roads and access shall not be closed in a way that prevents access by emergency vehicles and equipment.

2.6.2.11. Outages/Work Clearance: If work requires scheduled or unscheduled interruptions, disconnect or cut-off of any utility to, or within the facility, or that a facility be vacated, the Contractor shall take action to:

(1) notify the Facility Manager, affected customers, and the Program Manager verbally and by e-mail upon knowledge of a need for an outage,

(2) prevent damage to customer equipment, and

(3) minimize disruption of the activity's operation.

2.6.2.12. Outage Coordination: The Contractor shall schedule and coordinate outages (e.g. electricity, water, gas, sanitary sewer, chilled water, or alarms) with the respective Facility Manager to ensure that critical processes or missions are not disrupted or security compromised. The Contractor shall also notify other appropriate Civil Engineer offices prior to commencement of work by processing a Work Request (e.g. AF Form 332) according to current VAFB established procedures and receive clearance before starting work.

2.6.2.13. Mission Impact: The Contractor shall reschedule as agreeable to all parties when critical outages cannot be approved due to conflicting mission requirements. Outages that are delayed for a period greater than 30 days shall be reviewed monthly by the Contractor. A risk analysis shall be performed with recommendations presented to the Program Manager via e-mail within a week after knowledge of impact.

2.6.2.14. Emergency Outage: The Contractor shall contact the Program Manager and affected customers to execute an emergency, unscheduled outage upon knowledge of need. When approval cannot be obtained, and life/health, or substantial property are in danger unless the outage occurs, the Contractor shall notify the Civil Engineer DCC of their intent to proceed, document the situation, and inform the Program Manager at the earliest possible time verbally and by e-mail.

2.6.3. Cost Estimating: The Contractor shall provide Rough Order of Magnitude (ROM) estimated cost and schedule for Contract Work Requests, Task Assignments, damaged P&E, and P&E utilization change impacts.

2.6.3.1. The Contractor shall provide a ROM estimated cost within three weeks, for any Contractor recommended work that is above the Range Support CLIN level of effort as a result of findings discovered while performing maintenance, operations, inspection, testing, or certification efforts.

2.6.3.2. The Contractor shall provide a ROM estimated cost within three weeks to correct the damage as reported in the Damage Report.

2.6.3.3. The Contractor shall provide a ROM estimated cost within three weeks of discovery for any cost impact based on utilization change to building/facilities or P&E (e.g. stop/start using crane, new tenant with different M&R requirements).

2.6.4. Data Input and database maintenance: The Contractor shall input all contract work effort and documentation data into the Contractor Computerized Management System (CCMS). The CCMS collects, tracks, schedules resources, and processes all work requirements and data. The Contractor shall input and update only RP and RPIE work effort information into the Civil Engineer’s IWIMS, or its latest version, directly and through the Civil Engineer Production Management Unit (PMU) for VAFB assigned installations.

2.6.4.1. CCMS: The Contractor shall use an industry recognized enterprise reporting system as the sole integrated work and financial management database system. The CCMS shall capture all P&E management and support, M&R, operations, Other Services, minor facility alteration information, work effort, and financial data. The CCMS must have the capability of being accessed (at least two seats) through the Program Manager’s office (or computer system). The system shall be capable of storing and processing data (e.g. labor and material cost, future and past work schedule) for all P&E and M&R management functions. Tracking will be to the equipment level in each facility. Tracking schedules shall be in Microsoft Project or similar software, compatible with the Program Office’s computer system. The M&R management functions typically include the following and similar items:

· Work accomplished by Job Order Number (JON)

· Down Time and Delays

· Funding Status

· Job Estimating

· P&E Inventory

· P&E History

· P&E Inspection and Assessment

· Reliability Centered Maintenance

· Preventive Maintenance

· In-Service Inspection (ISI) Plan

· Lock Out/Tag Out Status

· Work Input Control

· Work Scheduling and Tracking

· Material Management

· Protective Coating

· Detailed parts breakdown lists from drop down menus

· Two year out estimated date to replace P&E due to age, wear, condition, deterioration, or other condition

· Capability to monitor asset state of health, configuration, and overall readiness.

CMMS data, entity identification, descriptions, and Work Orders shall be created using a developed Standard Operating Procedure (SOP) that standardizes data entry. Work order comments should include, at a minimum, problem definition, root cause, problem correction, and recommendations to mitigate a recurrence. To ensure data integrity and accurate sorting, data entry standards need to be established through the SOP for all key CMMS information, ensuring proper and consistently entered data. The Contractor shall submit the accumulated CCMS data as part of standard reporting practices. (CDRL A007)

2.6.4.2. Interim Work Information Management System (IWIMS): IWIMS is a Civil Engineer CCMS. The Contractor shall update IWIMS providing both approved and completed schedules of ongoing work efforts for RP and RPIE (minimum of three months out). The Contractor shall utilize IWIMS via a Contractor provided computer in the designated primary Administrative Space (Bldg. 861, located at VAFB).

NOTE: The IWIMS utilization requirement is limited to similar actions performed by personnel manning the Civil Engineer Zones (i.e. create, schedule, update, and close Recurring Work Program, Direct Schedule Work, and planned work in IWIMS; report scheduled and closed In-Service Work Program to PMU). The Contractor shall use IWIMS to coordinate efforts so as not to duplicate or conflict with other parties’ scheduled actions. IWIMS information entered for ongoing efforts shall include identifiable descriptions and/or CMMS Work Order tracking numbers, to allow for matching CCMS work orders and IWIMS work orders.

The Contractor shall input actual cost data into IWIMS as follows: burdened material or subcontractor cost, actual labor hours, and comparable Government supplied labor rates.

2.6.4.3. Defects or Deficiencies: The Contractor shall record in the CCMS any defects or deficiencies identified by the Contractor that may result in risk to persons or property or mission accomplishment and notify the DCC and Program Manager via e-mail within 24 hours. All other defects or deficiencies identified by the Contractor but not corrected during scheduled maintenance shall be recorded in the CCMS within three days of completion of the scheduled maintenance.

2.6.4.4. Archive of Completed Work: The Contractor shall maintain an indexed archival system for both hard copy and electronic data generated as a result of normal work functions for future review and audit, until the end of the contract period (Ref. I.2.6.5.2). Closing a requirement in CCMS and IWIMS by entering a completion date constitutes the Contractor’s certification that the work was completed.

2.6.4.5. The Contractor shall update P&E records at the individual P&E sites (e.g. significant maintenance and/or inspection activity), the Central Library, and the CCMS with the inspection, completed certification actions, condition, and status (e.g. lock/tagged out).

2.6.5. Document and Records Maintenance: The Contractor shall accurately and continuously update and maintain contract documentation and records as part of their documentation archive. The documentation archive shall include (but is not limited to) the central data library, drawings, manuals, procedures, listings, records, warranties, and CCMS data.

2.6.5.1. As-Built Drawings: The Contractor shall provide new configuration, P&ID, electrical, wiring diagrams, or as-built drawings. These shall be included in the Central Library and referenced in the CCMS.

2.6.5.2. Central Library: The Contractor shall archive, manage and maintain accurate documentation (both hard and electronic copy) at a central database library under the performance of this contract. The archive information shall also include documentation received from the previous contractor.