|
|
|
|
|  | 
Other Concepts Links:
Change Control, in the context of a Business Intelligence Production deployment, is the practice of making deliberate changes to a BI deployment instance, and communicating/documenting those changes in terms of files, database metadata, and context. In order for Change Control to be successfully implemented, two things are required: 1) the Metadata and Documentation must be accurate and up to date(See Metadata Manager Overview); and 2) There must be a strict Change Control process in place, with the means to record and communicate the changes at hand. See BI Manager Overview.
Roles and Responsibilities
Please note that one person can take multiple roles.
Requestor: Person making the request. Could be a user, manager, consultant, or anyone else in the IT department.
Change Control Manager: Person who is responsible for prioritizing requests and managing the process.
Developer: Person who is responsible for carrying out the request, either by himself/herself, or through others (DBA, etc.). This includes making the change in development, QA in development, and migrating objects into Production. The developer is also responsible for maintaining the changes in Documentation.
Help Desk: Person and/or software application that collects Requests, and provides reports on the status and priority of those Requests.
The Process
1. A Requestor initiates a request. It is typically called into a central place where it is logged. Each request should have a stated business reason.
2. Regular meetings should be held by the Change Control Manager and the Developer(s) to discuss the active requests at hand. Requests should be reevaluated on a regular basis.
3. The Help Desk not only fields the call, but also follows up with the user, with the status of the request.
4. After approval, developers make the code changes in a test environment, test, and implement changes in production. There should be some form of control reporting to assure that the change produced the desired result.
5. Developer(s) communicate these changes to the Help Desk.
6. The Help Desk contacts the Requestor, and follows up to make sure that the change was done accurately and as expected.
7. After Acknowledgement, the Request’s status is updated, and the Metadata is updated. (See Metadata Management).
Note: BI Manager is designed to facilitate the Change Control Procedure detailed above. See BI Manager.
|
|
|
 |
| Search
SNCL |
|
|
|
| Success
Stories |
| Time Warner Cable –
The Marketing Department needed a visual breakdown of demographics and penetration across the geographic area of NYC by zip code and census tract. |
|
Harry Fox – wanted to create an automated procedure that would allow b-to-b companies to run IWR reports pertaining to the status of their business.
|
|
| NYC Board of Education – needed to provide vital educational statistics on students, test scores, demographics, salaried positions, and teacher certifications to its superintendants over a Web-based interface. |
|
| Orix – A leasing company for trucks and construction equipment needed to consolidate its lease portfolio across its decentralized subsidiaries, and provide mission critical Risk Management reporting. |
|
|
More Success Stories
|
|
|
|
Success Stories by Company
|
|
|
|
|
|
