Solution Engineering43 tasks
Design Field Service Solutions
Turns a Field Service use case (scheduling, crews, assets, technician and dispatcher agents) into a design: a plan, a data model, a pressure test of the design and a phased build sequence ready for approval.
Method
How MeshMesh does it
- Reads the use case or support case to fix the scope. In one case, a support case raised several Field Service problems: splitting crews mid-day, scheduling around equipment and reducing license cost.
- Proposes a data model. The work centres on Work Orders, Service Appointments and Asset Lifecycle Management. In the support case, the plan covered crew objects, equipment modeled as service resources with skill aggregation, and a Contact-based licensing approach for ground crew.
- Pressure-tests the design from an end user's point of view, lists friction points, then runs a second pass showing which were resolved and which were new.
- Captures design decisions and updates the plan.
- Revises the plan when the user rejects a direction. In a demo design, the user turned down an irrelevant customer, and MeshMesh rewrote the golden-path plan around a fictional one.
- Stops for the user to approve the plan before any build begins. Some plans also wait on an org connection.
Products
Products and features it works with
Bars show how many of this capability's tasks touched each product.