Oracle 1Z0-1196-26 Real Exam Questions [October 2026 Update]

The relationship between a customer, a service point, and a service agreement is the architectural foundation that every other concept in Oracle Customer to Meter builds on – and it is consistently the first category of questions where exam candidates reveal whether they have implemented C2M or merely used it. A service point is the physical delivery location where utility service is provided – the address, the meter socket, the connection to the distribution network. A service agreement is the contractual relationship between the utility and the customer for service at that point – defining the rate schedule, the billing cycle, and the start and stop dates of the service. A customer can have multiple service agreements at the same service point (for example, separate agreements for electricity and gas at the same address), and a service agreement links the customer’s account to a specific rate – the rate is not configured on the customer record, and it is not configured on the service point. Understanding the data model at this level of specificity is what the exam tests, not whether candidates know that billing happens monthly.

The Head End System (HES) integration is where C2M’s Meter Data Management function connects to the physical world – and it is the most technically precise topic in the exam. The HES is the software system that communicates with smart meters in the field: sending commands (read the meter now, enable demand response, disconnect service remotely), and receiving readings (interval data uploads, scalar reads, meter event notifications). In C2M’s architecture, the HES is an external system – C2M does not communicate with meters directly. C2M communicates with the HES through a configured Head End System record and its associated processing methods, which define how C2M sends commands to and receives data from a specific HES vendor’s system. The exam tests Head End System configuration – which options control how the SGG (Smart Grid Gateway) adapter communicates with each specific HES – as implementation setup, not vendor-specific technical knowledge.

Duplicate person prevention is a precisely-tested configuration point that looks trivial but is specifically called out in exam question sets. Oracle Customer to Meter includes configurable rules that check incoming person records for potential duplicates before allowing them to be saved – comparing name, address, phone number, and identification numbers against existing records. Where this duplicate check is configured – in the installation options, not on the person record template – is the specific knowledge the exam tests. The exam presents scenarios where a utility wants to prevent duplicate person records across all entry channels (web portal, call centre, data migration) and asks which system configuration achieves this, with the incorrect options placing the configuration in the wrong location.

Exam Snapshot

What Oracle Customer to Meter and Customer Cloud Service Does

Oracle Utilities Customer to Meter (C2M) is a unified utility platform that combines Customer Information System (CIS) and Meter Data Management (MDM) functionality in a single application – managing the full customer lifecycle from account creation through billing, payments, and service termination, alongside meter data collection, validation, and usage calculation.

Oracle Utilities Customer Cloud Service (CCS) is the cloud-hosted deployment of the same platform – C2M functionality delivered as a managed SaaS service on Oracle Cloud Infrastructure, including Oracle Utilities Rate Cloud Service (for rate configuration) and Oracle Utilities Billing Cloud Service (for billing execution) as optional companion services.

Together, C2M and CCS serve electric, gas, and water utilities that need both customer management and smart meter data management in one integrated system.

Domain 1: Customer Information Management

Person records represent the individuals or organisations that are customers, contacts, or guarantors of a utility account. Person records carry name, address, identification numbers, contact preferences, and the relationships that link a person to accounts and service agreements.

Duplicate person prevention: The system-wide configuration that prevents duplicate person records from being added is defined in the C2M installation options – the administrative configuration that applies globally across all entry points. A duplicate check algorithm evaluates incoming person data against existing records before the save operation completes. The exam tests this as an installation options configuration, not a person record type configuration.

Account records represent the financial relationship between a person or organisation and the utility – the account is what receives bills, records payments, and carries the financial balance. One person can have multiple accounts; one account can have multiple service agreements.

Service agreements (SA) are the core contractual objects in C2M – each service agreement links a specific account to a specific service point under a specific rate, covering a defined service period. Every active service point has at least one active service agreement. When a customer moves in, a Start Service request creates new service agreements; when they move out, a Stop Service request ends them.

Service Agreement types (SA Types) define the characteristics of a service agreement – whether it is a billed SA (regular metered consumption billing), an unbilled SA (a contract service with no metered usage), a deposit SA, or a loan SA. SA Type configuration defines the billing and financial behaviour of every service agreement of that type.

Domain 2: Device Management and Device Installation

Devices in C2M are the physical meters and associated equipment installed at service points. A device record represents a single physical meter – carrying its manufacturer, model, serial number, and the measuring components (the channels of measurement) it provides.

Device configuration types define the template for a device’s measuring components – which data channels the meter supports (kWh total, kWh by TOU period, kW demand, kvarh reactive energy), the interval length for interval-recording meters, and the units of measure for each channel.

Device types classify meters by their physical characteristics and communication capabilities – the meter’s form factor, its communication technology (RF mesh, PLC, cellular, optical), and the head end system it reports to. Device types link devices to the specific SGG adapter configuration used to communicate with them.

Device installation links a device to a service point – recording when the meter was installed, which meter socket it occupies, and the initial meter reading at the time of installation. A device installation also captures the multiplier (the factor by which raw meter readings are multiplied to produce actual consumption quantities – used when meters measure in larger units than the billing unit).

Meter exchange: When a meter is replaced, a meter exchange creates a new device installation for the replacement meter and ends the installation record for the removed meter. The exchange records final readings for the removed meter and initial readings for the new meter. The exam tests meter exchange as the workflow for mid-service meter replacement – distinct from the Stop/Start service workflow that transfers a service agreement between customers.

Domain 3: Measurements and VEE Processing

C2M’s MDM functionality processes meter readings through VEE – the same Validation, Estimation, and Editing workflow described in the Utilities Meter Solution exam. In C2M, VEE processing converts Initial Measurement Data received from the Head End System or entered manually into Final Measurement Data used for usage calculation and billing.

Head End System configuration: A Head End System record in C2M defines the external AMI system that communicates with smart meters. The HES configuration includes: the processing methods that control how C2M sends commands to the HES (read meter, connect/disconnect service remotely), the adapter configuration that defines the technical interface (which SGG adapter handles communication with this specific HES vendor), and the data formats used for inbound reading uploads and outbound command messages.

IMD types define the data format and processing behaviour for each type of Initial Measurement Data – how scalar readings are structured, how interval data files are formatted, how meter event data is interpreted. IMD types determine which VEE rule set applies to each category of inbound measurement.

Usage calculation: When a billing request is initiated, C2M uses the final measurement data for the service point to calculate service quantities – the bill determinants that the rate engine uses to calculate charges. The usage calculation uses the measurement data within the billing period, applies TOU derivation rules if the rate requires TOU quantities, and produces the service quantities recorded on the bill segment.

Domain 4: Usage Subscriptions and Billing Determinants

Usage subscriptions in C2M define how meter data is linked to the billing process – specifying which measuring components provide data for billing, which usage calculation rules apply, and which service quantity identifiers are produced. The usage subscription is the bridge between the MDM layer (meter data) and the CIS layer (billing).

Service quantity identifiers (SQIs) are the named quantities that rate components reference in their calculation formulas – “KWHONSUPERPEAK”, “KWDEMAND”, “KVARH” are examples of SQIs. Each SQI maps to a specific billing determinant produced by the usage calculation. The exam tests SQIs as the linkage between MDM-calculated quantities and CIS rate component references.

The prerequisite for billing: Before a customer’s usage can be calculated for billing, a usage subscription must exist – linking the service agreement to the measuring component and defining the calculation rules. The exam tests this prerequisite ordering as a scenario question: given a described billing failure, identify that the missing or misconfigured usage subscription is the cause.

Domain 5: Rate Configuration

Rates in Oracle C2M define how charges are calculated from usage quantities. A rate contains rate components – each component calculates one line item on the customer bill. Rate components can be: consumption charges (price per kWh consumed), demand charges (price per kW of peak demand), minimum charges (a floor charge regardless of consumption), fixed charges (a flat fee per billing period), or tiered charges (different unit prices for different consumption bands).

Rate schedules and effective dates: Rates are managed with effective dates – a new version of a rate schedule takes effect on a defined date, allowing rate changes to be configured in advance without immediately affecting current bills. Historical bills use the rate version that was effective during the billing period, preserving historical accuracy.

Configuring rates and bill segment calculation lines: Bill segment calculation lines are the individual line items produced when a rate calculates charges – one line per rate component. The configuration of each rate component determines which SQI it sources from, how the price is applied, and what description appears on the customer’s printed bill.

Domain 6: Billing, Payments, and Adjustments

Billing: The billing process creates bill segments – the individual charge calculations for one service agreement in one billing period. A complete bill aggregates all bill segments for all service agreements on the account into one invoice document. The exam tests the distinction between a bill segment (SA-level calculation) and a bill (account-level invoice).

Payments: Payments are applied to an account and distributed across its service agreement balances. Payment algorithms control how a payment is distributed when an account has multiple service agreements with outstanding balances – whether the oldest balance is paid first, the highest balance first, or the customer designates which SA receives the payment.

Adjustments: The adjustment transaction transfers a monetary amount between two service agreements or between a service agreement and a financial account. Adjustments are the mechanism for correcting billing errors, applying credits, or transferring balances between accounts without reversing the original bill segment.

Credit and collections: C2M includes configurable credit and collections workflows – overdue debt detection, severance notices, payment arrangements, and service disconnection. The exam tests credit and collections as a configured business process: the rules that determine when accounts become overdue, how severance notices are generated, and when automatic service disconnection is triggered.

Domain 7: Service Orders

Service orders in C2M are work orders dispatched to field crews – starting service (installing a meter), stopping service (removing a meter), investigating a reported issue, or performing a meter test. Service orders are generated from service request transactions entered by customer service agents and trigger field work dispatch.

Service order workflow design: C2M’s service order framework is highly configurable – the business objects and algorithms that control the service order lifecycle (from request creation, through dispatch, to field completion and confirmation) are implementation-configured. The exam tests service order configuration as an administrator task – defining which activities trigger service orders, which service order types are generated, and how completion notifications update the system.

5 Study Tips for Oracle 1Z0-1196-26

• Study the customer-account-service agreement-service point data model as an implementation data design, not as a user workflow – know what each object contains, what links what, and where rates are configured (on the SA type, not on the customer or service point).
• Study Head End System configuration – the HES record, its processing methods, and the SGG adapter configuration – as the technical setup that connects C2M to the physical smart meter network.
• Study the duplicate person prevention configuration location (installation options) as a specifically-tested scenario: the exam asks which configuration prevents duplicates across all entry channels.
• Study the usage subscription as the prerequisite for billing – know that a missing or misconfigured usage subscription is the root cause in exam scenarios describing billing calculation failures.
• Practice with Cert Empire’s 1Z0-1196-26 exam questions covering all seven domain areas at service agreement data model, HES configuration, VEE integration, and billing determinant prerequisite depth.

Best Study Resources

• Cert Empire 1Z0-1196-26 exam questions PDF and practice simulator (October 2026 edition).
• Oracle official 1Z0-1196-26 exam page (education.oracle.com – search “1Z0-1196-26”).
• Oracle Utilities Customer to Meter documentation (docs.oracle.com/en/industries/energy-water/advanced-meter/).
• Oracle Utilities Customer Cloud Service documentation (docs.oracle.com/en/industries/energy-water/customer-cloud-service/).
• Oracle University: Implementing Oracle Utilities Customer to Meter course.

Why Candidates Choose Cert Empire for Oracle 1Z0-1196-26 Preparation

Free Practice Tests

Sample our 1Z0-1196-26 questions before purchasing. Test your C2M data model knowledge, Head End System configuration understanding, and billing prerequisite reasoning before committing.

Regular Updates

Oracle updates Customer to Meter and Customer Cloud Service with each quarterly utilities platform release. Our 1Z0-1196-26 question bank is continuously reviewed against current Oracle documentation and exam objectives.

Free Exam Guides

Every purchase includes our free 1Z0-1196-26 exam guide covering all seven domain areas, the C2M data model reference diagram, the usage subscription prerequisite checklist, and a structured study plan.

PDF Exam Questions – Study Anywhere, Anytime

Download your 1Z0-1196-26 questions instantly after purchase. Study on any device or print the PDF. No login required after download, no expiry on the file.

24/7 Chat Support

Available at any hour for questions about your materials, your order, or specific Oracle C2M concepts – including SA type configuration, Head End System processing method setup, and rate component bill line calculation.

3 Months of Unlimited Access

Three full months of unlimited access to the 1Z0-1196-26 question bank and simulator. Revisit customer data model scenarios, VEE processing questions, and service order workflow topics as many times as needed.

Official Vendor Resources – Learn from the Source

Every solution in our 1Z0-1196-26 question bank links directly to the relevant official Oracle documentation – the Customer to Meter Administrative User Guide or the specific Oracle Utilities documentation behind the answer.

Deep Knowledge – Every Answer, Every Option, Fully Explained

Every 1Z0-1196-26 question includes a complete explanation covering not just why the correct SA type configuration, usage subscription prerequisite, or duplicate prevention location is right, but precisely why each incorrect option fails – whether it places the duplicate person check on the person record type rather than in installation options, tries to configure the rate on the service point rather than the service agreement, or creates billing determinants without first establishing the usage subscription. Each explanation references the specific Oracle Utilities documentation behind the answer.

Interactive Practice Simulator – Think Like the Exam

Our simulator presents Oracle C2M implementation scenarios exactly as the real 1Z0-1196-26 exam does – describing a utility configuration requirement, a billing process failure, or a device management workflow and testing which data model object, configuration location, or prerequisite step correctly addresses it. Per-question feedback explains the full utility platform reasoning behind every correct and incorrect option.

Backed by a Full Money-Back Guarantee

If our 1Z0-1196-26 exam questions do not help you pass, you receive a full refund – no questions asked, no conditions.

FAQ’s

What is the Oracle 1Z0-1196-26 certification?

1Z0-1196-26 is the Oracle Utilities Customer to Meter and Customer Cloud Service 2026 Implementation Professional exam. It validates expertise in implementing Oracle’s utility CIS and MDM platform – covering customer information, device management, service points, measurements and VEE, usage subscriptions, billing, rates, service orders, payments, and credit and collections.

What is the difference between Oracle C2M and Oracle Customer Cloud Service?

Oracle Utilities Customer to Meter (C2M) is the application software; Oracle Utilities Customer Cloud Service (CCS) is the cloud-hosted (SaaS) deployment of C2M on OCI. CCS includes companion services – Oracle Utilities Rate Cloud Service for rate configuration and Oracle Utilities Billing Cloud Service for billing execution. The functional coverage is the same; the deployment model differs.

Where is the duplicate person prevention configuration in Oracle C2M?

Duplicate person prevention is configured in the C2M installation options – the system-wide administrative configuration that applies across all person entry channels (web portal, call centre, data migration). It is not configured on individual person record types or person templates.

What must exist before a customer’s usage can be calculated for billing?

A usage subscription must exist – linking the service agreement to the measuring component that provides meter data, specifying the usage calculation rules, and defining the service quantity identifiers produced for the billing process. Without the usage subscription, the system cannot identify which measurement data belongs to which billing process.

What is a Head End System in Oracle Customer to Meter?

A Head End System (HES) is the external AMI software system that communicates with smart meters in the field. In C2M, a Head End System record defines how C2M communicates with a specific HES vendor’s system – including the processing methods for sending commands to meters and the SGG adapter configuration for receiving interval data uploads.

What is the difference between a bill segment and a bill in Oracle C2M?

A bill segment is the charge calculation for one service agreement in one billing period – the result of applying a rate to usage quantities for one SA. A bill is the account-level invoice that aggregates all bill segments for all service agreements on the account into one customer-facing document.

What is the passing score for the 1Z0-1196-26 exam?

The passing score is 68%. The exam is multiple-choice format delivered through Pearson VUE either online-proctored or at a test centre. The cost is USD $245.

Related Certifications Worth Exploring

Oracle Utilities Customer to Meter implementors working across the Oracle Utilities suite will find the Oracle 1Z0-1196-25 (Oracle Utilities Customer to Meter and Customer Cloud Service 2025 Implementation Professional) exam questions page covers closely aligned C2M and Customer Cloud Service functionality – customer accounts, billing, meter data, service requests, field work, and meter-to-cash processes that reinforce the same core Oracle Utilities implementation expertise. For Oracle Utilities professionals expanding into the cloud infrastructure and operations supporting utility workloads, the Oracle 1Z0-1067-26 (OCI Cloud Operations Professional 2026) exam questions page covers OCI monitoring, automation, security, availability, troubleshooting, and infrastructure management skills relevant to maintaining reliable Oracle Utilities cloud environments.