Integrations & customisation
Your engineers keep their tools. Integration is scoped around them.
Teams build years of standards and templates around their CAD and BIM software. Integration starts from your tools, versions and templates, and its scope is agreed per project.
- Starting pointYour drawingsPDF drawing sets, as they exist today
- RamerionWorkflow outputModels, data and deliverables for engineers to review
- DestinationYour toolchainThe CAD/BIM tools and standards your team already uses
01Philosophy
Integration starts from your tools, versions and templates.
Every team’s toolchain is different: versions, plug-ins, templates, naming conventions and file-exchange habits built up over many projects. An integration has to handle those details.
So we treat integration as engineering work in its own right. Custom integration scope depends on the target tool, version, data formats and project requirements, and it is agreed before anything is built.
Sometimes a clean file export is all a team needs. Sometimes it is an API or a purpose-built connector. We would rather recommend the simplest pathway that works than the most elaborate one.
02Possible pathways
Four ways data could move between our workflows and yours.
A From a Ramerion workflow
- 3D model data
- BOM & BOQ tables
- Drawing sets
- Component & asset data
B Pathway, scoped per project
- File export / import
- API access
- Custom connector
- Version-specific project
Direction of data flow is agreed during scoping
C Your toolchain
- CAD / BIM authoring tools
- PLM, ERP or asset systems
- Document control
Versions, templates and standards stay yours
Export & import pathways
Exchange models, tables and drawings through file formats your tools can already read and write, agreed for each project.
API access
Programmatic access so your own systems can request or receive data, where the deployment and use case support it.
Custom connectors
A purpose-built connector or plug-in for a specific tool, scoped to the versions and workflows your team actually uses.
Version-specific projects
Integration work tied to a particular tool version, template or company standard, with maintenance responsibilities agreed up front.
03Toolchains
Tools an integration may involve.
Integration conversations often start with a specific application. These are examples — not a compatibility list. Whether and how a connection is built is decided per project.
| Tool | Workflow area | Status |
|---|---|---|
| Tekla Structures | Steel modelling, detailing and fabrication-drawing workflows | Scoped on request |
| SOLIDWORKS | Mechanical parts, assemblies and drawings | Scoped on request |
| Siemens NX | Product engineering and manufacturing workflows | Scoped on request |
| Other 3D CAD / BIM tools | Model exchange, review and documentation workflows | Scoped on request |
Tool names are trademarks of their respective owners. They are listed only as examples of software an integration conversation may involve; no partnership, endorsement, certification or shipped native integration is implied.
04Scoping
What we need to scope an integration.
Bring what you have. A short description, a screenshot of the current workflow or a few sample files are enough to start the conversation.
Discuss your workflowTool and version
Which applications are involved, their exact versions, and any add-ons or templates in use.
Supported data formats
The file formats or interfaces each tool can import and export in your set-up.
Direction of data flow
Into your tools, out of them, or both — and which system is the source of truth.
Expected output
What a successful exchange produces: models, drawings, tables, metadata or reports.
Deployment & security constraints
Network boundaries, hosting rules, access policies and the approvals your IT team requires.
Success criteria
How your engineers will judge the result, including review steps and acceptance checks.
How we would approach it
Discovery
Understand the workflow, tools and constraints.
Sample-data trial
Test the pathway on representative files you choose to share.
Engineer review
Your team checks the output against its own standards.
Agreed scope
Deliverables, support and maintenance set out in writing.
Next step
Tell us how your team works today.
Describe the tools, versions and handoffs involved, and we will give you a straight answer on which integration pathway — if any — makes sense.