Sepal Assets

Live in weeks, one department at a time.

Because your assets are already in GIS, there’s no asset import to clean up. Most of the work is deciding how you want to work — and moving the history you want to keep.

  1. Connect GIS

    We connect to your ArcGIS services, register the layers that make up the asset register, map their fields and run the first index. The data-quality report shows odd codes and missing values for your GIS team.

  2. Set up access

    SSO and SCIM with your identity provider, departments, roles, approval thresholds and contractor accounts.

  3. Configure the work

    Asset classes with expected lives and condition methods, inspection forms, work templates, PM schedules and request categories — starting from the public works preset.

  4. Connect the rest

    CitySourced or CommunityCore, the 811 center, Sepal ERP or your finance system, telematics and Power BI, in the order that helps most.

  5. Train

    Role-based courses in the Sepal Assets Academy, with hands-on sessions on your own data for supervisors and crews.

  6. Go live by department

    Public Works first, then Parks and Facilities — or all at once. Open work moves on go-live day so nothing in flight is lost.

Moving from Cityworks or spreadsheets

History is matched to assets by GlobalID or facility ID, staged and validated before anything is saved, and re-runnable without duplicates.

  • Work orders and requests

    With their costs, crews and dates, so lifetime cost and history are there on day one.

  • Inspections and condition

    Prior scores become the starting point for deterioration curves.

  • Resources

    Employees and rates, equipment and rates, materials and stock, contracts.

  • What isn’t in GIS

    Fleet, generators and building systems, with an asset class each.