PIM Program Imperatives Management
Data classification: GM_Confidential
Domain: Finance IT - Vehicle Cost Optimization / Future Product Cost
Application / data product ID: ASMS 118966 - Program Imperatives Management (PIM)
Primary business capability: Program imperative target allocation, status-to-target tracking, material cost, and vendor tooling analytics
Primary application storage: Azure Database for PostgreSQL
Analytics surfaces: Power BI semantic models and Databricks-backed curated datasets
Overview
PIM (Program Imperatives Management) is GM's global application for managing new product program imperatives from early program framing through launch. It gives vehicle program teams one place to define material cost and vendor tooling targets, allocate targets across programs and regions, track current position against target, manage potentials and bookings, and capture milestone snapshots for business-case and gate reviews.
Key benefits
PIM helps business and analytics users manage program imperatives with a consistent view of targets, current position, opportunities, and milestone snapshots.
| Benefit | How it helps |
|---|---|
| Status-to-target management | Is the program above or below target for material cost or vendor tooling, and which owners need action? |
| Target allocation | How are approved targets allocated across programs, regions, SMTs, VPPS level 3 categories, BOM levels, and functional owners? |
| Potentials and booking | Which cost, mass, material, or tooling opportunities have been identified, reviewed, booked, or left open? |
| Milestone control | What did the program position look like at DSI, AFI, PFI, MVR, CSO, VDR, or another review point? |
| Executive reporting | Which material cost and vendor tooling exposures require leadership attention across programs or regions? |
Who uses it
PIM serves approximately 2,600 registered users globally across engineering, GPSC, logistics, cost, program management, and leadership roles.
| Team / persona | How they use PIM |
|---|---|
| Vehicle program leadership | Review program imperatives, gaps, milestone snapshots, and executive reporting for business-case and gate decisions |
| VSE / PEM and VPE roles | Manage program actions, potentials, and trade-offs tied to engineering execution and program status |
| GPSC PPM / buyers | Support purchasing and supplier-facing cost or tooling opportunities that affect program position |
| MIM, SMT, and cost engineering teams | Enter, review, and book material, mass, cost, and vendor tooling changes at the appropriate structure level |
| Logistics and related functional teams | Contribute program-impacting inputs and actions where logistics or regional execution affects imperatives |
| Finance IT Vehicle Cost Optimization | Own and support the application in the future product cost ecosystem |
| Finance Data / analytics users | Consume PIM Analyzer semantic models, curated Databricks datasets, and Power BI reporting for cross-program analysis |
Core business scope
PIM covers global new vehicle programs across GMNA, GMIO, GMSA, GME/OV, and related business units. Its main business scope is material cost, vendor tooling, and related potential opportunities for future programs.
| Subject | What it captures |
|---|---|
| Program and baseline setup | Donor baselines, future program setup, program structures, and initial material cost or tooling context |
| Target definition | Approved targets for material cost, vendor tooling, and related imperatives |
| Target allocation | Allocation and localization of targets by program, region, SMT, VPPS level 3, part, BOM level, and owner |
| Current position | Current material cost and tooling position compared with approved target |
| Potentials and tasks | Cost, mass, material, and tooling opportunities, related actions, and ownership workflows |
| Booking workflows | Review and booking of approved changes into program positions |
| Snapshots | Program state captured at milestone points such as DSI, AFI, PFI, MVR, CSO, and VDR |
| Change history | Comprehensive change logs that support traceability from donor baseline through current position |
| Reporting outputs | PIM Analyzer semantic models, raw data outputs, and Power BI reporting datasets for program and executive analytics |
Source systems by business subject
PIM combines operational program data, engineering and product structure references, security data, and cost/tooling datasets.
| Subject area | Key source patterns |
|---|---|
| Enterprise master and program data | GPDS, GDiMPS, and SAP program or engineering structures |
| Product and content reference | GPD UPC, FNA, VPPS, and RPO master data for content and sales configuration context |
| Directory and security | LDAP-based user and role information used for granular role-driven access control |
| Cost and tooling data | Databricks-hosted TCPCM_SRC schema for vendor tooling cost information used by the PIM / VTAT solution as part of Oracle-to-Databricks migration work |
| Capital and cost analytics | Databricks datasets connected to capital and cost data, including MaRS-sourced datasets where applicable |
| Operational application data | PIM application data stored in Azure Database for PostgreSQL by environment |
| Reporting and analytics | Databricks-landed PIM data exposed through Power BI semantic models and PIM Analyzer datasets |
Business measures and rules
PIM analysis is most useful when the user is clear about whether the question is about an approved target, an allocated target, a current position, a potential, a booked change, or a milestone snapshot.
| Measure / rule | Business meaning |
|---|---|
| Target | Approved program imperative value for material cost, vendor tooling, or related scope |
| Allocated target | Target distributed to a region, SMT, VPPS level 3 category, part, BOM level, or functional owner |
| Current position | Latest recorded program position for material cost, tooling, or related imperative scope |
| Status to target | Difference between target and current position, used for gap management and leadership review |
| Donor baseline | Starting baseline used to compare future program target and current position against a prior or reference program |
| Potential | Identified cost, mass, material, or tooling opportunity that may change the program position if reviewed and booked |
| Booking | Approved update that moves a potential or change into the managed program position |
| Snapshot | Point-in-time copy of program state used for milestone reviews and auditability |
| Change log | Historical record of updates used to trace how the program position changed over time |
When comparing reports, confirm the grain and scenario being used. Program-level totals, SMT views, VPPS level 3 rollups, part or BOM details, current positions, and milestone snapshots can each answer different questions.
Reporting, interfaces, and consumers
PIM is exposed through application, reporting, and curated-data surfaces.
| Interface / consumer | View of the data | Primary use cases |
|---|---|---|
| PIM web application | Operational application workflow | Target setup, target allocation, status-to-target tracking, potential entry, review, booking, and milestone snapshots |
| PIM Analyzer semantic models | Curated semantic reporting layer | Power BI reporting, program analytics, and executive-ready reporting |
| Power BI | Business reporting layer | Cross-program and cross-region reporting for cost, vendor tooling, targets, gaps, and milestone status |
| Future Product Cost ecosystem | Related cost optimization solutions | Reuse of material cost, vendor tooling, and program imperative outputs |
| PIM / VTAT analytics | Vendor tooling and program imperative data | Tooling cost capture, reporting, and migration from older source patterns |
| Databricks curated datasets | Analytics and data engineering layer | Data landing, semantic model support, downstream analytics, validation, and advanced analysis |
| Finance IT operations | Application and infrastructure support context | Cloud migration support, environment operations, and ongoing application support |
Application links:
| Environment | URL |
|---|---|
| Development | https://pim-dev.musea2.azure.ext.gm.com |
| Test | https://pim-tst.musea2.azure.ext.gm.com |
| Production | https://pim.musea2.azure.ext.gm.com |
PIM belongs to the Finance IT Vehicle Cost Optimization persistent team within the broader Fin_IT_Analytics portfolio. It sits in the capital and future product cost ecosystem alongside related applications such as CCR, CTLF, Future Product Cost, and other finance analytics and planning solutions.
Security and access model
PIM uses role-based workflows and shared views so different business roles can enter, review, book, and analyze the data appropriate to their responsibilities.
| Access pattern | Intended audience | Typical capability |
|---|---|---|
| PIM application user access | Approved program, engineering, GPSC, logistics, cost, and leadership users | Use the web application according to assigned role and workflow responsibilities |
| Role-driven workflow access | VSE/PEM, VPE, GPSC PPM/buyer, MIM, SMT, cost engineering, and related roles | Create, review, manage, or book potentials and target updates at the appropriate grain |
| Power BI / semantic model access | Approved analytics and leadership users | Consume PIM Analyzer and program reporting outputs |
| Databricks analytics access | Approved data engineering and analytics users | Work with curated PIM, capital, cost, and vendor tooling datasets for analysis and reporting support |
| Azure platform access | Approved application support and engineering users | Operate Azure Container Apps, Azure Database for PostgreSQL, deployment pipelines, and supporting infrastructure through GM Azure RBAC and PIM access controls |
Getting access
For application or reporting access, start with the PIM support and operating channels used by the Finance IT Vehicle Cost Optimization team. The main team channel listed for the application is #pim-team in GM Slack.
When requesting access, include the program, region, role, reporting need, and whether the request is for the PIM application, Power BI / PIM Analyzer reporting, Databricks analytics, or Azure platform support. Access is role-driven, so the business justification should explain the workflow or reporting responsibility being performed.
Where the data lives
PIM has an operational application store and a curated Databricks gold serving layer.
The Databricks gold serving layer is:
finance_prod.gold_program_imperatives_management_gbl
This schema is the best starting point for curated PIM analysis in Databricks. It contains managed PIM gold-layer views for target allocation, status-to-target reporting, material cost, vendor tooling, logistics, snapshots, security, and reference dimensions. Business users should usually start with the PIM application, PIM Analyzer, or Power BI reporting before moving to direct-query analysis in Databricks.
The gold layer is organized around a few practical object families:
| Object family | What it supports |
|---|---|
| Program and tracking model views | Program team, vehicle tracking model, build region, brand, body, drive, country, donor vehicle, and other program framing attributes |
| Material cost views | Costbook, target, potential, change, and snapshot analysis for part-level and program-level material cost questions |
| Vendor tooling views | Vendor tooling targets, details, potentials, and booked deltas used for tooling exposure and status-to-target analysis |
| Logistics views | Donor, future, and snapshot logistics views for inbound logistics and BOM-change context |
| Product structure and reference views | VPPS, SMT, UPC/FNA, part, date, currency, FX, source identifier, and program event references |
| Security and refresh views | Role/security orientation and the latest gold-layer refresh timestamp |
The strongest direct-query pattern is to start with the business question, then choose the grain: program or tracking model for leadership views, SMT or VPPS for rollups, part/BOM for reconciliation, and snapshot views for milestone or historical comparisons.
The operational application data is stored in Azure Database for PostgreSQL. Databricks is used for analytics landing and curated data connected to PIM, capital, vendor tooling, and cost datasets. The current Confluence operating page also identifies TCPCM_SRC as a Databricks-hosted schema used to provide vendor tooling cost information into the PIM / VTAT solution as part of Oracle-to-Databricks migration work.
Refresh guidance: the PIM gold layer includes refresh tracking through finance_prod.gold_program_imperatives_management_gbl.refresh_dates. For time-sensitive analysis, confirm the latest refresh timestamp before comparing PIM application activity with Databricks or Power BI reporting.
Useful data objects and analytics starting points
These entries are orientation points from the PIM gold layer and operating context, not a complete schema inventory.
| Object or dataset | What it is used for |
|---|---|
| PIM operational PostgreSQL database | Primary application store for target allocation, current position, potentials, bookings, snapshots, and change history |
| PIM Analyzer semantic models | Curated reporting layer used by Power BI for program and executive analytics |
finance_prod.gold_program_imperatives_management_gbl.tracking_model_vw | High-use program and vehicle tracking model orientation for build region, brand, donor vehicle, and program framing |
finance_prod.gold_program_imperatives_management_gbl.program_vw | Program team and program identifier reference for joining PIM facts to program-level reporting |
finance_prod.gold_program_imperatives_management_gbl.costbook_vw | Material cost costbook view used for part, SMT, VPPS, unit cost, status, and currency-oriented analysis |
finance_prod.gold_program_imperatives_management_gbl.pgm_material_cost_ptnls_vw | Program-level material cost potentials, including change category, current step, confidence, impact, and booking status context |
finance_prod.gold_program_imperatives_management_gbl.ptnls_material_cost_vw | Part-level material cost potential detail for deeper reconciliation and potential-to-costbook analysis |
finance_prod.gold_program_imperatives_management_gbl.change_material_cost_vw | Booked material cost changes and explanations, including booking dates, categories, quantities, and derived reporting-currency amounts |
finance_prod.gold_program_imperatives_management_gbl.tgt_material_cost_vw | Material cost target values by program, tracking model, SMT, and target status |
finance_prod.gold_program_imperatives_management_gbl.snap_material_cost_vw | Point-in-time material cost snapshots for event or milestone comparisons |
finance_prod.gold_program_imperatives_management_gbl.vendor_tool_dtl_vw | Vendor tooling detail, including parts, buyer/DRE context, event status, costbook amount, and reporting-currency tool cost values |
finance_prod.gold_program_imperatives_management_gbl.tgt_vendor_tool_vw | Vendor tooling target values and contingency status for program-level tooling target analysis |
finance_prod.gold_program_imperatives_management_gbl.ptnls_vendor_tool_vw | Vendor tooling potentials, booked deltas, approvals, and related SMT/VPPS context |
finance_prod.gold_program_imperatives_management_gbl.future_logistics_bom_chg_vw | Future logistics BOM-change analysis, including before/after UPC, FNA, SMT, VPPS, and delivery context |
finance_prod.gold_program_imperatives_management_gbl.vpps_vw, smt_vw, upc_fna_vw, and part_vw | Reference views for rollups, filters, part orientation, and product-structure joins |
finance_prod.gold_program_imperatives_management_gbl.program_event_vw | Program event and snapshot status reference for milestone-based reporting |
finance_prod.gold_program_imperatives_management_gbl.refresh_dates | Gold-layer refresh tracking; use the latest timestamp to confirm whether reporting data is current |
TCPCM_SRC | Databricks-hosted vendor tooling cost source used by the PIM / VTAT solution during Oracle-to-Databricks migration work |
| MaRS-sourced datasets | Capital and cost analytics inputs connected to PIM and the broader future product cost ecosystem |
For most business analysis, start with the PIM application or PIM Analyzer / Power BI reporting before moving into Databricks or operational database objects.
When direct Databricks analysis is needed, use these starting points:
| Analysis question | Start with |
|---|---|
| Program or vehicle tracking model orientation | tracking_model_vw, joined to program_vw when program team context is needed |
| Material cost current position or costbook reconciliation | costbook_vw with part_vw, smt_vw, vpps_vw, and upc_fna_vw as reference views |
| Material cost targets and status-to-target analysis | tgt_material_cost_vw, with SMT or VPPS target views when rollup grain matters |
| Material cost opportunities and booked changes | pgm_material_cost_ptnls_vw, ptnls_material_cost_vw, and change_material_cost_vw |
| Vendor tooling target and detail analysis | tgt_vendor_tool_vw, vendor_tool_dtl_vw, and the SMT/VPPS vendor tooling target views |
| Vendor tooling opportunities | ptnls_vendor_tool_vw |
| Milestone or point-in-time comparisons | Snapshot views such as snap_material_cost_vw, snap_costbook_vw, and the target snapshot views |
| Logistics before/after or BOM-change questions | future_logistics_bom_chg_vw plus donor, future, and snapshot logistics views |
| Refresh validation | refresh_dates |
Getting started path
- Start in the PIM production application when the question is operational: target allocation, current position, potentials, bookings, snapshots, or role workflow status.
- Use PIM Analyzer or Power BI when the question is analytical: cross-program comparison, regional exposure, executive summary, or milestone reporting.
- Use the Databricks gold layer when the question requires curated dataset exploration, downstream reporting support, vendor tooling data validation, logistics/BOM-change analysis, or migration analysis.
- In Databricks, choose the right grain before comparing values: program, tracking model, SMT, VPPS, part, BOM, target, potential, booked change, or snapshot.
- Check
refresh_datesfor the latest gold-layer refresh when reconciling current application activity to reporting outputs. - Contact the Finance IT Vehicle Cost Optimization / PIM support channel for role access, workflow questions, or environment-specific details.
Reference links
| Reference | URL |
|---|---|
| PIM Confluence page | https://gm-sdv.atlassian.net/wiki/spaces/IT/pages/989594163/118966+-+PIM |
| PIM development application | https://pim-dev.musea2.azure.ext.gm.com |
| PIM test application | https://pim-tst.musea2.azure.ext.gm.com |
| PIM production application | https://pim.musea2.azure.ext.gm.com |
| PIM Slack channel | https://gm.enterprise.slack.com/archives/C0AE82APEDR |