OptimalBI Consulting Customer Process Flow

This flow is for OptimalBI customers who can’t follow the community process but with whom we are engaged enough to do extra for them. Our customer provides us their tested and working code as an archive (zip). We create a feature branch on origin. We un-archive...

Community Process Flow

The community contributor forks our origin to a new remote repository. The community contributor makes changes The community contributor issues a pull request to our origin. OptimalBI performs the code review and follows our internal processes (except the rebase as we...

Optimal’s Internal Process Flow

Install SourceTree. Clone the development branch of the origin repository. Create a feature branch. Perform the standard good practises: discuss the requirement with the requestor of the user story, agree to acceptance criteria, write down the design, review the...

Star Schema naming standards

The sections below describe our naming standards for Star Schema layers in the Optimal Data Engine. Whatever is on this web page is our current version.   Star Schema Design Principles If the data is not being manipulated then the column name should not...

Data Vault naming standards

The sections below describe our naming standards for Data Vault objects in the Optimal Data Engine. Whatever is on this web page is our current version.   Hub Tables Table Convention Example   Hub.h_<Entity_Name> Hub.h_Customer Attribute Attribute...