Solution Partners
1. Oracle AutoVue – View Any File, From Right Inside PRO.FILE
When engineers and project stakeholders need to review technical documents, CAD drawings, or engineering files, the default answer is usually “open it in the native application.” That means switching tools, tracking down the right software version, and hoping the file opens cleanly. For anyone without a full CAD license, it means asking someone else to do it for them.
The Oracle AutoVue integration for PRO.FILE removes that friction entirely.
One Viewer for Every File Type
Oracle AutoVue connects directly to PRO.FILE, giving every user in your organization the ability to open, review, and mark up documents without leaving the PLM environment. Whether it’s a 2D engineering drawing, a 3D CAD assembly, a PDF, or a technical specification, AutoVue handles it natively. There’s no need to install the originating application, convert the file, or pass it off to someone who has the right license.
This matters most for the people who sit outside engineering — project managers, quality teams, procurement, and service — who regularly need to look at product documentation but don’t have (or need) a full CAD seat.
Annotation and Review, Built In
AutoVue includes markup and redlining tools that work directly on the source document within PRO.FILE. Review comments are stored alongside the document in the PLM system, keeping feedback traceable and connected to the correct revision. Reviewers can measure geometry, compare drawing versions, and add annotations — all without touching the native file.
For companies running formal design review or change management processes in PRO.FILE, this means every participant can engage meaningfully, regardless of their software setup.
Fewer Licenses, Faster Reviews
Because AutoVue supports over 500 file formats — including formats from major CAD vendors — organizations can reduce the number of costly CAD licenses needed solely for viewing purposes. Reviews happen faster when stakeholders don’t have to wait for exports or screenshots.
The integration keeps document access, viewing, and annotation activity inside PRO.FILE’s access controls and audit trail, so nothing falls outside the managed process.
If your team spends time working around file format barriers or routing documents outside your PLM system for review, the Oracle AutoVue integration is worth a closer look.
2. Invenio – Automate Your DMU Analysis With Job Server Extensions
Running geometric analysis, collision detection, and data reduction on complex 3D assemblies is critical work. It’s also timeconsuming when done manually. For engineering teams managing large product structures, waiting for individual jobs to complete before moving on is a real bottleneck.
The Invenio Job Server extensions for PRO.FILE solve this by automating the heavy lifting.
Background Processing for DMU Tasks
Invenio Virtual Technologies specializes in Digital MockUp (DMU) software used by leading manufacturers including Daimler, BMW, Magna, Bosch, and Continental. Their VTDMU platform handles complex engineering computations: collision and distance checks, geometric comparison between model versions, assembly and disassembly path calculation, data reduction, and automated image generation.
The Job Server extensions connect this capability directly to PRO.FILE’s product structure. Instead of manually triggering each analysis, teams configure jobs that run automatically — overnight, on schedule, or when a model version changes. PRO.FILE triggers the job, Invenio processes it, and results are stored back where engineers can act on them.
Catch Problems Earlier
One practical benefit is scale. Invenio’s Quality Monitor can process 50 million component pairings per night across 1,400 virtual assemblies, flagging potential collision or clearance issues for engineers to review the next morning. That kind of throughput isn’t possible manually.
Geometric difference analysis makes change management more concrete: when a new version of a component is released in PRO.FILE, the Job Server can automatically calculate what changed geometrically and surface that information alongside the revision data.
Data Reduction That Keeps Things Moving
Invenio’s data reduction algorithms can shrink a 1,200 MB assembly to 12 MB in under a minute, generating exact surface representations suitable for downstream use in visualization, service documentation, or supplier sharing. This happens as a managed job, not a oneoff manual export.
For manufacturers with large assemblies and regular revision cycles, connecting PRO.FILE to Invenio’s Job Server means less waiting, earlier problem detection, and a more automated path from design change to validated product structure.
3. HES – Connect PRO.FILE to Your ERP System
Product data managed in a PLM system and business data managed in an ERP system should reinforce each other. In practice, they often don’t. Parts masters created in PRO.FILE have to be manually reentered in SAP. BOMs updated in engineering don’t automatically reach purchasing. Documents filed in PRO.FILE aren’t visible to ERP users who need them.
The HES ERP Integration Framework for PRO.FILE changes that.
A Proven Integration Architecture
HES Digital Management GmbH has been building enterprise integrations for over 16 years. Their Integration Suite for PRO.FILE has been deployed successfully in over 300 installations worldwide. It’s built as a SAP Silver Partner solution and supports not just SAP but virtually any ERP — including AMS, PSI, ABAS, IFS, Infor, and Microsoft Business Central.
The architecture is modular. A base transmission layer handles the connection, and individual process modules can be activated for the data types you need: parts masters, BOMs, documents, projects, generic objects, change records, and links between objects.
Clear Rules for Who Owns What
One of the more practical aspects of the integration is how it handles data ownership. HES defines four distinct SAP use cases based on which system originates a document and what the other system is allowed to do with it. For example, in one scenario SAP is the owner and PRO.FILE is the storage location; in another, PRO.FILE owns and stores while SAP can only read. This prevents conflicts and keeps data governance clean.
Bidirectional data flows are secured via HTTPS, and the unique HES namespace in SAP prevents collisions with existing developments. With thousands of users in production, the system averages only 100 support tickets per year across its install base.
Compatible With Revalize Integration Hub
The HES Integration Suite works alongside the Revalize Integration Hub, giving teams flexibility in how they architect their integration landscape. For organizations already using or evaluating hubbased connectivity, HES complements that investment rather than replacing it.
For manufacturers where the gap between PLM and ERP creates manual work, the HES framework provides a structured, scalable way to close it.
4. EPLAN – Bring Electrical and Mechanical Engineering Together
Most manufacturers build complex machines or systems manage two distinct engineering worlds. Mechanical design lives in PLM — drawings, assemblies, parts lists, and change processes all managed in a system like PRO.FILE. Electrical and fluid engineering lives in EPLAN — schematics, wiring lists, cabinet layouts, and ECAD reports managed separately.
These two worlds intersect constantly. When a component changes on the mechanical side, the electrical design needs to reflect it. When a new part is added to an EPLAN project, it needs to exist in the parts master. Without integration, keeping them aligned requires manual coordination and creates data redundancy.
The PRO.FILE Connector for EPLAN resolves this at the system level.
One Product Model, Both Worlds
The integration brings ECAD data from EPLAN directly into PRO.FILE’s product structure. Wiring diagrams, connection lists, schematics for electrical and fluid systems, BOMs, and EPLAN reports are stored alongside mechanical data in a single, consistent product model. Engineers in either system work with current, accurate information.
Bidirectional synchronization keeps project attributes aligned automatically. PRO.FILE’s naming and numbering rules apply in EPLAN, so parts and documents follow consistent identification standards across both tools. Catalog parts are synchronized in both directions, including attribute values and classifications.
Support for the Full Change Process
The integration isn’t limited to data storage. The full PRO.FILE release and change management workflow applies to EPLAN data. When an EPLAN project is ready to release, it moves through the same approval process as any other engineering document in PRO.FILE. Changes are tracked, revisions are managed, and the complete history is maintained.
BOM management benefits too. BOMs generated in EPLAN can be created and updated in PRO.FILE through largely automated processes, reducing manual rework and the risk of discrepancies between the electrical and mechanical parts lists.
Competitive Advantage Through Data Integration
Access to cost data, supplier information, inventory levels, and quality records is available from early in the product development process. Teams no longer have to wait until a design is mechanically complete before engineering can see what a component costs or whether it’s in stock.
For manufacturers where electrical and mechanical engineering are closely interdependent, this integration removes one of the most persistent sources of rework and coordination overhead.
5. Microsoft – Work in the Tools Your Team Already Uses
Engineering teams invest heavily in PLM systems to manage product data. But a large portion of the people who need to interact with that data — project managers, operations staff, leadership, procurement, and service teams — spend most of their working day in Microsoft Office, Microsoft Teams, and SharePoint. Asking those users to adopt a separate PLM client for occasional access creates adoption barriers and means product data gets shared outside the managed system.
The Microsoft integration for PRO.FILE bridges that gap.
Office Documents, Right in PRO.FILE
PRO.FILE VIEW, the built-in viewer integrated into the PRO.FILE V10 Desktop Client, handles Office documents natively. Word documents, Excel files, PowerPoint presentations, emails, images, and even video files open directly in the PRO.FILE preview pane. There’s no need to launch separate applications or break out of the PLM workflow to see document contents.
This extends to less obvious formats too — voice mail messages in MP3 format, for example, can be played directly in PRO.FILE without opening a media player. The goal is simple: stay in one system, avoid context switching, and keep all document interactions inside the managed environment.
Collaboration Without the Context Switch
For teams using Microsoft Teams and SharePoint as their primary collaboration layer, the integration allows product documents and data managed in PRO.FILE to be accessed and referenced without leaving those environments. Stakeholders can participate in design reviews, access current document versions, and track change processes through familiar Microsoft interfaces.
This is particularly valuable during cross-functional reviews where not everyone on the call has a PRO.FILE client or engineering background. Making the right document available in the right tool at the right time keeps reviews moving.
Consistent Data, Across Both Systems
Because the integration keeps documents in PRO.FILE as the system of record, there’s no risk of people working from outdated SharePoint copies or emailed attachments. Access permissions from PRO.FILE apply, so information reaches the right people without escaping governance.
For organizations that run Microsoft 365 as their productivity backbone, connecting it to PRO.FILE reduces the friction between where people work and where product data lives.
6. Kisters – HighPerformance 3D Viewing Directly in PRO.FILE
Design reviews, supplier conversations, service documentation, manufacturing instructions — all of these require people outside the engineering team to look at 3D models. The traditional answer has been to export screenshots, generate PDFs, or ask an engineer to share their screen. These workarounds are slow, create version control problems, and keep nonengineers one step removed from the actual product data.
PRO.FILE VIEW 3D+, powered by Kisters technology, makes that unnecessary.
Native CAD Viewing, No CAD License Required
PRO.FILE VIEW 3D+ is fully integrated into the PRO.FILE V10 Desktop Client and supports native multi-CAD format reading — including SolidWorks, Solid Edge, Inventor, NX, and CATIA — without requiring those applications to be installed. A 200 MB CATIA assembly loads in under one second. Neutral formats like JT and STEP are also supported for environments where format agnostic workflows are preferred.
This means anyone with PRO.FILE access can open a 3D model directly from the document manager, see the actual current geometry, and work with it — not a static export of it.
Tools for Everyone, Not Just Engineers
The viewer includes capabilities that go well beyond simply rotating a model. Users can measure distances and angles, add annotations and redlines directly on the geometry, create cross sections to inspect internal structure, and generate explosion views to understand assembly relationships. Geometry comparison between two model versions is available as well, surfacing exactly what changed geometrically without needing to interpret a change log.
Individual views with dimensions and markups can be saved and shared, making it practical to communicate specific design intent or quality concerns without a CAD seat on either end of the conversation.
Available as a Standalone Application Too
For users who need 3D viewing capability outside the PRO.FILE client — field service, external partners, or standalone review stations — PRO.FILE VIEW 3D+ is also available as a standalone Windows application. It maintains the same format support and functionality without requiring a full PRO.FILE installation.
For organizations where 3D model access has historically been limited to engineering, this integration opens that capability to the entire business in a controlled, PRO.FILE-integrated way.
