180817_Grey_Wolf_Network_RFP_REV1.docx

Grey Wolf Pocatello PROCUREMENT SENSITIVE 08/17/2018 U.S. Department of Justice Federal Bureau of Investigation Finance Division / Procurement Section

Federal Bureau of Investigation/ Department of Justice Grey Wolf Buildout RFP No. 18-9138

Request for Proposal August 17, 2018 Rev 1

Contents

1.0 BACKGROUND – DOJ/FBI

The Information Technology Infrastructure Division (ITID), Data Center Hardware Operating Systems Section (DCHOSS) is charged with supporting the FBI’s core missions by providing and supporting effective and efficient Information Technology (IT) systems. These systems provide a platform and hosting environment for investigative and administrative applications to the FBI end user community and are used by more than 60,000 employees, contractors, and other Government personnel agency-wide. The Section is also responsible for the administration and daily operations of all Core Enterprise data center Facilities (CEF’s). In response to the Data Center Optimization Initiative (DCOI), an expansion to the CEF in Pocatello, Idaho, is scheduled for completion in 2018. This new CEF will serve as one of three primary data centers for all DOJ Agencies, consolidating applications from more than 100 legacy data centers. The new CEF will be multi-tenant and will provide networking transport as a service to all customers globally.

2.0 SCOPE

Establish a new contract to obtain network systems and services. In the first year obtain data center networking for the CEF expansion in Pocatello. LAN Components are to be suitable for a large cloud centric multi-tenant data center with a spine/leaf fabric. Policy-driven fabric controllers, network orchestration controllers, network and security analytics systems, network intent assurance tools, and out of band management are to be addressed. The network installation will be green-field and will require all servers, appliances or other systems necessary to stand up controllers or tool suites proposed be included in the Proposal. In addition, WAN-Edge connectivity and campus networking for additional local office space are to be addressed. WAN Edge components are required to support propriety protocols and to adhere to the Security in-depth design deployed at other Datacenters. This hardware covers network modules and routers required to build Secure IP paths to FBI remote offices LANs. This hardware also includes Firewalls and IPS applications required to support internal Demilitarized Zones (DMZ) at the Datacenters.

Temporary warehousing, inventory, pre-installation preparation, rack and stack, and post installation services must also be addressed. Formal training on all components provided must be included. Post installation will include on-site network engineers to support tenant move-ins, integration with tenant systems, automation and API integration, and the development of documentation and standard operating procedures for support and documentation of the new CEF expansion. All components must be flexible and open to allow for integration with tenant systems from multiple vendors without requiring extensive tenant redesign or complex work arounds. Automation of repeatable processes will be implemented during the first year of operation to provide a system where multi-tenant provisioning of resources and sustainment can be achieved with a minimum number of staff.

During normal operations, the CEF expansion must be able to inter-operate with all other geographically separate DOJ data centers as one virtual data center. In the event of disaster, major event, or CEF outage, the CEF expansion must be able to operate as the sole data center for all DOJ entities worldwide.

The hardware and software maintenance and on-site support services shall include network administration, network engineering, performance tuning, third party product integration, software upgrades and hardware component support to keep the current infrastructure running at optimal performance. This shall include; but not be limited to: break fix, network service provisioning, component replacement, software installation and patching, configuration and maintenance.

3.0 CONTRACT TYPE

This contract/contracts will be a Hybrid with base plus four option years. The option years will consist of maintenance and on-site engineering services only with no expectation of additional system purchases.

The EDCN Price Template is included as an Attachment, with fields to capture discounts. Offerors shall provide the percent discount for each item offered for each Period of Performance (POP). The Government reserves the right to renegotiate discounts if the list prices increase.

3.1 Contract Line Item Number (CLIN) Structure

The CLIN structure for this contract/contracts shall be as stated below. Contract Type for each CLIN shall be Firm Fixed Price or Time and Materials as outlined in the table below. CLIN A and CLIN B will have different evaluation criteria.

As a result of this competition, there may be a single award or a multiple award. Offerors that meet the qualifications for CLIN A are free to bid on CLIN B as well.

3.2 Labor/Product Availability

CLIN A – WAN (Brand-Name Only CISCO) Only OFFERORS with a valid, posted and verifiable CISCO Gold Partner or CISCO Premier Partner certificate will be eligible for consideration. Discounts, expense and overhead will be built into all rates offered to the Government. Throughout the life of the Contract, the Government anticipates that labor categories and products not originally proposed in the Contractor’s price catalogue may become necessary. In such event, the Government and the winning Offeror will enter into bilateral negotiation for pricing and any unique terms and conditions.

CLIN B – LAN

Specific requirements follow.

A. WAN (Brand-Name Only CISCO):

A1. On-Site Engineering and Installation Services:

Network Technology Architect / Engineer Duties and Responsibilities

· Participates as a network expert in meetings and discussions. Works with the Government, OEMs, and contractor support personnel in designing, testing, configuring, implementing, diagnosing and solving the Government's network challenges.

· Provides network systems product support and maintenance in accordance with OEM standard practices and Government policies.

· Uses available resources to maintain knowledge of available network software patches and upgrades and recommends appropriate implementation to the Government.

· Assists the Government in tenant installations and provisioning of network systems.

· Performs network engineering. Establishes standard operating procedures, and maintains documents on current configurations and methods.

· Maintains knowledge of state-of-the-art networking and provides networking technology information to the Government with recommendations.

· Designs, executes, and reports detailed Government network environment benchmarks and performance analyses on a monthly basis. Uses tools to optimize performance.

· Provides oversight of installation, testing and maintenance of network hardware.

· Under Government supervision and oversight, provides for the implementation, integration, and refresh of new or revised systems.

· Tracks and reports to the Government quarterly software license allocations and usage.

· Under Government supervision and oversight, implements new or revised network solutions into operations, to include the planning and execution of Government testing.

· Develops and recommends network architecture designs, strategies, documentation and plans for Government approval, including disaster recovery solutions.

· Under Government supervision and oversight, implements approved designs, strategies, and plans, including disaster recovery solutions.

A2. WAN -- Hardware/Software Purchases and Maintenance:

· There will be two separate Point of Presence (POP) rooms within the data center, each with 10 cabinets for all WAN systems. WAN systems should be equally distributed between the POP rooms to ensure redundancy and path diversity for all circuits into the data center.

· A proposed single vendor solution from Cisco is included in the attached EDCN Price Template spreadsheet. For the WAN portion, no substitutions will be considered.

· The solution shall support Cisco configuration for use with network encryption devices using the DMVPN network protocol to establish a mesh network between all Government sites.

· Shall support multicast to stream video using Generic Routing Encapsulation (GRE) tunneling to pass traffic through the unicast-only encryption devices.

B. LAN:

B1. On-Site Engineering and Installation Services:

Network Technology Architect / Engineer Duties and Responsibilities

· Participates as a network expert in meetings and discussions. Works with the Government, OEMs, and contractor support personnel in designing, testing, configuring, implementing, diagnosing and solving the Government's network challenges.

· Provides network systems product support and maintenance in accordance with OEM standard practices and Government policies.

· Uses available resources to maintain knowledge of available network software patches and upgrades and recommends appropriate implementation to the Government.

· Assists the Government in tenant installations and provisioning of network systems.

· Performs network engineering. Establishes engineering documentation, standard operating procedures, network drawings, and maintains documents on current configurations and methods.

· Maintains knowledge of state-of-the-art networking and provides networking technology information to the Government with recommendations.

· Designs, executes, and reports detailed Government network environment benchmarks and performance analyses on a monthly basis. Uses tools to optimize performance.

· Provides installation, testing and maintenance of network hardware and software components.

· Under Government supervision and oversight, provides for the implementation, integration, and refresh of new or revised systems.

· Tracks and reports to the Government quarterly software license allocations and usage.

· Under Government supervision and oversight, implements new or revised network solutions into operations, to include the planning and execution of Government testing.

· Under Government supervision and oversight, implements approved designs, strategies, and plans, including disaster recovery solutions.

· Under Government supervision and oversight, creates, implements and supports automated/orchestrated network solutions leveraging API’s via JSON, Python, Ruby, or comparable.

· Under Government supervision and oversight, engineer, implement and maintain Software Defined Networking (SDN) controller architectures.

· Consults with Application SME’s on telemetry information and essential communications.

· Analyzes telemetry to create security contracts or equivalent and enforce tenant separations.

· Provides troubleshooting and support of security contracts or equivalent

· Utilizes real-time telemetry data from application components and uses behavior-analysis algorithms to identify application groups and their communication patterns and service dependencies

· Under Government supervision and oversight, engineer, implement and maintain load balancer and firewall solutions and their integration with the network fabric. Develop towards an as a service model for each.

· Under Government supervision and oversight, engineer, implement and support Storage Area Networks using ISCSI, Fiber-Channel, or equivalent alternatives.

· Performs rack mounting of hardware using approved vendor installation techniques and mounting systems, power connectivity to rack PDUs, and burn-in of electronic systems

· Performs connectivity of network hardware to pre-installed data center optical transport systems, link testing, and fault isolation of faulty links across transport

· Under Government supervision and by direction, assists with tasks associated with the design, implementation and support of data center networks.

B2. LAN -- Hardware/Software Purchases and Maintenance:

· The Offeror will provide a spine-leaf network solution with WAN connectivity to other DOJ CEF’s and customer locations worldwide

· For the day 1 LAN portion, the Proposal will accommodate 120 network cabinets and 576 server/storage cabinets with spine components in the network cabinets and leaf components in the server/storage cabinets.

· Proposed Leaf devices shall each be capable of servicing 3.6Tbps of performance or greater

· Proposed Leaf devices shall each provide a MAC table size of 250,000 or greater

· Proposed Leaf devices shall each provide a minimum of 30MB of buffer space per device

· Proposed Spine devices shall each provide 150Tbps of performance or greater

· Proposed Spine devices shall each support a minimum of 450 100Gbps with at minimum half being reserved for future expansion

· Network cabinets are collocated in groups of 30 cabinets which service server/storage pods which consist of 36 cabinets, for a total of 696 cabinets equally separated between classified and unclassified use. The data center can be expanded up to a total of 1392 cabinets.

· Each server/storage cabinet will have an OM5 multi-mode patch panel leading to the Network cabinets

· Analytics, Orchestration, and Assurance components for the Fabric must be provided and proven to integrate with the full proposed solution with the ability to incorporate third party products which may be brought in by tenants.

· All management, analytics, assurance, and orchestration tools must be sized appropriately for the scale of the architecture with the ability to extend between multiple CEF’s. Day 1, the proposed solution shall support a minimum of 8,000 end points; 5,000 end points on one network and 3,000 end points on the other network and be capable of expanding to support double those end points from a common dashboard as other sites and services come online in the future.

· The Analytics Platform must have the ability to integrate with the network fabric in order to collect and enforce usage policy

· Out of band management leaf switches must be provided for each server/storage cabinet with a minimum of 24 10/100/1000 ports per switch, not to include uplink ports. The management ports will be copper. Each switch will have a minimum of two 10Gbps multimode fiber ports for uplink to the spine.

· Out of band management leaf switches must be provided for each end of the network cabinet row with a minimum of 48 10/100/1000 ports per switch, not to include uplink ports. The management ports will be copper. Each switch will have a minimum of two 10Gbps multimode fiber ports for uplink to the spine. There are a total of 8 network cabinet rows.

· Leaf switches for the server/storage cabinets will have reverse flow fans to ensure separation of hot/cold isles. By default, these devices will be mounted with ports to the rear of the server/storage cabinets

· Out of band management components must also have zero touch provisioning capabilities and policy based automation controllers.

· The new CEF expansion will be separated into two equally sized and separately operated networks. One for Unclassified traffic, and the other for classified traffic. 60 network cabinets each, and 288 server/storage cabinets each

· A smaller unclassified transport network of six cabinets will also be on site to manage WAN components. These cabinets are in addition to the LAN cabinet numbers.

· Standard capacity server/storage cabinets will have a single 48 port leaf switch in each

· Standard capacity cabinet server/storage systems will share the ports in two cabinets for path redundancy.

· High capacity server/storage cabinets will have two 48 port leaf switches (estimate 72 cabinets)

· A proposed single vendor solution from Cisco is included. Alternative vendor’s solutions to the LAN portion of this requirement will be considered. Use this reference list of components as a guide in providing feedback on the detailed technical capabilities of the LAN products provided in the Proposal. Provide line by line technical equivalents for each component. This example bill of materials is being provided as a comprehensive technical document describing equivalent capability would require an exceptionally large requirements document that would not allow vendors to provide flexibility in their approach.

· Alternatives to the examples in the spreadsheet and Cisco BOM example will be accepted, but should meet similar operating specifications such as performance and connectivity.

· Fabric controllers must be able to support auto provisioning of devices on both management and data networks.

· The network fabric must support and include micro-segmentation of applications and workloads.

· The current plan and BOM includes the plan for re-use of GFE optics from a legacy data center for leaf switches. If a non-Cisco switch is proposed, additional optics must be included in the Proposal. Quantity of 1,090 1Gbps multimode fiber, quantity of 284 1Gbps copper, and quantity of 1,745 10Gbps multimode fiber.

· Only optics that use 2 strand fiber will be accepted due to limitations in the passive cable infrastructure. If Cisco, all optics must support BiDi to minimize specialized patch cabling. If non-Cisco, provide options that minimize specialized patch cabling for various speed connectivity.

· Leaf switch must support speeds of 1, 10 and 25 Gig, in addition another 30 switches must be provided that support 40/100 Gig for special use cases.

· Spine to Leaf connection speeds must be 100 Gig

· Ten additional out of band management switches will be provided that support 10 Gig copper. Switches must be 1RU fixed form factor.

· Out of band management spine switches must be able to support a mix of copper 1 and 10 Gig connections. The uplinks will be 10 Gig fiber multimode.

· Out of band management leaf switches must be able to support copper 10/100/1000 connections. The uplinks will be 10 Gig fiber multimode.

· The solution must be capable of integrating with an Enterprise deployment of Cisco ISE for end to end segmentation

4.2 Network Services – DOJ/FBI

Configuration Requirements:

Hardware WAN hardware and sample LAN hardware for this requirement is provided in the Attachment EDCN Price Template. The final list of equipment will be determined at time of award. The Government reserves the right to add to this list of hardware due to technical refreshment as deemed necessary to provide support and maintenance for mission critical components.

Software WAN software and sample LAN software for this contract is provided in the Attachment EDCN Price Template. The final list of software will be determined at time of award. The Government reserves the right to add to this list of software due to technical refreshment as deemed necessary to provide support and maintenance for mission critical components. Government will negotiate price for any additional software identified.

Maintenance:

Availability Hardware and software maintenance services under this requirement shall be available 24 hours a day, 7 days a week with a four hour on-site or telephonic response time.

Outage Response In the event of a failure resulting in a system outage, the Contractor shall provide additional on-site OEM services within four hours of the identification of the need to provide maintenance services.

Hardware Maintenance The Contractor shall provide maintenance services (e.g. all services, break fix, support, response times, spares, and other items and services normally associated with the OEM warranty of new equipment) for supported equipment.

Software Upgrades Software upgrades (i.e. hot fixes, patches, etc.) shall be provided to the Government without additional cost.

Licenses The Governments preference for all software licenses in the proposal are for both perpetual and enterprise for unlimited use. If subscription-based software licensing is the only option, it must be specifically approved and documented. The Government reserves the right to transfer location of these licenses under the terms of the license.

Software Maintenance The Contractor shall provide OEM software maintenance services to include all commercial services normally provided under commercially available OEM software support. This support shall include, but shall not be limited to, software revisions, patch upgrades, and on-call support and troubleshooting services.

On-site Spares:

Access The Contractor shall ensure the on-site support service individuals, both Government and contractor, are provided access to, and are authorized use of any required on-site spares if parts depots are not located in four-hour proximity to the data center.

Sparing The Contractor shall provide the OEM sparing strategy (to include floor space, cabinets, etc.) to align with current Enterprise Support Services (ESS) operational procedures and service times as part of their response to this RFP.

Supply and Replenishment If parts depots are not located in four-hour proximity to the data center, the Contractor shall provide all on-site spares and replenish all spares used from the on-site spares at no additional cost to the Government. Note that non-volatile components (hard drives, flash memory) that cannot be sanitized according to FBI Security procedures will be retained by the FBI at no additional cost.

Inclusions Spares shall include all necessary spare parts, including but not limited to spare drives, spare switches, spare memory, spare batteries and spare power supplies.

General Project Scope The following requirements apply to LAN, WAN and Services

The vendor shall:

· Provide integrated network hardware, software and services solutions to address the needs of the CEF expansion.

· Provide on-site consulting (to include rack and stack, cabling, base configuration and advanced configuration services) for all stages of the implementation (pre/post/during) in classified and unclassified environments.

· Provide technical documentation within the bounds of the end user license agreement.

· Provide operations and maintenance (O&M) access to patches, updates, bug fixes, and work-arounds. Work-arounds include pre-views of early releases which may solve any current software problems. Patches include solutions in the form of firmware/software or functional configurations for any security vulnerabilities within 24 hours for critical vulnerabilities and 48 hours for other vulnerabilities.

· Provide a test plan to validate the performance of the system for final acceptance after installation and configuration is complete.

· Provide a final design and documentation

· Assist in system accreditation through development of design, documentation, security tests, test result reports and security issue mitigations.

· Provide network engineering services full time on-site. The first year will require an unspecified number of on-site engineers depending on the final solution selected.

· Provide access to Letters of Volatility, Certificates of Conformity, and Section 508 compliance documentation for all systems.

· Provide component non-return maintenance options for items that cannot be sanitized.

· Provide electronic capability to submit and receive software technical solutions (i.e. e-mail problem issues support, vendor portal submission of problems or issues to obtain product resolution support, software, upgrades, patches, fixes, documentation, and literature).

· User Manuals, authoritative guides (white papers) and technical functional capabilities of the components.

· Hardware and software product compatibility and systems requirements literature.

· Pre and post installation inventory.

· Warehousing of components until systems are ready to ship as complete, rather than components.

· Warehousing at the vendor’s secure site until CEF’s are able to accept deliveries for install. Estimated completion window of March 2019 through August 2019.

· Provide training credits for all components.

· Pre-installation (assembly) of systems.

· Rack and stack of systems.

· Attach uplink cables from systems to patch panels and label cables

· Attach cables between network devices in the same rack

· Label cables

· Post-installation (base configuration) of systems.

· Sustainment support augmentation

· All components and configurations must meet FISMA standards of operation for classified environments.

· No remote access to the systems or system logs will be provided.

General Requirements

· All components must be OEM and TAA validated.

· All solutions must include vendor validated design documents. If a multi-vendor solution is proposed, all vendors included in the solution must provide vendor validated designs that guarantee their integration and interoperability with the other vendor components.

· All submitted proposals must be based on technologies already proven to work in data centers of similar or larger scale to the Pocatello CEF and include vendor certification of scalability and support.

· Provide staff augmentation and consulting services for the installation and configuration of all systems and assist with full integration within the data center for one year as the CEF expansion is populated. To include rack and stack and cabling of all components and development of automation scripts.

· All systems will be integrated with a base configuration for day 1 use and configurations matured and tuned as tenants move in.

· Automation and Orchestration tools will be configured and documented and changes and integrations made as required for production use.

· Provide detailed technical explanation, overview, and documentation of the systems configuration to include setup, installation, mapping, administration, and troubleshooting.

· On-site support for all aspects of network support to include engineering, optimization and coordination of break-fix issues. After hours and weekend work when required will offset regular weekday work hours and shall be billed at a fixed price rate

· Documentation of the systems configuration and logical/physical mappings.

· Provide documentation of all components and full systems to include all serial, model and location details for inventory.

· Full time on-site engineers should be available after normal working hours to address issues and to perform functions during times that are least disruptive as the CEF becomes operational

· All non-warehouse work must be performed on-site, with no expectation of remote work or access

· Provide deliveries according to timeframes determined by CEF availability to receive the systems.

· All on-site staff must have a Top Secret clearance and capable of passing an SCI polygraph.

Standard Network Requirements

· All components will address high availability with included redundancy for power supplies, control models, multi-paths, and resiliency for self-healing

· All components shall be Jumbo Frame capable

· Cabinets, rack PDU’s, and standard host patch cables will be government provided

· All top of rack patch panels will be LC connections

· All uplink cables for network devices to the top of rack patch panels, or between network devices in the same rack will be provided as part of the proposal.

· All uplink ports leaving the cabinet must be fiber optic and redundant.

· Power plugs in the data center cabinets will be C19 and C13 at 230volts. All proposed components must be delivered with C19 or C13 power cables. In instances where the Vendor is unable to provide the required power cables with the specified connections, the re-seller must ensure 3rd party power cables are provided.

· Ensure that no components will result in bottlenecks within the design as only a fraction of the systems and workloads that will be going into the data center are known at this time.

· With a multi-tenant environment, no single use case is appropriate. Uses will include everything from simple file/print servers to enterprise scale Big Data clusters.

· Currently deployed CEF’s do not use the proposed Spine/Leaf architecture and no multi-tenant LANs are currently in use across the agencies. Therefore, no actual use case metrics are available to derive required performance numbers. Vendors should provide solutions equivalent to large scale Internet Service Providers (ISP’s) and Public Cloud Providers (PCP’s) in determining size and scale of models to offer.

· All Orchestration, Assurance and Analytics components must include licensing and support for multi-vendor environments as each tenant is permitted to bring their current systems or to purchase new as they relocate to the new consolidated CEF. Both Linux and Windows systems will be present.

· Tools must be provided to manage all possible networking facets of a multi-tenant data center, to include workflows, logs, approvals of changes, and validation/integrity of changes before and after implementation.

· All management components must support multi-tenant environments within the data center for both management, security and reporting functionality.

· All networks must support a multi-tenant data center in the ability to allow tenants to both manage and monitor the standard infrastructure of the CEF and components they bring to the CEF

· All Proposals must include both basic and advanced capabilities in the Proposal. For example: All tools should include GUI, CLI, and API interfaces at a minimum.

· All components, to include all hardware and software must be managed by limited numbers of panes of glass, to be included within the Proposal. One is preferred.

· All components must be able to utilize open northbound and southbound API’s.

· Must be able to support Role Based Authentication (RBAC) and integration with TACACS, RADIUS, AAA, and RSA.

· Analysis tools must be able to support the use of dynamically collected data for continual learning and implementation of that data into actionable network tuning.

· Provide tools for dynamic inspection of data to address forensic needs and operational optimization.

· Provide details on how the Proposal implements security. Example: blacklist, whitelist, audit logs, anomalous network traffic detection, etc.

· If this Proposal is implemented successfully, it will be extended to other CEF’s. Provide details on how multi-site management, assurance, analytics, orchestration and security integration will be addressed between sites, and the tools extended.

· Provide information on how the proposed management tools are implemented for redundancy both within one data center and between multiple data centers.

· Provide details on how the proposed solution will integrate with existing Cisco enterprise network components and technologies such as ISE, SD Access, and SD WAN.

· Ensure all proposed design components are correctly scaled to the current data center specifications and can be expanded and scaled to support the potential growth of the additional cabinets and expansion of the management systems/software for a secondary equivalent sized data center.

Campus Network Requirements

· User access to support 300 users in office space (campus network), 1 Gig Fiber connection ports for user connectivity (50 micron). Uplinks will be single mode fiber (redundant pairs of 40 Gig) Warehousing / Staging Requirements

· Provide secure storage with restricted access to include access validation/monitoring

· Provide secure assembly area with restricted access

· Ensure only authorized removal of systems for shipment or to assembly area

· Receive and inventory all components

· Assemble all components into final system configurations in preparation for racking and cabling.

· Confirm power on test for any equipment dead on arrival (DOA)

· Manage RMA’s as needed

· Affix agency barcodes and update inventory

· Install latest patches and firmware upgrades.

· Burn in (minimum 24 hours) and install base configurations on all devices developed by the on-site engineers

· Re-box and prepare for shipment to final install locations.

· Access should only be granted to those with background checks

· Validate approval for all shipments with the Government POC and provide shipping information to Government POC

· Provide specific details on how the equipment will be safeguarded while in the custody of the vendor.

Proposal Deliverables

· Documentation on the systems configuration and logical/physical mappings.

· A comprehensive list of all required software and tools to manage, monitor, and support the systems.

· Access to User Manuals on the current version, specifications and Quick Reference Guides

· An estimated timeline for all phases of the proposal

ON- SITE AND OFF–SITE

The on-site support service and engineering individuals provided under this contract shall be designated as key personnel. Key personnel requirements (See Section 12.6) shall be extended to any subcontractors supplying on-site support service individuals.

The on-site support engineering individuals required under this requirement shall be provided full-time, however, the Government reserves the right to decrease the full-time on-site support services.

Full-time labor services individuals shall meet all security requirements for access to Department of Justice (DOJ) information technology systems as specified in Section 12.6, including access to law enforcement information, classified information, and personally identifiable information (PII). Full-time labor services individuals shall possess a top secret clearance to access information, which may include top secret and specialized access information.

5.0 GOVERNMENT FURNISHED INFORMATION / EQUIPMENT / SOFTWARE:

The Government will provide a typical working environment, including office furniture and furnishings, storage for materials, and access to copiers, fax machines, personal computers (PCs), telephone and related software.

6.0 DELIVERABLES

The Contractor shall deliver the following to the Contracting Officer Representative (COR):

Delivery and performance shall be in accordance with relevant sections of this RFP and associated delivery orders. No changes in delivery and performance schedule shall be made without the written authorization of the Contracting Officer. Format of deliverables will be determined after award by the COR and the Contractor. Pricing discounts included in the Proposal for goods and services in support of the deliverables shall be honored for the life of the contract.

All deliverable reports are required to be sent out monthly to the COR and CO and will begin at the end of the first full month after award.

7.0 PERIODS OF PERFORMANCE

The Government anticipates a one (1) year base Period of Performance (POP) with four (4) exercisable option years for this contract for a total of 5 years as follows:

All options may be exercised by the Government unilaterally, and are contingent on the availability of fiscal funding, continuation of need, and satisfactory Contractor performance.

8.0 PLACE OF PERFORMANCE

The primary place of performance is the Pocatello, Idaho site.

Federal Bureau of Investigation 3975 Pole Line Road Pocatello, ID 83201

The contractor shall be allowed to access government facilities during normal FBI business hours, generally 6:00 am to 6:00 pm MST, and is expected to perform all work on-site at the assigned building and/or an FBI approved off-site. Flexible hours shall be permitted so long as the core business hours are 9:00am to 3:00pm are covered and support is provided for a total of eight hours per day, not including breaks. The contractor shall not be expected to cover federal holidays or weekends.

The Contractor is responsible for providing communications to support after hours call back services. Call back services provided contribute to the hours of a normal work week of services and are part of their firm fixed price. On-site support service work week shall correspond to the equivalent Government work week in the area of federal holidays as well as facility unique events (e.g. weather closings).

The on-site support service individuals under this requirement shall be required to work a minimum of 40 hours per week 2080 hours yearly. Any work hours outside of established work schedules must be coordinated with the COR or designated representative and must be approved prior to work.

The on-site engineering service individuals provided under this requirement shall be authorized to perform work within any network enclave of the data center.

Shipping:

The point of delivery for this effort is:

Federal Bureau of Investigation 3975 Pole Line Road Pocatello, ID 83201

Except as noted, the Contractor shall bear all shipping costs. The CO or COR may designate other shipping or delivery locations when needed.

9.0 INVOICING

Invoices are to be sent to Central_Invoices@fbi.gov.

Invoices shall be based on FAR 32.905. Invoices are only to be submitted for delivered and accepted services, hardware, and software. Invoices are to be submitted electronically to the following email address:

A proper invoice shall include the following:

· Name of Contractor

· Invoice date and Invoice Number

· POP of contract

· Contract number, Task Order number, Contract line item number

· Electronic Funds Transfer (EFT) Banking Information

· Taxpayer Identification Number (TIN)

· Detailed of hours for all personnel

· Invoice contact (name, phone number, email address

· Appropriate documents with travel invoice

10.0 TRAVEL

The Contractor shall not charge local travel cost in the Pocatello, Idaho (within 50 miles of primary work location) to the Government. The Contractor shall be available for travel Sunday through Saturday, including Federal holidays, to locations within the United States as well as internationally. All travel, when required, will be billed in accordance with Federal Travel Regulations (FTR). The Contractor shall submit travel forms to the government task lead for coordination with the COR for approval as least two (2) weeks in advance of travel, when feasible. The following is required for reimbursement to take place:

a) Approval from COR

b) Hotel Receipt

c) Parking Receipts

d) Rental Car receipts (showing type of car: economy, etc)

e) Airline ticket (boarding pass)

f) Luggage receipt (only 1 allowed)

g) Transpiration receipts (UBER, TAXI, etc)

h) Spreadsheet detailing individual travel

i) GSA Per Diem for travel location

11.0 DELAYS

FAR 52.212-4(f) dictates the Governments course of actions if the Contractor fails to meet deadlines established under Contract or during the execution of the Contract.

Consideration for delays shall be approved bilaterally by the Government and Contractor. The approved consideration shall be documented and may include, but not be limited to price or schedule considerations or termination. All orders placed against this Contract shall be booked with the manufacturer within 3 business days of receiving the order (Purchase Order) from the Government.

This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text of a clause may be accessed electronically at this/these address(es): www.acquisition.gov.

Normal Delay Any circumstances which may hinder any completion date or required delivery shall be immediately reported in writing to the Contracting Officer’s Representative (COR) and the Contracting Officer (CO) for consideration. In the event the Contractor encounters difficulty in meeting performance requirements, or when he/she anticipates difficulty in complying with the contract delivery schedule or completion date, or whenever the Contractor has knowledge that any actual or potential situation is delaying or threatens to delay the timely performance of this contract, the Contractor shall immediately notify the Contracting Officer and the COR. This notification shall be in writing, giving pertinent details. However, this data shall be informational only in character and this provision shall not be construed as a waiver by the FBI of any delivery schedule or date, or any rights or remedies provided by law or under this contract.

Critical Delay For this tasked effort, a critical delay is defined to include any actual or anticipated occurrence meeting one or more of the following criteria:

A) The delivery or installation of the task products to the FBI data centers will not be within 30 calendar days of the proposed scheduled due date.

B) The delivery of services to the FBI data centers will not be within 30 calendar days of the proposed scheduled due date.

C) Required services will not be available at the beginning of the period of performance.

Within five calendar days of discovery, for each occurrence of any actual or anticipated critical delay, the Contractor shall deliver to the COR and CO a corrective action plan containing the following information:

A) Critical delay description and date of discovery.

B) For anticipated critical delays, description of corrective/mitigation actions taken or to be taken to meet contract requirements. If the critical delay cannot be completely mitigated, include a description of expected contractual impact/extent of the partially mitigated critical delay.

C) For actual critical delays, description of correction/mitigation action taken or to be taken. Include a description of expected contractual impact/extent of the critical delay.

D) For all critical delays, description of corrective actions taken or to be taken to preclude future critical delays. Include descriptions of metrics put in place to preclude recurrence or allow discovery of potential delays earlier, allowing effective delay mitigation.

Non-U.S. Citizens shall not be authorized to access or assist in the development, operation, management or maintenance of Department of Justice Information technology (IT) systems. By signing the contract or commitment document, the Contractor agrees to this restriction. This requirement shall flow down to all subcontractors and to all vendors, where applicable.

12.2 Residency

All Contractor Personnel performing services under this contract within the United States shall meet the Department of Justice Residency Requirement. The Residency Requirement states, in part, that for three of the five years immediately prior to work on the contract, the individual shall have resided in the United States; worked for the United States overseas in a federal or military capacity; or be a dependent of a federal or military employee serving overseas.

12.3 Dedicated Equipment

All Contractor and Government Furnished Equipment, hardware, software, local-area networks, wide-area networks, or other processing facilities that contain FBI information or data that are provided by the FBI or that are generated by tasked efforts shall be solely dedicated to FBI tasked efforts, except as specifically approved by the FBI in writing.

12.4 Accountable Property

The Contractor shall include the FBI Purchase Order Number on all shipping documents (i.e., packing list). Shipments of equipment to the FBI without the FBI Purchase Order Number are subject to refusal. For this paragraph, accountable property is defined to be all Government property valued at $2,500.00 or more or individual components of IT systems such as external hard drives, monitors, switches, scanners, printers, and modems regardless of value.

12.5 Registration and Tax requirements for Contractors and Subcontractors For any work performed on-site within the Pocatello, Idaho city limits, the Contractor shall be responsible for obtaining a City of Pocatello, Idaho, business license in order to meet Business and Occupation Tax obligations.

12.6 Personnel

General Personnel Requirements Upon the award of the contract, appropriate Contractor individuals will be processed as directed by FBI policies and procedures. The FBI requires that access approval and/or security clearance be granted by the FBI Security Programs Manager (SPM) to all Contractor personnel who will have access to: Sensitive but Unclassified (SBU) information; FBI information; FBI facilities; and/or FBI equipment.