1Z0-1090-24 — Oracle Utilities Work and Asset Cloud Exam Blueprint

How to Use This Exam Blueprint

Use this page as a practical readiness map for the Oracle Utilities Work and Asset Cloud 2024 Implementation Professional (1Z0-1090-24) exam. It is organized around implementation skills a candidate should be able to apply: interpreting requirements, choosing the right configuration approach, understanding work and asset lifecycle behavior, and recognizing where data, security, integrations, and operational processes fit.

Because exact exam weights are not provided here, treat the sections below as readiness areas, not as official percentages. For final review, focus on whether you can explain the purpose of each topic, configure or validate it in a realistic implementation scenario, and troubleshoot common mistakes.

Exam identity

Readiness scale

Use this scale as you work through the checklist.

Topic-area readiness table

Core implementation concepts to know

Product process map

A typical implementation scenario connects several process areas. Be able to explain the dependencies, not just define each record type.

    flowchart LR
	    A[Foundation setup] --> B[Assets and locations]
	    A --> C[Resources, crews, calendars]
	    A --> D[Inventory and procurement setup]
	    B --> E[Maintenance strategy]
	    E --> F[Work generation or request]
	    F --> G[Planning and estimating]
	    G --> H[Scheduling and assignment]
	    H --> I[Execution and completion]
	    I --> J[Costs, history, reporting]
	    D --> G
	    C --> H

Can you explain these relationships?

• Why assets, locations, crews, calendars, inventory, and accounting structures are usually configured before transactional work is tested.
• How work records capture planning, execution, completion, and costing information.
• How asset hierarchy affects maintenance history and reporting.
• How materials move from planning to reservation, issue, return, and actual cost.
• How labor or crew setup affects scheduling and completion.
• How status transitions control what users can do at each point in a process.
• How implementation choices affect reporting quality after go-live.

Foundation configuration checklist

Foundation setup is a common weak area because errors appear later as work, scheduling, inventory, or cost problems.

Foundation configuration prompts

Ask yourself:

• If a user cannot create a work order, is the likely cause security, missing required setup, invalid status, or incorrect organizational context?
• If a crew cannot be assigned, could the issue be calendar, skill, availability, crew definition, or work status?
• If costs are not appearing correctly, could foundational accounting or cost center setup be incomplete?
• If reporting is inconsistent, are classifications and codes being used consistently?

Asset lifecycle checklist

Can you do this?

• Choose whether a scenario should create a new asset, update an existing asset, or relate work to a location only.
• Explain the difference between an asset hierarchy issue and a location setup issue.
• Identify which asset attributes should be standardized for reporting.
• Determine whether maintenance should be attached to an asset, asset class, location, or route-type grouping.
• Explain how asset replacement affects historical reporting and future maintenance.
• Recognize data migration risks for asset identifiers, serial numbers, locations, hierarchy, and status.

Work management checklist

Work management scenarios usually test process judgment: what record to use, what status should come next, and what data is needed for execution.

Work lifecycle decision path

    flowchart TD
	    A[Need identified] --> B{Is it only a request?}
	    B -->|Yes| C[Create or review work request]
	    B -->|No| D[Create planned work record]
	    C --> E{Approved for work?}
	    E -->|No| F[Reject, defer, or request more info]
	    E -->|Yes| D
	    D --> G{Planning complete?}
	    G -->|No| H[Add labor, material, asset, location, instructions]
	    G -->|Yes| I{Resources and materials available?}
	    I -->|No| J[Reserve, procure, or reschedule]
	    I -->|Yes| K[Schedule and assign]
	    K --> L[Execute]
	    L --> M[Complete and close]
	    M --> N[Update costs, asset history, reports]

Work management “can you do this?” checklist

• Explain the difference between request intake, work planning, work execution, and work closeout.
• Identify when work should be emergency, corrective, planned, preventive, inspection, or follow-up work.
• Determine what information is required before a work order can be scheduled.
• Explain why a work order may be visible to one user but not another.
• Recognize why a work record may be blocked from approval, assignment, or closeout.
• Determine whether actual labor, materials, equipment, or failure information must be entered before completion.
• Explain how completed work updates asset history and reporting.
• Identify when follow-up work should be created instead of reopening completed work.

Preventive maintenance and inspection checklist

Maintenance scenario cues

Planning, estimating, and standard work checklist

Plain-language cost readiness:

• Estimated cost should include the planned cost components used by the implementation.
• Actual cost should be driven by executed transactions such as labor, material issue, procurement receipt, or service charges.
• Cost rollups are only useful when work, asset, project, and accounting relationships are configured consistently.

Scheduling, crews, and dispatch checklist

Scheduling decision prompts

• Is the work approved and planned?
• Are required materials available or reserved?
• Are labor skills and crew capacity available?
• Is the asset or location accessible?
• Is there a dependency on another work activity?
• Is the schedule date compatible with calendars and shifts?
• Are there priority conflicts that require dispatch judgment?

Inventory, materials, and procurement checklist

Inventory and procurement scenario cues

Financial and costing checklist

Costing readiness prompts

• Can you explain why an estimate and actual cost do not match?
• Can you identify which transaction created an actual cost?
• Can you determine whether a cost belongs to a work order, asset, project, or accounting distribution?
• Can you identify missing setup when cost posting or reporting fails?
• Can you explain how material return or cancellation affects actual cost?
• Can you separate operational completion from financial completion or closeout where the process requires it?

Security, roles, and access checklist

Access troubleshooting pattern

When a user says, “I cannot do this,” check in this order:

1. Is the record in a status that allows the action?
2. Does the user have the correct role or responsibility?
3. Is the record in the user’s organization, operating area, or data scope?
4. Are required fields or prerequisite records missing?
5. Is an approval, lock, integration status, or validation error blocking action?
6. Is the user looking at the right portal, page, queue, or task list?

Data migration and conversion checklist

Data migration is not just loading records. You need to validate that converted data works inside business processes.

Data validation checks

• Can users search and find converted assets using expected identifiers?
• Do asset hierarchies and locations support realistic work creation?
• Can maintenance schedules generate or support work only for eligible assets?
• Do inventory balances reconcile to the legacy source?
• Can open work move through its next lifecycle step?
• Do converted records pass security, ownership, and reporting checks?
• Are conversion rejects and exceptions tracked to resolution?
• Is there a cutover plan for delta data created between extract and go-live?

Integration checklist

Common integration scenarios

Reporting, analytics, and operational review checklist

Reporting readiness prompts

• Can you identify which fields drive each report?
• Can you explain why poor classification leads to poor analytics?
• Can you distinguish operational dashboards from historical trend reports?
• Can you trace a report discrepancy back to transaction data, setup, security, or integration timing?
• Can you define test cases that prove reporting works before go-live?

Configuration and implementation artifact checklist

For the exam, be able to connect configuration choices to implementation artifacts.

Scenario and decision-point review

Use these prompts to practice exam-style judgment.

Common weak areas and traps

High-value “Can you do this?” checklist

Before exam day, you should be able to do the following without relying on notes.

Process understanding

• Explain the end-to-end work lifecycle from request through closeout.
• Explain how assets, locations, maintenance schedules, and work records relate.
• Explain how planning differs from scheduling and dispatch.
• Explain how inventory and procurement support work execution.
• Explain how actual cost is created and reported.
• Explain how completed work contributes to asset history.

Configuration judgment

• Identify required foundation setup for a new implementation area.
• Choose appropriate work types, asset classes, priorities, and statuses for a scenario.
• Determine whether a scenario needs a new configuration value, a process change, or data correction.
• Identify which roles need access to each process step.
• Recognize when approval rules or lifecycle controls are blocking progress.
• Sequence configuration, migration, integration, and testing tasks logically.

Troubleshooting

• Diagnose why a work record cannot move to the next status.
• Diagnose why an asset is not eligible for maintenance generation.
• Diagnose why planned material did not become actual cost.
• Diagnose why a user cannot see or update a record.
• Diagnose why an integration message failed.
• Diagnose why a report total does not match transaction detail.

Implementation readiness

• Build a simple test scenario that covers asset, work, material, labor, cost, and reporting.
• Identify data migration fields that must be cleansed before loading.
• Define integration reconciliation checks.
• Explain cutover risks for open work, inventory balances, and maintenance schedules.
• Identify post-go-live support categories: access, configuration, data, process, integration, reporting.

Final-week review checklist

Seven to five days before

• Review the current Oracle exam page and any exam-specific preparation guidance available to you.
• Create a one-page map of the asset-to-work-to-cost lifecycle.
• Review foundation setup dependencies: organizations, locations, roles, calendars, crews, inventory, accounting.
• Practice at least one scenario each for asset lifecycle, work management, maintenance, inventory, costing, and integration.
• Mark all Yellow and Red topics from this checklist.

Four to three days before

• Rework weak scenarios without looking at notes.
• Practice distinguishing similar terms: request/work order/activity, planned/actual, issue/reservation, transfer/purchase, asset/location.
• Review status and approval logic across work, procurement, and closeout scenarios.
• Review common integration failure causes and reconciliation methods.
• Review data migration validation checks.

Two days before

• Focus on decision questions, not broad reading.
• Explain each major process aloud in implementation sequence.
• Revisit common traps and write your own example for each.
• Confirm that you can identify the next best action in a scenario.
• Avoid learning large new topics unless they are core gaps.

One day before

• Review your condensed notes and this checklist.
• Practice short scenario prompts until you can justify each answer.
• Rest your memory on process flow, dependencies, and troubleshooting logic.
• Prepare exam logistics so your study time is not lost to administrative issues.

Practical next step

Pick one end-to-end scenario and work it fully: create the asset context, initiate work, plan labor and materials, schedule the work, record completion, account for cost, update asset history, and verify reporting. If you cannot explain any step, return to that topic area and practice targeted questions until the decision points feel routine.