CBORD User Group Conference 2018

1. CBORD User Group Conference 2018 Odyssey – Best Practices System Administration

2. Best Practices Odyssey System Administration Tuesday 10/8/2018 11:00pm – 12:00pm Presented by: Michael J Schutte

3. Best Practices Odyssey System Administration Daily All sites should do Daily Task to ensure Odyssey is running well to avoid downtime or loss of funds Bi-Weekly Bi-Weekly Bi-Weekly tasks are vital for sites that use Payroll Deduction All sites should also complete monthly tasks to aviod downtime and loss of funds System Total System up keep will assist support with speed of service and support. It will also help with Upgrades

4. Best Practices Odyssey System Administration • Check the System Dashboard • Verify Transaction speed • View Rejected Transactions or Sales Summary • Location Status by Terminals • Scheduled Task status for last 24 hours • Start of the Day Task • Daily System Administration

5. Best Practices Odyssey System Administration • Rejects and Sales Summary • Date and Time • Transaction type • Location • Reason – potential training opportunity • Invalid account (cashier used wrong tender) offline issue • Not on System (card number does not belong to an account) offline issue • Plan End date (Hospital – terminated account, University – not enrolled or no longer a student) • Patron • Can verify account and reason verification • Amount (if these were offline transaction each 1 would be a potential loss of revenue) • Start of the Day Task • Daily System Administration

6. Best Practices Odyssey System Administration • Terminals • Online Status • Terminal Name • Terminal Type • IP Address and Socket • Address • Cluster • Start of the Day Task • Daily System Administration

7. Best Practices Odyssey System Administration • Scheduled Tasks • End of Day completion status • Any task that fails will list out here • Those failure can be investigated in the schedule task module in history • Start of the Day Task • Daily System Administration

8. Best Practices Odyssey System Administration • Daily Reports • End of Day File Verification • End of Day Logged Transaction Summary • POS Reconciliation Failures by Terminal Report • Checker’s Log • Start of the Day Task • Daily System Administration

9. Best Practices Odyssey System Administration • Daily Report • End of Day File Verification • This report runs as a part of End of Day and it signifies its completion. • It is also a self audit as part of the process it collects the balances of all tenders at the start of the day calculates all sales, voids, add and deletes against all balances and compares totals of actual and calculated. • If it fails this report is replaced by the End of Day Audit Failure Report • Start of the Day Task • Daily System Administration

10. Best Practices Odyssey System Administration • Daily Report • End of Day Logged Transaction Summary • This report runs also a part of End of Day and it signifies its completion. • This report will list any transactions that were logged and sent to Odyssey • The importance of this report is to notify management that transaction were at risk from being offline and if there is a pattern, it could be a network or hardware issue that needs to be fixed • Start of the Day Task • Daily System Administration

11. Best Practices Odyssey System Administration • Daily Report • POS Reconciliation Failures by Terminal Report • This report runs as part of the daily report and is best if emailed. • This report gathers and compares transaction from Micro POS (3700, Simphony 1 and 2 versions) • The importance of this report is to determine if all transactions placed on the Micros POS all posted correctly to accounts in Odyssey and works with another Report the Daily Checker’s Log • Start of the Day Task • Daily System Administration

12. Best Practices Odyssey System Administration Odyssey Reporting POS Reconciliation Failures by Terminal • Date Range for the Report • Location • Accepted by Odyssey • Count / Amount • Rejected Offline Transactions • Submitted by POS • Count / Amount • Terminal Vaiiance Represents All Terminals in a Revenue Center

13. Best Practices Odyssey System Administration • Daily Report • Checker’s Log Report • This report runs as part of the daily report • This report displays all transactions that fail to post to patron accounts for any Odyssey reason. The report is filter only to gather data that is processed as Logged, Signoff and Batches for Sale and Voids only. • These transactions represent a potential for loss of funds for many reasons. • Start of the Day Task • Daily System Administration

14. Best Practices Odyssey System Administration Odyssey Reporting Checker’s Log • Date Range for the Report • Location • Transaction Date & Time (Actual) • Posted Date & Time • Patron ID and Name • Error that caused transaction to fail • Missing Funds

15. Best Practices Odyssey System Administration • Verify that Odyssey Payroll totals match the amount of funds received after the Payroll Deduction file was processed in to the payroll system. • 2 report can be used • Tender Totals Report in Operations filtering by tender Payroll and Unit • Tender Totals Report by Patron in Operations filtering by tender Payroll this report will give detail amount by each patron that spent funds • Bi-Weekly Task • Bi-Weekly System Administration

16. Best Practices Odyssey System Administration • Verify that Odyssey Department Recharges • Verify any accounts that require billing • Collect a report on Declining Balance Report • Monthly Tasks • Bi-Weekly System Administration

17. Best Practices Odyssey System Administration • Total System upkeep allows Odyssey to run smoothly • Will make things easier when needing support • Assist with speed of the upgrade process especially when moving servers or dealing with a POS upgrade • System Best Practices • Bi-Weekly System Administration

18. Best Practices Odyssey System Administration • Make sure a Daily Database Purge is running on the your system • This will remove non-essential data from your database keeping it clean and the database a small as possible • Keep Plans and Terminal area organized and clean • This help improve the ability of support to assist you and changes to the system • Remove Reporting/Exporting that is no longer in use • This will eliminate confusion when support/implementation is needed for assistance • System Best Practices • System Administration

19. Best Practices Odyssey System Administration • The Purge task is located under scheduler • It is programmed to run daily to remove log files and old data to keep the database small • Most noticeable data removed is the POS Check Detail • That data is only available for 425 days by default • Daily Database Purge • System Administration

20. Best Practices Odyssey System Administration • Daily Database Purge • System Administration

21. Best Practices Odyssey System Administration • Use of the hidden check box to remove inactive plans from view • Keeps plans organized and clean • Plan - Organization • System Administration

22. Best Practices Odyssey System Administration • Use of the hidden check box to remove inactive plans from view • Keeps Terminals organized and clean • Terminal - Organization • System Administration

23. Best Practices Odyssey System Administration • Disable tasks the are no longer in use to keep Scheduler clean and organized • Task - Organization • System Administration

24. Best Practices Odyssey System Administration • Delete Reports and Exports not longer needed • Need reports will always be: • Checker’s Log • Reconciliation • Reports and Export • System Administration Exports • If a new export is copied, created and placed into production. Once it is verified that it is working and will remain in production Delete old copies. It will stop a lot of confusion if upgrade or new implementation happens.

25. Questions?

26. Last Helpful Trick of the AdminwebOne of the biggest issues I have had and had comments about Adminweb is that if you are working on something in Odyssey and need to check data in an other module but if you navigate away from your current page you have to start over. If you open Odyssey in another webpage and complete the other task it overrides your original page and you still have to start over. This is caused because the 2 pages use the same cache from the browser. **Resolved open Adminweb in different browser and you can completed different tasks in different modules at the same time with the same user.

27. Michael J SchutteSr. System EngineerCBORD 950 Danby Road, Suite 100CIthaca, NY 14850Tel: 844.GO.CBORD (844.462.2673)| Cell:  402.707.0368 mjs2@cbord.comwww.cbord.com

28. We want your feedback! Please evaluate this session in the ERMobile app. Your feedback helps usimprove future sessions. Find this session in the app,and touch COMPLETE SESSION SURVEY. Thank you!