How do trigger allocations work?
Readings that trigger an allocation
As part of the network setup up process, there are two places where there is an association done between the readings and the allocations process.
Allocation Config
Allocation config defines all the reading-attributes, their reading_types and the objects types they belong to, which can be used when allocating a product/disposition on a network.
Triggers are linked to updates to the readings and not to reading-attribute
Example: Tank readings may be acting as volume source to both oil/water production, but a change to any attribute on the tank reading would trigger allocation to both oil/water production, since the underlying reading was the same ( although attributes contributing to oil/water volumes may be different).
Allocation volume sources
When an allocation config is assigned to a network, choose the volume sources for each product and disposition to enable allocations for specific product/disposition combinations on a network.
This trigger allocation setup only enables triggered allocation runs on those objects/reading_type changes which are contributing to the allocation of product/disposition enabled as part of volume sources configuration.
Reading types
Readings which effect allocation of one specific day but not a period ( such as well test) are capable of triggering allocations.
Triggers are not supported for reading types such as “well tests” and “downtime events” readings as they impact allocations of more than one day.
Readings which only impact allocations for the reading-date are supported in trigger allocations (for example, commonwellreading( downtime), run-ticket( grossvol), Oiltankreading( oilproduction))
Dates over which the allocations are triggered
Stage/Prod accounts
Trigger allocations support a 14 day look back period. Any changes (edit, delete, create) to a reading which has a reading-date within 14 days of date/time you’re modifying the reading will trigger an allocation run.
Dev/QA accounts
Trigger allocations support a 1 day look back period. i.e any reading changes (edit, delete, create) to a reading which has a reading-date within 1 day of date/time ou’re modifying the reading will trigger an allocation run..
Networks with multiple versions
A single trigger setup across all the versions of the network
If there are multiple network versions to a network, the triggered allocation setup is updated using the information on the latest version of the network which was edited/saved.
Depending on which version of the network was edited most recently, the triggers on the specific network are set to the allocation config and volume sources defined in that network version.
Triggers run the effective network-version for the reading-date of the modified reading
As readings are modified, the triggers will force allocations to run on the appropriate network.
The network version whose effective date range includes the Reading-date of the modified reading is allocated.
Related Articles
- What is the difference between Daily Ledger- Tanks, Daily Ledger Wells and Monthly Ledger - Tanks
- What dispositions in Joyn Allocations are locked-in ( not changeable)?
- Do calculated attributes calculate when I use bulk upload?
- How do I update formula meters in a pre-existing allocation network with a new calculation logic?
- Can you load sets of transactional files in multiple open tabs at the same time?
- Why isn't a meter showing up as a volume source?
- How do trigger allocations work?
- Can I run allocations by Purchaser or Production team?
- Why is a reading not showing up in my app?
- How do I configure a network to use downtime and flowing events for allocations?
- How do I setup event-based downtime allocations?
- Does re-running allocation create duplicates or over-write existing allocation results?
- How do I create a calculation for a reading attribute?
- How do I configure a custom button and associate event readings to it?
- What does the exception found in "Wells Beginning and Ending inventory Mismatch" indicate?