Follow

Oneserve Data cut - Example

Oneserve Data cut

The data cut is intended to provide a solid base from which to query Oneserve operational data in a safe environment. To allow for any possible queries on said information the export is in the form of a ‘cut down’ SQL server Oneserve instance database. All recipients of this database will be able to query all the data with their own logic.

 

Insight into Oneserve

For the purpose of this document this section will focus only on details relevant to the Data Cut interface. It is included to provide a basic understanding of the high level architecture of Oneserve and to aid in querying the data provided when the interface is live. As such this information is subject to change.

 

WorkLog/Job

The Oneserve architecture regarding orders is shown in the below ERD. Oneserve ‘Jobs’ are built from the top down starting at Worklogs. A Worklog holds high level attributes such as the property, tenant details and a high level description of the work needed. In order for operatives to attend and costs to be attributed a job(s) is created belonging to the Worklog.

The job will have specific descriptions of what work is to be done and of what type that work is (carpentry, electrical etc) how many jobs is required per Work log is down to how the contract is set up to operate.

Data_cut_ERD___Data_Flow_-_WorkLog_Job.jpeg

 

 

Activity/Appointment

Against a job(s) there may be a number of appointments. Appointment attributes are all to do with actual visits to the properties and will include who went at what time and how long for etc.

A job may also be assigned several activities; these are high detail descriptions of individual work aspects based on a schedule of rates e.g. 2 x Fix tap.

Data_cut_ERD___Data_Flow_-_Activity_Appointment.jpeg

 

 

Job Costs

Job costs are assigned to jobs and may also be related to an activity. Alternatively they may have no relationship to an SOR, a late appointment charge for example.

Data_cut_ERD___Data_Flow_-_Job_Costs.jpeg

Job Event(s)

Events can be related to jobs or work logs and are mainly concerned with ad hoc activity. Events can be generated either by the system or by an end user.

Data_cut_ERD___Data_Flow_-_Job_Events.jpeg

Site/Contact(s)

Every job in Oneserve has to be created against a site, each site can have many contacts.

Data_cut_ERD___Data_Flow_-_Sites_Contacts.jpeg

Survey(s)

Data_cut_ERD___Data_Flow_-_Survey_s_.jpeg

Stock Management

Data_cut_ERD___Data_Flow_-_Stock_Management.jpeg

Activity (SOR) and Supplier Costs

Data_cut_ERD___Data_Flow_-_Activity__SOR__and_sup_costs.jpeg

 

Calendar and Holidays

Data_cut_ERD___Data_Flow_-_Calendar_Holiday.jpeg

 

Resource Working Time

Data_cut_ERD___Data_Flow_-_Resource_Work_Time.jpeg

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request