Your Cost Data.
Any Customer's Format.
Minutes, Not Days.
CBD Controller reads cost data from whatever costing system you use today — SAP, Excel, your ERP, or ORAGO Cost Controlling — and exports finished cost breakdowns in the exact format each OEM customer requires. No manual reformatting. No re-entering numbers. No template gymnastics.
Works alongside your existing costing system. No replacement required.
CBD Controller is the right fit for:
- Any manufacturer that must produce customer-facing cost breakdowns for OEM customers — regardless of what costing system they use internally
- Suppliers using SAP, a proprietary ERP, or Excel-based costing who cannot or will not replace their costing process but need a reliable cost breakdown export layer
- Controllers spending hours or days per quote reformatting internal cost data into OEM-specific cost breakdown templates
- Companies supplying to multiple OEMs, each requiring a different cost breakdown format
- Industrial, medical, and electronics suppliers facing the same OEM cost transparency demands as automotive suppliers
Not designed for:
- Companies that need to calculate manufacturing costs from scratch — that is Cost Controlling's job. CBD Controller reads cost data that has already been calculated.
- Managing OEM relationships, tracking RFQ status, or negotiating quotes — CBD Controller produces the deliverable (the cost breakdown file), it does not manage the commercial process
- Internal financial reporting or ERP cost tracking
4–8 Hours of Manual Work.
Per Quote. Every Time.
Your cost data already exists — in SAP, in your ERP, in Excel, in whatever system your controllers use today. But when an OEM customer asks for a cost breakdown in their format, someone still has to copy those numbers into a specific spreadsheet — cell by cell. Wrong template version? Missed a field? Transposed a digit? Every manual transfer is a risk.
The result: hours of low-value work, late submissions, and the constant fear that a copy-paste error will cost you the project — or worse, lock you into a price you can't defend.
ORAGO Cost Breakdown Controller
Reads your existing cost data — from whatever system you use today — and produces the cost breakdowns your customers require, in their format, in minutes instead of days. No need to change your costing system. No re-entering data. Connect your existing process, simulate your presentation, and export.
Three Layers. Any Source.
Any Customer Format.
CBD Controller is built around three independent layers. This architecture is what makes it source-agnostic and format-agnostic — and what means connecting a new data source or supporting a new OEM format is a configuration task, not a development project.
Data Source Connectors
Reads cost data from your existing system — Excel exports, database tables, REST APIs, or direct manual entry. Each connector maps your source fields to the internal model through a visual field mapping UI. Adding a new data source is a consultant configuration exercise, not a development project.
Costing Records
All imported cost data — regardless of source — lands in Costing Records: a normalised model organised by material, processing, and tooling. Each record is uniquely identified by Customer × Part Number × Version. Controllers adjust presentation values through Sessions without changing the underlying source data.
Export Format Engine
Export Templates map Costing Records to each OEM's specific cost breakdown format — row by row, cell by cell. The same internal data can be exported in multiple customer formats simultaneously. Adding a new OEM format is configured through a row mapping UI — no code changes required.
Your Cost Breakdown Pipeline at a Glance.
The Dashboard is the default landing screen for every user. It surfaces what matters right now: sessions that need attention, source data changes that affect open work, recent exports, and the health of your data connector.
Session Pipeline
See how many sessions are in Draft, Simulating, In Review, and Exported this month — at a glance. Stat cards show your active sessions, items awaiting review, and last import status with colour-coded urgency.
Source Update Alerts
When underlying cost data changes after import, the Dashboard highlights every affected session with a plain-language change summary — so you know exactly which sessions need review before export.
Connector Health
Last import timestamp, records processed, new/updated/failed counts, and import frequency — all in a compact panel. Amber and red warnings surface issues before they affect your pipeline.
One Normalised Model.
Every Source, Same Structure.
Costing Records are the central data layer where all imported cost data lands — regardless of whether it came from Excel, a database, or manual entry. Each record is uniquely identified by a compound key: Customer × Part Number × Version.
Materials, Processing, Tooling
Each Costing Record contains tabbed panels for Materials, Processing, and Tooling — mirroring the standard cost structure. All child data is filterable, sortable, and fully searchable.
Change History
Every field change is logged: table, field name, old value, new value, timestamp, changed by, and import source. Filter by date or table type to trace exactly when and why a value changed.
Archive & Search
Archive completed records without deleting them. Unified search across customer, part number, version, and description. Archived records are excluded from default views but accessible via a filter toggle.
Connects to Whatever Costing System
You Already Use.
There is no requirement to replace or modify your existing costing process. CBD Controller adds a configurable read layer on top of it. The Connector maps your source fields to the internal model through a visual mapping UI with formula expressions and validation.
Excel / CSV File Import
Upload costing Excel files against a configured mapping. The connector maps cells, ranges, or columns to cost elements in the internal model. Validation checks structure and required fields before import — with per-record error detail.
Database Connectors
Direct read from database tables or views in your costing system. Supports SQL Server, PostgreSQL, Oracle, and ODBC-compatible databases. Field mapping and formula transformations apply to database sources identically.
Manual Entry
Create Costing Records directly in the system when no automated source is available. All child tables — Material, Processing, Tooling — can be added and edited inline. Compound key uniqueness validated automatically.
SAP Cost Data
Pre-configured connector for SAP costing transactions and tables (CK11N, CK13N, CKMLCP or equivalent OData services). Designed for the most common SAP cost estimate structures used in European manufacturing.
ORAGO Cost Controlling API
Ready-made REST API connector for ORAGO Cost Controlling customers. Pre-filled mapping template reads calculation data from the Cost Controlling Data API. One connector among many — implemented using the same framework as all others.
Machine Hourly Rates. Plants. Cost Centres.
Versioned and Immutable.
Core Data provides the rate foundation for every cost breakdown export. Machine hourly rates, plant structures, and cost centres are managed centrally with full version history. Once created, rate records are immutable — no silent edits, no overwritten history.
Internal & OEM-Specific MHR
Maintain internal machine hourly rates and OEM-specific overrides. Rate resolution is automatic: OEM-specific rates take precedence over internal rates for the matching machine and date. Both tiers are displayed in a combined view with tier indicators.
Immutable Rate History
Every rate version is permanently stored with effective dates, version label, and who created it. Superseded rates remain visible in the timeline. The current active rate is highlighted. No rate record is ever modified after creation — append-only by design.
Export Traceability
For any rate version, see which export artifacts reference it. The audit chain runs from exported file → session → MHR version — so every number in every cost breakdown can be traced back to the exact rate that produced it.
Every OEM Has Their Own Format.
CBD Controller Supports All of Them.
Pre-built templates for major OEM cost breakdown formats. No OEM template yet? Our implementation team configures new formats in 1–3 working days from format receipt to first successful export.
Row-Level Mapping
Each template row maps a specific cost element to the OEM's own label and cell reference. Source type (material, processing, tooling, calculated, static), formula expressions, conditional visibility, section grouping — all configurable per row without code changes.
OEM Management
Manage OEM customers centrally. Each OEM can have multiple export templates (different formats or versions). Templates are versioned independently — sessions retain the template version they were created with.
OEM Template Upload
Upload the OEM's actual Excel template file (.xlsx). CBD Controller writes values into the exact cells the OEM expects — preserving their formatting, formulas, and structure. Excel formulas recalculate automatically on open.
From Import to Export.
Every Step Tracked.
A Session is one Costing Record viewed through one Export Template. It is the working copy where controllers adjust presentation values, submit for review, and ultimately export the finished cost breakdown. Every session follows a defined lifecycle with snapshot locking on export.
Create Session
Select a Costing Record, choose an OEM and Export Template. The system calculates all line values using Core Data rates automatically.
Adjust Values
Rate overrides and flat deltas with mandatory reasons. Live-linked to source data — if the Costing Record is re-imported, affected values recalculate automatically.
Submit for Approval
Mark the session ready for review. Reviewers can approve or return for revision. The Adjustment Screen is read-only during review.
Approve & Export
Pre-export checklist validates completeness. On approval, the cost breakdown is exported and the session is permanently snapshot-locked. No further modifications possible.
See What the Customer Will See.
Before You Send It.
The Adjustment Screen is a three-panel workspace where controllers refine the commercial presentation of each cost breakdown. The left panel shows Costing Record metadata and session info. The centre grid displays every line in the OEM's format with calculated values, adjustments, and final presentation values. The right panel shows a live session summary with totals, margin, and completeness.
Column Layers
Source Value, Core Data Applied (rate tier and version), Calculated Value, Adjustment, and Presentation Value. Toggle columns on or off to focus on the data layer you need. State persists per user session.
Rate Overrides & Flat Deltas
Override the Core Data rate for rate-calculated rows, or apply a signed flat delta for direct-value rows. Every adjustment requires a mandatory reason field — no undocumented changes. Positive deltas show green; negative show amber.
Live-Link Diff Highlighting
When source data changes via re-import, affected rows show a blue left border and a “Source Updated” badge with previous vs. new values on hover. Review and dismiss diffs line by line or in bulk before export.
Session Summary Panel
- Calculated Value Total — sum of all system-calculated baseline values
- Net Adjustment — signed total of all overrides, colour-coded positive/negative
- Presentation Total — the final number the customer will see
- Approximate Margin % — live estimate from presentation values
- Completeness — progress bar showing how many editable rows have been reviewed
Grid Row Types
- Section Headers — full-width, dark background, grouping rows visually
- Data Rows — editable or read-only, using the OEM's own labels verbatim
- Total Rows — bold with top border, auto-calculated from child rows
- Conditional Rows — automatically hidden when presentation value is zero
Preview the Finished Cost Breakdown.
In the OEM's Own Excel Template.
Before you export, download a live preview of the cost breakdown in the customer's actual Excel template. Changes you make in the Adjustment Screen appear in the Excel file automatically — no re-downloading, no manual refresh.
How Live Preview Works
- Click “Preview” in the Adjustment Screen to download the OEM's Excel template populated with current presentation values
- A VBA module in the preview file polls the server every 3 seconds for changes
- When you adjust values in the web UI, the Excel file updates automatically — including recalculating any OEM formulas
- Preview tokens are time-limited (8 hours) and automatically revoked when the session is exported
- Toggle live updates on/off from a button in Excel. No preview template configured? A static populated .xlsx is generated instead
Why This Matters
OEM cost breakdown templates often contain their own Excel formulas, conditional formatting, and summary calculations. A web-only preview cannot replicate these. By downloading the actual Excel template with live data, controllers see exactly what the customer will see — including all OEM-side formula results.
The VBA module is signed with an ORAGO certificate. Users add it to Trusted Publishers once. No ActiveX controls are used.
Audit-Proof Exports.
Every Number Traceable.
When a session is approved, the export process creates an immutable artifact. The session is permanently snapshot-locked in the same database transaction — no silent changes after export. Every number in the exported cost breakdown can be traced back to its source.
Pre-Export Checklist
Before export, a modal verifies: all mandatory adjustment reasons provided, no unresolved live-link diffs, session status valid for export. Each item shows green (passed) or red (blocked with explanation). Export proceeds only when all items pass.
Excel Export
CBD Controller copies the OEM's .xlsx template and writes each presentation value into the exact cell defined by the template's row mapping. OEM formulas recalculate automatically on open. Naming convention: PartNumber_OEMTemplate_Session_Date.xlsx.
Full Audit Chain
Every export artifact stores: the MHR version IDs and rates used, the Costing Record compound key snapshot, the OEM template name and version, who exported, and when. Exported file → Session → MHR version → source data. Complete reproducibility.
Three Roles. Clear Boundaries.
Enforced at Every Layer.
Each user has exactly one role. Permissions are enforced at the service layer, not just the UI — so even API access respects the same boundaries.
Controller
Browse Costing Records, create and manage sessions, work in the Adjustment Screen, submit for review, approve and export cost breakdowns. The Controller is the primary user who transforms imported cost data into customer-ready cost breakdowns.
Implementation Consultant
Configure Connectors (field mapping, validation), manage Export Templates (row mapping, OEM template upload), maintain Core Data (plants, cost centres, machines, MHRs). Full CRUD on all configuration. Typically an ORAGO consultant during initial setup, then an internal power user.
Administrator
User and license management, role assignment, system configuration. Administrators see a system health panel on the Dashboard with active licensed users vs. total seats, connector status, failed imports, and non-revoked preview tokens.
REST API.
Automate the Entire Pipeline.
Every CBD Controller capability is accessible through a secure REST API with JWT authentication and OpenAPI documentation. Import costing records from external systems, trigger cost breakdown generation, monitor session status, and retrieve exported files — all programmatically.
- Import costing records from any source system via REST endpoints
- Trigger session creation and cost breakdown generation programmatically
- Retrieve session status, adjustment data, and exported files via API
- JWT token authentication — same role-based permissions as the UI
- OpenAPI specification for your integration team — no proprietary protocols
We Already Have a Process for This.
Here Is Why That Changes.
“We already have a costing system.”
CBD Controller does not replace your costing system. It reads from it. You keep your SAP, your Excel, your existing process. CBD Controller adds the export layer your customer requires — without touching how you calculate.
“We handle this in Excel.”
How many hours does your controller spend per cost breakdown? How many formatting errors reach the customer? Can you refresh instantly when the underlying calculation changes? Can you compare this submission with the last one? CBD Controller answers all four questions.
“We only have a few customers requiring Cost Breakdowns.”
Even 50 cost breakdowns per year at 4 hours each is 200 hours of controller time — more than a month of full-time work on manual formatting. Implementation typically takes 2–5 days for Excel-based sources.
Customised to your reality at implementation
Every CBD Controller deployment requires customisation — your data sources, cost element structures, and OEM export formats are unique to your business. Our implementation team maps your specific connectors, cost model structures, and customer templates through a proven, repeatable process — typically 2–5 working days per data source and 1–3 days per new OEM format.
Stop Filling Cost Breakdowns Manually
See CBD Controller in Action — Live Demo in 20 Minutes
Request Your Demo →