CPURAM Cost Per Unit Read Across Matrix
Data classification: GM_Confidential
Domain: Finance IT
Application / data product context: CPURAM Cost Per Unit Read Across Matrix (ASMS 188520)
Primary business capability: Cross-functional vehicle, propulsion, BOM, part, RPO, and option-cost analytics across product, cost, logistics, purchasing, and supplier data
Catalog schema: Finance_prod.gold_vehicle_cost_per_unit_gbl
Overview
CPURAM is a cross-functional analytics product that links global product, cost, logistics, purchasing, and supplier information so users can investigate vehicle and propulsion-systems data over time.
It uses the VOIC construct, or Vehicle of Interest Configuration, to make large data sets smaller and easier to analyze in business context.
At a business level, CPURAM helps users move from summary cost and configuration questions into deeper analysis across vehicles, propulsion systems, parts, BOMs, RPOs, and related configuration views.
CPURAM is designed to answer practical questions such as:
- How do vehicle costs compare across cost periods, configurations, and reporting views?
- What part-level attributes and costs explain movement in a vehicle or propulsion-system result?
- How do BOM comparisons differ period over period or under a true-cost lens?
- Which RPOs, options, or VIN populations drive a given cost or penetration pattern?
- What report, cube, or direct-query path is best suited for a specific analytical need?
Key benefits
- Connects product, cost, logistics, purchasing, and supplier data in a single analysis environment
- Simplifies complex analytical data through the VOIC construct
- Supports multiple reporting paths across vehicle, part, BOM, RPO, VOIC, Super Six, and propulsion topics
- Provides both report-driven and direct-query access patterns for business and technical users
- Includes training, examples, reference content, and direct team support to speed adoption and troubleshooting
Who uses it
| Team / persona | How they use CPURAM |
|---|---|
| Finance and product-cost analysts | Vehicle cost analysis, BOM comparison, option-cost analysis, and recurring reporting |
| Purchasing and logistics stakeholders | Cross-functional cost investigation using supplier, logistics, and sourcing context |
| Engineering and propulsion-focused users | Propulsion-system cost analysis, part-level investigation, and configuration drill-down |
| Technical and power users | Direct-query access, utility-file usage, and deeper analytical exploration |
Core business scope
CPURAM organizes analysis across several major subject areas.
| Subject | What it captures |
|---|---|
| Vehicle level reports | Vehicle-level cost analysis and related configuration views |
| Vehicle part level reports | Part-level cost, attributes, and detailed vehicle part analysis |
| BOM reports | BOM explosion, cost comparison, and period-over-period BOM investigation |
| RPO reports | RPO penetration, decode, compare, and option-related analysis |
| VOIC / Super Six reports | Vehicle configuration-driven analytical views |
| Propulsion reports | Engine, transmission, RESS, drive unit, and propulsion-system cost analysis |
| CPURAM-F and mini-BOMs | Future-vehicle content and smaller BOM-oriented analysis paths |
Business measures and rules
The source page does not publish a formal measures table like the PCA page, but CPURAM clearly centers on these analytical themes.
| Measure / rule | Business meaning |
|---|---|
| Vehicle-level cost views | Compare vehicle costs across cost periods, configurations, and reporting perspectives |
| Part-level cost and attributes | Investigate detailed cost drivers and part characteristics |
| BOM comparison and explosion | Analyze structure and cost differences across BOMs and time periods |
| Propulsion-system detail | Review propulsion assembly, BOM, and summary cost information |
| RPO penetration and option-cost analysis | Understand option cost, penetration, and VIN comparison patterns |
| VOIC-based configuration analysis | Use the Vehicle of Interest Configuration construct to simplify and compare analytical scope |
Reporting and analytics interfaces
CPURAM is exposed through a mix of reports, support content, and query utilities.
| Interface | View of the data | Primary use cases |
|---|---|---|
| CPURAM reports | Business-facing reporting across vehicle, part, BOM, RPO, VOIC, Super Six, and propulsion topics | Standard analysis and recurring cost investigations |
| Direct query utilities | Query-oriented access to key reports and utility files | Faster or deeper analytical access for approved users |
| Training videos and decks | Guided walkthroughs by subject area | Onboarding, self-service learning, and report-specific how-to support |
| Data dictionaries and field primers | Definitions for cube and report fields | Field interpretation and analytical consistency |
| Use-case examples | Solved analysis examples using CPURAM and direct query | Reusable patterns for business problem solving |
Training and support
CPURAM includes a structured onboarding path for new and occasional users.
Users are directed to begin with the CPURAM Overview to learn the CPURAM language, content structure, source context, curation timing, and reporting platforms used.
The published training path includes:
- CPURAM Overview
- Vehicle-Level Cost
- Vehicle Part Cost
- BOM Comparisons
- Propulsion System Cost
- Additional Tools: RPO and Option Cost Analysis
- CPURAM-F
- SharePoint Reports
- Direct Queries
- Mini-BOMs
For support, users can post questions directly in the #help-cpuram Slack channel.
Security and access model
CPURAM access begins through myAccess.
Direct-query files require additional access and setup to run, so the access model differs between standard report consumers and users who need deeper query-based access.
| Access pattern | Intended audience | Typical capability |
|---|---|---|
| CPURAM report consumer | Business users and analysts | View and use approved reports, cubes, and training materials |
| CPURAM power user | Experienced analysts | Broader analytical use across report families and reference assets |
| Direct query access | Approved technical or advanced users | Use direct-query utility files and supporting setup for deeper investigation |
Getting access
- Request CPURAM access through myAccess
- For direct-query capability, review the setup and Databricks access instructions
- Validate any additional prerequisites for local setup or utility-file execution before using direct-query tools
Getting started path
- Watch the executive overview and introductory CPURAM overview materials to learn the terminology, structure, and reporting context
- Identify the best report family for the question: vehicle, part, BOM, RPO, VOIC / Super Six, or propulsion
- Use the quick tips and co-located how-to material for the selected report or cube
- Request access through myAccess if it is not already provisioned
- Review direct-query setup if the analysis requires utility files or deeper technical access
- Use the Slack support channel when a business or tool question is not resolved through the published training and reference content