Rig identity, configuration, ownership, runtime, and interval data could arrive through different sources.
Case study
Turning installed-base data into preventive service action for a drilling-equipment manufacturer.

Carric turned runtime and service evidence into governed maintenance cases with the correct kit, scope, schedule, authority, and completion trace.
The service interval was known, but planning the work still required the exact rig, observed evidence, parts, technician, and customer window.
One of our clients, a drilling-equipment manufacturer, supports an installed base of rigs with different configurations, owners, runtime, operating conditions, modifications, service histories, maintenance schedules, parts requirements, and customer availability. Preventive service protects continuity only when the plan reflects the actual installed unit.
Before Carric, service teams compared runtime feeds, customer reports, maintenance schedules, service history, diagnostic records, kit lists, parts inventory, technician capacity, and customer calendars. Upcoming work was visible, but a complete plan still depended on manual consolidation and follow-up across several sources.
One 1,000-hour service event exposed the gap. The standard kit was available and the service window was approaching, but one observed diagnostic record needed qualified confirmation before the scope could be approved. The system could not treat that record as a predicted failure. It needed to preserve the observation, separate standard maintenance from technical escalation, and keep the customer commitment current.
Carric built an installed-base maintenance and service system. It synchronizes rig identity and runtime, opens the correct maintenance case, assembles service and observed diagnostic evidence, validates kit and parts readiness, prepares scope and schedule options, and routes the technical condition to the appropriate owner. The Service Manager approves scope and schedule. Completion, parts, customer, work-order, and next-interval updates remain connected.
One unresolved condition could change scope, parts, technician, or schedule.
The operation needed to prove completion across every authoritative record.
See how one installed-base service event moves from runtime signal to confirmed preventive action.
Open both screens to inspect rig evidence, maintenance criteria, observed diagnostic condition, kit readiness, human authority, and completion trace.
Service Coordinator sees which cases can move, which need evidence, and which require human review.
The queue organizes maintenance planning by operating consequence, owner, decision window, and current state.

Every service event now connects the actual rig, approved scope, parts, schedule, and completion record.
Carric organizes observed evidence and standard maintenance work. It does not predict failure, diagnose a condition, or authorize safety-sensitive work automatically.
Preventive service begins from the installed unit and ends with a confirmed next interval.
The service team sees the exact evidence, scope, parts, customer window, authority, and completion state for every event.
Installed-base records current
Rig identity, configuration, owner, runtime, location, modifications, and history stay synchronized.
Service readiness visible
Maintenance rules, observed diagnostics, kit, parts, technician, and customer availability are checked together.
Technical limits preserved
Observed conditions are routed for qualified review without being turned into unsupported predictions.
Completion trace complete
Parts, work order, technician evidence, customer confirmation, and next interval remain linked.
Which preventive-service plans still require coordinators to reconstruct the equipment and customer context by hand?
Bring one recurring service interval, the installed-base sources behind it, and the approvals required. We will use the first call to map the connected maintenance capability.