CIPS PWS FY11-FY15.pdf

38th Cyberspace Engineering Group (38 CEG)

38th CEG/PKE

Tinker Air Force Base, OK 73145-2713

PERFORMANCE WORK STATEMENT

for the

CYBERSPACE INFRASTRUCTURE PLANNING SYSTEM (CIPS)

Date: 14 December 2010

Section 1: DESCRIPTION OF SERVICES/GENERAL INFORMATION

1.1 Introduction

1.2 Background and Overview

1.3 Scope

1.4 Requirements

1.5 Optional Requirements

Section 2: SERVICES SUMMARY

Section 3: GENERAL INFORMATION

3.1 Hours of Operation

3.2 Contractor Personnel

3.3 Security Requirements

3.4 Internal Operating Procedures

3.5 Safety Requirements

3.6 Other

Section 4: GOVERNMENT FURNISHED PROPERTY AND SERVICES

4.1 General

4.2 Government Furnished Services

APPENDIX 1: ABBREVIATIONS, ACRONYMS, AND TERMS

APPENDIX 2: SOFTWARE PROGRAM DETAILS

APPENDIX 3: DELIVERABLES

APPENDIX 4: SOFTWARE AND HARDWARE

APPENDIX 5: SYSTEM DETAILS

Section 1: DESCRIPTION OF SERVICES/GENERAL INFORMATION

1.1 Introduction

This is a Performance Work Statement (PWS) for the sustainment, maintenance and modernization of the Cyberspace Infrastructure Planning System (CIPS). The PWS contains a detailed description of the services required for the continued operation of the premier cyberspace planning and implementation tool for the United States Air Force (USAF).

1.2 Background and Overview

Through technological evolution of enterprise tools, the USAF has continually developed tools and processes to leverage cutting edge technology to enable cyberspace planners to more efficiently and effectively perform management of strategic planning for Base information technology infrastructures. The latest evolution of this capability is found in the current version of CIPS released in 2006. Since that time, CIPS capability has increased in accordance with its Vision Document and according to adjusted needs dictated through the CIPS Configuration Control Board (CCB) and CIPS Oversight Group (CIPSOG).

1.2.1 CIPS is organized based on data elements required to support a lifecycle-based business process that includes cyber infrastructure assessments, requirements management, cost estimates, project planning, prioritization of plans, funding allocation, program management, project management, and documentation of baseline infrastructure changes.

1.2.2 CIPS is the System of Record for:

Official processing of infrastructure related information technology /National Security System (IT/NSS) documents (formally known as Computer Systems Requirements Documents (CSRD) or AF Form 3215).

Air Force wide processing of IT Infrastructure funding requests

Integrated project funding management

Base outside cable plant infrastructure documentation

Communications layer of the Installation Geospatial Information and Services (IGI&S)

1.2.3 Other CIPS capabilities and information include the ability to document IT assets, real property assets, and contracts; perform ad-hoc queries; manage role-based user accounts; link graphical and database information; perform work order management, project management, and portfolio/program management. The CIPS Operational View 1 (OV-1) is in Figure 1.

Figure 1. CIPS OV-1

1.3 Scope

The scope of this effort is to provide all personnel, supervision, consumable supplies (non-office), and transportation, not otherwise identified as Government Furnished Property (GFP) herein, to provide maintenance, sustainment, documentation, and modernization of the CIPS, on both classified and unclassified networks, for the 38 Cyberspace Engineering Group (38 CEG), Tinker AFB, OK. This includes supporting the CIPS to sustain an operational standard of 99% availability during Tinker AFB normal duty hours of 0800 to 1700,(See paragraph 3.1.1).

Services include system software and hardware support to ensure correct and available operation of CIPS and implementation of system enhancements that evolve and expand CIPS capabilities and performance.

1.3.1 Period of Performance: The period of performance of this effort consists of one phase-in period of one (1) month, one base period of 11 months, and four option years.

1.3.1.1 Utilizing the CIPS Transition Plan, the contractor shall work in concert with the incumbent during normal duty hours at Tinker Air Force Base, Oklahoma during the phase-in period. During this time, the Contractor shall familiarize themselves with the CIPS system, architecture, code, hardware, security, and configuration management processes. The Contractor shall not interfere with any on-going O&M activities or development work during this phase-in period.

1.3.2 Place of Performance. Work will be accomplished on-site at Tinker AFB, OK.

1.4 Requirements

1.4.1 Overview. This section identifies requirements for daily CIPS operation and sustainment. It includes requirements for System Support, Lifecycle Support, Additional Support, and Customer Support.

1.4.1.1 Policy Compliance. The Contractor shall adhere to Department of Defense, Air Force, Major Command, Installation, Organizational, or any other Government mandated guidance and directives while developing and maintaining CIPS.

1.4.2 System Support. The Contractor shall provide qualified personnel for the sustainment, maintenance, and operational support of CIPS. This shall include support for system hardware and software, database administration, system technical support, and other support necessary to meet CIPS standard levels of service. System Support shall include daily support for each system as well as backup/recovery. The Contractor shall also provide support for the CIPS EDU, Secure CIPS, CIPSNET, Disconnected CVC (DCVC) and stand-alone CIPS Demo copies. (Software and Hardware information can be found in Appendix 4 and 5.)

1.4.2.1 Daily Support for CIPS. The Contractor shall provide the support and services required to ensure CIPS is available for use by the AF Cyber community.

1.4.2.1.1 The Contractor shall provide database monitoring, administration, and system tuning as necessary to ensure system performance is maximized and that a minimum system availability of 99% is achieved during Tinker AFB normal duty hours for the NIPRNET version of

CIPS.

1.4.2.1.2 The Contractor shall, upon Government notification of system failure or upon the discovery of system failure by Contractor personnel, provide the system troubleshooting and maintenance necessary to restore the systems. The Contractor shall respond within 15 minutes of Government notification of a system failure during normal duty hours at Tinker AFB. The Contractor shall ensure that CIPS is fully operational following troubleshooting and maintenance activities. The Contractor shall restore CIPS to normal functionality within one business day of Government notification of system failure. (Note: troubleshooting and maintenance of the production infrastructure is a Government responsibility).

1.4.2.1.3 Contractor shall ensure that personnel are on-call during non-duty hours to address problems with CIPS should any arise. On-call personnel shall respond to any problem with CIPS within one hour of notification. Response shall either be via personal visit to the facilities where CIPS is housed and/or maintained, or (if available) via remote access to the system. The Contractor shall implement a means by which on-call personnel are automatically notified in the event that the CIPS servers go off line or experience issues that require Contractor intervention.

1.4.2.1.4 The Contractor shall perform database updates and application changes as directed by the Government. The Contractor shall maintain and sustain all Commercial-Off-The-Shelf (COTS) software to support upgrades, testing, production and training CIPS environments. The Contractor shall also ensure that CIPS is compatible with the AF standard desktop configuration.

1.4.2.1.5 The Contractor shall read and evaluate all Government provided Time Compliance Technical Orders (TCTOs) and Time Compliance Network Orders (TCNOs) for their impact on CIPS. The Contractor shall conduct the testing and evaluation necessary to determine impacts to CIPS by the changes/updates/patches detailed in the TCTOs and TCNOs, and provide recommended courses of action to the Government. The Contractor shall also address, with Government assistance as needed, any system impacts caused by un-announced software, application and operating system patches.

1.4.2.1.6 The Contractor shall develop a set of meaningful system performance metrics that provide insight into the performance of the application and database servers and the system as a whole. The Contractor shall submit these metrics for Government approval. The Contractor shall gather the Government approved metrics and provide them to the Government bi-weekly.

The goal of this requirement is to provide continual monitoring of the CIPS system and to provide metrics and statistics that will aid the Government in determining the ability of the system to meet the user load. These metrics shall be updated and expanded, with Government approval or at the request of the Government, as required.

1.4.2.2 Daily Support for CIPS EDU. The Contractor shall provide all support services defined in paragraph 1.4.2.1 (excluding support services defined in 1.4.2.1.3 and 1.4.2.1.6) for the CIPS EDU system, with the exception of the loading of live production data. The Contractor shall ensure that the CIPS EDU system achieves a minimum 99% availability during Tinker AFB normal duty hours.

1.4.2.3 Daily Support for Secure CIPS. The Contractor shall provide all support services defined in paragraph 1.4.2.1 for Secure CIPS.

1.4.2.4 Daily Support for CIPSNET. The Contractor shall provide the support and services required to ensure CIPSNET is available, functional, and supports the ongoing CIPS O&M activities.

1.4.2.4.1 The Contractor shall manage all systems on the CIPSNET to include operating systems, application software, databases, and hardware, with Government assistance as needed.

1.4.2.4.2 The Contractor shall maintain all cabling, switches, and servers that comprise the CIPSNET with Government support as required. This includes all servers and services necessary for upgrade and test efforts, including the client computers that are joined to the CIPSNET.

1.4.2.4.3 Contractor shall perform the management, troubleshooting and system maintenance necessary to ensure all environments on CIPSNET does not accrue more than 80 hours of cumulative downtime in a contract year during normal duty hours.

1.4.2.5 Daily Support for DCVC. The Contractor shall provide support for the Disconnected CVC (DCVC) capability as needed. This support shall include all services necessary to deliver DCVC clients to users when requested, and the importing of the data from the DCVC clients to the enterprise CVC application as needed. The current method for delivering this capability is to use Oracle Virtual Machine (VM). (Software and Hardware information can be found in Appendix 4 and 5.)

1.4.2.6 Daily Support for Demo CIPS. The Contractor shall provide support to the CIPS PMO by creating stand-alone versions of CIPS to be used for Government purposes. This shall involve the loading of the requisite software and data required for a substantially functional copy of CIPS on a Government provided stand-alone client. No requirement exists for the import of data from the demo versions of CIPS to the production database. There are normally no more than two demo versions of CIPS in use at any given time.

1.4.2.7 Backup and Recovery. The Contractor shall, with Government assistance, perform backup and restoration actions of CIPS Production and CIPSNET.

1.4.2.7.1 Backup and Recovery of CIPS Production. The Contractor shall, with Government assistance, perform system backup, recovery, and restoration of services IAW the CIPS Disaster Recovery Plan and the CIPS Server MPTO 31S5-4-7027-1 in the event of a catastrophic system failure or a natural or man-made event that results in damage to, or destruction of, the CIPS production and/or training servers. The Contractor shall verify that system and data backups can be used for restoration purposes IAW the CIPS Disaster Recovery Plan and MPTO 31S5-4- 7027-1. The verification shall ensure the backups are not corrupted, are complete, and are useable for system or data restoration.

1.4.2.7.2 Quarterly Verification of Backup and Recovery Plan. The Contractor shall assist the Government in quarterly verification of the backup and recovery procedures documented in CIPS Disaster Recovery Plan and the CIPS Server MPTO 31S5-4-7027-1. This verification shall be performed by the government at the CIPS facility at Tinker AFB, OK. The Government does not conduct unscheduled disaster recovery exercises requiring direct contractor support.

1.4.2.7.3 Backup and Recovery for CIPSNET. The Contractor shall practice due diligence in conducting source code backups for the upgrade and test baselines on the CIPSNET. These backups shall be accomplished weekly. In the event of a catastrophic system failure or a natural or man-made event that results in damage to, or destruction of, the CIPSNET, the Contractor shall perform necessary recovery actions, with Government assistance, to bring the CIPSNET back to full functionality in an expeditious manner. The Contractor shall also perform a minimum of a weekly backup of support servers on CIPSNET, such as CIPSNET e-mail, software lifecycle management tools, and testing data.

1.4.3 Lifecycle Support. The Contractor shall provide all support, services, testing and documentation in support of the CIPS system lifecycle for all environments.

1.4.3.1 The Contractor shall provide sustainment, maintenance, operational support, and necessary documentation for CIPS system lifecycle support for all CIPS environments. This shall include software bug fixes and enhancements documented in the approved software lifecycle management tool. This shall also include requirements specification support, design, implementation, unit testing, integration and system testing. Defects are initially submitted from the users and captured via an integrated CIPS application. Once evaluated, valid bugs and enhancements are entered into Microsoft Team Foundation Server (TFS). The Government and incumbent also utilize Microsoft Test Manager 2010 to create test cases and enable configuration management.

1.4.3.2 The Contractor shall conduct comprehensive system testing in support of each scheduled software release or application update. The Contractor shall develop and maintain test procedures for new and/or enhanced capabilities. The Contractor shall make these test procedures available for Government use. The Government will perform customer acceptance testing. The Contractor shall provide consultation and support to the Government to facilitate customer acceptance testing.

1.4.3.3 The Contractor shall maintain as current all technical documentation of CIPS Production (NIPRNET and SIPRNET) and CIPS EDU (NIPRNET) systems.

1.4.3.4 The Contractor shall update and release CIPS online help by close of business on the day of a release as part of lifecycle support. The online help files shall be accurate and shall reflect actual step-by-step procedures, screenshots and relevant information required to assist users in using CIPS. The Government will provide final acceptance of help file content as part of customer acceptance testing.

1.4.3.5 The Contractor shall correct and update, with Government approval, any reported errors in existing online help. Updates shall be released within 5 business days of Government approval.

1.4.3.6 The Contractor shall produce CIPS technical orders (T.O.s) for AF publication. The Contractor shall be responsible for creating and updating required T.O.s for CIPS. Currently, there is a requirement to develop and publish a CVC T.O. Work has not started on this T.O. In addition to this, the contractor shall be responsible for the maintenance and updating of all existing CIPS T.O.s , which includes MPTO 31S5-4-7027-1 and TO 00-33D-3003. This also requires the Contractor to maintain any future CIPS T.O.s upon their publication. The Contractor shall work closely with the CIPS PMO when creating or updating T.O.s to ensure that the document(s) produced meet the needs of the AF users. The CIPS PMO must approve all T.O.s prior to submittal for publication, and the CIPS PMO must approve all changes to existing T.O.s prior to submittal for publication. Each existing CIPS T.O. must be updated, at a minimum, yearly.

1.4.3.7 The Contractor shall support the CIPS user community by providing report creation and maintenance expertise. The Contractor shall support the user community by creating ad hoc reports on demand. Ad hoc reports shall be created using the existing ad hoc creation and reporting tool. The current ad hoc report tool is LogiXML AdHoc. The Contractor shall update the ad hoc reporting tool as needed so that it reflects the most current CIPS and CVC database structures. In addition to this, the Contractor shall provide support by writing or updating non-ad hoc reports to meet user demands for reporting or to reflect updates to the CIPS and CVC databases.

1.4.3.8 The Contractor shall document system defects, bugs and enhancements using the approved software lifecycle management tool (as referenced in 1.4.3.1). The contractor shall manage this tool. The Contractor shall attend all system review boards in support of the Government. The Contractor shall provide software defect and reported issues reports to the Government in support of these boards.

1.4.3.9 The Contractor shall coordinate maintenance actions with the appropriate Government POC. The Contractor shall get Government approval prior to taking actions that will impact system performance, functionality or users.

1.4.3.10 The Contractor shall provide recommendations to the Government for replacement/upgrade of equipment on the Production, Training and CIPSNET networks. The Contractor shall install and bring on line new servers purchased by the Government to include realignment of servers from production to CIPSNET.

1.4.3.11 The Contractor shall ensure system security is maintained and upgraded according to DoD and AF regulations.

1.4.3.12 The Contractor shall maintain a single software baseline for use on Production and Training environments, to include third party applications and database connections. The contractor shall update all environments with the same baseline as part of each software release, unless otherwise directed by the Government. The Contractor shall ensure that the classification marking schema is enabled on the classified version of CIPS.

1.4.3.13 Hardware, operating system, and network connections for the production and training systems will primarily be managed by the Government with Contractor coordination.

1.4.3.14 All products and documents produced by the Contractor in support of this contract shall be the property of the Government. The Contractor shall obtain Government approval prior to any use of these products and documents outside of this effort.

1.4.4 Additional Support. The Contractor shall provide additional support, such as technical reviews, participation in working groups, and assurance of CIPS compliance with relevant technical standards.

1.4.4.1 CIPS Team Effort. The Contractor shall participate in working groups as directed by the Government. The Government will prioritize and direct project efforts taking into consideration Contractor input and user priorities.

1.4.4.2 Maintenance of System Architecture. The Contractor shall maintain or improve the System Architecture strategy as prescribed by the Program Management Office.

1.4.4.3 IGI&S Support. The Contractor shall, as required, assist the 38 CEG and the CIPS PMO in support of the Installation Geospatial Information Services (IGI&S) effort. The Contractor shall, at the direction of the CIPS PMO, act as a liaison between the 38 CEG, Headquarters Air Force (HAF) Geospatial Integration Office (GIO), MAJCOM GIOs, other agencies, or users of CVC.

1.4.4.4 Spatial Data Standards Compliance. The Contractor shall ensure database structure is compliant with spatial data standards. The Contractor shall update the Communications Mission Data Set (CMDS) for CVC as directed by the Government.

1.4.4.5 CIPS Account Administration: The Contractor shall provide complete CIPS Account Administration services and support, overseeing and implementing processes necessary to support user account creation, user role requests, user access issues (passwords, CAC, etc), and other related services.

1.4.4.6 User training for CIPS and all of its components: The Contractor shall provide CIPS training to the user community. The preferred training location will be a currently existing Government facility at the 38 CEG. Average class size is 20 students. Other training methods may involve local or remote classroom instruction and/or web-based conferencing. Travel for remote classroom instruction at a user provided, furnished and equipped facility is not to exceed one week per a month. Contractor will be required to provide training materials and instructor.

1.4.5 CIPS Help Desk. The Contractor shall provide Help Desk services in support of unclassified Production and EDU CIPS. The Contractor Help Desk personnel shall:

1.4.5.1 Be available during normal duty hours at a Government-provided Help Desk location collocated with the CIPS team on Tinker AFB, OK.

1.4.5.2 Be available to assist users who walk into the Help Desk location requesting CIPS assistance. On average there are 2 walk-in contacts each week.

1.4.5.3 Screen each phone call to determine the nature of the call. Assist callers with issues and questions regarding CIPS functionality. Monitor voice mail for missed calls and get back with user within one business day of their leaving a message. Provide feedback to user regarding status of submitted or reported issue. On average there are 31 calls and 15 e-mail contacts each week. Since November of 2006 there have been 7,226 help desk contacts.

1.4.5.4 Log, manage, and record final resolution of defects using the approved software lifecycle management tool (as referenced in 1.4.3.1).

1.4.5.5 Log, manage, and process enhancements and Change Requests as directed by the Government using the approved software lifecycle management tool (as referenced in 1.4.3.1).

1.4.5.6 Assist the Government in providing CIPS Account Administration services and support, implementing processes necessary to support user account creation, user role requests, user access issues (passwords, CAC authentication, etc), and other related services.

1.4.5.7 Assist the Government in improving customer support by providing metrics of Help Desk effectiveness and customer satisfaction. The contractor shall develop a means by which Help Desk customer’s satisfaction can be measured. At a minimum, these metrics should measure whether the customer was satisfied with the support from the Help Desk and whether the customer was satisfied with the personnel providing the support (by name). Additional metrics should include type of contact (e-mail, phone, walk-in), number of contacts, area of concern, and MAJCOM of customer making the contact. Metrics shall be delivered to the Government on a bi-weekly basis, and will include running totals by Calendar Year (CY). Note – The CIPS PMO does not use Remedy for trouble calls or tracking.

1.5 Optional Requirements.

This section identifies optional requirements for planned CIPS enhancement and services that the Contractor shall provide or develop and integrate into the existing system. The Contractor shall coordinate changes through Requirement Statements, Use Cases, Storyboards, Prototype testing, or any other means as directed by the Government.

1.5.1 FPC Optional Requirements. The following is a listing of optional requirements for the Financial Planning Component of CIPS. This includes upgrades to WOMS and PMID.

1.5.1.1 Organizational Structure: The Contractor shall redesign the system’s current 3-tiered organizational structure (AF → Major Command (MAJCOM) →Base) to a structure accommodating other entities in the AF and Department of Defense (DoD). The intent is to migrate away from the current hard-coded structure to a ‘virtual’ structure that can be adapted to create, define, manage and display parent-child relationships between organizational entities. Authorized users will have the ability to create new entities and define relationships and business processes. The system shall permit the movement of entities within the structure, along with all related business objects. The goal is to provide an agile organizational structure in CIPS that can be quickly adapted to accommodate changes to missions and alignments, and do so without disrupting day-to-day business functions.

1.5.1.2 Enterprise Dashboard. The Contractor shall upgrade CIPS to include an Enterprise Dashboard functionality that will provide a more aesthetically pleasing view of the blueprints as well as enhanced drilldown capability to data. This enables ease of briefing and access to information. The Enterprise Dashboard will include rollups of infrastructure assessments, program and project management, and financials related to Program Element Codes (PECs).

The Enterprise Dashboards will be integrated with the existing Program and Project dashboards as well as the AF Work Plans and Implementation Plans. The Enterprise Dashboard will function as a focal point for all of the information in the various CIPS components, and shall be customizable by the individual users.

1.5.1.3 Organic Dashboard: The Contractor shall upgrade CIPS to include a dashboard that permits the organic E&I units to view and bid on pending projects across the AF. Integrated functions shall include organic cost estimates, MAJCOM man-day management, assigning workload, and integration into the Work Plan and Implementation Plan processes. Dashboards will also display active and pending Project dashboards assigned to organic units.

1.5.1.4 Rights Based Access: Currently, CIPS requires users to possess one or more roles in order view data and complete various tasks in the integrated system. The Contractor shall replace the current roles-based security model in order to permit access to CIPS based on assigned user rights. These rights will permit them access and/or edit rights to data and business objects in the system, and can be assigned by location. This requires the interface to be intuitive and streamlined, making it easy to manage the rights assigned to a user.

1.5.1.5 Usability Improvements: The Contractor shall implement upgrades to enhance capabilities and improve performance. These upgrades include the following capabilities:

improved email and system notifications, enhanced user query capabilities, digital signatures, and business object cloning. This requirement shall also include improvements to the Graphical User Interface to improve the user experience with CIPS. These improvements shall ensure that information is presented in a clear and easy-to-understand manner, and navigation within the system is more intuitive. The Contractor shall also improve the reporting and export capabilities to ensure users can easily extract data from CIPS in useable formats.

1.5.1.6 AF 1067 Process: The Contractor shall upgrade CIPS in order to incorporate the AF 1067 process into CIPS business flow. The AF 1067 is a form by which users can request modifications to fielded AF systems. The goal of this upgrade is to incorporate the processing of AF 1067s related to the Combat Information Transport System (CITS) modifications. This will include the populating, pre-arranged routing, and processing of AF 1067s. The Contractor shall provide linkage between follow-on business objects to the approved AF 1067, and the enforcement of business rules that would preclude the association of a requirement and follow-on business objects with the CITS PEC and/or Program without an approved AF 1067 for the requirement. This requirement shall permit users to digitally sign the AF 1067s. Although use of the 1067 is primarily intended to support the CITS PMO, the ability to expand the approval process to other programs shall be provided.

1.5.1.7 External System Interface: The Contractor shall upgrade CIPS such that it will accommodate interfaces with other Enterprise Automated Information Systems (AIS), such as Telephone Management System (TMS), Remedy, and AFWAY.

1.5.1.8 WOMS Enhancements: The Contractor shall upgrade WOMS to allow for the creation of additional tiers above the Base level. This will include the ability for MAJCOM and AF level entities to establish Work Centers. Base-level users, with the proper rights, shall be allowed to elevate workload submitted at the base level to a MAJCOM or AF-level work center.

These higher-level entities shall also be able to route workload between themselves. Workload transfer from higher-level entities to lower-level entities shall also be permitted. Also included in this requirement will be the establishment of MAJCOM and AF consolidated Work Center dashboards that will permit the AF and MAJCOMs to quickly access Base-level consolidated Base dashboards for visibility into the activities at the Base Work Centers. Appropriate metrics will be provided that will permit MAJCOMs to compare workload processing at bases associated with them.

1.5.1.9 Automatically Generated WOs in WOMS: The Contractor shall enhance WOMS to provide for the creation of regularly scheduled WOs. This means that an authorized user will be able to create a recurring, automatically generated work order for the completion of a task or some other recurring event. The user shall be able to define the work center responsible for the task and period of time that will elapse between automatic WO generation for the task.

The user shall be able to associate this task to an asset tracked in CIPS.

1.5.1.10 Cross Domain Solution: The Contractor shall assist the Government in the implementation of a plan to transition a portion or all of CIPS from the unclassified network (NIPRNET) to the classified network, SIPRNET. Data will have to flow from NIPRNET to the SIPRNET, as well as from the SIPRNET to the NIPRNET.

1.5.2 CVC Optional Requirements. The following is a listing of optional requirements for CIPS Visualization Component (CVC).

1.5.2.1 CVC Inside Plant: The Contractor shall upgrade CVC to include the Inside Plant (ISP) in order to provide a complete end to end picture of the base-level communications infrastructure (voice, video, data, etc). In essence, a geo-referenced wiring diagram of the Base can be created and overlaid with detailed circuit information, providing maintainers and decision makers with unprecedented situational awareness as well as easy and instantaneous updates as needed. This capability will map the layer 1 port-to-port structure of the Base. It will include the rack elevation diagrams depicting the placement of items in the rack; bubble diagrams depicting building-to-building or asset-to-asset connections and inter-base (long haul) connections. This requirement will tightly integrate the CVC function with the asset management and business process in CIPS. For example, source documents and project dashboards that result in the addition of an asset will be linked to the asset in CVC, and disposition actions in CVC will result in reclassification or removal of the linked business objects in CIPS. Included in this will be the placement of tracked assets in racks, enforcement of the update of CVC for changes to assets that are linked to a CIPS business object, and detailed reporting. Implementing this requirement will include the ability to attach documentation to assets visualized in CVC (both Outside Plant and Inside Plant). This capability will also integrate with the planning functions of CIPS so that planners can claim space in racks or ducts for projects, and be notified if these planned spaces are used prior to the implementation of a project.

1.5.2.2 Enhanced CVC Views: The Contractor shall upgrade CVC to include an enhanced capability to provide for access to CVC data outside of the CVC client. This includes the ability to view and/or brief individual projects in an easy-to-use presentation format. In essence, a version of CVC will be made available to users who do not need the Java client reserved for those who are actively engaged in the day-to-day management of the infrastructure. This enhanced view will be intuitive, easily accessed, and will support data query, search, and the export of reports and data on demand. This enhanced view capability shall be web-based and will not require the use of the CVC client. No editing of the data will be allowed using this new interface. The following summarizes the major requirements for this capability:

View CVC data in web browser without the use of the CVC client

Query and search

Reports and exports

Create project briefings

No updates to CMDS

‘Red line’ capability with annotations for briefings

1.5.2.3 Disconnected CVC (DCVC) Enhancements: Currently, the DCVC will only export the CMDS for an entire GEOLOC (base). The Contractor shall enhance the existing DCVC to allow for the editing of a tightly defined (bounded area) subset of the CMDS for a base. Exported data shall seamlessly import back into the enterprise CMDS. The assets included in bounded area export will be locked for editing in the CVC tool until the data from the DCVC is reintegrated into the CMDS. (Software and Hardware information found in Appendix 4 and 5.)

1.5.2.4 Computer Aided Design (CAD) Linkage to CVC. The Contractor shall upgrade CVC to include a capability that will permit users to link CAD software to the CMDS so that the users can function in the CAD tool and view, update and/or print the CMDS. Targeted CAD software for this capability shall include, at a minimum, AutoCAD 3D Map or the latest CAD standard in use by the AF Community at the time of implementation. The solution shall include both the enterprise CVC and the DCVC.

1.5.3 Optional System Support Services: The Contractor shall provide the following system support services:

1.5.3.1 Extended Help Desk Hours: Provide a full time CIPS Help Desk available outside of the normal duty hours at Tinker AFB, OK. Help Desk personnel shall perform their duties at a Government provided Help Desk location on Tinker AFB, OK., where the Help Desk Personnel will have access to Government phones and the CIPS system. The Contractor shall continue to provide a CIPS Help Desk during normal duty hours at Tinker AFB, OK as specified in 1.4.5, but shall also provide these same services for additional time periods that are outside of normal duty hours for Tinker AFB, OK.

Section 2: SERVICES SUMMARY

Performance Objective

PWS

Paragraph Performance Threshold

Software modernization/ maintenance efforts.

1.4.2.1.4 1.4.3.1 1.4.3.2

Quality: Release meets project specific standards as defined and determined by the Government PMO and agreed upon by the Contractor.

Timely: No more than two (2) missed scheduled software delivery dates per year (not Government-caused) with missed dates being met within five (5) business days.

Maintain and support Disconnected CVC (DCVC).

1.4.2.5

No more than two (2) incidents in a contract year where DCVC data fails to import into CVC after contractor has exhausted all available means to import the data, as agreed to by the Government.

Perform regularly scheduled database backups on the CIPS Production system IAW the CIPS Disaster Recovery Plan.

1.4.2.7.1

Timely: No more than three (3) missed weekly full backups in a contract year with the missed weekly backups being accomplished within three (3) business days from the missed scheduled backups or no more than ten (10) missed daily backups in a contract year. Any missed daily backup must be performed within 24 hours or sooner at the discretion of the Government.

Ensure integrity of database backups.

1.4.2.7.1

Quality: Verify backups can be used for restoration purposes IAW the CIPS Disaster Recovery Plan and TO 31S5-4-7027-1.

Timely: No more than one (1) missed quarterly verification in a contract year (not Government caused), with missed date being met within one calendar month of planned verification date.

Respond to Production and Education system failures within 15 minutes of Government notification of a problem during normal duty hours.

1.4.2.1.2 1.4.2.2

No more than three (3) incidents in a contract year where Contractor failed to respond in the specified time.

Performance Objective

PWS

Paragraph Performance Threshold

Ensure that Production and Education CIPS environments are operational 99% of the time during Tinker AFB normal duty hours.

1.4.2.1.1 1.4.2.2

No more than twenty-four (24) cumulative hours down-time per environment during normal duty hours at Tinker AFB within a contract year.

Maintain CIPSNET and CIPSNET servers.

1.4.2.4 No more than eighty (80) cumulative hours down-time during normal duty hours at Tinker AFB within a contract year.

Provide live on-site Help Desk support during Tinker AFB normal duty hours.

1.4.5

No more than three (3) incidents in a contract year where Help Desk is unmanned for more than four (4) hours during Tinker AFB normal duty hours (excluding PMO-authorized support functions).

Provide and maintain lifecycle documents

1.4.3

Quality: Maintain documents as specified in Table A3.1

Timely: No more than two (2) instances per a contract year where deliverable due date is missed with missed dates being met within 14 business days.

Perform weekly backups of source code for upgrade and test baselines on CIPSNET.

1.4.2.7.3

No more than three (3) missed weekly backups in a contract year with missed backups being accomplished within three

(3) business days.

Section 3: GENERAL INFORMATION

3.1 Hours of Operation

3.1.1 Normal duty hours are Monday through Friday, from 0800 hours to 1700 hours except recognized federal holidays as identified in 5 U.S.C. 6103, and any other day designated as a “Down Day” by the Government. The Contractor will be advised by the Contracting Officer if services are required, in advance of such days. The Government is not obligated to pay for work that is not required on “down days”. Approval shall be obtained from the Contracting Officer if the Contractor chooses to work holidays and/or down days at the regular contract rates. All functions shall be open during normal duty hours.

3.1.2 After Hours Support: The Contractor may utilize time outside of normal duty hours, as needed, in support of the duties required to maintain and sustain CIPS.

3.1.3 The Contractor shall ensure that all employees enter time off into the 38 CEG Employee Information Database or provide comparable, timely notification of Contractor employee absences to the CIPS Program Office.

3.2 Contractor Personnel

3.2.1 Project Manager

3.2.1.1 The Contractor shall provide an individual to act as project manager who shall have full Contractor authority to act in all contract matters related to this PWS. This individual shall be responsible and accountable to the Contracting Officer (CO) in representing the Contractor for meeting the performance requirements of this PWS.

3.2.1.2 The project manager or alternate shall be available during normal duty hours, Monday through Friday, except Federal Holidays, to meet with Government personnel (designated by the contracting officer) to discuss program and/or technical issues.

3.2.1.3 The project manager or alternate shall attend regularly scheduled staff meetings, as requested by the Quality Assurance Personnel (QAP).

3.2.2 Contractor Employees

3.2.2.1 The Contractor shall not employ any person for work on this contract if such employment is identified to the Contractor by the CO as a potential threat to the health, safety, security, general well being, or operational mission of the installation and its population.

3.2.2.2 The Contractor shall employ and maintain a technically trained and experienced work force to fulfill all requirements listed in the Performance Work Statement (PWS) in accordance with DoDI 8570.01M. The referenced DoDI requires that any individual (Contractor, Government Civilian or Military Member) that performs IAT Level 1 and/or IAM Level 1 functions to possess, within 6 months of assignment of duties , specific certifications. For our purposes, we require personnel to possess (at a minimum) CompTIA Network + and CompTIA Security + certifications. The Government will not pay for these certifications.

3.2.2.3 All Contractor employees shall be able to read, write, speak and understand the English language to the extent necessary in the performance of the work.

3.2.2.4 Contractor Common Access Cards (CAC) identified by a vertical green stripe, shall be worn by employees in such a standardized manner as to be clearly visible except when in use (i.e. inserted in a computer CAC reader).

3.2.2.5 The Contractor shall not employ any person who is an employee of the US Government if employing that person would create a conflict of interest. Additionally, the Contractor shall not employ any person who is an employee of the Department of the Air Force, unless such has been approved according to DOD 5500.7-R, Joint Ethics Regulation.

3.2.2.6 The Contractor shall maintain a current listing of employees. The list shall include employee’s name, social security number, and level of security clearance. The list shall be validated and signed by the company Facility Security Officer (FSO) and provided to the contracting officer and Government QAP prior to contract start date. The Contractor shall provide updated listings whenever an employee’s status or information changes.

3.2.2.7 Contractor employees shall identify themselves as contractor personnel by introducing themselves or being introduced as contractor personnel and displaying distinguishing badges or other visible identification for meetings with Government personnel.

In addition, contractor personnel shall appropriately identify themselves as contractor employees in telephone conversations and in formal and informal written correspondence.

3.2.2.8 Base Closures Due to Emergencies. From time to time, the Center or Base Commander may decide to close all or part of the Base in response to an unforeseen emergency or similar occurrence. Such emergencies include, but are not limited to adverse weather such as snow or ice, “An Act of God”, such as tornado or earthquake, or a Base disaster such as a natural gas leak or fire. Contractor personnel are “non-essential personnel” for purposes of any instruction regarding the emergency. Base closure announcements will normally be disseminated by local television and radio stations.

3.3 Security Requirements

3.3.1 The Contractor shall comply with all security and threat related requirements as specified in DOD 5220.22M, National Industrial Security Program Operating Manual (NISPOM);

AFI 31-401, Information Security Program Management; AFI 31-601, Industrial Security Program Management; Tinker Air Force Base Installation Anti-terrorism Plan 10-245; AFI 36-3026, Identification Cards for Members of the Uniformed Services, their Eligible Family Members, and Other Eligible Personnel; TAFBI 31-101, Installation Security Instruction; and TAFB Plan 31-101, Installation Security Plan (2005).

3.3.2 All Contractor employees shall have a SECRET security clearance and must be United States citizens.

3.3.3 The Contract Project Manager or Alternate shall provide the Government Contracting Officer, or their designee, a list of all Contractor employees requiring a Department of Defense Common Access Card (CAC). The list shall identify the full name, date of birth, Social Security Number, and drivers license number or state identification number of each employee. The Government will use that information to initiate CAC applications in the DOD Contractor Verification System (CVS). Contractor employees shall complete the application process as directed by the Government and report to the Military Personnel Flight (MPF) for issue of their CAC when notified by the Government that CAC issue has been approved. The CAC issued shall be displayed, used and surrendered as prescribed by the Government. The Contractor shall ensure that all employees have the proper identification credentials prior to entering Tinker AFB, OK. The Contractor Project Manager shall be responsible to confiscate CACs that were issued to Contract employees no longer supporting this PWS, and surrender to the QAP or CO.

3.3.4 The Contractor Manager or Alternate shall complete an Unescorted Entry Authorization Certificate (AF Form 2586) for each employee requiring entry into controlled areas IAW TAFBI 31-101. The request shall be coordinated through the Wing Information Assurance Office and submitted to Base Pass and Registration. The Government will provide a USAF Restricted Area Badge, AF Form 1199D. The credentials shall be displayed and surrendered as directed in TAFBI 31-101.

3.3.5 The Contractor shall conform to the provisions of the NISPOM for safeguarding classified information.

3.3.6 Not later than five (5) workdays prior to the start of the performance period, or notification of an issuance of security clearances to required Contractor personnel, whichever occurs last, the Contractor and the Government representatives, as designated by the CO, shall conduct a joint inventory of all classified documents and material. The Contractor shall receipt for all items on the inventory.

3.4 Internal Operating Procedures

3.4.1 The Contractor shall follow all established local operating procedures for internal circulation control, protection of resources, and regulation of entry into Air Force controlled/restricted areas during normal, simulated, and actual emergency operations, and any additional direction of 38 CEG leadership.

3.4.2 Pursuant to the NISPOM, the appropriate user agency's Designated Approving Authority (DAA) as referenced in DoD, USAF, and Tinker AFB COMPUSEC directives shall approve operation of communications and computer systems at Tinker AFB. The Contractor shall comply with the established COMPUSEC program to protect classified, sensitive and unclassified information processed in Information Systems (IS), which are furnished to, and operated by, the Contractor. The Contractor shall comply with all existing and future applicable USAF, MAJCOM, and local computer security directives to include AFI 33-202V1, Network and Computer Security, AFI 33-203, Emission Security; AFI 33-114, Software Management; Air Force Systems Security Instruction (AFSSI) 5024 Volumes I-IV (the Certification and Accreditation Process); and AFSSI 5027, Network Security Policy.

3.4.3 Accreditation of Systems

3.4.3.1 The Government will ensure accreditation of all computer systems using the DoDI

8510.01 bb, Department of Defense Information Assurance Certification and Accreditation Process (DIACAP).

3.4.3.2 The Contractor shall comply with the established Information Assurance (IA) Program to integrate security education, training, and awareness covering the COMSEC, COMPUSEC and Emission Security (EMSEC) disciplines. All Contractor employees shall successfully complete Information Assurance Awareness Program (IAAP) training (a network user computer based training course) and complete OC-ALC Form 532 prior to obtaining access to the Base local area network. Upon termination of an employee the Contractor shall notify 72nd Communications Squadron (72 CS) within two duty hours and request that the employee’s network access be terminated. 72 CS reserves the right to terminate the Contractor’s access to the Tinker network at any time to preserve network integrity.

3.4.4 Physical Security Controls

3.4.4.1 The Contractor shall establish and implement methods of ensuring that all keys/key cards issued to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons. NOTE: All references to keys include key cards. No keys issued to the Contractor by the Government will be duplicated. The Contractor shall immediately report the occurrences of lost or duplicate keys to the CO. In the event keys, other than master keys, are lost or duplicated, the Contractor shall, upon direction of the CO, re-key or replace the affected lock or locks; however, the Government, at its option, may replace the affected lock or locks or perform re-keying. When the Government performs the replacement of locks or re-keying, the total cost of re-keying or the replacement of the lock or locks shall be deducted from the payment due the Contractor. In the event a master key is lost or duplicated, the Contractor will replace all locks and keys for that system and the total cost deducted from the payment due the Contractor. The Contractor shall prohibit the use of Government issued keys by any persons other than the Contractor's employees. The Contractor shall prohibit the opening of locked areas by Contractor employees to permit entrance of persons other than Contractor's employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the CO. The Contractor shall ensure turn in of keys by Contractor personnel who no longer require access to locked areas.

3.4.4.2 The Contractor shall control access to all Government provided lock combinations to preclude unauthorized entry.

3.5 Safety Requirements

3.5.1 General Safety Requirements

3.5.1.1 Safety Program Requirements. The Contractor shall implement a safety program that ensures protection of Government personnel and property. The program will address as a minimum, the Safety Program Elements listed in paragraph 3.6.2, and shall be used during performance of the work described in the PWS.

3.5.1.2 Mishap Notification

3.5.1.2.1 The Contractor shall notify the QAP or 38 CEG Safety Office within one (1) hour of all mishaps or incidents. A written report of the mishap/incident shall be sent within three calendar days to the QAP, who will forward it to the 38 CEG Safety Office.