Date post: | 07-Apr-2018 |
Category: |
Documents |
Upload: | erik-philippe |
View: | 230 times |
Download: | 0 times |
of 16
8/4/2019 Cred Admin AppB Op Scen R05
1/16
CVISN Guide to Credentials Administration: Appendix C
Operational Scenarios and Functional Thread Diagrams
C - 1
Operational Scenarios and FunctionalThread Diagrams
An operational scenario is a description of how a state intends that theircustomers and the state, or the state and core infrastructure systems shouldinteract 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 differentiatebetween different time schedules, numbers are used to show the interaction
between the applicant and the state, and the states update of snapshots. Thoseinteractions occur as soon as possible after the initial application is received bythe state. Letters are used to show the states connections to the clearinghouses,
since that occurs at a regular period instead of being triggered immediately by thecarriers actions.
Each operational scenario is illustrated by overlaying information onto the statesystem design template. The lines represent data flow between products, witharrows indicating the direction of flow. Each line is labeled with a number orletter. The complete set of lines constitutes a thread of activities that accomplisha function. Hence, the diagram is called a functional thread diagram.
This appendix provides examples of operational scenarios and functional threaddiagrams. They are included for reference, and as starting points for states thatplan to implement similar processes.
8/4/2019 Cred Admin AppB Op Scen R05
2/16
CVISN Guide to Credentials Administration: Appendix C
Operational Scenarios and Functional Thread Diagrams
C - 2
CVISN Level 1 Credentials AdministrationKey Operational Scenarios
Accept and process electronic IRP credential applications forsupplements (e.g., adding a vehicle to an existing account)
Example 1: VISTA/RS, PC-CAT, CVIEW
Example 2: Web Browser/Web Site, CVIEW
Accept and process electronic IRP renewal applications
Accept and process electronic IFTA credential applications forsupplements (e.g., changing the carriers address)
Accept and process electronic IFTA renewal applications
Example 3: RPC, PC-CAT, CVIEW
Example 4: Web Browser/Web Site, CVIEW
8/4/2019 Cred Admin AppB Op Scen R05
3/16
CVISN Guide to Credentials Administration: Appendix C
Operational Scenarios and Functional Thread Diagrams
C - 3
1. Carrier enters an IRP credential application via a Carrier AutomatedTransaction (CAT) system which submits it to the CredentialingInterface (CI) as an EDI X12 TS 286.
2. The CI submits a query to its state database to perform preliminarychecks as part of evaluating the application.
3. The state database reports the status, i.e., flags and condition to theCI.
4. If a satisfactory status is received, the application is sent to the IRPsystem (VISTA/RS) for processing via EDI X12 TS 286.
5. The IRP system processes the application and sends an invoice noticeto 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 informationto the CI via EDI X12 TS 286.
8. If a Temporary Authority (TA) is requested, the CI releases it to theCAT via EDI X12 TS 286.
9. If a TA was granted, the CI sends a vehicle snapshot segment updateto 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 TS285.
12. SAFER sends updated snapshot data to subscribers via EDI X12 TS285.
13. The CI verifies payment method information (financial systeminterfaces are not shown)and passes payment approval to the IRPsystem via EDI X12 TS 286.
14. The IRP system validates payment amount and updates applicationstatus to indicate the permanent credential granted and notifies the CIvia EDI X12 TS 286.
15. The CI passes the permanent credential to the CAT via EDI X12 TS286. Cab Cards may be printed in the carriers office or state office.
16. The CI updates CVIEW with permanent credential information via EDIX12 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 EDIX12 TS 285.
A. Periodically (daily), the IRP system sends updates to the IRPClearinghouse 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 approvaland/or correction. Today, the states review the information interactivelyusing terminals.
C. The IRP Office and also other participating jurisdictions report back tothe IRP Clearinghouse the approvals or corrections. Today, theapprovals/corrections are made via terminals.
D. The IRP Clearinghouse performs the actual netting and makes availablecorrected/approved vehicle and fee actions (post-netting transmittal) andnetting results (remittance netting reports) to the participating
jurisdictions. Today, the information is reviewed via terminals.
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 arenoted by also replying with a TS 286. The results of processing an incoming TS 285 are reported via TS 824.
Accept and process electronic IRP credential applications for supplementsExample 1: VISTA/RS, PC-CAT, CVIEW
8/4/2019 Cred Admin AppB Op Scen R05
4/16
CVISN Guide to Credentials Administration: Appendix C
Operational Scenarios and Functional Thread Diagrams
C - 4
Generic State Roadside Systems
Generic State Commercial Vehicle Administration Systems
Carrier Systems
Credentialing
System
(e.g., CAT)
CVISNCore Infrastructure
Systems(National/Regional)
CDLIS
IRP
Clearinghouse
IFTAClearinghouse
NMVTIS
MCMIS
SAFER
IFTA
Registration
L
S
I
L
M
ComplianceReview
(e.g., CAPRI)
Sensor/
Driver Comm
ScreeningL
M
Roadside
Operations
L
S
I
L
M
Inspections(e.g., ASPEN,
ISS-2, PIQ)
L
MCitation &
Accident
L
S
I
L
M
Service Providers
Internet Tools
(e.g. Browser)
Other Carrier
Systems
CV Info Exchange
Window (CVIEW)
Credentialing
Interface (CI)
Transponder
Carrier CommercialVehicle
IFTA Tax
Processing
L
S
I
L
M
Web Site
Intrastate Veh
Registration
L
S
I
L
M
Driver
Licensing
L
S
I
L
M
Licensing &
Insurance
E-Screening
Enrollment
TitlingL
S
I
L
M
SSRSL
S
I
L
M
IRPL
M
HazMatL
S
I
L
M
OS/OWLS
I
L
M
SAFETYNETL
S
I
L
M
ComplianceReview
(e.g., CAPRI)
L
S
I
L
M
Treasury orRevenue
LS
I
L
M
1
15
8
6
7
VISTA/RS IRP Office
State DatabaseL
S
I
L
M
Other Jurisdictions
5
4
13
14
2, 3
9, 16
A
B
C
D
BCD
12,19
11, 18
Accept and process electronic IRP credential applications for supplementsExample 1: VISTA/RS, PC-CAT, CVIEW
10, 17
8/4/2019 Cred Admin AppB Op Scen R05
5/16
CVISN Guide to Credentials Administration: Appendix C
Operational Scenarios and Functional Thread Diagrams
C - 5
1. Carrier enters an IRP credential application via a Web browserto a state-based Web Site.
2. The Web Site passes it to the Credentialing Interface (CI).
3. The CI submits a query to its state database to performpreliminary checks as part of evaluating the application.
4. The state database reports the status, i.e., flags and condition tothe CI.
5. If a satisfactory status is received, the application is sent to theIRP system for processing via EDI X12 TS 286.
6. The IRP system processes the application and sends an invoicenotice to the CI via EDI X12 TS 286.
7. The CI sends the invoice notice to the Web Site and maintainsarchival/audit copies of all transactions.
8. The carrier retrieves the invoice notice from the state Web Siteusing a Web Browser.
9. The carrier reviews the invoice data and verifies that theapplication data matches the intent. The carrier indicatespayment method information via the Web Browser to the WebSite.
10. The Web Site passes it to the Credentialing Interface (CI).11. If a Temporary Authority (TA) is requested, the CI releases it to
the Web Site.
12. The carrier prints the TA from the Web Site.
13. If a TA was granted, the CI sends a vehicle snapshot segmentupdate to CVIEW via EDI X12 285.
14. CVIEW sends updated snapshot data to SAFER via EDI X12 TS285.
15. CVIEW sends updated snapshot data to Roadside via EDI X12
TS 285.
16. SAFER sends updated snapshot data to subscribers via EDI X12TS 285.
17. The CI verifies payment method information (financial systeminterfaces are not shown)and passes payment approval to theIRP system via EDI X12 TS 286.
18. The IRP system validates payment amount and updatesapplication status to indicate the permanent credential granted
and notifies the CI via EDI X12 TS 286.19. The CI passes the permanent credential to the Web Site via EDI
X12 TS 286.
20. The carrier prints the Cab Cards from the Web Site.
21. The CI updates CVIEW with permanent credential information viaEDI X12 TS 285.
22. CVIEW sends updated snapshot data to SAFER via EDI X12285.
23. CVIEW sends updated snapshot data to Roadside via EDI X12285.
24. SAFER makes updated snapshot data available to subscribersvia EDI X12 TS 285.
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 arenoted by also replying with a TS 286. The results of processing an incoming TS 285 are reported via TS 824.
Accept and process electronic IRP credential applications for supplementsExample 2: Web Browser/Web Site, CVIEW (1 of 2)
8/4/2019 Cred Admin AppB Op Scen R05
6/16
CVISN Guide to Credentials Administration: Appendix C
Operational Scenarios and Functional Thread Diagrams
C - 6
A. Periodically (daily), the IRP system sends updates to the IRPClearinghouse on IRP registration information and fee payments(recaps).
B. Monthly, the IRP Clearinghouse makes available the feeinformation (pre-netting transmittals) to the participatingjurisdictions for approval and/or correction. Today, the statesreview the information interactively using terminals.
C. The IRP Office and also other participating jurisdictions reportback to the IRP Clearinghouse the approvals or corrections.Today, the approvals/corrections are made via terminals.
D. The IRP Clearinghouse performs the actual netting and makesavailable corrected/approved vehicle and fee actions (post-
netting transmittal) and netting results (remittance nettingreports) to the participating jurisdictions. Today, the informationis reviewed via terminals.
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 arenoted by also replying with a TS 286. The results of processing an incoming TS 285 are reported via TS 824.
Accept and process electronic IRP credential applications for supplementsExample 2: VISTA/RS, Web Browser/Web Site, CVIEW (2 of 2)
8/4/2019 Cred Admin AppB Op Scen R05
7/16
CVISN Guide to Credentials Administration: Appendix C
Operational Scenarios and Functional Thread Diagrams
C - 7
Generic State Roadside Systems
Generic State Commercial Vehicle Administration Systems
Carrier Systems
Credentialing
System
(e.g., CAT)
CVISNCore Infrastructure
Systems(National/Regional)
CDLIS
IRP
Clearinghouse
IFTAClearinghouse
NMVTIS
MCMIS
SAFER
IFTA
Registration
L
S
I
L
M
ComplianceReview
(e.g., CAPRI)
Sensor/
Driver Comm
ScreeningL
M
Roadside
Operations
L
S
I
L
M
Inspections(e.g., ASPEN,
ISS-2, PIQ)
L
MCitation &
Accident
L
S
I
L
M
Service Providers
Internet Tools
(e.g. Browser)
Other Carrier
Systems
CV Info Exchange
Window (CVIEW)
Credentialing
Interface (CI)
Transponder
Carrier CommercialVehicle
IFTA Tax
Processing
L
S
I
L
M
Web Site
Intrastate Veh
Registration
L
S
I
L
M
Driver
Licensing
L
S
I
L
M
Licensing &
Insurance
E-Screening
Enrollment
TitlingL
S
I
L
M
SSRSL
S
I
L
M
IRPL
M
HazMatL
S
I
L
M
OS/OWLS
I
L
M
SAFETYNETL
S
I
L
M
ComplianceReview
(e.g., CAPRI)
L
S
I
L
M
Treasury orRevenue
LS
I
L
M
1, 9
8, 12, 20
IRP Office
State DatabaseL
S
I
L
M
Other Jurisdictions
6,18
5, 17
7, 11,19
3,4 13, 21
A
B
C
D
BCD
16,24
15, 23
Accept and process electronic IRP credential applications for supplementsExample 2: VISTA/RS, Web Browser/Web Site, CVIEW
14, 22
2, 10
8/4/2019 Cred Admin AppB Op Scen R05
8/16
CVISN Guide to Credentials Administration: Appendix C
Operational Scenarios and Functional Thread Diagrams
C - 8
1. The IFTA Registration System sends a registrationrenewal 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 aCarrier Automated Transaction (CAT) system, and sendsit to the Credentialing Interface (CI) via EDI X12 TS 286.The carrier pays for the application (through EFT, creditcard, debit card,)
4. The CI checks the carriers status (delinquent, nonpayment etc.) with the IFTA Registration System and
IFTA Clearinghouse via Regional Processing Center(RPC).
5. The CI sends the application to the IFTA RegistrationSystem via EDI X12 TS 286.
6. Once the application is processed by the IFTARegistration System, a message is returned to the CI viaEDI X12 TS 286.If processing was completed
successfully, credential information is returned. Ifproblems were found, an error message is returned.
7. The IFTA Registration System also proactively updatesthe CI whenever the carriers status changes, (e.g., from
Active to Inactive, Active to Revoked).
8. The CI sends a return message to the CAT via EDI X12TS 286.
A. Periodically (no more than daily), the IFTARegistration System creates a file reflecting IFTA
credential renewals, additions, and changes. Theinformation is sent to RPC in RPC proprietary format.
B. Daily, RPC updates new or changed IFTA credentialinformation (Demographic) and sends it to the IFTAClearinghouse, for all client jurisdictions, via EDI X12TS 286.
C. The IFTA Clearinghouse database is updated withregistration information (Demographic) received fromparticipating jurisdictions. Jurisdictions can query the
IFTA database using reporting tools. Jurisdictionsmay be able to download an extract file containing
all demographic data submitted by participatingjurisdictions in EDI X12 TS 286 format.
D. Nightly, the CI generates a new or modified carriersnapshot IFTA segment and sends it to CVIEW viaTS 285.
E. CVIEW updates the carrier snapshot with IFTAcredential data and forwards it to subscribers,
including SAFER and the State roadside sites via EDIX12 TS 285.
F. SAFER updates (or creates) a carrier snapshot withIFTA credential data and forwards it to subscribers viaEDI X12 TS 285.
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.
Accept and process electronic IFTA renewal applicationsExample 3: RPC, PC-CAT, CVIEW
8/4/2019 Cred Admin AppB Op Scen R05
9/16
CVISN Guide to Credentials Administration: Appendix C
Operational Scenarios and Functional Thread Diagrams
C - 9
Generic State Roadside Systems
Generic State Commercial Vehicle Administration Systems
Carrier Systems
Credentialing
System
(e.g., CAT)
CVISNCore Infrastructure
Systems(National/Regional)
CDLIS
IRP
Clearinghouse
IFTAClearinghouse
NMVTIS
MCMIS
SAFER
IFTA
Registration
L
M
ComplianceReview
(e.g., CAPRI)
Sensor/
Driver Comm
ScreeningL
M
Roadside
Operations
L
S
I
L
M
Inspections(e.g., ASPEN,
ISS-2, PIQ)
L
MCitation &
Accident
L
S
I
L
M
Service Providers
Internet Tools
(e.g. Browser)
Other Carrier
Systems
CV Info Exchange
Window (CVIEW)
Credentialing
Interface (CI)
Transponder
Carrier CommercialVehicle
IFTA Tax
ProcessingL
M
Web Site
Intrastate Veh
Registration
L
S
I
L
M
Driver
Licensing
L
S
I
L
M
Licensing &
Insurance
E-Screening
Enrollment
TitlingL
S
I
L
M
SSRSL
S
I
L
M
IRPL
S
I
L
M
HazMatL
S
I
L
M
OS/OWLS
I
L
M
SAFETYNETL
S
I
L
M
ComplianceReview
(e.g., CAPRI)
L
S
I
L
M
Treasury orRevenue
LS
I
L
M
CH Access
RPC
Other Jurisdictions
2
3
8
6, 7
5
4
1
A
C
4
C
B
E
D
F
C
Accept and process electronic IFTA renewal applicationsExample 3: RPC, PC-CAT, CVIEW
8/4/2019 Cred Admin AppB Op Scen R05
10/16CVISN Guide to Credentials Administration: Appendix C
Operational Scenarios and Functional Thread Diagrams
C - 10
1. Carrier enters an IFTA registration application via a WebBrowser to a state-provided Web Site. The carrier pays
for the application (through EFT, credit card, debitcard,).
2. The Web Site passes it to the Credentialing Interface (CI)via EDI X12 TS 286.
3. The CI sends the application to VISTA/TS via EDI X12TS 286 for processing.
Note:
The Web Site, and/or the CI validates the application data
to determine completeness, format, agreement withbusiness rules, payment status, and whether to grant ordeny the credential.
4. Once the application is processed by The IFTA System, amessage is returned to the CI via EDI X12 TS 286.
5. If processing was completed successfully, credentialinformation is returned to the Web Site via EDI X12 TS286.
6. The carrier retrieves the credential information from theWeb Site using a Web Browser.
A. Nightly, The IFTA System updates new or changedIFTA credential information (Demographic) for all and
sends it to the IFTA Clearinghouse via EDI X12 TS286.
B. The IFTA Clearinghouse database is updated withregistration information (Demographic) received fromparticipating jurisdictions. Jurisdictions can query theIFTA database using reporting tools. Jurisdictionsmay be able to download an extract file containing
all demographic data submitted by participatingjurisdictions in EDI X12 TS 286 format.
C. Nightly, The IFTA System generates a new ormodified carrier snapshot IFTA segment and sends itto CVIEW via TS 285. (Alternatively The IFTASystem could generate a new or modified carriersnapshot IFTA segment and provide it to the CI andthen CI sends it to CVIEW).
D. CVIEW updates the carrier snapshot with IFTAcredential 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 viaEDI X12 TS 285.
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.
Accept and process electronic IFTA renewal applicationsExample 4: Web Browser/Web Site, CVIEW
8/4/2019 Cred Admin AppB Op Scen R05
11/16CVISN Guide to Credentials Administration: Appendix C
Operational Scenarios and Functional Thread Diagrams
C - 11
Generic State Roadside Systems
Generic State Commercial Vehicle Administration Systems
Carrier Systems
Credentialing
System
(e.g., CAT)
CVISNCore Infrastructure
Systems(National/Regional)
CDLIS
IRP
Clearinghouse
IFTAClearinghouse
NMVTIS
MCMIS
SAFER
IFTA
Registration
L
M
ComplianceReview
(e.g., CAPRI)
Sensor/
Driver Comm
ScreeningL
M
Roadside
Operations
L
S
I
L
M
Inspections(e.g., ASPEN,
ISS-2, PIQ)
L
MCitation &
Accident
L
S
I
L
M
Service Providers
Internet Tools
(e.g. Browser)
Other Carrier
Systems
CV Info Exchange
Window (CVIEW)
Credentialing
Interface (CI)
Transponder
Carrier CommercialVehicle
IFTA Tax
Processing
L
S
I
L
M
Web Site
Intrastate Veh
Registration
L
S
I
L
M
Driver
Licensing
L
S
I
L
M
Licensing &
Insurance
E-Screening
Enrollment
TitlingL
S
I
L
M
SSRSL
S
I
L
M
IRPL
S
I
L
M
HazMatL
S
I
L
M
OS/OWLS
I
L
M
SAFETYNETL
S
I
L
M
ComplianceReview
(e.g., CAPRI)
L
S
I
L
M
Treasury orRevenue
LS
I
L
M
CH Access
4
3
1
6
2
5
Other Jurisdictions
A
B
D
B
E
Accept and process electronic IFTA renewal applicationsExample 4: VISTA/TS, Web Browser/Web Site, CVIEW
C
8/4/2019 Cred Admin AppB Op Scen R05
12/16CVISN Guide to Credentials Administration: Appendix C
Operational Scenarios and Functional Thread Diagrams
C - 12
NOTE: The Regional Processing Center (RPC) retrieves taxrate 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 CarrierAutomated Transaction (CAT) via EDI X12 TS 813.
2. The carrier queries the CI for appropriate tax rate matricesusing the CAT via EDI X12 TS 150.
3. Daily, RPC sends the CI any credits available to thecarrier.
4. The CI sends the CAT the appropriate tax matrices andany credits due the carrier via EDI X12 TS 150 and 813respectively.
5. The carrier enters IFTA tax filing information using theCAT and submits it to the CI via EDI X12 TS 813. Thecarrier pays the Tax Due (through EFT, credit card, debitcard,).
6. The CI verifies the correct carrier name, ID, and checksthe carriers status (Active, Inactive, Revoked, or
Suspended) with the IFTA Registration System.
7. The IFTA Registration System also proactively updatesthe CI whenever the carriers status changes, (e.g., from
Active to Inactive).
A. Nightly, the CI forwards the carriers tax filings andstatus to RPC in RPC proprietary format.
B. The tax filings are checked for format and correctcalculations when received from the CI. A nettingfunction is performed on a monthly basis prior totransmittal to the IFTA CH. RPC clients placepayments in accounts according to the netting results.
Monthly, RPC sends a transmittal summary to theIFTA Clearinghouse via EDI X12 TS 826.
C. The IFTA Clearinghouse database is updated withtransmittal tax filing information (transmittal) received
from participating jurisdictions. Jurisdictions canquery the IFTA database using reporting tools.Jurisdictions may be able to download an extract file
containing all transmittal data submitted byparticipating jurisdictions in EDI X12 TS 826 format.
D. Nightly, the CI generates a new or modified carriersnapshot IFTA segment and sends it to CVIEW viaTS 285.
E. CVIEW sends the updated snapshot IFTA segments
to SAFER and the State Roadside via EDI X12 TS285.
F. SAFER updates the snapshots with IFTA data andprovides them to subscribers and other jurisdictionsvia EDI X12 TS 285.
NOTE: Functional acknowledgment for all EDI messages (except TS 997) is made by responding with a TS 997. The results of processing anincoming 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.
Accept and process electronic filing of & payment for IFTA quarterly tax returnsExample 5: RPC, PC-CAT, CVIEW
8/4/2019 Cred Admin AppB Op Scen R05
13/16CVISN Guide to Credentials Administration: Appendix C
Operational Scenarios and Functional Thread Diagrams
C - 13
Generic State Roadside Systems
Generic State Commercial Vehicle Administration Systems
Carrier Systems
Credentialing
System
(e.g., CAT)
CVISNCore Infrastructure
Systems(National/Regional)
CDLIS
IRP
Clearinghouse
IFTAClearinghouse
NMVTIS
MCMIS
SAFER
IFTA
Registration
L
M
ComplianceReview
(e.g., CAPRI)
Sensor/
Driver Comm
ScreeningL
M
Roadside
Operations
L
S
I
L
M
Inspections(e.g., ASPEN,
ISS-2, PIQ)
L
MCitation &
Accident
L
S
I
L
M
Service Providers
Internet Tools
(e.g. Browser)
Other Carrier
Systems
CV Info Exchange
Window (CVIEW)
Credentialing
Interface (CI)
Transponder
Carrier CommercialVehicle
IFTA Tax
ProcessingL
M
Web Site
Intrastate Veh
Registration
L
S
I
L
M
Driver
Licensing
L
S
I
L
M
Licensing &
Insurance
E-Screening
Enrollment
TitlingL
S
I
L
M
SSRSL
S
I
L
M
IRPL
S
I
L
M
HazMatL
S
I
L
M
OS/OWLS
I
L
M
SAFETYNETL
S
I
L
M
ComplianceReview
(e.g., CAPRI)
L
S
I
L
M
Treasury orRevenue
LS
I
L
M
1
2
4
5
A 3
6, 7
CH Access
RPC
Other Jurisdictions
C
C
B
F
E
D
C
Accept and process electronic filing of & payment for IFTA quarterly tax returnsExample 5: RPC, PC-CAT, CVIEW
8/4/2019 Cred Admin AppB Op Scen R05
14/16CVISN Guide to Credentials Administration: Appendix C
Operational Scenarios and Functional Thread Diagrams
C - 14
1. The IFTA System generates a tax filing notification foreach carrier registered under IFTA and sends it to theCredentialing Interface (CI) via EDI X12 TS 813.
2. The CI sends the notifications to the Web Site via EDI X12TS 813.
3. The carriers retrieve the notification from the Web Siteusing a Web Browser.
4. The IFTA System sends the appropriate Tax Rates to theCI via EDI X12 TS 150.
5. The CI forwards the Tax Rates to the Web Site via EDI
X12 TS 150.6. The carriers enter IFTA tax filing information to the Web
Site using a Web Browser. The carrier pays the Tax Due(through EFT, credit card, debit card.).
7. The Web Site performs calculations using tax rates andsends the IFTA tax filing information to the CI via EDI X12TS 813.
Note: The Web Site and/or the CI validate the tax filing data todetermine completeness, format, and agreement withbusiness rules.
8. The CI receives the transaction and sends the tax filing toVISTA/TS via EDI X12 TS 813 for processing.
Note: The IFTA System validates and tracks tax filing data todetermine payment status.
A Nightly, The IFTA System evaluates and updates taxfiling (Demographic, including Tax Payer Type andStatus - Active, Inactive, Revoked, or Suspended),information for all client jurisdictions, and sends it tothe IFTA Clearinghouse via EDI X12 TS 826. TheIFTA System also generates updated snapshot IFTAsegments and provides them to CVIEW via EDI X12TS 285. (Alternatively, The IFTA System may providesnapshot IFTA segment updates to the CI fortransmittal to CVIEW).
B. CVIEW sends the updated snapshot IFTA segmentsto SAFER and the State Roadside via EDI X12 TS285.
C. SAFER updates the snapshots with IFTA data andprovides them to subscribers and other jurisdictionsvia EDI X12 TS 285.
D. Monthly, The IFTA System updates tax filing(transmittal) information for all client jurisdictions andsends it to the IFTA Clearinghouse via EDI X12 TS826.
E. The IFTA Clearinghouse database is updated withtransmittal tax filing information (transmittal) receivedfrom participating jurisdictions. Jurisdictions can querythe IFTA database using reporting tools. Jurisdictionsmay be able to download an extract file containing
all transmittal data submitted by participatingjurisdictions in EDI X12 TS 826 format.
Accept and process electronic filing of & payment for IFTA quarterly tax returnsExample 6: Web Browser/Web Site, CVIEW
NOTE: Functional acknowledgment for all EDI messages (except TS 997) is made by responding with a TS 997. The results of processing anincoming 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.
8/4/2019 Cred Admin AppB Op Scen R05
15/16CVISN Guide to Credentials Administration: Appendix C
Operational Scenarios and Functional Thread Diagrams
C - 15
Generic State Roadside Systems
Generic State Commercial Vehicle Administration Systems
Carrier Systems
Credentialing
System
(e.g., CAT)
CVISNCore Infrastructure
Systems(National/Regional)
CDLIS
IRP
Clearinghouse
IFTAClearinghouse
NMVTIS
MCMIS
SAFER
IFTA
Registration
L
S
I
L
M
ComplianceReview
(e.g., CAPRI)
Sensor/
Driver Comm
ScreeningL
M
Roadside
Operations
L
S
I
L
M
Inspections(e.g., ASPEN,
ISS-2, PIQ)
L
MCitation &
Accident
L
S
I
L
M
Service Providers
Internet Tools
(e.g. Browser)
Other Carrier
Systems
CV Info Exchange
Window (CVIEW)
Credentialing
Interface (CI)
Transponder
Carrier CommercialVehicle
IFTA Tax
ProcessingL
M
Web Site
Intrastate Veh
Registration
L
S
I
L
M
Driver
Licensing
L
S
I
L
M
Licensing &
Insurance
E-Screening
Enrollment
TitlingL
S
I
L
M
SSRSL
S
I
L
M
IRPL
S
I
L
M
HazMatL
S
I
L
M
OS/OWLS
I
L
M
SAFETYNETL
S
I
L
M
ComplianceReview
(e.g., CAPRI)
L
S
I
L
M
Treasury orRevenue
LS
I
L
M
CH Access
Accept and process electronic filing of & payment for IFTA quarterly tax returnsExample 6: VISTA/TS, Web Browser/Web Site, CVIEW
3
6
2 57
1
4 8
A
D
E
B
E
C
Other Jurisdictions
8/4/2019 Cred Admin AppB Op Scen R05
16/16
Operational Scenarios and Functional Thread Diagrams
This page intentionally blank.