Website & App Development

1) SUPER ADMIN – OWNER of the APP, source code and Mother server -Super admin can assign multiple sub admin with completely different branding and user interface controlled by login credentials – Sub-admin is a company which is the end user. -Each sub-admin can assign admins within their user interface Considering the first sub admin to be a Restaurant chain company - A - Departments – a) Operations- Sub Sub-admin (assigned by Sub-admin) i) Chefs – Field user (Assigned by sub-sub admin) ii) GMs- Field user (Assigned by sub-sub admin) iii) Safety & Hygiene – Field user (Assigned by sub-sub admin) b) Maintenance & Engineering- Sub Sub-admin (assigned by Sub-admin) i) Supervisor – Field user (Assigned by sub-sub admin) ii) Technician – Field user (Assigned by sub-sub admin or Supervisor) 2) Operations workflow. - Chef/ Safety & Hygiene user interface is linked to login credentials- based on the username and password entered, the team will get the user interface for Chefs or Safety & Hygiene. - Chefs and Safety team have a daily routine form to be filled out which will be shared. - Chefs and Safety team can also raise a ticket which will be notified to Maintenance & Engineering team for breakdown or malfunction and once the Maintenance team fixes that issue and close the ticket, it will automatically close the ticket with Operations too. - Similarly, General Managers (GMs) or Asst GMs will log in and either raise a ticket for issues based on the form or complete their daily routine checks and close the task for the day. - Any ticket on the app not closed or at least commented with a time frame to fix the issue within 24 hours will get escalated to the sub-sub admin of that field user. - Report for operation can be generated in PDF or Excel as required by the Sub Sub-admin, report can also be sorted out based on day, field username, open tickets, and maintenance issues within the Operations interface. 3) Maintenance & Engineering workflow - Supervisor and field technician user interface to be linked to the login credentials. - Sub-sub admin will assign tasks (corrective actions) to the supervisor on a daily basis and also receive tickets escalated by the operations and assign them to Supervisor directly. - The supervisor will have a list of daily routine tasks to finish (checking and reporting) which he will assign to the technician on daily or weekly basis. - Also logging in the app will also record as the attendance sheet, after logging in within 30 minutes if the routine reporting did not start then Sub sub admin & supervisor will get a notification that technician A/B has not started yet. - All photos are to be captured only within the app with timestamp and geolocation captured. - Supervisor or Sub-sub-admin can add more restaurants and assign daily preventive maintenance task forms within each restaurant to complete, daily preventive maintenance task is assigned once and gets copied across all days, weeks, months, and years. - Technicians will also have access to request spare parts on the app and once requested that will be an open ticket for the supervisor and maintenance sub-sub-admin, once procured and installed technician will close the ticket and will automatically close the ticket across all users, if procurement is from 3rd party supplier then a PO to be uploaded by Maintenance sub-sub-admin to keep the ticket in ongoing mode, once material received and installed by a technician that ticket will be closed all across. - Any issue reported as critical/emergency by operations any user or maintenance sub-sub-admin will override the daily preventive maintenance tasks and become the priority for the supervisor or technician to complete. - Reporting should be in PDF format with photos of before and after and the checklist of preventive maintenance done. Sorting should be restaurant-wise, technician-wise, issue-wise. - Commercial reporting should highlight all spare parts procured and their bills, PO issued, etc for a month.