| CPC G06F 16/9537 (2019.01) [G06F 3/0482 (2013.01); G06F 3/04845 (2013.01)] | 18 Claims |
|
1. Computer implemented method for configuring and operating a workflow automation data structure for a vendor having a plurality of customers each with a geographically dispersed destination serviced by a plurality of mobile workers comprising:
providing a cloud-based or web-based server coupled to a data store;
providing each worker, of the plurality of workers, with a mobile device, the mobile device being a cell phone, a tablet or a computing device, providing a communications network which communicatively couples the mobile device to the server, each mobile device having a camera, a geolocation module generating geolocation data based upon the location of the mobile device, and an interactive display screen with perceptual inputs including at least a textual input and a tactile input;
initially configuring and storing in the data store for one customer of the plurality of customers:
an interactive worker main menu mobile device display with a horizontally bifurcated user interface (UI) display with first and second UI segments, the first UI segment displaying static displayable datasets including at least: (a) a customer dataset unique to the one customer Including customer name, destination address and contact data, and (b) a customer-related job or project type which is one job or project type (Type) of a plurality of job or project types, the one Type being preselected dependent upon a request for goods or services by the one customer;
the first UI segment having a changeable displayable worker current-status indicator dataset based upon a real-time (RT) geolocation dataset captured by the server from a respective mobile device of an assigned worker of the plurality of workers, the assigned worker being one of a plurality of assigned workers engaging the interactive worker main menu mobile device display;
the second UI segment having a plurality of worker interactive displayable datasets including (i) at least three required worker action items (R-actions) of a plurality of R-actions, all R-actions only being sequentially actuatably selectable by the assigned worker, and (ii) at least one optional worker action item (O-action) of a plurality of O-actions, the at least one O-action being actuatably selectable as needed by the assigned worker;
the at least three R-actions required to fulfill the one Type, the at least three R-actions including: a first R-action representing an in transit to destination task event by the assigned worker, a second R-action related to a worker fulfillment task event of the one Type, and a third R-action representing either a completion action or a close action task event by the assigned worker;
the at least one O-action being optionally selectable by the assigned worker as supplement fulfillment task events for the one Type for the one customer;
a plurality of interactive sub-menu datasets including at least one of: (m) a work to perform (WP) sub-menu dataset including a WP textual input sub-segment, WP photo capture input, a WP photo image display sub-segment, or a WP tactile signature input sub-segment, (n) one goods-related (GR) sub-menu dataset from a group of GR sub-menu datasets including a parts-installed sub-menu dataset displaying a selectable list of potential parts to be installed, a parts-to-order sub-menu dataset displaying a selectable list of potential parts-to-order, and a goods-available for sale sub-menu dataset display a selectable list of potential goods for sale, or (o) a services to perform (SP) sub-menu data dataset including at least a SP textual input sub-segment or a SP sub-menu dataset displaying a selectable list of potential services to be provided and the installed;
the at least one of WP sub-menu, the one GR sub-menu, and the SP sub-menu related to the one Type and hierarchically below the at least three R-actions or the at least one O-action;
a completion/close action (CC) interactive sub-menu dataset for the completion action or close action task event, the CC sub-menu dataset including at least one of: a CC textual input sub-segment, a CC photo capture input, a CC photo image display sub-segment, or a CC tactile signature input sub-segment;
a time constraint and a location constraint which are both unique to the one customer, the time constraint based upon a respective temporal customer (Time) dataset imposed by the one customer as one destination limit, and the location constraint based upon a respective compulsory destination access or egress limitation (LOC) dataset based upon another destinational limit imposed by the one customer;
after initially configuring the data store, the server, interactively with the assigned worker's mobile (AW mobile) device;
generating a vendor back office multi-worker time-blocked schedule display for all assigned workers of the plurality of assigned workers associated with scheduled jobs or projects, each assigned worker of the plurality of assigned workers being displayed by a worker or task identifier in a respective assigned worker cell in the time-blocked schedule display in addition to customer or task data associated with each respective assigned worker, the time-blocked schedule conforming to the Time dataset for the one customer;
for the respective assigned worker, accepting a respective assigned worker actuation of the first R-action presenting the in transit to destination task event;
monitoring and accepting an updated RT geolocation data from the AW mobile device;
for the respective assigned worker, color-coding the respective assigned worker cell in the time-blocked schedule display with a first color-code upon the respective assigned worker's actuation of the first R-action showing the in transit task event;
for the respective assigned worker, changing the changeable displayable worker current-status indicator dataset on the AW mobile device to indicate the in transit event based upon an updated RT geolocation automation dataset transmitted to the AW mobile device;
for the respective assigned worker, changing the color-coding on the AW mobile device with a first R-action UI displayable dataset based upon the updated RT geolocation data;
for the respective assigned worker, accepting respective assigned worker actuation of the second R-action representing the worker fulfillment task event and: (q) further color-coding the respective assigned worker cell with a second color-code upon the respective assigned worker actuation of the second R-action, (r) downloading at least one or more of the WP sub-menu dataset, the GR sub-menu dataset or the SP sub-menu dataset to the AW mobile device, (s) accepting and storing, in the data store, corresponding second R-action data input, by the respective assigned worker into the AW mobile device, one or more of a supplemental WP sub-menu (sWP) dataset, a supplemental GR sub-menu (sGR) dataset or a supplement SP sub-menu (sSP) dataset, and (t) changing the color-coding on the AW mobile device with a second R-action UI displayable dataset based upon the respective assigned worker actuation of the second R-action and the downloading at least one or more of the WP sub-menu dataset, the GR sub-menu dataset or the SP sub-menu dataset;
accepting the respective assigned worker's optional selection of the at least one O-action and, in that event, downloading one or more of the WP sub-menu dataset, the GR sub-menu dataset or the SP sub-menu dataset to the AW mobile device, then accepting and storing in the data store corresponding O-action data input data by the respective assigned worker as sWP dataset, sGR dataset or sSP dataset;
in the event of the respective assigned worker optional selection of the at least on O-action, generating invoice data based upon the sWP, sGR, and sSP datasets;
accepting the respective assigned worker actuation of the third R-action representing either a completion action or a close action task event and; (v) color-coding the respective assigned worker cell with a third color-code, (w) downloading or activating the CC sub-menu dataset on the AW mobile device, (x) accepting and storing, in the data store, a corresponding third R-action data input, by the respective assigned worker which is one or more of a supplemental CC textual input (sCC-text); a supplemental CC photo input (sCC-photo), or a supplemental CC tactile signature input (sCC-sig), and (y) changing the color-coding on the AW mobile device with a third R-action UI displayable dataset based upon the storage of the one or more of the sCC-text, the sCC-photo, or the sCC-sig;
downloading supplemental invoice data to the AW mobile device based upon one or more of the sCC-text, the sCC-photo, or the sCC-sig.
|