Terms of Service
The terms a PLM buyer actually reads are the ones about who owns the product data, what happens to it if the relationship ends, and what we are on the hook for when the service is down. Those are sections four, eleven and ten.
1 · The agreement
These terms are between dev.co (“we”) and the organisation subscribing to Manufacturing PLM (“you”). They apply together with the order form recording your plan, seat counts and term, and with the data processing agreement governing tenant content.
Where the documents conflict, the order form wins over these terms, and the data processing agreement wins over both on anything concerning personal data. That order is stated because ambiguity here is only ever discovered during a dispute.
The person accepting these terms confirms they are authorised to bind the organisation. If you are evaluating in a sandbox and nobody has signed anything, these terms still govern that use, and the liability cap is correspondingly small in both directions.
2 · Subscription, seats and billing
Subscriptions run for the term on the order form and renew for successive terms of the same length unless either party gives thirty days' notice before renewal. Published pricing applies unless the order form says otherwise.
Seats come in three classes and only one of them is charged.
- Full seat — creates and edits product data. Charged.
- Viewer seat — reads, comments and approves. Free and unlimited, because charging for approvals is how change control stops happening.
- Supplier seat — reaches only what you have explicitly shared. Free and unlimited, because a supplier who will not pay to answer your change notice simply does not answer it.
3 · AI usage and metering
Each plan includes an allowance of AI usage, metered in tokens. You set a per-tenant budget and per-agent caps beneath it, and the usage screen shows which agent spent what.
When a budget is reached, agents degrade in a stated order rather than failing silently: expensive reasoning stops first while retrieval and citation continue. Overage above the included allowance is billed at cost plus the margin published on the pricing page, and we will not invoice overage you were not warned about — a budget reached is a notification, not a surprise on the next invoice.
If you bring your own model key, those requests go to your provider account under your contract and are not metered by us at all.
4 · Your data, and who owns what
You own your tenant content, including all intellectual property in it. Parts, structures, documents, drawings, changes, supplier records, configuration and everything derived from them remain yours throughout and after the subscription.
You grant us a licence to host, store, index, resolve, transmit, back up and display that content strictly as necessary to provide the service to you and the users you authorise. That licence exists for no other purpose, ends when your data is deleted, and is not sublicensable except to the sub-processors named on our published list.
We will not use your tenant content to train, fine-tune or improve any model. This is a term of the contract rather than a policy we may revise, and it is not conditioned on an opt-out you have to find.
Aggregate operational statistics — request volumes, error rates, feature usage counts — may be used to run and improve the service. These never contain tenant content, part numbers, document text or anything identifying your products, and we will not publish them in a form that identifies you.
5 · Our intellectual property
We own the platform: the software, the object engine, the resolution engine, the interface, the documentation and the trademarks. Your subscription is a licence to use it, not a transfer of any of it.
Configuration you build inside your tenant — object types, attribute definitions, lifecycles, workflows, numbering schemes, saved views and custom agent definitions — is yours, and is exportable with the rest of your data. It is not treated as a contribution to the platform, and we will not lift a customer's model into the product.
If you send us feedback or feature suggestions, we may act on them without owing you anything. That is a standard clause and we state it plainly rather than burying it: telling us the grid should support fill-down does not create an obligation, and we would rather you told us anyway.
6 · Acceptable use
Do not use Manufacturing PLM to break the law, infringe somebody else's rights, or store material you have no right to hold. Do not attempt to circumvent tenant isolation, access another customer's data, or probe the service for vulnerabilities without a written engagement — we run a disclosure process, and it is faster than the alternative.
Do not resell or provide the service to third parties except through the white-label and partner arrangements, which have their own terms. Supplier access via the supplier portal is a normal and expected use, not a breach of this clause.
We may suspend access where continued use presents a genuine risk to the service or to other customers. Where we do, we will tell you why, and we will restore access as soon as the cause is resolved. Suspension is not a substitute for termination and will not be used as one.
7 · Availability, support and changes
We target 99.9% monthly availability excluding scheduled maintenance, which is announced at least five days ahead and scheduled outside European working hours. Where an order form includes a service level agreement with credits, that document governs and these targets are informational.
Support is by email on all plans, with response targets by plan on the pricing page. Security issues get a response the same working day regardless of plan.
We ship continuously and features are added often. We will not remove or materially degrade a capability you depend on without ninety days' notice and, where the change is ours rather than forced on us, a migration path. Deprecations are announced in the changelog and by email to administrators, never discovered.
8 · Confidentiality
Each party will protect the other's confidential information with at least the care it uses for its own, and will not disclose it except to people who need it and are themselves bound to confidentiality. Your tenant content is your confidential information by definition and needs no separate designation.
These obligations do not apply to information that is public through no fault of the receiver, was already known without obligation, or is independently developed. Where disclosure is compelled by law, the compelled party will give notice where it is lawful to do so.
Confidentiality survives termination for five years, and indefinitely for anything that is a trade secret.
9 · Warranties and disclaimers
We warrant that the service will perform materially as described in the documentation, that we will provide it with reasonable skill and care, and that we have the right to grant the licences we are granting.
We do not warrant that the service will be uninterrupted or error-free, and — stated plainly because this is a PLM — we do not warrant the accuracy of your product data or of any decision made from it. The resolution engine is deterministic and tested; it resolves the structures you gave it. It cannot know that a quantity was typed wrong.
AI output is assistive. Agents cite the object revisions they read so that a person can verify, and they abstain where they cannot support a claim. They are not a substitute for engineering review, and nothing in the product treats them as one. Except as stated here, all other warranties are excluded to the extent the law permits.
10 · Liability
Neither party excludes liability for death or personal injury caused by negligence, for fraud, or for anything else that cannot lawfully be excluded.
Subject to that, each party's total liability arising out of the agreement in any twelve-month period is capped at the fees paid or payable in that period. Neither party is liable for indirect or consequential loss, loss of profit, loss of anticipated savings, or loss of business opportunity.
Two carve-outs sit outside the cap because they should: your obligation to pay fees, and either party's breach of the confidentiality obligations. We considered carving out data loss too, and did not, because an uncapped data-loss exposure produces a vendor who declines to hold the data at all — which is not the outcome either side wants.
11 · Termination, and getting your data out
Either party may terminate for material breach that is not cured within thirty days of written notice, or immediately on the other's insolvency. You may terminate for convenience at the end of a term with thirty days' notice; fees already paid are not refunded, and fees not yet due are not owed.
On termination your data is available for export for thirty days. Export covers parts, structures with their effectivity, documents and files, change records, supplier and AML data, configuration and the audit trail, in documented open formats — not a proprietary archive that only we can read. The same export is available at any time during the subscription; there is no charge and no support ticket required.
After thirty days, tenant content is deleted from live systems within a further thirty days and expires from encrypted backups within ninety days of that. We will confirm deletion in writing on request. Data is never held hostage against a commercial dispute, which is a thing that happens in this industry and should not.
12 · Changes, governing law and contact
We may update these terms. Material changes are notified to administrators by email at least thirty days before they take effect, and the previous version stays available. If a change is materially adverse to you, you may terminate before it takes effect and receive a pro-rata refund of prepaid fees.
These terms are governed by the laws of England and Wales, and the courts of England and Wales have exclusive jurisdiction. Where you are a public body or your procurement rules require a different governing law, raise it during contracting — it is negotiable, and discovering it after signature is not.
If any provision is unenforceable it is severed and the rest stands. Neither party may assign without the other's consent, except to a successor of the whole business. Contact: legal@dev.co.