Without the platform
Information about Product Engineering (PLM) lives in separate spreadsheets, and nobody knows which version is current.
With Partiu Formatura
7 modules share the same class, graduate and event records.
Finance and management · Product Engineering (PLM)
Why the bill of materials changed, who approved it and when it takes effect
Engineering governance on top of the factory. Each product has a lifecycle stage, a revision and a technical sheet with specification and tolerance; drawings, artwork and certificates are versioned with approval and expiry. The engineering change records the reason, the reviews, what to do with the old stock and the date it takes effect, and creates the new bill of materials version directly in Production Planning. New product projects move through five decision gates, and suppliers are approved part by part.
The problem and the solution
What changes when Product Engineering (PLM) works inside the platform
This is connected information about classes, graduates and events across 7 modules, replacing scattered spreadsheets and messages.
Without the platform
A request for a number takes time because someone has to combine data from several places.
With Partiu Formatura
Lifecycle and Technical Sheet and Versioned Technical Documents update together, with figures ready for the next meeting.
Without the platform
The process depends on who is working that day, and its history disappears.
With Partiu Formatura
Everyone follows the same workflow, with recorded actions and role-based permissions.
Without the platform
Connecting with other departments means exporting spreadsheets and entering data again.
With Partiu Formatura
Product Engineering (PLM) shares information directly with other areas of the platform.
How it works
How information moves through Product Engineering (PLM)
Each step is a real module in this area. Its output moves to the next step without anyone entering the same information again.
What is available in Product Engineering (PLM)
- Lifecycle and Technical SheetWhich stage each product is in and what it must meet to be compliant.7
- Versioned Technical DocumentsDrawings, artwork and certificates with version, approval and expiry.4
- Engineering ChangeFrom the request to the new version released in Production Planning, with approval levels and segregation of duties.7
- Structure and Impact AnalysisWhat changes if a component is replaced, with no side spreadsheet.4
- New Product ProjectsThe development funnel in five decision gates.5
- Approved Supplier per ComponentWho is approved to supply each part, and what has no source.4
- Governance and PermissionsWho looks, who maintains the sheet, who runs changes and who approves.3
Featured
The structure only changes with a reason, a review and an effective date
The engineering change records what is wrong today, what changes, what to do with the old stock and when it takes effect. Whoever opened it cannot approve it, and the new bill of materials version starts as a draft in Production Planning, copied from the previous one. On completion, the product revision moves up one letter.
See this in action- Lifecycle from concept to obsolete, with a reason for every change
- Specification with tolerance and a critical flag
- Versioned documents with approval and expiry
- Where-used up to 6 levels and impact on open orders
- New product projects in five gates
- Approved supplier per component
Lifecycle and Technical Sheet
Which stage each product is in and what it must meet to be compliant.
- Catalog opened with every manufactured and semi-finished item from Production Planning, with no parallel product record
- Stages concept, development, pilot, released, in production, discontinued and obsolete, with a required reason for every change
- A manufactured item only goes to released with a released bill of materials in Production Planning, a rule the company can turn off
- Product revision (A, B, C) kept apart from the internal bill of materials version, moving forward on its own with each completed change
- Sheet with product line or family, engineering owner, target cost, target price, planned launch and planned discontinuation
- Specification by group, characteristic, value, unit, tolerance and test method, with a critical flag
- Product history with every stage change, document and engineering change
Versioned Technical Documents
Drawings, artwork and certificates with version, approval and expiry.
- Drawing, technical sheet, artwork, manual, certificate, test report, packaging and others, with files up to 50 MB stored in the cloud
- The same type and title become a new version, with the number going up on its own
- Draft, approved or obsolete status, and approving a version makes the previously approved one obsolete
- Expiry for certificates and test reports, with a dashboard warning as many days ahead as the company chooses
Engineering Change
From the request to the new version released in Production Planning, with approval levels and segregation of duties.
- Sequential code per company, type (correction, improvement, cost reduction, supplier change, regulatory, customer request) and priority
- Reason, what changes, cost impact and effectivity: immediate, from a date or when stock runs out
- Affected products with the source version and the disposition of old stock: use until depleted, rework, scrap or return to supplier
- Approval with a minimum number of reviews set by the company, from 1 to 5, and whoever opened the change cannot approve it
- One rejection closes the change, and rejecting requires a written review
- Implementing creates the new bill of materials version as a draft in Production Planning, copied from the source
- Completing requires every new version to be released in Production Planning, and the product revision moves up one letter
Structure and Impact Analysis
What changes if a component is replaced, with no side spreadsheet.
- Comparison between two bill of materials versions: components added, removed and with changed quantity, scrap or type
- Where-used, climbing the tree up to 6 levels
- Impact of the change: parent products, open production orders that consume the item and stock on hand
- Target cost compared with the standard cost calculated from the bill of materials
New Product Projects
The development funnel in five decision gates.
- Gates idea, feasibility, development, validation and launch
- Deliverables per gate, checked off when ready, and moving on requires the mandatory ones to be done
- Decision to go, hold, redo or stop, always with a written review
- Project with objective, budget, target date, owner and linked product
- Going through the last gate moves the product to released and closes the project
Approved Supplier per Component
Who is approved to supply each part, and what has no source.
- Component by supplier from the Purchasing record, with status approved, conditional, in qualification or blocked
- Manufacturer part number, priority and approval expiry
- List of purchased components used in a released bill of materials with no approved and valid source
- Approval done from the pending list or from the product sheet
Governance and Permissions
Who looks, who maintains the sheet, who runs changes and who approves.
- Separate permissions to view, maintain engineering data, run changes and projects, and approve
- Checks done on screen and again on the server
- A module separate from Production Planning: whoever plans the factory does not have to buy engineering governance, and the other way around
Checklist
Everything included in Product Engineering (PLM)
All 34 features in this area, grouped by module so you can compare systems item by item.
- Catalog opened with every manufactured and semi-finished item from Production Planning, with no parallel product record
- Stages concept, development, pilot, released, in production, discontinued and obsolete, with a required reason for every change
- A manufactured item only goes to released with a released bill of materials in Production Planning, a rule the company can turn off
- Product revision (A, B, C) kept apart from the internal bill of materials version, moving forward on its own with each completed change
- Sheet with product line or family, engineering owner, target cost, target price, planned launch and planned discontinuation
- Specification by group, characteristic, value, unit, tolerance and test method, with a critical flag
- Product history with every stage change, document and engineering change
- Drawing, technical sheet, artwork, manual, certificate, test report, packaging and others, with files up to 50 MB stored in the cloud
- The same type and title become a new version, with the number going up on its own
- Draft, approved or obsolete status, and approving a version makes the previously approved one obsolete
- Expiry for certificates and test reports, with a dashboard warning as many days ahead as the company chooses
- Sequential code per company, type (correction, improvement, cost reduction, supplier change, regulatory, customer request) and priority
- Reason, what changes, cost impact and effectivity: immediate, from a date or when stock runs out
- Affected products with the source version and the disposition of old stock: use until depleted, rework, scrap or return to supplier
- Approval with a minimum number of reviews set by the company, from 1 to 5, and whoever opened the change cannot approve it
- One rejection closes the change, and rejecting requires a written review
- Implementing creates the new bill of materials version as a draft in Production Planning, copied from the source
- Completing requires every new version to be released in Production Planning, and the product revision moves up one letter
- Comparison between two bill of materials versions: components added, removed and with changed quantity, scrap or type
- Where-used, climbing the tree up to 6 levels
- Impact of the change: parent products, open production orders that consume the item and stock on hand
- Target cost compared with the standard cost calculated from the bill of materials
- Gates idea, feasibility, development, validation and launch
- Deliverables per gate, checked off when ready, and moving on requires the mandatory ones to be done
- Decision to go, hold, redo or stop, always with a written review
- Project with objective, budget, target date, owner and linked product
- Going through the last gate moves the product to released and closes the project
- Component by supplier from the Purchasing record, with status approved, conditional, in qualification or blocked
- Manufacturer part number, priority and approval expiry
- List of purchased components used in a released bill of materials with no approved and valid source
- Approval done from the pending list or from the product sheet
- Separate permissions to view, maintain engineering data, run changes and projects, and approve
- Checks done on screen and again on the server
- A module separate from Production Planning: whoever plans the factory does not have to buy engineering governance, and the other way around
Want to see Product Engineering (PLM) in your operation?
See a demonstration using your own numbers, with no obligation. A conversation will help you decide whether the module solves your needs.