Reference · built on requestOperator by FibricEnergy & demand

Price Shift

Deferrable production runs moved to cheaper hours on the wholesale day-ahead curve, with the real-time price watched after approval.

Request accessPricing ↗

About

Some runs have a deadline but no fixed hour: a grind, a bake, a wash cycle, a compressor top-up. This operator reads the day-ahead locational marginal prices your ISO posts, such as CAISO OASIS PRC_LMP for the DAM market run, and the batch schedule from your SCADA, MES, or historian over OPC UA. EIA's grid monitor supplies hourly demand and the day-ahead demand forecast; EIA publishes no hourly prices, so prices come from the ISO alone.

For each run marked deferrable it proposes a later or earlier block of hours inside the deadline. The planner approves, the start tag is written, and the real-time price is watched for a plan that no longer holds.

This is a reference listing. It documents what Fibric would read from Price Shift and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Day-ahead hourly locational marginal prices from your ISO's feed, for example CAISO OASIS PRC_LMP with market_run_id DAM, queried by node or grp_type ALL
  • Real-time prices as the ISO posts them: CAISO PRC_INTVL_LMP for RTM and PRC_RTPD_LMP for the fifteen-minute market
  • Hourly demand and the day-ahead demand forecast for your balancing authority from EIA's electricity/rto route
  • The batch or production schedule from SCADA, MES, or the historian: planned start, duration, and the run's deadline
  • Machine state, counters, and schedule tags read from OPC UA nodes, each with its StatusCode and SourceTimestamp
  • Which runs are flagged deferrable, with the earliest and latest start each may take

Proposed actions

  • Target capability: propose deferring a run to a later block of hours where the day-ahead price is lower, inside its deadline
  • Target capability: propose advancing a run into the hours before a priced peak when material and crew are available
  • Target capability: propose a write to the run's scheduled-start tag on the controller through the PLC Command Bridge
  • Target capability: propose pausing an approved plan when the real-time price departs from the day-ahead price it was built on
  • Target capability: propose a note to the production planner with the price blocks it compared and the runs it left alone

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Batch runs on the CAISO day-ahead curve

    The evening grind runs are read from the historian over OPC UA. Against PRC_LMP for the next trade date, the operator proposes the cheapest block that still meets each run's deadline.

    With CAISO OASIS, OPC UA

  • Ignition schedule tags in PJM

    Deferrable runs tagged in Ignition are compared with PJM's day-ahead hourly LMPs at your pnode. The planner approves a shifted start and the tag is written back once.

    With Ignition, PJM Data Miner 2

  • Start-time writes to a SIMATIC controller

    A compressor top-up cycle whose start time lives on an S7 controller is moved through the bridge to the declared tag, with the demand forecast from EIA shown beside the price.

    With PLC Command Bridge, SIMATIC S7-1500, Grid Demand & Prices

Requirements

  • Access to your ISO's price feed: CAISO OASIS answers SingleZip queries without an account, while PJM and ERCOT issue subscription keys
  • A free EIA API key and your balancing authority code for the demand and forecast series
  • An OPC UA endpoint or a SCADA or MES connector exposing the schedule and run-state tags, with certificates exchanged
  • A list of deferrable runs with deadlines; the operator never chooses which runs may move
Authentication
It signs in nowhere on your plant floor. ISO feeds are read with the keys those markets issue, EIA with your free API key, and the schedule through the OPC UA or SCADA connector's own certificate exchange.

Limits

  • Wholesale prices are not your retail bill. Unless you buy on an index or real-time rate, the price is a signal, not a saving.
  • EIA publishes no hourly price data. Prices come only from ISO feeds, which differ in nodes, intervals, and access terms.
  • A run chained to an upstream or downstream step moves only when the whole chain has slack you have declared.
  • It works from the demand forecast until the ISO posts the day-ahead prices. Proposals made before that are marked provisional.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Price Shift ↗

Questions and answers

What does the planner approve?
One proposal per run: the current start, the proposed start, the price blocks compared, the market run they came from, the deadline, and the estimated cost difference. The planner approves, edits the hours, or declines.
What record does a moved run leave?
A receipt with the run id, both schedules, the price series and node it read, the forecast used, timestamps, who approved, and the write outcome on the controller. The original start stays on the receipt for undo.
Will a price spike move a run without asking?
No. A real-time price that breaks an approved plan produces a new proposal to pause or restore. Nothing is written to a controller without an approval, and never twice.
Ask about Price Shift

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy