Upvise Documentation
Overview:
The documentation is divided into four main areas of information:
https://webwbdoc.atlassian.net/wiki/spaces/UPVISE/pages/1222148099 for information about modules and features available in Upvise and how they interact with Workbench.
https://webwbdoc.atlassian.net/wiki/spaces/UPVISE/pages/1222246411 for information specific to the civil field.
https://webwbdoc.atlassian.net/wiki/spaces/UPVISE/pages/1221951516 for information specific to construction businesses.
for information related to servicing, maintenance, and hire companies.
The specialised areas will reference back to the general information and will assume the general information is understood. There will also be links to the Workbench as needed.
What is Upvise?
Upvise is a third-party tool that Workbench partners with which provides proven mobility in the field. This includes a disconnected model where users can record data and sync to the database upon reconnection to the internet. Upvise has its own hosting environment which is separate to our AWS environment. Upvise is a software as a service (SaaS) and Workbench subscribes to monthly licences on behalf of our clients which is then included in our billing.
Workbench synchronises companies, contacts, jobs, plant, etc. to Upvise. We bring back selected transactional data captured in and transactional information e.g. , Plant Issues, Dockets, Job Outputs, Billings, depending on your use-case scenario.
Upvise is a comprehensive product in its own right but Workbench has decided to strategically position some vertical market uses to enhance mobility in these areas:
Job Scheduling (Servicing/Reactive & maintenance works)
Resource scheduling for People & Equipment
Equipment Servicing and Maintenance
Safe Work Templates (SWMS)
Expense Claims
Daily Diary for transactional data capture (Project hours, dockets, stock transactions etc)
Asset management
Sales & deals (Quotes)
Our transaction offering has been built into Upvise in the form of form-entry data that generates native Upvise transactions from any of the above scenarios. When transactions are being generated in Upvise Workbench is always the host. For example, timesheets entered in Upvise will be exported to Workbench and form part of the users timesheet in Workbench.
