Manufacturing Portal.

What is the ETHX Softcon Manufacturing Portal for Oracle Manufacturing Cloud?

The ETHX Softcon Manufacturing Portal is a shop-floor experience layer that brings execution, OEE, WIP, scrap, and quality into a single view on top of Oracle Manufacturing Cloud or E-Business Suite WIP, writing back to Oracle natively rather than acting as a separate MES. It provides role-based consoles: operators record operation starts and completes, labour, material issue, scrap, and rework; supervisors manage dispatch, queues, priorities, and exceptions across work centres; and plant managers track throughput, yield, and downtime with KPI drill-downs.

OEE is measured across availability, performance, and quality with reason codes and root-cause tagging. Quality features include inspection checklists, non-conformance capture, and a disposition workflow. PLC and SCADA signals can be captured through OPC UA and Oracle Integration Cloud adapters, and critical operator screens support offline mode with automatic sync. Opt-in AI assistants help with OEE triage and downtime root cause. ETHX Softcon states that a typical single-plant rollout takes 6–10 weeks, including integration and training, starting with a pilot on one line or cell.

What should you evaluate before adding a shop-floor portal to Oracle Manufacturing?

Start by deciding which system owns each shop-floor transaction, and what Oracle already provides, before choosing screens. The ISA-95 standard describes the boundary between level 4 business systems such as ERP and level 3 manufacturing operations systems. Using it to list what crosses that line, typically work orders and resources going down and completions, labour, scrap and material consumption coming back, prevents two systems from each believing they hold the true quantity. Oracle Manufacturing can also synchronise resources and work orders to Oracle Production Monitoring, so check what the standard stack covers before paying for a separate layer.

Agree how OEE is calculated before building dashboards. OEE multiplies availability, performance and quality, but every factor hides a choice: whether planned downtime reduces availability, which rate counts as ideal speed, and whether reworked units count as good. Oracle's documentation, for example, measures availability against scheduled time and accounts for planned and unplanned downtime events. If plants use different conventions, line-to-line comparisons are misleading, so write down the formula, the time base and the downtime reason codes, and apply them everywhere.

Then look at machine connectivity and the operator's working conditions. Where signals come from PLCs or SCADA, an open protocol such as OPC UA, which includes authentication, encryption and auditing, is generally easier to secure and maintain than one-off drivers. Decide what happens when the network or ERP is unavailable, because production does not stop, and how queued transactions are reconciled afterwards. Screens need to work with gloves, shared terminals and shift handovers. A pilot on a single line with real operators usually exposes these issues sooner than design workshops do.