Manufacturing buying guide
Choosing a manufacturing deployment boundary
Evaluate hosting around data, connectivity, ownership, recovery, and the exact environment being proposed.
Discuss your requirements
Define the operating constraints
List where users work, which connections are available, what data may be processed, and which systems must exchange records. Identify contractual requirements and responsible security and legal reviewers before selecting a deployment label.
Ask who operates each layer
Document infrastructure, identity, patching, keys, monitoring, backups, restore, incident response, and support responsibilities. For any disconnected proposal, require evidence for installation, updates, licensing, data transfer, and recovery without assuming access to an external service.
Test the proposed configuration
Request dated architecture and release-specific evidence. Exercise an outage, restore, failed update, and the required data exports. Cloud, private, on-premises, and disconnected availability must be confirmed for the actual product and scope; these labels are not interchangeable guarantees.
General evaluation guidance, not professional advice or proof of product availability. Use current primary evidence and qualified advisers for obligations affecting your organization.