Oracle Fusion SCM

Oracle Fusion SCM Managed Service

Oracle Fusion SCM: End-to-End Supply Chain Visibility in the Cloud

TL;DR

Oracle Supply Chain Management Cloud brings procurement, inventory, order management, and logistics into one connected platform so teams can plan, execute, and respond with better visibility and control.

  • ✓What Oracle Supply Chain Management Cloud covers across the end-to-end supply chain
  • ✓How a unified data model improves visibility from purchase order to delivery
  • ✓Where organisations typically see friction (handoffs, master data, integrations) and how to address it
  • ✓How AppsolveGroup supports Oracle Fusion SCM delivery in the UK with implementation plus ongoing managed service

Oracle Fusion SCM: End-to-End Supply Chain Visibility in the Cloud

Oracle Supply Chain Management Cloud (Oracle Fusion SCM) runs procurement, inventory, order management, and logistics on a single platform. No disconnected tools. No spreadsheets bridging gaps between teams.

When those functions share the same data and workflows, demand and supply signals get clearer. Manual handoffs drop. Execution from sourcing through to fulfilment becomes something you can actually rely on.

The simplest way to think about it: an end-to-end operating model in the cloud.

  • ✓Procurement: manage suppliers, purchasing, approvals, and spend controls with consistent policies and a full audit trail.
  • ✓Inventory: track on-hand stock, inbound movements, reservations, and replenishment across every location in one view.
  • ✓Order management: orchestrate promising, pricing, holds, allocations, and exception handling across all your channels.
  • ✓Logistics and fulfilment: manage shipping execution, carrier processes, and delivery milestones tied directly to orders and inventory.

Because everything sits on the same platform, teams are working from the same picture at the same time. An inventory constraint can flow through to order promising, which can trigger a procurement action or a fulfilment alternative—without anyone having to reconcile three systems first.

That's what end-to-end visibility actually means in practice: fewer surprises, faster decisions, and a process you can measure and improve.

The tricky part is that visibility doesn't come from the screens. It comes from the foundations.

In delivery, the biggest barriers we see consistently are master data quality, process design across teams, and integration points. ERP financials, WMS and TMS systems, eCommerce platforms, 3PLs, EDI. Most organisations underestimate how much these friction points matter until they're already live.

A solid implementation tackles them early. Who owns item, supplier, customer, and location data. How real-world exceptions—substitutions, backorders, partial shipments, returns—are actually handled. And how integrations are designed around operational timing, not just overnight batch reporting.

So what does good look like after go-live?

AppsolveGroup is a UK Oracle partner supporting organisations across both Oracle Fusion SCM implementation and oracle fusion scm managed service. That combination matters because supply chains don't stand still. New fulfilment routes, supplier changes, shifting lead times, evolving customer expectations—these require continuous configuration, monitoring, and improvement, not a one-time deployment.

A managed service should handle the day-to-day: incidents, access, integrations, scheduled jobs. But it should also deliver structured progress—process enhancements, release management, reporting refinements, and governance that keeps pace with the business. We see this constantly during technical audits: organisations with strong implementations that stall because there's no structured model for what comes next.

If you're standardising supply chain processes or replacing fragmented legacy tools, Oracle Supply Chain Management Cloud gives you the platform to connect planning and execution. A managed service keeps it stable, secure, and aligned with how your business actually operates. For a broader view of the platform and how the applications fit together, see our Oracle Fusion guide.

Core Oracle Fusion SCM Modules and What They Deliver

Oracle SCM Cloud is best understood as a set of tightly connected applications covering planning, buying, making, moving, and fulfilling. No separate systems to reconcile. No duplicate data models to maintain.

When these modules run on a single platform and security model, you get consistent definitions for items, suppliers, customers, organizations, and costs across the board. That consistency matters—a lot—when you're trying to trust your reports or trace a problem back to its source.

Oracle SCM Cloud
Oracle SCM Cloud is Oracle's integrated suite of cloud applications for running core supply chain processes—procurement, inventory, order orchestration, manufacturing, and logistics—on a shared data model.

Procurement Cloud

Procurement Cloud handles supplier onboarding, sourcing, purchasing, and invoice controls—with approvals and policy enforcement built in, not bolted on.

For commercial and marketing teams, the practical win is fewer delays when buying for campaigns, packaging, events, or agencies. Requisition-to-PO processes become standardised and auditable. Spend gets easier to forecast, and far easier to explain when someone asks.

Inventory Management Cloud

Accurate on-hand and available-to-promise data isn't just an ops concern. It directly shapes customer experience.

Inventory Management Cloud governs item structures, stocking policies, transactions, and valuation across sites. Oversells drop. Avoidable backorders drop. Delivery messaging becomes something you can actually stand behind.

Order Management Cloud

Without proper orchestration, exceptions get handled manually and inconsistently. That quietly erodes lead-time performance and customer trust over time.

Order Management Cloud manages order capture, pricing, orchestration, and exception handling across fulfillment paths—ship, pickup, drop-ship, split shipments. It puts structure around what most teams are currently handling ad hoc.

Manufacturing Cloud

Manufacturing Cloud supports work definitions, production execution, and quality processes with traceability. We see this come up constantly during audits of product-launch operations—promotions go live before anyone has confirmed real production capacity. Manufacturing visibility closes that gap and gives product marketing teams something reliable to plan against.

Logistics Cloud

Logistics Cloud covers shipping execution, transportation planning, freight rating, and delivery tracking. Better logistics control improves the delivery promise you can actually market. It also gives customer service teams real status data instead of educated guesses.

Principal Oracle Fusion SCM Cloud modules

Procurement Cloud

Controls sourcing-to-purchasing with approvals, supplier management, and compliant buying to reduce cycle times and improve spend visibility.

Inventory Management Cloud

Keeps item, stock, and transaction accuracy across locations, supporting dependable availability and cleaner costing.

Order Management Cloud

Orchestrates orders across fulfillment paths with exception handling, improving on-time performance and reducing manual intervention.

Manufacturing Cloud

Supports production execution and traceability so supply can match demand plans and product launch commitments.

How the modules connect (and why it matters)

The real value isn't any single module. It's the shared data model underneath all of them.

A supplier record created in procurement flows consistently downstream. Item and organisation definitions used for inventory also drive order promising and manufacturing consumption. Logistics events update order status without custom sync jobs running in the background.

That shared foundation cuts handoffs, makes root-cause analysis faster, and turns cross-functional reporting from a quarterly project into something you can actually do on demand.

A common mistake we see is organisations treating these modules as independent tools—then wondering why reconciliation is so painful.

For organisations running an oracle supply chain management cloud program, this integration is also what makes an oracle fusion scm managed service effective. Managed services teams can monitor end-to-end process health—not just single-module tickets—prioritise fixes based on actual business impact, and hold configuration discipline as requirements shift over time.

One model, fewer gaps

The biggest operational gains come from shared master data and connected workflows across modules, which reduces reconciliation work and makes performance reporting consistent from purchasing through fulfillment.

Procurement and Sourcing Automation with Oracle Fusion SCM

Procurement is where cost control either holds or quietly falls apart. In practice, it erodes through workarounds—urgent free-text requests, off-contract purchases, suppliers missing documentation that nobody checked. Oracle supply chain management cloud addresses this through Oracle Procurement Cloud, and it's a frequent focus in an oracle fusion scm managed service precisely because the value isn't locked in at go-live. It depends on how well catalogues, supplier records, and policy rules are maintained over time.

Self-service procurement that people will actually use

The core problem with most procurement systems is that the compliant route is slower than just emailing a supplier directly.

Oracle Procurement Cloud is designed to fix that. Guided buying and role-based controls make the preferred route the easiest one—which is the only way compliance actually sticks.

  • Searchable catalogues and negotiated items cut down free-text requests and off-contract buying.
  • Approvals can be driven by category, amount, cost centre, project, or supplier status—so the right people review the right things, not everything.
  • Punchout and supplier-hosted catalogues keep item content current without your team maintaining it manually.
  • Receiving and matching workflows enforce "no PO, no pay" where needed, without turning routine purchases into a finance exercise.

Fewer exceptions, cleaner requisitions, better invoice match rates downstream. Less rework for everyone.

Supplier qualification management for lower risk and better performance

This is where procurement meets risk management. And it's where we see a lot of gaps during audits.

Oracle Procurement Cloud supports structured qualification: capturing requirements, evidence, approvals, and expiry dates in one place, with controls tied directly to buying activity. You can segment suppliers by risk level and apply different onboarding checks accordingly. Certifications, insurances, modern slavery questionnaires, cyber attestations—all tracked with expiry dates and re-qualification triggers based on time, category, or performance issues.

Critically, qualification status can be tied directly to buying controls. Block POs to suppliers missing required documentation. Automatically.

Policy enforced by the system is policy that actually holds.

Sourcing optimisation to improve outcomes—not just run events

Issuing an RFQ is the easy part. Evaluating responses consistently—across price, lead time, service levels, sustainability criteria, and compliance—without it becoming a spreadsheet exercise buried in email threads. That's the harder part.

Oracle's sourcing tools support structured events with weighted scoring, bid analysis (including alternates and partial awards), and award recommendations aligned to governance. Stakeholders can review offers and provide input directly in the system. No email chains, no version confusion.

When this is configured well, sourcing becomes repeatable. Teams can run events consistently across categories—not just for high-value, high-visibility procurement where someone senior is watching.

Supplier portal capabilities that reduce admin for everyone

A supplier portal removes friction on both sides—when it's implemented with clear process rules behind it.

Suppliers can maintain their own profile information, acknowledge POs, provide shipment updates, submit invoices where enabled, and respond to sourcing events. Communication becomes structured and auditable. That's the goal.

The tricky part is making this stick operationally. Define exactly what suppliers are expected to do in the portal—and what your internal team will stop doing manually as a result. Without that clarity, portals often become a secondary channel rather than the primary one. We see this constantly during technical audits.

Reducing maverick spend with catalogues

A UK manufacturer had frequent off-contract purchases for MRO items because engineers raised urgent free-text requests and buyers couldn't easily enforce preferred suppliers. After implementing Oracle Procurement Cloud self-service buying with supplier catalogues, they configured category-based approval rules and guided buying to steer users to pre-negotiated items. Engineers could find compliant parts quickly, requisitions required fewer clarifications, and buyers spent less time converting ad-hoc requests into valid orders.

What to manage in an oracle fusion scm managed service

Procurement value drifts without active maintenance. Catalogues go stale. Supplier qualifications lapse. Approval rules stop reflecting how the organisation actually works.

Most teams underestimate how much ongoing governance is needed here.

In a managed service, the areas that consistently need attention are:

  • Catalogue content governance—item attributes, pricing updates, discontinued items, substitutes.
  • Supplier lifecycle administration—qualification renewals, expiry alerts, segmentation changes.
  • Approval rule tuning as the organisation changes, to reduce bottlenecks without opening gaps.
  • Sourcing templates and scoring models to keep events consistent across teams and categories.
  • Exception monitoring—blocked invoices, 3-way match failures, supplier non-compliance—as the input to continuous improvement.

It's not glamorous work. But it's what keeps the system delivering rather than slowly reverting to workarounds.

Procurement setup decisions

  • ✓Define buying channels: catalogue, punchout, non-catalogue, and when each is allowed
  • ✓Set approval design: thresholds, category rules, delegation, and exception paths
  • ✓Agree catalogue governance: ownership, refresh cadence, and content standards
  • ✓Design supplier onboarding and qualification steps, including required evidence and expiry handling
  • ✓Decide receiving and matching policy: when to require receipt, 2-way vs 3-way match, and tolerances
  • ✓Standardise sourcing templates: event types, scoring model, and award approval process
  • ✓Configure supplier portal scope: which transactions suppliers can perform and internal SLAs for responses
  • ✓Establish controls for restricted suppliers/items and what triggers blocks or warnings
In procurement projects, the biggest gains come from making compliant buying the fastest option—catalogues, sensible approvals, and clear receiving rules. We also see supplier qualification deliver quick risk reduction when expiry management and buying controls are tied together, so policy is enforced automatically rather than by reminders.

Inventory Management and Warehouse Optimisation on Oracle Fusion SCM

Oracle Inventory Management Cloud is the foundation for accurate stock control across sites, warehouses, and business units. It supports multi-organisation inventory—meaning you can model real operating structures: legal entity, business unit, inventory organisation, subinventory, locator. Without that flexibility, teams rely on workarounds that quietly create reporting gaps over time.

Design org structures first

Get the inventory organisation, subinventory, and locator model right before you migrate data. If the structure changes after go-live, you often end up remapping items, rebalancing stock, and rewriting integrations.

For traceability and compliance, Fusion SCM provides lot and serial tracking end to end. Lot control handles expiry, grade, and country-of-origin requirements. Serial control covers warranty, service, and regulated products.

The tricky part is control-level design.

You need to define controls at the right level—item, organisation, or subinventory/locator—and align them with your actual inbound and outbound flows. If receiving, put-away, picking, and shipping aren't set up consistently, users find shortcuts. When that happens, data quality erodes fast. Usually quietly.

For warehouse accuracy, Fusion supports cycle counting with flexible scheduling, tolerances, and approvals. You can segment count classes by velocity or value, set thresholds for automatic acceptance versus recount, and keep a full adjustment audit trail.

In practice, three things drive the most impact:

  • Aligning count frequency to item criticality, not just calendar convenience
  • Standardising how exceptions are handled—damage, short picks, unknown stock
  • Enforcing locator discipline so counts reflect where inventory actually sits, not where it's supposed to sit

Min-max planning handles stockout and excess prevention through straightforward replenishment rules. It works well for stable demand and indirect materials. We see this used widely across implementations. But the detail that gets missed most often is governance.

Min and max values need an owner, a review cadence, and a connection to actual lead times, order multiples, and service-level targets. Without that, the system replenishes accurately—straight towards the wrong numbers.

MistakeBox: common inventory data migration mistakes (EBS → Fusion)

Inventory data migrations from Oracle EBS to Fusion SCM fail most often due to avoidable design and data issues. For broader migration context, see /oracle-ebs/fusion-migration/.

We see the same pitfalls come up repeatedly across projects:

Common inventory data migration mistakes

Copying EBS organisations 1:1 without rethinking inventory org, subinventory, and locator strategy for Fusion. Inconsistent UOM and item definitions, which causes transaction failures or incorrect on-hand valuations. Lot and serial history gaps—missing expiry dates, origination attributes, or uniqueness rules—that break traceability from day one. On-hand loaded without controls: no locator assignments, missing lot numbers, wrong status flags, all of which create downstream picking and ATP issues. Min-max parameters migrated as-is, even when lead times, sourcing, and reorder policies have changed in the new operating model. Cycle count setup deferred until after go-live, leaving teams with slow correction cycles and no confidence in on-hand figures.

So what does a practical approach look like? Treat inventory migration as both a data exercise and a process-control exercise. Validate master data. Confirm transaction rules. Run trial conversions that include real receiving and shipping scenarios—not just on-hand balances.

On-hand is the last thing to load, not the first thing to test.

AppsolveGroup Oracle Fusion SCM Managed Service: What's Included

Our oracle fusion scm managed service is built for organisations already running oracle supply chain management cloud—teams that have gone live and now need consistent, expert support without handing over control of their roadmap.

We handle the operational work that keeps SCM stable, secure, and performing well. And we provide functional guidance so your teams aren't left guessing when things change.

1) Post-go-live support (BAU)

The handover from project team to BAU is where things go wrong most often. We act as your support extension from day one:

  • Incident management: triage, reproduce, fix or workaround, confirm resolution with business users
  • Service request handling: master data changes, configuration assistance, reporting fixes, user access support (as agreed)
  • Root cause analysis: address the underlying configuration, data, or integration cause—not just the symptom
  • Operational runbooks: documented procedures, ownership boundaries, and clear definitions of what good looks like for common tasks

Everything runs against agreed SLAs, severity definitions, and escalation routes. The business always knows what happens next and when.

2) Quarterly update management (Oracle cadence)

Oracle's quarterly updates aren't optional. And they can quietly break things.

Planning flows, order execution logic, procurement processes, integrations, reporting—any of these can shift. We manage the full update cycle:

  • Release impact assessment: review Oracle release notes, identify what's likely to affect your configured flows
  • Regression test planning: define what gets tested, by whom, in which environments
  • Test execution support: coordinate functional testing, validate outcomes, manage defects and config changes
  • Change control and cutover support: readiness checkpoints and post-update verification
  • Production stabilisation: a hypercare window after each update, focused on transaction stability and interface health

Fewer surprises, clearer accountability, predictable quarterly readiness. That's the goal.

3) Performance monitoring and stability management

Performance problems rarely announce themselves. They show up as slow screens, stuck jobs, delayed interfaces—user friction before anything actually breaks.

We see this constantly during technical audits, and it's almost always preventable.

We monitor and tune proactively:

  • Scheduled process health: monitor critical ESS processes, failure patterns, run-time anomalies
  • Interface throughput: spot backlogs, retry storms, and timing-related issues across connected systems
  • Environment checks: validate configuration and operational settings that commonly degrade over time
  • Operational reporting: monthly service reporting with trends, risks, and recommended actions

Where the issue sits on Oracle's side, we'll build the evidence case and handle escalation with Oracle Support directly.

4) Integration and interface maintenance

Most SCM risk sits at the edges. Inbound and outbound messages, master data loads, execution confirmations—this is where problems hide and where failures hurt most.

Our managed service covers integration care across the full lifecycle:

  • Interface monitoring: detect failures early, respond quickly, reprocess in a controlled way
  • Mapping and transformation updates: maintain mappings when upstream or downstream schemas change
  • File/API/SOAP/REST support: troubleshoot authentication issues, payload format errors, sequencing problems
  • Data quality controls: identify recurring data issues and implement prevention steps—validation rules, reference data alignment

We prioritise practical controls: alerts, dashboards, and documented recovery steps. The business shouldn't be dependent on two people who know where everything is.

5) Functional consulting and continuous improvement

Ticket resolution is the floor, not the ceiling.

Support that only reacts to incidents isn't really support—it's fire-fighting. We provide functional consulting that helps teams improve, not just stabilise:

  • Configuration guidance: changes that use standard product capability and avoid brittle workarounds
  • Process optimisation: remove friction in approvals, exception handling, high-volume execution steps
  • Training and enablement: targeted sessions for superusers and support teams based on real issues coming through the queue
  • Backlog management: prioritisation, effort sizing, and a steady delivery cadence for small enhancements

We'll also help you draw the line between what belongs in BAU and what needs a controlled mini-project. That boundary matters more than most teams realise. Blurring it is one of the most common ways production stability gets eroded.

Typical managed service onboarding journey

  1. Weeks 1–2

    Discovery and service design

    Confirm modules in scope, integrations, pain points, environments, and support boundaries. Agree SLAs, severity model, and ways of working.

  2. Weeks 2–3

    Access, tooling, and controls

    Set up secure access, ticketing/triage workflow, monitoring/alerts, and documentation locations. Establish change control and approval paths.

  3. Weeks 3–4

    Knowledge transfer and baseline

    Review configurations, key jobs, integrations, and recurring incidents. Create runbooks and baseline performance/interface health metrics.

  4. Month 2

    Steady-state support begins

    Start BAU ticket handling, proactive monitoring, and weekly service touchpoints. Implement quick wins and reduce repeat incidents.

  5. Ongoing (Quarterly)

    Quarterly update cycle

    Run impact assessment, coordinate regression testing, manage remediation, and provide post-update stabilisation with clear release readiness checkpoints.

What SLAs do you typically offer for Oracle Fusion SCM managed service?

We define SLAs by severity (e.g., business-stopping vs. degraded service) and agree response and restoration targets in the contract. We also document what information is needed at ticket submission to hit those targets consistently.

How does escalation work if an issue is blocking critical SCM processing?

We use a clear escalation path: immediate triage, functional and technical swarm support, and—when required—escalation to Oracle Support with evidence (logs, timestamps, replication steps). You'll have named contacts and agreed communications cadence during major incidents.

Can you support UK data residency requirements?

Yes. We'll align to your Oracle hosting region and your internal policies on data handling. Access is controlled, audited, and limited to what's needed for support, with documented procedures for any data extracts or troubleshooting evidence.

Will Oracle quarterly patches break our SCM processes?

Quarterly updates can introduce changes that affect configured flows, integrations, and reports. Our process is to assess impact early, run targeted regression testing, remediate issues before production, and provide post-update stabilisation so disruptions are minimised.

Get an SCM Managed Service Proposal

Tell us your Oracle Fusion SCM scope and support needs. We'll respond with SLAs, onboarding steps, and a practical support model.

AI and Embedded Analytics in Oracle Fusion SCM

Oracle Fusion SCM includes embedded AI and analytics that show up inside the workflows people use every day. Not bolted on as a separate reporting layer. Actually inside the process.

The practical point isn't "AI for AI's sake." It's getting usable signal from operational data without waiting for a weekly report or an offline analysis cycle.

Demand sensing is one of the most immediately useful capabilities here. Rather than relying purely on periodic forecast refreshes, it adjusts near-term signals using live order patterns and operational inputs. Tighter cycles. Faster responses when demand shifts—without rebuilding planning models from scratch every time conditions change.

Disruption prediction is where it gets more interesting.

The goal is surfacing risk indicators early enough that planners can actually do something: expedite an alternative path, adjust sourcing, rebalance supply, re-sequence work. The tricky part is connecting the alert to the action. We see implementations fail when prediction is well-configured but no one has defined what happens next—who sees the alert, what they're supposed to do with it, and which workflow they move into to resolve it.

Adaptive intelligent apps push this further by bringing AI-driven recommendations into day-to-day screens. No dashboard hunting. The system highlights exceptions, suggests next-best actions, and guides prioritisation in context.

That's when embedded analytics actually pays off—when it's part of the operational process, not a destination you have to visit separately.

Turn data into decisions

Embedded AI works best when insights land inside the workflows people actually use. In Oracle Fusion SCM, demand sensing and disruption signals can shorten decision cycles—provided alerts, context, and actions are designed together.

Real-time analytics also matter for governance. When teams can see performance trends, constraint signals, and exception patterns as they happen, the "whose numbers are right" arguments tend to disappear. For organisations running an oracle fusion scm managed service, this is especially relevant. You're not just keeping the platform healthy—you're continuously improving how insights are consumed, escalated, and acted on.

Real-time supply chain analytics turn exception management into a controlled, repeatable operational habit.

So what does it actually take to get real value from embedded AI? Usually three things need to be true:

  • Define the decisions you want to improve—not just the metrics you want to track
  • Tune exception thresholds so people trust the alerts rather than ignoring them
  • Operationalise outcomes with clear owners—who reviews, who approves, and what "resolved" actually means

Most SaaS teams miss that last one. Configuration gets done, alerts start firing, and then nothing changes because ownership was never established.

The AI works. The process around it doesn't.

For a broader view of how Oracle is applying AI across the platform—including agent-driven patterns—see: Oracle AI agents.

Explore related Oracle Fusion topics

Transform Your Supply Chain with Oracle Fusion SCM and AppsolveGroup

Most Oracle Fusion SCM projects go live. Far fewer deliver the operational improvement they were supposed to.

The difference is almost always execution after go-live—how the platform gets configured, governed, and supported once the implementation team has left.

At AppsolveGroup, we help UK organisations get more from Oracle Fusion SCM by treating it as a managed, continuously improved service. Not a one-and-done deployment. That means clear ownership, controlled change, and the technical and functional support your team actually needs day to day.

Supply chain leaders care about specific outcomes: better planning confidence, cleaner item and supplier data, fewer workarounds, faster resolution when something breaks. That's where an oracle fusion scm managed service fits.

After go-live, the real challenges tend to be operational.

User adoption. Integration reliability. Master data that slowly drifts. Quarterly Oracle updates that nobody has time to test properly. We've seen this repeatedly during SCM engagements—and it's rarely down to the platform itself. It's down to not having the right support structure around it.

Our approach is straightforward:

  • ✓Stabilise what's already in place
  • ✓Prioritise improvements by business impact, not loudest voice
  • ✓Keep changes safe through structured testing and controlled deployment

We're UK-based, which matters. We work directly alongside UK operational teams and IT functions, navigate internal governance structures, and align to practical service levels.

Whether you need functional BAU cover, help managing Oracle's release cycle, or a proper backlog of enhancements that actually moves forward—we meet you where you are.

The tricky part for most teams is knowing where to start. If you want to sanity-check your current setup, understand what's slowing users down, or map out a support model that fits your organisation—that's exactly the conversation we have.

Talk to an SCM Specialist

Discuss your Oracle Fusion SCM priorities, current pain points, and the right managed service model for reliable BAU and change.

Ready to transform your supply chain?

Talk to us about Oracle Fusion SCM implementation and managed service.

Talk to a specialist

Get in touch about Oracle Fusion SCM

Ian and Gavin and the wider APPSolve Group team can talk through your situation — no obligation, no generic sales pitch. Just a direct conversation about what a realistic path forward looks like.