DataPoint Manual Fare Entries

Your DataPoint application, located in ETMS in the Operations product suite, is used for a variety of scheduling-related tasks. Use this application to manually enter fare information for cases when vehicles are not connected to your ITS system, and you need a way to document and reconcile collected fares from revenue service. After these are manually documented in DataPoint, the data becomes available for exceptions processing in myAvail as the final reconciliation process. Follow the steps below to use this feature.

1. Have your paper tally sheets for fare collection in hand
2. Login to ETMS and navigate to DataPoint in the Operations product suite.
   • Or type DataPoint in the Search bar and select it from the results.
     
3. Select Import from the menu on the left from the Home screen.
4. Select the blue text hyperlink for Manual Entry above the calendar.
5. Next, use the date picker to enter the Date in Step 1 then select Continue.
   
6. On the next screen, use the menus on the left to indicate the route, trip and stop.
   Manual Fare Entry Screen:
   • Best Practice: fill in all fields
   • Without stops indicated here, the data will be undefined at the stop level in your Business Intelligence ridership reports
7. Then use all dropdown menus and fare-type boxes to enter needed information: bus, driver, fare types and frequency, time.
8. Press the button at the bottom of the screen to Add Record to save the data.
9. The recorded data record displays below the table.
   
   
   • Press Delete if you need to cancel
10. Next, press the blue hyperlink at the top of this screen - Bus Summary and Import
    
    • You’ll see a table with the fare data you entered 
11. Press the Finish and Import button
    
    • Data moves to an interim database so you can process your exceptions records to make the data available in your Business Intelligence reports
12. Repeat the process if you need to add more fares by pressing the Data Entry button
13. Process the exceptions records so the data populates in your ridership reports in Business Intelligence
14. Enter any known system adjustments as these feed into your S10 NTD reporting metrics
    Exceptions Processing in ETMS:
    
15.