Contact person: Customisable Sign-In/Out System Development

Phone:Show

Email:Show

Location: Brisbane, Australia

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"Looking for a one off build, the system that needs to be built is a Sign In/Out system. You will need an ABN and any required insurances. The company that you will be doing work for is a publicly listed company.

Core Features and System Architecture

1. Customisable Sign-In and Sign-Out Process
The system must be highly flexible to accommodate the specific needs of each of your 100 sites. This will involve:
• Customisable Fields: The HSEQ team needs a central admin dashboard where they can add, remove, and modify mandatory form fields for each site. This ensures that site-specific questions (e.g., "Are you wearing steel-toe boots?") can be included in the sign-in process.
• QR Code Integration: The system will use QR codes as the primary trigger for both signing in and signing out. These QR codes will need to be unique to each location and easily printable for placement at the dispatch/admin area for each site and one for each evacuation point.
• Device Agnostic Interface: The sign-in and sign-out forms must be accessible from any mobile device, so the user experience must be optimised for various screen sizes.

2. Evacuation Management
An effective evacuation module is critical for safety and compliance. The system will need to:
• Generate a Real-Time Manifest: When the evacuation QR code is scanned, the system must immediately display a live list of all signed-in visitors and staff currently on-site. This list should be accessible to designated fire wardens or HSEQ personnel.
• Clearance and Record Keeping: The system will need a function to mark the evacuation as over, clearing the active list and storing a record of the event for auditing purposes.

3. Staff Directory and Communication
To streamline communication and security, the system will need to:
• Azura Active Directory Integration: The system will need to integrate with our existing Azura Active Directory. This allows visitors to easily select the person they are visiting from an up-to-date staff list, eliminating manual data entry errors.
• Automated Notifications: The system will automatically send an SMS and/or email to the host when a visitor signs in and signs out. This provides real-time awareness and a record of the visit.

4. Data Management and Storage
The system must have a robust and secure data management:
• Centralised Database: All visitor and staff sign-in/sign-out data, along with evacuation records, will be stored in a single, centralised database. This database will be hosted on your DGL Group server, ensuring full control over your data.
• Search and Reporting: The HSEQ team will require access to the database to run reports, search for specific visitor records, and perform audits.

5. Phased Rollout
Based on the scale of the project we will be rolling this out as a two-phase rollout – (we should only need this to be a single build with an option to activate the system for internal use by staff).
• Phase 1: Visitors Only: This initial phase will focus on perfecting the visitor sign-in/out process, including the customisable forms, QR code functionality, and host notifications.
• Phase 2: Staff Inclusion: Once the visitor system is stable and fully operational, the second phase will extend the functionality to include staff. This will likely require linking the staff's daily arrival and departure to the system, which can also be done via QR codes.

If this is something that you can do, please reach out." (client-provided description)