- Accessing the application
- Application security
- Devices and communication protocol
- Application access control levels
- Employees, departments and device users
- Time & Attendance Functionality
- Access control
- Batches & payroll integration
- Binary City Time API (Application Programming Interface)
-
Binary City Time integration with BioTime Technical Documentation
-
Application Security - SSL certificate (Biotime Technical documentation)
-
Application Security - What is an SSL certificate (Biotime Technical documentation)
-
Data encryption and User security (Biotime Technical documentation)
-
Firewalls (Biotime Technical documentation)
-
Backups (Biotime Technical documentation)
-
BioTime linking to Binary City Time (Biotime Technical documentation)
-
BioTime device Communication (Biotime Technical documentation)
-
Syncing to BioTime (Biotime Technical documentation)
-
Application backups
Application backups
The Binary City Time source code is backed up incrementally as any changes are made on an industry standard platform (Details not disclosed for security reasons).
The Binary City Time server instance(s) are guaranteed by the Amazon Web Services to always remain online, however, a snapshot of the server hosting the application is available for immediate restore. This is incrementally done daily to ensure an up to date version of the code is available by administrators without requiring a developer's assistance.
The Binary City Time database instances(s) are guaranteed by the Amazon Web Services to always remain online, however, a daily snapshot is taken of the entire database every night at 2 am and this is available for immediate restore and again ensure that the application can be brought back online by an administrator without requiring a developer's assistance.
Views | |
---|---|
297 | Total Views |
4 | Members Views |
760 | Public Views |
Actions | |
---|---|
0 | Likes |
0 | Dislikes |
0 | Comments |
Share by mail
Please login to share this webpage by email.