FX Data Integrity Check Tool
The table lists the check boxes in each of the panes in the FX Data Integrity Check dialog box.
Not all of the items on this list apply to all transit sites. For example, if your transit site does not use the system map then you do not need check boxes such as Missing Pattern Trace or Missing Destination Signs
| Panes | Fields | Remarks |
|---|---|---|
| Miscellaneous | Non Production SignUp Calendars |
When you click the Ops button, this option is automatically selected. The system searches for non-production sign-up periods that have Exception Calendar records in the calendar table. |
| Overlapping and Gaps in Peaks |
Checks peak service hours for overlapping times or gaps between time periods and verifies records entered separately in FX and Trapeze PLAN. |
|
| Nodes/Stops | Missing Name | Looks for any missing names such as abbreviations and long names. |
| Not Geocoded | Looks for stops and nodes that are missing coordinates. | |
| Nodes with No Trip Times |
Identifies nodes that do not have trip times. The report shows the services and sign-up periods associated with the missing trip times. |
|
| Stops Not Used On Any Line | Identifies stops that are not found on any line. | |
| Duplicate Stops | Looks for identical stops at the same location. It checks the On Street, At Street, Stop Position and City (where stop is located) fields of the stops in the database. | |
| Duplicate Nodes | Checks for duplicate node abbreviations that are used only within one agency. It does not consider nodes common among agencies within a multi-agency environment. | |
| Nodes Over Capacity | Identifies nodes where more than a set number of buses are at the point within a certain number of minutes. This is associated with the Capacity time field in Ranges dialog box. | |
| Stops Not In Service | Looks for stops that have not been marked as in service (in use). | |
| Nodes Not In Service | Looks for nodes that have not been marked as in service (in use). | |
| Duplicate Stop Names | Looks for stop names that are used more than once. | |
| Duplicate Node Names |
Looks for node names that are used more than once. |
|
| Duplicate Stop Positions |
Looks for stop positions that are used more than once. |
|
| Lines | Missing Line Trace | Checks for any missing map pattern or route map traces. |
| Lines With No Stops | Identifies lines that do not have stops associated with it. | |
| Line Missing Relief Points | Identifies lines that do not have any relief points for the divisions to which the lines are assigned. | |
| Line Does Not Start/End with Node |
(Used with TransitMaster) If selected, FX checks if the line starts and ends with a stop that does not have an associated node. This is automatically selected if the ITS button is clicked. |
|
| Routes With More Than X Node |
X stands for a number of nodes. If selected, FX checks lines with more than the number of nodes set in the field, Max nodes per line direction set in the Ranges dialog box. |
|
| Patterns | Missing Distance | Looks for any negative distances that may have been applied. The main reason that negative distances may appear is due to the geocode sequence of any nodes and/or stops that are part of a pattern. For instance, if you have Node 1, Node 2, Node 3 in sequence order for a pattern but the physical location of the nodes is actually in this sequence: Node 1, Node 3, Node 2; a negative distance occurs between Node 2 and Node 3. Geocode the node again to the correct coordinates or change the sequence of the node order in the pattern and update the pattern accordingly. (You may also have to re-extract your Stop Patterns depending on the problem. |
| Zero or Negative Node to Node Distance | Identifies node to node pairs that are missing distances. | |
| Zero or Negative Stop to Stop Distance | Identifies stop to stop pairs that are missing distances. | |
| Missing Pattern Trace | Identifies patterns that do not have traces defined by pattern and line. | |
| Fragmented Pattern Trace | Identifies the number of fragments for each pattern trace. | |
| Patterns with no Running Times | Identifies the patterns that do not have run time records. | |
| Patterns Missing Stop Pattern |
Identifies patterns and lines from which stop patterns have been extracted. |
|
| Stop Pattern Missing Nodes | Identifies stop patterns that do not have nodes. | |
| Stop Pattern Missing Stops | Identifies stop patterns that do not have stops. | |
| Missing Destination Sign Text | Identifies patterns and lines that do not have destination information shown as text. | |
| Missing Destination Sign Code | Identifies patterns and lines that do not have destination information shown as sign codes. The Ranges value for Skip Unused Patterns is used with this option. | |
| Stop Too Far From Trace | Checks to see if nodes and stops are too far from a pattern trace. When you select <All>, the system applies the check to all lines. The report that shows these nodes and stops also includes the distance between them and the route trace. | |
| Duplicate Pattern Names |
Checks to make sure that there are no duplicate pattern names in either direction of the line. |
|
| Pattern vs. Stop Pattern Distances |
Checks for inconsistencies between the pattern and stop pattern distances. |
|
| Trace Length Exceeds Pattern Distance | Checks for patterns where the trace is longer than the stored distance. | |
| Patterns Not on Trips | Checks for patterns not associated with any trip. | |
| Stop Flag Differences | Identifies all stops that are not set as node only at the stop pattern level but are set as node only at either the line direction level or node level. | |
| Pattern Stop Flag Differences |
Checks for lines that have multiple patterns and direction and compares them with other patterns and directions, which have Load or Unload points. The tool checks if the stop abbreviations match those nodes/stops. For stops that have an action of Load or Unload, the tool checks stops with Load or Unload points that have similar stop abbreviations on both patterns. (The stopNum sequence is used but the error messages show stopabbr for easier identification.) |
|
| Missing Special Points |
Searches for patterns that have missing special points or do not have special points. In order that the system does not have to check unused patterns, make sure to select the option, Skip Unused Patterns (for Pattern Checks) in the Ranges dialog box. |
|
| Trips | Patterns Missing Running Times |
Only checks for patterns associated with trips that do not have run time records at the time of the trips. A missing run time is typically indicated by a ? instead of a value on the Run Times tab in the Trip Building screen. |
| Patterns Missing Run Times Ignore Zeros | Only checks for patterns associated with trips that have missing run times but ignores trips that have zero ( '0' ) values. | |
| Mismatching Running Times |
Identifies running times that do not match the trip times. |
|
| Mismatching Running Times Ignore Frozen | Checks for trips with mismatching running times but ignores the trips that are frozen. | |
| Times Decrease Across Trip | Compares successive trip times and checks if the trip time of successive nodes are in order. For example, Node A and Node B are successive nodes. The trip time of Node A is 10:00 and the trip time of Node B is 9:58. The system detects the error, which probably occurred during data entry. | |
| Trips Missing Patterns | Identifies trips that do not have patterns | |
| Trips Mismatching Patterns | Identifies trips that do not match the selected pattern. | |
| Trips Mismatching Patterns Ignore Frozen | Checks for trips with mismatching patterns but ignores the trips that are frozen. | |
| Negative or Zero Headway | Checks for trips that have buses on the same route going in the same direction that pass each other during the trip. | |
|
Speed Out of Range by Trip |
The system performs a speed check for trip times. This is controlled by a setting in the Ranges dialog box. | |
| Speed Out of Range Node to Node | Checks for pairs of nodes on a trip that are scheduled at a speed outside of the range defined in the Ranges dialog box. | |
| Overlapping Running Times | Identifies overlapping running time bands. | |
| Overlapping Node to Node Time Bands | Identifies overlapping Node to Node time bands. | |
| Lines with No Stop Trips | Checks for lines whose stop trips have not been generated. Stop trips are generated in the Trip Building process or using the Extended FX Data Tool. | |
| Stop Trips Missing Times | Identifies stop trips that have not been extracted or have missing times. | |
|
Stop Trip Integrity
|
Identifies stop trips that are not whole, that is, not showing “I” in the INT column. | |
| Stop Trip Validity | Identifies stop trips that are not valid, that is, not showing “V” in the VAL column. | |
| Stop Trips Not Matching Stop Pattern |
Checks if the stop trips match the stop patterns. Errors may arise when you do not regenerate the stop trips after you modify the stop patterns. |
|
| Non Revenue Trips | Identifies the trips that are not marked as Revenue. | |
| Blocks |
Missing Block Number |
Identifies blocks that do not have block numbers, that is, trips that had not been blocked. |
| Missing Garage | Identifies blocks that have not been assigned garages. | |
|
Missing Division |
Identifies blocks to which no division is assigned. | |
| Different Divisions in Block | Identifies blocks to which more than one division are assigned. | |
| Layover Out of Range | Checks if layovers are within the ranges set in Properties dialog box or in the Ranges dialog box. | |
| Missing or Out of Range Deadheads | Looks for missing or out of range deadheads. The search results include the type and the from and to nodes of the missing or out of range deadheads. | |
| Layover+Dhd Out of Range | Looks for missing or out of range layover and deadheads. The search results include the type and the from and to nodes of the missing or out of range deadheads. | |
| Missing Deadhead Comments | Identifies blocks that do not have comments. | |
| Interline/Relationship Violations |
Looks for interlining that are set as Not allowed on the Relationship tab in the Interlining dialog box. |
|
| Missing Block Names | Identifies blocks that do not have block names. | |
|
Times Decrease Across Block |
Identifies where the time on blocks decrease. | |
| Different Vehicle Types in Block | Identifies blocks that have been assigned two or more vehicle types. | |
| Overlapping Interline Relationships | Checks for overlapping lines that have been interlined. | |
| Missing Vehicle Type | Checks for Block records that have not been assigned vehicle types. | |
| Pull-in/Pull-out Mismatch | Checks if the pull-in garage is the same as the pull-out garage in a block. | |
| Trip Start Time Before Pull-out Time | Checks for trips that start before the pull-out time. | |
| Trip End Time After Pull-in Time | Checks for trips that end after the pull-in time. When users click the ITS button, this option together with the Pull-in/Pull-out Mismatch and Trip Start Time Before Pull-out Time options are automatically selected. |
|
| Duplicate Block Number | Checks for vehicle and driver blocks that have the same block number in the same service. | |
|
Duplicate Block Name |
Checks for blocks that may have different block numbers but the same block name in the same service. | |
| Block Over Fuel Range | Searches for any block whose distance is over the maximum fuel range. The distance is measured from the pull-out time to the pull-in time. | |
|
Block Over Hours of Service |
Searches for any block whose hours of service are over the set maximum number of hours of service. | |
| Blocks More Than X Trips | Searches for blocks that have more than the number of trips set in the Max Trips in a Block field in the Ranges dialog box. | |
| Deadheads |
Missing or Out of Range Distance |
Checks if the distance is within the range of the Deadhead Distance set in the Ranges dialog box. |
| Missing or Out of Range Time | Checks if the time is within the range of the Deadhead Time set in the Ranges dialog box. | |
| Missing Comments | Identifies deadheads without comments. | |
| Overlapping Time Bands | Identifies time bands that overlap. | |
| Speed Out of Range | Performs a speed check for trip times. (This is the same as in Trips.) | |
| Fragmented Deadhead Trace on Used Deadhead | If selected, the system provides a list of deadhead traces that are fragmented. (This option is for users who use calculated deadheads and do not use exceptions.) | |
| Missing Trace on Used Deadhead | Checks deadheads, which are used within a sign-up period, for missing traces. | |
| Runs |
Uncut Work |
Checks for uncut work. |
| Missing Run Name | Identifies runs that do not have Run Names. | |
| Missing Costing | Identifies runs that do not have costing. This option applies if you are not using BlockBuster. | |
| Illegal Runs | Identifies illegal runs. (This filter is shown and applies only if you are using BlockBuster.) | |
| Missing Active Scenario | Checks whether each division/service group has an active scenario. (This filter is shown and applies only if you are using BlockBuster.) | |
| Travels |
Missing or Out of Range Actual Time |
Checks for travels that have missing or out of range Travel Actual Time based on the values set in the Ranges dialog box. |
| Missing or Out of Range Paid Time | Checks for travels that have missing or out of range Travel Paid Time based on the values set in the Ranges dialog box. | |
| Missing Comments | Identifies travels with missing comments. | |
| Overlapping Time Bands | Identifies time bands that overlap. | |
| Rosters |
Missing Roster Number |
Identifies rosters that are missing roster numbers. |
| Missing Roster Name | Identifies rosters that are missing roster names. | |
| Missing Costing | Indicates that Update Costing should be performed on your roster data. | |
| With Invalid Run Type | Identifies rosters with invalid run types. |