Prerequisites: 

  • ...TBC


In Cx: 


The following steps will require the information within the 'Schedule of Rates' tab of the template. 

  1. Type 'Schedule of Rates' into the Quick Access Menu and select 'Schedule of Rates'.
  2. Copy the 'SOR code' into the field from the spreadsheet. N.B. This should be a max 10 characters (Max of 8 characters if going to be used in URM due to number of characters the standard procedure carries over). 
  3. Copy the 'Short Description' into the field from the spreadsheet. N.B. This should be a max 50 characters.
  4. Copy the 'Long Description' into the field from the spreadsheet. This can be the same as the short description if required. 
  5. SOR Table should always be set to LWSORBOOK.
  6. Select EACH in the Unit of Measurement. N.B. This is interchangeable with the use of Item - they mean the same.
  7. Add the Trade that is displayed in the Trade ID column of the spreadsheet. (Do not use ANY TRADE without having this authorised by Meg Trevaskis - need to select the correct relevant Trade).
  8. Add the Section Trade that is displayed in the Section Trade ID column of the spreadsheet. N.B. This must always be the same as the Trade. 
  9. Add the Default Priority that is displayed in the Default Priority ID column of the spreadsheet. 
  10. Add the Default Repair type that is displayed in the Repair Type ID column of the spreadsheet. 
  11. If provided, add the Standard Minute Values from the spreadsheet. 
  12. Add the appropriate VAT option as per the spreadsheet. 
  13. Ensure that the User Selectable check box is ticked. N.B. if it is NOT ticked, the user will not be able to select the SOR when raising a job. 
  14. Save.
  15. Access the Price Tab and select New Price.
  16. Add the Labour Price provided on the spreadsheet. 
  17. Ensure that Use Base Price is selected. 
  18. Save. 
  19. If there are contract specific pricings to be added, these must be added separately, if so, select New Price.
  20. Add the contract specific pricing to the Labour Price field and untick the Use Base Price check box. N.B. SORs cannot have more than one Use Base Price added. 
  21. Add the Contract in the Contracts field. 
  22. Save. 


Now add into the Contract Definition for the contracts that have been provided on the spreadsheet - please note that if new/existing SORs are to be added to an existing contract that also exists in Keystone then the contract in Keystone will need to be cancelled and re-raised before the SORs become visible.


URM Changes:

Please ensure this is done in Test and updated. If your work order(s) do not reach source systems then you can check the reason why by checking the audit table in the database, if you need extra support please contact Lucy Myton for extra support with Mulesoft Integration errors.


Create new SORs in URM:


1. Search for Schedule of rates in URM using maintenance menu.

2. Type your SOR Code into search box. Its worth checking its not already in there.

3. Add the SOR in the Schedule Code.

4. Add the Unit.

5. Add the Work Type.

6. Add the Trade.

7. Add the SMV.

8. Select that invoices are required.

9. Select the appropriate action in the Export Behaviour.

10. Update the Description on the next tab.


Use Fault Code mapping document to create the ones you need for your new SORs:


Create new Fault Code in URM:

A. If you are just adding one new SOR follow these instructions:


1.Search for Fault Code in URM using maintenance menu.

2. Create new Fault Code.

3. On the main screen add in Both Fault Code details.

4. Add in Description.

5. Select Fault option on this page.

6. Choose the activity which is generally for repairs or maintenance. 

7. On the Schedules section add in your SOR created previously.

8. Make sure you add the required quantity and make sure you save.

9.Navigate to the standard information section and add in the budget codes required. N.B you may have more than one.

10. Add the required Attribute type for Smoke and CO Detectors for Maintenance.


B. If you are adding multiple SORs use the Fault Code mapping document to generate the code required to update the document and complete update in the database. TBC


Creating new budget information:


FCM - TBC


There are differences for SORs going to the new ROCC Contractor Portal


There are differences for SORs going to ROCC Resolve


ET to update - when new fault codes are created the DETECT attributes need to be added as Ancillary Attributes to make sure they are pushed to the tablet on all jobs for Operatives


Note to be added that any SOR changes/additions are notified to Sarah Pearce, Meg Trevaskis and Neil McAtmney so they are aware for any Keyfax changes.