History & Statistics
History#
The History shows everything that has happened in the shop related to ACS in chronological order. It is the most important page for staff to monitor when working.
The top of the history page has a search bar for finding past records, as well as a date range to narrow results. Only 100 results can be viewed at once, sorted chronologically, newest first.
For further sorting, in the history, different categories of message types can be selectively hidden.
Info
The formatting of the code blocks below doesn't show it, but many of these reports have embedded links to go to relevant sections. For example, clicking on a user's name brings up their Account Page, or clicking on the machine's name brings up the relevant part of the Access Devices Page.
Sign-In Attempts#
Users signing into a space are logged in the history, so you can match a face to a name.
Users with ID cards that are not recognized are reported with the following message:
UID Click to Reveal failed to swipe into Atrium - Wood Shop, Atrium - Manual Shop, Atrium - South Shop with error 'User does not exist'
Manual Sign-In#
If a user wants to sign in to a space but they don't have their ID, or the Sign-In Reader is not working, staff can manually sign them in by pressing "Manual Room Sign-In" in the top right corner of the screen. The staff will then need to enter the user's email, and select the room to sign them into.
Equipment Activation Attempts#
When a user attempts to activate a piece of equipment, both the user and equipment are reported in the history.
If the activation was not successful, the reasoning is reported;
- "User requires Welcome" - User did not sign in to the space today.
- "User does not exist" - User's UID could not be found in the system.
- "Incomplete Trainings" - User is missing one or more of the Training Modules.
- The missing training(s) will be listed in the history log as well.
- If the user has a hold on their account, this is the error message used but with no trainings listed.
- "Missing Staff Approval" - User does not have the staff approval for that equipment.
If the user is a Staff role, the history record will indicate they were authorized because of their Staff access.
ACS Status Reports#
ACS Status reports are used for reporting notable status reports from the ACS Core. This is predominately used for reporting when a user signs out of a machine, ending a session. The session length is included in the message.
Example:
ACS State Change#
The ACS State Change is used to indicate an ACS Core is in a state different than the website last recorded.
If a user's ID was present when the state changed, it is included in the history log.
Note
Since the state change is based on the website's records, it is possible for a Core to quickly swap between states and the website not record them. State changes are also not recorded if there are networking issues with the Core.
Example Format:
ACS Messages#
As part of the API, the ACS Core can send plaintext messages to the server to convey verbose data or reports. These are logged in the history as the ACS Message.
Example Messages:
Server Messages#
Server Messages report actions undertaken by the website. There are over a dozen different server messages. Some are periodic, some are for logging events, and some are for generating debug data.
Example Messages:
Training Hold Applied:
Training API Trigger:
Daily Server Cleanup:
Admin Actions#
Admin Actions refer to tasks carried out by staff.
Examples:
Training Submissions#
This section shows users completing Training Quizzes. The user, the quiz, and the score are reported.
Example:
Uncategorized#
Any message type that does not fit one of the above categories goes into Uncategorized.
Statistics#
The Statistics page shows summary information about the shop that is useful for gauging use.
Today's Numbers#
This section shows information about today's usage of all spaces. Statistics reset at midnight local.
Note
"Room Sign-Ins" counts all unique rooms signed into by users that day, not sign-ins by users. So if a user signs into multiple rooms, they will be counted multiple times.
Room Usage#
The Room Usage section lets you generate graphs showing the number of sign-ins per hour per room per day. This can be useful for identifying trends in usage for informing staffing.
Optionally, the graphs can show both the sum for that specific day and the average over a range for each hour. This can be useful for comparing an arbitrary week's sign-ins to the average.
Equipment Usage#
The Equipment Usage section shows how often machines are being used, as well as a percentage utilization versus the open hours of the space they are located in. A data range can be specified to narrow down the results.
Trainings#
The Training section lets you see how many people took and passed a training in the defined time frame. The pass rate will be calculated for each test.