Home / Utility ERP and CIS / Oracle MDM
Oracle MDM staffing and consultants
Oracle Utilities Meter Data Management (MDM) stores and processes meter reads from AMI and legacy metering, applies validation, estimation and editing (VEE) rules, and produces the usage transactions that billing consumes. Mako places MDM functional analysts, VEE configuration specialists, integration developers and data analysts.
Metering talent for AMI rollouts, MDM implementations, exception backlog recovery and ongoing operations.
- Submittals within 48 hours
- 80% of submittals hired at a utility client
- AMI Integration Developer
Meter read
AMI head-end into Oracle MDM
- MDM Functional Consultant
Validate
VEE rules in Oracle MDM
- C2M Configuration Lead
Bill determinants
Usage to billing in C2M
- CC&B Rates Analyst
Bill
Rates and bill calculation in CC&B
- Collections Analyst
Pay and collect
Payments, credit and collections
What Oracle MDM is
The system between the meter and the bill, and the one blamed when either is wrong.
MDM is the utility's authoritative store of measurement data. It receives reads from head-end systems, validates and where necessary estimates them, and publishes usage transactions that Oracle CC&B turns into bills. In the converged product line, that boundary moves inside a single platform. See Oracle C2M and CCS, and CC&B vs C2M vs CCS for how the generations compare.
Because MDM sits on the Oracle Utilities Application Framework, extension and batch work draws on the same OUAF developer skill pool as the rest of the suite. Broader program context lives in our utility ERP and CIS practice.
The AMI data path
Reads flow from the meter to the head-end system, through Smart Grid Gateway adapters or equivalent integration, into MDM for validation, and then out as usage transactions to billing. Each hop has its own failure modes, and troubleshooting requires someone who understands the whole chain.
Interval versus scalar data
Legacy metering produces periodic scalar reads; AMI produces interval channels at typically 5-, 15-, 30- or 60-minute intervals depending on the meter and the program, plus registers and events. Interval data enables time-of-use and demand rates but increases stored volume by orders of magnitude.
Measurement cycles and completeness
MDM tracks what should have arrived against what did, so completeness monitoring is a daily operational function. Missing or late reads must be resolved or estimated before the billing window closes, which makes cycle timing a hard operational constraint.
VEE rules and exception handling
VEE configuration determines how much data self-corrects and how much lands in an analyst's queue. Tuning rules is a balance: loose rules push bad data into billing, tight rules generate exception volume no team can clear.
Usage subscriptions and transactions
Usage subscriptions define how measurement data is aggregated for a given service agreement, and usage transactions are the resulting billable quantities. This is the contract between metering and billing, and it is where most integration defects surface.
Smart Grid Gateway adapters
SGG provides adapters for common head-end systems, handling device provisioning, commands such as remote connect and disconnect, and inbound measurement and event processing. Adapter work is a distinct integration skill from core MDM configuration.
Volume and performance
Interval data at scale makes batch tuning, partitioning and archiving real engineering concerns rather than afterthoughts. Programs that size only for go-live volumes tend to hit performance problems as history accumulates.
Roles we place
Functional, technical and operational metering roles across all 50 states.
- MDM Functional Analyst
- VEE Configuration Specialist
- SGG / Head-End Integration Developer
- Meter Data Analyst
- OUAF Developer
- Conversion Analyst
- Test Analyst
- AMI Program Manager
Where teams need help
The metering gaps that most often reach billing before anyone notices.
VEE tuning and exception backlog
Exception volume after an AMI cutover routinely exceeds forecasts. Teams need both a configuration specialist to tune rules and analyst capacity to clear the queue before billing is affected.
Head-end integration troubleshooting
Defects between the head-end, SGG and MDM require someone comfortable reading both integration payloads and MDM processing. This blended skill is scarcer than either side alone.
Measurement history conversion
Migrating historical reads and device configuration into MDM, with reconciliation that proves the load, is a full workstream, especially when consolidating into a converged platform.
Performance at interval scale
Batch and database tuning for interval volumes is specialized work that most implementation teams do not carry internally.
Oracle MDM and AMI staffing questions
What does Oracle MDM do?
Oracle Utilities Meter Data Management stores measurement data from AMI and legacy metering, validates and corrects it through configurable rules, and converts it into the usage transactions that billing consumes. It is also the system of record for device configuration, measurement history and metering exceptions.
What are VEE rules?
VEE stands for validation, estimation and editing. Validation rules detect problems such as missing intervals, spikes, negative consumption or readings outside tolerance. Estimation rules fill gaps using historical or profile-based logic, and editing rules apply corrections. Anything the rules cannot resolve becomes an exception a meter data analyst works before billing runs.
Do you staff AMI and smart meter rollouts?
Yes. We place meter data analysts, VEE configuration specialists, head-end and Smart Grid Gateway integration developers, conversion analysts and program managers for AMI deployments and meter replacement programs, on contract, contract-to-hire or full-time.
How does MDM connect to billing?
Billing does not read raw meter data. MDM aggregates validated measurements according to usage subscriptions and produces usage transactions that CC&B or C2M consume as bill determinants. When bills are wrong or delayed, the cause is frequently upstream in measurement data or exception backlog rather than in rate configuration.
A 30-minute hiring call with our team
We'll talk through the role, the experience your team needs and your timeline. You don't need a finished job description.