New Features

New Product Introduction (NPI)

No	Feature	Description
1	NPI Structured BOM Ingestion	Ability to ingest a structured NPI BOM (in a pre-defined / pre-configured template - sample attached in Documentation section)
2	Create BOM - Upload Excel	Create a BOM by uploading Excel
3	Create BOM - BOM Copy	Create a BOM by copying an existing NPI BOM
4	Program Management	Configure Program Parameters such as Program Manager, Forecast, Users Team Permissions etc. Configure Checkpoint / Phase Gate Review dates Define Maturity Levels 1 to 5 Configure Risk
5	Stage Gate Management	Configure Stages / Timelines Stage Process Graph Define Gatekeepers (without workflow)
6	BOM Management	View BOM with structure Edit BOM Onscreen Edit BOM via Excel upload (Bulk edit) View changes on-screen Multi-vendor pivot view (MPN View)
7	BOM Compare	Allows the user to compare the existing Program / Revision with that of another Rev within same NPI Program Rev of another NPI Program
8	Collaboration & Notification	Enables the user to collaborate with other user(s) at multiple levels (Row level, Widget level, Program level etc - depending on persona) through : Tagged conversations Tasks Documents attached to messages
9	View History - BOM level	Users would be able to see changes (At BOM level) made between each Check Out / Check In
10	Integration to Levadata Systems	CMS Opportunities Leva (Chatbot)
11	BOM Analytics	Part Counts Opportunity Drivers Cost Drivers Risk Drivers

A Program can be associated with only one Product. Phase 2 will allow 1-many relationships.
BOM Template is defined while onboarding. Any changes to template will involve effort till Template Configuration is released.
Additional columns (other than those defined in template) will be captured as a snapshot and displayed in UI.
Gatekeepers will need to approve the Program Stage in no specific workflow
Maturity Level is for definition only. It is not currently used in / for any calculation
Cost Rollup is performed bottom up i.e. MPN Cost is aggregated into CPN which is then aggregated into SubAssembly and then into Product.
Cost Rollup Flag is used to define if a particular Component’s cost should be rolled up or not. If the flag of the parent is Y, then the children will be flagged N (and vice versa) to avoid double count.
Part cost is editable only at the MPN level. So if only CPN exists, it is recommended that a dummy MPN is added to be able to enter part cost (If no MPN is given, LD will generate dummy MPN)
Costs can be pulled from CMS only at CPN level. If the CPN has even a single MPN, Autofill will not pull data in order to avoid confusion on No. of MPNs vs Split assign. Users are encouraged to pull data at CPN level and then modify the data attributes
Multi CMODM data is not handled as part of the MVP i.e., System does not consider CMODM as part of key while pulling data. This case will be scoped as part of Phase 2