On-premises deployment specification

This is a technical reference for installing and operating V5 Ultimate 5.10 On-Premises, meaning on infrastructure that you (or your contractor) operate. That includes a cloud account, subscription or tenancy that you control, which the MSA calls a Customer-managed cloud and treats as On-Premises.

Commercial terms (licence or subscription, fees, support, liability) are set only by the Master Services Agreement V1.24 and your Order. This document is technical only and does not amend them. The On-Premises Licence Addendum of June 6, 2026 is kept as historical text and does not govern current purchases.

Sizing, topology examples, versions and objectives in this document are planning starting points. The delivery format and supported configurations for a release are those in the Documentation for that release (MSA §4.3), and each site's design is confirmed in writing during project design.

This document does not describe V5 Classic 5.9. Classic is a separate product with its own technology stack, supplied On-Premises only (MSA §2.1.2). A Classic licence does not include V5 Ultimate; any move is a separate Order with its own scope and fees (MSA §4.8).

V5 Ultimate is available as Cloud, Private Cloud or On-Premises. Your Order states which one applies; there is no default. Private Cloud is hosted and operated by us on the same hosting platform and environment, by the same operator, as standard Cloud, with a separate isolated application instance and a separate database for you (MSA §2.4). A deployment in a cloud account you control is not Private Cloud: it is a Customer-managed cloud, which is On-Premises.

Private Cloud release deferral (not On-Premises)

For a Private Cloud production instance you may defer a routine, non-security feature release and stay on the prior supported version for up to 180 calendar days from our written release notice, which includes release notes and impact information. Installation windows are agreed together, and we give at least 30 days' written notice before the window ends. If you supplied a documented validation plan with milestones and need more time, a reasonable extension can be recorded in writing before the window ends. We may require earlier mitigation or upgrade for a critical security vulnerability or active threat, a legal or regulatory requirement, a material incompatibility or end of life of an underlying platform component; urgent security patches may be applied sooner (MSA §8.5). This window does not apply On-Premises, where you control deployment timing.

The patterns below are the shapes most often discussed in project design. Which ones are supported for a given release, and in what form, is confirmed from the release Documentation.

Hybrid means a deployment that spans your own site infrastructure and your own cloud tenancy. Every tier is operated by you. Common shapes to discuss in project design:

• Application on site, data in your cloud. Application and operator stations on the plant network, close to scales and printers; database and file storage in your cloud account. Needs a stable, adequately sized site-to-cloud link; behaviour when the link is lost is confirmed during design.
• Site edge with central application. A site node connects local devices while the main application and database run in your cloud account. Whether and how local operation continues through a network outage is confirmed during design; it is not assumed.
• On-site primary with cloud recovery. Production on site, with a standby copy in your cloud account for disaster recovery. Your recovery objectives are set and tested by you.
• Multi-site. Some sites on-premises, others in your cloud account, with shared single sign-on and reporting and per-site data residency as you design it.

The project design records which tier runs where, who owns the link between them, and how your validation covers each part.

V5 Ultimate 5.10 (and V5 Classic 5.9) have each been independently assessed by Dr. Bob McDowall. Each assessment is limited to the version, scope and findings in its report and is available on request under confidentiality (MSA §7.1). You may use the 5.10 assessment as supporting evidence in your own validation of that version. It is not regulatory approval or certification, and it does not validate your instance, configuration or deployment, or any later version.

Your Quality team is responsible for intended-use validation, testing (including IQ, OQ, PQ and UAT as applicable), approval, release and change control (MSA §7.2, §10.1). Validation assistance, including any qualification documentation or help executing it, is provided as described in the MSA and as purchased in your Order.

On-Premises, you decide when to apply a release in your environment (MSA §8.1(c)), so you can validate before production use. Emergency patches are made available with recommended deployment guidance (MSA §8.4).

For On-Premises, backup, disaster recovery and availability are yours to design, operate and test. The MSA's uptime, backup, RPO and RTO commitments apply only to hosted services and not to On-Premises (MSA §11.9). For comparison, Private Cloud backup and recovery levels are in MSA §11.4.

• Backups: a common design is regular full database backups plus continuous transaction-log archiving to storage you control, encrypted with your keys, with retention set by your record-keeping rules.
• Recovery objectives: set by you for each site and proven by restore tests.
• High availability: where needed, multiple application instances behind your load balancer and a replicated database, scoped in project design.
• Drills: restore into a separate database at go-live and at regular intervals thereafter.

• Application logs can be collected by your existing log platform.
• Health checks for your load balancer or orchestrator are described in the release Documentation.
• Monitoring, alerting and capacity management of the infrastructure are operated by you.

Availability depends on your plan, configuration and connected systems; feasibility for an On-Premises site is confirmed in project design.

• ERP: ERP connectors that extend your existing ERP to the shop floor, set up through a guided connect, map, dry-run and go-live process. V5 runs alongside your ERP; it is not an ERP.
• API: REST API (read and write) and webhooks.
• Trading partners: EDI documents and GS1-128 shipping labels.
• Devices: scales, printers, sensors and PLCs, including Mettler SICS, Modbus TCP, OPC-UA, MQTT and Zebra ZPL.
• Identity: SAML single sign-on, as in Section 8.

For On-Premises we provide remote software support, operational guidance and troubleshooting for defects reproducible in a supported configuration. No uptime is warranted. Target initial response times (MSA §11.2):

• These are initial response targets, not resolution guarantees. On-site support needs a separate statement of work.
• The former Silver, Gold, Platinum and Diamond support tiers are retired and replaced by this severity-based framework (MSA §11.12).
• Licence or subscription terms, entitlements and any source-code escrow are only those stated in the MSA and your Order.