Plan For Every Part
Plan for Every Part is a use case where a Mendix app takes the complex and large Bill of Material from Teamcenter and collaborate with teams and systems to govern of the status, attributes and the critical due dates on the development timeline of the product and its sub-systems.
Plan For Every Part
Plan For Every Part is a use case where a Mendix app takes the complex and large Bill of Material from Teamcenter and collaborate with teams and systems to govern of the status, attributes and the critical due dates on the development timeline of the product and its sub-systems.
How to setup
The application contains all of the data required on start up. The master data can be reset by signing in as an Administrator and navigating to Mock Data and selecting 'Reset Mock Data'.
The application can be requested, downloaded and can then be customised using Studio or Studio Pro to suit your needs.
Administrator - Responsible for the administration of the platform, including technical configuration and data management.
User - General user role for the different account disciplines (see below)
Program Manager - Ultimately responsible for the Program BOM
Anonymous - For anonymous access to the application
ProgramBOM - for managing the Bill of Materials information
SAP - for retrieving data from SAP
Custom Admin Module - for administration and custom layouts
Mock Data - enables creation of sample data for demonstration purposes
Teamcenter_Extension - extends the appstore TCConnector module
Teamcenter_Viewer_Extension - utilities to help with rendering 3D models from Teamcenter
BOM Dashboarding - manages the dashboard creation for the BOM
Users are linked to account disciplines. These are hard coded into the workflow to route the submissions.
- Manufacturing - Responsible for the Usage information
- Procurement - Responsible for the Supplier and Order information
- Warehousing - Responsible for the Location information
- Program Manager - Responsible for the overall Program
Data Model Description
The Program BOM contains all of the information for the Program BOM:
- Program - The program containing the different Bill of Materials
- Program BOM - The parent for the Bill of Materials
- BOM Line - Each line within the BOM. Hierarchies are set using the child BOM association
- BOM Line Data Generalisation - A generalisation to manage the different data groups connected to the BOM Line
- BOM Line Data Request - To manage the data request workflow
- BOMLineUsage, Supplier, ItemDetails, OrderDetails, LocationDetails - the information related to the BOM Line
The application has been designed to leverage mock data and user switcher has been provided for ease of demonstration.
Information can be generated or reset by the administrator by clicking Configurations -> Reset All MockData . This will read the JSON files located in the resources/mockdata folder and create corresponding data within the application. It will also create demonstration workflows at different stages and will update the Program BOM information from Teamcenter.
Bill Of Materials
Each Program BOM (item) has an associated Bill Of Materials. The BOM information is pulled from Teamcenter, using the Item ID of the top level item.
Each BOM Line has an associated status and an indicator as to whether it is On Time, Overdue or At Risk. The status is unique to the BOM line, whilst the Overdue nature cascades up from the children.
Information related to the BOM Line can be updated directly by the Program Manager, or data can be requested from other user types.
The Request process consists of a data request, assigned to an individual and then an approval step from the Program Manager.
When updating BOM Lines, cost and weight can either be calculated or manually entered. Calculated values will roll up the values from all of the children.
The Program Manager can define the objectives for the Program BOM, this can include target weights and costs. If a change to a BOM Line causes these objectives to be exceeded, a warning will appear.