HQ0034-16-R-0218-0001_RRMC_IT_Support.docx

HQ0034-16-R-0218

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 1449 - CONTINUATION SHEET

SOLICITATION/CONTRACT FORM

The required response date/time has changed from 14-Nov-2016 11:00 AM to 28-Nov-2016 11:00 AM.

The following have been modified:

PWS

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 enterprise IT services including 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:

· The environment within RRMC IT must enable the customer to provide Enterprise Services throughout the Department of Defense.

· The technical approach shall 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 technical approach must incorporate the capability for Contractor personnel to perform “in-house” maintenance using on-site stored hardware and repair parts.

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;

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

· Provide innovative unified capability (UC) IT solutions that improves security, increases efficiencies, and improves command & control mission effectiveness to meet increasing demands.

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

· 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 of 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. (See Technical Exhibit 3)

· 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. The Contractor shall provide 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 shall 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 - TBD Option Year I - TBD Option Year II - TBD Option Year III - TBD Option Year IV - TBD

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 in accordance with time frames specified by the Contracting Officer (CO) and/or Contracting Officer Representative (COR). 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 or second notice), the Contractor shall complete applicable sections and return it to the CO or COR within time constraints directed 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 will 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.

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. 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) 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) include after hours on weekdays, weekends and holidays. Extended work hours shall be the same labor rate as normal work hours (NWH).

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 an indefinite delivery, indefinite quantity (IDIQ) contract type.

1.6.7 Security Requirements: Contractor personnel performing work under this contract must have a minimum active DoD security clearance (SECRET). .The Contractor shall 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

The Contractor and all associated subcontractor employees shall provide all information required for background checks to meet installation access requirements to be accomplished by the installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor em[loyees shall 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.

The 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 counterintelligence (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

Privileged

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 Security Manager 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 CO or COR.

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 Officer’s 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 a 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.6.10 Environmental Protection: The Contractor is accountable to comply with local, state, and federal laws pertaining to the environment in effect at contract award and enacted and put into effect during the performance period. Examples of some of the hazardous substances which may require environmental action are: asbestos, CFCs, lead, PCB, mercury, waste water, water, furnace emissions, vehicle emissions, VOCs, oil, waste oil, pesticides and herbicides. These examples constitute the most significant volume of materials for which the Contractor has environmental accountability. There may be other substances that require environmental action as new laws become effective. All of the facilities operated and maintained by the Contractor may be inspected by local, state or federal Inspectors. The Contractor shall pay all environmental fines and penalties attributable to Contractor negligence.

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 Data 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 Management (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 contractors 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. Certified Information Systems Security Professional (CISSP) Certification is not required but is desired. 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 Engineering Services: 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.

· Knowledge 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.

· Experience configuring and troubleshooting Nutanix server based VDI deployments.

1.7.1.3 Virtualization/Server Engineering Services: 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:

· 5 years of prior similar duties and experience or familiarity with virtualization technologies

· Scripting experience desired (PowerShell/WMI/Shell)

· Strong knowledge and hands on experience with virtualization technologies such as server virtualization (using VMWare ESX/vSphere or Hyper-V) and/or application/desktop virtualization using (VMware View/Horizon)

· Strong working knowledge of Microsoft server and workstation operating systems, registry settings, DNS/DHCP, TCP/IP networking, and firewalls

· Experience working with Microsoft Active Directory

· Experience with Microsoft Exchange, SQL, Office Communications Server

· Knowledge of Disaster Recovery and Business Continuity best practices

· Experience with SSL VPNs including Cisco ASA, and Juniper solutions

· Knowledge of Cisco UCS and Fabric Interconnects

· Knowledge of large VMWare deployments

· Experience with IBM, Dell, HP, or Nutanix Server Platforms.

1.7.1.4 Storage Engineering Services: 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.

· 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.5 Network Engineering Services: 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.

1.7.1.6 Technical Writer Service: 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:

· 3+ year experience with a technical subject such as computer science, engineering, telecommunications, or IT.

· A Bachelor’s degree in journalism, English, or communications is desireable

· Experienced in developing the following types of documentation;

· Technical Manuals and user guides

· Policies and procedures

· Document updating

· API Documentation

· Knowledge Articles

· SOPs

1.7.1.7 Information Assurance Engineering Services: 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 is desired.

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

· Certification and accreditation experience performing authoring, maintaining, and submitting accreditation and Risk Management Framework (RMF) packages.

· Experience working with Host Based Security System (HBSS).

1.7.1.8 Registered Communications Distribution Designer (RCDD) Service: 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®) BICSI Credentialis required.

1.7.1.9 A/V Engineer Services: The Contractor shall provide personnel that are skilled in design, installation, and troubleshooting Audio / Video Presentation 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.

1.7.1.10 Planet IRM Integration Engineer Services: 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.

· 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 Crystal Reports or a similar report writer is highly desirable.

1.7.2 As the RRMC IT mission and operations increases, the Contractor may be required to add additional Full Time Equivalents (FTEs) with the required technical certifications, as identified to accommodate RRMC IT systems expansion (hardware, VDI, SAN, and network), and increased O&M. The Contracting Officer will coordinate with the Contractor to issue a task order to support the additional work.

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 identifies 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 with 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 Cost (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 at least 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 Federal Travel Regulation (FTR). For Contractors traveling in Alaska, Hawaii, and possessions of the United States, the maximum per diem rates are set in the Joint Travel Regulation (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:

· Name Individual(s) traveling

· Current invoice period

· Persons travel

· Days of travel

· Travel dates

· Number of days being charged per diem

· Per diem rate used

· Total per diem charged

· Transportation costs

· Other costs

· 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 (5) 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. The 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. At a minimum the Contractor shall reach a 50% staffing level within 30 calendar days of the contract effective date. At a minimum the Contractor shall reach a 75% staffing level within 45 calendar days of the contract effective date. The Contractor shall reach 100% staffing levels within 60 calendar days of the contract effective date. The Contractor shall work professionally with the Government to achieve a successful and timely transition. The Contractor shall transition all services without interruption or degradation of service levels. The Contractor shall verify system and facility access with the Government.

The Contractor shall submit a draft transition-in plan. The Contractor shall conduct a transition-in kick-off meeting with the program office, and the Contractor shall submit a kick-off meeting presentation to the Government.

The Contractor shall submit a final transition-in plan. The final transition-in plan must be detailed and include start-up activities that may be required to transition to full operational capability to successfully assume all duties under this PWS. The final transition-in plan must include identification of key transition events and objectives with a corresponding completion timeline. During transition in, the Contractor shall become familiar with performance requirements and establish the management organization.

The Contractor shall be 100% transferred in within 60 calendar days of the contract effective date, and it shall submit a Transfer Complete Report. The Contractor shall conduct a weekly “Transition Status” meeting throughout the transition-in, and it shall submit a Transition Status Report.

1.13 Transition Phase-Out Plan. The Contractor shall maintain complete documentation that is 100% assessable to the designated Government representatives via a web portal or some other method directed by the Government. The Contractor shall overlap with the incoming contractor during the transition out period, work with Government personnel and the incoming contractor to transfer all knowledge, information and documentation for all projects and tasks related to this contract. At all times during the transition-out period, the Contractor must exhibit professional conduct and work hand-in-hand with the incoming contractor to provide for a successful transition-out.

The Contractor shall submit a draft transition-out plan (Deliverable 9) and a final transition out plan. The final transition-out plan must include all pertinent information for a successful transition, to include at a minimum:

1. Project management processes

1. Points of contact

1. Location of technical and project management documentation

1. Status of ongoing technical initiatives

1. Appropriate contractor to contractor coordination to ensure a seamless transition

1. Schedules and milestones

1. Document operational baseline

1. Actions required of the Government.

1. Effective communication with the incoming contractor

PART 2

DEFINITIONS & ACRONYMS

2. DEFINITIONS AND ACRONYMS:

2.1. DEFINITIONS.

2.1.1. CONTRACTOR. A supplier or vendor awarded a contract to provide specific supplies or service to the government. The term used in this contract refers to the prime.

2.1.2. CONTRACTING OFFICER. A person with authority to enter into, administer, and or terminate contracts, and make related determinations and findings on behalf of the government. Note: The only individual who can legally bind the government.

2.1.3. CONTRACTING OFFICER'S REPRESENTATIVE (COR). An employee of the U.S. Government appointed by the contracting officer to administer the contract. Such appointment shall be in writing and shall state the scope of authority and limitations. This individual has authority to provide technical direction to the Contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract.

2.1.4. DEFECTIVE SERVICE. A service output that does not meet the standard of performance associated with the Performance Work Statement.

2.1.5. DELIVERABLE. Anything that can be physically delivered, but may include non-manufactured things such as meeting minutes or reports.

2.1.6. KEY PERSONNEL. Contractor personnel that are evaluated in a source selection process and that may be required to be used in the performance of a contract by the Key Personnel listed in the PWS. When key personnel are used as an evaluation factor in best value procurement, an offer can be rejected if it does not have a firm commitment from the persons that are listed in the proposal.

2.1.7. PHYSICAL SECURITY. Actions that prevent the loss or damage of Government property.

2.1.8. QUALITY ASSURANCE. The government procedures to verify that…