Maintenance Profiles
Define PM schedules with components, events, and cost forecasts for each equipment model.
Overview
Maintenance Profiles are the core planning tool in MineSync's lifecycle module. A profile defines the complete maintenance schedule for an equipment model -- which components need servicing, at what hour intervals, and at what cost. Profiles are then assigned to individual fleet vehicles to drive forecasting and scheduling.
Key Concepts
- Profile -- A named maintenance plan tied to a specific OEM and equipment model (e.g. "CAT 793F -- Standard PM Schedule").
- Components -- Machine components tracked within the profile (e.g. Engine, Transmission, Final Drive), each with a target replacement hour interval and default cost.
- Events -- Scheduled maintenance activities within the profile. Event types include:
- Component Replacement -- Full component swap at a target hour interval
- Preventative Maintenance -- Routine PM tasks
- Midlife Repairs -- Intermediate rebuilds or refurbishments
- Running Cost -- Ongoing operational costs
- Allocation -- Whether an event is used for Forecasting or Tracking Only.
- Machine assignment -- Vehicles from the fleet are assigned to a profile so the system can forecast their maintenance needs based on current hours.
How to Use
Profile list
The profiles list page shows all profiles with their OEM, model, and counts of assigned vehicles, components, and events. Use the search bar and OEM/model filters to find profiles. The list supports pagination and sorting by name, OEM, model, last updated date, or number of assigned machines.
Creating a profile
- Click Add Profile.
- Enter a Name for the profile.
- Select the OEM and Equipment Model (both required).
- Optionally add a Site and Notes.
- Click Create.
Profile detail page
Click a profile name to open its detail page with three tabs:
Overview tab
- Shows profile metadata (name, OEM, model, dates).
- Displays summary metrics: component count, event count, assigned machines, and estimated lifecycle cost.
- Lists assigned machines with fleet ID, model, site, status, and current hours.
- Use Assign Machines to bulk-assign vehicles to this profile, or click X to unassign.
Components tab
- Add components by specifying a name, location (position on the machine), target hours, and default cost.
- When a component is added, a default Component Replacement event is automatically created.
- Edit or delete components as needed. Deleting a component also removes its associated events.
Events tab
- Add events linked to components with activity type, event type, allocation, target hours, and estimated cost.
- Events can be linked to other events to form maintenance chains.
- Each event can include part numbers, source of supply, and comments.
Exporting and importing
- Export All -- Download all profiles as JSON (Admin only).
- Export Single -- Download a single profile as JSON.
- Import -- Upload a JSON file to bulk-import profiles with their components and events. The import validates OEM/model references against master data and reports per-profile success or failure.
Bulk import components and events
For a single profile, use the Bulk Import feature to upload components and events in batch. The system automatically creates catalog component and machine position records if they don't already exist.
Common Questions
What happens when I assign a vehicle to a profile?
The vehicle's profileId is updated to reference the profile. The forecasting system uses the vehicle's current hours and the profile's event intervals to project future maintenance dates and costs.
Can a vehicle be assigned to multiple profiles?
No. Each vehicle can have at most one profile assigned. Assigning a new profile replaces the previous one.
Who can manage profiles?
Admin, Planner, and Technician roles can create profiles and manage components/events. Only Admin and Planner roles can delete profiles. Export/import is restricted to Admin users.
What is a "linked event"?
Events can be chained together via the linked event field. For example, a Midlife Repair event at 15,000 hours might be linked to a Component Replacement event at 30,000 hours, indicating they are stages of the same component's lifecycle.