Attachment_1_BNTS_PWS_16_May_13.docx

PERFORMANCE WORK STATEMENT (PWS)

FOR

OPERATIONS AND MAINTENANCE SERVICES

BASE NETWORK AND TELECOMMUNICATIONS SYSTEM

(BNTS)

COLUMBUS AFB, MS

16 MAY 2013

PERFORMANCE BASED WORK STATEMENT (PWS)

FOR

OPERATIONS AND MAINTENANCE SERVICES

BASE NETWORK AND TELECOMMUNICATIONS SYSTEM (BNTS)

Description of Services

Scope of work The contractor shall perform all duties and tasks associated with the management, installation and configuration of communications, information and computer systems for Columbus AFB (CAFB) and CAFB supported sites. The Contractor shall provide all personnel, equipment, tools, materials, vehicles, supervision and other items and services, unless specified in this contract as Government Furnished Property (GFP) listed in section 5.0. Work under this PWS will support the mission of the 14th Fighter Training Wing (14 FTW) at CAFB by performing/providing timely, proactive, high quality communications and computer services.

These services shall include the below requirements and other related services to ensure comprehensive base network and telephone service support.

· Highly reliable wired and wireless communications systems

· Telecommunications support and administration

· Networked voice

· Cable Infrastructure (ISP/OSP)

· Voice Over IP (VoIP)

· Information Technology (IT) planning

· Local customer support of regionalized data processing

· AF Global Information Grid (GIG) Network Management (NM) and Administration

· Defense Information System Network (DISN) node administration

· Combat Information Transport System (CITS)

· Software installation, configuration and support

· Wing software management

· Information Assurance (IA)

· Information protection operations

· Customer training, support and education The Contractor shall perform Operation and Maintenance (O&M) and other services required to ensure the Base Network and Telephone Systems (BNTS) services are available 24 hours per day, 7 days per week. As part of the AF network enterprise transformation efforts, identified network support and operations requirements have transferred to AFNetOps consolidated support/operations centers off of CAFB. The responsibilities for the AFNetOps centers will broadly include management of core servers/services; most network administration functions (excluding applications services); and most network management functions. All core servers/services (mail, DNS, domain controllers etc.) and infrastructure from the boundary equipment to the Service Delivery Point (SDP) will be remotely administered. The SDP router will be managed by AFNetOps. AFNetOps centers will be responsible for the configuration, administration, and routine tasks associated with operating the devices.

Device/System Management Network/device management services covered by this PWS may include the below requirements and other related services:

· MS Windows XP/Vista/7/8

Operations and Maintenance

Trouble Tickets

Base Telephone Systems (BTS) Trouble Ticket Processing Telephone trouble calls shall be reported to the Communications Focal Point (CFP) via the trouble call line 434-2666, option 3. The CFP will notify the on-call person for the Contractor. The Contractor will provide the CFP and/or the COR ongoing updates associated with outages/trouble call/tickets. The call will be opened and recorded in a Government provided Automated Information System (AIS). The category of the outage will be based on the Restoration Priority List (RPL) found in Appendix 5 and/or this section 2.2 of this PWS. If multiple outages occur the COR/CFP will assign the category of the outage and establish the repair priority. The COR may declare any outage as Emergency if declared mission critical. The Contractor shall respond on site and initiate repair actions within the specified time listed below from the time the contractor is notified of the outage. However, exceptions to time limits may be allowed, with the written approval of the COR, with appropriate justification. The Contractor shall continue to work on repair actions until service is restored based on priority or until a COR determines the repair is no longer mission critical.

Base Network Control Center (BNCC) Trouble Ticket Processing

This activity may include dealing with customers, troubleshooting, data collection and storage, and resolving the problems or routing the issues to people who can resolve the problems. All trouble tickets will follow AFNet escalation matrix unless otherwise directed by the COR. The below items remain the responsibility of the NCC.

The Contractor will utilize the AF provided Trouble Ticket (TT) system/process to maintain proper communication and coordination throughout problem resolution.

Open TTs to track resolution actions for within the NCC AOR.

Update and route TTs as required to track all resolution actions/efforts for given TTs.

Keep TT continuously updated with all current information/actions as soon as possible.

Work with base Functional System Administrators (FSA), Client Support Technicians (CST), ESD, MCCC, and I-NOSC to resolve problems as needed.

System and Service Outages

Authorized Service Interruption Contractor shall identify, coordinate, and schedule service outages with the CFP and/or COR. The contractor will conduct work after receiving approval from the COR. The Contractor shall schedule such outages to minimize inconvenience to users based upon Government user work schedules. Notification shall include the reason for the interruption, start and stop times, the service affected and buildings involved. The Contractor shall maintain records of all scheduled service interruptions on site for the life of the contract and make available for Government review at any time. These records shall include the reason for the interruption, authorization, start and stop times, the service affected, the buildings involved and the action taken with Contractor’s initials.

Outage actions and recommended dates and times will be coordinated to the contractor through the CFP or COR. The contractor will review proposed ASIs and advise the 14 CS on the impact to base network services. Once the ASI is approved, the contractor will schedule/coordinate approvals with the CFP and AFNetOps centers, and will monitor e-mail boxes to review any AIS requests/responses from AFNETOP centers, and will maintain the schedules to ensure compliance. Re-occurring outages established by the 14 CS will be performed during non-duty hours. The contractor will prepare and submit ASI messages, review responses and maintain ASI schedules. Non-re-occurring ASIs will be scheduled at least two weeks in advance or as soon as practical. The contractor will perform system checks after ASIs are terminated and report status to the CFP.

Unauthorized Service Outages

Emergency: Contractor shall respond on-site within one hour and restore service within eight hours unless otherwise approved by the COR. Emergency outages/trouble calls are classified as any of the following or as directed by the COR:

· Loss of over 75% or more of total call handling capability of any communications system

· Loss of any Primary or Secondary Crash System or any portion thereof

· Failure of one or more circuits listed in the Base Restoral Priority List (RPL)

· Loss of LAN Local Area Network (LAN) connectivity affecting Command and Control (C2) user(s)

· Affects security or emergency type operations, including Emergency Operations Center (EOC); as well as those affecting safety

· Affect specifically identified events and/or exercises

Priority: Contractor shall respond on-site within six hours and restore service within one working day. Priority outages are classified as any of the following or as directed by the COR:

· Loss of over 25% or more of total call handling capability of any communications system

· Major alarm of any switching system identified in Appendix 3

· Loss of LAN connectivity affecting 50% or more users

Routine: Contractor shall restore service within two working days. Expediting parts and/or labor is not required. Routine outages/trouble calls are any other outage(s) not included in the above categories.

OTHER Outage/Trouble Cause The Contractor, shall determine if a reported problem or system failure is the contractor’s responsibility. The Contractor shall immediately notify the COR if the malfunction is determined to be due to other causes (outside the Contractor-maintained system/equipment). The Contractor shall be liable for the cost of any third party service calls or charges necessary to isolate and repair the problem if it is later determined by the COR that the cause of failure is directly related to the BNTS contractor or failure of proper O&M of the system.

Touch Maintenance The contractor will be required to perform touch maintenance on all Columbus AFB and associated communication systems that provide voice, data and video services as requested from the COR, AFNETOPS or as necessary according to applicable directives.

Coordinate all maintenance tasks that may require system downtime with the COR and or designated AFNetOps offices.

Preventive Maintenance Inspections (PMIs) Contractor shall perform PMIs as required on all systems covered by this contract IAW OEM recommended or established schedules and/or manuals. The contractor will coordinate and provide the 14th Communications Squadron Communications Focal Point (CFP) a published schedule of PMIs. Contractor shall elevate any problems and identify any trends to the BTS Contract Office Representative (COR) in writing within one workday.

Global Positioning System (GPS) Service Data The Contractor shall use GPS technology to provide geospatial coordinates and feature description data of cable/duct installation pathway which includes but not limited to data on new, modified and repaired underground, direct buried and/or aerial communication cables, ducts, manholes, hand holes, splice points, pedestals and building entry points and terminals. Contractor shall ensure data compatibility and updates with the CVC database.

The Contractor shall use GPS equipment and technology supplemented with electronic underground cable locating equipment and land surveying operations necessary to collect required CFD following the Federal Geographic Data Committee (FGDC)-STD-007.4-2002 specified in Appendix 4. The Contractor shall be responsible for providing all required equipment including software, hardware and any other tools, material and labor necessary to provide CFD on electronic storage media in the specified formats.

Each communication feature requiring geospatial coordinates shall be located within one meter of its true ground position, in the horizontal plane, with a 95% spatial accuracy confidence level as defined in FGDC-STD-007.3-1998, specified in Appendix 4. Geospatial coordinates shall be in the center of each manhole, hand hole, pull box, pedestal and splice points. Geospatial coordinate data for the location of utility lines shall be recorded at a minimum every 50 feet, and each turn or bend in the pathway must also be recorded so the coordinates for any point along the turn pathway will fall within the allowable accuracy.

Communications and Information Systems Installation Record (CSIR).

The Contractor shall have a CIPS account in order to use CVC. The Contractor shall coordinate with the CISR Manager to apply for an account.

OSP Drawing Records Contractor shall load, edit, update and maintain CSIR information, for the OSP, in the CVC database IAW applicable directives. The Contractor is responsible for verifying Contractor entered information for accuracy and completeness. When the update is completed the Contractor will close the session and notify the CSIR Manager that the edit is ready for QC/approval. The CSIR Manager will notify the Contractor if any feature was rejected during the quality control approval process in order for the Contractor to take corrective action.

ISP Drawing Records The Plans & Implementation Work Center/CSIR Manager shall maintain ISP records in electronic format using software commonly included in the AF standard desktop configuration (SDC) whenever possible. Graphic records (communications equipment room layouts, rack elevations, etc.) shall be created/maintained using Microsoft Visio. Tabular records (e.g., equipment inventory) shall be created/maintained using Microsoft Excel or as a list on the Columbus (or AETC) SharePoint site. The CSIR Manager shall transfer all required inside plant information from other sources (e.g., administrative and maintenance CSIR, Legacy CSIRs, work orders, inspection reports, as-built and as-installed marked-up drawings or other project information produced as a result of the Contractor’s IT/Comm. base network operations) into electronic ISP records as defined below [currently Base Project Implementation Database (BPID)]. The CSIR Manager shall ensure any changes/additions made to a record will also update any associated records. For example, if a floor plan has changes, the changes shall also be posted to the related rack elevations, as well as the equipment inventory.

Work Center Specific O&M

Telephone Switch System O&M The Contractor shall operate and maintain the system(s) identified in Appendix 3. The Government will measure the acceptable standard performance level by a determination of the total systems availability (up time) and reliability. Rating during any given month shall not fall below 99.9% attributable to the contractor’s maintenance procedures, actions or culpability. All equipment or services installed by the Contractor shall automatically become part of the O&M services. This includes, but is not limited to: management; administration and maintenance; performing software functions (i.e. number reclamation) and translations for any trunk or circuit of configurations required by on-base systems or users; data administration; trouble assistance; and, records administration. O&M shall also include Voice over Internet Protocol (VoIP) and Unified Capabilities (UC); operations as part of the BTS. VoIP equipment is identified in Appendix 3. Demarcation of VoIP maintenance shall not extend beyond the Voice Gateway and Call Manager(s). The VSSs Technicians shall be full qualified to operate and maintain the Base’s VSSs listed in appendix 3 and all associated equipment. Contractor shall track and document BTS O&M activities in the Telecommunications Management System (TMS) or approved Automated Information System (AIS). O&M shall also include Voice over Internet Protocol (VoIP) and Unified Capabilities (UC) operations as part of the BTS. As the DoD and AF replaces legacy telephone components with Unified Capabilities/Voice Over Internet Protocol components, contractor maintenance responsibilities will transfer from legacy components to Unified Capabilities/Voice Over Internet Protocol components.

Perform ISP and OSP O&M Contractor shall maintain ISP and OSP cable and equipment as identified in Appendix 3 and IAW applicable documents listed in Appendix 2 of this PWS.

PMI’s

Switch Power Test: The Contractor shall perform scheduled PMI tests of the telephone switch backup power system. PMIs shall test and document the power systems identified in Appendix 3. Each power system shall be tested IAW OEM specifications.

Manholes and/or Hand holes: The Contractor shall inspect 12 manholes identified or accepted by the COR quarterly to cover 100% of the manholes on Columbus AFB within the life of this contract. These manhole inspections will be covered under the O&M portion of this contract. Additional inspections in excess of the base 12 shall be accomplished as a work order IAW PWS section 2.7. If the Contractor is working in a manhole not scheduled for a PMI, the Contractor must correct any discrepancies before the job is considered complete. Then, the manhole will be counted in the monthly PMI schedule. The Contractor shall inspect each manhole/hand hole for the following discrepancies and correct as required:

· All Base cables will be identified and tagged. At each splice, tags will be placed on each side of the splice identifying each cable. In manholes with pull through cables, each cable will be identified with a tag.

· All Base cables will be racked to the manhole cable supports.

· All ducts (vacant or occupied) will be sealed.

· All manholes or hand holes will be cleaned of mud, water and any other debris.

· Update the Cyberspace Infrastructure Planning System (CIPS) Visualization Component (CVC) database - for the manhole or hand hole and record all descriptive information for splices, cables, ducts and other communication features in the manhole or hand hole.

Cable Vault and Sump pump: The Contractor shall perform a monthly PMI of the cable vault sump pump, back-up mobile sump pump and generator.

Cable Location, Staking, and Marking The Contractor shall locate, stake, and mark encased or direct buried conduits/cable when requested by the COR. Marking shall be within three feet of the actual location at ten-foot intervals and at direction changes. The marking shall begin two feet from the point of entry into the work area and shall continue two feet past the point of exit from the work area. Contractor shall complete location, staking and marking within the specified time listed below from the time the COR advises the Contractor of the requirement unless additional time is permitted by the COR. The Contractor shall document time extensions in writing, which includes the signatures of the COR and the BTS manager. The Contractor shall comply with the following timelines for location, staking, and marking:

Emergency: Within two hours of notification Priority: Within 24 hours of notification.

Routine: Within 2 duty days of notification.

Administrative Changes (Admin Change) Admin changes are programming changes made through the telephone switch to include but not limited to: display, line appearance, ringing, groups, intercom, paging access. Admin changes will be part of monthly maintenance and will not require a work order to accomplish. Admin changes shall be completed within 2 duty days after receipt of the 7-in-1 form unless otherwise specified by the COR.

Call Accounting System (CAS) All Call Accounting will be managed and provided via TMS. The Contractor shall ensure Voice Switching System (VSS) System Message Detailed Recording (SMDR) is compatible for feeding into TMS.

Off-Site Switch Back-Ups Contractor shall perform disk backup of the switching system(s) memory within 24 hours of data base changes. When no database changes have occurred over a seven-day period, Contractor shall perform switching system backup. Contractor will be required to supply all equipment and supplies necessary in order to accomplish this requirement.

Voice Mail The Contractor shall provide voice mail O&M. This includes: management and administration of system network table and networking plan for multiple systems; additions; deletions; modifications to user’s mailbox; password resets; distribution list; holiday schedule tables; daylight savings time; synchronization with the phone switch; proper functioning of the auto attendant feature; and other related services required to operate and maintain voice mail. Functions also include diagnostic, maintenance, minor programming changes on current software applications, and performing system backups of system configuration and names. Voice mail O&M shall be completed within 2 duty days after receipt of request unless otherwise specified by the COR.

Automated Health and Morale System (AHAMS) The Contractor shall provide, configure and issue AHAMS PINs in accordance with the COR directed process. AHAMS PIN cards shall be within 2 duty days after receipt of request unless otherwise specified by the COR.

Automatic Call Distribution (ACD) System The Contractor shall provide O&M for the ACD system installed under the TelMod program (See Appendix 3). O&M includes reconfiguration; blocking/busying out trunks; configuring and modifying call routing; monitoring system operations; updating firmware; initiating least cost routing; updating the dial plan; and other related services to operate and maintain the ACD system.

Traffic Measurement and Analysis The Contractor shall perform traffic measurement and analysis within system capabilities and limitations and perform analysis and studies on the base switching system when on an as needed basis. The information required by the contract must cover no less than a five-day period, (Monday-Friday, excluding holidays). The Government may also request measurement and analysis for a particular line or group of lines.

Contractor Support Services

BTS Work Center Records

Manhole, Hand hole, and Building Terminal Inspection/Maintenance/Repair The Contractor shall maintain manhole, hand hole, distribution pedestal terminal, and building terminal inspection. The Contractor shall update the CVC database with pertinent Communication Feature Data (CFD) information gathered during the inspections. The record shall be available for inspection and analysis by the Government. If other electronic documentation is implemented, the Contractor shall grant the Government access to those records.

Cable Installation/Repair Test Results Contractor shall develop and maintain a cable installation/repair test results record after the installation or repair of an OSP cable. Graphics and pictorials may be used to illustrate. The record shall, at a minimum, contain the purpose of test; identification of item tested and test equipment used; copy of results/analysis; actual recorded data (e.g., instrument readings) (if extensive, provide as an appendix).

Switching System and ISP & OSP Equipment Operational Records Contractor shall retain records on site and make available for the COR, CO orCA review at any time.

Telecommunications Management System (TMS) The Contractor shall perform BTS record updates using TMS. Some updates may require the Contractor to manually enter the data upon completion of individual work orders or record changes. The Contractor shall update TMS records within two duty days of completion of work orders or trouble ticket reassignment. Contractor shall also maintain cable pair assignment records using TMS.

Traffic Measurement Records The switch-generated record shall be used to satisfy this requirement as requested. The record shall contain an analysis of the traffic measurements including a trunk traffic summary and individual analysis of each trunk group. Printed records shall be provided to the COR on an as-needed basis, not more often than twice annually. The Government may also request measurement and analysis records for a particular line or group of lines. This selective record shall be maintained on site and made available to the COR within three work days from occurrence of Traffic Measurement analysis.

System Capacity Records Contractor shall produce system capacity records upon request by the COR. Records shall include each cable and terminated cable count, type of cable (bad and spare), and number of conductors used. Quarterly system capacity records shall be produced for the host switch and remotes. The records shall include total line ports, line ports in use, line port type (analog/digital/ISDN/etc.) total used, and DS-1 digital trunk ports (total ports used and available) and available directory numbers.

System Security Audit Record The Contractor shall develop and maintain an electronic weekly user event log that contains, at a minimum: the number of logins (remote and local); number of login attempts (remote and local); password changes; and/or any critical table modifications including new user accounts as allowed by the switch.

Call Accounting System (CAS).

The Contractor shall gather and electronically store records output from the CAS as formatted by the AIS (currently TMS) provided by the government.

Music-On-Hold The Contractor shall be responsible for the day to day operation of the music on hold service. The Contractor will utilize the service provided by the Air Force News Agency, “Air Force Radio News on Hold”, that will feed into the Columbus AFB switch. The COR will notify the Contractor when, if needed, to change the music selection.

E911 Database The Contractor shall maintain the E911 database for the 7-digit telephone number generated from the Base CS 1000 telephone switch. Database updates shall be completed within 24 hours that the telephone number has been installed or relocated and within two duty days of being disconnected from service. Local procedures are located in the Bellsouth 9-1-1 Pin Point Service Reference Guide.

BNCC Specific O&M Requirements

Administrative Tasks

Limited NIPRNET and SIPRNET Administration Contractor will perform routine administrative tasks for NIPRNET and SIPRNET as necessary or directed by COR(s) to include but not limited to user/computer account tasks (create, delete, updates, password resets, etc...) Contractor will assist other organizations or entities, local or external, with administrative tasks and/or interoperability with base communications system.

Provide/perform system administration support to wing users in the application and operation of COTS software, specialized applications and standard desktop devices and software.

Maintain logon scripts to ensure security patches, user notifications, mapping of network drives are addressed at log-in.

Maintain shared drive permissions and directory structure for 14 FTW and tenant organizations.

Perform premise level configuration standardization and interface engineering.

Maintain current listings of all unit representatives, to include for example, Functional System Administrators (FSA’s), Computer Systems Technicians (CST’s) and IAOs. Listing shall be made readily available to COR upon request.

Maintain the base network characterization and validate the DISA Minimum Essential Circuit Listing (MECL) and the Defense Information Technology Contracting Office (DITCO) database product.

Manage all equipment/system preventative maintenance actions, schedules and historical information data in IMDS.

Administer Patch Management

Manage local automated patching efforts including pushing out vulnerability patches, software upgrades, and configuration changes to workstations and servers. Coordinate and track unit compliance with patching efforts.

Develop SCCM packages, queries and reports as necessary or as directed by the COR(s).

Utilize patching system administrative tools to assist in troubleshooting process and provide face-to-face interaction with customers, FSA/CST, etc… in troubleshooting or as directed by AFNetOps.

Virtual Private Network (VPN) The Contractor will provide current VPN client installation and configurations to FSA/CSTs. When requested, the Contractor will provide support for VPN client installation to the FSA/CSTs as well as assistance in resolving issues for individuals requiring access to the NIPRNET.

Distribution Lists The Contractor will create, modify, and or delete Distribution Lists as necessary.

Process Incoming Directives & Coordinate Resolution

Review, track and disseminate all directives received from higher level AFNetOps organizations or base and 14 CS leadership.

Provide physical response assistance to ESD, MCCC and all AFNetOps offices based upon directives and Network Task Orders received.

Forward all directives/Network Task Orders to base FSAs/CSTs as needed.

Virtual Computing

The contractor will configure/maintain all software and hardware necessary for the operation of the virtual computing environment. The virtual computing environment consists of a VMWare enclave and all associated software and equipment. The contractor will aid CSTs in the deployment of any user interface devices. The contractor will also develop documentation computing environment. IAW all applicable directives, and all subsequent revisions, listed in A2, and as outlined below, the service contractor shall:

Virtual enclave: Ensure devices are configured and optimized to support the configuration and operations of the Columbus Enterprise as directed by the COR.

Develop and maintain physical and logical drawings of the virtualized enclave

Actively monitor virtual systems and supporting devices with AF provided virtualization monitoring tools.

Maintain restore points (snapshots), as resources permit, as changes to virtualized systems occur, for all virtualized systems to facilitate rapid restoral of services.

PDA Support

Provide operating system and application server support for locally controlled PDA server to support all AETC authorized PDAs. Initial user and device upgrade configurations will be performed by AF personnel.

Provide second level troubleshooting and resolution of PDA device problems/issues.

Storage Area Network (SAN)

Perform daily physical checks on SAN racks including everything with physical indicators.

Troubleshoot, remove and replace defective hardware and perform equipment upgrades as directed.

Apply software/hardware updates for SAN when directed by higher headquarters.

Perform customer storage requirements definition, local customer interface and file system management (share administration, folder/file permission assignment)

Provide higher headquarters with Storage Resource Management (SRM) utilization/expansion requirements and maintain SRM.

Administer base specific configuration and accomplish changes only after coordination with higher headquarters or the COR.

Automated Patching System

Perform client installation and troubleshoot/resolve failures.

Complete package, query and advertisements as necessary to ensure applicable system patches.

Coordinate with AFNetOps organizations on packaging and advertisement actions.

Provide queries and reports as requested.

Assign permissions to 14 CS/FSA/CST personnel to access reporting capabilities.

Network Monitoring Monitor all local communication systems to facilitate reliable base communications. The contractor will utilize AF supplied AISs (i.e. CISCO works, Solarwinds etc.) to provide alerts and warnings as well as comparing results to baselines. Respond to events and/or alarms appropriately and provide all information to the COR for up channeling. Possible ( > 5%) service effecting responses will be approved by COR prior to execution.

Provide Network Management & Network Defense (NM/ND):

Information protection is driven by changes in regulations and threats and a constant demand for defense. IPO performs scheduled scans and works with people who monitor the network.

Implement, Operate, & Maintain Directed Security Measures

Take necessary actions to ensure all applicable Federal, DoD, DISA, AF, AFNetOps, MAJCOM, base, unit or higher echelon network operations office security measures/practices are implemented and requirements are completed for all BNCC AOR equipment or systems. Also, take all measures practical to ensure all Columbus AFB systems are compliant with applicable security guidance.

Coordinate, terminate service and/or network connectivity of local systems and networks, as directed by 14 CS leadership, which fail to maintain compliance with Air Force and local security policy.

Assist customers in collecting accreditation information for base networks and systems, ensuring all systems and networks meet Air Force and local security and anti-virus requirements and have appropriate Designated Approval Authority (DAA) approval before they are connected to the base network infrastructure, and ensuring all network and systems accreditation packages are maintained.

Report and assist in the remediation of security incidents according to appropriate guidelines or as directed by AFNetOps or COR.

Work with responsible offices to identify internal actions such as local reporting channels and criteria for determining who is notified.

Conduct Security Audit/Assessment

Develop and implement a base-wide network security policy in addition to the AFNetOps policy to effectively manage the base network and prevent intrusions, viruses and/or other network insecurities. Coordination and approval must be accomplished by the COR prior to implementation.

Develop procedures with AFNetOps centers and any designated agency to allow performance of security/vulnerability scans on all systems connected to the Columbus Enterprise. Develop local procedures for the distribution and documentation of corrective actions for deficiencies identified on system scans whether performed locally or by AFNetOps centers. Reports of completed scans shall be forwarded to the responsible organization as well as to the COR(s). The NCC will track all corrective actions within 7 workdays or by compliance date if suspense is shorter, of the date of report. Follow-up on this action will be required.

Network Scans

Perform Vulnerability Scanning via DoD/AF provided AIS’ at directed intervals. Ensure both physical and logical access to AISs and supporting infrastructure for scanning and vulnerability assessments.

Coordinate and track with appropriate entities for vulnerability remediation. Report and upload vulnerability data to DoD Vulnerability Management System (VMS) or other provided system as directed.

Perform fix actions as needed within allotted time frame.

Notifies required AFNetOps organizations and 14 CS specified work center of completion.

Password (PW) cracking

Scan networked devices with AF approved tools on a semi-annual basis or as directed by COR as resources permit. Provide reports to COR as requested.

Coordinate with FSAs/CSTs for remediation.

Provide final action via the appropriate AF supplied AIS.

Time Compliance Items Contractor shall monitor, review, implement, coordinate, update, and or manage all Time Compliance items as applicable. These may include, but not be limited to: MTO, NTO, CTO, TCNO, TCTO, NOTAM, or any other time compliance item from any responsible agency. The Contractor will be required to gather and report compliance data on network assets as required by this PWS or as directed by the COR.

Respond to Security Events

Work with responsible office(s) (i.e., CFP, ESD, I-NOSC and MCCC) on all categorized network security issues/actions within the timelines outlined by notifying authority. Timelines for actions and reporting may be dictated by AFNETOPS centers, policies, MTOs, TCTOs and SPINs or as directed by the COR.

Manage Certification/Accreditation

Support the certification of core services by providing AFNetOps organizations network topology and infrastructure information as necessary or as directed.

Update specific base security documentation as within 30 days to ensure certifications and accreditations packages meet AETC and AFNetOps established timelines and requirements.

Configuration Management Process

Maintain network configuration map and/or documents (typically Visio drawings but may vary) of the network infrastructure, and provide “as is” network topologies to the AFNetOps reporting channels.

Maintain communication closet wiring & network diagrams following the CSIR Manager’s direction and process via master CSIR drawings.

Manage Local IP Addresses (subnets, IPs, DHCP) as necessary or directed by the COR within 30 days of notification.

Change Management

Coordinate and obtain approval from Base Change Manager (14 CS/SCOS) for any request to change network configuration that affects any server, service, application, or device that is part of the Air Force Enterprise core services (e-mail, file, web, print, etc...).

Research, count, and report MTO compliance to the approved MTO compliance tracking system and as directed by COR.

Quality Control/Standardization-Evaluation

Perform network/circuit base lining and QC testing and evaluation for interfaces and connections between infrastructure devices such as routers, switches, etc. The testing should include available bandwidth, throughput, traffic collisions, latency, and other related requirements IAW applicable manufactures documentation or manual(s).

Cryptographic Equipment

Troubleshoot, and load/reload all cryptographic devices (e.g., TACLANEs).

Perform cryptographic equipment updates as necessary or directed by the COR, applicable AFKAG’s, or other authoritative DoD entity. Updates will be performed by the deadlines provided by the tasking or key lifetime.

Wireless Local Area Networking (WLAN)

Install, remove, and replace all wireless equipment connected to the Columbus AFB network. Be responsible for touch maintenance of wireless equipment as required/directed by INOSC.

Ensure WLAN operations security in accordance with the applicable accreditation package.

Assist customers with setting up and maintaining peripheral equipment required for operation of wireless systems located on Columbus AFB. The contractor shall maintain second look responsibilities for laptop and desktops utilizing the WLAN. If the NCC cannot determine or fix the laptop failure, they will return the laptop/desktop to the organizational POC for required replacement action.

Coordinate the changing of encryption keys between the client and VPN server with the assigned POCs as needed.

In coordination with INOSC, provide situational oversight of each wireless access point and manager for operational status as either “up” or “down”.

Provide second level support to POCs with DoD/AF authorized WLAN networks running on Columbus AFB not connected to the Columbus Network.

Local Servers

Manage, operate, upgrade, configure and maintain all wing servers as requested. Perform upgrades, security patches, etc as directed by Higher Headquarters agencies, AFNetOps organizations or COR.

Provide access to FSA/CST/POC for NCC co-located servers as requested or directed.

Ensure all aspects for AF Data Center Consolidation Implementation Plan are met, requiring all servers be physically migrated to one data center.

Performance Management

Conduct performance management operations (such as, establish baseline performance thresholds for systems and circuits, utilize performance data to identify service interruptions, performance degradation, or security breaches using government provided equipment/software). Provide reports to COR as requested.

Perform network/circuit base lining and QC testing and evaluation for interfaces and connections between backbone infrastructure devices such as routers switches etc and problem connections. The testing should include, but not be limited to, available bandwidth, throughput, traffic collisions, and latency. Maintain documentation of baseline and quarterly records of results. Provide reports to COR as requested.

Network Management

Control, manage, and document all service access points to/from Columbus AFB networks.

Maintain and provide network configuration map and/or documents (typically Visio drawings but may vary) of the network infrastructure to include the number of servers and terminals supported. Update the diagrams as changes occur. Provide access to the COR(s).

Administer/configure all devices from the Core/Distribution/Access to desktops that are within the Columbus Enterprise (i.e. switches, routers, servers, VOIP switches).

Base Software License Management

BSLM will utilize the AF provided automated tools (i.e. ForeScout CounterACT, SCCM) to perform inventorying and tracking software installed on the base network. Perform an annual (or as directed) inventory of all software, licenses, and corresponding documentation of unit software. Ensure each computer utilizing commercial software products is included in the inventory, to include laptops, desktops, workstations, and servers and reflects a full accountability of the commercial software loaded on each system. Ensure inventories reflect the total number of each product authorized compared to the total number of each product installed on the organization’s computers. Maintain accurate records of all software, licenses, correspondence and documentation for the 14 FTW and tenant organizations. Records will be available to the COR upon request.

Maintain the base primary and backup (geographically separated) software library for all software in use in a secure environment. This will include physical software media, license keys, and license documentation or proof of purchase.

BSLM will coordinate/track with CST/FSAs removal of unauthorized or illegal software from systems when detected. Coordinate with functional system administrators, client support administrators, users, and/or purchasers on all software acquisitions using approved AF process such as WOMS.

Conduct periodic/annual compliance visits to base units and tenant organizations to ensure AFI requirements are followed. Inspect at least 50 percent of units annually and inspect each unit at least every 2 years. Provide reports to COR upon request.

Coordinate on all software requirements. Receive all new software and become familiar with license agreements prior to releasing software to FSA/CSTs. Ensure the legal acquisition and use of all software utilized on Columbus AFB. Ensure software has been certified for use on the AFNET and published on the AF EPL or approval is obtained from the DAA for any software placed on computers.

Disseminate semiannual guidance on the processes, procedures, software user agreements and issues related to software management. Guidance should reinforce the legal requirement of maintaining software licenses according to their stated conditions as well as reiterating that noncompliance could result in criminal prosecution due to violation of copyright laws.

Network Coordination & Engineering Provide Engineering & Network Design and technical solutions, IAW para 3.19, using established processes and AF provided AISs. Support implementation of network migration and upgrade plans. Review/coordinate network upgrade plans. Coordinate, with the appropriate Comm squadron office, any equipment expansion to ensure the availability of electrical, HVAC, and other allied support through base Civil Engineers.

Work Order Requirements The Contractor shall comply with the following requirements. Examples of work orders include, but are not limited to, equipment/material purchases, installation of cable plant, organizational moves and ceremonial pubic address. The Contractor shall maintain the installed infrastructure and will not be held responsible for completing third party installations or bringing third party installations up to industry standard unless so directed by issuance of a work order or contract modification. The Equipment and Installation Performance Specification (EIPS) provides descriptions of the material and labor effort required by the attached Pricing Tables A, B, C, D, G and U and identified by PIDs. When an item required to complete a work order is not pre-priced within the Pricing Table (Appendix 6), the Government may negotiate the addition of these items, negotiate a special project (Section 2.8), or opt to use another vehicle (material PID) to accomplish the task. The COR will notify the Contractor of any installation found to be incomplete or not installed according to industry standards.

Work Order Procedures.

Work orders will be prepared as directed by the COR. All work orders shall be reviewed and approved by the COR before work starts. Approval from the CO is required for any work order exceeding $2,500.00 in labor charges or $25,000.00 total. All work orders shall be prepared via a Government provided AIS or in a document or format provided by the government. Work order numbers shall be established by the COR. If necessary, the Contractor shall perform a Technical Solution (See section 3.19) to provide required items needed to accomplish work. The Contractor may be accompanied by Government personnel.

All work orders issued hereunder are subject to the terms and conditions of the contract. In the event of disagreements with any work order, the Contractor shall refer their questions, concerns, or disputes concerning work orders to the COR in writing within 24 hours (two hours for emergencies, eight hours for priorities) of receipt of the work order. If the Contractor and COR cannot agree, the issue will be elevated in writing to the CO for resolution.

Work orders will be accomplished during normal duty hours; however, occasions may arise that require emergency outage work to be accomplished outside of these hours. The Contractor shall be responsible for covering such situations with adequate personnel and completing the work within the stipulated time.

Work Order Classifications.

The COR will classify work orders as routine, priority, or emergency. The COR is authorized to reclassify/reprioritize work orders without cost before work commences. The Contractor shall comply with the time limits listed below from the time of receipt of the work order. However, exceptions to time limits may be allowed, with the written approval of the COR or the CO, with appropriate justification. Failure to obtain materials due to supplier delay is not typically considered an adequate reason for an extension. All cable cut repairs shall be classified as emergency unless determined otherwise by the COR.

Emergency: Respond on work site within 4 hours of notification and complete work as soon as possible upon approval. The COR may provide initial notification to the Contractor verbally, with a written follow-up within 4 hours. The Contractor will keep the COR apprised of emergency work order status.

Priority: Complete within 3 duty days

Routine: Complete within 10 duty days

Public Address System The Contractor shall perform public address (PA) duties. The Contractor shall provide personnel, equipment, tools and materials to install, uninstall and operate the system upon receipt of a work order. The Contractor will coordinate the event requirements with the COR or POC before the event. PA work orders will be considered fee for service.

Capabilities for the PA shall be up to four speakers, podiums and stands; appropriate microphones (up to 2 wired or 1 cordless (regular cordless or lapel), music playing capability (CDs and/or auxiliary audio input) and associated cords.

Required Information on Work Orders Work orders placed under the contract will contain the following information as a minimum:

· Date of preparation.

· Contract number, Task Order number, and work order number.

· CLIN/SLIN/PID, description, quantity ordered, building number, room number, and contract unit and extended prices and total Not-To-Exceed (NTE) price.

· The work order priority and established completion time.

· When completed, Contractor initials and dates of completion for work and applicable work center records.

· Any other pertinent information required to properly document work performed.

· Include the statement “Invoice Work Order Against Funding CLIN(s) _____”

Additions, Relocations and Modifications to premise wiring or devices Additions, relocations and modifications (adds, moves and changes) of premise wiring or devices, to include necessary administrative changes, not directly tied to new facility construction or refurbishment, will be considered fee for service. The contractor will provide premise wiring from a wall outlet to the nearest communications closet. All wiring should be installed with local building/construction and industry codes. Wiring within walls is the primary installation method external conduit or raceway must be approved/coordinated with the COR.

Submittal of Completed Work Orders The Contractor shall provide copies of all completed work orders issued under this contract to the COR by delivering them to a designated location within two duty days of completion.