Processes
A Process is a collection of Tasks, prescribed in a logical sequence. Using Processes, you can standardise these combinations of Tasks and repurpose them across business units, or on multiple projects, or in multiple locations within a project.
General Overview
The steps to creating a usable Process:
- Create a Business Process and add Tasks to it.
- Assign the Business Process to a Project.
- Assign each Task to an organisation.
- Assign the Project Process to a Location or Asset.
- When you assign a Business Process to a Project, the system uses the template to generate a Project Process and retains the template for use again later.
- Processes which have one or more Tasks not yet assigned to an organisation are indicated in red font and these cannot yet be assigned to a Location.
- For a given Process, once you assign each Task to an organisation, the Process name changes color from red to grey font and you can then assign the Process to a Location.
- Assigning a Process to a Location is what makes the Tasks become actionable.
Creating Process templates
Typically business-level administrators create and configure Process 'templates' in the Business Processes setup area. Changes made in Business Processes affect only the templates.
Access Business Processes from the drop down that appears when you click on your name in the upper right corner.
Before you get started
Business Process templates can be assigned to more than one Project, whereas Project Processes can only be copied to the same Project. For this reason, Viewpoint highly recommends you start most if not all your organisation's Processes as Business Process templates, which can be repurposed at any time, and across any number of Projects.
Get started
- Create a Business Process and then assign it to one or more projects. Field View uses the template to create a new Project Process, but retains the template for future use.
- If you're certain a Process will only be used on one project, you may opt to create a Project Process pertaining to just that project.Note: Users with project-level access cannot create business-level templates. Even still, rather than creating a Project Process, it is preferable that a user with business-level access be tasked with creating a Business Process template.
Either way, once you have a Project Process, you must assign each Task to an organisation and then assign the Process to one or more Locations in order for field workers to use it.
Viewing and updating deployed Process Tasks
Once you assign a Project Process to a project Location, permissioned web and mobile users can begin to take action on the collection of Tasks. Once a Process Task is moved beyond its initial state, the only part of it you can modify is the description.
