The Part Module manages "Parts", "Part" are designs, which are used to procure, manufacture or assemble a product. Parts can be components, sub-assemblies or complete Product assemblies (ref. Part Types further down). Parts utilises the same effecient review/approval, revision control and traceability functionality as the document module and adds functionality required for PDM (Product Data Management).
Depending on your need, the Part module manages all parts down to lowest level standard components, or it manages e.g. sub-parts on a procurement level.
The Part module enables fast development and maximum reuse of existing designs/IP’s. Cloning on various levels of a structure is supported and enables efficient creation of product variants. The part module supports both waterfall and agile product development and still allow compliance with rigorous QA/RA practice.
Each company can create various types of parts that are needed. Each part type can have their own sets of metadata, e.g. electrical parameters for electrical part types, material parameters for mechanical part types, etc. Certain of these parameters can be made mandatory, to enforce that critical data are actually described and approved. For each part, there can be stored documents, drawings, etc., either on the part itself on on referenced documents.
Parts can also manage standard components and related data like datasheets, parameters and procurement, manufacturer and supplier information.
BOM and Structures
The Part module can be used to create and maintain product structures by applying references from parent part to child parts. Highstage prevents circular references and a reference may be static locked to a specific version or dynamic pointing to latest approved version.
The product structure elements can hold any type of product data like product sheets, specifications, designs, drawings, assembly instructions, test-specifications/instructions, manuals etc. As a whole, the complete product structure comprises all relevant information about the product.
Structured product release
Highstage enforces bottom-up approval process for the product structure, providing a structured and stringent release process for products. No part can be approved until all child parts and documents are approved first. This contributes to a higher level of knowledge sharing, and increased transparency of the development process within the various product-disciplines.
Documentation package exports
Advanced export functionality enables effective generation of BOM's (Bill of Material) and documentation packages for external partners, e.g. suppliers. BOM/Documentatin packages can be generated from any level in the product hierarchy, and can be exported in many ways.
Highstage's own mail journalling system can be used to submit document packages to suppliers, or suppliers could access Highstage directly to download the packages.
Re-use your base design in as many product variants as you like. The strong reference feature of Highstage guarrantees stable products in a changing world. Approve the core product as a base part, and use this base part in as many products as you want. Each of these variants can the be equipped with additional parts as required, for e.g. localization kits, colours, etc.
All disciplines - all formats - one product
The Highstage product structure brings together all disciplines into one product model. This gives the product/project manager a better overview of status and progress, and ensures good interfaces and a common, structured product release.
Highstage Parts can contain any number of files of any type. Files may also be delegated to sub-documents (which is the most common way). Thereby Highstage invites the users to use their existing software and allow any kind of external software to be used instead of limiting contribution to specific tools or programs.
The Part module is system independent (MCAD/ECAD/etc.) and may be used by cross-functional teams designing and maintaining products using various tools.
Customers can choose to e.g. only import PDF's generated from the CAD tool, or manage the native CAD model in Highstage.
Besides the open file structure provided by Highstage, Integrations to various state of the art design tools have been developed.
M-CAD For Mechanical CAD an integration against Ansys SpaceClaim exists, that allows for rapid creation of structures directly from the CAD-tool. The Integration allows highstage to control components properties and provide data transfer between the design tool and the Highstage.
E-CAD For Electronical Development (E-CAD) an integration with Cadence's Orcad CIP exists. The Integration allows highstage to control components properties and provide data transfer between the design tool and the Highstage. BOM's, schemas and PCA/PCB's can be transferred from Orcad CIP to Higshtage.
ERP Highstage supports creating product/part data integration with other systems (ERP etc.) through various generally accepted standard technologies like https, web services, REST, SOAP, XML, JSON, SQL.
Available integrations are, amongst others:
- - Dynamics AX
- - Navision
- - Xledger
- - SuperOffice
Why Choose Highstage Part Module
The Part Module should be chosen because of its:
- All disciplines - one model - Highstage is unique in the way it can develop from a document control system to a complete corporate management system, e.g. PDM, PLM, etc.
- Structured product release - So simple it will actually be done
- Comprehensive documentation export - Get status of a document or a list of documents with a glimpse of an eye
- Independent PDM - Not exclusive to any particular M-CAD/E-CAD tool
- Starting point for PLM/IOT - With all your product data structured, you have an excellent starting platform for a PLM system by adding the Action Module, and for IoT management via the Device Module