Consumption views are created and edited through the Omni-Gen GUI. The views or documents produced by the GUI are stored in an Omni system table in the Omni repository. Updating a currently deployed bundle will create the tables associated with completed Consumption View documents or ODS’s. Once created, the tables can be populated by a work order generated via a REST endpoint via the Omni Server and deployed with a Swagger call. The project bundle and IDS must be active to view an ODS. A completed consumption view produces a set of database tables in the designated consumption data source file when the user deploys the associated bundle.