CATIA V5 → Aras Innovator
Europe · Automotive OEM
CAD assembly metadata lands in Aras straight from the CATIA interface, with the manual re-keying designed out.
Platform-Independent
Enterprise Integration Framework
A configuration-driven framework to connect enterprise systems and orchestrate business operations.
- Reusable Connectors
- Monitored & Governed
Six systems, one layer — every exchange flows through the framework, not point to point.
Connecting Business Processes
Connect Systems the Way Your Business Works
Product information rarely moves in a straight line. It runs from engineering to the plant floor, out to suppliers, back again, and on to customers — across systems that were never designed to agree.
- Engineering
- PDM
- PLM
- ALM
- ECAD
- MCAD
- Manufacturing
- MES
- ERP
- Supply Chain
- Supplier Systems
- Supplier Portal
- Service
- Read-Only Portal
- External Access
- Partner Portal
- Customer Portal
Integration Challenges
Enterprise Integration Is More Than Exchanging Data
Point-to-point does not scale. Ten systems wired directly is forty-five interfaces to build, test and maintain, and every system added multiplies them again. The fix isn’t another connector — it’s moving every exchange onto one configurable integration framework: reusable, monitored, and governed.
- Point-to-pointInterfaces multiply with every system added, and each one is someone’s to maintain.
- One frameworkReusable, orchestrated flows — one place to change, monitor and govern as the landscape grows.
Move Beyond Hardcoded Integrations
Five Layers, One Framework
Connectivity → Transformation → Orchestration → Monitoring → Runtime. Each layer replaces something you would otherwise hardcode.
Enterprise Connectivity
Connect anything, anywhere — instead of wiring every system to every other.
- APIs
- Databases
- Files
- Messaging
- Cloud services
- Legacy systems
Data Transformation
Translate meaning between systems — instead of hardcoding business logic into each interface.
- Mapping
- Validation
- Enrichment
- Configurable rules
- Model-to-model
Process Orchestration
Coordinate, not just connect — instead of rebuilding the same logic in every new interface.
- Configurable flows
- Event processing
- Scheduling
- Automation
Monitoring & Governance
See and control every exchange — instead of limited monitoring and high maintenance.
- Health
- Execution history
- Alerts & retries
- Audit logs
- Reporting
Runtime Platform
A secure, extensible foundation — instead of vendor dependency.
- Authentication
- Plugin architecture
- Role management
- Scalable execution
Build integrations once. Configure, extend, monitor, and scale them across the enterprise.
Integration Expertise
Built for Enterprise Integrations
How it fits together
In the product
The Framework, Configured
Systems, flows and mappings, as the framework shows them.
Integration Platform
- Integrations running
- 0
- Currently running flow(s)
- Success rate
- 82.8%
- In last 24H
- Records processed
- 24
- In last 24H
- Systems with issues
- 2
- Degraded
Processing Volume
Recent Alerts (Failed Messages)
| Timestamp (UTC) | Flow | Error Message |
|---|---|---|
| 2026-08-14 09:15:33 | 3DX to ASAP BOM Sync | ASAP MATERIAL HTTP 500 |
| 2026-08-14 08:48:17 | 3DX to ASAP BOM Sync | ASAP BOM aborted: parent material sync failed |
| 2026-08-14 02:54:57 | 3DX to ASAP BOM Sync | Mapping error: required field AES_ITEM_NAME missing |
System Configurations
| System Name | Application | Auth Method | Username |
|---|---|---|---|
| Enovia PLM | 3DX | BASIC | 3DEXP01 |
| Odoo | ODOO | BASIC | admin@cif.local |
System Health
| System | Status |
|---|---|
| Enovia PLM | DOWN |
| Odoo | DOWN |
Edit Integration Flow
3DX to ASAP BOM Sync
- Basic Info
- Source & Trigger
- Target System
- BOM Mapping
- Post-Processing
- Advanced
Basic Info
- Type
- Point-to-Point
- Category
- BOM
- Processing
- Synchronous
- Concurrency
- Parallel
Source System
- System
- Enovia PLM
- Type
- REST
- Preprocessor
- ENOVIA BOM Structure Mapper
Target System
- System
- Odoo
BOM Mapping
- Status
- Mapping configured and saved
Integration Flows
| Flow Name | Source System | Target System | Category | Status | Processing |
|---|---|---|---|---|---|
| 3DX to ASAP BOM Sync | Enovia PLM | Odoo | EBOM | ACTIVE | SYNCHRONOUS |
| 3DX to Odoo Doc Sync | Enovia PLM | Odoo | MODEL | ACTIVE | SYNCHRONOUS |
Attribute Mapping Configuration
Map attributes from 3DX to ERP
- Basic Info
- Source & Trigger
- Target System
- Attribute Mapping
- Post-Processing
- Advanced
| Source Field | Target Field | Transform |
|---|---|---|
['PLMEntity.PLM_ExternalID'] | default_code | None |
['PLMEntity.V_Name'] | name | None |
['PLMEntity.V_description'] | description | None |
Source System
- System
- 3DX
- Type
- REST
- Path
- /from/Enovia/partCreate
Target System
- System
- ERP
Job History
- Total jobs
- 520
- All runs
- Successful
- 511
- Completed
- Failed
- 9
- With error detail
Success Rate96.73%
| Flow Name | Status | Duration | Retries | Summary |
|---|---|---|---|---|
| 3DX to ASAP BOM Sync | SUCCESS | 930ms | No retries | BOM 208912851 updated (ECO 862894858): lines re-synced |
| 3DX to Odoo Doc Sync | SUCCESS | 646ms | No retries | Drawing DRW-290311 released; .tif fetched and synced to Odoo |
| 3DX to ASAP BOM Sync | IN_PROGRESS | N/A | No retries | Queued for target processing |
| 3DX to ASAP BOM Sync | ERROR | 1.11s | No retries | Error: ASAP MATERIAL HTTP 500 |
| 3DX to ASAP BOM Sync | SUCCESS | 1.04s | 1 retry | Retry succeeded for 208961031 |
System Reports
07/01/2026 – 08/31/2026
- Overall success rate
- 84%
- Average across all flows
- Avg execution time
- 1.2s
- Across all integrations
- Total messages
- 475
- This month
- Running flows
- 0
- Currently running flow(s)
Integration Metrics
| Flow Name | Success Rate (%) | Failure Rate (%) | Avg Execution Time (s) | Total Volume |
|---|---|---|---|---|
| 3DX to ASAP BOM Sync | 89.38 | 10.62 | 1.44 | 250 |
| 3DX to Odoo Doc Sync | 81.07 | 18.93 | 0.98 | 261 |
Retry Success Rate
| Flow Name | Total Retries | Successful | Failed | Success Rate (%) | Pending |
|---|---|---|---|---|---|
| 3DX to ASAP BOM Sync | 1 | 1 | 0 | 100.00 | 1 |
| 3DX to Odoo Doc Sync | 5 | 0 | 5 | 0.00 | 0 |
Resources
The Framework in Production
Four integrations already running in production.
Customer stories
SmarTeam + SOLIDWORKS ePDM → one search
Oil & Gas
A custom ONEPART connector across two PDM systems, extraction aware of each system’s access control.
PLM · MES · Quotation · HRMS
USA · Electronics
Four business systems carried inside one Aras estate, supported since 2010.
Supplier portal → Aras
Denmark · EPC
Two thousand suppliers inside the workflow, with an MVP live in a month.
Get Started
Build an integration architecture that evolves with your business.
Tell us the systems you need to connect — PLM, ERP, MES, CAD, ALM, cloud, or legacy — and we’ll scope the integration with you.
The service behind the framework
The framework is the tooling. The service is the team that runs it—nine steps from business discovery to continuous optimisation.
- Business Discovery
- Integration Assessment
- Architecture Design
- Interface Mapping
- Development
- Validation
- Deployment
- Monitoring
- Optimization
FAQ
Frequently Asked Questions
Yes — PLM ↔ ERP is the flow we build most often: parts, BOMs, documents, materials and engineering changes kept in step, in both directions. SAP, Oracle, Microsoft Dynamics, Epicor, IFS and Odoo are already connected.
Very likely. The systems shown are the ones already built and in production, not a limit. Connecting a new platform is a configuration exercise against the framework’s existing connectivity layer rather than a new integration built from scratch. Tell us the system and we will confirm what it needs.
Your team can. Flows are configured rather than coded, so building and changing them is an administrative task once the framework is in place, and we train your people to do it. Most customers keep us for the first integrations and the architecture decisions, then run day-to-day changes themselves.
Integrations are configured against the framework rather than hardcoded into each system, so a source or target upgrade is a mapping change, not a rebuild. Monitoring shows what stopped behaving as expected, and the reusable logic stays in place.
Authentication and role management are part of the runtime platform, and execution history and audit logs record what moved, when, and what failed — so a question asked months later has an answer. Where policy requires it, the framework runs entirely inside your own environment.
Either. It can run in your own environment — on-premises or your cloud — or be hosted by SteepGraph. Customers with controlled data or strict network policies generally keep it in-house; the framework works the same way in both.
Both. The framework is available on a subscription or a perpetual licence, and which one fits usually depends on whether your integration landscape is a fixed scope or something you expect to keep extending.