GEF Monitoring App
GEF developed App to manage and maintain kiosk with Ticket management feature.
What's GEF Monitoring App APK?
GEF Monitoring App is a app for Android, It's developed by Last Local App Solutions author.
First released on google play in 54 years ago and latest version released in 2 years ago.
This app has 10 download times on Google play
This product is an app in Business category. More infomartion of GEF Monitoring App on google play
This is customized developed application of GEF’s NDRS (kiosks) which is built to automate the ticket cycle in order to manage and maintain all Kiosk and Bins remotely.
It caters to below purpose:
1. Provides the ability to distribute information (and predictions) pertaining to the “Condition” of an actual NDRS, or an NDRS location in the form of a Request/Order (ticket).
2) Allows users to create and track status of tickets until closed.
Below are the users who shall be actively using this app.
1. MC (Monitoring Centre)
The (Remote) “Monitoring Centre” utilizes the application to:
b. Observe and report
i. Among those is the “number-of-cages” inside the kiosk
ii. Among those is the type of “Contractor Service” needed
iii. Issues/Assigns “NDRS Condition” related tickets
b. To Targeted Recipients
i. Admin/Super
ii. Monitoring Centre
iii. Area Supervisor
iv. Drivers
v. Contractors
1. Primary
2. Secondary
c. To create, track and manage tickets for PUC, CC, COC, DO, TSC, CST, etc.
2. Area Supervisor
The Area Supervisor uses the application, with same access, and for same view as “Monitoring Centre”. Except he can only see the information pertaining to his territory, and he is on the performance end of the tickets which has been issued.
He also controls assets which he uses to perform the tickets raised-
A. Drivers
B. Trucks
3. Contractor
The contractor may open the ticket on his phone and request additional time to complete the service.
The Monitor can either approve or deny request.
The Contractor responds to a Ticket # (Ticket - that’s just what we’re calling the field which holds all the other service types).
a. CC (Clear Chutes)
b. COC (Clear Overflow Cart)
c. DO (Donations Outside)
He uses the app to perform the job. By definition he should be on location, and therefore the information collection which is part of his job is taking place on location, at the NDRS. We assume that the contractor only needs his cell phone and a data plan at the location.
4. Driver
The driver accepts the ticket and fills out the mileage of his truck and the time he is leaving to do the service. When the driver arrives at each location assigned (there may be one location or multiple locations) he must upload pictures (one when he arrives of the outside and one of the inside, then one of the battery level and when he has completed the service he uploads a picture of the inside and of the outside). He repeats these steps at each location, then when he returns to the warehouse, he unloads, weighs the product,
INPUTS the weights into the app and marks his mileage and time of completion.
5. Technician
The Technician is responds to a Ticket ID which is more complex, and involves transmission of equipment numbers, photos of equipment, etc., which have likely been provided by an earlier (Contractor) “COS” Therefore the precise details required for a “COS” Ticket ID is important.
It caters to below purpose:
1. Provides the ability to distribute information (and predictions) pertaining to the “Condition” of an actual NDRS, or an NDRS location in the form of a Request/Order (ticket).
2) Allows users to create and track status of tickets until closed.
Below are the users who shall be actively using this app.
1. MC (Monitoring Centre)
The (Remote) “Monitoring Centre” utilizes the application to:
b. Observe and report
i. Among those is the “number-of-cages” inside the kiosk
ii. Among those is the type of “Contractor Service” needed
iii. Issues/Assigns “NDRS Condition” related tickets
b. To Targeted Recipients
i. Admin/Super
ii. Monitoring Centre
iii. Area Supervisor
iv. Drivers
v. Contractors
1. Primary
2. Secondary
c. To create, track and manage tickets for PUC, CC, COC, DO, TSC, CST, etc.
2. Area Supervisor
The Area Supervisor uses the application, with same access, and for same view as “Monitoring Centre”. Except he can only see the information pertaining to his territory, and he is on the performance end of the tickets which has been issued.
He also controls assets which he uses to perform the tickets raised-
A. Drivers
B. Trucks
3. Contractor
The contractor may open the ticket on his phone and request additional time to complete the service.
The Monitor can either approve or deny request.
The Contractor responds to a Ticket # (Ticket - that’s just what we’re calling the field which holds all the other service types).
a. CC (Clear Chutes)
b. COC (Clear Overflow Cart)
c. DO (Donations Outside)
He uses the app to perform the job. By definition he should be on location, and therefore the information collection which is part of his job is taking place on location, at the NDRS. We assume that the contractor only needs his cell phone and a data plan at the location.
4. Driver
The driver accepts the ticket and fills out the mileage of his truck and the time he is leaving to do the service. When the driver arrives at each location assigned (there may be one location or multiple locations) he must upload pictures (one when he arrives of the outside and one of the inside, then one of the battery level and when he has completed the service he uploads a picture of the inside and of the outside). He repeats these steps at each location, then when he returns to the warehouse, he unloads, weighs the product,
INPUTS the weights into the app and marks his mileage and time of completion.
5. Technician
The Technician is responds to a Ticket ID which is more complex, and involves transmission of equipment numbers, photos of equipment, etc., which have likely been provided by an earlier (Contractor) “COS” Therefore the precise details required for a “COS” Ticket ID is important.
