Time period (day, month, year). Toll Transaction Processing Summary Report The OBOS receives transactional information from roadside toll systems and builds them into viable transactions. WSDOT requires the OBOS to receive and process roadside toll information according to WSDOT business rules and guidelines. It is critical for OBOS to document both viable and non-viable transactions. It is a check point for roadside toll systems performance. WSDOT requires OBOS to produce a comprehensive toll transactions processing report that will document the processing status for all toll transactions built for a given period. The report shall also provide the ability to locate a specific transaction by license plate or pass number. Specific requirements for this report shall include: The OBOS is responsible to build complete toll transactions as either pass-based or image-based. This report will summarize all information received from each roadside toll system and put them in the following processing categories: Received; Viable; Built completed, In review, Dismissed (from image review, duplicates, etc.), and Specialties (from HOV); Non-viable; Variances; For the In-image review and dismissed categories, the report will provide additional details, to ensure all images are being reviewed and all dismissals are accounted for correctly. This includes: Image review transactions -The report shall follow the normal image review workflow and summarize the transaction counts in each stage of the workflow, and Dismissed - The report list all dismissal reasons, including various image review rejection/dismissal reasons, and summarize the transaction counts for each dismissal reason. The dismissal reasons must be configurable based on WSDOT business rules; This report will support both operations and financial reconciliations. The report must be capable of running with multiple parameters. These parameters shall include but not be limited to: Toll facility; Toll lane; Type of transactions (pass vs.
Time period (day, month, year). Toll Transaction Processing Summary Report The OBOS receives transactional information from roadside toll systems and builds them into viable transactions. WSDOT requires the OBOS to receive and process roadside toll information according to WSDOT business rules and guidelines. It is critical for OBOS to document both viable and non-viable transactions. It is a check point for roadside toll systems performance. WSDOT requires OBOS to produce a comprehensive toll transactions processing report that will document the processing status for all toll transactions built for a given period. The report shall also provide the ability to locate a specific transaction by license plate or pass number. Specific requirements for this report shall include: The OBOS is responsible to build complete toll transactions as either pass-based or image-based. This report will summarize all information received from each roadside toll system and put them in the following processing categories: Received; Viable; Built completed, In review, Dismissed (from image review, duplicates, etc.), and Specialties (from HOV); Non-viable; Variances; For the In-image review and dismissed categories, the report will provide additional details, to ensure all images are being reviewed and all dismissals are accounted for correctly. This includes: Image review transactions -The report shall follow the normal image review workflow and summarize the transaction counts in each stage of the workflow, and Dismissed - The report list all dismissal reasons, including various image review rejection/dismissal reasons, and summarize the transaction counts for each dismissal reason. The dismissal reasons must be configurable based on WSDOT business rules; This report will support both operations and financial reconciliations. The report must be capable of running with multiple parameters. These parameters shall include but not be limited to: Toll facility; Toll lane; Type of transactions (pass vs.
IndustryComment_CSCBOSTechSpecs_Amend.docx