Body
Oracle Hospitality Simphony Application Support Documentation
Application Summary
Oracle Hospitality Simphony is a enterprise Point of Sale System used primarily for Michigan Dining Retail Operations to conduct cash register sales. Transactions can be performed using Cash, Blue Bucks/Dining Dollars, and Credit Cards (using FreedomPay).
General architecture relies on: A Transaction Processing Server that cash registers communicate with (sl-simph-tp), a dedicated Reporting & Analytics Server that is run on an OracleWeblogic instance (sl-simph-rp), and an underlying MS SQL database used by the application servers (db-sl-simph-p).
Michigan Dining Systems Support are the primary application administrators for this environment (including managing items, cashiers, defining new workstations and revenue centers).
SLTS performs some of the following functions: Server patching/monitoring, Certificate Management, firewall management, aid in the distribution of equipment and inventory management.
Include the following information in this section:
-
On-Prem
-
Server Name:
-
Prod Transaction Processing Server: sl-simph-tp
-
Prod Reporting Server: sl-simph-rp
-
Database server (Prod): db-sl-simph-p
-
IP:
Support Information
-
If content needs to be provided, edited, updated or changed, provide the contact information of the person responsible for those tasks.
-
Managing users/groups/password resets: Michigan Dining System Support
-
Importing data: Michigan Dining System Support
-
Changing items/prices: Michigan Dining System Support
System Upgrades/Maintenance
-
We do not have a test Simphony server in place. If changes are needing to be evaluated, support requests should be made to CBORD Support
-
Recurring Database maintenance should be performed after Fall and Winter terms end Recommended System Maintenance for Micros Simphony Updated Jan 1 2020.pdf
-
Under normal circumstances, how often should application patches be installed, will upgrades be evaluated on the Test Server?
-
Currently, there is no defined cycle for app maintenance. Some patches like Java can be applied after engaging with CBORD Support. Maintenance tasks need to be coordinated with mds-systemsupport so that they can schedule work to minimize downtime.
-
How much time is needed for patch testing?
-
N/A
-
How frequently should new application patches be installed (i.e. annually, quarterly, as new releases become available, etc)
-
As releases become available (biannually when possible, but outages can be scheduled if coordinated with MDS Systems Office
-
When can the system be taken down to install new application versions in production? If there's an ideal time of day to minimize disruption, specify what that window is. Is there a time of year that is less disruptive than others for application maintenance?
-
After Fall Term Ends (late December)
-
Before Spring Term Begins (end of April - Early May)
User Accounts
EMC Desktop Application: Used exclusively by MDS System Support Staff & Dining System Administrator for managing Simphony POS environment. Account provisioning is performed by Dining POS Administrator (Lori Haberland)
Cashier logins - provisioned by Michigan Dining System Support staff at request of Michigan Dining Retail managers.
Important Contacts
Include the following information in this section:
-
Unit Contact (Name, email, role)
-
SLTS Contact (Name, email, role)
-
Vendor Contact (Name, email, support number, and role) – if necessary
Quick Reference
Include the following information in this section: (update or remove references with new linked document locations.