SLA Table.docx
DOCX document 23 KB Posted
- Attached to
- WSDOT- Highway Speed Camera Pilot Program
- Solicitation number
- RFQQ 2024-0904
- Issued by
- Adams County, Asotin County, Benton County, Chelan County, Clallam County, Clark County, Columbia County, Cowlitz County, Douglas County, Ferry County, Franklin County, Garfield County, Grant County, Grays Harbor County, Island County, Jefferson County, King County, Kitsap County, Kittitas County, Klickitat County, Lewis County, Lincoln County, Mason County, Okanogan County, Pacific County, Pend Oreille County, Pierce County, San Juan County, Skagit County, Skamania County, Snohomish County, Spokane County, Stevens County, Thurston County, Wahkiakum County, Walla Walla County, Whatcom County, Whitman County, Yakima County, Asotin City, Clarkston City, Clarkston Heights-Vineland CDP, West Clarkston-Highland CDP, Benton City, Chelan City, Chelan Falls CDP, Clallam Bay CDP, Lewisville CDP, Rock Island City, Pacific Beach CDP, Whidbey Island Station CDP, Mercer Island City, Pacific City, Bainbridge Island City, Kingston CDP, Kitsap Lake CDP, Kittitas City, Klickitat CDP, Okanogan City, Anderson Island CDP, Fort Lewis CDP, Fox Island CDP, Herron Island CDP, Ketron Island CDP, North Fort Lewis CDP, Raft Island CDP, Stevenson City, Hat Island CDP, Lake Stevens City, Snohomish City, Spokane City, Spokane Valley City, Puget Island CDP, Garfield Town, Yakima City, Washington
About this file
This document contains a Service Level Agreement (SLA) table for a state and local contract opportunity issued by the Washington State Department of Transportation (WSDOT) for the installation of 2 Average Speed systems at locations to be determined. The SLA outlines service requirements, measurements, and associated Service Level Agreements (SLAs) and credits for issues such as problem notification, problem resolution, and scheduled system downtime/maintenance. The contract opportunity is for a Highway Speed Camera Pilot Program and covers jurisdictions across the state of Washington, including counties such as Franklin, Grant, Grays Harbor, Chelan, Yakima, and others.
The SLA includes provisions for timely notification and resolution of high and low priority issues, with SLA credits ranging from 1% to 2% of the contract value. Scheduled system downtime and maintenance is required to occur during non-business hours, with 14 calendar days' notice provided to WSDOT. No additional pricing details or funding information is provided in the document.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Exhibit C-CostProposal.docx | DOCX document | |
| Exhibit D-Contract.docx | DOCX document | |
| 2024-0904 - Amendment2.docx | DOCX document | |
| REVISED-2-Exhibit B-PerformanceRequirements.docx | DOCX document | |
| 2024-0904 -Highway Speed Camera RFQQ.docx | DOCX document | |
| Exhibit A-3-Client Reference Form.docx | DOCX document | |
| Exhibit E-ContractIssuesList.docx | DOCX document | |
| 2024-0904 - Amendment1.docx | DOCX document | |
| Mailing Process Graphic.pdf | ||
| Exhibit A -1-BiddersCertification.docx | DOCX document | |
| Exhibit F-DiverseBusinessInclusionPlan.docx | DOCX document | |
| REVISED Exhibit B-PerformanceRequirements.docx | DOCX document | |
| Deliverables Table.docx | DOCX document | |
| Exhibit A -2-BiddersProfile.docx | DOCX document | |
| Exhibit B-PerformanceRequirements.docx | DOCX document | |
| 2024-0904-Q&A-1.docx | DOCX document | |
| 2024-0904-Q&A-2.docx | DOCX document |
Show all 17
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Service Level Measurements Table (System Performance)
| No. |
| Service Requirement |
| Measurement |
| Service Level Agreement |
| SLA Credit |
| 1 |
| Problem Notification - High |
| For issues that involve service disruption, impact data collection, or lead to issues related to the integrity of the program, WSDOT Program Management is notified via phone and/or e-mail (e.g., equipment malfunction and system outages). |
| 100 % < 2 hours |
| 1% |
| 2 |
| Problem Notification - Low |
| For issues that involve no service disruption or impact to data collection, WSDOT Program Management is notified via e-mail (e.g., personnel issues). |
| 100 % < 24 hours |
| 1% |
| 3 |
| Problem Resolution - High |
| Eliminate the system operation interruption or provide a plan acceptable to WSDOT that will resolve the problem to eliminate system operation interruption. When a plan is provided, problem must be resolved within agreed upon time frame or SLA credit will be assessed. |
| 100 % < 24 hours |
| 2% |
| 4 |
| Problem Resolution - Low |
| Resolve the problem or provide plan to resolve problem. When a plan is provided, problem must be resolved within agreed upon time frame or SLA credit will be assessed. |
| 100 % < 5 business days |
| 2% |
| 5 |
| Scheduled System Downtime/ |
Maintenance
| Scheduled system maintenance, inspection and downtime (inclusive of both back office systems and field equipment) shall only occur during non-business hours. The ASV shall provide 14 calendar days’ notice prior to any scheduled downtime. |
| <12 hours each month |
| 1% |
| 6 |
| Service Availability |
| All application functionality and accessibility shall be maintained at 99.5% uptime performance levels. ASV shall minimize or eliminate unscheduled system downtime to 0.5% or less. This metric applies to, but is not limited to, the speeding event processing system, reports system. |
| <99.5% |
| 1% |
| 7 |
| Enforcement and Collection Availability |
| Contract pay will be based on a per time cost the system is operational (proportional to lump sum contract amount). Payment to the ASV will be made on a per hour per location fee. Scheduled downtime will be not be included in any measure of ‘missed’ enforcement time. |
| Maximum Operational Time – Scheduled Service/Maintenance Time |
| Equivalent to Percentage Hours Reduction in Collection Time |
| 8 |
| Disaster Recovery |
| ASV shall provide recovery and continuity of operations within 24 hours of a System/network failover. |
| 24 hours |
| 2% |
| 9 |
| Notification of Security Incident |
| Notification of a Security Incident within 4 hours of occurrence |
| 4 hours |
| 1% |
File details come from the government source that posted it. Updated .