The District Setup section of ML Work Orders™ allows District Amin to configure 13 system sections. The system sections are arranged from broadest to most focused. This section will provide definitions for each area as it applies to Work Order management.
District settings lets administrators determine different system wide settings and which they would like to turn on/off.
Organizations are any group that may be completing a work order. Typical ML Work Orders™ customers use their School District as the Organization. However you can also add other Organizations that may fulfill work orders, such as contractors or BOCES (If your District is in New York State.)
Roles are a classification of system user. Each Role is assigned a set of permissions defining what they can see and what they can do in the system.
Examples of possible Roles are: Director of Facilities, Principal, Custodian, Teacher, and Director of IT.
Examples of permissions that might be assigned to Role are: Approve WOs, Assign WOs to others, and View Closed WO Report.
Users are people who are using ML Work Orders™ in some capacity. They may be employees of the school district or external Organizations.
Users can be assigned Roles or they may not have a specific Role and just need to be able to enter a Work Order to the system.
If your District has multiple campuses, you can add them to ML Work Orders™. Campus/Location can be used to tie groups of Buildings together and can be helpful when assigning Work Orders.
Buildings are the individual locations in your district. They may be schools or administrative offices. Most users are assigned to one Building.
Spaces are areas of buildings for which Work Orders may be issued. They include classrooms, offices, fields, hallways, auditoriums, gyms, cafeterias, and more.
What is the reason for the Work Order. Examples include maintenance, inspection, cleaning, and event.
Problem Types are the specific problem to which the Work Order applies. Examples include Audio/Visual, Lighting, Event Set Up, and Custodial.
This is used to define what account is to be charged to complete the work order, if applicable.
Procedures are used for multi-step Work Orders. They are typically assigned to Preventative Maintenance items. An example of procedure is the list of steps required for annual boiler inspection.
Approval paths are used to determine how Work Orders will be approved. They are developed per building and per Work Order Request Type. You can also determine if there are any conditions that would override an approval path.
Dynamic Fields are used to display custom information on Request Forms and on the Asset Details Page. You can also determine if these fields are required or not required to be filled out when they are being displayed.