Reference · built on requestOperator by FibricFleet, routes & field

Parts Readiness

Checks each scheduled job's required parts against van stock and warehouse levels and proposes a pick, transfer, or reschedule.

Request accessPricing ↗

About

Parts Readiness is an operator job for tomorrow's jobs and the parts they need. It reads each scheduled work order and the products estimated on it, the technician booked, and the truck that technician draws from. It reads what that truck holds, what the warehouse holds, and what is on order.

A job whose parts are not on the truck is matched to the nearest stock: a pick from the warehouse before the technician leaves, a transfer from another truck, or a purchase order if nothing is available. Where nothing can arrive in time, it proposes moving the appointment. The service manager sees each job with its gap and the fix proposed, and approves. Transfers and purchase orders are then created once in the field service system, and the stock as read is kept with the decision.

This is a reference listing. It documents what Fibric would read from Parts Readiness and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Work order product lines in Dynamics 365 Field Service: msdyn_workorderproduct with msdyn_product, msdyn_estimatequantity, msdyn_linestatus Estimated or Used, and msdyn_allocated
  • Stock per warehouse, technician trucks included, from msdyn_productinventory: msdyn_qtyonhand, msdyn_qtyavailable, msdyn_qtyallocated, msdyn_qtyonorder, and msdyn_reorderpoint
  • Bookings that say which technician, and so which truck, takes the job: bookableresourcebooking and the resource's default warehouse
  • ServiceTitan jobs and appointments from jpm/v2, with trucks and warehouses as inventory locations through Trucks_GetList and Warehouses_GetList
  • Transfers and purchase orders in flight: ServiceTitan Transfers_GetList and PurchaseOrders_GetList, or Dynamics 365 purchase order receipts
  • MaintainX work orders with partsAvailability of PARTS_AVAILABLE, PARTIAL_PARTS, PARTS_UNAVAILABLE, or PARTS_AVAILABLE_BUT_OVERCOMMITTED, and part status from NO_PARTS to ISSUED

Proposed actions

  • Target capability: propose a Dynamics 365 Field Service inventory transfer through POST /msdyn_inventorytransfers from the warehouse to the technician's truck, with products and quantities
  • Target capability: propose a ServiceTitan transfer update through Transfers_Update with transferFromId, transferToId, dateRequired, and items by skuId and quantity
  • Target capability: propose a purchase order through ServiceTitan PurchaseOrders_Create or a Dynamics 365 purchase order, where no stock exists
  • Target capability: propose a MaintainX part transfer request through POST /parttransferrequests with quantityRequested, sourcePartId, and destinationPartId
  • Target capability: propose rescheduling the appointment: a bookableresourcebooking update, or a ServiceTitan appointment reschedule, with the date the part arrives

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Transfer parts to the truck before a Dynamics 365 job

    Estimated work order products are compared with msdyn_qtyavailable at the technician's truck. Where short, an inventory transfer from the main warehouse is proposed for the morning pick.

    With Microsoft Dynamics 365 Field Service, Slack

  • Raise a ServiceTitan purchase order for a part nobody holds

    A job's required part is absent from every truck and warehouse. The operator proposes PurchaseOrders_Create with the vendor and the job, and a reschedule if the lead time misses the appointment.

    With ServiceTitan, Microsoft Teams

  • Borrow from another truck through a MaintainX transfer request

    A work order showing PARTIAL_PARTS is matched to stock on another technician's truck. The operator proposes a part transfer request between the two, with a requestMessage naming the job.

    With MaintainX, ServiceTitan

  • Reschedule when the part cannot arrive

    Where msdyn_qtyonorder shows the part inbound after the appointment, the operator proposes a bookableresourcebooking update to the day after receipt, for the manager to approve.

    With Microsoft Dynamics 365 Field Service, Microsoft Teams

Requirements

  • A field service connector with parts on the work order and stock by location: Dynamics 365 Field Service, or ServiceTitan with its Inventory API
  • Products marked as inventory items, so quantities exist per warehouse or truck; in Dynamics 365 the Field Service Product Type must be Inventory
  • Each technician tied to a truck or default warehouse, so the operator knows which stock a job draws from
  • Slack or Microsoft Teams for the service manager's approval
Authentication
Work orders, stock, and transfers are read and proposed through the field service and maintenance connectors you bind; the operator keeps no credential of its own.

Limits

  • It reads stock as the system records it. A part used but not yet recorded still counts as on the truck
  • Dynamics 365 does not stop quantities going negative by default; the operator flags a negative count rather than trusting it
  • ServiceTitan's Inventory API lists trucks, warehouses, transfers, purchase orders, and receipts; on-hand quantity per truck is not something this listing confirms
  • It proposes a reschedule with a date; it does not contact the customer. Pair it with a notice operator for that

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Parts Readiness ↗

Questions and answers

What does the service manager approve?
For each job at risk: the parts required, the quantity on the technician's truck and in the warehouse, the gap, and one proposed fix, a pick, a transfer, a purchase order, or a reschedule. The manager approves, changes the source, or declines.
What record is left?
The work order and its product lines as read, the stock by location with the time read, the fix proposed and the alternatives, the approval with name and time, and the transfer, purchase order, or booking change as the field service system accepted it.
Does it move stock or reschedule customers on its own?
No. Transfers and purchase orders are created only after approval, and a reschedule changes the booking, not the customer's expectation. Telling the customer is a separate, approved step.
Ask about Parts Readiness

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy