Case study

Turning installed-base data into preventive service action for a drilling-equipment manufacturer.

Used and replacement filters arranged inside the weathered service bay of an installed drilling rig
Drilling-equipment manufacturer

Carric turned runtime and service evidence into governed maintenance cases with the correct kit, scope, schedule, authority, and completion trace.

The operating constraint

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.

01 · Service dueRuntime and schedule indicated upcoming maintenance

Rig identity, configuration, ownership, runtime, and interval data could arrive through different sources.

03 · Work confirmedParts, work order, technician, customer, and next interval were updated separately

The operation needed to prove completion across every authoritative record.

Full system view

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.

Use a business email. Free and disposable addresses are not accepted. By continuing, you agree that Carric may contact you about this case study. Privacy policy.

How installed-base evidence becomes governed preventive service

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.

01 · Event opened

Runtime and maintenance rules create one rig-specific case

Serial, configuration, owner, location, runtime, history, and interval retain source and freshness.

02 · Readiness checked

Observed diagnostics, kit, stock, technician, and customer window are assembled

The system separates standard scope, missing evidence, and technical conditions requiring review.

03 · Scope approved

Service and technical authority remain explicit

The Service Manager approves scope and schedule. Qualified technical owners handle diagnostic escalation.

04 · Completion confirmed

Work and source systems close the service loop

Parts, customer, work order, technician evidence, completion, and next interval remain connected.

The Service Manager approves scope and schedule. Qualified technical owners handle diagnostic escalation.

The system may prepare the service plan from observed records. It cannot predict a failure, diagnose a condition, authorize safety-sensitive work, or confirm return to service automatically.

What changed operationally

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.

01

Installed-base records current

Rig identity, configuration, owner, runtime, location, modifications, and history stay synchronized.

02

Service readiness visible

Maintenance rules, observed diagnostics, kit, parts, technician, and customer availability are checked together.

03

Technical limits preserved

Observed conditions are routed for qualified review without being turned into unsupported predictions.

04

Completion trace complete

Parts, work order, technician evidence, customer confirmation, and next interval remain linked.

Where this pattern appears in your installed-base operation

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.

Book a 30-minute fit call No formal brief is required.