Core principle 4: Dynamic data

If you end up in a traffic queue as a truck driver, your cargo will arrive at its destination later. To avoid disrupting the logistics process after your delivery, the recipients of your cargo – and the following logistics parties – must immediately receive an update on the delay. 

The BDI makes this possible, as this framework allows you to share data that is time-sensitive and may be created ad hoc. In other words: the BDI is based on what is called a Dynamic Data Lifecycle. 

Data and logistics stages

In the BDI, the operational data completes various stages as the logistics activities develop. These stages include (so are not limited to): 

• Requested 
• Accepted 
• Planned 
• Changed plan 
• In transit 
• Delivered 
• Registered/Logged 
• Proof of compliance 
• Confirmed 

Consequences 

It must be possible for a data element to complete several stages during the execution of logistics processes. The BDI must be able to ‘handle’ these dynamics as it were. That is why this framework offers a robust structure that supports the dynamic nature of business processes. Furthermore, you can use the BDI with specific standards, semantics (programming languages) and rules of engagement. The most appropriate option can be chosen for each case or situation.