Frequently asked questions
Questions manufacturing teams ask before starting
These answers explain how a practical engagement can be scoped. Actual recommendations depend on the process, systems, data, risks, responsibilities, and commercial agreement.
Buying questions
Questions to resolve before work starts
These answers establish a practical default. Actual scope follows the systems, process, data, risks, and responsibilities in view.
01Can this work with our existing systems?
Usually, but compatibility must be confirmed. We first identify supported interfaces, data ownership, update frequency, security constraints, and failure behavior. Where a direct connection is unsafe or unavailable, a controlled file exchange or staged replacement may be more appropriate.
02How do you limit disruption during rollout?
We keep the first scope bounded, test with representative data, define rollback and manual fallback procedures, and agree a cutover window with process owners. Safety-critical control remains outside an information-workflow project unless separately assessed by qualified specialists.
03How are scope, timeline, and price determined?
They depend on process variation, systems and interfaces, data condition, security requirements, testing effort, number of sites, training, and support boundaries. Discovery produces an evidence-based scope rather than an unsupported fixed promise.
04Who owns the data and operating documentation?
The client remains responsible for its data and operational decisions. Project terms should identify ownership of configuration, custom code, credentials, runbooks, architecture records, and vendor accounts before implementation begins.
05What support can be included after launch?
Handover can include training, runbooks, monitoring, incident triage, change requests, and periodic optimization. Response targets, hours, exclusions, access, and escalation routes must be agreed in the support scope.
06How do we know whether the work is worthwhile?
Agree the metric, definition, baseline period, comparison conditions, data source, owner, and review date before changing the workflow. Released capacity is reported separately from cash savings, and operational outcomes are not attributed to software without comparable evidence.
07Do we have to move everything to the cloud?
No. Workloads can remain on-site or at the edge where latency, connectivity, machine autonomy, licensing, security, or support constraints require it. Placement should follow operating needs rather than a cloud-only rule.
08What happens when an automated step fails?
The design should make failures visible, retain the source record, route the item to an owned exception queue, allow authorized correction, and preserve an audit history. A workflow is incomplete until its exception path is tested.
Start with one process
Which workflow currently costs your team the most time?
Bring one normal example and one exception. Use them to frame the systems, decisions, controls, and evidence a sensible next step needs.
Discuss your operation