Introduction
After running your simulation, GAINS generates a number of comprehensive report output tables that capture every aspect of your supply chain's performance. This guide explains what each report table contains and how you can use the data for analysis and decision-making. Whether you're looking to understand service levels, analyze costs, or gain visibility into orders, inventory or shipments, you'll find the right table and know exactly what it tells you.
Quick Analysis Guide
Is our network meeting customer service targets?
• Use: NetworkServiceSnapshotCustomer, OrdersReport, OrderLinesReport
Where are our costs concentrated?
• Use: CostSnapshot, ShipmentReport
Are we carrying too much inventory?
• Use: SiteInventorySnapshotReport, UtilizationSnapshotInventory,
Which sites are bottlenecks?
• Use: SiteServiceSnapshotCustomer, LoadingSnapshotReport, UnloadingSnapshotReport, UnloadQueueReport
Is our shipment consolidation working well?
• Use: ShipmentReport, ShipmentLineItemReport, LoadingSnapshotReport
How does performance vary over time?
• Use: SiteServiceSnapshotCustomer
Getting Started
Start with the output of the KPI table to understand overall performance. Then drill into specific tables matching your question. Most analyses combine data from multiple tables. Don't hesitate to explore—each table provides different insights into your supply chain operations.
Service Level & Fulfillment Reports
Service Level & Fulfillment Reports
rpt.NetworkServiceSnapshotCustomer
rpt.NetworkServiceSnapshotCustomer
Daily network-level summary of customer order fulfillment performance.
Purpose
Shows how many customer orders were fulfilled each day and in what manner. Reveals patterns in service level over time.
Key Columns
• DateStamp – Date of snapshot
• CustomerOrders counts – Total, delivered in full/partial, not delivered, OTIF, split, shipped from primary, backordered, canceled
• CustomerUnits – Requested, delivered, lost/canceled, backordered
• CustomerRevenue – Revenue (based on delivered units)
How to Use It
• Track service level trends over the simulation period
• Identify seasonal or temporal patterns
• Diagnose when and why performance degrades
rpt.NetworkServiceSnapshotReplenishment
rpt.NetworkServiceSnapshotReplenishment
Daily network-level summary of replenishment (inbound) order fulfillment performance.
Purpose
Shows how many replenishment orders were fulfilled each day and in what manner. Reveals patterns in service level of replenishment orders over time. Shows how well suppliers, or other sites, are meeting replenishment needs.
How to Use It
• Understand supplier reliability over time
• Visualize replenishment order patterns over time
rpt.OrdersReport
rpt.OrdersReport
Order-level detail for every customer order in the simulation.
Purpose
Most granular view of customer order fulfillment, including whether each order was on-time, in-full, split, or lost.
Key Columns
• OrderID, Destination – Order and customer identification
• Service Status: OrderDeliveredInFull, OrderDeliveredPartial, OrderNotDelivered, OTIF
• ShippedfromPrimary - was this order shipped from its primary source (preferred source)?
• AnyLineBackordered, AnyLineCancelled - summary across the lines of this order
• Dates: DateRequestReceivedMin, DateArrivedMax, DestinationDueDate
• WasOrderSplit, AnyLineSplit – Was the Order fulfilled from more than one source? Were any lines on the Order fulfilled from more than one source?
• OrderCycleTimeDays – Time from order to delivery
How to Use It
• Analyze system performance by Customer
• Calculate fill rate, OTIF rate, and order split frequency
• Understand order cycle times
rpt.OrderLinesReport
rpt.OrderLinesReport
Order line-level detail for each SKU within each customer order.
Purpose
Shows the outcome of each product line within an order, including quantity sourced, shipped, backordered, or lost.
Key Columns
• OrderID, OrderLineID, SKU, Destination – Order, Customer and product identification
• Order Line Quantity: QuantityRequested, QuantityShippedOnTime, QuantityShippedFromOrigin, QuantityBackorderedAtOrigin, QuantityLostOrCancelled
• Order Line Service Status: OTIF, ShippedFromPrimary, SplitShipment
• CycleTimeDays – Time to fulfill this line
• Revenue – Revenue of each order line based on quantity delivered
How to Use It
• Identify which products are problematic (high backorder/split/loss rates)
• Analyze by SKU to find demand/supply mismatches
• Examine line-level splits to understand fulfillment complexity
• Calculate fill rates and service levels by product
rpt.SiteServiceSnapshotCustomer
rpt.SiteServiceSnapshotCustomer
Daily site-level summary of customer order line service metrics.
Purpose
Shows the order fulfillment and service level for each site over time.
Key Columns
• LocationName – Site name (or "NotSourced" if no site could fulfill)
• CustomerOrderLines - number of order lines, and all service level metrics by line (OTIF, backordered, split, etc)
• CustomerUnits – quantity sourced, shipped, backordered, lost
How to Use It
• Evaluate relative performance of different sites
• Identify bottleneck locations generating backorders
• Understand sourcing patterns and role of each site
• Diagnose capacity constraints or sourcing rule issues
Inventory Reports
Inventory Reports
rpt.SiteInventorySnapshotReport
rpt.SiteInventorySnapshotReport
Daily inventory position by site and SKU, including on-hand, policy parameters, and carrying costs.
Purpose
Provides the most detailed view of inventory across the network. Shows daily on-hand, position and costs.
Key Columns
• Site, SKU, InventoryDate
• InventoryOnHand – quantity of this SKU at this Site on this date
• InventoryPosition – quantity of this SKU at this Site plus any product that is inbound to this Site, on this date.
How to Use It
• Analyze inventory levels against reorder points
• Calculate total inventory investment and carrying costs
• Identify sites with excessive or insufficient stock
• Validate that reorder policies are working as designed
• Track inventory trajectory over the simulation period
rpt.InventorySiteSKUReport
rpt.InventorySiteSKUReport
Detailed event-by-event inventory activity for each site/SKU combination.
Purpose
Most granular inventory view, showing every inventory event and its impact on on-hand balance. Useful for understanding dynamics.
Key Columns
• InventoryDate, Site, SKU – Date and location
• InventoryEventOrActivity – Type of event (Review, Receipt, Shipment, etc.)
• InventoryOnHand, InventoryInbound, InventoryOutbound – Before and after
• InventoryPolicyParameter1 (s), InventoryPolicyParameter2 (S) – Reorder point and quantity
How to Use It
• Trace inventory through time at individual location/product level
• Validate replenishment logic
• Understand inventory volatility and variability
• Analyze seasonal or demand-driven inventory swings
rpt.InventoryInTransitSnapshotReport
rpt.InventoryInTransitSnapshotReport
Daily in-transit inventory by shipment and SKU, including carrying costs.
Purpose
Shows goods shipped but not yet arrived. Important for understanding pipeline inventory and cost impact.
How to Use It
• Calculate total in-transit inventory investment
• Understand impact of long lead times on network inventory
• Identify routes with high pipeline inventory
Cost Reports
Cost Reports
rpt.CostSnapshot
rpt.CostSnapshot
Daily cost breakdown by location and SKU, including transportation, carrying, and operational costs.
Purpose
Shows where costs are incurred across the network.
Key Columns
• DateStamp, LocationName, SKU
• InboundTransportationCost, OutboundTransportationCost
• AverageInventoryCarryingCost, AverageInTransitInventoryCarryingCost
• LoadingCost, UnloadingCost, DetentionCost
• CustomerRevenue, CustomerRevenueLostOrCancelled
How to Use It
• Identify cost drivers and high-cost SKUs or locations
• Understand cost trends over time
• Calculate cost per unit by location/SKU
Shipment & Transportation Reports
Shipment & Transportation Reports
rpt.ShipmentReport
rpt.ShipmentReport
Shipment-level detail for every shipment including origin, destination, mode, weight, cube, and costs.
Purpose
Provides visibility into transportation performance, shipment consolidation, mode selection, and freight costs.
Key Columns
• ShipmentID, Origin, Destination, Mode – Shipment identification
• ShipmentWeight, ShipmentCube, ShipmentQuantity – Physical characteristics
• ShipmentUtilization – How full was the shipment?
• TransitTimeDays – Time in transit
• ShipmentTotalCost – Freight cost
How to Use It
• Analyze shipment consolidation
• Understand transportation cost structure
• Identify mode selection patterns and cost implications
• Diagnose inefficiencies (many small shipments vs. few large)
• Evaluate whether mode constraints are being met
rpt.ShipmentLineReport
rpt.ShipmentLineReport
Detail of each product line within each shipment, including weight/cube contribution.
Purpose
Shows composition of each shipment and enables cost allocation across products.
How to Use It
• Allocate shipment costs to individual order lines or products
• Understand shipment consolidation patterns
• Analyze which products consolidate together
• Evaluate whether consolidation opportunities are missed
Site Operations Reports
Site Operations Reports
rpt.LoadingSnapshotReport
rpt.LoadingSnapshotReport
Daily summary of loading activity at each site, including total volume loaded.
Purpose
Shows daily volume of outbound activity from each site. Useful for resource planning and capacity analysis.
How to Use It
• Understand daily loading volume patterns
• Identify peak loading days and sites
• Calculate average daily loading volume
• Assess whether loading capacity is constraining performance
• Plan labor and equipment needs
rpt.UnloadingSnapshotReport
rpt.UnloadingSnapshotReport
Daily summary of unloading activity at each site, including total volume received.
Purpose
Shows daily inbound/receiving volume at each site. Useful for capacity and resource planning.
How to Use It
• Understand daily receiving volume
• Identify peak receiving periods
• Determine if unloading capacity is a bottleneck
• Plan dock and labor resources
rpt.LoadingLineDetail
rpt.LoadingLineDetail
Itemized loading costs for each product within each shipment.
Purpose
Allocates loading costs to individual products for detailed cost analysis.
How to Use It
• Allocate loading costs to products or orders
• Identify high-cost loading situations
• Analyze loading cost per unit by SKU
rpt.UnloadingLineDetail
rpt.UnloadingLineDetail
Itemized unloading costs for each product within each shipment.
Purpose
Allocates unloading costs to individual products for detailed cost analysis.
How to Use It
• Allocate unloading costs to products or orders
• Analyze unloading cost by product or site
• Identify high-cost unloading operations
rpt.UnloadQueueReport
rpt.UnloadQueueReport
Shipments waiting in yard (queue) for unloading and associated detention costs. Shipments wait in the yard if the unloading capacity has been met or if the storage capacity has been met and therefore the Site cannot accept any products.
Purpose
Identifies bottlenecks in receiving process. Shows which shipments experienced delays and cost impact.
Key Columns
• ShipmentID, Destination – Shipment identification
• DateArrived, DateUnloadingStartMin – Timeline
• TotalDaysInQueue – Time waiting
• YardDetentionCost – Cost of waiting
How to Use It
• Identify sites with receiving bottlenecks
• Calculate detention costs and drivers
• Determine if unloading capacity or staffing is constraining
• Evaluate trade-offs between capacity investment and detention costs
rpt.UtilizationSnapshotInventory
rpt.UtilizationSnapshotInventory
Daily storage capacity utilization for each site.
Purpose
Shows how full each site's storage is over time. Useful for capacity planning and identifying congestion.
Key Columns
• LocationName – Site name
• OnHandUnits, OnHandCases, OnHandPallets – Current inventory
• StorageCapacity – Total capacity
• StorageUtilization – Percentage of capacity used
How to Use It
• Track inventory levels against storage capacity
• Identify sites approaching or exceeding capacity
• Understand seasonal capacity needs
• Plan capacity expansions or consolidations
• Validate whether constraints are binding or loose
