What's a Progress Point?
Progress Points are maps to the type of data you collect in Forms, Actions and Memos in APE Mobile.
They help you define how you want data to be defined when you ask the Site Assistant a question.
For example, you might want to report on:
- Hours in timesheets for different people and with different codes - overtime, ordinary, etc.
- Vehicle Inspections completed with different outcomes
- Injuries reported of different types and severity, for different projects or sites.
Note: you must be a Super user with "Manage Templates" access to configure Progress Points.
But why do I need them?
You fill out forms in APE Mobile, so you've got the data - now you want to get answers on the spot - about progress, about safety, about inspections, about time sheets.
Say you're tracking loads of material moved on forms in APE Mobile.
You might want to know the answers to questions about progress. Not only "How many loads?", or "How many loads last week?", or even "How many sand loads this week?"
You want to get instant answers (no Exports or manual data analysis necessary) to questions such as:
You can achieve this using Progress Points, which tell Site Assistant where that specific data is.
How do I create a Progress Point?
Progress Points can be found under the Insights menu.
You'll start on the Progress Points list, containing your existing Progress Points (which you can Edit or Delete). You can also create new Progress Points here, using the green Create button.
An Example Progress Point
We want to be able to ask the Site Assistant about Loads of material reported in our Daily Operations Report form, like this:
But how does the Site Assistant know where to find data relating to Loads, or how they Loads relate to materials (like sand) or equipment (like WT-33)?
We've created a Progress Point called Loads - so now, we can specify the Sources and Attributes.
Below we've chosen the Daily Operations Report template (because we know that's the form where Loads are reported on site). More specifically, we choose the Operator table, and specify the "Lds" column (which is where users fill in the number of Loads).
From here, we add an Attribute. We know we'll want to find out things like:
- How many loads for Jim (or another operator) last week?
- How many loads using LV33 (or other plant/equipment) this year?
Each of these is an Attribute. So, we add a new Attribute called Activity and define the field in which the Activity is specified, in the Daily Operations Report (in this case, it's a field containing a list of materials).
Similarly, we add Attributes for the Operator (which corresponds to the Operator Name field) and the Plant (a list of plant codes).
Note, for each Source (i.e. each different template that Loads are recorded in) you'll need to define which fields the Activity, Plant, and Operator correspond to (if there are such fields).