Skip to content

Systems and records

Energy procurement exception dataset: a date change after approval

By SourceX Editorial · Reviewed by Noah Loul ·

9 sections

Short answer

Represent a supplier date change after schedule approval as a task record, not an edited field: snapshot the promised date and the approved schedule it supports, log the change notice with its time and channel, attach the contract terms and approval limits in force, show the impact on dependent work, name the role that decided, and verify the outcome against receipt and work completion records.

Provenance trail

Energy procurement exception

This page covers energy procurement exception dataset: a date change after approval.Illustrative

Key takeaways

  • Snapshot the promised date when the dependent schedule is approved; many systems keep only the latest expected date.
  • Record each change notice as a new event with time, channel and acknowledgment type.
  • The decision belongs to whoever owns what the new date breaks, such as the outage window, not to whoever received the email.
  • Verify outcomes against receipt and work completion records, because purchasing statuses can look on time while the task failed.
  • Classify packets for CEII, cyber asset and pricing content before anything leaves the utility.

How do you represent a supplier date change after a schedule was approved?

Represent it as a task, not as an edited field. The record needs the starting state (the approved purchase order line, its promised date and the approved work schedule that depends on it), the change notice with its received time and channel, the contract term and approval thresholds in force on that date, the impact on dependent work, the decision and the role that made it, and an outcome verified against receipt and work completion records. Each element points to the record that proves it.

That structure is what makes an energy procurement exception dataset useful to an AI team. A model learning to handle supplier changes needs to see what was known when the notice arrived, which rules applied, who was allowed to decide, and whether the decision held. A table of purchase orders with a final expected date shows none of that, because the original promise has usually been overwritten.

This page uses a utility's maintenance procurement as the running example: equipment ordered for a planned outage, with crews, switching and clearances scheduled around the delivery. The same packet works for fuel, chemicals, meters or contracted services where an approved schedule depends on a supplier's date.

Why does the purchase order alone forget the original date?

Many purchasing systems keep the latest expected date and nothing else, so the change has to be captured as its own record. Odoo's open source purchasing module is a clear example because its code is public. The purchase order's Expected Arrival field is described as the expected delivery date of goods by the vendor based on the latest information, and the order-level value is computed as the earliest date across its lines.

When a confirmed order line changes, Odoo's line write method posts a chatter note for changes to quantity and unit price; the expected arrival date is not in that list. In the stock extension, a new planned date is pushed only to incoming moves that are not already done or canceled. Anyone exporting order lines later sees the newest date and may find no trace of the date that the outage schedule was built on. Other systems differ, which is the point: check how your own system keeps history before you assume the change is recoverable.

Electronic data interchange gives a cleaner signal when trading partners use it. X12 lists the 860 as the buyer's purchase order change request and the 865 as the seller's purchase order change acknowledgment or request, which a seller uses to accept, reject or modify an order. X12's published examples also show that an acknowledgment without detail requires a follow-up 865 that either accepts or carries the changes. A supplier date change that arrives this way already has a timestamp, a sender and a transaction reference to keep.

  • Snapshot the line's promised date at the moment the dependent schedule is approved.
  • Store every later date notice as a new event with received time, channel and sender, never as an overwrite.
  • Keep the acknowledgment type when EDI is used, since an acknowledgment without detail is not an acceptance of a date.
  • Record which incoming receipts were already complete when the date moved.

What do the contract, the asset and the crew safety plan allow after the slip?

Three kinds of fact decide what the buyer may do next: what the contract and approval policy said on that date, what the late item is and which system it belongs to, and which safety and reliability steps were built on the original date. A packet that omits any of them cannot show why the decision was right.

Contract and policy facts include the delivery clause, remedies for late delivery, substitution rules and the approval thresholds for changing an order. Odoo again illustrates the mechanics: a company can confirm purchase orders in one step or require two levels of approval above a set amount, and can lock confirmed orders against editing. A change accepted on a day when two-step approval applied needs the second approver in the packet.

Asset facts matter because some items carry their own controls. For high and medium impact BES Cyber Systems, NERC's supply chain standard CIP-013 requires a documented supply chain cyber security risk management plan whose procurement processes cover, among other things, vendor notification of incidents and coordination of responses. The version cited here is CIP-013-2; NERC has since adopted CIP-013-3, so check which version is in effect for the entity. If the late item is a relay, controller or other cyber asset, a supplier's proposed substitute or revised shipment is a procurement change that the plan may govern, and the packet should record that the plan applied.

Safety facts are the boundary the dataset records but never replaces. OSHA's 1910.269 standard requires a job briefing before each job on covered generation, transmission and distribution work and additional briefings when significant changes that might affect employee safety occur. A slipped delivery that moves the work into a different outage window or crew changes the plan those briefings covered. The packet notes that re-planning and re-briefing happened and links to the record; it does not describe switching steps or energized work, which stay with qualified staff.

What should one change-notice packet record, row by row?

The packet below is the original asset. Fill one per change notice, keep every row even when the answer is none, and give each row an evidence reference that someone outside the procurement team could follow. Label each packet real or illustrative and record the packet version.

What should one change-notice packet record, row by row?
Packet elementWhat to captureSource recordConfirmed by
Starting stateOrder and line keys, promised date at approval, approved schedule or outage window it supportsPurchase order history snapshot, schedule approval recordBuyer and outage or work planner
Change noticeNew date, reason given, received time, channel, acknowledgment type if EDI865 transaction, supplier email or portal messageBuyer
Rules in forceDelivery and substitution clauses, approval thresholds, lock settings, cyber supply chain plan applicabilityContract version, purchasing configuration, plan referenceContract owner, compliance
ImpactDependent work orders, outage windows, crews, permits and customer notices affectedWork order and outage schedule recordsWork planner, system operations
Options consideredAccept, expedite, source alternate, re-sequence work, cancel and reorderDecision notes, quotes or alternate supplier responses with pricing removedBuyer and planner
Decision and authorityChosen option, approver role, approval time, policy versionApproval log or change recordApprover named by role
Safety and confidentiality flagsRe-planning and re-briefing required, CEII or cyber information presentJob planning record reference, information classificationSafety lead, information owner
Verified outcomeActual receipt date, inspection result, work completed in which window, any second slipReceipt record, work order completion, outage logWarehouse and work planner
Counterexample flagWhether a status or message claims success the records do not supportComparison of status fields with receipt and completion recordsReviewer

Who may accept a new delivery date?

Authority depends on what the new date touches, not on who received the email. A date that moves inside the schedule's slack can usually be accepted by the buyer. A date that breaks an approved outage window or a committed customer or regulatory date needs the owner of that commitment to decide, and the packet should show that decision rather than only the buyer's reply to the supplier.

Who may accept a new delivery date?
What the new date affectsTypical decision ownerEvidence that the decision was madePacket label if missing
Nothing scheduled; slack absorbs itBuyerAcknowledged date and updated line historyDecision implied, low risk
An approved outage or clearance windowOutage coordinator or system operationsRevised outage request and approvalAuthority not shown
Crew assignments or contractor bookingsWork planner or field supervisorRescheduled work order and crew planAuthority not shown
Item revision, substitute or partial shipmentEngineering and, for cyber assets, the plan ownerEngineering acceptance and procurement review recordUnapproved substitution risk
Contract terms, remedies or priceContract owner under the approval policyContract amendment or change orderCommercial change not authorized
A customer or regulatory commitment dateCompliance or customer operations leadNotice record and internal sign-offCommitment risk not handled

How should an illustrative breaker slip past an outage window be recorded?

This case is invented to show the packet; all counts and durations are illustrative and no real asset is described. A utility orders a replacement circuit breaker for a substation maintenance outage. The order line is confirmed with a promised date 10 days before a three-day outage window, and the outage request is approved on that basis.

Twenty-two days before the window, the supplier sends an 865 acknowledgment without detail, then an email five days later moving shipment to two days after the window opens. The order line's expected date is updated from the email. The buyer's packet records the original promised date from the snapshot taken at outage approval, the email's received time and the fact that the earlier EDI acknowledgment carried no date.

Impact review shows the window cannot absorb the slip because the breaker must be inspected on receipt before installation. Options considered are expediting, borrowing a spare from another district, or moving the outage. The outage coordinator approves a new window 18 days later, which changes the crew assignment, so the work planner records that the job plan and briefing were redone for the new window. Purchasing policy that week required a second approver for order changes above its threshold; the expedite option would have crossed it and was not taken.

The verified outcome is a receipt seven days before the new window, an inspection pass and a work order completed in the new window. The packet's label is success with a schedule change, decided by the role that owned the outage. A model trained on it learns that the right next step after a slip into an approved window is a re-approval by the outage owner, not a reply to the supplier.

Can a task fail while every purchasing status says on time?

A status field can say on time while the task failed. In a variant of the same case, the buyer overwrites the expected date, the supplier ships on the new date, and the receipt is marked complete against the latest expected date, so a delivery performance report shows the order on time. Meanwhile no one asked for a new outage window. The crew arrives in the original window without the breaker and the work order is canceled and reissued.

Measured against the packet, the decision and authority row is empty, the impact row shows a canceled work order, and the verified outcome is a failure even though every purchasing status is green. A plausible final message such as rescheduled, all set does not change that. Datasets that grade tasks by status fields or by the tone of the last message will mark this case a success, which is why the packet compares statuses with receipt and completion records and flags the mismatch.

What must be removed before an energy procurement exception dataset leaves the utility?

Utility procurement records can contain information that must not leave the company in usable form, so classify each packet before it is shared. Federal Energy Regulatory Commission rules at 18 CFR 388.113 define critical energy infrastructure information as specific engineering, vulnerability or detailed design information about existing or proposed critical infrastructure that could be useful to a person planning an attack and that goes beyond giving the general location of the infrastructure. Equipment specifications, one-line references, substation identifiers tied to locations and protection settings can fall near that line.

At a glance

What must be removed before an energy procurement exception dataset leaves the utility

Keep what the task needs and remove the rest. Replace asset and substation identifiers with stable pseudonymous keys, generalize equipment to a class, drop drawings and settings, remove supplier pricing and commercial terms, and replace staff names with roles. Information about cyber assets and their vendors deserves the same review under the company's own information protection program. When an item's role cannot be described without sensitive detail, leave that packet out.

  • Keep: event timestamps, date deltas, document types, approval roles, policy versions, outcome flags.
  • Generalize: equipment model to equipment class, location to region or voltage class.
  • Remove: drawings, protection or control settings, network details, pricing, personal names.
  • Escalate: any packet the information owner cannot classify, before it leaves the utility.

What changes when these packets become a licensed dataset?

A utility or energy services company with years of linked procurement, schedule and work order history holds decision records that are hard to reproduce: real slips, real authority decisions and outcomes that can be checked. Before licensing them, keep four questions apart. Having access to the records, having privacy permission, owning the records and holding contractual rights under supplier and vendor agreements are different things, and removing identifiers does not create a right to license.

Utilities that license this kind of history through SourceX hand it the rights review, contract, preparation and delivery work that turns chosen procurement and work order records into an AI dataset. Eligibility is checked through a brief company assessment, with no files uploaded, and multi-terabyte exports never sit on SourceX servers: they remain in the utility's own storage or travel on encrypted drives.

Frequently asked questions

Should the original promised date be kept after a supplier changes it?

Yes. Snapshot it when the dependent schedule is approved and record every later date as a new event. Without the original, a dataset cannot show that a change happened or measure its impact.

Is an EDI acknowledgment the same as accepting the new date?

No. X12's examples show that an acknowledgment without detail needs a follow-up that either accepts or carries changes. The packet should record the acknowledgment type and the internal decision separately.

Who should approve a delivery date that breaks an outage window?

The owner of the outage or clearance window, usually system operations or an outage coordinator, under the company's own procedures. The buyer's reply to the supplier is a communication, not that approval.

Can these records include safety information?

They can reference that re-planning and job briefings happened and link to those records. They should not describe switching steps, energized work procedures or protection settings, which belong with qualified staff and are often sensitive.

What makes a supplier date change a failed task rather than a late delivery?

The task fails when the dependent work is disrupted or the decision was made without the right authority, even if the delivery itself was eventually received and marked complete.

Sources

  • Odoo's purchase order model defines Expected Arrival as the expected delivery date based on the latest information and computes the order's date as the earliest line date. Source
  • Odoo's purchase order line write method posts a note for quantity and unit price changes on confirmed orders. Source
  • Odoo's stock extension applies a new planned date only to incoming moves that are not done or cancelled. Source
  • Odoo lets a company confirm purchase orders in one step or require two levels of approval above a set amount, and lock confirmed orders against editing. Source
  • X12 lists the 860 buyer-initiated purchase order change and the 865 seller-initiated change acknowledgment or request used to accept, reject or modify a purchase order. Source
  • X12's example shows an acknowledgment without detail requires a follow-up 865 that accepts or carries changes. Source
  • NERC CIP-013-2 requires documented supply chain cyber security risk management plans for high and medium impact BES Cyber Systems, including vendor notification of incidents and coordination of responses. Source
  • OSHA 1910.269 requires a job briefing before each job and additional briefings when significant changes that might affect employee safety occur. Source
  • 18 CFR 388.113 defines critical energy infrastructure information as specific engineering, vulnerability or detailed design information that could be useful in planning an attack and goes beyond general location. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies