DW Methodology Summary

THE FINANCIAL REPORTING AUTHORITY WWW.SQLPOWER.CA

The number one roadblock to successful XBRL Adoption is the need for filers to retool their back-end systems to generate XBRL filings that are compatible with their Regulators evolving Taxonomy(s). Regulatory organizations that have mandated XBRL in their jurisdiction without providing an XBRL Data Collection/Conversion facility have significantly burdened their filers, resulting in lower compliance and resistance to the XBRL mandate.

XBRL Forms removes the financial and technological burden from the filers and provides them with an easy-to-use, web-based front end for users to verify financial information prior to submission. With the taxonomy identified, the XBRL Forms application dynamically renders a set of taxonomy-driven returns and schedules to facilitate the data capture of high-quality financial information. XBRL Forms validates each filing in real time against the taxonomy and certifies the return, generating the required XBRL instance document.

XBRL Forms also allows regulatory organization the flexibility to change their Data collection requirements, validation rules and reporting frequency, in very short order - without the need to provide filers with a significant lead-time for retooling.

With XBRL Forms, Regulators move beyond compliance by effectively removing the burden and complexity of generating XBRL filings from the filing organization, thus enabling immediate adoption of the new filing standard.

Zero-Footprint SoftwareXBRL Forms provides a Zero-Footprint thin-client facility for data entry of financial information. This means zero software downloads are required - which translates into maximum compliance and maximum adoption. Zero-Footprint offers the highest levels of automated filing to Regulators and their regulated subscriber entities: a subscriber simply logs in via the internet and submits its business information or corporate financial filings via a secure, intuitive submission form dynamically rendered by from the required XBRL taxonomy.

XBRL Forms:Thin-Client Data Collection & Validation Facility

Detailed Functionality Web based (Java) Integrates with XBRL Power EAS: User access control Reporting management Enablement of resubmissions View past filings Create new filings Import and output/download XBRL

Instance Documents Print (pdf) Instance Documents XBRL Taxonomy Metadata drives: Data Domain Validation Online Help Admin Guide Validation (formulas) Interactive Final Calculations Multilingual

Other Systems

Work in Progress

Taxonomy

Import

Save & Load

Validation

Submission

XBRL Filed Data

XBRL Forms

COMMERCIALLY AVAILABLE OFF-THE-SHELF (COTS) SOFTWARE

Features Ensures accuracy - interactive

real-time validation against the taxonomy, triggering all required calculations, formulas, and rules

Easily deployed on all standard browsers, integrates tightly with the superVision Suite portal

Stores works in progress for future revisions

Allows for final Validation/Certification of returns prior to submission

Generates XBRL Instance Documents for submission

Imports XBRL instance documents for viewing, modification and re-submission

Provides full Multilingual support

Validation & CertificationReturns and schedules are automatically rendered based on information embedded in the taxonomy. Accurate submissions are ensured through extensive real-time validation as well as final certification.

Interactive ValidationInteractive validation occurs on a field by field basis: as the user enters data, they are alerted to fatal errors or warnings defined within the taxonomy.

Final CertificationFinal certification occurs when the user is ready to submit or output the filing: all rules in the taxonomy are processed and a validation screen presents details on any and all fatal errors or warnings. Fatal errors will prevent a filing from being submitted, warnings will not.

Validation errors and warnings can be extended in the taxonomy to virtually cover an infinite number of business rules through the use of XBRL Formulas.

SQL POWER SUPERVISION SUITEBUSINESS INTELLIGENCE

Data Warehousing Methodology OvErvIEw


2


SUMMArY

SQL Power Data Warehousing Methodology has evolved with our Data Warehousing Consulting practice and has been validated and confirmed by our Clients and Consultants on many successful BI Solution implementations.

Our Methodology contains activities grouped in seven major phases:

1. BI VisionBI Strategic Planning activities focus on the development of a Business Case for a BI Solution; Organization of a BI Steering Committee; Definition of the Required BI Infrastructure and creation of the BI Evolution Roadmap.

2. ScopeScoping activities relate to the initiation of a BI project and include the development of the Project Charter, Business Assessment, Requirement Gathering, Project Planning and creation of the Project Team.

3. ArchitectThis phase includes Analysis and Design activities to create the DW Architecture, conduct Technology and Data Quality Assessments, design Data Models, Metadata Repository, ETL Application and BI Reports.

4. BuildThis is the code construction phase during which all physical Data Models, ETL Code and BI Reports are constructed.

5. TestTesting activities focus on Unit testing, System Integration Testing, User Training and User Acceptance Testing. Testing includes quality checking of all ETL code and BI reports constructed in the Build phase.

6. DeployThe solution deployment planning rollout and Production Rollout execution activities include User Training and Production deployment of BI databases, Metadata Repository, ETL code and BI Report.

7. SupportPost-production implementation activities focus on BI application Monitoring and Support, including monitoring of Data Load Logs, Data Volumes, Data Auditing, Report Usage frequencies and Change Tracking.

THE FINANCIAL REPORTING AUTHORITY WWW.SQLPOWER.CATHE FINANCIAL REPORTING AUTHORITY WWW.SQLPOWER.CA

3

The effective execution of a successful BI project requires that a proper project management approach is used. Thus there is an additional Project Management phase that applies equally to any activities on a BI project.

The shortest time to delivery of the BI Solution is guaranteed by high quality deliverables produced in each development phase, as shown on the diagram below:

Figure 1: SQL Power Data Warehousing Methodology & Deliverables

5. Test

System Integration Test ResultsTested BI Reports & CubesLoad Test ResultsQuality Checking ResultsUser Acceptance ResultsTrained Users

3. Architect

Technology AssessmentMetadata Repository DW Design Specifications Data Quality AssessmentSource Data ModelsDW Data ModelsETL Application ArchitectureReporting Prototype

8. Project Management

Project Initiation & PlanningExecution & ControlProgress Monitoring & ReportingProject Closing

7. Support

Volume & Usage Monitoring Report Change Management Report

6. Deploy

Physical Data WarehouseETL ApplicationBI Reports & CubesAd-hoc Reporting EnvironmentMetadata Repository

4. Build

DW Database SchemaUnit Tested ETL CodeBI Reports & CubesSystem Integration Test Plan User Acceptance Test PlanCapacity & Support Plan

2. Scope

Project CharterBusiness AssessmentProject TeamBI RequirementsProject Schedule

1. BI Vision

BI Readiness AssessmentBI Business CaseRequired InfrastructureBI Steering CommitteeBI Evolution Roadmap


4


1. BI vISION

1.1. DescriptionThe BI Vision phase defines the BI strategy for the company. It addresses the business needs and defines the business case for a Business Intelligence solution. Before the BI Steering Committee is organized and the required infrastructure is put in place, a study must be conducted to determine the readiness of the business for a BI solution, so that business executives are in a position to sponsor the BI vision. A very important outcome of this phase is the BI Evolution Roadmap.

1.2. ObjectivesThe objectives of this phase include:

Establishing business goals that will be met by implementing the BI solution

Obtaining buy-in from the business executives that sponsor the BI vision

Assessing the readiness of the organization for the BI solution

Developing the BI business case Organizing the BI Steering Committee Creating the BI evolution roadmap

1.3. InputsThe inputs for this phase include:

Business strategy and business objectives that will be met by a BI solution

Business executives criteria for sponsoring a BI vision

Existing and future documented information reporting requirements

Results of previous business assessments Business case criteria Existing infrastructure Current state of information reporting

1.4. Activities/TasksThe activities of this phase include:

1. Conducting BI Readiness Assessment 2. Develop Business Case 3. Document Infrastructure Requirements 4. Conduct BI Architecture Review 5. Establish BI Steering Committee 6. Develop BI Evolution Roadmap

1.5. DeliverablesThe deliverables of this phase include:

BI Readiness Assessment Business Case justification Required Infrastructure including: - People - Processes - Systems and Technology - Architecture BI Evolution Roadmap including: - BI Matrix - High Level Project Scope - High Level Timelines and Estimates

BI Vision deliverables are delivered in the BI Strategic Plan, a document that outlines the business need for a BI Solution. This strategic document must be signed by the business executive who will be the sponsor for the BI initiative.


5

2. SCOPE

2.1. DescriptionThe second phase of the SQL Power Methodology defines the scope and the plan of each of the BI projects outlined in the BI Evolution Roadmap developed in the BI Vision phase. The projects scope, plan, quality plan, required resources, etc. are documented in the Project Charter that must be signed off by the BI Steering Committee.

2.2. ObjectivesThe objectives of this phase include:

Define scope and plan for each identified BI project Develop Project Charter Gather and document business requirements Assess technical state of required infrastructure Organize project team Compile and publish project schedule Develop and obtain sign off on the Project Charter


BI Evolution Roadmap BI Matrix Business readiness assessment Technical assessment Resource availability


1. Review BI Evolution Roadmap and high level project scope

2. Develop Project Charter 3. Gather Business Requirements 4. Develop Quality Plan 5. Conduct Technology Assessment 6. Develop Project Schedule (timeline, resources) 7. Obtain Sign-off of the Project Charter


Approved Project Charter and Project Schedule Business Requirements Document Quality Plan Technology Assessment Change Management Plan Review of the required infrastructure Recommendations for new technology infrastructure Allocated project team Allocated resources

The Scope phase will define in detail each of the BI projects that have been identified. It defines the scope, timelines and resources for the new project.


6


3. ArCHITECT

3.1. DescriptionThe third phase of the SQL Power Methodology designs the intended BI solution. During this phase the architecture of the solution is finalized and all the necessary logical pieces (such as: Logical Data Models, Metadata Repository, ETL Application Architecture, and Design Document) are put in place. The plan for system integration testing is developed, and Capacity and Support Plans are also drafted in this phase. Originating systems and source data quality are analyzed and detailed, and ETL interfaces (including source-to-target mapping) are designed and documented.

In some cases, a reporting prototype can be created to verify business requirements with the users.

3.2. ObjectivesThe objectives of this phase include: Perform detailed analysis of the source data Define technical architecture requirements Assess data quality Design target data warehouse architecture Define and design ETL interfaces Define test plan Define infrastructure capacity plan Define data warehouse support plan


Project Charter Technology assessment Source data Business requirements Required resources

The Architect phase will produce the design of the intended BI solution, including all the necessary specifications to start building the actual system.


1. Review Technical Architecture 2. Perform Detailed Analysis 3. Conduct Data Quality Assessment 4. Perform Detailed Design 4.1. Data Modeling (logical, physical) 4.2. ETL Interface Design 4.3. BI Reporting Design 5. Build BI Prototype (optional) 6. Review and refine project plan 7. Negotiate Interface Agreements 8. Formulate Test Plan 9. Prepare Capacity Plan 10. Create Support Plan


Logical and physical data models for: - Data Audit Repository - Metadata Repository Design Document of the ETL/Interface Application

design, including: - Source-To-Target mappings - ETL Modules/Procedures design - ETL Process Dependencies and

Schedule design Test Plan Capacity Plan Support Plan


7

4. BUILD

4.1. DescriptionThe fourth phase of the SQL Power Methodology develops the intended BI solution. During this phase the physical database and the ETL code are developed and unit tested. Data migration and conversion plans are developed. User Acceptance testing is planned in this phase. In cases where a reporting prototype was created, it can be reviewed and refined based on user feedback.

4.2. ObjectivesThe objectives of this phase include: Develop physical database Develop ETL applications Unit test ETL processes Develop and review BI prototype Plan data migration and conversion to production


Project Charter Logical and physical data models for: - Data Audit Repository - Metadata Repository Design Document of the ETL/Interface Application

design, including: - Source-To-Target mappings - ETL Modules/Procedures design - ETL Process Dependencies and Schedule design Test Plan Required resources


1. Review Design Documents 2. Create Physical Database 3. Develop ETL module 4. Conduct code reviews 5. Develop Production Migration Plan 6. Develop User Acceptance Plan


DDL Scripts for Physical Database Implementation Constructed and unit tested ETL modules Constructed and unit tested BI Reports Constructed and unit tested ETL load scheduling

procedures User Acceptance Test pan

The Build phase will build the BI solution and will prepare it for the User Acceptance testing.


8


5. TEST

5.1. DescriptionThe fifth phase of the SQL Power Methodology tests the developed BI solution. During this phase the ETL code is tested for performance. The whole system is tested for integration and data flow. Users test the system for acceptance based on the User Acceptance Test Plan developed in the previous phase. System administrators may be required to maintain the system. Users are trained in the use of the new system.

5.2. ObjectivesThe objectives of this phase include: Verify that the BI solution functions as expected Conduct Integration (System) Testing Conduct Performance Testing Conduct Regression Testing Perform User Acceptance Testing Obtain user approval Train administrators Train users


Project Charter Business Requirements Design Document Developed system System Integration Test Plan User Acceptance Test Plan Required resources


1. Review results of unit testing 2. Conduct System Integration Testing 3. Conduct Performance Tests 4. Train Users 5. Train Administrators 6. Conduct User Acceptance Testing


Test Results of: - Integration Testing - Performance Testing - Regression Testing Tested ETL programs & ETL application Test results & recommendations User Acceptance Approval Trained Administrators Trained Users

The Test phase will confirm that the developed BI solution conforms to the specified business requirements and will prepare the system for migration to production environment.


9

6. DEPLOY

6.1. DescriptionThe sixth phase of the SQL Power Methodology rolls out the developed BI solution to the production environment. During this phase, the tested system is migrated to production so that the users can start using it.

6.2. ObjectivesThe objectives of this phase include: Determine organizations deployment readiness Develop user documentation Train business users Rollout the solution into production environment


Tested System Trained Administrators Trained Users Migration Plan


1. Prepare system for migration 2. Rollout system to production 3. Publish user documentation 4. Develop system documentation 5. Monitor system migration


User Documentation Operations Manuals (Runbooks) Implementation Approval Document Packaged Project Documentation Production system

The Deploy phase will roll out the developed BI solution to the production environment and will make it available for everyday use.


10


7. SUPPOrT

7.1. DescriptionThe seventh phase of the SQL Power Methodology consists of the post-production implementation activities. The main activity here is the monitoring of the production BI system, including Data Auditing, Data Volume and Report Usage monitoring, as well as Data Load Logs (Journal) review. This phase also defines the Change Management processes that are required to incorporate any changes to the system.

7.2. ObjectivesThe objectives of this phase include: Ensure smooth running of the system Monitor system performance and take corrective

action, as required Establish orderly process to enable seamless

changes to the system


Fully functional production system Data Load Logs Data Volumes reports Report Usage reports System documentation


1. Monitor system operations and performance 2. Conduct data auditing 3. Support production system 4. Define and implement change management


Fully functioning Production system Data Volumes and Report Usage reports System status reports Change Management process Implemented changes

The Support phase is the ongoing monitoring of the BI system. It is intended to ensure that the system is functioning as expected. The duration of this phase will be determined by the needs of the users for the system.


11

8. PrOJECT MANAGEMENT

8.1. DescriptionProject Management is not a separate phase of the SQL Power Methodology, but rather an activity that takes place throughout any BI project, starting from scoping and planning to roll-out and production support. Project Management activities include the necessary steps to ensure that the project is properly scheduled, the required resources and infrastructure are available and that the project is implemented on time and on budget.

8.2. ObjectivesThe objectives of this phase include: Ensure proper project planning Oversee project execution at every phase Ensure project controls are adhered to Provide required project management reporting Identify and control project risks Ensure the project execution is on time and within

budget Monitor and manage user expectations Conduct project closing at the end of the project


Business requirements Approved Statement of Work (SOW) Infrastructure resources Human Resources Project Charter Timesheets Minutes of Project Status meetings


1. Analyze user requirements 2. Develop Project Charter (project schedule, risks and

expected outcomes) 3. Assign project team 4. Monitor project execution and quality of

deliverables 5. Prepare and submit Project Status reports 6. Address project issues and manage user

expectations 7. Manage project scope, initiate and manage changes 8. Obtain approval for project deliverables 9. Conduct project closing


Properly planned and executed project Satisfied users Satisfied project team High quality deliverables

The Project Management phase applies to all other phases of the BI project and is intended to properly plan, execute and control the project. This phase closely resembles the Project Management approach developed by PMI (Project Management Institute), as documented in the PMI PMBOK (Project Management Book of Knowledge - see www.pmi.org.) The use of productivity tools for project management, e.g. Microsoft Project 2007 is strongly encouraged.

ABOUT SQL POWER

Founded in 1988, and headquartered in Toronto Canada, SQL Power Group Inc. is a global application Software firm specializing in Business Intelligence and XBRL implementations. Since implementing the first Regulatory XBRL Solution in Canada in 2009, SQL Power has been at the forefront of XBRL software innovation - rolling out the worlds first fully-integrated XBRL data collection, return management and analytics solution designed specifically for regulators business users. Our consultants possess deep domain knowledge and strong practice expertise in XBRL, Data Integration and Analytics and will help de-risk any XBRL implementation.

LIVE DEMOS To learn more about SQL Power solutions, contact us today to schedule a live demonstration.

SQL Power Group Inc.

4950 Yonge St.

Suite 1900

Toronto, Ontario, Canada

M2N 6K1

TEL 416.221.4220

TOLL FREE 1.866.SQL.POWR

FAx 416.221.5898

EMAIL [email protected]

www.SQLPower.ca

DW Methodology Summary

Documents

Transcript of DW Methodology Summary