Configuring projects for use with Asta Siteprogress Mobile

You must open each project that you want to use with Asta Siteprogress Mobile in Asta Powerproject and configure it as described below.

If you use Asta Siteprogress Mobile to collect field evidence, you can collect field evidence for tasks that appear on the Task Progress screen, but not for tasks that appear on the Ticksheet Tasks screen.

Configure tasks to make them appear in the Asta Siteprogress Mobile Ticksheet Tasks screen

In order for a task to appear as a build stage in the Asta Siteprogress Mobile Ticksheet Tasks screen, you must carry out the following steps:

Create a bar-level user-defined field with the following attributes:
- Object type: Bar.
- User field type: String.
- User field name: Plot_No.
If you are using Asta Enterprise, you create user-defined fields in Server Admin rather than in Asta Powerproject itself.
Display the 'Plot_No' user-defined field in the spreadsheet.
For each bar in the project that represents an individual plot, enter a text string to identify the plot into the user-defined field. For example, you might enter 'Plot 1', 'Plot 2', 'Plot 3', etc into the user-defined field.
Within Library Explorer, create a code library in which to store the code library entries that relate to different build stages. You can give this code library any name, but if you are using more than one Asta Powerproject project, the name of the code library must be the same within each project.
Specify the name of the code library in the Build stage code library name field, on the Ticksheet/Notes tab of the Site Progress Settings dialog.
Within the code library, create a code library entry for each build stage. Give each code library entry a name that accurately describes the build stage.
Assign the relevant build stage code library entries to the tasks in the project that represent build stages.
Associate the appropriate Mobile user with the task.

In summary, a task appears as a build stage on the Ticksheet Tasks screen if:

It is located on a bar against which text has been entered into the 'Plot_No' user-defined field.
A code library entry from the build stage code library has been assigned to the task.
The name of the build stage code library has been specified in the Build stage code library name field, on the Ticksheet/Notes tab of the Site Progress Settings dialog.
The appropriate Mobile user has been associated with the task.

If you want Mobile users to be able to record progress remotely using the Ticksheet Tasks screen, you must ensure that the Progress via duration remaining check box, on the Export tab of the Site Progress Settings dialog, is cleared: if you select this check box, the Ticksheet Tasks screen will not appear in Asta Siteprogress Mobile.

Configure tasks to make them appear in the Asta Siteprogress Mobile Task Progress screen

In order for a task to appear in the Asta Siteprogress Mobile Task Progress screen, you must carry out the following steps:

Associate the appropriate Mobile user with the task.
Ensure that nothing has been entered into the 'Plot_No' user-defined field against the bar on which the task is located.

In summary, a task appears on the Task Progress screen if:

The appropriate Mobile user has been associated with the task.
Nothing has been entered into the 'Plot_No' user-defined field against the bar on which the task is located.

Configure projects and tasks to enable the collection of field evidence

If you use Asta Siteprogress Mobile to collect field evidence, you must structure your projects so that all of the tasks for each individual plot are located within a summary task or expanded task that bears the name of the plot. Provided that a plot's tasks are all contained with a summary task or expanded task that corresponds to the plot, you can create as many summaries or subcharts within the plot's summary task or expanded task to structure the plot's tasks.

You must also ensure that the names of the tasks for which you want to collect field evidence match exactly the names of the corresponding tasks in your field evidence template. For example, if you have tasks called 'Dig Foundations' in your projects for which you want to collect field evidence, the corresponding task in your field evidence template must also be called 'Dig Foundations'. Calling the task 'Digging Foundations' or 'Foundations' will not work. However, the name matching is case-insensitive, so a task called 'Dig Foundations' in your projects would match a corresponding task in your field evidence template called 'Dig foundations'; or one called 'DIG FOUNDATIONS'; or one called 'dig foundations'. Make your task names detailed and unique to ensure that task matching occurs only when it should.

You can collect field evidence on tasks that appear on the Task Progress screen. For each task for which you want to collect field evidence, you must therefore:

Associate the appropriate Mobile user with the task.
Ensure that nothing has been entered into the 'Plot_No' user-defined field against the bar on which the task is located.