CIPS_PWS _FY16-21.docx

38th Cyberspace Engineering Installation Group (38 CEIG)

38 CONS/LGCC

Tinker Air Force Base, OK 73145-2713

PERFORMANCE WORK STATEMENT

for the

CYBERSPACE INFRASTRUCTURE PLANNING SYSTEM (CIPS)

Date: 6 Nov 2015

DESCRIPTION OF SERVICES

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).

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 and managers 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 (IAW) its Vision Document and according to adjusted needs dictated through the CIPS Local Configuration Control Board (LCCB) and CIPS Oversight Group (CIPSOG).

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.

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)

Other CIPS capabilities and information include the ability to document IT assets, real property assets, and contracts; manage user accounts and permissions; 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

Scope The scope of this effort is to provide all personnel, supervision, consumable supplies (non-office), and transportation, not otherwise identified as Shared Property or 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 Installation Group (38 CEIG), 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.3.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.

Requirements

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

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.

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, CIPSNET, and stand-alone CIPS Demo copies. (Software and Hardware information is documented in Appendix 4 and 5.)

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.

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.

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).

Contractor shall ensure that personnel are on-call during non-duty hours to address any problems encountered with CIPS, that requires remote or onsite access, if feasible. On-call personnel shall respond to any problem with CIPS within one hour of notification. Contractor shall coordinate with Government personnel to determine the best method to address the problem and act accordingly.

The Contractor shall perform database updates and application changes. 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.

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.

The Contractor shall develop a set of meaningful system 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 Contracting Officer Representatives (COR) approval. The Contractor shall gather the Government-approved metrics and provide them to the COR bi-weekly, as part of the Progress and Status Report (see CDRL A005, Table A3.1). 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 COR approval, quarterly.

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 and providing system metrics. The Contractor shall ensure that the CIPS EDU system achieves a minimum 99% availability during Tinker AFB normal duty hours.

Daily Support for Secure CIPS. In the event of a stand-up of a secure instance of CIPS on SIPRNET (Secure CIPS), the Contractor shall provide all support services defined in paragraph 1.4.2.1 for Secure CIPS.

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

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

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.

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.

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.

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

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 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 quarterly that system and data backups can be used for restoration purposes IAW the CIPS Disaster Recovery Plan. The verification shall ensure the backups are not corrupted, are complete, and are useable for system or data restoration.

1.4.2.6.2 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.

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

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. Once evaluated, the Contractor shall enter valid bugs and enhancements into Microsoft Team Foundation Server (TFS) promptly. The Government and Contractor also utilize Microsoft Test Manager to create test cases and enable configuration management.

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 the Government’s use in performing customer acceptance testing. The Contractor shall provide consultation and support to the Government to facilitate customer acceptance testing.

The Contractor shall maintain as current all technical documentation of CIPS Production (NIPRNET and SIPRNET) and CIPS EDU (NIPRNET) systems, (to include the Software Design Description (SDD) - A001, and Database Design Description (DBDD) - A002, per Table A3.1).

The Contractor shall update and release CIPS online help (see Table A3.1, A006, Updated 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 COR will provide final acceptance of help file content as part of customer acceptance testing.

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

The Contractor shall produce and maintain CIPS technical orders (TOs) for AF publication. The Contractor shall be responsible for creating and updating required TOs for CIPS. This also requires the Contractor to maintain any future CIPS TOs upon their publication. Currently, there are four (4) CIPS TOs. The contractor shall review each CIPS TO, at a minimum, yearly, then update as required. The Contractor shall work closely with the COR when creating or updating TOs to ensure that the document(s) produced meet the needs of the AF users. The Contractor shall make all TO updates within 5 working days of COR’s request.

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. In addition, 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 databases.

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.

The Contractor shall coordinate maintenance actions with the COR. The Contractor shall get CO’s approval prior to taking actions that will impact system performance, functionality, or users.

The Contractor shall provide recommendations to the COR 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.

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

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 COR.

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

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

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.

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

Maintenance of System Architecture. The Contractor shall maintain or improve the System Architecture strategy as prescribed by COR via the Program Management Office (PMO).

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

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 COR.

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 permissions, user access issues, and other related services.

User training for CIPS and all of its components: The Contractor shall provide CIPS training, to include all capabilities, to the user community. The preferred training location will be a currently existing Government facility at the 38 CEIG. Other training methods may involve local or remote classroom instruction, AF Keesler AFB Schoolhouse support, and/or web-based conferencing. Contractor shall schedule, coordinate, and conduct training for all CIPS components. The Contractor shall coordinate with Government personnel to insure class size does not exceed training resources and facilities. Travel for remote classroom instruction at a user provided, furnished and equipped facility shall not exceed 50% of work schedule. The COR will review and approve training schedule and activities. Contractor shall provide the instructor. Government will provide subject matter experts as needed. Contractor shall produce and maintain training materials, to include, instructor materials, classroom materials, and videos, using tools and supplies provided by the Government (see CDRL A007, CIPS Training Materials, in Table A3.1). The COR will review and approve all training materials for sufficiency and accuracy.

System Metrics: The Contractor shall provide, to the COR on a monthly basis, metrics related to the utilization of the system. The metrics shall be provided via a medium agreed upon by the COR, preferably as database queries that are accessible, readable, and reusable by the CIPS PMO, via web-based graphical user interface (GUI), and shall contain the following data:

Number of Active Accounts. Metric shall be in the form of a line graph and shall contain six months of data, with the current month and the five previous months’ worth of data included.

Number of Requirements Submitted. Metric shall be in the form of a line graph and shall contain six months of data, with the current month and the five previous months’ worth of data included.

Dollar Value of Cost Elements in System. Metric shall be in the form of a line graph and shall contain six months of data, with the current month and the five previous months represented. Metric shall be divided into active Cost Elements and completed Cost Elements.

Number of Project Binders in System. Metric shall be in the form of a line graph and shall contain six months of data, with the current month and five previous months represented.

Number of ISP Assets in System. Metric shall be in the form of a line graph and shall contain six months of data, with the current month and five previous months represented.

Number of New Accounts: Metric shall be in the form of a line graph and shall contain six months of data, with the current month and five previous months represented.

Number of Submitted Work Orders: Metric shall be in the form of a line graph and shall contain six months of data, with the current month and five previous months represented.

Number of Work Orders in System. Metric shall be in the form of a line graph and shall contain six months of data, with the current month and the five previous months represented. Metric shall be divided into active Work Orders and completed Work Orders.

Number of Organizations with Work Orders in System. Metric shall be in the form of a line graph and shall contain six months of data, with the current month and five previous months represented.

Number of Work Orders by Command Organization. Metric shall be in the form of a bar graph, with the x-axis representing individual Command Orgs. All work orders (active and complete) will be included in the metric. Graph shall also contain a total of all work orders in the system.

Number of Manholes in System. Metric shall be in the form of a line graph and shall contain six months of data, with the current month and five previous months represented.

Total Sheath Count in System. Metric shall be in the form of a line graph and shall contain six months of data, with the current month and five previous months represented.

Total Miles of Sheaths in System. Metric shall be in the form of a line graph and shall contain six months of data, with the current month and five previous months represented.

Total Miles of Ducts in System. Metric shall be in the form of a line graph and shall contain six months of data, with the current month and five previous months represented.

Total Number of Ducts in System. Metric shall be in the form of a line graph and shall contain six months of data, with the current month and five previous months represented.

1.4.5 CIPS Help Desk. The Contractor shall provide Help Desk services in support of 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. If unforeseen circumstances prevent this (i.e. weather, power outages, etc), Contractor Help Desk personnel may temporarily work from another location to ensure coverage.

1.4.5.2 Provide these same services outside of normal duty hours at Tinker AFB, OK, during the following times: a) Monday through Friday, 0300 – 0800 hrs and 1700 – 2100 hrs. If unforeseen circumstances prevent this (i.e. weather, power outages, etc), Contractor Help Desk personnel may temporarily work from another location to ensure coverage.

1.4.5.3 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.4 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 213 contacts each week.

1.4.5.5 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.6 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.7 Provide CIPS Account Administration services and support, implementing processes necessary to support user account creation, user role requests, user access issues, and other related services.

1.4.5.8 Assist the Government in improving customer support by providing metrics of Help Desk effectiveness and customer satisfaction. The contractor shall utilize 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 (i.e. e-mail, phone, walk-in), number of contacts, area of concern, and MAJCOM of customer making the contact. Metrics shall be delivered to the COR on a bi-weekly basis, and will include running totals by Calendar Year (CY). Note –Remedy is not used for trouble calls or tracking.

Special Projects.

This section identifies special projects planned for 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 COR.

1.5.1 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.2 SIPRNET CIPS Implementation: The Contractor shall assist the Government in the creation and implementation of a plan to transition a portion or all of CIPS from the unclassified network (NIPRNET) to the classified network, SIPRNET. Requirement may involve flow of data from NIPRNET to the SIPRNET, as well as from the SIPRNET to the NIPRNET.

1.5.3 CIPS Visualization Component (CVC) Migration to CIPS: The Contractor shall upgrade CVC, with the intent to integrate with CIPS 5.0, to include an enhanced capability to provide for access to, and edit, 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

· ‘Red line’ capability with annotations for briefings

SERVICES SUMMARY

Performance Objective

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.

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.

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

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.

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

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.

GENERAL REQUIREMENTS

Period of Performance The period of performance of this effort consists of one transition period of one (1) month, one base period of 11 months, and four option years.

Place of Performance Work will be accomplished on-site at Tinker AFB, OK, unless Government approval has been granted for specific Contractor employees to work from another location.

Hours of Operation

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 CO if services are required in advance of such days. All functions shall be open during normal duty hours.

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.

The Contractor shall ensure that all contract employees working on site at Tinker AFB, OK enter time off into the 38 CEIG Employee Information System (EIS) Database.

Contractor Personnel

Project Manager

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 CO in representing the Contractor for meeting the performance requirements of this PWS.

The project manager or alternate shall be available during normal duty hours, Monday through Friday, except Federal Holidays and any day designated as a “Down Day” by the Government, to meet with the COR to discuss program and/or technical issues.

The project manager or alternate shall attend regularly scheduled staff meetings, as requested by the COR.

Contractor Employees

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.

DoDI 8570.01M requires that any individual (Contractor, Government Civilian or Military Member) that performs IAT Level 1 and/or IAM Level 1 functions to possess specific certifications. The Contractor shall assume these functions and shall provide technically trained and certified personnel to fulfill all requirements listed in the PWS IAW referenced DoDI. For our purposes, we require personnel to possess (at a minimum) CompTIA Security + certifications.

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.

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).

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.

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 CO and COR prior to contract start date. The Contractor shall provide updated listings whenever an employee’s status or information changes.

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.4.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.

Freedom of Information Act (FOIA) Program. All official Government records affected by this contract are subject to the provisions of the FOIA, 5 U.S.C. 552/DoD 5400.7-R/AF Supplement. Any request received by the Contractor for access/release of information from these records to the public (including Government/Contractor employees acting as private citizens), whether oral or in writing, shall be immediately brought to the attention of the CO for forwarding to the Base FOIA Manager to ensure proper processing and compliance with the Act.

Government Provided Training. The Government will provide the required Government unique training as defined by Air Force and DoD directives. This training is mandatory for all Contractor employees. The Government will provide the necessary equipment with access to accomplish mandatory Government unique training no later than 10 workdays after contract start date, unless mandatory completion dates dictate otherwise. All employees, including newly hired within the course of the contract period, will meet mandatory training within 10 days from the date the Government provides necessary equipment with access. The Contractor may request additional Government training/certification (at Contractor expense) through the CO. The Government will provide technical training for new Government furnished equipment, requirements or technologies not addressed in this PWS, as determined by the CO. This training will be provided only to an initial cadre of Contractor personnel requiring specialized formal training, not to exceed 25 percent of the affected personnel. The Government will be responsible for all approved costs associated with the training.

3.4.5 Continuation of Essential DoD Contractor Services During Crisis. This requirement has been determined not to be mission-essential and does not require continued support during a crisis as defined by Department of Defense Federal Acquisition Regulation Supplement (DFARS) 237.7600.

3.4.6 Government Reimbursement for Travel/Per Diem. Subject to the provisions below, the Government will reimburse the Contractor for travel/per diem expenses incurred by Contractor personnel in the course of official temporary duty (TDY). Prior approval by the CO is required. If Government transportation is not available or authorized, the Contractor shall use the most economical yet expeditious means of travel to, from and at the site. Government quarters, dining facility, and transportation shall be utilized if available. The Government does not reimburse for local travel in the TDY area. Statement of Non-Availability is issued by the Government and shall be required if Government quarters are not available. The Contractor shall be responsible for making all necessary travel and lodging arrangements. Reimbursement rates shall be the same as those applicable to Government Civil Service employees IAW Joint Travel Regulations (JTR), Volume 3. Within 5 workdays after the return of the persons who performed the travel, the Contractor shall furnish the COR all required supporting documentation of actual travel/per diem expenses, including the cost, if any, of transporting equipment and materials required at the sites. Reimbursement thereafter by the Government for travel/per diem expenses will be IAW, but not exceed the limits of, the JTR.

3.4.7 Publications and Forms. The Contractor shall obtain the publications and forms expressly required to perform the work in this contract via internet at www.e-publishing.af.mil. In the event that a form or publication is not available online, the COR will provide it to the Contractor upon written request (e-mail is acceptable) by the Contractor.

3.4.8 In the event that laws, regulations, technical orders, or official instructions or directives change during the term of the contract, the Contractor shall comply with the changes as they come into effect.

Section 508 of the Rehabilitation Act The Contractor shall meet the requirements of the Access Board’s regulations at 36 CFR Part 1194, particularly 1194.22, which implements Section 508 of the Rehabilitation Act of 1973, as amended. Section 508 (as amended) of the Rehabilitation Act of 1973 (20 U.S.C. 794d) established comprehensive requirements to ensure: (1) Federal employees with disabilities are able to use information technology to do their jobs, and (2) members of the public with disabilities who are seeking information from Federal sources will be able to use information technology to access the information on an equal footing with people who do not have disabilities.

Contractor Manpower Reporting.

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

3.7 Non-Personal Services.

The Government shall neither supervise contractor nor control the method by which the contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual contractor employees. It shall be the responsibility of the Contractor to manage its employees and to guard against any actions that are of the nature of personal services, or give the perception of personal services. If the Contractor believes that any actions constitute, or are perceived to constitute personal services, it shall be the Contractor’s responsibility to notify the CO immediately.

SPECIAL REQUIREMENTS

4.1 Security Requirements

4.1.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).

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

4.1.3 The Contract Project Manager or Alternate shall provide the CO or COR 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 driver’s 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 COR or CO.

4.1.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.

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

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

4.2 Internal Operating Procedures

4.2.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 CEIG leadership.

4.2.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-200, Information Assurance (IA) Management; AFMAN 33-153, Information Technology (IT) Asset Management; Air Force Systems Security Instruction (AFSSI) 5024 Volumes I-IV (the Certification and Accreditation Process).

4.3 Accreditation of Systems

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).

4.3.2 The Contractor shall comply with the established Information Assurance (IA) Program to integrate security education, training, and awareness. All Contractor employees shall successfully complete Information Assurance Awareness Program (IAAP) training (a network user computer based training course) and complete the required forms prior to obtaining access to the Base local area network. Upon termination of an employee, the Contractor shall notify the COR within two duty hours and request that the employee’s network access be terminated. AF reserves the right to terminate the Contractor’s access to the Tinker network at any time to preserve network integrity.

4.4 Physical Security Controls

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.

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

4.5 Quality Control

4.5.1 Quality Control Plan. In compliance with Federal Acquisition Regulation (FAR) Clause 52.246-4, entitled Inspection of Services, the contractor shall establish, deliver, and maintain a Quality Control Plan (QCP) to ensure the requirements of this contract are provided as specified (see CDRL A008, QCP, in Table A3.1).

4.5.2 Quality Assurance. The Government will periodically evaluate the Contractor's performance by appointing CORs to monitor performance to ensure services are received. Subsequent to contract award, the identity of the COR(s), with a letter defining their duties and authority will be promptly furnished to the Contractor. The COR(s) will evaluate the Contractor's performance through intermittent on-site inspections of the Contractor's quality control plan. The COR(s) may inspect each task as completed or increase the number of quality control inspections if deemed appropriate because of repeated failures discovered during quality control inspections. Likewise, the COR(s) may decrease the number of quality control inspections if merited by performance.

4.6 Safety Requirements

4.6.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.

4.6.2 Mishap Notification

4.6.2.1 The Contractor shall notify the COR or 38 CEIG Safety Office within one (1) hour of all mishaps or incidents that occur while working on a Government facility. A written report of the mishap/incident shall be sent within three calendar days to the COR, who will forward it to the 38 CEIG Safety Office. For information not available at the time of initial written report, the Contractor shall provide the remaining information no later than 20 calendar days after the mishap, unless extended by the 38 CEIG Safety Office.

4.6.2.2 Mishap notifications shall contain, as a minimum, the following information:

a. Contract, Contract Number, Name and Title of Person(s) Reporting

b. Date, Time and exact location of accident/incident

c. Brief Narrative of accident/incident (Events leading to accident/incident)

d. Cause of accident/incident, if known

e. Estimated cost of accident/incident (material and labor to repair/replace)

f. Nomenclature of equipment and personnel involved in accident/incident

g. Corrective actions (taken or proposed)

h. Other pertinent information

4.6.2.3 If requested by the COR or 38 CEIG Safety Office the Contractor…