Depicts a fictional corporation to describe Oracle Business Intelligence initiative examples.
Eden Corporation (a fictional company) recently purchased Oracle Business Intelligence. They have two divisions that are licensed and plan to use the product.
Because of this, the company has two separate initiatives:
Initiative S: The Sales Division wants to use Oracle Business Intelligence for dashboarding and analysis of revenue versus plan. They want to deploy an initial phase to production quickly to meet an immediate need. Then, they want to roll out more functionality in Phases II and III. Initiative S is large enough that they will have two developers working on it.
Initiative H: The Human Resources Division (HR) needs to do dashboarding and analysis of HR data. Initiative H is a smaller initiative, so it will have only one developer. They plan to deliver their application to production between Initiative S Phases II and III.
Note that the Sales developers and the HR developers are not allowed to see each others' data or metadata. The metadata administrator is the only person who has security privileges for all the metadata.
As in all organizations, there will also be a steady stream of urgent requests and occasional bugs from production. The developers will need to deliver fixes for these within days, even though the longer-term initiatives S and H are in development at the same time.
About the Technical Team Roles and Responsibilities
Eden Corporation has staffed the team as follows:
Adam Straight - MUD Administrator
Sally Andre - Developer for Sales Division, Revenue project
Scott Baker - Developer for Sales Division, Quota project
Helen Rowe - Developer for HR Division
About the Eden Corporation Development Phases
Eden Corporation plans to deploy RPDs to production based on the following timeline:
January - Sales Phase I (projects Revenue and Quota)
February - Sales Phase II (add project Target, extend projects Revenue and Quota)
March - HR (one project used)
April - Sales Phase III (extend all three projects)
About the Eden Corporation Topology
Eden Corporation plans to use the following systems for their multiuser development environment:
MUD Administrator - NT computer with a share
Sally Andre - NT computer for Administration Tool client, and Linux computer to run the Oracle Business Intelligence stack
Scott Baker - high-powered NT computer
Helen Rowe - either of the above
Test - Linux computer
Production - Clustered Linux computers
About the Repository Architecture
Because of Eden Corporation's business structure and initiatives, they need to have two independent semantic models in their repository: one for Sales and one for HR. Each of these models can have multiple projects.
Planning the Repository Structure
Eden Corporation knows that it is important to plan the structure of their repository file so that it will be able to support the multiuser development needs of their organization. They assigned owners to major objects, so the developers know who to go to when conflicts arise, and which objects they should not modify on their own.
Tip:
When hosting multiple independent semantic models, be sure to itemize the names of top-level objects to prevent duplicate names.
The tables show the high-level repository objects in main.rpd for both Initiative S and Initiative H, mapped to projects and owners. Note that Adam is the overall owner of both Initiative S and Initiative H.
| Object Type | Object | Owner | ProjRevenue | ProjQuota | ProjTarget |
|---|---|---|---|---|---|
|
physical database |
Sample App Data |
Sally |
Yes |
Yes |
Yes |
|
business model |
Sales |
Sally |
n/a |
n/a |
n/a |
|
logical fact table 1 |
F10 Billed Rev |
Sally |
Yes |
Yes |
No |
|
logical fact table 2 |
F30 Facts Targets |
Scott |
No |
No |
Yes |
|
logical fact table 3 |
F50 Facts Quotas |
Scott |
No |
Yes |
No |
|
logical dimension |
(various) |
Sally |
Yes |
Yes |
Yes |
|
subject area (1) |
Sales Quota |
Scott |
No |
Yes |
No |
|
subject area (2) |
Sales Revenue |
Sally |
Yes |
No |
No |
|
subject area (3) |
Sales Target |
Scott |
No |
No |
Yes |
|
variable |
S_Last_Load |
Sally |
Yes |
Yes |
Yes |
|
initialization block |
S_Last_Load |
Sally |
Yes |
Yes |
Yes |
|
application role (1) |
Sales Management |
Sally |
Yes |
Yes |
Yes |
|
application role (2) |
Sales Rep |
Sally |
Yes |
Yes |
Yes |
| Object Type | Object | Owner | ProjHR |
|---|---|---|---|
|
physical database |
Human Resources Data |
Helen |
Yes |
|
business model |
HR |
Helen |
n/a |
|
logical fact table (1) |
Payroll Facts |
Helen |
Yes |
|
logical fact table (2) |
Medical Ins Facts |
Helen |
Yes |
|
logical dimension |
(various) |
Helen |
Yes |
|
subject area (1) |
HR Payroll |
Helen |
Yes |
|
subject area (2) |
HR Medical |
Helen |
Yes |
|
variable |
H_Last_Load |
Helen |
Yes |
|
initialization block |
H_Last_Load |
Helen |
Yes |
|
application role (1) |
HR Management |
Helen |
Yes |
|
application role (2) |
HR Rep |
Helen |
Yes |