--- title: "Equipment commissioning readiness workflow before dispatch" description: "A workflow that ties sold commissioning scope, NetSuite shipment status and site prerequisites to a dispatch decision that service operations approves." canonical: https://www.stacksync.com/blog/equipment-commissioning-readiness-workflow last_modified: 2026-09-18 --- # Equipment commissioning readiness: connect sales promises, site prerequisites and service dispatch > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md Before a technician travels, this workflow shows which accessory, site condition or customer confirmation is still missing and who owns resolving it. Author Ignacio Malpartida · GTM Engineer Published September 18, 2026 Read time 4 min read APP TIPS ## The operating decision A commissioning-readiness workflow should connect the sold service scope to the machine, delivery status, site prerequisites and assigned service owner. Automate the collection of evidence and follow-up while keeping dispatch approval with service operations. A shipped machine does not establish that the site is ready, and a calendar invitation is not proof that required conditions are satisfied. Show which prerequisite blocks a visit and what evidence will resolve it. Explore the complete [industrial equipment and machinery integration and automation hub](https://www.stacksync.com/industry/manufacturing/industrial-equipment-machinery) for the systems and processes around this guide. ![Summary card: Equipment commissioning readiness workflow before dispatch](https://www.stacksync.com/images/blog-highlights/icp-equipment-commissioning-readiness-workflow.webp) ## What this looks like in industrial equipment and machinery A machinery builder schedules commissioning shortly after equipment delivery. The site contact says installation is ready, but one purchased accessory has not arrived and the customer has not confirmed a required site condition. Sales wants to preserve the promised date, while service risks sending a technician who cannot complete the work. A shared readiness case can combine the accepted service scope, shipment information and customer confirmations, allowing the dispatcher to approve a visit with clear evidence or negotiate a revised plan before travel is committed. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Sold commissioning scope | Sales operations | Retain the accepted services, machine reference and customer obligations from the approved commercial record. | | Site prerequisite | Service operations | Record the requirement, responsible party, evidence and current verification state. | | Equipment readiness | Order management | Expose the relevant shipment and accessory status without assuming delivery means installed readiness. | | Dispatch decision | Service operations | Record the approved visit, assigned resources and unresolved conditions explicitly. | ![Record ownership diagram: Sold commissioning scope, Site prerequisite, Equipment readiness](https://www.stacksync.com/images/blog-diagrams/icp-equipment-commissioning-readiness-workflow.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Translate the sold scope into prerequisites Have service define which customer, equipment and site conditions matter for the selected visit type. Record what counts as adequate evidence. A generic ready checkbox is not enough when different machines require different preparation. 2. 02 Collect current operational evidence Link the machine serial, shipments, accessory orders and customer confirmations. Distinguish confirmed facts from promises to complete work before the visit. Missing access to a source should remain visible instead of being interpreted as a satisfied condition. 3. 03 Route gaps to accountable owners Assign the customer-site question, missing component or internal scheduling issue to the person who can resolve it. Coordinate follow-up through approved channels and retain responses on the same case. Escalate when the required decision date approaches. 4. 04 Approve the visit against the evidence Let service operations review the complete readiness state and any accepted exceptions. Record the approved conditions under which dispatch may proceed. A salesperson’s target date should not automatically overrule a known unresolved prerequisite. 5. 05 Recheck when the situation changes If delivery slips or a customer withdraws confirmation, reassess the dispatch decision. Preserve the prior plan and notify its owner. Close readiness only when the visit is appropriately authorized or deliberately rescheduled, not when reminders have been delivered. ![5-step operating sequence: Equipment commissioning readiness workflow before dispatch](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-equipment-commissioning-readiness-workflow.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### The machine arrives but an accessory is missing Ask service whether the visit can proceed under an approved limited scope. Do not infer that the accessory is optional. ### The customer provides an informal verbal confirmation Record it through the accepted process and identify whether further evidence is required for that prerequisite. ### The assigned technician changes Reconfirm the skills, availability and handoff information required for the new assignment. A name replacement alone may not preserve readiness. ## What to verify before expanding - Each blocking prerequisite has a named owner and defined evidence requirement. - Dispatch approval is separate from shipment and requested visit date. - A later prerequisite failure reopens the readiness decision. - The service team can explain any approved exception before committing the visit. ## Connect this process to the rest of your operation [Explore Stacksync workflows](https://www.stacksync.com/workflow-automation) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real sold commissioning scope example and the exception your team handles most often, for example the machine arrives but an accessory is missing. - [Commissioning-readiness automation for equipment manufacturers](https://www.stacksync.com/use-case/equipment-commissioning-readiness-automation) - [Equipment warranty RMAs: coordinate replacement, return and credit decisions](https://www.stacksync.com/blog/equipment-warranty-rma-replacement-return-workflow) - [AI agents for equipment aftermarket requests: prepare compatible parts proposals](https://www.stacksync.com/blog/equipment-genie-aftermarket-part-request-guide) - [Equipment parts AI exceptions: serial ambiguity, supersession and incomplete kits](https://www.stacksync.com/blog/equipment-genie-part-supersession-serial-exceptions) - [Coordinate Closed-Won Onboarding Across Salesforce and NetSuite](https://www.stacksync.com/blog/coordinate-closed-won-onboarding-across-salesforce-and-netsuite) - [Salesforce ERP Integration: Best Real-Time Sync Solutions in 2026](https://www.stacksync.com/blog/best-data-integration-solutions-for-salesforce-and-erp-with-real-time-sync) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Salesforce: change data capture events](https://developer.salesforce.com/docs/platform/platform-events/guide/platform-events-objects-change-data-capture.html) - [Oracle NetSuite: using external IDs](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_156334828635.html) FAQ ## Frequently asked questions Can the workflow book travel automatically? Only within an explicitly approved process and demonstrated execution route. Start with readiness evidence and dispatch approval before extending the scope to consequential booking actions. What is the smallest useful pilot? Choose one machine family and one standard visit type. Include a missing accessory and an unconfirmed site condition to test the handoff. What should a service director track once commissioning readiness is live? Track coordination touches, time to readiness decision and visits rescheduled for prerequisites that were discoverable earlier. Avoid claiming every cancelled visit was caused by missing integration. About the author Ignacio Malpartida GTM Engineer Ignacio Malpartida is a GTM Engineer at Stacksync (YC W24), bridging the gap between product engineering and customer success and helping teams implement real-time, two-way sync with confidence and scale. [All posts by Ignacio Malpartida](https://www.stacksync.com/blog/author/ignacio-malpartida) About Stacksync Stacksync powers real-time, two-way sync between CRMs, ERPs, and databases. Engineers sync data at scale and automate workflows, not dirty API plumbing. Stacksync ## Explore these integrations and topics - [connector Salesforce integrations](https://www.stacksync.com/connectors/salesforce) - [connector NetSuite integrations](https://www.stacksync.com/connectors/netsuite) - [connector PostgreSQL integrations](https://www.stacksync.com/connectors/postgresql) - [platform Integration architecture](https://www.stacksync.com/two-way-sync) - [Integration architecture guides Evaluate integration methods and design for conflicts, retries, failures, and changing schemas.](https://www.stacksync.com/blog#topic-integration-architecture) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [App tips Coordinate Closed-Won Onboarding Across Salesforce and NetSuite 8 min read read](https://www.stacksync.com/blog/coordinate-closed-won-onboarding-across-salesforce-and-netsuite) [App tips AI agents for equipment aftermarket requests: prepare compatible parts proposals 4 min read read](https://www.stacksync.com/blog/equipment-genie-aftermarket-part-request-guide) [App tips Equipment parts AI exceptions: serial ambiguity, supersession and incomplete kits 4 min read read](https://www.stacksync.com/blog/equipment-genie-part-supersession-serial-exceptions) ## You just read how it should work. See it run on your own data. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)