If PLM is integrated with CAD and technical documents (not a complete merger), what formats can it currently support? Are there any files that include software and hardware development documents?

CIMer PDM can recognize Solidworks, NX, Solid EDGE, PTC Creo, AutoCAD, Inventor, etc. CIMer integrates with CAD through the APIs provided by these CAD systems. If customization is required for integration with these CAD systems, CIMer can provide training and services for both the CAD API and the CIMer API.

Does the CIMer system offer functions such as countersigning, merging, withdrawal, and additional signing? Is its operability better than existing BPM approval systems?

CIMer's workflow engine offers features such as workflow customization, countersigning, document rejection, applying team roles to workflow projects, and specially assigning approvers. Special approvals will be for specific elements such as drawings (with interrelationships between drawings) and materials. Once approved, specific versions of these elements will be in a release state and cannot be modified. These features are not typically found in standard suite approval software.

How can we verify that the PLM and PDM systems remain compatible when the operating system is upgraded? How can we ensure seamless user workflow transition?

CIMer considered this issue from the outset. Its development environment follows Microsoft's .NET Framework architecture, using Microsoft IIS as the entry point for its Application Server. Furthermore, most mainstream CAD software development on the market is also based on Microsoft's .NET Framework. Therefore, they are essentially all on the same development platform. To date, Microsoft's Windows operating system still supports very old versions of the .NET Framework.

How can we integrate the data from the existing PLM system?

Taking the integration of the Windchill PLM system as an example, CIMer serves as Windchill's front-end drawing processor, providing design units with collaborative design, file sharing, attribute data maintenance, component structure creation, BOM generation, drawing review, and project schedule control during the product design phase. Similarly, CIMer can also serve as a front-end drawing processor for mainstream PLM systems such as ENOVIA and Teamcenter.

We have three companies. Can we share a single PDM system? Will there be any problems for the other two companies' users when they connect to the server via the Internet?

The CIMer system operates on TCP/IP, so in principle, there should be no problem accessing data over the network. However, since CAD drawings are relatively large data sources, it is necessary to pay attention to the potential limitations imposed by network bandwidth and speed.

How can we achieve paperless manufacturing by enabling manufacturers or customers to participate in the review and design of design documents?

CIMer PDM has a web interface that can be viewed on-site via computer/tablet/mobile phone. It can be used anytime, anywhere, and on any device, saving on tree felling.

If a CIMER is running an MBOM/SBOM on a PLM system, what will it do?

In ERP systems, MBOM (Master Inventory Management) considers issues such as inventory, procurement, and manufacturing processes. CIMer, currently focused on product development and design, does not record any inventory, procurement, or manufacturing process information within its system. However, we already have the architecture for these functional modules, which can serve as development targets. At this stage, CIMer integrates with ERP systems using APIs from both ends, allowing users to directly query warehouse inventory, supplier information, etc., during product development.

Home
FAQ

You can find the answers to the most common questions here!

Q
If PLM is integrated with CAD and technical documents (not a complete merger), what formats can it currently support? Are there any files that include software and hardware development documents?

A
CIMer PDM can recognize Solidworks, NX, Solid EDGE, PTC Creo, AutoCAD, Inventor, etc. CIMer integrates with CAD through the APIs provided by these CAD systems. If customization is required for integration with these CAD systems, CIMer can provide training and services for both the CAD API and the CIMer API.
Q
Does the CIMer system offer functions such as countersigning, merging, withdrawal, and additional signing? Is its operability better than existing BPM approval systems?

A
CIMer's workflow engine offers features such as workflow customization, countersigning, document rejection, applying team roles to workflow projects, and specially assigning approvers. Special approvals will be for specific elements such as drawings (with interrelationships between drawings) and materials. Once approved, specific versions of these elements will be in a release state and cannot be modified. These features are not typically found in standard suite approval software.
Q
How can we verify that the PLM and PDM systems remain compatible when the operating system is upgraded? How can we ensure seamless user workflow transition?

A
CIMer considered this issue from the outset. Its development environment follows Microsoft's .NET Framework architecture, using Microsoft IIS as the entry point for its Application Server. Furthermore, most mainstream CAD software development on the market is also based on Microsoft's .NET Framework. Therefore, they are essentially all on the same development platform. To date, Microsoft's Windows operating system still supports very old versions of the .NET Framework.
Q
How can we integrate the data from the existing PLM system?

A
Taking the integration of the Windchill PLM system as an example, CIMer serves as Windchill's front-end drawing processor, providing design units with collaborative design, file sharing, attribute data maintenance, component structure creation, BOM generation, drawing review, and project schedule control during the product design phase. Similarly, CIMer can also serve as a front-end drawing processor for mainstream PLM systems such as ENOVIA and Teamcenter.
Q
We have three companies. Can we share a single PDM system? Will there be any problems for the other two companies' users when they connect to the server via the Internet?

A
The CIMer system operates on TCP/IP, so in principle, there should be no problem accessing data over the network. However, since CAD drawings are relatively large data sources, it is necessary to pay attention to the potential limitations imposed by network bandwidth and speed.
Q
How can we achieve paperless manufacturing by enabling manufacturers or customers to participate in the review and design of design documents?

A
CIMer PDM has a web interface that can be viewed on-site via computer/tablet/mobile phone. It can be used anytime, anywhere, and on any device, saving on tree felling.
Q
If a CIMER is running an MBOM/SBOM on a PLM system, what will it do?

A
In ERP systems, MBOM (Master Inventory Management) considers issues such as inventory, procurement, and manufacturing processes. CIMer, currently focused on product development and design, does not record any inventory, procurement, or manufacturing process information within its system. However, we already have the architecture for these functional modules, which can serve as development targets. At this stage, CIMer integrates with ERP systems using APIs from both ends, allowing users to directly query warehouse inventory, supplier information, etc., during product development.