LMR_PWS.doc

DOC document 277 KB Posted

Attached to
LMR Sources Sought Federal contract opportunity
Solicitation number
FA2517-15-R-9003
Issued by
Department of the Air Force Space Command

View the file

Other files for this federal contract opportunity

Other files attached to LMR Sources Sought, newest first.
File Type Posted
LMR_J A_Redacted.pdf PDF

On GovTribe

Work with this file on GovTribe

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

Text version

Performance Work Statement For Headquarters Air Force Space Command (HQ AFSPC) Enterprise Land Mobile Radio (ELMR)

Operations & Maintenance (O&M) Contract

17 November 2014

AFSPC/A6CIX

Peterson Air Force Base, Colorado

TABLE OF CONTENTS

1.0 DESCRIPTION OF SERVICES

PAGE

1.1 Organization Being Supported

1.2 Mission

1.3 Overview of Services Required

2.0 SPECIFIC TASKS

2.1. Contractor Responsibilities

3-8

3.0 SERVICE SUMMARY

3.0 Service Summary

8-10

4.0 GOVERNMENT FURNISHED PROPERTY AND SERVICES

4.1. Government Furnished Property (GFP)

4.2. Proprietary Data

4.3. Product Ownership

5.0 GENERAL INFORMATION

5.1 ELMR (ASTRO 25) Training Policy Guidance

10-11

5.2 Hours of Operation

5.3 Inherently Governmental

5.4 Representation of Government

5.5 Contractor Identification

5.6 Security

5.7 Access to Government Property and Facilities

12-13

5.8 Management

5.9 Materials and Other Direct Costs (ODCs)

5.10. Purchase of IT Hardware/Software Products Through AFWay

5.11 Deliverables

13-14

SECTION 6 - APPENDICES

Appendix A – Acronyms

Appendix B – Monthly Maintenance Report

1.0 DESCRIPTION OF SERVICES

1.1 ORGANIZATION BEING SUPPORTED: Headquarters Air Force Space Command (HQ AFSPC), Subordinate Commands, and the Air Force Academy. The primary location to be HQ AFSPC, Peterson Air Force Base, Colorado Springs, CO 80914.

1.2 MISSION: Implement maintenance and sustainment for the AFSPC ELMR system to include the Zone Controller at Peterson AFB and ELMR equipment attached to the Peterson AFB Zone Controller located at Peterson AFB, Schriever AFB, Los Angeles AFB, Cheyenne Mountain Air Force Station, Vandenberg AFB, Patrick AFB, Buckley AFB, Grand Forks AFB, Malmstrom AFB, FE Warren AFB, Minot AFB, United States Air Force Academy (USAFA), Edwards AFB, Tinker AFB and Robins AFB.

1.3 OVERVIEW OF SERVICES REQUIRED: The Contractor shall provide non-personal Enterprise Land Mobile Radio (ELMR) maintenance, troubleshooting, installation, and integration support for locations identified in Table 2.1. ELMR systems listed in Table 2.1 can increase or decrease based upon new systems being added or old systems being deactivated through contract modification. Services include: maintenance of the master site zone controller, repeater equipment, dispatch consoles, base stations connected to dispatch consoles, Universal Cryptographic Module/ Key Management Facility (UCM/KMF) terminals, and associated equipment used for Over-The-Air-Rekeying (OTAR).

2.0 SPECIFIC TASKS: The Contractor shall provide all personnel, supplies, facilities, transportation, tools, materials, supervision, and other items/services (other than those designated as Government –furnished property) necessary to perform ELMR Support Services as defined in the PWS.

2.1. CONTRACTOR RESPONSIBILITIES. The Contractor shall:

2.1.1 Implement maintenance and sustainment for the AFSPC ELMR system to include the Zone Controller at Peterson AFB and LMR equipment attached to the Peterson AFB Zone Controller listed in Table 2.1.

2.1.2. Integrate all Trunking Systems into the Master Site at Peterson AFB.

2.1.3. Provide on-site ELMR network administration at the zone controller to include remote troubleshooting, software upgrade and licensing, maintenance dispatch, service restoral, and technical support Monday through Friday, 8:00am through 5:00pm MST (8/5) to include a one hour lunch break. Remote monitoring shall be provided 24 hours a day/seven days a week (24/7).

2.1.4. Provide 95 percent availability and 95 percent reliability to AFSPC ELMR network.

2.1.5. Provide centralized enterprise monitoring at Peterson AFB zone controller site. The scope of this monitoring shall include remote monitoring, remote diagnostics, contacting base Point of Contact (POC) for site-specific outage verification and maintenance coordination actions, initiate trouble tickets, and monthly Over-The-Air-Rekeying (OTAR) changing or updating encryption keys on active Air Force (AF) ELMR handsets and vehicle radios for Base ELMR Sites listed in Table 2.1. Perform maintenance, dispatch service, restoral of service and monitoring/notifications for Base ELMR Sites listed in Table 2.1. Response times and severity definitions are listed in Table 2.0 and are for per base or the Zone Controller.

2.1.6 Provide an on-site System Manager at Peterson AFB dedicated to the AFSPC network, responsible for the coordination of technical support, monitoring, and maintenance of the ASTRO 25 system. The System Manager must be qualified in ASTRO 25 technology, Project 25 technology, Advanced Encryption Standard encryption knowledge, Over-The-Air-Rekeying (OTAR) operations, dispatch console systems operations, Project 25 subscriber radios, System Fleet-mapping and applicable database operations, with a minimum of two years of experience.

2.1.7. Be responsible for troubleshooting, minor and major repair as a result of troubleshooting, and maintenance support of the Peterson AFB master site zone controller and repeater equipment, dispatch consoles, base stations connected to dispatch consoles, Universal Cryptographic Module/ Key Management Facility (UCM/KMF) terminals, Over-The-Air-Rekeying (OTAR) related equipment, and all associated infrastructure (switches, routers, gateways) connected to it located at all sites listed in Table 2.1. These responsibilities include validation of customer trouble tickets and maintenance solutions and providing maintenance -dispatch and depot-level maintenance.

2.1.8. Be responsible for coordination with each base LMR office to include interfacing directly with system users on work schedules and access issues, provide guidance and recommendations to users, and coordinate efforts preceding each phase of the project.

2.1.9 Perform annual recurring on-site inspections and periodic Preventive Maintenance Inspections (PMI) on all equipment listed in Table 2.1, in accordance with manufacture specifications, to ensure optimal operation. The contractor shall develop an annual master PMI schedule (31 Mar – 30 Mar) and submit the first year’s schedule to the COR and each Base LMR office within 5 days of contract award. This report will be delivered to the COR and each Base LMR office annually by 25 March of each subsequent year. The contractor will provide the COR a copy of all inspection reports within 15 calendar days after completion of inspection. These PMIs will ensure all equipment maintains an orderly appearance, filters cleaned as necessary, maintain sufficient spacing required for proper air flow, and ensure all connectors are tight and in good condition.

2.1.10 Unscheduled onsite maintenance shall be coordinated with the appropriate base LMR office no later than one hour prior.

2.1.11. Provide software maintenance upgrades and updates for all monitored LMR subsystems. Upgrades shall include manufacturer-approved pre-tested updates to the systems. Contractor will provide affected base LMR offices with 5 business days advance notification, when possible, of any possible disruption that may occur and describe what that disruption will be.

2.1.12 For all severity one outages the contractor shall notify via text message and coordinate via telephone call with the affected base LMR office no later than 30 minutes regardless of the time of day. For all other outages the contractor shall notify by email and text message the affected base LMR office no later than 30 minutes. For all outages the COR shall be notified by email within 30 minutes. For all outages the contractor shall provide the COR and affected base LMR office by email of the cause and repair actions within 24 hours of resolution. The contractor shall provide a monthly maintenance report to the COR listing all outage response actions performed throughout the month by the 5th calendar day of the following month in accordance with Appendix B.

Table 2.0 LMR Maintenance Response Times and Severity Levels

Remote Technical Support Response Times

SEVERITY
RESPONSE
Severity 1
Within 4 Hours from receipt of Notification 24/7, 365 days a year,
Severity 2
Within 8 Hours from receipt of Notification, Standard Business Day 8/5
Severity 3
Within next Business Day, Standard Business Day 8/5

Severity Definitions

Severity Level
Problem Types
Severity 1
Major System failure

33% of System down

33% of Site channels down

Site Environment alarms (smoke, access, temp, AC power).

This level is meant to represent a major issue that results in an unusable system, sub-system, Product, or critical features from the Customer’s perspective. No Work-around or immediate solution is available.

Severity 2
Significant System Impairment not to exceed 33% of system down

System problems presently being monitored

This level is meant to represent a moderate issue that limits a Customer's normal use of the system, sub-system, product, or major non-critical features from a customer’s perspective

Severity 3
Intermittent system issues

Information questions

Upgrades/preventative maintenance

This level is meant to represent a minor issue that does not preclude use of the system, sub-system, product, or critical features from a customer's perspective. It may also represent a cosmetic issue, including documentation errors, general usage questions, recommendations for product enhancements or modifications, and scheduled events such as preventative maintenance or product/system upgrades.

2.1.13 Adhere to any base specific weather delays, base closures or restrictions that are declared by the government through local media.

2.1.14 Provide a Quality Control Plan within 30 business days after contract award to the COR. The Contractor shall be responsible for identifying system deficiencies and/or discrepancies throughout the life of the project. A monthly report (soft copy) shall be submitted indicating progress/status and listing any deficiencies/discrepancies found and actions to correct them.

Table 2.1 AFSPC Enterprise ELMR Equipment Table by Base. The following tables are broken down for each year of the proposed contract, base year (31 Mar 15 – 30 Mar 16) plus 4 option years. Unless noted otherwise, all bases will require zone controller support (master controller operations, monitoring & dispatch services, etc.) and OTAR support for the entire 12-month period listed, however due to existing system warranties associated with purchase of new equipment (GTR-8000/MCC7500) some bases will not require O&M support until expiration of those warranties. In these cases the “Maint Repair/replc Months” is adjusted to indicate only number of months of contract O&M support required, with a corresponding note annotating those details.

Base Year (31 Mar 15 – 30 Mar 16)

BASE
Maint

Repair/Replc

Months

TRUNK

RF SITES

QUANTAR
GTR

DISP

SITES

CENTRACOM

OPS

MCC7500

OPS

PETERSON
12
1
8
0
6
13
0
SCHRIEVER
12
1
5
0
6
9
0
LOS ANGELES
12
2
8
0
2
2
0
CHEYENNE MOUNTAIN
12
2
10
0
2
4
0
VANDENBERG
115
4
26
8
8
12
0
PATRICK
12
3
0
23
9
0
14
BUCKLEY
123
1
0
10
4
0
6
GRAND FORKS
12
1
0
10
6
0
11
MALMSTROM
102
8
10
35
4
14
0
FE WARREN
102
9
15
35
9
11
14 (Note 1)
MINOT
102
12
0
53
8
0
15
USAFA
12
1
0
8
3
0
3
EDWARDS
06
4
0
25
1
0
22
TINKER
14
1
0
12
4
0
12
ROBINS
127
1
4
10
3
0
10

TOTALS

51
86
229
75
65
90

Note 1 – MCC-7500s not yet installed -- base currently working to replace current Centracom Ops with 14 new MCC-7500s – estimated completion date: 11 Jun 2015, followed by 1 year enhanced warranty

Note 2 – These bases (AFGSC) projected to terminate zone controller support by 23 Jan 2016

Note 3 – Base under warranty/does not require O&M support until 20 Nov 2016 – Until that date support limited to zone controller operations and OTAR support

Note 4 – Base under warranty/does not require O&M support until 01 Mar 2016 – Until that date support limited to zone controller operations and OTAR support Note 5 - GTR-8000s under warranty/does not require O&M support until 07 May 2015 – Until that date support limited to zone controller operations and OTAR support

Note 6 – Edwards AFB has its own separate base-level O&M contract and will not require O&M support – required contract support limited to zone controller operations and OTAR support only Note 7 – Robins AFB not yet operational; projected to stand-up on Peterson Zone Controller network effective 01 July 2015 – upon standup base under warranty/does not require O&M support for GTR-8000/MCC-7500s until 01 July 2016 – Until that date support limited to O&M support for 4 Quantar repeaters & zone controller operations and OTAR support Option Year 1 (31 Mar 16 – 30 Mar 17)

BASE
Maint

Repair/Replc

Months

TRUNK

RF SITES

QUANTAR
GTR

DISP

SITES

CENTRACOM

OPS

MCC7500

OPS

PETERSON
12
1
8
0
6
13
0
SCHRIEVER
12
1
5
0
6
9
0
LOS ANGELES
12
2
8
0
2
2
0
CHEYENNE MOUNTAIN
12
2
10
0
2
4
0
VANDENBERG
12
4
26
8
8
12
0
PATRICK
12
3
0
23
9
0
14
BUCKLEY
51
1
0
10
4
0
6
USAFA
12
1
0
8
3
0
3
EDWARDS
02
4
0
25
1
0
22
TINKER
12
1
0
12
4
0
12
ROBINS
123
1
4
10
3
0
10

TOTALS

21
61
96
48
40
67

Note 1 - Base under warranty/does not require O&M support until 20 Nov 2016 – Until that date support limited to zone controller operations and OTAR Note 2 - Edwards AFB has its own separate base-level O&M contract and will not require O&M support – required contract support limited to zone controller operations and OTAR support only

Note 3 - Base under warranty/does not require O&M support for GTR-8000/MCC-7500s until 01 Jul 2016 – Until that date support limited to O&M support for 4 Quantar repeaters & zone controller operations and OTAR support Option Year 2 (31 Mar 17 – 30 Mar 18)

BASE
Maint

Repair/Replc

Months

TRUNK

RF SITES

QUANTAR
GTR

DISP

SITES

CENTRACOM

OPS

MCC7500

OPS

PETERSON
12
1
8
0
6
13
0
SCHRIEVER
12
1
5
0
6
9
0
LOS ANGELES
12
2
8
0
2
2
0
CHEYENNE MOUNTAIN
12
2
10
0
2
4
0
VANDENBERG
12
4
26
8
8
12
0
PATRICK
12
3
0
23
9
0
14
BUCKLEY
12
1
0
10
4
0
6
USAFA
12
1
0
8
3
0
3
EDWARDS
01
4
0
25
1
0
22
TINKER
12
1
0
12
4
0
12
ROBINS
12
1
4
10
3
0
10

TOTALS

21
61
96
48
40
67

Note 1 - Edwards AFB has its own separate base-level O&M contract and will not require O&M support – required contract support limited to zone controller operations and OTAR support only Option Year 3 (31 Mar 18 – 30 Mar 19)

BASE
Maint

Repair/Replc

Months

TRUNK

RF SITES

QUANTAR
GTR

DISP

SITES

CENTRACOM

OPS

MCC7500

OPS

PETERSON
12
1
8
0
6
13
0
SCHRIEVER
12
1
5
0
6
9
0
LOS ANGELES
12
2
8
0
2
2
0
CHEYENNE MOUNTAIN
12
2
10
0
2
4
0
VANDENBERG
12
4
26
8
8
12
0
PATRICK
12
3
0
23
9
0
14
BUCKLEY
12
1
0
10
4
0
6
USAFA
12
1
0
8
3
0
3
EDWARDS
01
4
0
25
1
0
22
TINKER
12
1
0
12
4
0
12
ROBINS
12
1
4
10
3
0
10

TOTALS

21
61
96
48
40
67

Note 1 - Edwards AFB has its own separate base-level O&M contract and will not require O&M support – required contract support limited to zone controller operations and OTAR support only

Option Year 4 (31 Mar 19 – 30 Mar 20)

BASE
Maint

Repair/Replc

Months

TRUNK

RF SITES

QUANTAR
GTR

DISP

SITES

CENTRACOM

OPS

MCC7500

OPS

PETERSON
12
1
8
0
6
13
0
SCHRIEVER
12
1
5
0
6
9
0
LOS ANGELES
12
2
8
0
2
2
0
CHEYENNE MOUNTAIN
12
2
10
0
2
4
0
VANDENBERG
12
4
26
8
8
12
0
PATRICK
12
3
0
23
9
0
14
BUCKLEY
12
1
0
10
4
0
6
USAFA
12
1
0
8
3
0
3
EDWARDS
01
4
0
25
1
0
22
TINKER
12
1
0
12
4
0
12
ROBINS
12
1
4
10
3
0
10

TOTALS

21
61
96
48
40
67

Note 1 - Edwards AFB has its own separate base-level O&M contract and will not require O&M support – required contract support limited to zone controller operations and OTAR support only

3.0 SERVICE SUMMARY

Performance Objective
PWS Paragraph
Performance Threshold

Maintenance -

Maintain the master site zone controller, repeater equipment, dispatch consoles, base stations connected to dispatch consoles, UCM/KMF, and associated equipment used for Over-The-Air-Rekeying (OTAR).

2.1.4

2.1.7

2.1.9

Provide 95 percent availability and 95 percent reliability to AFSPC LMR Enterprise network on an eight hours a day/five days a week basis.

Be responsible for troubleshooting, minor and major repair as a result of troubleshooting, and maintenance support of the Peterson AFB master site zone controller and repeater equipment, dispatch consoles, base stations connected to dispatch consoles, Universal Cryptographic Module/ Key Management Facility (UCM/KMF) terminals, Over-The-Air-Rekeying (OTAR) related equipment, and all associated infrastructure (switches, routers, gateways) connected to it located at all sites listed in Table 2.1. These responsibilities include validation of customer trouble tickets and maintenance solutions and providing maintenance -dispatch and depot-level maintenance.

Perform annual recurring on-site inspections and periodic Preventive Maintenance Inspections (PMI) in accordance with manufacture specifications to ensure optimal operation.

Technical Support –

Provide on-site ELMR network administration at the zone controller to include remote troubleshooting, software upgrade and licensing, maintenance dispatch, and service restoral, and technical support Monday through Friday, 8:00am through 5:00pm MST (8/5) to include a one hour lunch break. Remote monitoring shall be provided 24 hours a day/seven days a week (24/7).

2.1.3

2.1.5

2.1.6 2.1.11 Provide technical support Monday through Friday, 8:00am through 5:00pm MST (8/5) to include a one hour lunch break. Remote monitoring shall be provided 24 hours a day/seven days a week (24/7).

Provide centralized enterprise monitoring at Peterson AFB zone controller site. The scope of this monitoring shall include remote monitoring, remote diagnostics, contacting base Point of Contact (POC) site-specific outage verification and maintenance coordination actions, initiate trouble tickets, and monthly Over-The-Air-Rekeying (OTAR) changing or updating encryption keys on active Air Force (AF ) LMR handsets and vehicle radios for Base LMR Sites.

Provide an on-site System Manager dedicated to the AFSPC network, responsible for the coordination of technical support, monitoring, and maintenance of the ASTRO 25 system. The System Manager must be qualified in ASTRO 25 technology, Project 25 technology, Advanced Encryption Standard encryption knowledge, Over-The-Air-Rekeying (OTAR) operations, dispatch console systems operations, Project 25 subscriber radios, System Fleet-mapping and applicable database operations, with a minimum of two years of experience.

Provide software maintenance upgrades and updates for all monitored LMR subsystems.

4.0 GOVERNMENT FURNISHED PROPERTY AND SERVICES:

4.1 GOVERNMENT FURNISHED PROPERTY (GFP)

4.1.1 The Government will provide access to resources e.g. cable conveyances, interfaces upon request.

4.1.2 The Government will obtain and provide all zoning approval, necessary permits, and Civil Engineering approvals at all sites and locations.

4.1.3 The Government will provide no more than one office space with furniture, to include desktop computer, and network printer, and desk telephone. This office space will be located at building on Peterson AFB, Colorado Springs, Colorado 80914.

4.2 PROPRIETARY DATA. The Contractor shall:

4.2.2 Request COR approval prior to the use of any proprietary data or software tools to fulfill the requirements of this contract.

4.2.3 Return all data pertaining to this contract to the Government upon contract expiration. The Contractor shall not retain unclassified material generated or received under this contract after the contract ends without approval of the appropriate office of primary responsibility.

4.2.4 Conform to all Operational Security (OPSEC) requirements when handling and discussing proprietary information.

4.3 PRODUCT OWNERSHIP: All products produced by the Contractor in the performance of this PWS are property of the Government.

4.3.1 The Government has unlimited rights to all deliverables developed under this PWS. The Contractor shall not use any materials pertaining to this contract for business development or any other vendor strategic purposes.

5.0 GENERAL INFORMATION

5.1 ELMR (ASTRO 25) TRAINING POLICY GUIDANCE

5.1.1 Contractor personnel shall be qualified in ASTRO 25 technology, Project 25 technology, Advanced Encryption Standard encryption knowledge, dispatch console systems operations, Project 25 subscriber radios, System Fleet-mapping and applicable database operations, with a minimum of two years of experience.

5.1.2 Complete all Government-provided local training IAW local policy (e.g. safety, security, Information Assurance, etc.).

5.2 HOURS OF OPERATION. The Contractor shall:

5.2.1 Provide on-site support Monday through Friday, 8:00am through 5:00pm MST (8/5), excluding all legal Federal Holidays observed by the Federal Government.

New Year’s Day
1 January
Labor Day
1st Monday in

September

Martin Luther King’s

Birthday 3rd Monday in

January

Columbus Day
2nd Monday in

October

President’s Day
3rd Monday in

February

Veteran’s Day
11 November
Memorial Day
Last Monday in May
Thanksgiving Day
4th Thursday in

November

Independence Day
4 July
Christmas Day
25 December

5.2.2 Provide continuous after-hours emergency response support for any Severity Level-1 outages as defined in Table 2.0. Contractor shall respond within 4 hours from receipt of notification.

5.2.3 Contractor employees will contact his/her supervisor for direction concerning late reporting or early release due to inclement weather. Government officials are not authorized to grant “administrative leave” or expend government resources to compensate contractor personnel to attend government-sanctioned morale building activities (e.g., picnics, golf outings, holiday parties, sports day events, fitness time). Military down days are not considered Government holidays.

5.3. INHERENTLY GOVERNTENTAL

5.3.1 Contractor shall ensure personnel do not perform any inherently governmental activities IAW FAR 7.503.

5.4 REPRESENTATION OF GOVERNMENT

5.4.1 Contractors shall not attempt to represent the Government of the United States or HQ AFSPC to any other person or entity, U.S. or foreign, except for delivering a Government-approved message or position.

5.5 CONTRACTOR IDENTIFICATION

5.5.1 Contractors shall wear company identification badges so as to easily distinguish themselves from government employees (e.g. corporate identification badges, Government issued identification that reflects Contractor status, etc.) These badges must be conspicuously displayed at all times when working with government personnel. Identification badges must be displayed above the waist at all times to allow for easy identification as a Contractor employee or authorized sub-contractor performing work for the Contractor. Badges shall be worn at all times when Contractor employees are co-located on a Government installation or when on temporary duty (TDY) working with other Government personnel. Sub-contractor employees’ identification badges shall identify their respective prime Contractor.

5.5.2 Contractors shall when conversing with government personnel during business meetings, over the telephone or via electronic mail, support Contractor personnel shall identify themselves. Electronic mail signature blocks and business cards shall identify Contractor/company affiliation.

5.5.3 When co-located space in a government facility, such as offices, separate rooms, or cubicles, work area must be clearly identified with Contractor supplied signs, name plates or other identification, showing that these are work areas for Contractor or sub-contractor personnel.

5.6 SECURITY. Contractors assigned to this contract require a SECRET United States Government Security Clearance. Information requiring classification in the interest of national security shall be consistent with security classification guides. The Contractor shall provide personnel with clearances commensurate with DD Form 254, Department of Defense (DoD) Contract Security Classification Specification.

5.6.1 Industrial Security. The Contractor shall comply with DoD 5220.22-M, “National Industrial Security Program Operating Manual” (NISPOM) and DOD 5200.2-R. The appropriate background investigation for IT-II with Secret clearance is a National Agency Check with Local Agency Check and credit Check (NACLC). The contractor shall forward their employee clearance information to: HQ AFSPC A6 Attention Personnel Security Office, Peterson AFB 80914.

5.6.2 Physical Security. The Contractor shall comply with base Operations Plans and Instructions for Force Protection Condition procedures, Random Antiterrorism Measures, and local search and identification requirements. The Contractor shall adhere to security policies and be responsible for the safeguarding of all Government property provided for Contractor use. At the end of each work period, all Government facilities, equipment, and materials shall be secured.

5.6.4 Commander’s Authority. The Government may direct the Contractor in writing to remove any employee from the installation when retention of such employee endangers life, property or security, or where such employee violates laws or regulations. This action does not relieve the Contractor from total performance of the contract tasks specified herein.

5.6.5 The provisions outlined above apply to the prime Contractor and any subcontractors the prime Contractor may employ during the course of this contract. No Contractor personnel performing sensitive duties shall be allowed to commence work on this effort until his or her trustworthiness has been favorably adjudicated. DoD CAC/access identification badge (ID badge)/electronic key card every Contractor employee shall obtain and possess a DoD Common Access Card (CAC) and an Access ID Badge as required. Contractor shall use the card in accordance with 500352.242-9001. Upon favorable review and initiation of the PSI to establish the suitability of an employee for the job and the approval for temporary Automated Information System (AIS) access pending final adjudication of the PSI, the Contractor shall submit to a designee request for the DoD CAC and ID Badge.

5.7 ACCESS TO GOVERNMENT PROPERTY AND FACILITIES. The Contractor shall:

5.7.1 Be allowed unescorted access to Building 1038 on Peterson AFB, and other sites consistent with contract requirements upon completing required building security requirements. Any other escorted and/or non-escorted access to DoD facilities will require local security access requests per the facility’s security policy. Contractor personnel may also enter facilities where escorted access is mandatory. If so, Contractor personnel shall be notified before entering the facility. Access to government facilities, documents, and systems shall be in accordance with DD Form 254, and Department of Defense Contract Security Classification Specifications.

5.7.2 Ensure employees who terminate their services shall return without delay any government identification/access badges issued in support of this contract.

5.7.3 Comply with directives pertaining to operation of privately owned vehicles on Air Force Installations per policies established by the installation commanders.

5.8 MANAGEMENT. The Contractor shall appoint a Program Manager 5 days after contract award who shall coordinate with the COR to obtain and clarify contract requirements and who will be responsible for the daily control and supervision of contractor's employees. The Program Manager shall ensure the contractor's employees understand the prohibitions imposed on the US Government regarding personal services contracts and will report instances where the Government attempts to control or supervise contractors' employees to COR or Contracting Officer immediately. The Program Manager shall have the authority to resolve problems, allocate resources, manage personnel, and monitor operation performance to ensure requirements are met.

5.8.1 The Contractor shall provide the name, telephone number (to include mobile telephone and pager, as applicable) and e-mail address of the Program Manager to the COR and Contracting Officer in writing within 8 business days of contract award.

5.8.2 Replacement of the Program Manager: In the event of the replacement of the Program Manager, the Contractor shall notify the designee, in writing, of such replacement. Information identified in paragraph 5.11.1 shall be provided to the COR and Contracting Officer at least 15 calendar days prior to a planned replacement and within 24 hours following an unplanned replacement.

5.9 MATERIALS AND OTHER DIRECT COSTS (ODCs). The Contractor may be required to purchase reimbursable items for items identified in PMIs or help desk support. Reimbursable purchases must be approved by the COR, in writing prior to purchase. The Contractor shall provide an itemized listing of purchased items and title the listing “Government-Furnished Property (GFP).”

5.10 ENTERPRISE-WIDE CONTRACTOR MANPOWER REPORTING

The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the ELMR via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address: http://www.ecmra.mil/ Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year, beginning with 2013. Contractors may direct questions to the help desk at help desk at: http://www.ecmra.mil.

5.11 Quality Control.

The Contractor shall provide a Quality Control Plan 30 business days after contract award. The Contractor shall be responsible for identifying system and outside plant deficiencies and/or discrepancies throughout the life of the project. A weekly report (soft copy) shall be submitted indicating progress/status and listing any deficiencies/discrepancies found and actions to correct them.

5.11 Deliverables

Title
PWS Paragraph
Remarks
Frequency
# of Copies
Format
Distribution
1
Master Preventive Maintenance Inspection (PMI) Schedule
2.1.9
Develop master PMI schedule and submit within 5 days of contract award. This report will be delivered annually by 25 March of each subsequent year
Annually
2 copies
Electronic
COR, Base LMR offices
2
Monthly Maintenance Report
2.1.11, Appendix B
Provide a monthly maintenance report of all outage response actions performed for each month
Monthly
2 copies
Electronic
COR, Base LMR offices
3
Quality Control Plan
2.1.13
Provide a Quality Control Plan within 30 business days after contract award. The Contractor shall be responsible for identifying system deficiencies and/or discrepancies throughout the life of the project.
Initial
1 copy
Electronic
COR
4
Quality Control Plan (deficiency/discrepancy tracking)
2.1.13
A monthly report (soft copy) shall be submitted indicating progress/status and listing any deficiencies/discrepancies found and actions to correct them.
Monthly
1 copy
Electronic
COR

6.0 APPENDICES

APPENDIX A – ACRONYMS

AFB

Air Force Base

AFSPC

Air Force Space Command

AIS

Automated Information System

CAC

Common Access Card

COR

Contracting Officer Representative

DoD

Department of Defense

DSN

Defense Switched Network

E/APL

Evaluated/Approved Products List

ELA

Enterprise License Agreement

ELMR

Enterprise Land Mobile Radio

FOIA

Freedom of Information Act

GFP

Government-Furnished Property

HQ AFSPC

Headquarters Air Force Space Command i-TRM

Infrastructure Technical Reference Model

IAW

In Accordance With

ID Badge

Identification Badge

IT

Information Technology

JFTR

Joint Federal Travel Regulations

KMF

Key Management Facility

LMR

Land Mobile Radio

NACLC

National Agency Check with Local Agency

Check and Credit Check

NISPOM

National Industrial Security Program

Operating Manual

NLT

No Later Than

O&M

Operations & Maintenance

OPSEC

Operational Security

OTAR

Over-The-Air-Rekeying

PA

Privacy Act

PMI

Preventive Maintenance Inspection

POC

Point of Contact

PSI

Personnel Security Investigation

PWS

Performance Work Statement

TDY

Temporary Duty

UCM

Universal Cryptographic Module

APPENDIX B – MONTHLY MAINTENANCE REPORT

Outage Date/Time
Outage Severity (1/2/3)
Location (base, master)
Description of Problem/Outage
Date Closed/Corrective Action Taken
Total Downtime (# Hours)
Current Status (Open/Closed)
Case/Tracking #

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