Continuous routing automation for the digital thread.

3D harness routing as a background process on your PLM – rule-driven, deterministic, on your premises. Results: native CAD routings, released as today.

See earlier. Route continuously. Trace every decision.

For teams routing electrical wire harnesses (EWIS) in NX with Teamcenter – aerospace, defence, machinery. Other PLM and CAD systems follow.

The problem

Routing today: every update costs a specialist, and every routing issue surfaces too late.

Routing issues today – late, in batches, once ECAD is mature With RoutingIQ – continuous, while the design is open
  1. 1×Concept
  2. 3–8×Design – MCAD, ECAD, integrationDesign
  3. 7–16×Build
  4. 21–78×Assembly / AITAIT
  5. 29–1,500×Operations
Cost per fix of a hardware design issue by phase: NASA / INCOSE 2004 (Stecklein et al.). Issue curves schematic. Routing today waits for ECAD maturity and runs in batches – issues surface late, where change is expensive.

Integration multiplies the impact

Every routing issue flows back into MCAD and ECAD – the later, the costlier.

Knowledge sits in heads

Rules are interpreted per engineer; scarce specialists spend their time on repetition.

Capacity sets the pace

A few specialists, not demand, decide how often routing runs.

So routing is rationed – and every configuration and every change means the same scheme again, by hand. RoutingIQ turns it into a background process that keeps up with your design, by your rules; your specialists decide the exceptions.

How it fits

RoutingIQ runs in the background of the systems you already have – your PLM stays the owner.

  • Your ECAD and MCADstay as they are
  • Your PLMowner of all design data
  • RoutingIQkeeps the routing in step with your design
  • Native CAD routingsreleased as today

Integrated today with Siemens Teamcenter and NX. Other PLM and CAD systems follow – talk to us about yours.

No new interface
Plugs into your PLM. ECAD and MCAD stay as they are.
On-premises, air-gapped
Runs in your environment – also with export-controlled data.
You decide when it asks
Only the situations you want to see reach an engineer.
Results as if made by hand
Native, associative NX routings, editable by hand.
Deterministic, traceable
Same input, same result. Every routing is auditable.
Who we are

Built by a team that has engineered in NX for twenty years.

Freiberger Aero GmbH

CAx experts since 2015, Bavaria, Germany. Customers include Isar Aerospace and Helsing.

20 years in NX

Julian Freiberger, founder: NX engineering, customising and methods since 2006.

A product, not a project

Built, maintained and supported by this team. Improvements reach you as releases.

German company

Your data stays on your premises. Support & maintenance agreement; security review supported.

Siemens Build Partner (Siemens Software & Technology Partner). Freiberger Aero GmbH is a Build Partner of Siemens Digital Industries Software and develops complementary applications for NX and Teamcenter. RoutingIQ is a product of RoutingIQ GmbH, a Freiberger.Aero company.

Next step

Three steps from today to a pilot – each with its own decision point.

  1. Talk

    45 minutes online with your routing leads: toolchain, priorities, and three figures – cables per unit, hours per cable, changes before release.

  2. See it on your data

    Under a mutual NDA, on a representative assembly, on a test system in your environment.

  3. Pilot

    One real unit or module, released through your PLM as today. Then scale.

Julian Freiberger

Julian Freiberger

Founder · RoutingIQ GmbH – a Freiberger.Aero company

Just a question? hello@routingiq.com

Questions we are asked

Does RoutingIQ replace NX Routing?

No. NX remains your authoring tool, and the results are native NX routings. RoutingIQ takes over what NX does not do: keeping the routing in step with your design – continuously, by your rules, outside the CAD session.

Is RoutingIQ AI?

No, and that is deliberate. Teams searching for AI routing in NX or AI cable routing in CAD usually want one thing: the repetitive routing work to disappear. RoutingIQ does that with rules, not with machine learning – no training data, no black box, same input, same result.

For release and audit, that is the point: every routing is traceable and auditable.

Where does our data go?

Nowhere. RoutingIQ runs on your premises, also in air-gapped networks and for export-controlled data. Your PLM remains the owner of all design, geometry and ECAD data.

Do we need a new ECAD interface?

No. RoutingIQ plugs into your PLM. Your ECAD and MCAD stay as they are; cable lengths flow back toward ECAD on the path you choose.

Will our engineers be flooded with requests?

No. Decision requests are optional. You set which situations reach an engineer; everything else is handled automatically.

Which PLM and CAD systems are supported?

Today: Siemens Teamcenter and NX. Other PLM and CAD systems follow – talk to us about yours.

How is RoutingIQ licensed?

As a subscription, priced by routing volume, not by headcount. Installed on your premises.

Do you work with resellers and implementation partners?

Yes, and we would like to hear from you. We are open to resellers and implementation partners – especially those who already serve customers on Teamcenter and NX. Write to us and we will set up a conversation.