Deploy within enterprise boundaries for long-term stability.
For organisations with defined requirements for deployment location, identity, data separation, audit and operations, choose SaaS, dedicated or private options from business and security boundaries.
- Deployment model
- Identity & access
- Audit & governance
CONNECTION MAP
- 01
Enterprise identity & network
Users, roles, environments and access boundary
- 02
ii3d runtime
3D experience, configuration rules and services
- 03
Audit & operational governance
Records, change, monitoring and response
Start with your integration needs.
Identify the problems to solve around your existing pages, product information and workflows.
Enterprise boundaries are absent from the plan
Network, identity, data residency and vendor requirements surface late and force broad rework.
Roles and pricing permissions are mixed
Employees, dealers, OEMs and end customers cannot access content and business capabilities by their proper scope.
There is no governance after launch
Upgrades, monitoring, incident response and ownership are not defined for ongoing operation.
Prepare the essentials for this connection.
Confirm standard publishing and additional business integration separately. Availability follows development, testing and project acceptance.
Assess deployment models
Compare SaaS, dedicated and private models against data, network, operations and procurement constraints.
Map identity and permissions
Separate identity, content and price-access boundaries for employees, channel partners, OEMs and end users.
Plan audit and data responsibility
Define which actions and data require logging, retention, export or security review.
Define the operating model
Put versions, change windows, monitoring, backup and incident response into mutually agreed ownership boundaries.
Start with a concrete use case.
These examples show how products and workflows connect, helping you choose the right entry.
Unified identity entry
Bring enterprise users and channel partners into the existing identity and role model.
Channel price tiers
Constrain visible content and pricing by role, organisation or business relationship.
Security and change review
Retain clear review and confirmation steps before launch, upgrade and cross-system connection.
Move from setup to integration in four steps.
Prepare source material, confirm content, validate the entry and deliver the agreed scope.
- 01
Confirm enterprise constraints and goals
Collect known requirements for deployment, identity, network, data and compliance.
- 02
Set the target architecture
Define environments, access paths, data boundaries and system connections requiring review.
- 03
Validate security and connectivity
Validate sign-in, permissions, network connectivity and core business flow in a controlled environment.
- 04
Hand over operations and governance
Confirm owners and processes for release, monitoring, incidents, changes and support collaboration.
Common questions
Understand the preparation and usage boundaries before you begin.
Can deployment use a specified cloud or enterprise network?
This requires assessment against network, runtime, data and operations requirements. The page does not presume an answer; it first gathers and clarifies constraints.
Is enterprise SSO supported?
Identity approach, protocol and role mapping need confirmation with the enterprise identity system and should be included in security review.
How is data ownership defined?
It should be explicit in project scope, deployment plan, data classification and contractual terms, not inferred from page copy.
Can upgrades affect live business?
Before launch, define version policy, change window, validation and rollback. The exact approach follows deployment and business risk.
Find the right connection for your platform and products.
Share your platform, product type, capabilities and page placement to discuss preparation and integration scope.