Classic BPM creates a package that contains various generated assets associated with a model. For example, the subscription triggers, transition triggers, and wrapper services are generated into various folders in this model package. A classic BPM model is dependent on this package for these various assets and needs to be deployed along with the classic model.

The Dynamic Business Orchestrator does not have a requirement for a model package, which is one less dependency during deployment. Classic BPM model generates wrapper services in the model package, while a Dynamic Business Orchestrator stores mapping internally in the model. Classic BPM model generates triggers in the model package, while Dynamic Business Orchestrator automatically creates all necessary triggers for all model-versions in a single package known as WmDBOAssets.