The following table explains the different model types that exist by default in the system.
| Model Type | Purpose | Special Significance/Rules |
|---|---|---|
| Building | A structure within a community that contains lease-able space or floors of lease-able space | Optional. Can be used to house Units. |
| Community | A primary asset that contains all other assets (i.e., work zone/property) | Dictates work flow and some financial settings are configured according to community. Currently only asset that has an address by default and can thus be denoted on a GPS map. |
| Equipment | Primary assets of value that get tracked | Similar to regular assets, but typically used for capital equipment to differentiate the 10% of important assets from the 90% of regular assets that hold little depreciable value. Symptoms and Tasks will show up on SR interface. |
| Floor/Level | An asset that can be used to divide up buildings and house lease-able spaces | Optional |
| Regular Asset | Most assets should be of this type | Primary assets that have tasks and against which work orders are placed. |
| Room/Area | An asset that can be used to subdivide units | Optional. Can have as many nested as desired. Can create a work order against a Room, but cannot display symptoms in the Service Request Interface. |
| Service/Utility | An asset that is used for services such as electricity or water that can pervade a unit and cannot be easily pinned down to a specific location | Appears differently at top of Service Request interface. |
| Unit | Lease-able or “Contractible” container assets | The only asset that can be “leased out” |
If you have the requisite permissions, you can customize the list based on your company's needs by completing the following steps: