Get started
Plan for operation after deployment.
Choose support for current-version stability or continued product improvements.
The approach
How does it work?
- 01 Choose the scope
Choose products by the capabilities needed
- 02 Size the deployment
Size capacity and servers for the site
- 03 Deployment & support
Make included and additional work clear
- 04 Agree on a plan
An actionable initial deployment plan
Details
Scope and considerations
Basic and Partnership maintenance
Basic maintenance supports stable operation within the installed version and licensed scope. It includes remote diagnosis, incident analysis, bug fixes, stability patches, site checks and performance updates. New features and feature updates are excluded.
Partnership adds new standard-product features, feature updates and deployment support within the licensed scope. New custom development, integrations and out-of-scope expansion are separate engagements.
Policy comparison
| Item | Basic | Partnership |
|---|---|---|
| Remote support and fixes | Included | Included |
| Scheduled site checks | 1/year | 2/year |
| Emergency site support | Up to 1/year | Up to 2/year |
| Performance updates | Included | Included |
| Feature updates | Excluded | Within licensed scope |
| Emergency initial response | Within 4 hours | Within 2 hours |
| Annual maintenance rate | 10% of basis | 20% of basis |
Detailed maintenance contract terms are agreed through consultation.
Cost basis and operating cooperation
The minimum term is one year. The basis includes supplied software/licenses and accepted custom software, excluding hardware. Delivered custom features receive incident and stabilization support within their accepted scope.
Provide incident time, affected equipment/functions, symptoms, recent changes and available logs. Agree remote access, site entry, work approval and backup responsibilities in advance.
Start together
Tell us what you want to improve first.
Tell us about your equipment, data and priorities to review a path from connection to operations.