Visit Boris website Job definition
Office based job creation

Office based job creation

Job definition that creates the above screen

Job definition that creates the above screen

Job definition define what information is prompted for when office users input a “job” of some description into the system. You only need a job definition if you are using the job dispatch module (rather than device users creating ad hoc forms on site).


When a job is created on Boris it will use a particular job definition or job type. Typical job definitions are “Job”, “Service”, “Installation”, “Delivery”, “Collection”, “Callout”, “Project” and “Work order”. Job definitions are a flexible way of sending tasks or information to mobile devices, so those typical examples can be supplemented with less obvious examples like “Weekly timesheet summary”, “Operative document”, “SHE alert” and “Clock card”.

Jobs created on the system will, by default, contain:
  • Customer
  • Location
  • Date
  • User (or Group)
The Job definition is used to specify any other information that the office user needs to input when creating or assigning the job. For example, contact person, job description, urgency, alarm code, notes (for office), notes (for user), job number and suggested equipment.

The additional items in the job definition can be text entry, list items, contacts, phone numbers or automatically generated.

The job items can be split into multiple pages if required.

Over and above the job definition items, the job definition contains a wide range of settings relating to how jobs of this type are processed and displayed by the system.

In many cases jobs are associated with a single template, the form used on the mobile device when a job of this type is opened. Once this form and any supplementary forms arising from this are completed, the job is closed. Alternatively, the job definition may be associated with a set of forms which the user picks from as required, the job being left open until closed by the office. Such “open ended” jobs may have a “start of day” form/template associated with them, a form that requires completion on every day of the job.

The in-built default job items (customer, location, user, date) can be hidden or preset, and the text associated with these items can be changed. For example, “Location” might be replaced by “Project”, and “User” by “Engineer”.

The Boris web site displays screens of jobs at varying statuses. The information shown in these lists can be customized. For example, the job number and urgency could be shown alongside the main job details or the customer could be hidden.

Jobs can also be viewed on the graphical planner. Colour coding of the job at various statuses is defined through the job definition.

Job definition actions are automated actions or options that arise at various stages of a job’s life cycle. An action could be something like “send an e-mail to the assigned engineer when a job is allocated” or they could be something like “if a job is at status ‘awaiting invoicing’ then give the user an option to mark it as invoiced”.
Device based job handling - downloaded job or ad hoc on site

Device based job handling - downloaded job or ad hoc on site

See Also

Concepts

 

 


Parts copyright 2014 Boris Software Ltd. Parts copyright 2014 Firetronic Software Ltd. Parts copyright 1998-2014 Cadence Computing Ltd. All Rights Reserved.

Menus, prompts, fields and options are from a typical installation - some items may not appear as shown. Please contact Boris support for information on additional features.