FSD-02-06 TVL LVL Processing v1.0

TVL and LVL Processing
Functional Specification Document

Version Number 1.0
FSD-02-06
TollPlus, LLC
November 8, 2018
Functional Specification Document (FSD-02-06)
Version History
Version No. Date Changed By Description
1.0 11/08/2018 Jagadish Lingam Initial Submission
TollPlus Confidential Page of Version 0.6 – 11/08/2018

Table of Contents
1 INTRODUCTION....................................................................................................................................... 5
1.1 BUSINESS OBJECTIVE................................................................................................................................................5
1.2 SCOPE....................................................................................................................................................................5
1.3 REQUIREMENTS.......................................................................................................................................................6
1.4 RELATED REQUIREMENTS..........................................................................................................................................6
1.5 PARKED REQUIREMENTS...........................................................................................................................................6
1.6 PROJECT REQUIREMENTS...........................................................................................................................................6
1.7 TVL AND LVL – AVAILABLE REFERENCES.....................................................................................................................8
2 SYSTEM OVERVIEW................................................................................................................................. 9
3 FUNCTIONAL REQUIREMENTS................................................................................................................ 12
3.1 UC-02-06-01: AUTOMATIC STATUS CHANGE OF TRANSPONDERS AND LICENSE PLATES....................................................12
3.2 UC-02-06-02: CREATE TVL IN T-BOS AND TRANSFER TO NTTA ROADWAYS................................................................15
3.3 UC-02-06-03: CREATE TVLS IN T-BOS AND TRANSFER TO CENTRAL US IOP HUB.........................................................17
3.4 UC-02-06-04: CREATE TVL IN T-BOS AND TRANSFER TO DAL AND DFW (AIRPORT PARKING FACILITIES).........................20
3.5 UC-02-06-05: CREATE TVL IN T-BOS AND TRANSFER TO TSA SUBSCRIBER LOCATIONS..................................................25
3.6 UC-02-06-06: RECEIVE TVL FROM CENTRAL HUB FOR CENTRAL REGIONAL AGENCIES.....................................................28
3.7 UC-02-06-06_1: RECEIVE TVL FROM CENTRAL HUB FOR SOUTHEASTERN STATE AGENCIES..............................................30
3.8 UC-02-06-06_2: RECEIVE TVL FROM CENTRAL HUB FOR NATIONAL INTEROPERABILITY..................................................33
3.9 UC-02-06-07: CONVERT AND TRANSFER TVLS TO NTTA/TSA ROADWAYS AS RECEIVED FROM CENTRAL HUB...................35
3.10 UC-02-06-08: CREATE LVL IN T-BOS AND TRANSFER TO CENTRAL US HUB FOR CENTRAL REGIONAL AND IOP AGENCIES....38
3.11 UC-02-06-09: RECEIVE LVL FROM CENTRAL US HUB................................................................................................40
4 INTERFACE SPECIFICATIONS................................................................................................................... 42
APPENDIX A: REQUIREMENTS TRACEABILITY..................................................................................................43

List of Figures
Figure 1: TVL and LVL Process..........................................................................................................................................11

1 Introduction
1.1 Business Objective
The objective of this FSD is to document details around the requirements related to:
1. TVL and LVL: Generation from T-BOS and transmitting it to other systems like NTTA lanes, TSA
roadways, Airport parking facilities (DAL, DFW) and Interoperable partners.
2. Process incoming TVL and LVL from other partners and transmit to NTTA lanes and TSA
roadways.
This FSD goal is to document the requirements and business rules for the TVL and LVL generation and
processing in T-BOS.
1.2 Scope
This document provides details for TVL and LVL generation, transfer, receive and processing of TVLs and
LVLs within T-BOS. This include
1. Status change of the transponders and license plates on an account in certain conditions and its
reflection in the TVL and LVL
2. Generation of TVLs and LVLs in T-BOS and sending them out to:
a. NTTA roadways
b. Central HUB (for regional partners)
c. Southeast HUB (through Central HUB for southeastern state agencies)
d. National HUB (through Central Hub)
e. Airport Parking Facilities (DAL/DFW)
f. TSA Subscribers
Also Receiving the acknowledgements from the respective recipients, where needed.
LVL s are created and sent only to IOP through central Hub.
(Assumed LVLs are not sent to NTTA lanes & TSAs)
3. Receive and processing of incoming TVLs and LVLs from interoperable, regional partners and
sending to NTTA and TSA roadways:
a. From regional partners (received via Central HUB)
b. From south eastern states (received via Central HUB, Southeast HUB)
c. For national interoperability (received via Central HUB)
Also Sending the acknowledgements to the respective initiators.

(Assumed IOP LVLs are not sent to NTTA lanes & TSAs)
1.3 Requirements
The following section of Functional Requirements and related Business Rules are included in this
document. Also, please refer to the TollPlus Standards Document (FSD-18-08) for additional validations
and details.
MODULE FUNCTIONAL AREA

2 – Transaction Processing 2.5 TAG AND LICENSE PLATE VALIDATION LISTS
1.4 Related Requirements

The following scenarios or use cases are not included in this document and will be included in separate
Functional Specification Documents (FSDs).
 General Account Management
 Account Preferences
 Vehicles, License Plates and Transponder Management
 Transactions Processing
1.5 Parked Requirements

The following requirements are included in the referenced sections above and are recommended or
agreed to be Parked. These requirements are not included in the use cases to follow.
Requirement # Description Reason

TXN-REQ-197 The BOS shall provide the TVLs, and LVLs, to the TSA NTTA recommends
Subscriber Roadways, at Configurable times of day parking LVLs to the
(LVL part is parked) TSAs for TXN-REQ-197
(TVLs will continue to
be sent)
1.6 Project Requirements
1.5.1 Functional Specification Document (FSD) Covered?

PROJ-REQ-101 The VSI shall develop and submit an FSD to NTTA for Yes
review and Approval. The FSD shall describe the
detailed functional BOS Design, which describes how
the Contract Requirements (using the RTM) and
Business Rules will be met in the BOS.
PROJ-REQ-102 The FSD shall define functions of the VSI’s system, or Yes
its component, with a set of inputs, behavior, and
outputs.
PROJ-REQ-103 The FSD shall include system and user interface screen Yes

1.5.1 Functional Specification Document (FSD) Covered?

diagrams, reports, figures and tables, and contain the
following; including, but not limited to:
PROJ-REQ-103.1  overall business objective and high-level Yes
Requirements;
PROJ-REQ-103.2  system overview that shows the overview of the Yes
system components and how they align with the
high-level Requirements and business objectives;
PROJ-REQ-103.3  high-level conceptual Design, such as a diagram of Yes
the system components affected, including any
data flows between the applications;
PROJ-REQ-103.4  common system behavior including navigation Not applicable
controls, menu structures and access to help that
impact certain BOS function, or all BOS functions;
PROJ-REQ-103.5  details of system changes required clearly No; will be addressed in
indicating existing functionality, configured or SDD
customized;
PROJ-REQ-103.6  detailed Use Cases that show the behavior of the Yes
system with data flows;
PROJ-REQ-103.7  detailed user Process Maps/Flows with any Yes
alternate paths;
PROJ-REQ-103.8  user interface screens, including screen mockup, Not applicable
reports, screen controls, user actions and
application behavior;
PROJ-REQ-103.9  Interface specification, including purpose, whether Yes
it’s new or existing, sender, receiver, frequency and
format;
PROJ-REQ-103.10  non-functional Requirements and how they will be Partial; Audit Control is
delivered. Examples include: performance, audit addressed
control, security configuration, message catalog,
and;
PROJ-REQ-103.11  high-level test conditions, including description. No; will be covered in
Test Plan

1.7 TVL and LVL – Available References
TVL
Roadways ICD Business Rules
NTTA • ICD007 External FS Lane X
Transaction Interface Rev
1_21
• ICD008 External AVI
Status Update Interface
Rev 1_4
Central US IOP SSIOP ICD VERSION 1 20 SSIOP Business Rules
FINAL RELEASED VERSION 2 7 FINAL
20170213 RELEASED 20160630
Sec 3 CLEAN
Sec 2.1.5
National IOP SSIOP ICD VERSION 1 20 SSIOP Business Rules
Hub FINAL RELEASED VERSION 2 7 FINAL
20170213 RELEASED 20160630
Sec 3 CLEAN
Sec 2.1.5
Airports - DAL •INTEROP-ICD-02 AVI Tag NTTA Business Rules-
& DFW Status_20170117_DAL_SK v2018.1 BASELINE -
IDATA_Integration DESIGN ANALYSIS
(Provided 20180921)
Business Rules
Sec 12.1
TSA Service Provider ICD V1.19 •TSP-ICD-Business
Subscribers CLEAN DISTRIBUTED Rules
20161019 LBJNTE12NTE3A3B
Sec 4&5 FINAL DRAFT v3.8
FINAL
Sec 4.1 & 5.1
•TxDOT NTTA DFW
Region Business Rules
- FINAL DRAFT V 2.1
20160915
Sec 4.1 & 5.1
LVL
Roadways ICD Business Rules
NTTA NA NA
Central US INTEROPERABLE-ICD-05- X
IOP LVL_v1_FINAL
Airports - DAL NA NA

& DFW
TSA Service Provider ICD V1.19 •TSP-ICD-Business
Subscribers CLEAN DISTRIBUTED Rules
20161019 LBJNTE12NTE3A3B
Sec 4.1.1.2 &5.2 FINAL DRAFT v3.8
FINAL
Sec 4.2 & 5.2
•TxDOT NTTA DFW
Region Business Rules
- FINAL DRAFT V 2.1
20160915
Sec 4.2 & 5.2

2 System Overview
Transponders/tags are issued to new customers when they sign up with NTTA or existing customer
when they request for additional tags. To these accounts or tags, license plate details are also
associated. Both tag and license plate details along with account balance available on the customer
account within T-BOS makes up for the ingredient of the TVL and LVL.
TVL and LVL
 TVL and LVL are list of tags and license plates along with their respective status that are
registered on customer accounts within the NTTA T-BOS system. They have status indicators
from a combination of tag status, account status, license plate effective dates etc. that defines if
a tag or license plate is good for use in the lane. Each tolling back office system generates such
files on a periodic basis to be supplied to the lanes, other facilities like airports and
interoperable partners for operational purposes. Customers can also add non-NTTA
transponders to their NTTA Tolltag account
 The TVL which also have associated license plate(s) information (if any) will be generated and
sent to the lanes, and the Interoperable partners via Hubs, on the schedule determined.
 The TVL & LVL will be sent across locations and partners either as bulk /differential files or as
full / incremental files (differential file - which carries any updates/ change in the tag status or
license plate details then the last bulk file was sent)
T-BOS Tag Status
When the tags are issued to the customer, they are marked as ACTIVE in T-BOS.
*Inclusion of the tags (based on the tag status and account balance) in the TVL will follow the
specifications as mentioned in the respective use cases
Various other status that a tag can go through in T-BOS during the entire life span are:
 Assigned
 Inventory
Retailer
 Expired
 TagInacti
ve
 Lost
 Stolen
 Returned
 Missing
 Replaced
 Destroye
dDisposal
 Destroye
dObsolet

e
 Returned
Damaged
 ShippedD
efective
 ShippedD
amaged
 VendorR
eturn
 Shipped
 Returned
Defective
 Returned
Good
 Inventory
Recycled
The tag status can be changed in T-BOS to appropriate status depending upon situations (explained
clearly in Use Case # UC-02-06-09) by:
1. Automatic by T-BOS: Tag status changed to expired, replaced, inactive depending upon other
business scenario (refer to account management FSD)
2. Manual by an authorized user: Customer reporting tag as lost/stolen/damaged and authorized
user doing it
3. Customer from Internet Portal: Customer reporting tag as lost/stolen/damaged
Tag Status in TVL – Inclusion of tag in a specific TVL and the corresponding status is done based by
taking below attributes in to consideration:
1. Customer account status, account balance, T-BOS tag status
2. Account attributes and flags (fleet, replenishment method, IOP, Airport Parking)
3. Area/region the tag serves (like tags on non-revenue accounts are non-revenue only for NTTA
lanes only)
Based on the above listed attributes, tags from T-BOS are indicated with one of the status based on the
respective interface specification in the TVL that is generated
TVL & LVL File main attributes – Detail record (May change based upon the agency)
TVL File
Tag Tag Serial Number Tag Status Tag Class Revenue Type Submitted
Agenc Date/Time
y ID

LVL File
Tag License Plate License Revenue Vehicle LVL Home

Status State Plate Type Classification Authority

Number

Figure 1: TVL and LVL Process

3 Functional Requirements
3.1 UC-02-06-01: Automatic status change of Transponders and
License Plates
Scope
Any change in the status of tag, license plate, replenishment type or account balance within T-BOS gets
reflected in the next TVL and LVL generated. T-BOS account management has specific triggers that
pushes these updates to queue from where TVL and LVL generation takes the input.
Process Details
Whenever there is a change in any of the attributes/flags/balances on the account, the same is reflected
in the TVL and LVL and the status will be changed accordingly.
Use Case Number UC-02-06-01

Use Case Summary The transponders and license plate status will be driven by the
customer account attributes and other changes happening within T-
BOS. Whenever there is a change in those attributes/flags/balances on
the account, the same is reflected in the TVL and LVL generated next.
The BOS shall automatically change the status of transponders and

License Plates in the TVL and LVL for the following conditions:
 Change in account attributes/flags
 Change in account balance
o Account balance is equal to or below the account’s Low
Balance Level
o Account balance goes negative
o Account balance is positive
o Account balance is greater than the low balance Level
 Account is suspended
 Account is pending closed
 Transponders are issued, transponder returned or reported lost,
stolen, transferred
 License plates are issued, returned, lost, stolen, transferred
Application T-BOS TVL and LVL Processing Engine
Actor(s) System Batch
Pre-conditions Transponders issued by NTTA having associated license plate
information, video customer having registered license plates are
available in T-BOS
Post-conditions Transponders and License Plates status as updated in T-BOS is reflected

in the next TVL and LVL generated
Step System Action Description Related

# Artifacts
1 Account attributes, flags or These are the
reasons like account differentiators/parameters/filters of
replenishment, account an account for any management
closure, account suspension purpose. For example:
1. Account Replenishment
method: For prepaid account
where automatic
replenishment method is not
available, and account
continues to get posted with
new tolls, account may soon
run out of the balance and
will reach zero balance. In
such cases, TVL and LVL would
carry and invalid status for the
transponders or license plates
associated with the account
2. Account status changes:
Customer requesting account
closure which in turn would
make the transponders or
license plate inactive which
gets reflected in the next TVL
and LVL generated
3. Account attributes like
bankruptcy, escheatment of
funds, Customer changing the
airport parking and IOP opting
options
4. Movement of prepaid
individual account to ZipCash
due to negative balance and
back when negative balance is
paid off
2 Transponder status changes Updated transponder status should
based on customer request get reflected in the next TVL
or system reasons like: generated reflecting the changes
1. Lost
2. Stolen
3. Returned

Step System Action Description Related

# Artifacts
4. Replaced
5. Expired
6. Damaged
3 Account replenishment When the account balance is changed
payments due to the payments, associated
transponder and license plate status is
also updated and sent in the next TVL
and LVL generated.
4 Updates to the license plate When the license plate details are
details on the customer updated due to:
account 1. Change in ownership
2. Customer surrendering
license plate
3. Rental/leased cars
4. Addition, removal of license
plates to the customer
accounts
Requirements, Business Rules Covered:
Reference Description
TXN-REQ-198 The BOS shall automatically change the status of transponders and License
Plates, on an Account, for the following conditions; including, but not limited
to
TXN-REQ-198.1  Account Attributes
TXN-REQ-198.2  Account Flags
TXN-REQ-198.3  Account balance is equal to or below the Account’s Low Balance Level
TXN-REQ-198.4  Account balance goes negative
TXN-REQ-198.5  Account balance is positive
TXN-REQ-198.6  Account balance is greater than the Low Balance Level
TXN-REQ-198.7  Account is suspended
TXN-REQ-198.8  Transponders are issued; returned, lost, stolen, transferred, and
TXN-REQ-198.9  License Plates are issued; returned, lost, stolen, transferred

3.2 UC-02-06-02: Create TVL in T-BOS and transfer to NTTA Roadways

Scope
The local TVL is created in T-BOS with all the available tags and made available to the lanes according to
the predefined schedule. These can be either a full data or an incremental batch update.
Process Details
 As of now NTTA Roadways do not accept a TVL file. Existing BOS provides the data to the lane
through a view. Any changes to this interface will be further reviewed during the design phase
 Updated tag status is made available to the lanes by T-BOS in real time through this view as and
when there is a status update
 The update can be a single tag update or full update or an incremental batch update
 The following tag statuses shall be available in the local TVL
1 – Valid – Good Standing
2 – Low Balance - account balance below rebill threshold
3 – Invalid/Negative Balance - account not in good standing & zero-balanced account
4 – Lost/Stolen/Inventory

Use Case Summary Pushing TVL data to queue following agreed interface specification and
made available to NTTA roadways on the schedule as determined by the
interface specification
Pre-conditions Tags issued by NTTA to the customers with different status are available
in T-BOS
Post-conditions TVL data is successfully created and made available to all the NTTA
roadways in the prescribed format
Step System Action Description Related Artifacts

#
1  T- BOS will make  Transfer local TVL tag  ICD007 External FS
the Tag information status updates that are Lane Transaction
available at the registered with the NTTA Interface Rev 1_21
host for the lane  Full and incremental TVL
controller to data containing the status  ICD008 External AVI
view/download for of the transponders in the Status Update
now format as agreed in the ICD Interface Rev 1_4
is generated per the
schedule mentioned in the
ICD.


#
 Contents of full and
incremental data to follow
the business rules
prescribed
 Generated data are made
available for view by the
lanes via queue as
mentioned in the ICD
T BOS Tag Status T BOS A/C BAL Matching NTTA Status

Assigned, 1- Valid
> Low Balance
InventoryRetailer
> Zero and <= Low
Balance 2- Low balance
<= Zero 3- Invalid / Negative Balance
Expired
TagInactive
Lost
Stolen
Returned
Missing
Replaced
DestroyedDisposal
DestroyedObsolet
4- Lost/Stolen/Inventory
e
ReturnedDamaged
ShippedDefective
ShippedDamaged
Shipped
ReturnedDefective
ReturnedGood
InventoryRecycled


TXN-REQ-188 The BOS shall create and transfer TVLs to the following Locations; including,
but not limited to.

TXN-REQ-188.1 Current and future NTTA Roadways, based on the Roadway ICD
3.3 UC-02-06-03: Create TVLs in T-BOS and transfer to Central US IOP

Hub
Scope
The NTTA TVLs are created in T-BOS with all the tags that are opted in for the IOP and forwarded to the
Central Hub at agreed schedule for southern IOP agencies, National IOP hub and other agencies. These
can be either bulk file or a differential batch update file.
In return T-BOS receives the acknowledgement from the Central Hub that the TVL file is received.
Process Details
 Tag Validation List (TVL) will be created by NTTA to inform the Central hub (in turn to other IOP
agencies) about the status of tags and license plates associated with a customer account in
NTTA T-BOS system
 An acknowledgement will be received by NTTA: To make the sender aware that the submission
was received in its entirety, the receiver IOP agency should send an initial acknowledgment of a
Tag Validation List (TVL) Data file, back to the SSIOP Hub which sent the TVL. Additionally, a
second Acknowledgement Data file shall be sent to provide the date/time the TVL is considered
operative by the Away SSIOP Hub and all its local Agencies. The second Acknowledgement Data
file will only be sent after an initial Acknowledgement Data file has already been delivered. In
turn received by NTTA via Central Hub for SSIOP and National IOP.
 Bulk and Differential TVLs will be sent on the schedules determined (covered under business
rules)
 The following Tag Statuses shall be available in the TVL.
 V – Valid (applies to both Bulk and Differential TVL)
 Z – Zero/Negative Balance (applies to both Bulk and Differential TVL)
 I – Invalid (only used for Differential TVL).
Use Case Summary TVL is generated in T-BOS following agreed interface specification and
transferred to Central US IOP Hub for SSIOP and National IOP on the
schedule as determined by the interface specification
Pre-conditions  Tags issued by NTTA to the customers with different status are
available in T-BOS

 Customers with transponders have opted in for interoperability

are also available in T-BOS
Post-conditions TVL file is successfully generated and electronically distributed to the
Central HUB in the agreed format

#
1 T-BOS creates and transfers  The Bulk and Differential  RFP_Consolidated_Scope-
the lists to the Central US TVL file containing the AppendixOnly-v3-CLEAN-
IOP Hub for central regional status of the 3–
agencies transponders in the  SSIOP ICD VERSION 1 20
agreed format is FINAL RELEASED
generated following the 20170213 Sec 3 - Tag
2 T-BOS creates and transfers
schedule as mentioned Validation List (TVL) Data
the lists to the Central US
in the ICD Sec 7 - Acknowledgement
IOP Hub for SSIOP & other
hubs on a scheduled  Differential updates will Data
interval/period contain all changes  SSIOP Business Rules
since the last Bulk and VERSION 2 7 FINAL
shall be used to indicate RELEASED 20160630
new tag/plate data CLEAN Sec 2.1.5
T-BOS creates and transfers and/or updates in
3  Business Rules
the lists to the National IOP tag/plate status
Hub via Central Hub on a AM-BR-46
 Contents of full and AM-BR-51
scheduled interval/period Differential file follow
the business rules
 Generated files are
transmitted to the
4 destinations as
Acknowledgement received
by NTTA from Central Hub mentioned in the ICD
 Initial and second
acknowledgement is
received via Central Hub
that the TVL is received
T BOS Tag
Status T BOS A/C BAL Matching SSIOP Hub Status
Assigned > Low Balance V- Valid (applies to both Bulk and Differential TVL)
<=Low Balance Z- Zero / negative Balance (applies to both Bulk and
Differential TVL)
Expired
TagInactive
I - Invalid (only used for Differential TVL)
Lost
Stolen

Returned
Missing
Replaced
Omitting a tag from a Bulk TVL automatically makes
the tag invalid
Business Rules:
 Accounts with a prepaid balance exceeding $0.00 (parameter) and valid Transponders will be
Interoperable
 Customers may opt-in/opt-out of interoperability use. When opted-out, their Transponder will
not be valid for use for interoperability
 The Home Agency shall document the status of its interoperable tags and license plates in the
Tag Validation List.
 The Tag Validation List shall denote the status of and associated license plate(s) for each
interoperable Tag based on the requirements and status defined in the ICD.
 Tag Validation Lists shall not contain fictitious Tags. (false tags)
 The SSIOP Hubs shall electronically exchange Bulk Tag Validation Lists on a regular schedule, at
least once per week. The Bulk Tag Validation List will have “now” valid and zero/negative
balance tags. It is up to the Home Agency as to whether the zero/negative balance tags are
included in the Bulk TVL.
 When changes occur to the Tag Validation List, Home Agencies shall create a Differential Tag
Validation List and distribute via the SSIOP Hubs. The Differential TVL contains new valid and
“now” invalid (invalid, zero/negative balance) tags compared to the last Bulk TVL. The
Differential TVLs are exchanged at least daily. It is up to the Home Agency as to whether the
zero/negative balance tags are included in the Differential TVL.
 Each Hub shall provide a utility to be used by authorized users to pull a tag’s history in the event
of a dispute or other inquiry.
TXN-REQ-188.2 The BOS shall create and transfer TVLs to Central US IOP Hub, based on the
Southern States ICD and Business Rules
TXN-REQ-188.3 The BOS shall create and transfer TVLs to National IOP Hub, based on the
National Interoperability ICD and Business Rules (Using SSIOP rules)
AM-BR-46 Accounts with a prepaid balance exceeding $0.00 (parameter) and valid
Transponders will be Interoperable.
AM-BR-51 Customers may opt-in/opt-out of interoperability use. When opted-out, their

Transponder will not be valid for use for interoperability

3.4 UC-02-06-04: Create TVL in T-BOS and transfer to DAL and DFW
(Airport Parking Facilities)
Scope
The NTTA TVLs created in T-BOS with all the tags that are opted in for the DAL and/or DFW airports
forwarded to the respective airports at scheduled interval. It can be which can be a full file or an
incremental batch update.
In return T-BOS receives the acknowledgement from the Airports that the TVL file is received
Process Details
 Periodically, T-BOS creates a tag status file for the tags owned by the Authority and transmitted
to Airport authorities. T-BOS sends tags managed by NTTA as well i.e. tags where NTTA is the
home agency. For example, customer may add a OTA tag to NTTA account to use at DAL/DFW
airports
 Tag status file requires acknowledgement from the receiving Authority. If the NTTA as
originating authority does not receive an acknowledgement after a reasonable delay, an attempt
should be made to retransmit the tag status file
 Full and Incremental TVLs will be sent on the schedules determined (covered under business
rules)
 The following Tag Statuses shall be available in the TVL
 G – Good
 B – Low Balance
 I – Invalid
 L – Lost
 N – Negative Balance
 R – Returned
 S - Stolen

Use Case Summary TVL is generated following the agreed interface specification a
transferred to Airports – DAL and DFW on the schedule as mentioned in
the ICD
available in T-BOS

 Tags managed by NTTA (NTTA as Home agency) are also

available in T-BOS
 Customers with transponders have opted in for airport parking

are also available in T-BOS
Post-conditions TVL file is successfully created and electronically distributed to the DAL
and DFW Airports in the prescribed format
Ste System Action Description Related Artifacts

p#
1 T-BOS creates and 1. The TVL file contains the  RFP_Consolidated_Scope-
transfers the lists to status of the AppendixOnly-v3-CLEAN-
the Airport Parking transponders who have 3
on a scheduled opted for the airport  INTEROP-ICD-02 AVI Tag
interval/period parking in the agreed Status_20170117_DAL_
format (per interface SKYDATA_Integration Sec
specification) 2&3
2 NTTA receives the
acknowledgement 2. “FULL” TVL= Complete  NTTA Business Rules-
from the Airports list of all owned tags. v2018.1 BASELINE -
3. “INCREMENTAL TVL” = DESIGN ANALYSIS
Incremental list of tags, a (Provided 20180921)
periodic update Sec -12.1
4. The BOS shall generate a And
full TVL file for AM-BR-47
DFW/DAL, every AM-BR-48
morning starting at time
AM-BR-49
X (Configurable,
currently 12:45 AM); AM-BR-50
including, but not limited AM-BR-93
to: AM-BR-94
 all the “DNT.” and AM-BR-95
“DFW.”
transponders
registered on NTTA
Accounts;
 the tag status, based
on NTTA/DAL/DFW
Business Rules;
 a revenue type equal
to full-fare, and;
 the Guest Type
assigned by a
DAL/DFW user.

Ste System Action Description Related Artifacts

p#
5. The BOS shall generate
an incremental TVL files
every X (Configurable,
currently (30) minutes as
necessary between time
Y (currently 6:00 AM)
and time Z (currently
11:00 PM) for DAL and
between time Y
(currently 3:30 AM) and
time Z (currently 10:45
PM) for DFW if the full
TVL file for DAL/DFW is
not in the process of
being generated;
including, but not limited
to: • all the “DNT.” and
“DFW.” transponder
updates since the
previous TVL file;
 the tag status, based
on NTTA/DAL
Business Rules;
 a revenue type equal
to full-fare, and;
 the Guest Type
assigned by a DAL
user
6. NTTA will receive the
acknowledgement from
the airports in the
prescribed format as
mentioned in the ICD
T BOS Tag
Status T BOS A/C BAL Matching Airports Status
Assigned > Low Balance G – Good
> Zero and <= Low
Balance B – Low Balance
<= Zero N – Negative Balance
Expired I – Invalid

TagInactive
Missing
Replaced
Stolen S - Stolen
Lost L – Lost
Returned R – Returned
Business Rules:
 TVL files sent to Parking Service Providers shall only include Transponders allowed by the
Parking Service Provider.
 TVL files sent to Parking Service Providers shall not include Transponders with a proposed
status. (sitting in a queue with no TVL)
 TVL files sent to Parking Service Providers shall not include Transponders that have not been
fulfilled. (sitting in a queue with no TVL)
 The TVL status sent to a Parking Service Provider shall be invalid for a Transponder with any of
the following conditions:
1. The Account is not active.
2. The Account is not replenished by an automatic replenishment method.
3. The Account does not have a valid Credit Card or other replenishment method on
file.
4. The Credit Card or replenishment method has expired and there are no additional
valid methods on file.
5. The Credit Card has a failed payment flag set due to an unsuccessful parking
transaction posting attempt (for any Parking Service Provider) and there are no
additional valid payment methods on file.
6. The Account has a failed replenishment flag set and three (3) consecutive failed
replenishment attempts (condition reset by a successful payment or by a Credit
Card update), and there are no additional valid payment methods on file, and the
Transponder has a Public Parker guest group Guest Type designated by the
Parking Service Provider.
7. The Transponder has been blocked from being used at the Parking Service
Provider’s facility by the patron.
8. The Transponder has been blocked from being used at the Parking Service
Provider’s facility by NTTA (at the request of the Parking Service Provider).
9. The Transponder has a returned status.
10. The Transponder has a defective status.
11. The Transponder has a retired status.
Otherwise,
1. The TVL status sent to a Parking Service Provider shall be lost for a Transponder
with a “lost” status.
2. The TVL status sent to a Parking Service Provider shall be stolen for a Transponder
with a “stolen” status.

3. The TVL status sent to a Parking Service Provider shall be negative balance for a
Transponder with an active status on an Account with a zero or negative balance.
4. The TVL status sent to a Parking Service Provider shall be low balance for a
Transponder with an active status on an Account with a positive balance that is
less than the Low Balance Level.
5. The TVL status sent to a Parking Service Provider shall be good for a Transponder
with an active status on an Account with a positive balance that is greater than or
equal to the Low Balance Level and a valid replenishment method is on file.
 TVL files sent to Parking Service Providers shall specify the revenue type as full-fare.
TXN-REQ-188.4 The BOS shall create and transfer TVLs to DAL, based on the DAL ICD and
NTTA’s Business Rules
TXN-REQ-188.5 The BOS shall create and transfer TVLs to DFW, based on the DFW ICD and
NTTA’s Business Rules
TXN-REQ-188.6 The BOS shall create and transfer TVLs to Parking facilities, based on the
existing ICD and NTTA’s Business Rules
AM-BR-47 A Customer’s Transponder may be used for payment at DFW and DAL Airports
if the Customer maintains a valid payment method specified for airport use,
on their Account
AM-BR-49 Customers may opt-in/opt-out of using their Transponder at the Dallas/Ft.

Worth Airport (DFW) and/or the Dallas Love Field Airport (DAL) Airport. When
opted-out, their Transponder will not be valid for use at the specified airport
AM-BR-48 A Customer who has a valid replenishment method on their Account shall be
automatically opted in to airport and parking
AM-BR-50 Customers may opt-in/opt-out of parking use. When opted-out, their
Transponder will not be valid for use at any parking facility (this does not
include the airport parking facility if the Customer opted in to Airport use).
AM-BR-93 Each Parking Service Provider may designate its own version of a unit ID for a
vehicle
AM-BR-94 Each Parking Service Provider may designate its own version of a Guest Type
(parking class) for a Transponder/Vehicle
AM-BR-95 Transponders/Vehicles that have not been designated with a Guest Type
(parking class) by a Parking Service Provider shall be treated as Class 01
(General Public) for that Parking Service Provider

3.5 UC-02-06-05: Create TVL in T-BOS and transfer to TSA Subscriber

Locations
Scope
The NTTA TVL created in T-BOS with all the tags and their respective status is forwarded to the
respective subscribers (TSA) for processing at scheduled intervals. It can be bulk file or a differential
batch update. Also receiving an acknowledgement from the subscriber
Process Details
 NTTA, as a service Provider (TSP) will create Bulk Transponder Validation List Files and pushed
from the Service Provider to the Subscriber
 Differential Transponder Validation List shall be created and pushed from the Service Provider to
the Subscriber’s SFTP server only if there are changes since the last Bulk TVL
 An acknowledgement will be received by NTTA from the respective Subscribers end
 The following Tag Statuses shall be available in the TVL
 X – Exempt; First Responder
 Before sending the TVL, NTTA will updated the TVL with the following from NTTA
 Add valid exempt Tags from First Responder accounts (Tag Status = X).
 Add valid Tags from cash-based accounts
 Add additional valid Tags from credit card-based accounts (those between $0
and $X dollars where they are not included as valid on the IOP TVL.
 Add valid Tags that are blocked for interoperability

Use Case Summary TVL is generated following agreed interface specification and
transferred to all the TSA Subscribers on the schedule as mentioned in
the ICD
available in T-BOS
 Tags managed by NTTA (NTTA as Home agency) are also
available in T-BOS

Post-conditions TVL file is successfully created and electronically distributed to all the
TSA locations in the prescribed format

#
1 TVL and LVL  The bulk and  RFP_Consolidated_Scope-
Generation Engine, T- differential TVL file AppendixOnly-v3-CLEAN-3
BOS creates and containing the  Service Provider ICD V1.19 CLEAN
transfers the lists to status of the DISTRIBUTED 20161019 Sec
the TSA subscribers transponders in the 4and5.1 & 5.6
on a scheduled agreed format is  TSP-ICD-Business Rules
interval/period generated LBJNTE12NTE3A3B FINAL DRAFT
following the v3.8 FINAL Sec 4.1 and 5.1
schedule as
NTTA receives the  TxDOT NTTA DFW Region Business
2 mentioned in the
acknowledgement Rules - FINAL DRAFT V 2.1
ICD
from the Subscribers 20160915– Sec 4.1 and 5.1
 Bulk Tag Validation
List with a valid tag
status are good
tags until they are
identified as zero,
negative balance or
invalid on the Tag
Validation List or
drop off the next
Bulk Tag Validation
List
 Differential Tag
Validation List that
contains the tags
that have changed
status since the last
Bulk Tag Validation
List
 Contents of bulk
and differential file
to follow the
business rules to
include data in the
file
 Generated files are
transmitted to the


#
destinations as
mentioned in the
ICD
 The party that
sends a file shall
receive an
acknowledgement
file within 5
minutes of the file
being received by
the target entity
T BOS A/C
T BOS Tag Status BAL Matching TSA Status
Assigned, > Low V- Valid (applies to both Bulk and Differential TVL)
InventoryRetailer Balance
<=Low Z- Zero / negative Balance (applies to both Bulk and Differential
Balance TVL)
Expired
TagInactive
Lost
Stolen
Returned
Missing
Replaced
DestroyedDisposa
l
DestroyedObsolet
e I - Invalid (only used for Differential TVL)
ReturnedDamage
d
ShippedDefective
ShippedDamaged
Shipped
ReturnedDefectiv
e
ReturnedGood
InventoryRecycle
d
Assigned X - Exempt, First Responder

Omitting a tag from a Bulk TVL automatically makes the tag

invalid
Business Rules:
 Bulk Transponder Validation List Files shall be created and pushed from the Service Provider to
the Subscriber Once per week
 The Bulk Tag Validation List will have “now” valid and zero/negative balance tags. It is up to the
Home Agency as to whether the zero/negative balance tags are included in the Bulk TVL
 Differential Transponder Validation List shall be created and pushed from the Service Provider
to the Subscriber Once a day on the days where a Bulk TVL is not transmitted
 The Differential TVL contains new valid and “now” invalid (invalid, zero/negative balance) tags
compared to the last Bulk TVL
 The TVL shall contain the Oklahoma Turnpike Authority’s TVL. OTA tags are processed as IOP
tags
 “DFWC” shall be used instead of “DFW” so that the locations are not confused with the DFW
Airport.
 There will be multiple TVLs, one per Interoperability Hub in operations
 Exempt Vehicle shall be included in the TVL with a transponder status of “X”, for TxDOT
 Data Record Format – TVL File LICENSE PLATE TYPES –
TL = Trailer
AQ = Antique
EX = Exempt
ZZ = All other

TXN-REQ-188.7 The BOS shall create and transfer TVLs to TSA Subscriber Locations, based on
the Subscriber/Service Provider ICD and Business Rules

3.6 UC-02-06-06: Receive TVL from Central Hub for central regional
agencies
Scope
The TVL tag status files are received by T-BOS from Central Hub with all the tags that are registered with
other Agencies connected to Central Hub & NTTA at predefined timelines which can be a full bulk
update or an Incremental batch update
Process Details
 NTTA receives Tag Validation List (TVL) from other regional agencies through the Central HUB
that contains status of tags and license plates associated with customer accounts held by each
of them in their respective BOS
 Central hub will combine TVLs from each home Agency before sending the TVL to the NTTA, so
NTTA receives the Consolidated TVL from the Central Hub
 T -BOS receive a Bulk or Differential TVL from the Central US Hub
 NTTA will acknowledge the TVL from Central Hub within a prescribed time
 The following Tag Statuses shall be received in the TVL.
 I – Invalid (only used for Differential TVL)

Use Case Summary TVL is received from partners and Hubs
 From Central HUB (for regional agencies)
Pre-conditions TVL files are sent from various agencies to the Central
Post-conditions TVL file is successfully received by T-BOS from all the locations via
Central Hub in the prescribed format of NTTA


#
1 TVL received from These files are related  RFP_Consolidated_Scope-
Central Hub on to regional states AppendixOnly-v3-CLEAN-3 –
scheduled intervals which are being sent to  SSIOP ICD VERSION 1 20 FINAL
/period Central Hub and RELEASED 20170213
received by T-BOS Sec 3 - Tag Validation List (TVL)
2 Acknowledgement NTTA should Data
should be sent by NTTA acknowledge the TVL Sec 7 -Acknowledgement Data
to central Hub files received from  SSIOP Business Rules VERSION
Central Hub as per the 2 7 FINAL RELEASED 20160630
ICD CLEAN Sec 2.1.5
3.7 UC-02-06-06_1: Receive TVL from Central Hub for southeastern

state agencies
Scope
other Agencies connected to Central Hub & NTTA at predefined timelines which can be a full bulk
Process Details
 NTTA receives Tag Validation List (TVL) from all IOP agencies through the Central HUB that
contains status of tags and license plates associated with customer accounts held by each of
them in their respective BOS
 SSIOP hub will combine TVLs from each home Agency before sending the TVL to the Central
Hub, so NTTA receives the Consolidated IOP TVL from the Central Hub
 NTTA will acknowledge the TVL from Central Hub within a prescribed time. the receiver IOP
agency i.e. NTTA should send an initial acknowledgment of a Tag Validation List (TVL) Data file,
back to the Central Hub which sent the TVL. Additionally, a second Acknowledgement Data file
shall be sent to provide the date/time the TVL is considered operative by the Central Hub and all
its local Agencies. The second Acknowledgement Data file will only be sent after an initial
Acknowledgement Data file has already been delivered.


Use Case Number UC-02-06-06_1

 From Central HUB (for southern states via South East Hub)
Pre-conditions TVL files are sent from various agencies to the Central Hub and other
Hubs
Central Hub and other Hubs in the prescribed format of NTTA

#
Central Hub on to Southern states AppendixOnly-v3-CLEAN-3 –
ICD CLEAN Sec 2.1.5
Business Rules:
 Each Tag Validation List (Bulk or Differential) shall be acknowledged by the receiving Hub and
Agency within sixty (60) minutes of receipt.
 Each Hub shall maintain a historical record of each Tag Validation List sent to and received from
the other Interoperable Agencies and hubs for a minimum period of one hundred-eighty (180)
days.
 Each Hub shall provide a utility to be used by authorized users to pull a tag’s history in the event
of a dispute or other inquiry.
 The Away Hub and each Away Agency is responsible to ensure each TVL is made active as soon
as possible after acknowledgement.

 The local Agency’s TVL and Transaction Acknowledgement date and time is recorded by the
SSIOP Hub who made the TVL or Transaction Submission available.
 There shall be two Acknowledgements for a TVL from the Away Hub, one to confirm the TVL
has been received, the second to record the TVL activation date and time.
 The Away Hub shall determine the TVL activation date and time based on the 2nd
Acknowledgement received for the TVL.
 The Away Hub shall send the second TVL ACK, indicating the TVL activation date/time, to the
Home Hub within four (4) hours. The Home Hub shall send the separate 2nd TVL ACK to its
Home Agency(ies) as needed.
 The Home Hub shall use the second TVL ACK to determine the activation date/time of its TVL at
another Hub and the tag status at the time of the transaction.
 It is the responsibility of the Away Agency to ensure bulk files and differential files are applied in
order based on Submission Date/Time such that a stale bulk or differential submission would
never overwrite more recent bulk or differential submission.
 In the event the Home SSIOP Hub receives a status for the same tag from two different Home
Agencies, the SSIOP Hub shall not filter the tags when creating and distributing the TVLs.

TXN-REQ-189 The BOS shall receive TVLs, from the Central US IOP Hub, for Southern States
Interoperability
TXN-REQ-190 The BOS shall receive TVLs, from other Hubs, for Southern States
Interoperability
3.8 UC-02-06-06_2: Receive TVL from Central Hub for National

interoperability
Scope
National IOP Agencies connected to Central Hub & NTTA at predefined timelines which can be a full bulk
Process Details
 NTTA receives Tag Validation List (TVL) from National IOP agencies through the Central HUB that
contains status of tags and license plates associated with customer accounts held by each of
them in their respective BOS
 National IOP hub will combine TVLs from each home Agency before sending the TVL to the
Central Hub, so NTTA receives the Consolidated IOP TVL from the Central Hub
 NTTA will acknowledge the TVL from Central Hub within a prescribed time


Use Case Number UC-02-06-06_2

 From Central HUB (for National IOP)
Pre-conditions TVL files are sent from National IOP hub to the Central Hub
Central Hub in the prescribed format of NTTA

#
Central Hub on to National IOP hub AppendixOnly-v3-CLEAN-3 –
ICD CLEAN Sec 2.1.5
TXN-REQ-191 The BOS shall receive TVLs, from other Hubs, for National Interoperability

3.9 UC-02-06-07: Convert and Transfer TVLs to NTTA/TSA roadways

as received from Central HUB
Scope
The TVLs are received by T-BOS from Central Hub with all the tags that are registered with external
agencies & NTTA at predefined timelines which can be a bulk or a differential batch update
After the receipt of the IOP TVL NTTA shall forwards the TVL information to NTTA Roadways & TSA
locations in the format agreed upon between the two entities
Process Details
 NTTA Host receives the Consolidated IOP TVL from the Central Hub in the form of a Bulk or
Differential TVL
 T – BOS will remove the NTTA tags from the consolidated list received
 It also makes these files available to the NTTA lane controllers to view to proceed further
 The following tag statuses shall be available in the IOP TVL for NTTA lanes
1 – Valid – Good Standing
2 – Low Balance - account balance below rebill threshold
3 – Invalid/Negative Balance - account not in good standing & zero-balanced account
4 – Lost/Stolen/Inventory
 Then the current back office takes it and converts it to tag status files for each TSA to send it to
the Facility Servers
 The following Tag Statuses shall be sent to TSA in the TVL
 X – Exempt; First Responder
 In the event NTTA does not receive a Bulk or Differential TVL from the Central US Hub, NTTA will
create and distribute a Differential TVL

Use Case Summary TVL as received from Central HUB are being converted to an agreed file
format (following agreed interface specification) and sent to
 NTTA Roadways (made available in Queue for view)
 TSA Subscriber Roadways

Pre-conditions  TVL files are sent from various agencies to the Central Hub and

Other Hubs and received in T-BOS

Post-conditions  TVL file is successfully transferred by T-BOS to NTTA roadways
and TSA subscriber roadways in the configurable file format

#
1 TVL received from Central  These files are  ICD007 External FS Lane
Hub and other Hubs are related to different Transaction Interface Rev
converted and pushed to home agencies 1_21
queues for NTTA Roadways which are being  ICD008 External AVI
sent to Central Hub Status Update Interface
and other hubs Rev 1_4
received by T-BOS.
 Transfer IOP TVL
tag status updates
that are registered
with other
agencies
 Converted based
on a Configurable
Flag before sent to
NTTA lanes
 Full and
incremental TVL
data containing the
status of the
transponders in
the format as
agreed in the ICD is
generated per the
schedule
mentioned in the
ICD.
 Generated data
are made available
for view by the
lanes via queue as
mentioned in the
ICD
2 TVL received from Central  These files being  RFP_Consolidated_Scope-


#
Hub are converted and sent sent to Central Hub AppendixOnly-v3-CLEAN-
to TSA Subscriber Roadways and received by T- 3
at configurable times of the BOS.  Service Provider ICD
day  Converted and V1.19 CLEAN
sent to TSA DISTRIBUTED 20161019
Subscribers after Sec 4and5
applying NTTA’s  TSP-ICD-Business Rules
transponder and LBJNTE12NTE3A3B FINAL
License Plate DRAFT v3.8 FINAL Sec 4.1
updates and 5.1
 Bulk as well  TxDOT NTTA DFW Region
Differential l files Business Rules - FINAL
are sent DRAFT V 2.1 20160915–
Sec 4.1 and 5.1
Business Rules:
TSA
 Bulk Transponder Validation List Files shall be created and pushed from the Service Provider to
the Subscriber Once per week
 Differential Transponder Validation List shall be created and pushed from the Service Provider
to the Subscriber Once a day on the days where a Bulk TVL is not transmitted
 There will be multiple TVLs, one per Interoperability Hub in operations
 Exempt Vehicle shall be included in the TVL with a transponder status of “X”, for TxDOT
TXN-REQ-192 The BOS shall convert and transfer the TVLs, from the Central US IOP Hub
and other Hubs, to NTTA Roadway, based on a Configurable Flag, for each
Home Agency; i.e., NTTA may require transponders, from the Florida
Turnpike Enterprise, to be sent to the Roadway, but not Miami-Dade
Expressway.
TXN-REQ-193 The BOS shall transfer the TVLs, from the Central US IOP Hub, to the TSA
Subscriber Roadways, after applying NTTA’s transponder and License Plate
updates, based on the Subscriber/Service Provider ICD and Business Rules.
TXN-REQ-197 The BOS shall provide the TVLs, and LVLs, to the TSA Subscriber Roadways,
at Configurable times of day.
(Sending LVL to the TSA locations is parked as per NTTA)

3.10 UC-02-06-08: Create LVL in T-BOS and Transfer to Central US Hub

for Central regional and IOP agencies
Scope
The LVL file created in T-BOS with all the license plates that are attached to a customer account in NTTA
T-BOS is forwarded to the Central HUB according at scheduled intervals. This can be full or an
incremental batch update files.
Process Details
 NTTA shall create a License Plate Validation List for the registered License Plates on patron
accounts used for video tolling by the Authority
 LVL status file contain a record for every License Plate in use by the Authority that is not
associated with a Tag
 Once the License Plate Validation List is created, it is transmitted to the other Service Providers
and Subscribers via the IOP Hub
 Also, The License Plate Validation List requires acknowledgement from the receiving Service
Providers and Subscribers. When a License Plate Validation List Acknowledgement File arrives,
the file size and the header record is examined to perform a simple data integrity check
 LVL files are Full or Incremental in type
 The following LVL file Statuses are sent
 G – Good
 B – Low Balance
 I – Invalid
 L – Lost
 N – Negative Balance
 R – Returned
 S - Stolen

Use Case Summary LVL is generated in T-BOS based on the agreed interface specification
(SSIOP) and transferred to Central US IOP Hub at the prescribed time
Pre-conditions Customers registered their license plates with NTTA (registered video
customers). License plate information is available in T-BOS for
registered customers
Post-conditions LVL file is successfully created and electronically distributed to the
Central HUB in the prescribed format

Step # System Action Description Related Artifacts

1 T-BOS creates and transfers  Full as well INTEROPERABLE-ICD-
the lists to the Central US IOP Incremental LVL files 05-LVL_v1_FINAL Sec 2
Hub on a scheduled are sent & Sec 3
interval/period  LVL Status, Vehicle
Classification,
Revenue Type,
License Plate State,
License Plate Number
and LVL Home
Authority are
mandatory attributes
in the LVL files
2 NTTA receives  Central Hub sends
acknowledgement from the the
recipient i.e. Central Hub acknowledgement to
NTTA received from
IOP hub after the
data integrity check
 A file noted as
incorrect based on
the file size, record
count, checksum, or
file format should be
flagged as damaged
and notification sent
 If the file size, record
count, checksum,
and file format are
all correct, file
processing continues
Business Rules:
 Bulk License Plate Validation Lists are transferred to receiving Service Providers and Subscribers
by 6:00 am (CDT).
 Incremental files are typically distributed once an hour. Since these lists contain only those
license plates whose status has changed, the updated lists may not be generated hourly

TXN-REQ-194 The BOS shall create LVLs for Interoperability, in accordance with the latest
LVL ICD and NTTA’s Business Rules
TXN-REQ-195 The BOS shall transmit LVLs to the Central US IOP Hub, in accordance with the
latest LVL ICD
3.11 UC-02-06-09: Receive LVL from Central US Hub

Scope
The LVL files are received in T-BOS with all the license plates information that are on registered
customer accounts with respective agencies at scheduled intervals. It can be bulk file or an incremental
batch update
Process Details
 The combined LVL list related to the away agencies is received by T-BOS via the Central Hub
 Then NTTA sends an acknowledgement to Central Hub as the License Plate Validation List
requires acknowledgement from the receiving Service Providers and Subscribers
 LVL files received are Full or Incremental in type
 The following are various status for the license plates included in the LVL file received
 G – Good
 B – Low Balance
 I – Invalid
 L – Lost
 N – Negative Balance
 R – Returned
 S - Stolen
Use Case Summary LVL is received from Central Hub (for regional partners and for southern
states via Southeast HUB)
Pre-conditions LVL files are sent from various agencies or Southeast HUB to the Central
Hub
Post-conditions LVL file is successfully received by T-BOS from all the locations via
Central Hub in the SSIOP format
Upon receipt, it is successfully acknowledged

1 LVL received from Central Hub are  These files being INTEROPERABLE-ICD-


converted and sent to NTTA and sent to Central 05-LVL_v1_FINAL 2 &
TSA Subscriber Roadways at Hub and received Sec 3
configurable times of the day by T-BOS
 Bulk as well
Incremental LVL
files are received
 LVL Status, Vehicle
Classification,
Revenue Type,
License Plate
State,
License Plate
Number and LVL
Home Authority
are mandatory
attributes in the
LVL files
2 NTTA sends acknowledgement to  NTTA sends the

the Central Hub acknowledgement
to Central Hub as
per the ICD
Business Rules:
 Bulk License Plate Validation Lists are transferred to receiving Service Providers and Subscribers
by 6:00 am (CDT).
 Incremental files are typically distributed once an hour. Since these lists contain only those
license plates whose status has changed, the updated lists may not be generated hourly
TXN-REQ-196 The BOS shall receive LVLs from the Central US IOP Hub, in accordance with
the latest LVL ICD

4 Interface Specifications
1. NTTA
ICD007 External FS ICD008 External AVI

Lane Transaction Interface Rev
Status
1_21Update
(Provided
Interface
by NTTARev20181031).doc
1_4.doc
2. SSIOP
SSIOP ICD VERSION 1 SSIOP Business Rules INTEROPERABLE-ICD-

20 FINAL RELEASED 20170213.docx
VERSION 2 7 FINAL RELEASED
05-LVL_v1_FINAL.doc
20160630 CLEAN.docx
3. Airports
INTEROP-ICD-02 AVI NTTA Business

Tag Status_20170117_DAL_SKIDATA_Integration.doc
Rules-v2018.1 BASELINE - DESIGN ANALYSIS (Provided 20180921).docx
4. TSA
Service Provider ICD TSP-ICD-Business TxDOT NTTA DFW

V1.19 CLEAN DISTRIBUTED
Rules
20161019.docx
LBJNTE12NTE3A3BRegion
FINAL Business
DRAFT v3.8
Rules
FINAL.docx
- FINAL DRAFT V 2.1 20160915.docx

Appendix A: Requirements Traceability

The attached table includes all requirements and business rules that are included in this FSD. Any
requirement or business rule in the appropriate sections that have been excluded are identified.
FSD-02-06 TVL LVL

Processing RTM.xlsx

FSD-02-06 TVL LVL Processing v1.0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FSD-02-06 TVL LVL Processing v1.0

Uploaded by

Copyright:

Available Formats

TVL and LVL Processing

Functional Specification Document

TollPlus Confidential Page of Version 0.6 – 11/08/2018

TollPlus Confidential Page of Version 0.6 – 11/08/2018

TollPlus Confidential Page of Version 0.6 – 11/08/2018

TollPlus Confidential Page of Version 0.6 – 11/08/2018

MODULE FUNCTIONAL AREA

1.4 Related Requirements

1.5 Parked Requirements

Requirement # Description Reason

1.6 Project Requirements

1.5.1 Functional Specification Document (FSD) Covered?

TollPlus Confidential Page of Version 0.6 – 11/08/2018

1.5.1 Functional Specification Document (FSD) Covered?

TollPlus Confidential Page of Version 0.6 – 11/08/2018

1.7 TVL and LVL – Available References

TollPlus Confidential Page of Version 0.6 – 11/08/2018

TollPlus Confidential Page of Version 0.6 – 11/08/2018

TollPlus Confidential Page of Version 0.6 – 11/08/2018

TollPlus Confidential Page of Version 0.6 – 11/08/2018

Status State Plate Type Classification Authority

Figure 1: TVL and LVL Process

TollPlus Confidential Page of Version 0.6 – 11/08/2018

Use Case Number UC-02-06-01

The BOS shall automatically change the status of transponders and

TollPlus Confidential Page of Version 0.6 – 11/08/2018

in the next TVL and LVL generated

Step System Action Description Related

TollPlus Confidential Page of Version 0.6 – 11/08/2018

Step System Action Description Related

Requirements, Business Rules Covered:

TollPlus Confidential Page of Version 0.6 – 11/08/2018

3.2 UC-02-06-02: Create TVL in T-BOS and transfer to NTTA Roadways

Use Case Number UC-02-06-02

Step System Action Description Related Artifacts

TollPlus Confidential Page of Version 0.6 – 11/08/2018

Step System Action Description Related Artifacts

T BOS Tag Status T BOS A/C BAL Matching NTTA Status

Requirements, Business Rules Covered:

TollPlus Confidential Page of Version 0.6 – 11/08/2018

3.3 UC-02-06-03: Create TVLs in T-BOS and transfer to Central US IOP

TollPlus Confidential Page of Version 0.6 – 11/08/2018

 Customers with transponders have opted in for interoperability

Step System Action Description Related Artifacts

TollPlus Confidential Page of Version 0.6 – 11/08/2018

AM-BR-51 Customers may opt-in/opt-out of interoperability use. When opted-out, their

TollPlus Confidential Page of Version 0.6 – 11/08/2018

Use Case Number UC-02-06-04

TollPlus Confidential Page of Version 0.6 – 11/08/2018

 Tags managed by NTTA (NTTA as Home agency) are also

 Customers with transponders have opted in for airport parking

Ste System Action Description Related Artifacts

TollPlus Confidential Page of Version 0.6 – 11/08/2018

Ste System Action Description Related Artifacts

TollPlus Confidential Page of Version 0.6 – 11/08/2018

TollPlus Confidential Page of Version 0.6 – 11/08/2018

AM-BR-49 Customers may opt-in/opt-out of using their Transponder at the Dallas/Ft.

TollPlus Confidential Page of Version 0.6 – 11/08/2018

3.5 UC-02-06-05: Create TVL in T-BOS and transfer to TSA Subscriber

 Add valid Tags from cash-based accounts

 Add valid Tags that are blocked for interoperability

Use Case Number UC-02-06-05

TollPlus Confidential Page of Version 0.6 – 11/08/2018