Shipment Node Performance Metrics in Refinery Simulation
Shipment Planning Series
1. Shipment Planning Fundamentals (complete guide)
2. Shipment Node Control
3. Shipment Execution Strategies
4. Daily vs Monthly Planning
5. Working Calendars
6. Shipment Performance Metrics
7. Why Shipment Planning Should Be Simulated
Solution: Shipment Node Simulation for Petroleum Refining Digital Twins
1. Shipment Planning Fundamentals (complete guide)
2. Shipment Node Control
3. Shipment Execution Strategies
4. Daily vs Monthly Planning
5. Working Calendars
6. Shipment Performance Metrics
7. Why Shipment Planning Should Be Simulated
Solution: Shipment Node Simulation for Petroleum Refining Digital Twins
A Shipment Node is a refinery simulation component for petroleum refining that represents the controlled transfer of petroleum products from the refinery to external transportation systems, pipeline operators, terminals, or customers as part of refinery logistics and production planning. Located at the end of the process flow, Shipment Node coordinates shipment plan execution by tracking actual transferred volumes against the defined plan. It supports multiple scheduling strategies, working calendars, and operating hour restrictions, enabling realistic simulation of production and shipment planning without directly controlling material flow. In addition to controlling (See Shipment Node Control in Refinery Simulation) shipment behavior, the component provides comprehensive performance metrics for monitoring operational efficiency, plan execution, and historical shipment performance.
Why Shipment Nodes Require Specialized Statistics?
In refinery operations, product dispatch is governed by shipment plans, loading schedules, pipeline availability, and working calendars. A shipment may maintain a stable flow while failing to meet its planned target, or experience temporary interruptions without affecting overall plan execution.
To address this, the Shipment Node provides specialized performance metrics that combine operational and planning data. In addition to monitoring current flow conditions, it tracks shipment progress, compares planned and actual shipped volumes, calculates the remaining shipment target, and stores historical execution records for performance analysis.
All metrics are calculated for a single assigned product and the currently active shipment plan. Each planning period is evaluated independently, reflecting common refinery practice where shipment plans are generated separately for each planning horizon or pipeline dispatch schedule. As a result, unfulfilled shipment volumes are not automatically carried over to the next planning period.
To address this, the Shipment Node provides specialized performance metrics that combine operational and planning data. In addition to monitoring current flow conditions, it tracks shipment progress, compares planned and actual shipped volumes, calculates the remaining shipment target, and stores historical execution records for performance analysis.
All metrics are calculated for a single assigned product and the currently active shipment plan. Each planning period is evaluated independently, reflecting common refinery practice where shipment plans are generated separately for each planning horizon or pipeline dispatch schedule. As a result, unfulfilled shipment volumes are not automatically carried over to the next planning period.
The Petroleum Refining Library provides direct access to all Shipment Node performance metrics through the ShipmentNodeStatistics class. The API allows developers to retrieve real-time operating data, evaluate shipment plan execution, analyze historical shipment records, and integrate performance indicators into custom applications, Digital Twins, and refinery dashboards.
Learn the complete refinery shipment planning workflow in Refinery Shipment Planning.
Learn the complete refinery shipment planning workflow in Refinery Shipment Planning.
Interactive Example Available!
See Petroleum Refining Library ShipmentNode in action!
Launch the interactive AnyLogic Cloud model and experiment with a live refinery tank farm simulation
See Petroleum Refining Library ShipmentNode in action!
Launch the interactive AnyLogic Cloud model and experiment with a live refinery tank farm simulation
Shipment Node Statistics Categories
Shipment Node exposes a comprehensive set of performance metrics covering every stage of refinery shipment operations. For ease of analysis, these metrics are grouped into four categories based on their engineering purpose: flow monitoring, shipment plan execution, scheduling information, and historical performance analysis. Together, they provide a complete framework for monitoring, evaluating, and optimizing refinery shipment processes.
Together, these statistics provide a complete operational picture of refinery shipment execution and enable engineers to evaluate logistics performance, monitor pipeline transportation, validate Digital Twin behavior, and optimize refinery production planning.
Together, these statistics provide a complete operational picture of refinery shipment execution and enable engineers to evaluate logistics performance, monitor pipeline transportation, validate Digital Twin behavior, and optimize refinery production planning.
Shipment Flow Statistics
Flow statistics provide real-time information about refinery product transfers and are widely used for pipeline transportation monitoring, loading rack supervision, refinery logistics dashboards, and Digital Twin visualization. They also provide valuable simulation results for validating refinery operating scenarios and comparing shipment behavior under different operating conditions. These metrics are primarily used to monitor loading operations, verify pumping rates, and analyze the distribution of incoming product streams.
Shipment Plan Statistics
Shipment plan statistics evaluate how effectively the Shipment Node fulfills refinery shipment plans and support production planning, refinery scheduling, logistics optimization, and shipment KPI analysis. Unlike flow statistics, which describe the current operating state, these metrics measure shipment progress, compare planned and actual shipped volumes, determine the remaining shipment target, and calculate plan completion indicators.
The Shipment Node evaluates each planning period independently. Shipment plans are not automatically carried over between planning periods, allowing monthly, daily, or pipeline shipment schedules to be analyzed separately. When required, overplanning can be enabled to allow the actual shipped volume to exceed the planned target.
The Shipment Node evaluates each planning period independently. Shipment plans are not automatically carried over between planning periods, allowing monthly, daily, or pipeline shipment schedules to be analyzed separately. When required, overplanning can be enabled to allow the actual shipped volume to exceed the planned target.
Shipment Scheduling Statistics
Shipment scheduling statistics identify the scheduling strategy currently used to execute the shipment plan and control the Shipment Node. These metrics help engineers verify refinery scheduling logic, validate shipment control strategies, and compare alternative refinery logistics scenarios within Digital Twin models. Unlike shipment plan statistics, scheduling statistics do not measure performance. Instead, they describe the operational logic used to generate shipment requests and execute the shipment plan.
Historical Shipment Statistics
Historical shipment statistics provide access to archived shipment execution data for refinery reporting, logistics KPI calculation, production planning analysis, and long-term Digital Twin validation. These statistics support long-term performance analysis, monthly reporting, KPI calculation, and comparison of planned versus actual shipment volumes. Historical shipment data also supports simulation analytics by enabling engineers to compare multiple refinery simulation runs, evaluate operational trends, and validate Digital Twin performance over different planning horizons.
Shipment records are automatically stored immediately before the shipment plan is updated. Consequently, the recording frequency depends on the selected planning strategy. Monthly planning generates one record per month, while daily and evenly distributed daily planning generate one record per day.
Applications of Shipment Node Performance Metrics
- Real-Time MonitoringMonitor refinery shipment operations and loading activities as they occur.
- Plan TrackingTrack shipment plan execution against scheduled refinery logistics operations
- Volume ComparisonCompare planned and actual shipped volumes across reporting periods
- Delay DetectionIdentify shipment delays, interruptions, and incomplete product deliveries automatically
- Pipeline PerformanceEvaluate pipeline export efficiency and overall shipment throughput performance
- Rack UtilizationAnalyze loading rack utilization and identify operational bottlenecks efficiently
- Monthly ReportingGenerate comprehensive monthly shipment reports for operational performance analysis
- Logistics DashboardsBuild refinery logistics dashboards using shipment statistics and key performance indicators
- Strategy ComparisonCompare alternative shipment scheduling strategies under identical operating conditions
- Digital Twin ValidationValidate Digital Twin models and refinery production planning scenarios accurately
These applications allow refinery engineers to build operational dashboards, compare production planning scenarios, evaluate logistics efficiency, validate Digital Twin models, and improve refinery shipment performance using historical and real-time operational data. Shipment Node statistics support both operational monitoring and long-term analysis of refinery logistics. They enable engineers to evaluate shipment execution, identify deviations from planned schedules, and compare the effectiveness of alternative shipment strategies. The collected statistics can also be used to calculate simulation KPIs for refinery logistics, shipment execution, production planning, and Digital Twin performance evaluation.
The following example demonstrates how to access the current shipment plan, shipped volume, completion ratio, and remaining shipment volume.
The following example demonstrates how to access the current shipment plan, shipped volume, completion ratio, and remaining shipment volume.
ShipmentNode shipment = ...;
ShipmentNodeStatistics stats = shipment.statistics;
double shipped = stats.getActualShipped();
double plan = stats.getActualPlan();
double completion = stats.getActualShippedRatio();
double remaining = stats.getRemainingToShip();Conclusion
Shipment Node performance metrics provide a comprehensive view of refinery shipment operations by combining real-time flow monitoring with shipment plan execution and historical performance analysis. Together, these statistics allow engineers to evaluate not only how much product is being shipped, but also how effectively shipment plans are being fulfilled. The Petroleum Refining Library exposes these metrics through a straightforward API, making them suitable for operational dashboards, KPI reporting, Digital Twin applications, and automated analysis of refinery logistics. By integrating operational, planning, scheduling, and historical statistics, Shipment Node enables accurate evaluation of refinery simulation results, supports simulation analytics, and provides reliable simulation KPIs for continuous optimization of refinery shipment performance.
Shipment Node statistics form a unified performance framework that combines operational monitoring, shipment planning, scheduling, and historical analytics within a single API. This enables consistent KPI reporting, Digital Twin validation, refinery logistics optimization, and production planning analysis.
Continue reading the complete Shipment Planning in Refinery Simulation guide to learn how shipment plans are created, executed and validated in refinery Digital Twin models.
Shipment Node statistics form a unified performance framework that combines operational monitoring, shipment planning, scheduling, and historical analytics within a single API. This enables consistent KPI reporting, Digital Twin validation, refinery logistics optimization, and production planning analysis.
Continue reading the complete Shipment Planning in Refinery Simulation guide to learn how shipment plans are created, executed and validated in refinery Digital Twin models.
FAQ
1. What is the purpose of Shipment Node performance metrics?
Shipment Node performance metrics measure both operational and planning performance. They report current shipment flows, evaluate shipment plan execution, calculate completion ratios, and provide historical statistics for long-term logistics analysis.
2. How is shipment plan completion calculated?
The Shipment Node compares the actual shipped volume with the current shipment plan and calculates the corresponding completion ratio. Additional metrics report the remaining shipment volume and the current plan completion status.
3. Does Shipment Node support overplanning?
Yes. Shipment Node can be configured to allow overplanning, enabling the actual shipped volume to exceed the planned shipment target when refinery operating conditions require additional product dispatch.
4. Are shipment plans carried over to the next planning period?
No. Each planning period is evaluated independently. Unfulfilled shipment volumes are not automatically transferred to the next shipment plan, reflecting common refinery planning and pipeline dispatch practices.
5. How often are historical shipment statistics recorded?
Historical records are stored automatically immediately before the shipment plan is updated. Therefore, the recording frequency depends on the selected planning strategy, typically once per month for monthly planning or once per day for daily scheduling.
6. Can historical shipment data be queried for a specific period?
Yes. The historical database supports queries for individual calendar months as well as arbitrary date ranges, allowing engineers to compare planned and actual shipment volumes over any reporting period.
7. Can Shipment Node statistics be integrated into refinery dashboards?
Yes. All performance metrics are available through the Petroleum Refining Library API, making them suitable for Digital Twin dashboards, KPI reporting, production monitoring, and refinery logistics analytics.
8. What is the difference between flow statistics and shipment plan statistics?
Flow statistics describe the current operating conditions of the Shipment Node, such as incoming flow rates. Shipment plan statistics evaluate operational performance by comparing planned and actual shipped volumes, calculating completion ratios, and tracking remaining shipment requirements.
9. How can Shipment Node statistics improve refinery production planning?
Shipment Node statistics provide operational KPIs, shipment completion ratios, historical performance records, and logistics indicators that help engineers optimize refinery production planning, pipeline transportation, and Digital Twin decision support.
Shipment Node performance metrics measure both operational and planning performance. They report current shipment flows, evaluate shipment plan execution, calculate completion ratios, and provide historical statistics for long-term logistics analysis.
2. How is shipment plan completion calculated?
The Shipment Node compares the actual shipped volume with the current shipment plan and calculates the corresponding completion ratio. Additional metrics report the remaining shipment volume and the current plan completion status.
3. Does Shipment Node support overplanning?
Yes. Shipment Node can be configured to allow overplanning, enabling the actual shipped volume to exceed the planned shipment target when refinery operating conditions require additional product dispatch.
4. Are shipment plans carried over to the next planning period?
No. Each planning period is evaluated independently. Unfulfilled shipment volumes are not automatically transferred to the next shipment plan, reflecting common refinery planning and pipeline dispatch practices.
5. How often are historical shipment statistics recorded?
Historical records are stored automatically immediately before the shipment plan is updated. Therefore, the recording frequency depends on the selected planning strategy, typically once per month for monthly planning or once per day for daily scheduling.
6. Can historical shipment data be queried for a specific period?
Yes. The historical database supports queries for individual calendar months as well as arbitrary date ranges, allowing engineers to compare planned and actual shipment volumes over any reporting period.
7. Can Shipment Node statistics be integrated into refinery dashboards?
Yes. All performance metrics are available through the Petroleum Refining Library API, making them suitable for Digital Twin dashboards, KPI reporting, production monitoring, and refinery logistics analytics.
8. What is the difference between flow statistics and shipment plan statistics?
Flow statistics describe the current operating conditions of the Shipment Node, such as incoming flow rates. Shipment plan statistics evaluate operational performance by comparing planned and actual shipped volumes, calculating completion ratios, and tracking remaining shipment requirements.
9. How can Shipment Node statistics improve refinery production planning?
Shipment Node statistics provide operational KPIs, shipment completion ratios, historical performance records, and logistics indicators that help engineers optimize refinery production planning, pipeline transportation, and Digital Twin decision support.