RRMC_IT_PWS_DRAFT_Watermark_4-12-2016.pdf

PERFORMANCE WORK STATEMENT (PWS)

Operations and Maintenance (O&M) and Engineering Support of Raven Rock Mountain

Complex (RRMC) Information Technology (IT) Enterprise Services

Part 1

General Information

1. GENERAL. This is a non-personal services contract to provide seamless, reliable, and responsive enterprise IT services essential for the engineering, implementation, and O&M of the

RRMC IT systems to include but not limited to, Virtual Desktop Infrastructure (VDI), Joint

Consolidated Server Room (JCSR), network, Audio Visual (A/V) conference room, and security camera systems. The Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Contractor who, in turn is responsible to the Government.

1.1 Description of Services/Introduction. The Contractor shall, as an independent Contractor, and not as an agent of the Government, furnish all management, labor, tools, supplies, and materials necessary to perform the requirements contained herein for Operations and

Maintenance (O&M) and Engineering Support as defined in this Performance Work Statement except for those items specified as government furnished property and services.

The Government expects operations and services are available at a consistent systems availability level of 99.95% that results in a stable and secure enterprise IT network that meets the functionality, speed, and capacity expectations of Government end users while complying with Department of Defense (DoD) and Federal rules and regulations.

In support of the above stated readiness level, all bidders’ responses must be developed to ensure the following:

The environment within RRMC IT must enable the customer to provide Enterprise

Services throughout the Department of Defense.

The proposed technical approach must not be constrained to a “single solution” that does not allow the Government the flexibility to insert new technologies to increase efficiencies and cost savings.

The proposed technical solution must incorporate the capability for Contractor personnel to perform “in-house” maintenance using on-site stored hardware and repair parts.

Knowledge of the existing infrastructure and Army enterprise licensed technology.

1.2 Background.

RRMC IT’s mission is to Plan, Operate, Maintain, and Defend Information Management Systems and Plan, Operate, and Defend Visual Information Systems in support of RRMC, thus providing an enduring platform from where the Department of Defense (DoD) can execute its mission essential functions (MEFs) in support of continuity of operations (COOP).

To execute this mission, RRMC IT focuses on four (4) lines of effort (LOE), namely;

1. Deploy enterprise-wide capabilities and services eliminating unnecessary duplication of capabilities, while maintaining autonomous operations during all hazard scenarios.

2. Provide innovative Unified Capability (UC) IT solutions that improves security, increases efficiencies, and improves Command & Control mission effectiveness to meet increasing demands.

3. Increase network efficiency and effectiveness by consolidating, standardizing, and expanding the network throughput to facilitate faster data transfer.

4. Consolidate and virtualize servers, applications, desktops, and storage to approved

RRMC IT hosting facilities.

Existing manpower shortages and increased workloads at RRMC has critically impacted the unit’s ability to efficiently execute its mission. The intent of this contract is to provide professional IT services and assets to meet RRMC IT mission requirements, DoD directives and consolidation policies. Additionally, this requirement will provide a means to quickly surge manpower support with the on-ramping off additional customers into the RRMC IT Joint

Consolidated Server Room (JCSR).

1.3 Objectives. The specific objectives of this acquisition are to:

Satisfy RRMC IT customer needs for secure, accessible, and stable IT

Support, ensuring compliance with the 114th RRMC IT Services Guide.

Continuously improve end-to-end service levels.

Capitalize on IT management, blade server and SAN, and VMware® (virtualization) best practices and emerging technologies.

Reduce Service Delivery Gaps within RRMC IT.

Work with and on-board customers into the JCSR.

Develop and deploy VDI on NIPR, SIPR, and SCI enclaves.

Develop and implement RRMC IT CONOPS, Technical Guides, SOPs, Engineering

Drawings, and IT Master Plan.

1.4 Scope. Enterprise IT services essential for the engineering, implementation, and O&M of the RRMC IT systems to include but not limited to, Virtual Desktop Infrastructure (VDI), Joint

Consolidated Server Room (JCSR), network, Audio Visual (A/V) conference room, and security camera systems. These support efforts shall include, but not be limited to, IT enterprise technical architecture and engineering planning, IT solution implementation and security support, IT system O&M support, IT demand planning and analysis, IT systems analysis & design, IT consolidation & lifecycle management, development of IT solution functional requirements & planning documents, technical deliverable review & advisory, and development of key IT technical solution documentation. The Contractor may also be required to acquire solutions

(hardware & software) on behalf of the Government under this effort.

1.5 Period of Performance. The period of performance shall be for one (1) Base Year of 12 months and four (4) 12-month option years. The Period of Performance reads as follows:

Base Year

Option Year I

Option Year II

Option Year III

Option Year IV

1.6 General Information

1.6.1 Quality Control Plan (QCP). The Contractor shall develop a QCP that demonstrates how the Contractor shall maintain an inspection system acceptable to the Government covering the services under this contract. The Contractor shall provide the QCP to the Government NLT 30 days after contract award date. The Contractor shall also provide updated versions to the Government within 15 days of implementation by the Contractor. The QCP shall demonstrate the Contractor’s documented processes and procedures to monitor and control:

Objectives in Performance Requirement Summary (Technical Exhibit 1) Subcontractor relationships Contractor and subcontractor invoicing Non-conformance (Paragraph 1.6.1.1)

1.6.1.1 Non-conformances. Identify and control non-conformances through root cause analysis, corrective actions, and preventive actions. Focus on eliminating the cause to prevent reoccurrence. Maintain records of non-conformities and actions taken. Correct and provide response to all Government-identified non-conformances IAW time frames specified by the CO.

This contract identifies two types of non-conformances: Minor and Major.

1.6.1.1.1 Minor Non-conformance. A minor non-conformance is a non-conformance, which by itself does not adversely impact mission, safety of personnel and/or equipment, performance (quality), schedule (delivery), or cost. It normally does not increase risk to the Government.

Minor non-conformances are typically low risk and are communicated through notices; first notices are issued for any identified non-conformance, second notices are issued for repeat non-conformances or failing to correct issues within a reasonable amount of time. Upon receipt of a non-conformance notification (first of second notice), the Contractor shall complete applicable sections and return it to the CO within time constraints directed by the CO in the notice. A formal corrective action plan is not required for notices.

1.6.1.1.2 Major Non-conformance. A major non-conformance is a non-conformance that adversely impacts (or has the potential to impact) mission, safety of personnel and/or equipment, performance (quality), schedule (delivery), or cost. This type of nonconformance increases risk to the Government and therefore has a risk assessment rating of moderate or high. An example of increasing risk would be a significant number of recurring non-conformances, which is an indication of inadequate preventive measures/actions and lowers the Government’s confidence that the Contractor can provide quality services on time and within costs. The CO will communicate major non-conformances on a Corrective Action Request (CAR) form with a suspense date for the Contractor’s corrective action plan. As a minimum, the Contractor’s corrective action plan will address:

Action taken to fix the immediate problem Root cause analysis of the problem to determine cause Corrective action on the cause of the problem Actions taken to prevent recurrence

1.6.2 Quality Assurance. The government shall evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan (QASP). This plan is primarily focused on what the Government must do to ensure that the contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

1.6.3 Recognized Holidays. All Government holidays will be observed.

New Year’s Day Labor Day

Martin Luther King Jr.’s Birthday Columbus Day

President’s Day Veteran’s Day

Memorial Day Thanksgiving Day

Independence Day Christmas Day

1.6.4 Hours of Operation. Initial core duty hours will be Monday-Friday, 0730-1630. All

Government holidays will be observed. As RRMC IT capabilities are brought online to support customers, duty hours will be modified to provide 24x7x365 operational coverage when required. The Contractor shall provide the Government a scheduling model to accomplish the aforementioned. The Government shall approve overtime compensation in support of this PWS until such time the Contractor is directed to begin 24x7 operations at which time overtime will no longer be approved except for extenuating circumstances. In case of emergency or critical event the contractor will provide 2 hour recall support.

The Contractor shall perform support services on-site (in Government work spaces) during core or normal work hours (NWH) for the purposes of supporting customers and the infrastructure.

The Contractor shall also provide limited on-site support during extended work hours (EWH) at no additional cost to the Government if the COR provides written notice to the Contractor at least two (2) business days in advance, and specifies the task areas that require support.

Extended Working Hours (EWHs) including after hours on weekdays, weekends and holidays.

In providing support during EWHs, the Contractor shall be capable of providing at least remote support within one (1) hour of receiving notification by the COR; however, depending on the nature of the activity/event, on-site support may be required. This type of support may occur on a scheduled or unscheduled basis. For scheduled on-site support activities, the Contractor shall report for work at the time and place pre-arranged with the COR. For unscheduled on-site support activities, the Contractor shall arrive on-site (ready to work) at the Government facility within two hours after efforts at remote resolution have been discontinued or otherwise receiving notification that on-site support is required.

1.6.5 Place of Performance. Work performance will primarily be conducted at the RRMC with possible work performed at Government facilities in and outside of the National Capital Region

(NCR)--the NCR includes the District of Columbia and neighboring counties and cities of

Maryland, West Virginia and Virginia, including Arlington, Loudon, Fairfax and Prince William counties in Virginia.

1.6.6 Type of Contract: The government will award a Firm Fixed Price Contract.

1.6.7 Security Requirements: Contractor personnel performing work under this contract must have a minimum active DoD security clearance (SECRET). The Contractor will be required to provide personnel with clearances at the appropriate level to support higher classification IT systems to include some personnel with TS/SCI. The table below identifies the possible required security clearance.

Table 1.6 Security Clearances

Position Highest Level of

Clearance

Program Manager Top Secret with Sensitive

Compartmented

Information (SCI) eligibility

VDI Engineer TS with SCI eligibility

Virtualization or Server Engineer TS with SCI eligibility

Storage Engineer TS with SCI eligibility

Network Engineer TS with SCI eligibility

Information Assurance Engineer TS with SCI eligibility

Technical Writer SECRET (Minimum)

Registered Communications Distribution

Designer (RCDD)

TS with SCI eligibility

A/V Engineer TS with SCI eligibility

Planet IRM Integration Engineer SECRET (Minimum)

Contractor and all associated sub-contractors employees shall provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office.

Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) as directed by DOD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

Contractor shall comply with FAR 52.204-2, Security Requirements. This clause involves access to information classified “Confidential,” “Secret,” or “Top Secret” and requires contractors to comply with— (1) The Security Agreement (DD Form 441), including the

National Industrial Security Program Operating Manual (DoD 5220.22-M); (2) any revisions to

DOD 5220.22-M, notice of which has been furnished to the contractor.

Per AR 381-12 Threat Awareness and Reporting Program (TARP), contractor employees must receive annual TARP training by a CI agent or other trainer as specified in 2-4b. For this contract, contractors shall complete training within 30 calendar days and deliver completion certificates to the COR.

DELIVERABLE: TARP training certificate

In addition, to the above security clearances, DoD Instruction 8500.2, Information Assurance

(IA) Implementation, requires certain investigative levels for Contractors working on DoD

Information Systems. For the purposes of this PWS the following IT Sensitivity Levels will apply:

Table 1.6.1: Investigative Levels

Position IT LEVEL

Technicians with access to router ACLs, VPN devices, firewall rule sets and supervisors of personnel who have these responsibilities.

IT-I

Privileged

Project Leaders, system analysts, system architects, and senior technicians with admin privileges to servers and

SANs.

IT-II

Limited

Privileged

Personnel shall comply with Contractor recognition procedures including identification of the company in signature blocks, wearing an appropriately colored and annotated (Contractor)

RRMC site badge. Contractor badges will be visibly displayed during all government meetings.

The Government will provide each Contractor the appropriate badges (site/building access), Common Access Cards (CAC), and RRMC IT space access as deemed appropriate for the work performed by each Contractor.

Before CAC issuance, the contractor employee requires, at a minimum, a favorably adjudicated

National Agency Check with Inquiries (NACI) or an equivalent or higher investigation in accordance with Army Directive 2014-05. The contractor employee will be issued a CAC only if duties involve one of the following: (1) Both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely; (2) Remote access, via logon, to a DoD network using DoD-approved remote access procedures; or (3) Physical access to multiple DoD facilities or multiple non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled

NACI at the Office of Personnel Management.

1.6.7.1 PHYSICAL Security. The contractor shall be responsible for safeguarding all government equipment, information and property provided for contractor use. At the close of each work period, government facilities, equipment, and materials shall be secured.

1.6.7.2 Security Clearance. DD Form 254, Contract Security Classification Specification, shall be coordinated with the contracting office and the program office at the time of the contract award date. Upon execution of award, the CO will sign the DD Form 254 for incorporation into the contract. The using activity will provide security classification guidance for performance of this contract. The Government will oversee the handling and storage of classified information and provide the appropriate storage capability for all classified material. All classified information shall be returned to the government upon termination of the contract. No classified work is authorized without an approved DD Form 254 and the appropriate personnel security clearances. Contractors must have valid personnel security clearances at the appropriate level at the time of contract award and shall maintain this status throughout the life of the contract.

If contractor personnel possess a Secret clearance at the time of contract award and require upgrading to a TOP SECRET, an interim TOP SECRET will be acceptable.

Subcontractors shall comply with the same personnel security clearance requirements as the contractor. The contractor shall issue DD Form 254s to each subcontractor, as directed by the government, reflecting the level of security requirements applicable, based off the level of support provided by the subcontractor.

1.6.7.3 Facility Clearance. The contractor shall possess and maintain a TOP SECRET facility clearance from the Defense Security Service. The contractor’s employees, performing work in support of this contract shall have been granted a TOP SECRET security clearance from the

Defense Industrial Security Clearance Office.

1.6.7.4 Key Control The Contractor shall establish and implement methods of making sure 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 shall be duplicated. The Contractor shall develop procedures covering key control that shall be included in the Quality Control Plan. Such procedures shall include turn-in of any issued keys by personnel who no longer require access to locked areas. The Contractor shall immediately report any occurrences of lost or duplicate keys/key cards to the Contracting Officer.

1.6.7.4.1. In the event keys, other than master keys, are lost or duplicated, the Contractor shall, upon direction of the Contracting Officer, 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 replacement of locks or re-keying is performed by the Government, the total cost of re-keying or the replacement of the lock or locks shall be deducted from the monthly payment due the

Contractor. In the event a master key is lost or duplicated, all locks and keys for that system shall be replaced by the Government and the total cost deducted from the monthly payment due the

Contractor.

1.6.7.4.2. The Contractor shall prohibit the use of Government issued keys/key cards 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 employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the Contracting Officer.

1.6.7.5 Lock Combinations. The Contractor shall establish and implement methods of ensuring that all lock combinations are not revealed to unauthorized persons. The Contractor, in coordination with the Government, shall ensure that lock combinations are changed when personnel having access to the combinations no longer have a need to know such combinations.

The Contractor is not authorized to record lock combinations without written approval from the

Government. Records with written combinations to authorized secure storage containers, secure storage rooms, or certified vaults, shall be marked and safeguarded at the highest classification level as the classified material maintained inside the approved containers. These procedures shall be included in the Contractor’s Quality Control Plan.

1.6.8 Post Award Conference/Periodic Progress Meetings. The Contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The contracting officer, Contracting Officers Representative (COR), and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings the contracting officer will apprise the contractor of how the government views the contractor's performance and the contractor will apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the government.

1.6.8.1 Kick-off Meeting. Within ten (10) calendar days after award, the Contractor shall conduct a kick-off meeting for the COR. The kick-off meeting shall be per the requirements stated in the General and Scope sections of the Contract. It shall also include a proposed Project

Schedule.

1.6.8.2 Special Meetings. Either the Contractor or the Government may request a special meeting in support of quick resolution of complex technical issues requiring in depth and highly specialized discussions and or collaboration with key technical personnel on either side or both sides.

1.6.8.3 Meeting Minutes/Documentations. The Contractor will submit meeting minutes/documentation via a transmittal within five (5) calendar days after the meeting. Upon receipt, the Government will have a review and response period of ten (10) work-days. Any exception is to be determined by the COR on a case-by-case basis.

1.6.9 Contracting Officer Representative (COR): The (COR) will be identified by separate letter.

The COR monitors all technical aspects of the contract and assists in contract administration The

COR is authorized to perform the following functions: assure that the Contractor performs the technical requirements of the contract: perform inspections necessary in connection with contract performance: maintain written and oral communications with the Contractor concerning technical aspects of the contract: issue written interpretations of technical requirements, including

Government drawings, designs, specifications: monitor Contractor's performance and notifies both the Contracting Officer and Contractor of any deficiencies; coordinate availability of government furnished property, and provide site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

1.7 Key Personnel: The Contractor shall provide on-site management staff with full company authority to oversee the assigned resources and enable rapid resolution of day-to-day service delivery issues.

The Contractor shall provide qualified personnel at start of contract that meets or exceeds the qualification requirements in this PWS.

During the first 90 calendar days of performance, the contractor shall make no substitutions of key personnel, unless illness, death, or termination of employment necessitates the substitution.

The contractor shall notify the Contracting Officer immediately after the occurrence of any of these events and provide the information required.

After the initial 90 calendar day period, the contractor may propose a substitution. The contractor shall notify the Contracting Officer in writing of any proposed substitution at least thirty (30) days in advance of the proposed substitution. The contractor shall provide a detailed explanation of the circumstances necessitating the proposed substitutions, complete resumes for the proposed substitutes, and any additional information requested by the Contracting Officer.

The contractor shall, prior to making any substitution permanent, demonstrate to the satisfaction of the Contracting Officer, that the qualifications of the proposed substitute personnel is equal to or better than the qualifications of the personnel originally identified for the position. The

Contracting Officer will notify the contractor within 15 calendar days after receipt of all required information of the decision on proposed substitutions. Only the Contracting Officer can approve any substitutions.

All contractor personnel shall be U.S. citizens. All contractor personnel shall speak fluent

English. The contractor shall provide the Key Personnel with the minimum qualifications as specified within the Key Personnel Table.

For replacement of non-key personnel, the contractor shall provide a resume to the Contracting

Officer prior to making any substitution permanent. The resumes shall demonstrate to the satisfaction of the Contracting Officer, that the qualifications of the proposed substitute personnel is equal to or better than the qualifications of the personnel originally identified for the position.

The follow personnel are considered key personnel by the government:

Table 1-7 Key Personnel

1.7.1.1 Program Manager

1.7.1.2 VDI Engineer

1.7.1.3 Virtualization or Server Engineer

1.7.1.4 Storage Engineer

1.7.1.5 Network Engineer

1.7.1.6 Technical Writer

1.7.1.7 Information Assurance Engineer

1.7.1.8 Registered Communications Distribution Designer (RCDD)

1.7.1.9 A/V Engineer

1.7.1.10 Planet IRM Integration Engineer

1.7.1 The contractor shall provide IT Technical Support. The Contractor shall provide technical planning, engineering, implementation, and IT operations and management support for RRMC

IT and government users it supports in performing their mission essential functions (MEF) in an all-hazards scenario. The subsections below identify the Key Personnel and desired Contractor provided skill sets.

1.7.1.1 Program Manager (PM): The contractor shall provide a PM that is charged with maintaining program/project oversight and management of the RRMC IT effort, from the initial notice to proceed (NTP) to project completion and turn over to the Government O&M, the PM will be the prime contractor’s representative. The PM will maintain working relationships with the government client and other contractor’s while providing leadership for the RRMC IT team.

The PM will focus on schedule, milestones, and project deliverables. The PM directs and oversees the project team and works closely with the government client providing interim and quarterly program review documentation on a monthly and quarterly basis, respectively. The

PM will also manage the transmittal and Request for Information (RFI) process, change orders, and “punch list” items in addition to developing the project schedule and the critical path requirements.

This position requires training and certification within DoD 8570.01-M compliance: minimum

IAM Level I. Additionally this position requires Project Management Professional Certification and Certified Information Systems Security Professional (CISSP) Certification. This individual should have at least 8 years of Project Management experience with IT and telecommunications systems and also have experience in management, budget development, strong communications and briefing skills, and strong interpersonal skills.

1.7.1.2 VDI Engineer: The contractor shall provide personnel that are skilled in the

Engineering, Administration and Management of a Virtual Desktop Infrastructure utilizing Zero

Clients and Nutanix devices. Skills and duties include but are not limited to:

Must have at least 5 years’ experience implementing and administering VDI solutions

Design, Configure and Support Enterprise Desktop and VPN Virtualization

Technologies

Certifications in Core VMware technology skills including experience with VMware v5.x, vCenter, Application Virtualization, Desktop Virtualization (VMware

Horizon/View/ThinApp), and Profile Unity.

Experience Designing, Deploying, Managing, Monitoring and Troubleshooting a VDI

Environment for Desktops and VPNs on unclassified and classified systems.

An In-depth knowledge of VDI technologies

An In-depth knowledge of Windows Server and Desktop Environments (Windows 7, Windows Server 2008R2 and 2012R2)

Experience Configuring and troubleshooting Nutanix server based VDI deployments.

Must understand drivers for completing requests for Virtual Machines in order to successfully support the environment

An In-Depth understanding of Application Packaging(ThinApp and Cloud Volumes)

Experience Designing, Deploying, Configuring and Managing VMware-based systems for high-availability and efficiency, including vCenter, vSphere, ESXi v5.x and Horizon

View VDI.

Experience scripting and managing printers in a VMware VDI environment

Experience troubleshooting SQL environments.

Experience with Stratosphere and Teradici consoles.

Excellent Communication and Documentation skills

Installing, Configuring and Managing VPN solutions, Thin, Zero, and Full Clients

Experience Managing, Monitoring, Maintaining and Troubleshooting SQL Server

Databases (2008, 2012)

Develops and implements testing strategies and document results.

Maintains current knowledge of relevant hardware and software applications as assigned.

Participates in special projects as required.

Define SLA’s, KPI’s, and forecasting (demand management) measures for delivering

VDI services

Build and maintain product and service standards for VDI capabilities that align with technology strategies

Assess opportunities and develop automation libraries to promote reuse and standardization

Provide input to cloud solutions design function to support the creation of repeatable solution patterns

Influence and incorporate security requirements into all engineering deliverables so that security is a foundational tenant of our VDI service

Leverage a lifecycle based delivery model that is underpinned by a feedback mechanism and drives continuous improvement

1.7.1.3 Storage Engineer: The contractor shall provide personnel that are skilled in the

Engineering, Administration and Management of storage infrastructure. Skills and duties include but are not limited to:

Must have 5 years minimum experience administering SAN environments

Designs, monitors and modifies all storage related technologies; Schedules and performs storage installations and maintenance

Installs, configures and tests storage management software and hardware

Supports SAN fabric using Brocade and Cisco switches including monitoring of usage and troubleshooting; Installs, configures and maintains Fabric management hardware and software.

Performs system capacity analysis and planning to ensure storage management system operation and resource utilization optimization;

Provides efficient and reliable storage allocation and defines backup, recovery, archival procedures.

Possesses skills and knowledge related to network, operating systems, Storage Area

Network (SAN), Network Attached Storage (NAS) in a Large Enterprise Environment

Maintains storage configurations to provide capacity planning and performance monitoring/tuning of systems

Benchmarks, evaluates and makes recommendations for the selection of storage management software and hardware products

Must possess an in-depth knowledge of storage networking standards, protocols, security, performance tuning, and troubleshooting

Experience with EMC, Nutanix, NETApps, Virtual, and other storage systems

Experience with virtualizing and managing IT infrastructures, utilizing VMware

Virtualization and VMware vSphere management tools

Experience in one or more areas including Brocade, Cisco, and Juniper fibre-channel switches in SAN environments

1.7.1.4 Virtualization or Server Engineer: The contractor shall provide personnel that are skilled in Virtualization Engineering, Administration and Management of Server environments. Skills and duties include but are not limited to:

Responsible for the day-to-day support of server, app, or desktop virtualization

Disaster recovery monitoring and operations to include vCenter heartbeat, High availability (HA), Distributed Resource Scheduler (DRS), and vMotion.

Designing, recommending, and deploying emerging server virtualization technologies

Support operations of multi-site and multi-vendor environments

Performing standard administration responsibilities including:

o Monitoring and providing break/fix support to virtualized systems across the enterprise.

o Architecting system logs and identifying potential issues with computer systems.

o Introducing and integrating new virtualization technologies into existing data center environments.

o Performing routine audits of systems and software.

o Applying operating system updates, patches, and configuration changes.

o Working with Network and Storage Administration, planning, installing and configuring new hardware and software.

o Answering technical queries from other IT support teams (DBAs, app development, Networking, etc.)

o Documenting the configuration of the infrastructure.

o Troubleshooting any reported problems.

o System performance tuning.

o Responding and resolving service outages and interruptions.

Research, evaluate, and recommend new tools and technologies for server virtualization.

Identify trends and abnormalities and proactively take steps to prevent performance impacts to virtual environment and business function.

Perform pro-active support functions and reporting to maintain the integrity of the enterprise virtual environment and business function.

Take lead in the research, planning and implementation of server virtualization projects in accordance with and in support of RRMC IT goals and objectives.

Provide on-going training and technical direction to other team members pertaining to virtualization optimization, installation, upgrades, configuration, and troubleshooting.

1.7.1.5 Network Engineer: The contractor shall provide personnel that are skilled in Network

Engineering, Administration and Management of RRMC IT Systems. Skills and duties include but are not limited to:

Minimum of 5 years of experience in designing, implementing, and supporting data and converged network infrastructure including most of the following: Cabling, Routing

Protocols including OSPF, EIGRP and BGP, Wireless LAN, SAN, Load Balancers, Virtual Private Networks (VPNs), Firewalls and other network related technologies in support of a large corporate network.

A good background working/scripting with UNIX and LINUX Operating Systems.

In-depth knowledge of Juniper IOS, Cisco IOS, NXOS, BGP, OSPF, EIGRP, MPLS, FCOE and FC environments

Experience configuring/troubleshooting VRRP (Virtual Router Redundancy Protocol) networks and ring technology.

Experience with Datacenter Virtualization technologies including hands on experience with Cisco Nexus 7K, 5K, 2K, 9000 series equipment

Experience deploying and maintaining wide area networks with emphasis on IPsec, VPN, MPLS & Optical ring transport and commonly used access technologies such as

DS1/T1, E1, DS3, OC3, OC12 and Metro Ethernet

Experience with Juniper Circuit to Packet (CTP) technology.

Knowledge of IP traffic flow, protocol analysis, capturing and monitoring of live traffic streams

Extensive knowledge with Cisco UCS, Juniper environment and VMware integration

Experience with Cisco UCM and VOIP technologies

Experience with CISCO ASA (Adaptive Security Appliance).

Experience with Radius authentication.

Provide network LAN/WAN design, implementation, consulting and leadership for data and converged communications infrastructure based largely on Juniper and Cisco equipment

Performs design integration for complex, cross-functional systems and leads technical design reviews of various infrastructure projects and function as a high level technical resource.

Collect, consolidate and analyze business and technical requirements from RRMC IT

Customers. Recommend appropriate technological designs and solutions that align with the Organizational requirements, the IT Master Plan, and provides the most efficient and cost effective solution

Lead the delivery of the specific network solutions, including requirements analysis, internal proposal preparation, evaluation of supplier proposals, tool selection, and implementation planning;

Develop LAN/WAN architectures, perform network traffic analysis, predict LAN network bandwidth needs, and recommend modifications to the network configurations which reduces costs, maintains regulatory compliance and improves service

Study product samples and talk with product designers and developers

1.7.1.6 Technical Writer: The contractor shall provide technical writers to prepare SOPs, CONOPS, Technical Guides, Logistical Support Plans, Deployment Plans, and other supporting documents to communicate complex and technical information for RRMC IT more easily.

Skills and duties include but are not limited to:

Determine the needs of end users of technical documentation

Study product samples and talk with product designers and developers

Work with technical staff to make products easier to use and thus need fewer instructions

Organize and write supporting documents for products

Use photographs, drawings, diagrams, animation, and charts that increase users’ understanding

Select appropriate medium for message or audience, such as manuals or online videos

Standardize content across platforms and media

Gather usability feedback from customers, designers, and manufacturers

Revise documents as new issues arise

1.7.1.7 Information Assurance Engineer: The contractor shall provide personnel that are skilled in Information Assurance Engineering. Skills and duties include but are not limited to:

At least 5 years’ experience in information assurance, security engineering, and/or system administration.

Must be fully 8570.1 certified; operating system certifications and IA certifications

(Security+ or SSCP (CISSP, CISM, or GSLC highly desired))

Network engineering design and architecture, security implementation, firewall/IDS, Juniper and CISCO router/switch configuration experience.

Vulnerability assessment and analysis experience utilizing Assured Compliance

Assessment Solution (ACAS), DISA Gold Disk, and DISA STIGs implementation across multiple platforms (Windows, Network, DNS, Enclave, etc.).

Experience remediating, mitigating, and reporting system vulnerabilities (IAVAs)

Army certification and accreditation experience performing authoring, maintaining, and submitting accreditation and Risk Management Framework (RMF) packages thereby achieving Authorizations To Operate (ATO).

Experience working with Host Based Security System (HBSS)

1.7.1.8 Registered Communications Distribution Designer (RCDD): The contractor shall provide personnel that have demonstrated knowledge in the design, integration and implementation of telecommunications and data communications technology systems and related infrastructures. Personnel should be skilled in the creation of detailed designs of a new system and/or integrate design in an existing structure. Skills and duties include but are not limited to:

At least 5 years’ of Information and communications technology (ICT) industry design experience or an equivalent combination of experience, approved education and industry certifications.

Experience in installation, and troubleshooting of inside and outside cable plant.

Must understand and be able to apply EIA/TIA Industry Standards, NEC/ NFPA codes, and OSHA regulations.

Qualified/trained for Confined Space.

Experience designing and installing cable infrastructure for Telecommunication Rooms and large Data Centers. Registered Communications Distribution Designer

(RCDD®)and Data Center Design Consultant (DCDC) BICSI Credentials are required.

1.7.1.9 A/V Engineer: The contractor shall provide personnel that are skilled in design, installation, and troubleshooting Audio / Video Presentation systems and Security camera systems in a digital, analog and IP environment. Skills and duties include but are not limited to:

At least 5 years’ experience in design, installation, and troubleshooting of Audio /

Video Presentation and Security camera systems.

In-depth knowledge of and ability to install, troubleshoot and repair BOSCH security camera and storage systems in a digital IP environment.

In-depth knowledge of and ability to install, troubleshoot and repair facility television, public address broadcast and production systems.

In-depth knowledge of and ability to install, troubleshoot and repair facility conference room audio visual presentation systems.

In-depth knowledge of and ability to install, troubleshoot and repair facility video teleconferencing systems.

Must understand and be able to apply EIA/TIA Industry Standards, NEC/ NFPA codes, and OSHA regulations.

Basis in knowledge of understanding networks topology, equipment and capabilities in an A/V systems environment

Gather usability feedback from customers, designers, and manufacturers

Revise documents as new issues arise

1.7.1.10 Planet IRM Integration Engineer: The contractor shall provide personnel that are skilled in Planet IRM data collection, implementation, and integration development. Skills and duties include but are not limited to:

At least 3 years’ experience working and developing Planet IRM application with a

Planet Core Certification.

Has domain knowledge and Planet IRM implementation proficiency in advanced areas of IRM features and functions, such as Outside Plant, Wireless data circuits and equipment documentations.

Able to conduct Product Library and Reports Library management functions

Strong technical and troubleshooting skills in configuring and developing integrations between Planet IRM and client information sources/terminations, such as BMC

Remedy.

Strong programming skills and knowledge of Applications Programming Interfaces

Knowledge and experience in developing and maintaining Office Automation macros and VBA

Knowledge and experience in Crystal Reports or a similar report writer is highly desirable

Ability to interpret integration objectives in terms of technical development requirements is required

Performs onsite surveys of client equipment, cables, geo-locational elements, and circuits for formatting and entry into Planet IRM

Operational experience and/or domain knowledge of customer data, sufficient to normalize, analyze, format, enter, and maintain customer equipment, cable, location, floor plan, and circuit data to required levels of accuracy, completeness, and usefulness

1.7.2 Based upon the current state of the RRMC IT Systems the following staff with technical certifications may be required in accordance with table 1-8. The table below identifies the labor category (position name).

Table 1-8 Position

Program Manager

VDI Engineer

Virtualization or Server Engineer

Storage Engineer

Network Engineer

Technical Writer

Information Assurance Engineer

Registered Communications Distribution Designer (RCDD)

A/V Engineer

Planet IRM Integration Engineer

As the RRMC IT mission and operations increases, the Contractor may be required to add additional Full Time Equivalents with the required technical certifications, as identified to accommodate RRMC IT systems expansion (hardware, VDI, SAN, and network), and increased

O&M.

1.8 Identification of Contractor Employees:

The contractor shall not perform or give the appearance of performing inherently governmental functions as described in FAR Parts 2 and 7, and all applicable DoD policy. All contractor personnel shall identify themselves as contracted support personnel in all forms of communication with all entities with whom RRMC has business dealings. The contractor shall:

Answer all telephone calls and have a personalized voice message with an introductory statement that includes the individual is contracted support.

Include a title block in all emails that states the fact that the person is contracted support.

Ensure all those with whom the person interacts in any face-to-face dealings while supporting EITSD understands that the person is contracted support.

At all times wear the appropriate assigned government badge while in the Pentagon or other government buildings.

Moreover, all contractor personnel attending meetings, answering government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression that they are government officials.

1.9 Travel and Other Direct Charges (ODC). Temporary Duty (TDY) Travel in support of this contract may be required as personnel are expected to attend meetings, industry, DoD and federal conferences and site visits. The contractor shall provide a written request for travel to the COR prior to finalizing any travel arrangements and two weeks before travel. Requests for travel shall include the name of the person traveling, the travel destination, dates of travel, mode of transportation, and estimated costs by cost type. All travel must be pre-approved in writing by the Contracting Officer and the COR prior to purchase of any tickets and commencement of travel. The contractor shall be reimbursed for actual allowable, allocable, and reasonable travel costs incurred during performance of this effort in accordance with the FAR 31.205-46 “Travel

Costs”. Thus, travel cost reimbursement shall not exceed the prevailing applicable per diem rates and limitations specified in the applicable regulations in FAR 31.205-46. Under the FAR travel cost principle, for contractors traveling in the contiguous United States, maximum per diem rates are set in the FTR. For contractors traveling in Alaska, Hawaii, and possessions of the United

States, the maximum per diem rates are set in the JTR. For contractors traveling to areas outside the United States and its possessions, the maximum per diem rates are set in the SR. For the purposes of this contract, local travel within 100 miles radius of the NCR will not be reimbursed.

The government is not responsible for, nor will it reimburse, normal commuting costs and contractor parking arrangements in order to perform work at the government site.

Travel and other direct costs (ODCs) will be built into the contract as a cost reimbursement contract line item number (CLIN) and total travel and ODC costs allocated to the contract will be provided at the time of contract award by the government.

1.9.1 Travel Documentation Requirements. Separate worksheets shall be submitted for each traveler. The travel documents shall delineate at a minimum and as applicable the following information:

a. Name Individual(s) traveling

b. current invoice period

c. persons travel

d. days of travel

e. travel dates

f. number of days being charged per diem

g. per diem rate used

h. total per diem charged

i. transportation costs

j. other costs

k. total charges

1.9.2 Trip Reports. The contractor shall submit a summary of each TDY trip to include dates and times for travel and work, meetings attended, activities performed and personnel visited with contact information provided, as required by the government and in a format designated by the government. Trip reports are due no later than five business days after travel.

1.10 Data Rights. The Government has unlimited rights to all documents/material produced under this contract. All documents and materials, to include the source codes of any software, produced under this contract shall be Government owned and are the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the Government.

These documents and materials may not be used or sold by the contractor without written permission from the Contracting Officer. All materials supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights. The Contractor shall obtain Government approval prior to

Contractor use of Contractor provided hardware and software in the performance of this work.

1.11 Organizational Conflict of Interest. Contractor and subcontractor personnel performing work under this contract may receive, have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services which may create a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR

Subpart 9.5. The Contractor shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. The

Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the

Contracting Officer and in the event the Contracting Officer unilaterally determines that any such

OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may effect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

1.12 Transition Phase-In Plan.

The contractor shall provide transition-in services. The contractor shall complete Transition-In services within 60 calendar days of the contract effective date.