Attachement_B_Technical_Reqs_1-19-58-69.pdf

Contract# 1-19-58-69 Technical Requirements Attachment B 1/24/2020

General Requirements

A. Contractor shall participate in the California Bureau of Automotive Repairs

Continuous Testing Program (BAR CTP) development. Contractor must maintain participation for the duration of the contract including approved extension period(s) and transmit necessary data for program compliance.

B. All equipment delivered will be tested to ensure it is operable and free from any defects or damage and is fully operational prior to shipment.

C. The Contractor will furnish upgraded equipment with improved technology, including OEM technology, at the request of the ordering agency. However, any hardware change must be pre-approved by the ordering agency. If it is determined that upgraded equipment is to replace existing equipment, the ordering agency and the Contractor will develop an agreed upon implementation plan that will include a systematic process to ensure a smooth transition occurs. The transition plan timeline will be based upon the Agencies’ staffing levels, operational needs, and training requirements.

D. All required data points for the Enterprise-Level Web Based Data Application

(Application) and reporting, will be tied to the VIN or other Agency specific unique identifier (such as asset ID) and not the GPS device serial number. This will ensure no data loss if the device needs to be replaced in an asset.

E. If an asset is sold or otherwise removed from the Agency fleet, a device deactivation process will be established. Data related to the inactive fleet asset will not be lost or archived, but available in the Application with all reporting functionality. Device re-use, where applicable, is required unless the device is defective or malfunctioning.

F. The GPS device and On-Board Diagnostic II (OBD II) link connector device will be the latest and most technically advanced model available from the Contractor.

Contractor shall provide a product generation history upon request any time during the contract period.

G. Contractor shall agree to establish reoccurring meetings with the ordering agency to discuss any issues with the Application, and deliverables and remedies.

H. The Application, Contractor Owned Storage Data Bases (data warehouse), and

Program Interface (PI) will be Software as a Service (SaaS). All terms and conditions shall be compliant with State Model Cloud Computing Service Special

Provisions (Software as a Service).

I. The solution shall enable role based access control that demonstrates compliance of least privilege and address segregation of duties compliance.

Asset Categories Defined

Products shall be installed systems into the following asset categories, and be compatible with the web based data application.

Light Duty Vehicles (Category 1)

Light duty (LD) vehicles are defined as being powered by an internal combustion engine equipped with OBD II protocol diagnostics and diagnostic connector. If asset does not have OBD II capabilities, alternative harness configurations must be made. All available data from the asset will be collected via the OBD II or alternative, diagnostic connector and transmitted wirelessly to the Application. OBD II emissions data necessary to comply with the BAR CTP shall be transferred directly to BAR daily, or as required by program policy, guidelines, statute or regulation. LD assets include, but are not limited to:

• Sedans

• Pickups

• Motorcycles

Heavy Duty Vehicles (Category 2)

Heavy duty (HD) vehicles are defined as being powered by an internal combustion engine equipped with Communication Protocol (CAN-bus) diagnostics J1708 & J1939

CAN-bus and diagnostic connector. Construction, off road, and auxiliary engine equipped assets are included in this category. All available data from the asset will be collected via the CAN-bus connector, if equipped, and transmitted wirelessly to the

Application. HD assets include, but are not limited to:

• Snow Plow Trucks

• Snow Blowers

• Paint Striper Trucks

• Personal Hoist Trucks

• Street Sweepers

• Mower Tractors

• Attenuator Trucks

Zero or Low Emission Vehicles (Category 3)

Zero or Low Emission Vehicle (ZEV) assets may include light duty or heavy duty vehicles. Zero or Low Emission Vehicle assets may include hydrogen fuel cell vehicles, pure battery electric vehicles, plug-in hybrid electric vehicles and compressed natural gas (CNG) vehicles. All available data from the asset will be collected via the diagnostic connector and transmitted wirelessly to the Application. OBD II emissions data necessary to comply with the BAR CTP shall be transferred directly to BAR daily, or as required by program policy, guidelines, statute or regulation. Current fleet consists of, and devices shall be compatible with, but not limited to the list below. BAR CTP is applicable to any vehicle with an Internal Combustible Engine. The fleet will grow as technology grows and new vehicle offerings become available.

• Chevrolet Volt

• Chevrolet Bolt

• Chevrolet Spark

• Ford C-Max

• Ford Focus

• Hyundai Tucson

• Hyundai Sonata

• Kia Soul

• Nissan Leaf

• Toyota Mirai

• Toyota Prius Plug-In

• Toyota Rav4 EV

• Sterling L8513

Non-Self Propelled Assets (Category 4)

Non-Self Propelled Assets (NSP) are not equipped with a means of propulsion or self-powered electrical system. Data will be collected via self-powered GPS device or if the asset has a standalone electrical system, the contractor shall provide for an alternative electrical power interface. Ordering agency will determine installation type. All data will be transmitted wirelessly to the Application. Non- self-propelled Fleet assets include, but are not limited to:

• Trailers

• Mobile Signs

In-Asset Data Services Requirements

The data and hardware service will include hardware and data transfer services, data collection, data storage, reporting, diagnostic trouble code (DTC) and alerts. Application shall be capable of supporting an ordering agency’s fleet size potentially as large as fifteen-thousand (15,000) assets and twenty-five thousand (25,000) asset operators, depending on ordering agency’s fleet count. Data plans shall be unlimited for both

Cellular and Satellite requirements.

The data and hardware service will also include overlay mapping and wireless data transmission services for assets in all regions of California and neighboring states.

Contractor shall provide a solution for areas without the ability to transmit data, in all areas of California and neighboring states.

Transmission of data from the in-asset hardware will be wireless and bidirectional to and from the Contractors and/or ordering agency’s data warehouse. Troubleshooting, such as firmware updates and device health checks, will be pushed to the in-asset hardware via the network. All wireless transmission and communications shall take place over secure and encrypted channels.

Contract service rates are only applicable to properly approved and installed devices actively sending complete data. The ordering agency reserves the right, and will be assigned rights, to activate or de-activate any device(s), at any time, via the Application and/or through Contractor’s customer service representative.

The data collection, storage, reporting, and alert service will be provided statewide, twenty-four (24) hours a day, seven (7) days a week, including all holidays. The State does not expect 100% uptime on the web application, but the level of service provided with this contract will include a twenty-four (24) hour notice for scheduled maintenance.

Maintenance should be scheduled outside normal business hours. Unanticipated downtime must be addressed within one (1) hour.

GPS Device and OBD II Link Software

The following data points at a minimum, will be collected by the Contractors device:

• Asset Usage information o Location information by latitude and longitude and nearest address where available o Date and time of travel o Trip route o Mileage of trips o Dash odometer values at beginning and end of each trip o ECM engine operating hours o Storage location o Asset operator ID o Days of use

• Diagnostic Information o Malfunction Indication Light (MIL) o Diagnostic Trouble Codes o Fluid levels o Tire pressure monitoring o Emissions monitor status

• Asset operator behavior o Excessive idling o Speeding o Harsh braking o Harsh acceleration

• Other o Fuel Usage o Green House Gas Emissions o Low fuel o Low charge

All aftermarket GPS devices must record location via trips through event-based data transmissions or pings, in latitude and longitude and nearest address where available.

In-Asset Data Requirements

Data Alert notices

For all connected device types, alerts shall include, but are not limited to, the following:

• Asset use via Geofencing

• Accident notification

• Rapid acceleration/deceleration

• Maintenance reminders such as oil change due, inspections due, etc.

• Excessive idle and speeding events

• Low primary power supply and battery level trend reporting

• Loss of primary power supply

• Odd hour activity as defined by ordering agency

Alerts may be sent via e-mail, short message services (SMS) or multimedia message services (MMS) and will be user definable via the Application based on user hierarchy.

Data transfers and updates will be configurable as required by the ordering agency.

Available alert type will evolve with industry availability.

ZEV Specific Data Required

a. Fuel consumption

b. Electricity usage by asset (kWh)

c. Hydrogen usage in kilograms by asset.

d. Fuel consumption for plug-in gas hybrid asset

e. Percentage of miles driven on electricity for plugin hybrid asset

f. Number of charging sessions per day, week, etc. per asset

g. Average mileage for hybrid electric Hydrogen – if available

h. For each charging session include the following:

i. Starting and Ending State of Charge (SOC)

ii. Total length of charging event

iii. Event start and stop time

iv. Amount paid per event transaction, if available

v. Electricity consumed (Kwh)

vi. Type of charger (level one, level two, and DC fast charger) if available.

vii. Location of event

i. Average starting and ending charging event SOC for each asset – if available

j. Average length of charging session (for each asset and/or the entire fleet) within any report time span– if available

k. Kilowatt hour consumption while charging (per charging session)

Device Storage

Devices will store data without loss, for a minimum of forty-five (45) days at maximum data gathering rate. When assets are operating in an area of no service, they will store data and transmit stored data when coverage is available. When device storage has reached capacity the device will overwrite stored data beginning with the oldest data and progressing forward. Devices that reach capacity shall not “lock up” requiring a hard restart effectively erasing any stored data.

In-Asset Hardware Requirements

A. All aftermarket GPS devices installed at any time by the Contractor will be of the most current available technology capable of communicating with OBD II or CAN-bus protocols to effectively process GPS, diagnostic, and sensor (AVL) data.

Devices will transmit all data via wireless data transmission service(s) to the

Contractor’s and/or ordering agency’s data warehouse server(s). Data transmission and communication shall take place over secure and encrypted channels.

B. All aftermarket GPS devices will be installed utilizing industry standard “Y” cabling sized appropriately for electrical load and shielded to prevent interference during operation and data transfer. “Y” cables shall connect directly to OEM installed OBD

II or CAN-bus diagnostic port connectors. In the absence of an OEM installed diagnostic connector, a 3 wire connection is acceptable to supply platform voltage, ground, and ignition (key on) signal. All installed devices connected to the OBD II diagnostic port or CAN-bus diagnostic port will “step aside” electronically when diagnostic equipment is attached allowing diagnostic data to pass freely via the OBD

II or CAN-bus, as applicable, while performing diagnostic work. This “step aside” function will be accomplished automatically and will not require physically unplugging the telemetry device.

C. Each selected asset will be equipped with the most current Radio-Frequency

Identification (RFID) or equivalent proximity (non contact) technology to identify asset operators and will have an audible asset operator alarm alerting the asset operator to register their ID if not accomplished within thirty (30) seconds of key on event. Device must be in the form of a proximity or quick identifier. Device firmware will be configured to request the asset operator ID within ten (10) seconds of key on event. The asset operator ID interface device will be mounted in an accessible location for easy use and will not impair the asset operator’s vision, cause a safety hazard to any occupant, or interfere with any OEM systems. Asset operator identity including the specific personnel ID number will be viewable only in the Application or through reports for defined user hierarchical roles. All aftermarket hardware will be of robust construction capable of withstanding off-road operating conditions (including but are not limited to, unusual shaking, vibration, extreme temperatures (-25 F to

150 F), dust, and noise).

D. All aftermarket GPS devices installed at any time by the Contractor will be the most current available technology capable and will communicate with OBD II or CAN-bus control systems as appropriate, process telemetry and diagnostic data, including but not limited to, live asset instrument display (dash) odometer and/or dash hour-meter reading and emission control system information. In order to provide proper GPS device functionality, reporting capabilities, data integrity, and effective GPS device communication with onboard asset systems and data transmission network(s), device firmware will be updated regularly to match evolving asset control protocol and communication technology advancements and configured to eliminate interference with asset systems communication. If, during the contract period, technology evolves and devices update generationally, the contractor will make devices, installation services or OEM technology available for ordering agency to procure.

E. No component will cause harmful interference with, nor be adversely affected by mobile shortwave radio receivers or transmitters. The Contractor will supply and install any shielding or noise suppression equipment required to prevent transmission or receipt of harmful interference. As required by Part 15 of the

Federal Communications Commission (FCC) Rules, a label will be placed in a conspicuous location on the main control unit that states the following: “This device complies with part 15 of the FCC rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation." This section applies to devices, connection harnesses, and any peripheral/associated equipment installed.

F. Health Check

Devices that have not reported via a key-on event within twenty-three (23) hours will “wake up” automatically and report location, condition, and battery voltage

(internal and supplied).

The Application may query all devices daily to determine “Health” as an alternate method.

Supplied battery voltage trend analysis will be conducted each week on all installed and activated devices to preempt non-reporting devices. Contractor will notify ordering agency authorized personnel of assets identified in the analysis as suspect by supplying asset ID, device serial number, last reported location of asset trend analysis, and current supplied battery voltage.

G. All aftermarket GPS devices for powered devices will be report, at a minimum, live asset dash odometer and/or dash hour-meter reading, Asset ID, battery voltage

(internal and supplied), position information in latitude and longitude (per ping rate or event) from key on to key off, engine RPM information, asset operator ID, date and time of travel, speed, and any additional parameters available in industry as requested by ordering agency. Devices installed on non-self-propelled assets will report, at a minimum, Asset ID, internal battery charge level in volts, position information in latitude and longitude, and date of position information change.

H. All GPS devices will obtain dash odometer and/or dash hour-meter values directly from the onboard computer data stream. If the dash odometer/hour-meter Parameter in Display (PID) is not available in the data stream, the data will be identified and supplied from the manufacturer data stream. When the dash odometer and/or Dash hour-meter PID is/are not available in any onboard data stream, any applied meter calculation algorithms will be calibrated within one hundred (100) miles for odometers and fifty (50) hours for hour-meters, or less per six (6) month time period.

Manual adjustments of meter information from the calculations mentioned above will be updated annually by the Contractor in the Application. Contractor will supply an annual certification of accuracy of odometers and hour-meters to ordering agency.

I. All GPS devices must provide usage and movement information for assets travelling at speeds slower than that of normal motorized assets (equal to or greater than one

(1) mile per hour), including non-passenger assets.

J. All GPS devices will be configured to operate, report, and communicate within a primary voltage range of 6vdc (volts direct current) – 36vdc as supplied by each individual asset platform. No voltage converter or reducers will be allowed.

K. Additional devices, components and hardware will be available for purchase by each ordering agency, to avoid downtime and ensure new assets have GPS installed with little delay. Cost for surplus devices and equipment will not exceed the initial

Contract quoted price.

L. Each GPS device must incorporate input/output ports to accommodate asset operator ID method, alert buzzer for asset operator ID, and two (2) additional port for potential expansion.

M. Compliant with Federal Motor Carrier Standards (FMCS) regulations for collecting and reporting Daily Vehicle Inspection Reports (DVIR) and Electronic Logging

Device (ELD), current at the time of bid.

Non-Self-Propelled (Category 4)

Selected assets that do not have an electrical system will be equipped with GPS devices powered by an internal rechargeable battery. Devices shall be capable of providing utilization information such as, but not limited to, hours of use, days of use, distance travelled, and location. Devices may be equipped with solar panels to facilitate charging of internal battery. If solar is not an option, contractor must provide alternative means of battery charging. For trailer applications the device will be connected to the tow asset power supply when the trailer cord is connected and will use this power supply to charge the internal battery and power the device.

Selected assets that have mounted powered equipment will be equipped with the asset operator ID option. Usage data, including but not limited to, days and hours of use, will be provided. Data points reported/required are specific to ordering agency operational needs will be determined by Contractor and ordering agency during the consulting period.

Automated Vehicle Location (AVL)

Contractor shall provide AVL options for Heavy Duty assets and other assets as needed. AVL shall provide real time data collection, control, data analysis and reporting as described below:

• Must be in compliance with state and federal asset operator reporting requirements

• Collect real-time data necessary to support cost savings for winter maintenance compatible with communication protocols such as Clear Roads “CR 14-04 Plug and Play” or equivalent.

• Automate the collection and reporting of highway maintenance activities

• Provide video feed of winter maintenance activities

• Real time tracking of assets for highway incident response and winter operations

• Achieve a ROI that at a minimum sustains the use of a telematics program

The Contractor will provide all equipment, service and labor to collect the data necessary to assess the current conditions associated with each of the objectives listed above.

AVL Program and Services shall meet the following requirements:

• Compatibility with a wide variety of light duty and heavy duty vehicles

• All cellular and GPS antennas shall be internal to the unit

• Contain serial ports for Power Take Off (PTO) inputs

• Contain battery power for unpowered assets or a rechargeable solution

• Alternate communications modem, i.e. satellite modem, for areas with limited cell service

• Provide real-time PTO tracking, service and detailed reporting and alerts, including:

o Spreader operation o Brine control o Material flow o Plow operation o Wiper operation o Forward and rear facing video feeds o Warning lamp operation o Current weather conditions, including road surface temp and pavement conditions

• Ability to provide real-time asset control, detailed reporting and alerts, including:

o ELD (www.fmcsa.dot.gov/hours-service/elds/electronic-logging-devices) o Daily Vehicle Inspection Records (DVIR) o Video capability for reporting out of service items o PTO work time

• Compliance with FMCS regulations for DVIR and ELD current at the time of bid

• Ability to interface with Asset Works Fleet Anywhere (FA) and Hansen Integrated

Maintenance Management Systems (IMMS) to collect/input the following data:

o DVIR data (FA and IMMS) o Out of service report data (FA and IMMS) o Subsystems and PTO data (FA and IMMS) o Component data (FA and IMMS) o ELD asset operator ID, duty status and hours of service (IMMS) o Material data (IMMS) o Highway Maintenance Reports (IMMS)

• AVL Software Requirements:

o Provides web based program access that requires no software installation to state computers o Provides continual program updates through the web without service interruption o Provides the administrative ability to include unlimited users, unlimited grouping hierarchy, unlimited geo-fences, and methods to group assets outside of the normal grouping hierarchy

Data Storage Services

A. The Contractor will provide a secure confidential Data Warehouse, and help desk facility with an uninterruptible power source, firewall protections, and a backup disaster recovery plan.

B. The Data Warehouse will operate twenty-four (24) hours a day, seven (7) days a week, including holidays. The Contractor must ensure that all data, data transmissions, and data storage is kept secure and confidential. The State does not expect 100% uptime on the Data Services, but the level of service provided with this contract will include a twenty-four (24)-hour notice for scheduled maintenance and must be communicated to the ordering agency at least twenty-four (24) hours prior. Maintenance should be scheduled outside normal business hours.

Unanticipated downtime must be addressed within one (1) hour.

C. The Data Warehouse will have a backup power supply to maintain continuous operations in the event of utility power failures. The service center will have duplicate computers for redundancy, with the ability to, at a minimum, permit restoration of data collection and user monitoring services within twenty-four hours after computer failure.

D. The Data Warehouse will have duplicate data storage devices with automated fail-over and automatic re-establishment of the duplicate databases upon replacement of the failed storage device.

E. The Contractor will have a written Emergency Disaster Recovery Plan at the start of the contract. The associated system and equipment will provide support in case of failures in power, telephone system, data networking equipment at its host site to the user-level equipment provided by the Contractor, due to the following but not limited to, all natural or man-made disasters including flood or fire at the data storage and reporting center. A written Emergency Disaster Recovery Plan shall be provided at time of bid submission.

F. All data produced will be the property of ordering agency and will be available for retrieval twenty-four (24) hours a day, seven (7) days a week, including holidays for a minimum of two (2) rolling years. The overwrite rate will be one (1) month and begin with the oldest data first. Data will be retained for a minimum of two (2) rolling years before overwrite (overwrite rate will be one (1) month), archiving, or deletion with the option for ordering agency to download the data prior to overwrite, archiving, or deletion. The download will be available in Excel, Comma Separated

Value, or other agreed upon form.

G. The data will be stored in and queried from a stable, relational database. All data corrections will reflect across the entire database system. All data must be encrypted at rest using Transparent Data Encryption (TDE) or like technology.

H. Data points as defined during the implementation process between the Contractor and ordering agency will integrate with Fleet Management Software/Programs in use by ordering agency via PI or equivalent means.

I. Ordering agency will regularly batch or import new data into, or update data in the

Contractor database. This will include a batch in or import geofence information or as a regular update batch on the asset hierarchy. This will reduce the time otherwise needed to manually enter or update data and reduce the potential for errors in the data. Updates can be completed by ordering agency or by the

Contractor. Proof of successful batch or update completion is required if completed by Contractor and will be provided to the ordering agency.

J. During the implementation of the project the Contractor will work with ordering agency to create a Data Mapping Specification to ensure the ability to bilaterally move data from an ordering agency system to the Contractor system.

K. All data collected by Contractor is owned by the ordering agency. Any use of, or change to, ordering agency data must be approved by the ordering agency, in writing prior to use of, or change to ordering agency data.

L. The Data Warehouse will have bidirectional secure and encrypted communication with the Contractor Application portal.

M. Ordering agency shall have the option to direct data to multiple alternative “cloud” or data warehouses instead of, or in addition to, the Contractor’s database

Enterprise-Level Web Based Data Application

A. The Application will allow state personnel to access securely the asset data stored in the Data Warehouse. The Application will provide pre-configured, customizable, viewable, printable and downloadable reports as described in, and has the capability of configuring and sending SMS, MMS or email alerts to users defined from within the Application, for each user. Data will be collected every one (1) second and transmitted directly to the Application of each ordering agency via cloud-based PI.

B. The Contractor will offer this service in such a manner that the ordering agency has no responsibility for the database, the Application software, or the technical infrastructure and associated processes and procedures. Access to the Application and the underlying database will be provided through the web will be secure, encrypted and role-based.

C. The Contractor will provide an internet secure link to ordering agency to the

Contractor’s Application and server with all data processing functions occurring solely on the Contractor’s servers.

D. The Application will not require installation of contractor provided software or applications on state-owned computers.

E. The Contractor will notify the ordering agency by phone and/or email thirty (30) calendar days prior to implementing Application system changes. Sixty (60) calendar day notice is required for database structure changes. All changes must be tested for functionality prior to release. All data will be backed-up prior to release of any changes. At least one (1) prior version of the backed up data should be available, tested and ready in the event a roll back is required.

F. The Application will provide the ability to overlay map an asset’s location throughout the day and provide viewable, printable, and downloadable reports for each data type collected or calculated. The mapping overlay will be a seamless route tracking log of the fleet asset movement during the given time parameters. These reports will be customizable by authorized ordering agency via the Application interface.

G. The Application UI map should be updated with the current vehicles location within thirty (30) seconds of vehicle movement

H. Due to possible data drift for calculated odometer and hour-meter readings, the

Application will accept odometer and hour-meter corrections for all platforms. Any odometer or hour-meter corrections entered will be actual dash odometer and dash hour-meter readings and will overwrite and eliminate the previous value causing the

Application to display and store odometer and/or hour-meter increases based on this new value and cascade backward replacing previous odometer and hour-meter values based on the corrected value for data continuity and integrity.

I. The Application will accommodate an unlimited user base with a minimum of one thousand (1,000) concurrent users per ordering agency account.

J. The Application will support user hierarchy (role-based) Application access levels based on user ID’s and passwords. All passwords must adhere with secure salted password hashing standards. Moreover, the solution must be configured to enable the agency to set a date for password changes if required. The Contractor will establish the initial ordering agency user accounts based on personnel information provided by the ordering agency during the consulting phase. The Contractor’s customer support will provide ongoing support for user hierarchy, report data entry, and report generation for the term of the contract. Parameters, included but not limited to the following, will be a one click yes/no adjustment parameter for each classification/user and shall be standalone (not group dependent):

• View Data – Current Location

• View Data/Run Reports – Historical Location

• View Data – Asset Diagnostics

• View Data – Asset Operator

• Run Reports – Asset Diagnostics

• Manage Users

• Manage Groups

• Register/Edit Assets

• Edit Odometer/ECM engine hours

• Manage Geofences

• Manage Scheduled Reports

• Manage Alerts

• Run Device Reports

• View All Users

• Manage Asset Operators

• Manage Asset Operator ID Key Assignments

• Manage Asset Operator Schedules

• View Analytics Dashboard

• View Asset Operator Behavior Dashboard

• Show Asset Operator Information

• Public Geofence Creation

K. User hierarchy templates will be available, customizable, and one (1) click or equivalent, if approved by ordering agency and assignable to speed the process of establishing user rights. Initial templates will be created by the Contractor based on the rights hierarchy provided by the ordering agency. Authorized personnel will have rights to create, edit, and assign custom rights and edit the templates mentioned above on an as needed basis.

L. Provisions to mask certain data points, such as operator and location, will be available based on user hierarchy.

M. Each ordering agency will supply a list of authorized personnel to the Contractor during project implementation process. The authorized personnel will have access to the Application twenty-four (24) hours a day, seven (7) days per week, including holidays. Personnel changes will be made as needed by each ordering agency through the administrator account by e-mail or by phone request to Contractor. The

State does not expect 100% uptime on the web application, but the level of service provided with this contract will include a twenty-four (24) hour notice for scheduled maintenance. Maintenance should be scheduled outside normal business hours.

Unanticipated downtime must be addressed within one (1) hour.

N. The Application will allow for unlimited location pings or event based data transmission for each asset (with key on or off) twenty-four (24) hours a day, seven

(7) days a week, including all holidays. The State does not expect 100% uptime on the web application, but the level of service provided with this contract will include a twenty-four (24) hour notice for scheduled maintenance. Maintenance should be scheduled outside normal business hours. Unanticipated downtime must be addressed within one (1) hour.

O. The Application will have acceptable processing performance for mapping and tracking data. Acceptable is defined as a response time of between three to four (3-

4) seconds for standard and ten (10) seconds to run complex process and content availability of 99.9 percent of the time.

P. The Contractor will provide the ability to download or export all data directly from the

Application.

Q. The Application will allow users to access the application over a Secure Socket

Layer connection with 256-bit encryption or equivalent utilizing Microsoft Internet

Explorer 11 or higher, Mozilla Firefox, or Google Chrome web browsers.

R. The overlay maps will work on all computers with Windows 7 or later, with at least

2GB of RAM, and Microsoft Internet Explorer 11 or higher, Mozilla Firefox, or Google

Chrome web browsers.

S. The Application will have the ability to geofence, both private and public. Any user created public geofences will be viewable to authorized personnel. Private geofences will be viewable to only that user account. When a user account is disabled, any geofences can be assigned to another account, or deleted by authorized personnel.

T. The Application will have a scalable search functionality. The ordering agency will have access to search based on ordering agency defined hierarchies, asset identifiers (year, make, model, Vehicle Identification Number (VIN) or Asset ID). A wildcard search feature is required.

U. The Application database will be compatibly structured to allow seamless data transfer to the ordering agency’s servers at any time if deemed necessary by the ordering agency.

V. The Application will have real-time, secure bidirectional information transfer with the

User Portal and Contractor Data Warehouse.

W. The Application will allow users to access the application utilizing Microsoft Internet

Explorer 11 or higher, Mozilla Firefox, or Google Chrome web browsers.

X. The Application data transmission shall use Transport Layer Security (TLS) 1.2 and above.

Y. The Contractor shall patch operating software for vulnerability at a minimum every thirty (30) calendar days. Additionally, the vendor shall implement a process that recognizes zero day, critical and high vulnerabilities and must work with the agency to deploy the remediation/patching required with an expeditious manner to avoid possible risks to the agency’s information and information assets.

Z. All hardware shall have a bar code or QR label affixed. Prior to each installation all hardware data shall be scanned and logged. At a minimum, the following data shall be captured:

• Asset Identification number

• VIN

• Year/Make/Model

• Telemetry Harness Type and part number

• Telemetry/GPS device model and serial number

Web Application Reporting

The Application will provide or generate the reports described within this section, if the required data is available from each selected asset. Reports will provide real time information, as needed. Reports will be available in the Application for a minimum of two (2) years. The reports will be provided at no additional cost. If reports include confidential, personally identifiable, or sensitive information, those reports must be labeled (Confidential). Information classification can be referenced in the SIMM5305-A section.

All reports will have minimum capabilities of being queried, sorted and filtered by any field contained in the report and by data parameters such as date or date range, asset

IDs, hierarchy, asset operator, geofence activity, or other parameters as agreed upon by ordering agency.

Reports will be readable on screen, printable and downloadable. Reports will be downloadable from the Application and be transmitted to the ordering agency via a scheduled email when report size allows, in any of the formats listed below. Zip file format or an option like dropbox will be used when emailing report(s) or data, where possible. Where the data transmission exceeds the allowable size for emailing, even with Zip file format, a Secure File Sharing process will be created. The Application will also have an ad hoc reporting feature, which allows for creation of reports that can be one time reports or become a regularly generated report. Available file types will include Excel (2013 or newer), Portable Document Format (.PDF), text comma delimitated (.txt), Comma Separated Values (.CSV), and Hypertext Markup Language

(HTML) at a minimum. Report(s) will be subject to approval by the ordering agency.

Overlay Mapping Analysis

• Asset’s location will be tracked and its travel plotted with no gaps between reporting points including directional arrows at reporting points on current maps. Travel will be depicted in lines corresponding to traveled route on up to date maps. Route will correspond to roadway traveled.

• The Contractor is responsible for identifying gaps in data. All gaps in data will be investigated and acted upon by the Contractor to minimize impact to the ordering agency. The Contractor will report to the ordering agency all data gap instances and proposed solutions including time lines to correct the cause. If the cause is not related to hardware malfunction, data transmission coverage issue, or installation fault, the Contractor will provide a detailed report of actionable findings to the ordering agency. Reporting will occur within one (1) week of gap occurrence, in writing. Acceptable formats are .PDF, .txt, e-mail, or Word (.doc).

• Mapping will plot and provide latitude and longitude coordinates and nearest address if available. The pinged asset location or event based data transmission should take no longer than thirty (30) seconds to be received via Application overlay map. The ping or event based data transmission will locate the asset regardless of ignition status.

• Overlay maps will be easy to navigate for an accurate depiction of the assets daily movements. Easy navigation means web users are able to easily find and identify daily movements of assets in a consistent manner.

• Overlay maps will load within a ten (10) second timeframe.

• Overlay maps and asset location will be updated within thirty (30) seconds when a device condition/health check is requested via the application portal.

• Overlay mapping will be scalable to display individual assets up to and including a nationwide view.

• Mapping will include selectable views allowing District, County, Region, and Zip

Code boundaries to be added individually or in groups overlaid on the map display.

Asset activity associated with these boundaries will be accessible in the Application and in report generation.

Application Generated Reports

The Application will generate the following pre-built (canned) reports through the secure internet site. All canned data will be available through the Application. All canned reports will be scalable, at a minimum, by:

• Asset(s) ID

• Asset operator name(s) and ID number(s)

• GPS device type and serial number

• Asset(s) odometer value

• Asset(s) summed mileage

• Alerts

• Geofence location(s)/violation(s)

• Ordering agency groups

• Ordering agency hierarchy

• VIN

• Asset year

• Asset manufacturer

• Asset model

• Asset fuel type

• Ordering agency defined regions, or

• Ordering agency assigned asset attributes

Equipment Report

The Application will provide an on demand report of all assigned Asset (in use). The report will include at a minimum:

• Asset ID

• Ordering Agency hierarchy

• Current dash odometer reading

• Asset operator name and ID number

• Asset year

• Asset make

• Asset model

• Contractor device serial number

• VIN

• Location latitude and longitude, nearest address where available and geofence information

Equipment Alert Report

The Application will provide at a minimum the ability to generate an alert report queried by Asset ID and date parameters. This report will be available on demand or as a scheduled daily, weekly or monthly delivered report. Alerts may be sent via e-mail, SMS or MMS. Alert data will include, but not be limited to:

• Identifying the type and time of alert, example MIL commanded on (as applicable)

• Excessive idling

• Speeding

• Off network

• Non-reporting unit

• Device disconnected

• Battery or supply voltage near lower threshold

• Diagnostic Trouble Code

• Geofence entrance or exit

• Unidentified operator

Automobile Log Report

The Application will provide a report with the following data points for each trip in report form within any time period where the data is accessible. This report will be available on demand or as a scheduled daily, weekly or monthly delivered report:

• Asset ID

• Asset operator name and ID number

• Ordering agency hierarchy

• Date and time of travel

• Begin trip dash odometer/dash hour-meter

• End trip dash odometer/dash hour-meter

• Trip mileage

• Engine hours

• Trip start location o Latitude and Longitude o Nearest address where available o Geofence information

• Trip end location o Latitude and Longitude o Nearest address where available o Geofence information

• Hyperlink to map for each location

• Overnight storage location for date of trip(s)

Usage Summary Report

The Application will generate a total usage summary report within any time period where the data is accessible, for a little as a one-hour time period and up to a year, indicating actual number of assets used during the selected time period. This report will be available on demand or as a scheduled daily, weekly or monthly delivered report.

This report will be summed by Asset ID. This report will be detailed to reflect the:

• Asset ID

• Ordering agency hierarchy

• Days used

• Begin dash odometer/dash hour-meter value

• End dash odometer/dash hour-meter value

• Mileage and/or hours used

• Overnight storage location

• Start latitude and longitude

• End latitude and longitude

• Nearest Addresses where available

• Hyperlink to map for each location

• Any geofences the asset stopped within

• Fuel used for the time period

Activity Detail Report

This report will show all of the asset activity data listed below, and be adjustable to any time range as for a little as a one-hour time period and up to a year. This report will be available on demand or as a scheduled daily, weekly or monthly delivered report.

ordering agency will have rights to pull up to one (1) month of time, in one request. This will be ping by ping (or event by event) for the time period requested. Map route tracking log will be available at a minimum for one (1) month in the Application portal and a minimum of two (2) years in the Application database. The report will provide, for each ping/event:

• Asset ID

• Asset operator name and ID number

• Ordering agency hierarchy

• Latitude and longitude location for each ping

• Asset hierarchy information

• Hyperlink to map for each location

• Nearest Addresses where available

• Date and time of each ping

• Asset operator ID for each ping

• Ignition Status for each ping

• Directional heading

• Average speed

• Max speed

• Instantaneous speed

• Posted speed

Fleet Asset Management Report

The Fleet Asset Management Report will be provided on a monthly basis and include the following data for the previous month time period:

• Days used

• Ending dash odometer value

• Ending hour-meter value

• Asset ID

• Asset Operator ID

• year/make/model

• VIN

Speeding Violation Report

A Speeding Violation Report will be provided on a weekly basis. This report will show the raw data and data in graph form. The report will be available in .PDF and Excel.

Contractor must be willing to provide a subject matter expert to stand behind their data in a court of law if required. If required by an agency to provide a subject matter expert in a court of law, the applicable agency shall pay for any costs and expenses incurred by Contractor to satisfy the applicable agency's request. This report will include and be scalable by:

• Asset ID

• Asset operator name and ID number

• Ordering agency hierarchy

• Average speed

• Minimum speed

• Maximum speed

• Duration of speed

• Posted speed

• Latitude and longitude

• Hyperlink to map for each location

• Nearest address where available

• Ordering agency defined hierarchy

Overnight Storage Report

The Overnight Storage Report will be provided on a monthly basis and cover a one-month time period, but will also be available on demand and for any time period up to one (1) year of data. This report will identify the overnight storage location for all assets and will include:

• Asset ID

• Asset operator name and ID number

• Ordering agency hierarchy

• Date

• Time

• Begin of day location latitude and longitude and nearest address where available)

• End of day location (latitude and longitude and nearest address where available)

• Hyperlink to map for begin and end locations

• Mileage traveled

• Engine hours for the day

Key Fob “Frequently Operated Button” Compliance Report (Asset

Operator ID)

The Key Fob Compliance Report will be provided on a weekly basis, and on demand.

The ordering agency will also have rights to pull this report for any time period up to one

(1) year. This report will provide, per trip, if an asset operator was assigned for the trip.

This report will show the raw data and the data in graph format acceptable to ordering agency.

Malfunction Indicator Lamp Report:

The Malfunction Indicator Lamp (MIL) report will be schedulable, on all applicable asset(s), and contain, at a minimum, the following data points:

• VIN

• Asset ID

• Ordering agency hierarchy

• License Number

• Year

• Make

• Model

• Fuel Type

• MIL status (on/off)

• Active DTC’s

• Monitor Status (complete/incomplete):

o Catalyst o Fuel System o Oxygen Sensor(s) o Oxygen Sensor Heater(s) o Secondary Air System o Misfire o Comprehensive Component o Exhaust Gas Recirculation System o Evaporative System o Heated Catalyst

The MIL report will have the following filters based on current BAR/CARB program requirements and regulations:

• Pass

• Failed

• Ineligible – Indicates assets not subject to BAR/CARB smog check

• CTP – Indicates assets participating in BAR/CTP Program

Custom Reporting Requirements

The Contractor agrees to work with ordering agency to meet the evolving reporting needs of ordering agency. Reports will be created as part of the Contract with no additional charges to ordering agency. Reports may be one-time reports, for a particular project or need, or regularly scheduled reports, delivered by e-mail when size allows, or available for download through the Application. All reports are scalable by the same parameters as the canned reports. All reports will include the ordering agency defined asset hierarchy. Ordering agency defined asset operator hierarchy will also be included whenever a report requires asset operator information.

Program Interface (PI)

A. The PI shall be capable of providing bidirectional, real-time information transfer between:

• The Application

• Ordering agency fleet management software

• ELD

• Ordering agency’s electric vehicle charger network

• Ordering agency bulk fuel network

• Ordering agency commercial fuel network

• The State of California’s, Employee Identity Software, per ordering agency.

The PI will provide one directional, real-time information to the BAR CTP, DGS

Office of Fleet Asset Management (OFAM) Fleet Asset Management System

(FAMS) and ordering agency ESRI software. At this time, BAR and ESRI are the only known working PI. Contractor must be able to work with agencies on additional

PI. The Application information transfer will be seamless, undetectable to log in users, and will not require portal exit log out to execute. Information must be accessible to authorized fleet managers.

B. Required data elements will be collected and an ability provided to integrate those data elements via free PIs into third-party application for reporting. Third-party application could include fleet asset management software, such as AssetWorks.

C. The PI will push available industry standard diagnostic information to the fleet management software, as required by the ordering agency.

D. The PI will push dash odometer, dash hour-meter, engine hour usage, days of use, overnight storage location, and other usage information to be determined, as needed to the ordering agency fleet management software.

E. The PI will pull asset information, such as hierarchy, year, make, model, VIN, license plate and other asset identifying information, as needed from the fleet management software.

F. Further data definitions, data mapping specifications, and Representational State

Transfer Architecture (RESTful) services will be developed during the consulting period.

G. The Roadmap will also be developed during the consulting period and agreed upon by the Contractor and ordering agency. The Roadmap will include potential changes in ordering agency data needs, fleet management software or need for other changes to the data definitions or RESTful services.

H. The security and privacy of the PI will meet or exceed the security and privacy requirements of the Application.

I. The terms of service and service level for the PI will be established by a collaborative team comprised of Contractor, ordering agency, and ordering agency

IT and will be drafted during the consulting phase by the Contractor in writing. The

Contractor must obtain ordering agency, and ordering agency IT written approval prior to commencement.

J. Any licensing (interface, data, code) and any policies will be provided in writing by the Contractor. Contractor must obtain ordering agency, and ordering agency IT written approval prior to commencement.

K. A Changelog will be provided, in writing, to ordering agency. The Changelog will include records of requests for changes from ordering…