Cat4506-E_install_SOW_Final.pdf

NETCENTS-2 SOLUTIONS

Application Services – Full & Open / Small Business Companion

Cisco Catalyst 4506-E Equipment and Installation Statement of Work

(SOW)

Name: Douglas F. Gulick

Organization: 10th Communications Squadron (CS)

Address: 4199 Academy Drive, USAF Academy, CO 80840

EXECUTIVE SUMMARY

USAFA desires to contract for supply of new Cisco OEM Catalyst 4500E series switches and installation services. USAFA currently operates a network with 37 existing Cisco Catalyst 4500 series chassis. The existing chassis go end of support from Cisco in Jul 31, 2015. Purpose of this SOW is to have contractor supply new chassis, supervisors and line cards to upgrade all existing non-E-series chassis to ones that are supported by Cisco. In addition, USAFA has eight existing 4506-E series chassis and a number of line cards, that are still supported by Cisco, being provided as GFE.

NETCENTS-2 Systems Sustainment PWS USAFA Microsoft Premier and Sharepoint

Migration

1) PURPOSE

The 10th Communications Squadron operates the USAFA.edu network supporting 7500 cadets, faculty and staff. USAFA currently has about 250 wired switches. The switches are primarily Cisco Catalyst 3560, 3750, 450x, 650x and Nexus 5500 and variants (3560C, 3560G, 3560X, etc). Of these, there are two (2) Catalyst WS-C4503, two (2) Catalyst WS-C4507R and thirty three (33) Catalyst WS-C4506 chassis that have reach end of support (EOS) from Cisco. The project outlined in the SOW is to upgrade all of these switches to supported E-series chassis and corresponding line cards.

2) SCOPE

The purpose of this SOW is to provide US Air Force Academy (USAFA) with Cisco OEM hardware and installation services to replace existing switches with the new hardware. No other equipment, to include other Cisco switches or wireless network hardware is covered under this procurement.

3) REQUIREMENT(S)/DESCRIPTION OF SERVICE(S)

Contractor shall provide e q u i p m e n t a n d man-hours for collection of existing configurations, designing replacement hardware, configuring the modular chassis with new hardware, to include GFE equipment, removing existing switches and installing new switches in its place and ensuring users connected to the new switch function at least the same way they did on the original switch.

a. USAFA also has an Aruba wireless infrastructure with approximately 700 access points. In most cases the wireless network relies on physical connections to existing wired network switches.

Except in cases where access points currently connect to Cisco 450x switches, this SOW will not affect the existing wireless network. Existing switches are not PoE capable. Existing APs are powered off of external PowerDSine power injectors. The new Cisco 450x-E switches shall have at least two 48-port PoE blades per chassis. Existing APs shall be connected to the new switches on PoE ports and the existing PowerDSine power injectors shall be removed. Moving APs from present ports to a PoE port may require reconfiguration of some switch ports.

b. USAFA IT personnel have spent considerable time implementing DISA STIGs and NSA security configuration templates. Every port that meets requirements for IEEE 802.1x port security should have it turned on. If during the course of this project, the contractor finds any ports without 802.1x port security turned on, they shall identify those ports to the Government. The Government will be responsible for taking corrective actions on those ports.

c. USAFA has broken the tasks required to accomplish the strategic direction into three separate tasks: 1) Engineering and System Design; 2) provide hardware; 3) Installation, configuration and testing. A listing of all 37 existing Cisco 450x switches to be replaced under this SOW is provided in Appendix A. Included are their current name, model, supervisor, line cards, location, room numbers and types and number of current GBICs installed.

1) Engineering and System Design: This task consists of analyzing existing switch and cabling configurations; and then developing technical solutions and configurations.

a) Analyze existing communications capabilities. Contractor shall survey existing switch installations and document existing network infrastructure (equipment, cable, locations, etc.) as well as power and environmental support. Documentation shall be in Microsoft Office compatible formats (Word, Excel and/or Visio).

b) Design Criteria. Contractor shall consider the following criteria when developing their system design.

I. Re-use of existing Supervisor cards. The 4013+ supervisor cards shall not be re-used. While the 4516-10GE supervisor card is supported in the E-series chassis, the contractor shall not re-use them in the new switches. The announced EOL of these supervisors is 31 Oct 2017 and end of security patch releases Oct 2015. All GFE supervisors used shall be either C45 Sup 6E or C45 Sup 7L-E. Contractor shall supply same supervisors as GFE or higher.

II. Re-use of existing Line cards. The existing WS-X4148, 4148-RJ, 4148- RJ45V, WS-X4306 and WS-X44xx (qty 98) line cards shall not be reused.

After completion of this project, all RJ45 line cards shall be 10/100/1000 Mbps.

The GFE WS-X4548-GB-RJ45 (qty 33), and WS-X4548-GB-RJ-45V (qty 2) line cards, like the 4516-10GE supervisor module, are announced as end of life on 31 Oct 2017. These cards can be re-used in new E-series chassis or used to satisfy the spare line card requirement of paragraph 2.2.1.4.

III. Re-use of existing Power Supplies. All new chassis shall have at least two PoE line cards and hence the power supplies shall be PoE support rated. No existing non-E series chassis power supplies shall be re-used. All new chassis shall come with two PoE rated power supplies. Power supplies shall be sized to support five line cards (two 48-port PoE, three 48-port non-PoE), one Supervisor and 24 of the PoE capable ports configured for 7 W PoE devices.)

IV. Switch Operating System. Most of the current 450x switches run IOS 12.2(54) SG1. It is expected that the new switches will be running an IOS 15 or XE version. Contractor shall convert existing 12.2 configurations into appropriate syntax for the version of IOS chosen. USAFA desires all switches to be running the latest common available IOS across the Supervisor modules in use. All like supervisors (e.g. all Sup 6E) shall all run the same version of IOS. DISA security implementation guides (STIGs) require all switches run the latest known OS with no known vulnerabilities. Contractor shall use versions of IOS that meet these criteria.

V. GBICs and Fiber Connections. Existing cards use older style SC type GBICs and connectors for fiber cabling. Connections to existing patch panels terminate with ST connectors. Contractor shall provide new fiber cabling with correct connectors for new switch and fiber GBICs. Current fiber jumpers are between 3 meters and 10 meters in length. Contractor shall not use bulkhead connectors or other adapters to convert fiber connection. Any existing fiber jumpers, which may include existing bulkhead/adapters, shall be removed and replaced with a single cable terminating at existing demark fiber patch panel.

If existing fiber is labeled with a circuit identifier, than new fiber jumpers shall be labeled with the identical circuit identifier. For any fibers found without a circuit identifier, contractor shall request Government provide a circuit identifier and cables shall be labelled using the supplied number.

c) Develop Technical Solutions/Configurations: Contractor shall develop technical solution to facilitate switch replacement.

I. Identify installation location of all new equipment to include any changes to power and heat loads.

II. Using copies of current switch configurations, contractor shall provide configuration files for the new switch. An example existing switch configuration is provided in Appendix C. New configurations shall account for syntax changes, feature changes or other potential problems.

III. Develop a schedule for cutover of switches. Schedule shall include dates and timeframes since outages will have to be scheduled with customers during non-duty hours.

IV. Provide government support requirements. If needed, USAFA will provide a work area for storage of materials and any pre-staging for installation work.

Contractor shall identify how much space they need. If requested, USAFA will also provide a Class C telephone (on-base calling only) for contractor use.

Contractor shall identify any requirements for additional storage space, work space or telephone support.

2) Provide Hardware/Software. Contractor shall provide all necessary switches, line cards and cabling required to complete this SOW.

a) 10 Gbps Uplinks. Contractor shall provide 10 Gbps GBICs or twinax cabling to connect the following switches at 10 Gbps. Switches needing 10 Gbps GBICs are 5210EDS0000, 5212ESS0000, 5214ESS0000. Contractor shall also provide a matching SFP+ 10 Gbps GBIC to be installed in a Nexus 5548 located in building 5130. One switch needing a 10 Gbps twinax cable is 5130ESS0000. It will connect into a Nexus 5548 collocated in building 5130. Contractor shall work with Government personnel to ensure the Nexus 5548 ports are configured properly.

b) Scheduled 10 Gbps Uplinks. Currently the following 450xs are connected back to bldg. 2354, room 2H25 over multimode cable using LH GBICs and a “conditioning” cable to convert from single mode to multimode fiber. The length of the multimode cable exceeds the distance for standard multimode GBICs. USAFA has work orders in to install single mode fiber from bldg. 2354 room 2H25 to each of these closets.

Contractor shall provide 10 Gbps single mode GBICs for the new 450x switches as well as compatible 10 Gbps SFP+ GBICs for the Nexus 5548 located in room 2H25 as described in paragraph 3.c.2.a. In the event the single mode fiber is not installed in time to connect these switches up at 10 Gbps to the Nexus switch, USAFA will provide 1 Gbps SFP GBICs for these switches to run over the existing connections.

The switches are: 2302ESS161A, 2354ESS2E42, 2350EDS2022, 2354ESS1J19, 2354ESSLib_Outdoor and 2354ESS2E11.

c) 1 Gbps Uplinks. Unless identified in paragraph 3.c.2.a or 3.c.2.b, all other switches shall use 1 Gbps GBICs for their uplinks. Contractor shall supply new 1 Gbps GBICs for 450x-E chassis when the present SC connector GBICs will not work. As current uplinks are all running at 1 Gbps, contractor does not need to supply new GBICs for the up or down channel switches that new switch connects to unless the switch is a 4500 being replaced under this SOW.

d) Spares. Enough line cards shall be included so that when complete there are at least seven spare 48-port 10/100/1000 line cards (approx. 5% of total line cards). At least one of them shall be a PoE capable card. There shall be at least one spare supervisor card of each type. The second Sup 6E in a 4507R-E chassis can be considered a spare for purposes of this requirement. Contractor shall supply two spare PoE rated power supplies.

e) Blank Panels. Once installation is complete, contractor shall ensure that there are no “open” card slots in any chassis. If not occupied by a line card or Supervisor, slot shall have a blank panel installed to ensure proper airflow and cooling of the switch.

f) SMARTNET Maintenance support. All new equipment shall come with one year of Cisco SMARTNET 8x5xNBD maintenance.

g) GFE Switches. In FY 14, USAFA ordered nine WS-C4506E-S7L chassis with one WS-X45 Sup 7L-E supervisor, two 4648-RJ45V+E, three 4648-RJ45-E line cards and two PWR-C45-1300ACV power supplies per chassis. Two of those have been installed by USAFA personnel. Seven are available for this project. In addition, USAFA obtained one used WS-C4507R-E chassis from another AF organization. The 4507R-E chassis includes 2 Sup 6-E Supervisor, and 2 PWR-C45-4200ACV power supplies. In addition, there is one WS-X4548-GB-RJ45V line card available in this chassis. The Government will make all of these chassis, supervisors and line cards available to contractor for re-use for this project. List of GFE parts is provided in tabular format in Appendix B.

h) Equipment Accountability. Contractor shall have all new equipment procured under this contract delivered to USAFA’s IT accountability warehouse so that equipment can be properly added to USAFA’s IT account before it is installed. Contractor shall arrange for pickup of the equipment from the warehouse with 10 CS/SCXPCI for configuration and installation.

3) Installation and configuration of new capabilities.

a) Installation. Contractor shall transport switch to installation location. Contractor shall un-install old switch and any unnecessary cabling or other mounting materials.

Contractor shall mount a new switch in selected location and make all connections (power, fiber and network (i.e. CAT 6)) to restore network connectivity to all users of the old switch. Contractor shall transport old switch back to an agreed to area for turn in to 10 CS/SCXPCI.

b) Cable Clean up. Contractor shall make best effort to clean up and dress all cables being reconnected to the new switch. Contractor shall use Velcro or similar product to bundle cables together.

c) Connection Test. Contractor shall power on the switch and verify switch can pass traffic to all other switches connected to it.

d) Network Management systems connectivity. Contractor shall verify switch can pass traffic to the TACACS and RADIUS servers. Contractor shall verify network administrators can log into the switch using a TACACS account. Contractor shall verify USAFA’s network management server (Solarwinds) has connectivity to the switch and all other switches connected to it.

e) Client Connectivity. If possible, contractor shall verify a user computer in the area serviced of the new switch has network connectivity.

f) Equipment Labelling. Contractor shall affix a label to each switch. Label shall identify the switches name and management IP address. Label shall be clearly visible from front of switch after all cabling is connected.

g) Comm closet clean-up. Contractor shall clean up the comm closet and remove all materials from old switch installation and any excess materials used during installation of new switch. This may include sweeping and emptying trash containers. Room shall be as neat or neater as the room was before work started.

h) Comm Closet Operational conditions. Contractor shall notify Government representatives of any conditions they find that they feel will be detrimental to future network operations. These conditions could include: use of comm closet for storage of non-communications items, excess heat/cool, ambient room temperature or humidity, inoperable or poor lighting, lack of or inoperable UPS, inoperable door locks.

Contractor is not responsible for fixing any of these conditions.

4) Miscellaneous.

a) Technician Qualifications: All contractor personnel who will have privileged

(administrator) level access to any IT system shall comply with requirements of MPTO 00-33B-5004. At a minimum, a favorable background investigation or clearance and a properly submitted DD Form 2875. Per DoDI 8500.2, Enclosure 3, Table 1, an SSBI investigation (TS clearance) is required for this person. Since contractor shall have root level access to the switch configuration, at least one member of the contractor team, shall have a TS clearance.

b) Installation. Contractor shall install all equipment according to the system design and using the standards referenced in section 1.5. Any deviations from original design which occur during installation and testing shall be noted. Any deviation that could result in a STIG or security violation must be approved by Government before implementing.

c) Computers. Contractor can use their computers for any console configuration changes required. If contractor requires a computer with network access to configure/test new switches than they shall identify that requirement to the Government. If requested, USAFA shall provide up to three laptop computers to be used for this purpose. Contractor shall identify any specialized software required and obtain Government approval before installing onto GFE. Contractor shall identify any special requirements for GFE hardware. (i.e. 9-pin USB serial cable for computer to be used for equipment console port access.)

d) Documentation. Final installation details shall be documented in electronic format.

Final switch configurations for every switch shall be provided. A 2 megapixel or larger photograph of final installation of each switch shall also be provided.

e) Naming Convention. New switches shall use the same name as the old switch unless it doesn’t meet USAFA’s switch naming convention. Current naming convention is: building number followed by an “E” for edu followed by “SS” for access switch (L2) or “DS” for Distribution (L3) or “CR” for core switch and either a room number where the switch is or a switch number for smaller buildings with only one comm closet. e.g. 5212ESS0000 is in building 5212, on the edu network, is an access switch and is the only switch in the one comm closet in the building.

f) Configuration Wipe of removed equipment. Contractor shall erase all existing configuration files from all equipment once it has been removed from service and new switch is operational.

g) Turn in of removed equipment: All existing Cisco 450x switches and associated hardware are accountable items in the AF ADPE inventory system. Upon removal of existing switches, contractor shall coordinate with 10 CS/SCXPCI for turn-in. In the event contractor has factored in trade-in credits with Cisco for old equipment, contractor shall be responsible for return of all trade-in equipment after equipment has been “turned in” to 10 CS/SCXPCI.

h) Documentation: All documentation shall be provided electronically in Microsoft Office 2010 editable formats (Word, Excel, Visio, Powerpoint). Photographs should be in .jpg format.

5) Optional CLINs.

a) Line Cards. Because USAFA has up to 35 GFE line cards that may be reused under this contract that have an announced end of life, contractor shall include optional line items for additional 48-port line cards that have not gone EOL and are identical to other 48-port line cards supplied under this SOW, both PoE and non-PoE.

Government will inform contractor NLT acceptance of the design and configuration gathering stage how many additional cards to order. Contractor shall include these cards as part of their installation work. Giving trade in credit for return of the WS- X4548-GB-RJ45 line cards on purchase of new line cards is acceptable for this option.

b) 10 GB GBICs. USAFA is upgrading all links to distribution and core switches to 10 Gbps per AF Base Area Network (BAN) guidance. Switches identified in paragraph 3.c.1.a and 3.c.1.b shall be connected at 10 Gbps under this SOW. As USAFA acquires core and distribution layer switches that support 10 Gbps ports, Government desires to be ready to upgrade remaining switches to 10 Gbps uplinks. Contractor shall include optional CLINs for 10 Gbps GBICs for 4506-E chassis as well as SFP+ GBICs compatible with Nexus 5500 switches. Government will inform contractor how many, if any, additional GBICs of each type are wanted before completion of installation and testing of the last switch. Contractor shall supply these GBICs before completion of the contract. Contractor shall be responsible for installation and configuration of any 10 GB GBICs installed before a switch installation is accepted.

Government is responsible for any 10 GB GBICs ordered and delivered after switch installations have been accepted.

3.1 Dependencies. All network switches to be replaced are under the operational control of the 10th Communications Squadron. No external coordination is required to schedule downtime for cutover of switches.

3.2 Systems Support. The Contractor shall design, develop, test and package systems and software changes as well as provide problem resolutions for the existing system. The Contractor shall maintain the current baseline of the system and provide software change and problem fixes to these baselines as required. The Contractor shall provide to the Government all developed, modified, or converted source modules, processes, programs, scripts, operating instructions, databases, system files, documentation, test files and test conditions used to develop each approved systems change request. Specific tasks may include the following:

• Maintain existing systems and environments IAW disciplined engineering practices and sustain applications, databases, and interfaces in compliance with applicable AF/DoD standards

• Perform system performance tuning, system re-hosting, and integration services

3.3 Vendor Proposals. To ensure Government can fairly and equally evaluate vendor proposals to ensure all parts are addressed, vendor shall provide in their proposal a completed table as presented in Appendix D identifying what they will provide and where they intend to use GFE.

4.1.1 Life-Cycle Systems Engineering

The contractor shall employ disciplined systems engineering processes including, but not limited to, requirements development, technical management and control, system/software design and architecture, integrated risk management, configuration management, data management, and test, evaluation, verification and validation practices throughout the period of performance of task orders in accordance with AFI 63-1201, Life Cycle Systems Engineering.

4.1.2 Systems Engineering Process (SEP)

If applicable, the contractor shall follow and refer to the Air Force Program Executive Office (AFPEO) Business Enterprise Systems (BES) SEP website for common plans, procedures, checklists, forms, and templates that support system life cycle management and systems engineering processes as it applies to Defense Acquisition, Technology, and Logistics tailored to Capability Maturity Model Integrated (CMMI) disciplines, or be able to demonstrate comparable processes and artifacts.

The contractor shall develop solutions that employ principles of open technology development and a modular open systems architecture for hardware and software as described in the DoD Open Technology Development Guidebook and Net-Centric Enterprise Solutions for Interoperability (NESI) body of knowledge. The contractor’s systems engineering plan and design activities shall also adhere to the DoD Information Sharing and Net-Centric Strategies published by the DoD CIO, and the engineering body of knowledge and lessons-learned accumulated in NESI.

4.2 Architecture and System Design

The contractor shall support the design and development of systems and applications and their integration into the overarching enterprise architecture. The contractor shall provide all required design and development documents, and supporting architectural documentation, for any frameworks as identified in this task order.

4.2.1 Department of Defense Architectural Framework (DoDAF) Guidance The contractor shall provide all required design and development documents, and supporting architectural documentation in compliance with the latest Department of Defense Architectural Framework (DoDAF) Enterprise Architecture guidance http://dodcio.defense.gov/Portals/0/Documents/DODAF/DoDAF_v2-02_web.pdf.

4.2.5 Federal Desktop Core Configuration (FDCC)

All services provided under this Task Order shall function and be in compliance with the Federal Desktop Core Configuration (FDCC).

4.3 Configuration Management

The contractor shall accomplish Configuration Management (CM) activities as described in the task order. CM activities include baseline identification, change control, status accounting, and auditing.

http://dodcio.defense.gov/Portals/0/Documents/DODAF/DoDAF_v2-02_web.pdf

4.4.2 Product/System Integration Testing

The contractor shall perform testing and inspections of all system services to ensure the technical adequacy and accuracy of all work, including reports and other documents required in support of that work. The contractor shall conduct on-site testing when requested. When specified by the Government, the contractor shall participate with the Government in testing the complete system or application which may include premise equipment, distribution systems or any additional telecommunications equipment or operating support systems identified in the task order. After appropriate corrective action has been taken, all tests including those previously completed related to the failed test and the corrective action shall be repeated and successfully completed prior to Government acceptance. Pre-cutover audits will consist of verification of all testing completed by the contractor such that the system is deemed ready for functional cutover. As part of this audit, any engineered changes or approved waivers applicable to the installation will be reviewed and agreed upon between the contractor and the Government. Post-cutover audits will verify that all post-cutover acceptance testing has been performed satisfactorily IAW the standard practices and identify those tests, if any, which have not been successfully completed and must be re-tested prior to acceptance. Testing shall be performed in two steps: operational testing, then system acceptance testing. The contractor shall provide a logical test process that minimizes interruptions and avoids sustained downtime and presents a contingency procedure to be implemented in the event of systems failure during testing.

4.5 Information Assurance

The contractor shall ensure that all system or application deliverables meet the requirements of DoD and AF Information Assurance (IA) policy. Furthermore, the contractor shall ensure that personnel performing IA activities obtain, and remain current with, required technical and/or management certifications.

4.5.1 System IA

For those solutions that will not inherit existing network security controls, and thus integrate an entirely new application system consisting of a combination of hardware, firmware and software, system security assurance is required at all layers of the TCP1IP DoD Model. The contractor shall ensure that all system deliverables comply with DoD and AF IA policy, specifically DoDI 8500.2, Information Assurance Implementation, and AFI 33-200, Information Assurance Management. To ensure that IA policy is implemented correctly on systems, contractors shall ensure compliance with DoD and AF Certification & Accreditation policy, specifically DoDI 8510.01, DoD Information Assurance Certification and Accreditation Process (DIACAP), and AFI 33-210, Air Force Certification and Accreditation Process (AFCAP). The contractor shall also support activities and meet the requirements of DoDI 8520.02, Public Key Infrastructure (PKI) and Public Key (PK) Enabling, in order to achieve standardized, PKI-supported capabilities for biometrics, digital signatures, encryption, identification and authentication.

5. CONTRACTUAL REQUIREMENTS

The Government is responsible for communicating and scheduling any outages with the USAFA user community.

Normal duty hours at USAFA are 0700 until 1700. Contractor shall expect majority of downtime for switch replacement will occur outside of these hours to minimize downtime to Academy normal operations.

The Government will coordinate and make any changes to o t h e r existing infrastructure using USAFA Change Management Processes. Existing infrastructure could include firewalls, Active D i r e c t o r y , E x c h a n g e , f i l e s e r v e r s , v i r t u a l s e r v e r s , p u b l i c k e y infrastructure, hardware load balancers and Storage Area Networks (SANs).

5.1 Contractors Use of NETCENTS-2 Products Contract

The contractor shall obtain all products and associated peripheral equipment required by each individual task order from the NETCENTS-2 Products contract as stipulated in Section H Clause H098 of the overarching Application Services RFP.

5.2 Place of Performance

The work will be completed remotely or onsite at the US Air Force Academy. Travel in and around the primary place of performance may be required throughout the period of performance.

5.3 Normal Hours of Operation

The average workweek is 40 hours. The average workday is 8 hours and the window in which those 8 hours may be scheduled is between 6:00 AM and 6:00 PM, Monday through Friday, except for days listed in Clause G021, Contract Holidays, in the overarching ID1IQ contract.

Billable hours are limited to the performance of services as defined in the TO. Government surveillance of contractor performance is required to give reasonable assurance that efficient methods and effective cost controls are being used. Work in excess of the standard 40 hour work week requires prior written approval by the Contracting Officer's Representative (COR).

5.4 Government Furnished Property

The Government will provide the equipment identified in paragraph 3.c.2 required to accomplish this PWS.

When the Task Order requires the contractor to work in a Government facility, the Government will furnish or make available working space, network access, and equipment to include:

• Windows PC with Microsoft Office Suite (Outlook, Word, Excel, PowerPoint, etc.)

• Telephone (local/long distance calls authorized as dictated by Task Order performance requirements)

• Facsimile

• Copier

• Printer

Copies of required Government furnished materials cited in the solicitation, PWS, DD Form 254, and/or in the Task Order will be provided to the contractor in hard copy or soft copy. All materials will remain the property of the Government and will be returned to the responsible Government QAP upon request or at the end of the Task Order period of performance.

Equipment purchased by the contractor with the approval of the Government and directly charged to this Task Order shall be considered government owned-contractor operated equipment. The contractor shall conduct a joint inventory and turn in this equipment to the COR upon request or completion of the Task Order.

5.5 Billable Hours

In order for man-hours to be billed, deliverable services must have been performed in direct support of a requirement in the TO SOW. In the course of business, situations may arise where Government facilities may not be available for performance of the TO requirements (i.e., base closure due to weather, Force Protection conditions, etc.). When the base is officially closed no contractor services will be provided and no charges will be incurred and/or billed to any TO.

There may also be occasions when support contractors are invited to participate in morale and recreational activities (i.e., holiday parties, golf outings, sports days and other various social events). Contractor employees shall not be directed to attend such events by the Government.

Since a contract employee is not a government employee, the contract employee cannot be granted the same duty time activities as Government employees. Participation in such events is not billable to the TO and contractor employee participation should be IAW the employees, company’s policies and compensation system.

5.6 Non-Personal Services

The Government will neither supervise contractor employees 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 feels that any actions constitute, or are perceived to constitute personal services, it shall be the contractor’s responsibility to notify the Task Order (TO) Contracting Officers CO immediately. These services shall not be used to perform work of a policy/decision making or management nature, i.e., inherently Governmental functions. All decisions relative to programs supported by the contractor shall be the sole responsibility of the Government. These operating procedures may be superseded by Theater Commander’s direction during deployments.

5.7 Contractor Identification

All contractor/subcontractor personnel shall be required to wear AF-approved or provided picture identification badges so as to distinguish themselves from Government employees.

When conversing with Government personnel during business meetings, over the telephone or via electronic mail, contractor/subcontractor personnel shall identify themselves as such to avoid situations arising where sensitive topics might be better discussed solely between Government employees. Contractors/subcontractors shall identify themselves on any attendance sheet or any coordination documents they may review. Electronic mail signature blocks shall identify their company affiliation. Where practicable, contractor/subcontractors occupying collocated space with their Government program customer should identify their work space area with their name and company affiliation. Refer to Clause H063 of the overarching ID/IQ contract for specific guidance.

5.8 Performance Reporting

The contractor’s performance will be monitored by the Government and reported in Contractor Performance Assessment Reporting (CPARs). Performance standards shall include the contractor’s ability to provide or satisfy the following:

• Provide quality products, incidentals, and customer support

• Meet customer’s agreed-upon timelines for scheduled delivery of items, warranty, and/or incidental services: Emergency/critical, Maintenance/Warranty – 24 x 7 x 365, and remote OCONUS, OCONUS vs. CONUS response times

• Timely and accurate reports

• Responsive proposals

• Configuration assistance as identified in each delivery order

5.9 Program Management / Project Management

The contractor shall identify a Program Manager or a Project Manager who shall be the primary representative responsible for all work awarded under this task order. He/She shall participate in Program/Project Management Reviews and ensure compliance with all standards referenced herein.

5.9.1 Services Delivery Summary

Reference Section 6, Services Delivery Summary, of this Task Order PWS for specific performance objectives.

The contractor’s performance at the contract level will be assessed quarterly by a process that measures success towards achieving defined performance objectives. The Services Delivery Summary will be in accordance with AFI 63-124, Performance Based Services Acquisition and FAR Subpart 37.6, Performance-Based Acquisition.

5.9.2 Task Order Management

The contractor shall establish and provide a qualified workforce capable of performing the required tasks. The workforce may include a project/task order manager who will oversee all aspects of the task order. The contractor shall use key performance parameters to monitor work performance, measure results, ensure delivery of contracted product deliverables and solutions, support management and decision-making and facilitate communications. The contractor shall identify risks, resolve problems and verify effectiveness of corrective actions. The contractor shall institute and maintain a process that ensures problems and action items discussed with the Government are tracked through resolution and shall provide timely status reporting. Results of contractor actions taken to improve performance shall be tracked, and lessons learned incorporated into applicable processes. The contractor shall establish and maintain a documented set of disciplined, mature, and continuously improving processes for administering all contract and Task Order efforts with an emphasis on cost-efficiency, schedule, performance, responsiveness, and consistently high-quality delivery. The contractor shall provide transition plans as required.

5.9.3 Documentation and Data Management

The contractor shall establish, maintain, and administer an integrated data management system for collection, control, publishing, and delivery of all program documents. The data management system shall include but not be limited to the following types of documents: CDRLs, White Papers, Status Reports, Audit Reports, Agendas, Presentation Materials, Minutes, Contract Letters, and Task Order Proposals. The contractor shall provide the Government with electronic access to this data, including access to printable reports.

5.9.4 Records, Files, and Documents

All physical records, files, documents, and work papers, provided and/or generated by the Government and/or generated for the Government in performance of this PWS, maintained by the contractor which are to be transferred or released to the Government or successor contractor, shall become and remain Government property and shall be maintained and disposed of IAW AFMAN 33-363, Management of Records; AFI 33-364, Records Disposition – Procedures and Responsibilities; the Federal Acquisition Regulation, and/or the Defense Federal Acquisition Regulation Supplement, as applicable. Nothing in this section alters the rights of the Government or the contractor with respect to patents, data rights, copyrights, or any other intellectual property or proprietary information as set forth in any other part of this PWS or the Application Services contract of which this PWS is a part (including all clauses that are or shall be included or incorporated by reference into that contract).

5.9.5 Security

Individuals performing work under these task orders shall comply with applicable program security requirements as stated in the task order. NETCENTS-2 will support the following levels of security: Unclassified; Unclassified, But Sensitive; Secret (S); Secret Sensitive Compartmented Information (S/SCI); Top Secret (TS); and Top Secret Sensitive Compartmented Information (TS/SCI).

Task orders may require personnel security clearances up to and including Top Secret, and may require all employees to be United States citizens. The security clearance requirements will depend on the security level required by the proposed task order. The task orders may also require access to sensitive compartmented information (SCI) for which SCI eligibility will be required. Contractors shall be able to obtain adequate security clearances prior to performing services under the task order. The Contract Security Classification Specification (DD Form 254) will be at the basic contract and task order level and will encompass all security requirements.

All contractors located on military installations shall also comply with Operations Security (OPSEC) requirements as set forth in DoD Directive 5205.02, Operations Security Program and AFI 10-701, Operations Security. In accordance with DoD 5200.2-R, Personnel Security Program (Jan 87), DoD military, civilian, consultants, and contractor personnel using unclassified automated information systems, including e-mail, shall have, at a minimum, a completed favorable National Agency Check plus Written Inquiries (NACI).

The types of Personnel Security Investigations (PSI) required for the contractor vary in scope of investigative effort depending upon requirements of the Government and/or conditions of the Task Order. In cases where access to systems such as e-mail is a requirement of the Government, application/cost for the PSI shall be the responsibility of the Government. In cases where access to systems is as a condition of the Task Order, application/cost for the appropriate PSI shall be the responsibility of the contractor. In such instances, the contractor shall diligently pursue obtaining the appropriate PSI for its employees prior to assigning them to work any active task order. Acquisition planning must consider Anti-Terrorism (AT) measures when the effort to be contracted could affect the security of operating forces (particularly in-transit forces), information systems and communications systems IAW DoD Instructions

2000.16 Anti-Terrorism Standards.

5.9.5.1 Transmission of Classified Material

The contractor shall transmit and deliver classified material/reports IAW the National Industrial Security Program Operating Manual (DoD 5220.22-M). These requirements shall be accomplished as specified in the Task/Delivery Order.

5.9.5.2 Protection of System Data

Unless otherwise stated in the task order, the contractor shall protect system design-related documents and operational data whether in written form or in electronic form via a network in accordance with all applicable policies and procedures for such data, including DoD Regulation 5400.7-R and DoD Manual 5200.01(v1-v4) to include latest changes, and applicable service/agency/ combatant command policies and procedures. The contractor shall protect system design related documents and operational data at least to the level provided by Secure Sockets Layer (SSL)/Transport Security Layer (TSL)-protected web site connections with certificate and or user ID/password-based access controls. In either case, the certificates used by the Contractor for these protections shall be DoD or IC approved Public Key Infrastructure (PKI) certificates issued by a DoD or IC approved External Certification Authority (ECA) and shall make use of at least 128-bit encryption.

5.9.5.3 System and Network Authorization Access Requests

For Contractor personnel who require access to DoD, DISA, or Air Force computing equipment or networks, the Contractor shall have the employee, prime or subcontracted, sign and submit a System Authorization Access Report (SAAR), DD Form 2875.

5.9.6 Travel

The contractor shall coordinate specific travel arrangements with the individual Contracting Officer or Contracting Officer’s Representative to obtain advance, written approval for the travel about to be conducted. The contractor’s request for travel shall be in writing and contain the dates, locations and estimated costs of the travel in accordance with the basic contract clause H047.

If any travel arrangements cause additional costs to the task order that exceed those previously negotiated, written approval by CO is required, prior to undertaking such travel. Costs associated with contractor travel shall be in accordance with FAR Part 31.205-46, Travel Costs.

The contractor shall travel using the lower cost mode transportation commensurate with the mission requirements. When necessary to use air travel, the contractor shall use economy class or similar accommodations to the extent they are available and commensurate with the mission requirements. Travel will be reimbursed on a cost reimbursable basis; no profit or fee will be paid.

5.9.7 Other Direct Cost (ODC)

The contractor shall identify ODC and miscellaneous items as specified in each task order. No profit or fee will be added; however, DCAA approved burden rates are authorized.

5.10 Training

Contractor personnel are required to possess the skills necessary to support their company’s minimum requirements of the labor category under which they are performing. Training necessary to meet minimum requirements will not be paid for by the Government or charged to TOs by contractors.

5.10.1 Mission-Unique Training

In situations where the Government organization being supported requires some unique level of support because of program/mission-unique needs, then the contractor may directly charge the TO on a cost reimbursable basis. Unique training required for successful support must be specifically authorized by the TO CO. Labor expenses and travel related expenses may be allowed to be billed on a cost reimbursement basis. Tuition/Registration/Book fees (costs) may also be recoverable on a cost reimbursable basis if specifically authorized by the TO CO. The agency requiring the unique support must document the TO file with a signed memorandum that such contemplated labor, travel, and costs to be reimbursed by the Government are mission essential and in direct support of unique or special requirements to support the billing of such costs against the TO.

5.10.2 Other Government-Provided Training

The contractor’s employees may participate in other Government provided training, on a non-discriminatory basis as among contractors, under the following circumstances:

(1) The contractor employees’ participation is on a space-available basis,

(2) The contractor employees’ participation does not negatively impact performance of this task order,

(3) The Government incurs no additional cost in providing the training due to the contractor employees’ participation, and

(4) Man-hours spent due to the contractor employees’ participation in such training are not invoiced to the task order

5.11 Data Rights and Non-Commercial Computer Software

In order to implement the provisions at DFARS 252.227-7013(b) and (e) and DFARS 252.227- 7014(b) and (e) and DFARS 252.227-7017, the Contractor shall disclose to the ordering Contracting Officer and ordering office in any proposal for a task order, or after award of a task order if not previously disclosed in the proposal, any technical data or non-commercial computer software and computer software/source code documentation developed exclusively at government expense in performance of the task order. This disclosure shall be made whether or not an express requirement for the disclosure is included or not included in the PWS or solicitation for the order. The disclosure shall indicate the rights asserted in the technical data and non-commercial computer software by the Contractor and rights that would be acquired by the government if the data or non-commercial software was required to be delivered under the task order and its CDRL requirements and any cost/price associated with delivery. This disclosure requirement also applies to Segre gable routines of non-commercial software that may be developed exclusively at Government expense to integrate Commercial Software components or applications provided under a commercial software license or developed to enable Commercial Software to meet requirements of the Task Order. This disclosure obligation shall apply to technical data and non-commercial computer software developed exclusively at Government expense by subcontractors under any Task Order. Performance of this disclosure requirement shall be considered a material performance requirement of any task order under which such technical data or non-commercial computer software is developed exclusively at Government expense.

5.12 COTS Manuals and Supplemental Data

The contractor shall provide documentation for all systems services delivered under this Task Order. The contractor shall provide COTS manuals, supplemental data for COTS manuals, and documentation IAW best commercial practices (i.e. CD-ROM, etc.). This documentation shall include users’ manuals, operators’ manuals, maintenance manuals, and network and application interfaces if specified in the task order.

5.13 Enterprise Software Initiative

In situations where the purchase of new COTS software is needed to satisfy the requirements of a particular task order, the contractor shall use available existing enterprise licenses. If enterprise licenses are unavailable, then products will be obtained via the DoD Enterprise Software Initiative (ESI) Blanket Purchase Agreements (BPAs). If products are unavailable from

ESI, then products will be acquired through the NETCENTS-2 Products contract. The updated listing of COTS software available from DoD ESI sources can be viewed on the web at http://www.esi.mil.

5.14 Software License Management

If developing and/or sustaining a system that requires and/or contains COTS, the contractor shall provide maintenance and support of that software license to manage its relationship to the overall system life-cycle, which would include applications, license agreements, and software upgrades. The contractor shall provide asset inventory and services that track the financial aspects of an asset to include cost and depreciation, contract management, leases, maintenance agreements and service contracts. The contractor shall provide support summary information to include the general terms and conditions, benefits, strategic and tactical directions, license ordering information, internal billing process, pricing and deployment and support of the products included in the agreement. The contractor shall support common practices for ordering assets, tracking orders and assets, and tagging the assets. The contractor shall support application installation, operations, customer support, training, maintenance, and sustainment and configuration control, to include the procurement of supporting software licenses.

5.15 Transition and Decommissioning Plans

The contractor shall create transition and decommissioning plans that accommodate all of the non-authoritative data sources (non-ADS) interfaces and ensure that necessary capabilities are delivered using approved ADSs.

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

5.17 Performance of Services During Crisis Declared by the President of the United States, the Secretary of Defense, or Overseas Combatant Commander The performance of these services may be considered mission-essential functions during time of crisis. Should a crisis be declared by the Secretary of Defense, the CO or representative will verbally advise the Contractor of the revised requirements, followed by written direction?