Manage Maintenance Contractors
Control vendor work, quotes, bills and SLAs.
Improve & Manage Maintenance Contractors
Contractors touch the same assets your in-house team maintains, so their costs, coverage and repair status need to sit inside one CMMS record rather than a separate spreadsheet or WhatsApp thread. AssetAI treats every AMC vendor, warranty date and outside repair as part of the asset's maintenance history — not a side process.
How Coverage and Cost Are Tracked
Every asset carries its AMC details — vendor, start/end dates, contracted cost, and a service schedule set to monthly, quarterly, half-yearly, or yearly — next to its warranty dates and any free-text notes. From this, the system computes a live coverage status for each asset using a fixed precedence: in warranty overrides under AMC, which overrides expired, which overrides no coverage recorded. There's no manual lookup required before a technician or planner acts.
- When a service call is raised, coverage (warranty, AMC, or paid) is stamped automatically.
- The vendor field pre-fills from the asset's AMC vendor, and falls back to its supplier if no AMC vendor is set.
- Outside-service line items are priced from the Service master, not typed in freehand, so contractor charges stay consistent across work orders.
This removes the guesswork of "is this job still under warranty" or "which vendor do we call" from the person raising the ticket, and keeps that decision consistent across shifts and plants.
Running the Repair Through to Closure
Once a contractor is engaged, the job moves through a defined external-repair loop: Requested, Visited, Quoted, Quote Approved, In Service, Completed, Billed, Bill Passed, Closed — with Cancelled available at any point. Each transition is timestamped automatically, giving you a full trail of when the vendor was engaged, when they quoted, and when the bill was passed, without anyone maintaining a separate log.
- Contractor cost posts directly to the work order alongside parts and labour, so vendor spend sits with the specific repair and asset — useful when reviewing cost by asset over time.
- The same closure gate that applies to internal breakdown and corrective work applies here: a BM/CM work order cannot be completed or closed without a recorded failure cause and remedy, even when a contractor did the physical repair.
- The asset record keeps an external technician contact and a service-vendor field for reference, so the next planner doesn't have to dig through past tickets to find who to call.
What This Deliberately Leaves Out
AssetAI records the transaction and the trail — it does not try to be a vendor-management or procurement system. There's no SLA field or breach flag, no rules-based quote-approval threshold, no vendor scorecard, and no vendor-facing portal — every status change is logged by your own staff, not the contractor. That keeps the data model simple and auditable rather than adding workflow your team would need to police. If you're comparing this against a broader maintenance strategy, it's worth reading how this fits alongside TPM practices, or how manufacturing plants across Indian industry typically split internal versus contracted repair work.
For the full picture of how contractor tracking fits with the rest of the platform, see all features or browse other use cases. To see it running against your own asset list and AMC contracts, book a 30-minute demo.
Manufacturing plants in India routinely run a mix of in-house crews and third-party contractors — for calibration, specialised repairs, or equipment still under an OEM's AMC. AssetAI keeps that mixed workforce inside one system so the record of who did what, under what coverage, and at what cost never depends on a phone call or a paper file.
Setting Up a Contractor-Covered Asset
Before you raise the first service call against an asset, a few fields are worth getting right at setup, since they drive everything downstream:
- AMC vendor and dates — enter the vendor name, contract start/end, and the agreed cost so coverage status computes correctly from day one.
- Service schedule — set the AMC's servicing frequency (monthly, quarterly, half-yearly, or yearly) so planned visits show up against the asset rather than living in a contractor's own calendar.
- Warranty dates — record these alongside the AMC, since warranty takes precedence over AMC in the coverage logic.
- External technician contact and service-vendor field — keep these current on the asset record so whoever raises the call knows who to phone, even though AssetAI doesn't push a notification automatically.
Getting these four right at onboarding means every subsequent work order inherits accurate coverage and vendor data instead of a planner re-typing it each time.
Where This Fits Alongside In-House Maintenance
A contractor-executed repair isn't a separate process from breakdown or corrective maintenance — it runs through the same work order structure covered across AssetAI's features, which is deliberately different from managing contractors in a spreadsheet next to a separate CMMS for internal work. Because contractor cost posts to the same work order as parts and labour, an asset's total repair cost is visible in one place regardless of who fixed it, which matters when you're reviewing input to metrics like OEE or comparing spend across industries with different mixes of outsourced servicing.
Common mistakes plants make when they keep contractor data outside the CMMS:
- Coverage status goes stale — a spreadsheet doesn't recompute whether an asset just moved from "under AMC" to "expired," so a paid repair gets logged as covered, or vice versa.
- Vendor cost sits in accounts, not against the asset — making it hard to see whether a specific machine's contractor spend is climbing over time.
- The failure cause and remedy get skipped for outsourced jobs — because the closure discipline applied to internal work orders doesn't extend to a WhatsApp thread with a vendor.
AssetAI closes each of these by keeping the AMC, the coverage computation, the work order, and the closure gate on failure cause and remedy inside one record — the same discipline you'd apply under a structured maintenance approach like TPM, just enforced by the system rather than by process discipline alone.
Where to Look Next
If you're evaluating how contractor management fits with the rest of a plant's maintenance operation, the use cases index covers related scenarios such as work order management and asset history tracking. Plants working toward a formal quality or maintenance standard can also check ISO & standards for how AssetAI's record-keeping aligns with audit expectations. For rollout cost, see pricing, or book a demo to walk through how an existing AMC vendor list would map into the system before you commit to switching over.
Manage Maintenance Contractors FAQs
How do I track which contractor is responsible for each asset's maintenance?
AssetAI records the contractor relationship directly on the asset through an AMC (Annual Maintenance Contract) record that stores the vendor name, contract dates, cost, and service schedule. When you raise a service call for that asset, the system automatically stamps the correct vendor and coverage type—warranty, AMC, or paid service—so you always know who is responsible and what terms apply. You can also store an external technician contact and service vendor field on the asset for quick reference.
What happens when a contractor submits a repair quote and I need to approve it before work starts?
The system runs a full external-repair workflow with defined states: when a contractor visits and provides a quote, the work order moves to the "Quoted" status. You review it, then transition it to "Quote Approved" before work begins. The full cycle tracks Requested → Visited → Quoted → Quote Approved → In Service → Completed → Billed → Bill Passed → Closed, with automatic timestamps on each transition so you have a complete audit trail. This ensures repairs don't proceed without your sign-off.
Can I see contractor costs alongside the parts and labour on a single work order?
Yes. AssetAI posts the contractor's service cost directly to the work order alongside any parts and labour charges, so all vendor spend is visible together tied to that specific repair and asset. When pricing external-service lines, the system pulls rates from your Service master rather than accepting free-text amounts, which keeps contractor costs consistent and auditable across /features.
What coverage priority does the system use when an asset has both warranty and an active AMC?
The system applies fixed precedence: in-warranty status beats an active AMC, then expired coverage, then no coverage recorded. When you raise a service call, AssetAI computes the live coverage status per asset using this hierarchy and stamps it automatically, so the highest-priority coverage type is always applied first and the correct vendor pre-fills on the work order.
Do contractor work orders require the same closure documentation as internal repairs?
Yes. Even when a contractor executes the repair, you cannot complete or close the work order without recording a failure cause and remedy—the same gate applies to both internal and external work. This ensures every repair, regardless of who performed it, is documented with root cause information that you can use for asset history and preventive maintenance planning.
How does the system handle the service schedule for contractors—do I have to re-enter it each time?
No. You record the contractor's service schedule once on the AMC—monthly, quarterly, half-yearly, or yearly—and the system holds it alongside the contract dates, cost, warranty dates, and vendor name. The schedule stays on the asset record so you have a single source of truth for when external service is due, and it integrates with your overall maintenance planning across /use-cases.
If a contractor's performance drops—delayed job completions, poor quality—how do I pause or terminate their access in AssetAI without disrupting active work orders?
You can mark a contractor as "inactive" in the system, which prevents new work orders from being assigned to them. Existing active orders continue normally until closed. For immediate termination, you'll need to reassign pending jobs to another contractor. AssetAI doesn't auto-pause; you manage status changes manually to maintain control over transition timing and handover.