DRAFT SOO EVSE Monitoring Maintenance.docx

RFI #

U. S. Customs and Border Protection

Request for Information

Draft Statement of Objectives (SOO) for EVSE Monitoring and Maintenance

October 21, 2024

Introduction and Instructions

This Draft Statement of Objectives (SOO) describes U.S. Customs and Border Protection’s (CBP) requirements for the Data Management and Access, Integration Capabilities, and Comprehensive Monitoring Solutions supporting Electric Vehicle Supply Equipment (EVSE) Monitoring and Maintenance. This SOO is intended to maximize Offeror flexibility in proposing solutions to meet CBP’s requirements.

1.0 PURPOSE

This SOO describes the goals that the Department of Homeland Security, CBP, Enterprise Services (ES), Acquisition Portfolio Management Directorate (APMD) requires to be achieved regarding the acquisition of a comprehensive solution for collecting, monitoring, managing, and maintaining the implementation of (exact quantity pending) EVSE devices in the migration of its fleet management systems to support zero-emissions vehicles.

The primary goal of this acquisition is to provide CBP with a range of technical, financial, and data management support solutions to achieve mature management of CBP’s EVSE infrastructure. Currently, there is no single integrator or cohesive method in place to collect and manage data across the EVSE equipment that is being implemented at CBP locations as part of the EVSE pilot program. This issue will become exponentially more difficult after the pilot if a system for management is not put into place before there are hundreds or even thousands of EVSE devices. Adding to the complication, is that there are different vendors providing the EVSE equipment that have differing connectivity and maintenance protocols and require varying and potentially proprietary portals to access usage and maintenance data.

CBP will need to be able to connect, monitor, manage, and maintain a wide variety of EVSE devices located in numerous CBP locations across the United States and its territories. This includes requirements for a system with a CBP-controlled dashboard that provides real-time monitoring and data collection of EVSE usage and status of all eligible devices.

This SOO encompasses objectives for EVSE Device and Data Management, Reporting and System Integration for the overall EV/EVSE effort. CBP has entered a pivotal time in technology transformation where our front-line officers and agents rely on emerging technology more than ever before to safeguard our nation’s borders and enforce legitimate trade and travel. Building a method for management of the information transfer, cost monitoring and device management for CBP’s EVSE infrastructure is a critical piece of movement toward sustainable and reliable energy resources for CBP. Therefore, it is vital to prioritize and pursue solutions which enable the building of consistent, standard, reliable and remote accessible solutions for the management of all eligible EVSE devices that fall under CBP purview. It is critical that all solutions maintain adequate cybersecurity posture and conform to all federal policies regarding data protection, transfer, and storage, to include FedRAMP certification and any other mandated cyber security certifications for the handling of federal sensitive data.

2.0 BACKGROUND

The mission of CBP is to “Protect the American people, safeguard our borders, and enhance the nation’s economic prosperity.” CBP enables this mission by ensuring the availability and high performance of mission critical systems, research and development of applications, automation, and leading technological/scientific strategies. The shift in vehicle manufacturing toward electrification has created a unique challenge for CBP to be able to maintain mission critical functionality using this new technology. It is also critical to be able to manage cost and sensitive data stored on vehicle On-Board Diagnostic systems (such as location, user, battery life, etc.) from EVSE devices to facilitate an efficient and effective vehicle fleet.

CBP’s shift to zero emission vehicles is part of a series of federal mandates such as, the “Executive Order on Catalyzing Clean Energy Industries and Jobs Through Federal Sustainability” signed by President Biden on December 8, 2021, which established the following primary goals:

· 100% carbon pollution-free electricity (CFE) by 2030, at least half of which will be locally supplied clean energy to meet 24/7 demand.

· 100% zero-emission vehicle (ZEV) acquisitions by 2035, including 100 % zero-emission light-duty vehicle acquisitions by 2027.

· Net-zero emissions from federal procurement no later than 2050, including a Buy Clean policy to promote use of construction materials with lower embodied emissions.

· A net-zero emissions building portfolio by 2045, including a 50% emissions reduction by 2032.

· Net-zero emissions from overall federal operations by 2050, including a 65% emissions reduction by 2030.

CBP fully recognizes the mission value associated with a modernized and efficient use of multi-faceted technology solutions in addition to complying with federal mandates. Additional drivers apply as CBP migrates its fleet management systems to support zero emission vehicles for the purpose of:

1. Improved Mission Continuity. Fuel costs continue to rise and the availability of fuel in the future remains in question due to depleting carbon-based resources. Electric Vehicles have performed at or above the capabilities of internal combustion engine vehicles in the most recent tests performed by CBP. The renewable aspect of electric power positions electric vehicles to become the primary vehicle type.

2. Cost. Electric Vehicles can reduce fuel cost dramatically due to the high efficiency of the electric-drive components. Today’s Electric Vehicles can exceed 130 MPG in comparison to fuel and use only 25-40 kWh of power to drive 100 miles. Cost of charging and charging stations, considered.

3. Emissions. Electric and Hybrid Vehicles have a significant reduction in tail pipe emissions, which in most cases are nearly zero. This is in line with federal policies to reduce harmful emissions and create a greener federal impact.

4. Safety. Most electric vehicles, particularly those rated for law enforcement, have high safety ratings for front and side impacts as well as rollover incidents. They have 5-star ratings from the National Highway Traffic Safety Administration.

5. Speed. Electric Vehicles are also capable of accelerating to high speeds faster than most fuel driven vehicles. The higher torque generation by an electric motor versus a gas-powered engine allows the vehicle to accelerate faster for pursuits and other law enforcement actions. Electric Vehicles also have a better distribution of weight and low center of gravity making them more manageable at high speeds.

Evolving the CBP fleet and vehicle management portfolio to integrate modern technologies is critical to keeping up with aggressively evolving mission requirements. CBP has faced an unprecedented number of national and international events that require updates to trade and travel systems, significant increased activity at the Southern border, and working across the federal/local governments for inbound refugees. CBP cannot afford to take the time to design, configure and integrate system infrastructure that is needed to accommodate the aggressive pace of growth. Instead, CBP must apply a single integrator strategy that leverages pre-existing EVSE management capabilities or builds on top of an existing service with inherent integration and management capacity. This strategy yields significant value, enabling CBP to respond quickly to mission requirements.

The single integrator strategy, connecting CBP’s EVSE infrastructure across the board, is vital to ensure cohesive and harmonized designs, implementations, sustainment, operations, management, and improvements. CBP expects this EVSE management effort to bring to fruition the vision of a mature system infrastructure with highly available data, remote access dashboards and vendor agnostic EVSE integration process, governed by CBP federal leadership (herein described as the Government or CBP), and delivered through the Objectives outlined in the following sections.

3.0 SCOPE

This SOO describes EVSE Monitoring and Maintenance effort:

Services acquired by CBP shall be used to provide the Government with:

4.0 PLACE OF PERFORMANCE

The primary location of the place of performance for CBP office is in Ashburn, Virginia. Contractors may also perform work at numerous CBP locations across the United States as needed or within their own facilities for work that can be perform remotely. Remote work may be authorized based on individual requirements, as approved by the project manager in coordination with the COR.

5.0 ENVIRONMENT

CBP currently maintains 110 EVSE at 22 locations and 16 mobile assets. The future state of the infrastructure is estimated to be over 10,000 EVSE systems at over 800 locations nationwide.

5.1 CURRENT ENVIRONMENT

5.1.1 CBP’s current environment consists of 33 ChargePoint, 10 Blink, 4 Clipper Creek, 4 Ford Pro, 4 Tritium, 3 Siemens, 3 PowerCharge, 2 BTC Power, 2 Kempower, and 1 Juice Bar system. These chargers are located in California, Arizona, New Mexico, Florida, Virginia, West Virginia, and New York. They are not currently on the CBP network and are running via third party mobile connections. This may not be feasible at all locations due to the lack of cellular service at some remote CBP facilities. Additional networking capabilities may be required.

5.2 TARGET ENVIRONMENT

CBP anticipates the target environment to be matured and modernized and considered successful when the target environment below has been established:

· Complete management of all CBP’s eligible EVSE devices/environments.

· The establishment of monitoring and alerting to inform the Government of any performance or availability issues.

· Provide a method for obtaining EVSE usage and cost data

· Security Information to illustrate that the vendor is conforming to all required DHS and CBP published policies and procedures.

· Establishment of a remote capability to manage access control

· Establishment of a remote capability to manage electricity demand at the facility level

6.0 OBJECTIVES

The overall objective of this procurement is to enable the monitoring, enhancement, and data management of EVSE and related EVSE equipment in use across all CBP locations and to provide upkeep and management of the devices during the performance of this procurement. To achieve this, these integration capability services shall meet the following objectives:

6.1 BUSINESS OBJECTIVES

6.1.1 AUTHORITY: The Government is the approving authority and no decisions, strategic or tactical shall be made without the explicit approval of the designated authorities. To that end, it is critical that the appropriate representatives be provided with adequate comparable metrics which allow them to make decisions based upon metrics (security, price, performance, and availability) and facts. Therefore, the Government leaders require a consolidated data collection and distribution service that shall include, but is not limited to, consolidated usage, cost and maintenance reporting for all included EVSE and related equipment. The vendor is required to provide accurate cost details related to the product or services provided by this procurement and the ability to see costs (drill down) determined by user number or license or any other subcategories as determined and directed the Government.

6.1.2 TECHNOLOGICAL COMPETITIVENESS: The Contractor shall keep pace with the publicly available federal or commercial offerings, including comparative advantages/disadvantages with CBP’s current-state architecture.

6.1.3 OPERATIONAL EXCELLENCE: The Contractor shall deliver and measure “operational excellence” (performance, scalability, and availability) in EVSE and EVSE related equipment management, reporting and monitoring.

6.1.4 INNOVATION: The Contractor shall focus on a Continuous awareness of evolving and trending changes in industry to ensure CBP is aware of potential opportunities such as cost savings, improved performance, meeting newly identified mission needs.

6.1.5 INTEGRATION: The Contractor shall integrate, leverage, and reuse application and system deployment and automation tools, and, to the greatest extent practicable, leverage the latest hardware, virtualization, and software solutions.

6.1.6 SERVICE DESK SELF-SERVICE: The Contractor shall create solutions to allow users to access assistance with technical issues as they arise. These capabilities may include, but are not limited to, knowledge portal, training, self-service password reset, cloud and or software resources, and user guides. Develop, propose, and obtain approval for metrics that track support requests and show how support is being obtained via self-service means.

6.2 TECHNICAL OBJECTIVES

6.2.1 TECHNICAL ACUITY: The Contractor shall demonstrate the ability to maintain Technical Acuity while managing various federal or commercial environments, demonstrate expertise with new capabilities and offerings, assist the Government in obtaining information for analysis and then secure, implement, and manage those capabilities.

6.2.2 INTEROPERABILITY / PORTABILITY: The Contractor shall facilitate application and data interoperability and portability effectively and efficiently.

6.2.3 AUTOMATION: The Contractor shall provide, implement, operate, manage, support and report on automation.

6.2.4 IDENTITY AND ACCESS MANAGEMENT (IAM): The Contractor shall integrate or federate into the available CBP IAM tools being utilized if possible, and then manage, operate, support and report on the different user roles, responsibilities, and access levels within a portal.

6.2.5 DATA PROTECTION AND BACKUP: The Contractor shall recommend data protection policies for the specific product being utilized by Government and CBP System owners, and then implement, operate, manage, support and report on the solutions within the scope of this procurement.

6.2.6 MONITORING AND ALERTING. The Contractor shall demonstrate the capability of implementing appropriate monitoring and alerting processes to interface with a variety of EVSE and related device providers and to propagate those alerts to the proper federal management platforms to inform the Government of performance and/or availability issues in real time.

6.2.7 DISASTER RECOVERY (DR): The Contractor shall provide a recommendation of a disaster recovery strategy for each in-scope product being utilized, which could include recommendation of an on-prem or other method.

6.2.8 STORAGE: The Contractor shall develop storage and data hygiene policies, governance, and procedures, as well as data sanitation and destruction processes that comply with applicable government regulations and retention policies.

6.2.9 NETWORK: The Contractor shall implement, operate, manage, support, and report on at a minimum, the creation of secure virtual system infrastructure, allow for connectivity between on-premises resources and devices and cloud, and provide a mechanism to control the way resources are accessed.

6.3 SECURITY OBJECTIVES

6.3.1 GENERAL SECURITY. The Contractor shall provision service offerings that ensure protection of CBP data located in any Cloud or vendor network and any physical infrastructure and information security, and limit and/or mitigate against threats, internally and externally. The Government reserves the right to acquire cloud services which are not FedRAMP authorized if necessary. Dedicated cybersecurity services, such as those typically performed by Security Operations Centers are provided separate from this procurement. However, to understand and support security-related requirements, the Contractor shall enable access to cybersecurity talent to facilitate and meet requirements within this order.

6.4 MANAGEMENT OBJECTIVES The Contractor shall develop, obtain Government approval for, and track performance metrics, while implementing policy, governance and permitting domain specific orchestration. The Contractor’s proposed solution shall be able to meet the requirements of this SOO.

6.4.1 BILLING AND CONSUMPTION DATA: The Contractor shall demonstrate an ability to ingest vendor provided billing and consumption data, including but not limited to power usage and cost, in as close to real-time as possible, and present this data to the Government which includes any CBP discounts for accurate financial tracking and governance by CBP.

6.4.2 COMMUNICATIONS BRIDGE ACROSS EVSE AND RELATED EVSE EQUIPMENT PROVIDERS: Contractor shall utilize resources to provide a bridge for collecting data from various vendors providing EVSE and related EVSE equipment to the Government. It is essential that the Contractor have a viable plan for effective and efficient communication to the Government. Metrics including Performance/Maintenance Status, Availability, Usage, and Cost information (with applicable discounts) from multiple sources shall be obtained and the data presented to Government officials in a concise and cohesive manner that allows the Government to make tactical and strategic decisions such as what services to engage based upon this data.

6.4.3 VISIBILITY/USAGE: The Contractor shall provide a single management interface that integrates all activities previously described herein which provides the Government oversight into all aspects of EVSE and related equipment models, to include management of all the network, cloud, and hybrid cloud activities, maintenance needs and actions, cost information, Service Level Agreement compliance, and self-service metrics in the environment that is being managed.

6.5 ADMINISTRATIVE OBJECTIVES

6.5.1 SERVICE LEVEL AGREEMENTS (SLA):

The Contractor shall implement, track, and report on industry leading SLAs for software service availability, scalability and data reliability and shall manage the provisioned resources to ensure those SLAs are met or exceeded.

6.5.2 TRANSITION: The Contractor shall provide a plan for a logical and seamless In-Coming and Out-Going Transition(s) of operations to minimize, as much as practicable, any adverse effect created by the transition process. Work with existing Government and Contractor personnel to execute their mission. Provide the capability, detailed documentation, detailed instructions, costs, and associated risks to transition from the Contractor provided product or service required by mission needs and/or when the contract (task order) ends. Ensure that the product and/services and all tools utilized are procured and licensed in a manner to support transition when the contract ends. All proprietary tools and licenses that do not support future transitions are to be avoided or specifically approved for use by the Government in writing.

6.5.3 ON-DEMAND SURGE SUPPORT: The Contractor shall provide in-scope Surge Support upon notification by the Government if needed. This work is in support of additional in-scope requirements in response to specific requirements or an increase in usage resulting in the need for more resources. Each surge support request will be managed as a project with an associated cost. The deliverables will be mutually agreed upon between the parties at the outset of the action.

6.5.4 CONSTRAINTS

Not applicable.

7.0 PERFORMANCE METRICS

The metrics defined below identify the performance requirements for EVSE Monitoring and Maintenance. The Contractor may make recommended changes to these metrics for Government approval. The Government will review these metrics at least annually, and this may change as technological advances occur.

The balance of this page is intentionally left blank Table 7.1

updates to eligible devices as required to uphold the security and functionality of eligible devices.

and updates must be completed within required time frame.

The remaining 5% must be completed within the following “X” days of the time frame Security audit by OIT, reporting by vendor

logging Less than 1 second after activity execution

analysis

service offerings and updates and modifications to existing service offerings available

Within 30 days

nature of related service incident impacting users Under 10 minutes

incident reports and notifications

8.0 DELIVERABLES

Item Title

preferred format The 5th day of each month after contract award

Plan

preferred format Within 30 days of contract award, then annually thereafter

Unless otherwise specified, the Government will have 15 calendar days to review and provide comments to all deliverables. Any deliverables that are not commented upon within that time frame are deemed approved. The Contractor shall have 15 calendar days to revise and resubmit any deliverables in response to Government comments.

Additional reporting requirements may be required.

9.0 PERIOD OF PERFORMANCE

The Ordering Period will be twelve (12) months from date of award with four (4) 12-month option periods.

10.0 APPLICABLE DOCUMENTS

The Contractor shall ensure all Contractor personnel follow and adhere to all applicable policies and procedures established by the DHS, CBP, as well as all the documents referenced below and any future amendments or superseding versions thereto.

The Contractor shall refer to the National Institute of Standards and Technology (NIST) Computer Security Resource Center (available at http://csrc.nist.gov/ ) for the latest editions of NIST computer security publications, including, but not limited to the following:

· NIST Special Publication (SP) 800-37, Rev. 1, “Guide for Applying the Risk Management Framework to Federal Information Systems”

· NIST SP 800-53, Rev. 4, “Security and Privacy Controls for Federal Information Systems”

· NIST SP 800-53A, Rev. 4, “Assessing Security and Privacy Controls in Federal Information Systems and Organizations: Building Effective Assessment Plans”

· NIST SP 800-144 “Guidelines on Security and Privacy in Public Cloud Computing”

· System Reporting Form Standards for Security Categorization of Federal Information and Processing Standards (FIPS 199)

The Contractor shall refer to and comply with the DHS IT Security Policy documents available at https://www.dhs.gov/dhs-security-and-training-requirements- (the most recent version will be applicable) which include, but are not limited to the following:

· DHS Directive (MD 11042.1) “Safeguarding Sensitive but Unclassified (FOUO) Information" dated January 6, 2005 or current version. https://www.bing.com/search?q=md+11042.1&src=IE-SearchBox&FORM=IESR4A

· DHS Information Security Policy, identified in MD 4300.1, https://itlaw.wikia.org/wiki/DHS_Management_Directive_4300.1

· Information Technology Systems Security Program and 4300A, 4300B, 4300C Sensitive Systems Handbook. https://www.dhs.gov/publication/dhs-4300a-sensitive-systems-handbook

· DHS Systems Life Cycle (SLC) Instruction 102-01-103 https://www.dhs.gov/sites/default/files/publications/Systems%20Engineering%20Life%20Cycle.pdf

The Contractor shall also refer to and comply with the following CBP policy documents (the most recent version will be applicable) which include but not limited to the following:

· CBP Information Systems Security Policies and Procedures Handbook, HB 1400-05D, or current version https://pods.cbp.dhs.gov/s/ (CBP internal)

· CBP OIT CSD STP ISSO Standard Operating Procedure (SOP)

· CBP Handbook for Safeguarding Sensitive PII, Policy Directive 047-01-007 https://www.dhs.gov/publication/handbook-safeguarding-sensitive-personally-identifiable-information (CBP internal)

· CBP OIT Change Management Handbook

· Information Technology Infrastructure Library (ITIL) Standards

3 | U.S. Customs and Border Protection EVSE Monitoring and Maintenance image1.png