Skip to main content
Axiotech Automation Ltd
+44 (0)7415 112 892
sales@axiotech.co.uk

Inventor API · iLogic · Vault workflows

Convert repetitive Inventor engineering work into a controlled, supportable software workflow.

Axiotech develops add-ins, iLogic automation, model and drawing processes, data exchange and connected engineering tools for the Autodesk Inventor product family. Client work remains Axiotech-led and scoped to the customer environment.

Scope this requirement See all engineering services

Good fit

Use this service when

  • Engineering teams using Inventor Professional, iLogic, Vault or connected Autodesk Platform Services where a supported API exists.
  • OEMs needing configuration, automation, migration, validation, integration or an internal engineering tool.

Scope boundary

Not assumed or silently included

  • Implying Autodesk sponsorship, product certification or endorsement of an Axiotech solution.
  • Automating undocumented design decisions without a customer-approved rule, sample set and exception process.

Why act

The operational risk behind the technical symptom

The first work package is shaped around reducing an explicit risk or enabling a named decision.

01

Desktop macros become critical infrastructure without ownership, tests or deployment control.

02

A model change produces drawings, BOMs or downstream data that are syntactically valid but technically wrong.

03

Version, add-in and Vault dependencies break when the engineering estate changes.

Purchasable entry points

Choose a bounded engagement before expanding scope

Final inclusions, dependencies, location, schedule and commercial terms are confirmed in a formal quotation.

Package 1

Inventor workflow assessment

Decision enabled: A costed automation opportunity with rules, exceptions and acceptance examples.

Typical scope: User workflow, sample files, version/dependency review, API feasibility, risk and architecture options.

Package 2

Add-in or iLogic work package

Decision enabled: A versioned tool proven on an approved representative dataset.

Typical scope: Specification, UI/logic, API implementation, tests, installer/deployment, source and user handover.

Package 3

Engineering-system integration

Decision enabled: Controlled data movement between Inventor and connected systems.

Typical scope: Schema/interface design, identity and error handling, integration, reconciliation tests and operations guide.

Artefact manifest

What remains after the engineering work

The exact document set scales with risk and the approved work package.

  • Workflow, rule and exception specification
  • Solution architecture and Autodesk dependency baseline
  • Version-controlled source and build/deployment record
  • Representative-model test set and acceptance results
  • User, support, rollback and lifecycle documentation

Technical and responsibility boundaries

Make ownership reviewable

  • The customer approves engineering rules, representative models and resulting design responsibility.
  • Autodesk licensing, supported API behaviour and environment access remain customer/platform dependencies.
  • Third-party and background IP are recorded; delivery rights are agreed before implementation.

Review and acceptance

Six gates from authority to handover

Gate depth changes with the work; named decisions and evidence remain.

  1. G0
    Scope authorityOutcome, boundaries, roles, assumptions and commercial basis agreed.
  2. G1
    Baseline acceptedKnown installed/source state, dependencies, constraints and unknowns recorded.
  3. G2
    Design approvedRequirements, interfaces, risks and acceptance evidence ready for implementation.
  4. G3
    Release candidateBuild reviewed, verified, versioned and accompanied by defect disposition.
  5. G4
    Site acceptanceCommissioning evidence, deviations and release decision recorded.
  6. G5
    Handover acceptedSource, configuration, records, recovery and residual risks transferred.

Read the complete delivery method

Assurance option

Compliance is a declared scope—not a badge

For quality-managed engineering workflows, rules, source, versions, representative test models, expected outputs, reviews, deviations and release approvals can be retained as a controlled software lifecycle. Applicable design approval remains with the authorised customer engineer.

Review validation services

Relevant engineering evidence

Governed Inventor configuration workflow

A capability pattern for separating approved engineering rules, automation code, model test sets, exception handling and authorised design release.

Review this evidence

Procurement FAQ

Questions to resolve before quotation

Do you develop Inventor add-ins as well as iLogic rules?

Yes. The choice depends on deployment, UI, performance, maintainability, version support, security and integration needs.

Can you integrate Vault or business systems?

Where licensed, supported interfaces and customer access permit it. Identity, transaction ownership, error recovery and reconciliation are designed explicitly.

Does Axiotech’s developer membership mean Autodesk endorses the solution?

No. Axiotech independently scopes and delivers client work. Autodesk trademarks and platforms remain Autodesk’s, and no sponsorship or endorsement is implied.

Next decision

Describe the outcome, installed baseline and constraints you already know.

Use “Not known” where evidence is missing. The first review will separate facts, assumptions and discovery work.

Scope Autodesk Inventor software development