1 / 14

Appendix C

Appendix C. Operational Scenarios and Functional Thread Diagrams. Operational Scenarios and Functional Thread Diagrams.

abeni
Download Presentation

Appendix C

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Appendix C Operational Scenarios and Functional Thread Diagrams

  2. Operational Scenarios and Functional Thread Diagrams • An “operational scenario” is a description of how a state intends that their customers and the state, or the state and core infrastructure systems should interact to accomplish key CVISN functions. An example was given in chapter 4. More examples are provided here. • The operational scenario is shown as a list of sequential steps. To differentiate between different time schedules, numbers are used to show the interaction between the applicant and the state, and the state’s update of snapshots. Those interactions occur as soon as possible after the initial application is received by the state. Letters are used to show the state’s connections to the clearinghouses, since that occurs at a regular period instead of being triggered immediately by the carrier’s actions. • Each operational scenario is illustrated by overlaying information onto the state system design template. The lines represent data flow between products, with arrows indicating the direction of flow. Each line is labeled with a number or letter. The complete set of lines constitutes a thread of activities that accomplish a function. Hence, the diagram is called a “functional thread diagram.” • This appendix provides examples of operational scenarios and functional thread diagrams. They are included for reference, and as starting points for states that plan to implement similar processes.

  3. CVISN Level 1 Credentials AdministrationKey Operational Scenarios • Accept and process electronic IRP credential applications for supplements (e.g., adding a vehicle to an existing account) • Example 1: MD Design using VISTA/RS, InterCAT, CVIEW • Accept and process electronic IRP renewal applications • Accept and process electronic IFTA credential applications for supplements (e.g., changing the carrier’s address) • Accept and process electronic IFTA renewal applications • Example 2: RPC, PC-CAT, CVIEW • Example 3: VISTA/TS, Web Browser/WebCAT, CVIEW • Accept and process electronic filing of and payment for IFTA quarterly tax returns • Example 4: RPC, PC-CAT, CVIEW • Example 5: VISTA/TS, Web Browser/WebCAT, CVIEW

  4. 1. Carrier enters an IRP credential application via a Carrier Automated Transaction (CAT) system which submits it to the Credentialing Interface (CI) as an EDI X12 TS 286. 2. The CI submits a query to its state database to perform preliminary checks as part of evaluating the application. 3. The state database reports the status, i.e., flags and condition to the CI. 4. If a satisfactory status is received, the application is sent to the IRP system (VISTA/RS) for processing via EDI X12 TS 286. 5. The IRP system processes the application and sends an invoice notice to the CI via EDI X12 TS 286. 6. The CI sends the invoice notice to the CAT via EDI X12 TS 286 and maintains archival/audit copies of all transactions. 7. The carrier reviews the invoice data and verifies that the application data matches the intent. The CAT sends payment method information to the CI via EDI X12 TS 286. 8. If a Temporary Authority (TA) is requested, the CI releases it to the CAT via EDI X12 TS 286. 9. If a TA was granted, the CI sends a vehicle snapshot segment update to CVIEW via EDI X12 285. 10. CVIEW sends updated snapshot data to SAFER via EDI X12 TS 285. 11. CVIEW sends updated snapshot data to Roadside via EDI X12 TS 285. 12. SAFER sends updated snapshot data to subscribers via EDI X12 TS 285. 13. The CI verifies payment method information (financial system interfaces are not shown)and passes payment approval to the IRP system via EDI X12 TS 286. 14. The IRP system validates payment amount and updates application status to indicate the permanent credential granted and notifies the CI via EDI X12 TS 286. 15. The CI passes the permanent credential to the CAT via EDI X12 TS 286. Cab Cards may be printed in the carrier’s office or state office. 16. The CI updates CVIEW with permanent credential information via EDI X12 TS 285. 17. CVIEW sends updated snapshot data to SAFER via EDI X12 285. 18. CVIEW sends updated snapshot data to Roadside via EDI X12 285. 19. SAFER makes updated snapshot data available to subscribers via EDI X12 TS 285. A. Periodically (daily), the IRP system sends updates to the IRP Clearinghouse on IRP registration information and fee payments (recaps). B. Monthly, the IRP Clearinghouse makes available the fee information (pre-netting transmittals) to the participating jurisdictions for approval and/or correction. Today, the states review the information interactively using terminals. In the future, it may be possible to receive the transmittals using EDI TS 286. If an EDI interface is provided, the interaction will occur with the CI. C. The IRP Office and also other participating jurisdictions report back to the IRP Clearinghouse the approvals or corrections. Today, the approvals/corrections are made via terminals. In the future, it may be possible to use TS 286. If an EDI interface is provided, the interaction will occur with the CI. D. The IRP Clearinghouse performs the actual netting and makes available corrected/approved vehicle and fee actions (post-netting transmittal) and netting results (remittance netting reports) to the participating jurisdictions. Today, the information is reviewed via terminals. In the future, it may be possible to use TS 286. If an EDI interface is provided, the interaction will occur with the CI. Accept and process electronic IRP credential applications for supplements Example 1: MD Design using VISTA/RS, InterCAT, CVIEW NOTE: Functional acknowledgment for all EDI messages (except TS 997) is made by responding with a TS 997. Content errors in a received TS 286 are noted by also replying with a TS 286. The results of processing an incoming TS 285 are reported via TS 824.

  5. L S I L S I L S I L M L M L M CAPRI IFTA Tax Processing Treasury or Revenue L S I L S I L S I L S I L M L M L M L M HazMat OS/OW SAFETYNET IFTA Registration L S I L S I L S I L M L M L M Titling Driver Licensing SSRS L S I L M Intrastate Veh Registration L M Screening Sensor/ Driver Comm L M L M L M Roadside Operations ASPEN IRP L S I L S I L M L M Citation & Accident State Database Accept and process electronic IRP credential applications for supplements Example 1: MD Design using VISTA/RS, InterCAT, CVIEW Generic State Commercial Vehicle Administration Systems 1 D VISTA/RS 13 14 IRP Office 6 CVISN Core Infrastructure Systems (National/Regional) 5 Service Providers Credentialing Interface (CI) C 7 4 Carrier Systems E-Screening Enrollment Credentialing System (e.g., CAT) B CDLIS 8 IRP Clearinghouse 15 A Internet Tools IFTA Clearinghouse ASAP MCDC Web CAT 9, 16 NMVTIS 2, 3 Other Carrier Systems RSPA HazMat CV Info Exchange Window (CVIEW) MCMIS BCD 10, 17 11, 18 SAFER Generic State Roadside Systems Licensing & Insurance 12, 19 Carrier Commercial Vehicle ASAP Analysis Admin/CAPRI Transponder Other Jurisdictions

  6. 1. The IFTA Registration System sends a registration renewal notification to the Credentialing Interface (CI) via EDI X12 TS 286. 2. The CI sends the notification to the Carrier Automated Transaction (CAT) via EDI X12 Ts 286. 3. The carrier enters an IFTA registration application using a Carrier Automated Transaction (CAT) system, and sends it to the Credentialing Interface (CI) via EDI X12 TS 286. The carrier pays for the application (through EFT, credit card, debit card,…) 4. The CI checks the carrier’s status (delinquent, non payment etc.…) with the IFTA Registration System and IFTA Clearinghouse via Regional Processing Center (RPC). 5. The CI sends the application to the IFTA Registration System via EDI X12 TS 286. 6. Once the application is processed by the IFTA Registration System, a message is returned to the CI via EDI X12 TS 286.If processing was completed successfully, credential information is returned. If problems were found, an error message is returned. 7. The IFTA Registration System also proactively updates the CI whenever the carrier’s status changes, (e.g., from Active to Inactive, Active to Revoked). 8. The CI sends a return message to the CAT via EDI X12 TS 286. A. Periodically (no more than daily), the IFTA Registration System creates a file reflecting IFTA credential renewals, additions, and changes. The information is sent to RPC in RPC proprietary format. B. Daily, RPC updates new or changed IFTA credential information (Demographic) and sends it to the IFTA Clearinghouse, for all client jurisdictions, via EDI X12 TS 286. C. The IFTA Clearinghouse updates its database with registration information (Demographic) from all participating jurisdictions. Jurisdictions using RPC can access clearinghouse data via a server located at RPC. Jurisdictions can also access queries and reports from the IFTA web site and can request creation of an “extract” file, and then download all demographic data submitted by all participating jurisdictions in EDI X12 TS 286 format. D. Nightly, the CI generates a new or modified carrier snapshot IFTA segment and sends it to CVIEW via TS 285. E. CVIEW updates the carrier snapshot with IFTA credential data and forwards it to subscribers, including SAFER and the State roadside sites via EDI X12 TS 285. F. SAFER updates (or creates) a carrier snapshot with IFTA credential data and forwards it to subscribers via EDI X12 TS 285. Accept and process electronic IFTA renewal applications Example 2: RPC, PC-CAT, CVIEW NOTE: Functional acknowledgment for all EDI messages (except TS 997) is made by responding with a TS 997. Content errors in a received TS 286 are noted by also replying with a TS 286. The results of processing an incoming TS 285 are reported via TS 824.

  7. L S I L S I L M L M Treasury or Revenue CAPRI L S I L S I L S I L S I L M L M L M L M OS/OW IRP HazMat SAFETYNET L S I L S I L S I L M L M L M Driver Licensing Titling SSRS L S I L M Intrastate Veh Registration L M Screening Sensor/ Driver Comm L M L M L M IFTA Registration Roadside Operations IFTA Tax Processing L S I L M Citation & Accident Accept and process electronic IFTA renewal applications Example 2: RPC, PC-CAT, CVIEW Generic State Commercial Vehicle Administration Systems 4 RPC 4 CH Access CVISN Core Infrastructure Systems (National/Regional) 5 Service Providers Credentialing Interface (CI) 2 C Carrier Systems 6, 7 C 3 A E-Screening Enrollment Credentialing System (e.g., CAT) CDLIS 8 1 IRP Clearinghouse Internet Tools B IFTA Clearinghouse ASAP MCDC Web CAT NMVTIS Other Carrier Systems RSPA HazMat CV Info Exchange Window (CVIEW) D MCMIS E SAFER C Generic State Roadside Systems Licensing & Insurance F Carrier Commercial Vehicle ASAP Analysis Admin/CAPRI Transponder Other Jurisdictions

  8. 1. Carrier enters an IFTA registration application via a Web Browser to a Web Cat. The carrier pays for the application (through EFT, credit card, debit card,…). 2. The Web CAT passes it to the Credentialing Interface (CI) via EDI X12 TS 286. 3. The CI sends the application to VISTA/TS via EDI X12 TS 286 for processing. Note: The Web Cat, VISTA/TS, and/or the CI validates the application data to determine completeness, format, agreement with business rules, payment status, and whether to grant or deny the credential. 4. Once the application is processed by VISTA/TS, a message is returned to the CI via EDI X12 TS 286. 5. If processing was completed successfully, credential information is returned to the Web Cat via EDI X12 TS 286. 6. The carrier retrieves the credential information from the Web Cat using a Web Browser. A. Nightly, VISTA/TS updates new or changed IFTA credential information (Demographic) for all VISTA/TS clients and sends it to the IFTA Clearinghouse via EDI X12 TS 286. B. The IFTA Clearinghouse updates its database with registration information (Demographic) from all participating jurisdictions. Jurisdictions can access queries and reports from the IFTA web site. Jurisdictions can also request creation of an “extract” file, and then down load all demographic data submitted by all participating jurisdictions in EDI X12 TS 286 format. C. Nightly, VISTA/TS generates a new or modified carrier snapshot IFTA segment for all VISTA/TS clients and sends it to CVIEW via TS 285. (Alternatively VISTA/TS could generate a new or modified carrier snapshot IFTA segment and provide it to the CI and then CI sends it to CVIEW). D. CVIEW updates the carrier snapshot with IFTA credential data and forwards it to subscribers, including SAFER and the State roadside sites via EDI X12 TS 285. E. SAFER updates (or creates) a carrier snapshot with IFTA credential data and forwards it to subscribers via EDI X12 TS 285. Accept and process electronic IFTA renewal applications Example 3: VISTA/TS, Web Browser/WebCAT, CVIEW NOTE: Functional acknowledgment for all EDI messages (except TS 997) is made by responding with a TS 997. Content errors in a received TS 286 are noted by also replying with a TS 286. The results of processing an incoming TS 285 are reported via TS 824.

  9. L S I L S I L S I L M L M L M Treasury or Revenue CAPRI IFTA Tax Processing L S I L S I L S I L S I L M L M L M L M IRP OS/OW SAFETYNET HazMat L S I L S I L S I L M L M L M Titling Driver Licensing SSRS L S I L M Intrastate Veh Registration L M Screening Sensor/ Driver Comm L M L M L M ASPEN Roadside Operations IFTA Registration L S I L M Citation & Accident Accept and process electronic IFTA renewal applications Example 3: VISTA/TS, Web Browser/WebCAT, CVIEW Generic State Commercial Vehicle Administration Systems CH Access B CVISN Core Infrastructure Systems (National/Regional) Service Providers 4 Credentialing Interface (CI) 3 Carrier Systems VISTATS E-Screening Enrollment Credentialing System (e.g., CAT) CDLIS A 2 IRP Clearinghouse Internet Tools 1 IFTA Clearinghouse 5 ASAP MCDC Web CAT NMVTIS 6 Other Carrier Systems RSPA HazMat CV Info Exchange Window (CVIEW) C MCMIS D B SAFER Generic State Roadside Systems Licensing & Insurance E Carrier Commercial Vehicle ASAP Analysis Admin/CAPRI Transponder Other Jurisdictions

  10. NOTE: The Regional Processing Center (RPC) retrieves tax rate matrices from IFTA Inc. and sends the matrices to the Credentialing Interface (CI) whenever the rates change. 1. The CI generates a tax filing notification for each carrier registered under IFTA and sends it to the Carrier Automated Transaction (CAT) via EDI X12 TS 813. 2. The carrier queries the CI for appropriate tax rate matrices using the CAT via EDI X12 TS 150. 3. Daily, RPC sends the CI any credits available to the carrier. 4. The CI sends the CAT the appropriate tax matrices and any credits due the carrier via EDI X12 TS 150 and 813 respectively. 5. The carrier enters IFTA tax filing information using the CAT and submits it to the CI via EDI X12 TS 813. The carrier pays the Tax Due (through EFT, credit card, debit card,…). 6. The CI verifies the correct carrier name, ID,… and checks the carrier’s status (Active, Inactive, Revoked, or Suspended) with the IFTA Registration System. 7. The IFTA Registration System also proactively updates the CI whenever the carrier’s status changes, (e.g., from Active to Inactive). A. Nightly, the CI forwards the carrier’s tax filings and status to RPC in RPC proprietary format. B. The tax filings are checked for format and correct calculations when received from the CI. A netting function is performed on a monthly basis prior to transmittal to the IFTA CH. RPC clients place payments in accounts according to the netting results. Monthly, RPC sends a transmittal summary to the IFTA Clearinghouse via EDI X12 TS 826. C. The IFTA Clearinghouse updates its database with tax filing information (Transmittal) from all participating jurisdictions. Jurisdictions using RPC can access clearinghouse data via a server located at RPC. Jurisdictions can also access queries and reports from the IFTA web site and can request creation of an “extract” file, and then download all Transmittals data submitted by all participating jurisdictions in EDI X12 TS 826 format. D. Nightly, the CI generates a new or modified carrier snapshot IFTA segment and sends it to CVIEW via TS 285. E. CVIEW sends the updated snapshot IFTA segments to SAFER and the State Roadside via EDI X12 TS 285. F. SAFER updates the snapshots with IFTA data and provides them to subscribers and other jurisdictions via EDI X12 TS 285. Accept and process electronic filing of & payment for IFTA quarterly tax returns Example 4: RPC, PC-CAT, CVIEW NOTE: Functional acknowledgment for all EDI messages (except TS 997) is made by responding with a TS 997. The results of processing an incoming TS 285 are reported via TS 824. Content errors in a received TS 826 and 150 are noted by replying with a TS 824. Content errors in a TS 813 are replied with a TS 151.

  11. L S I L S I L M L M CAPRI Treasury or Revenue L S I L S I L S I L S I L M L M L M L M IRP OS/OW HazMat SAFETYNET L S I L S I L S I L M L M L M SSRS Titling Driver Licensing L S I L M Intrastate Veh Registration L M Screening Sensor/ Driver Comm L M L M L M L M ASPEN IFTA Registration IFTA Tax Processing Roadside Operations L S I L M Citation & Accident Accept and process electronic filing of & payment for IFTA quarterly tax returns Example 4: RPC, PC-CAT, CVIEW Generic State Commercial Vehicle Administration Systems RPC A 1 3 CH Access CVISN Core Infrastructure Systems (National/Regional) C Service Providers Credentialing Interface (CI) 2 6, 7 Carrier Systems C E-Screening Enrollment Credentialing System (e.g., CAT) CDLIS 4 IRP Clearinghouse 5 Internet Tools B IFTA Clearinghouse ASAP MCDC Web CAT NMVTIS Other Carrier Systems D RSPA HazMat CV Info Exchange Window (CVIEW) MCMIS F SAFER C Generic State Roadside Systems Licensing & Insurance E Carrier Commercial Vehicle ASAP Analysis Admin/CAPRI Transponder Other Jurisdictions

  12. 1. VISTA/TS generates a tax filing notification for each carrier registered under IFTA and sends it to the Credentialing Interface (CI) via EDI X12 TS 813. 2. The CI sends the notifications to the Web Cat via EDI X12 TS 813. 3. The carriers retrieve the notification from the Web Cat using a Web Browser. 4. VISTA/TS sends the appropriate Tax Rates to the CI via EDI X12 TS 150. 5. The CI forwards the Tax Rates to the Web Cat via EDI X12 TS 150. 6. The carriers enter IFTA tax filing information to the Web Cat using a Web Browser. The carrier pays the Tax Due (through EFT, credit card, debit card….). 7. The Web Cat performs calculations using tax rates and sends the IFTA tax filing information to the CI via EDI X12 TS 813. Note: The Web Cat and/or the CI validate the tax filing data to determine completeness, format, and agreement with business rules. 8. The CI receives the transaction and sends the tax filing to VISTA/TS via EDI X12 TS 813 for processing. Note: VISTA/TS validates and tracks tax filing data to determine payment status. A Nightly, VISTA/TS evaluates and updates tax filing (Demographic, including Tax Payer Type and Status - Active, Inactive, Revoked, or Suspended), information for all client jurisdictions, and sends it to the IFTA Clearinghouse via EDI X12 TS 826. VISTA/TS also generates updated snapshot IFTA segments and provides them to CVIEW via EDI X12 TS 285. (Alternatively, VISTA/TS may provide snapshot IFTA segment updates to the CI for transmittal to CVIEW). B. CVIEW sends the updated snapshot IFTA segments to SAFER and the State Roadside via EDI X12 TS 285. C. SAFER updates the snapshots with IFTA data and provides them to subscribers and other jurisdictions via EDI X12 TS 285. D. Monthly, VISTA/TS updates tax filing (transmittal) information for all client jurisdictions and sends it to the IFTA Clearinghouse via EDI X12 TS 826. E. The IFTA Clearinghouse updates its database with transmittal tax filing information (transmittal) from all participating jurisdictions. Jurisdictions can access queries and reports from the IFTA web site. Jurisdictions can also request creation of an “extract” file, and then down load all transmittal data submitted by all participating jurisdictions via EDI X12 TS 826. Accept and process electronic filing of & payment for IFTA quarterly tax returns Example 5: VISTA/TS, Web Browser/WebCAT, CVIEW NOTE: Functional acknowledgment for all EDI messages (except TS 997) is made by responding with a TS 997. The results of processing an incoming TS 285 are reported via TS 824. Content errors in a received TS 826 and 150 are noted by replying with a TS 824. Content errors in a TS 813 are replied with a TS 151.

  13. L S I L S I L M L M Treasury or Revenue CAPRI L S I L S I L S I L S I L S I L M L M L M L M L M OS/OW IFTA Registration IRP HazMat SAFETYNET L S I L S I L S I L M L M L M Driver Licensing Titling SSRS L S I L M Intrastate Veh Registration L M Screening Sensor/ Driver Comm L M L M L M IFTA Tax Processing Roadside Operations ASPEN L S I L M Citation & Accident Accept and process electronic filing of & payment for IFTA quarterly tax returns Example 5: VISTA/TS, Web Browser/WebCAT, CVIEW Generic State Commercial Vehicle Administration Systems VISTA/TS 4 1 CH Access CVISN Core Infrastructure Systems (National/Regional) Service Providers E Credentialing Interface (CI) 8 Carrier Systems 2 E-Screening Enrollment Credentialing System (e.g., CAT) CDLIS 7 IRP Clearinghouse D Internet Tools 3 IFTA Clearinghouse ASAP MCDC A Web CAT 6 5 NMVTIS Other Carrier Systems RSPA HazMat CV Info Exchange Window (CVIEW) MCMIS B SAFER E Generic State Roadside Systems Licensing & Insurance Carrier Commercial Vehicle C ASAP Analysis Admin/CAPRI Transponder Other Jurisdictions

  14. This page intentionally blank.

More Related