IAC 2024 - IA Fast Track to Search Focused AI Solutions
Data warehouse 101-fundamentals-
1. Enterprise Data Warehouse Fundamentals 101 KIDS Phase II Project Mojo Nwokoma Director , Enterprise Data Systems Architecture Office of Assessment & Information Services Oregon Department of Education 503-378-3600 x2242 [email_address]
7. KIDS Phase II Project District/ESD Server Deployment & Data Warehouse Integration Architecture Transaction System Transaction System Transaction System Transaction System Transaction System ODE (State) DW Physical & Virtual ODS = Operational Data Store DW = Data Warehouse ODS ODS ODS ODS ODS Hillsboro District DW Beaverton District DW Portland District DW Eugene District DW ESDs DW LEGENDS: KIDS Work = ODE Districts Record Exchange
8. Project Planning Methodology – “The How?” For the Project Team Step 1: Define the Work Breakdown Structure The first is to create a comprehensive Work Breakdown Structure (WBS). The WBS lists all the phases, activities and tasks required to undertake the project. Identify and describe each phase, activity and task required to complete the project successfully. Depict the order in which the tasks must be undertaken and identify any key internal and external project dependencies. Also list the critical project milestones, such as the completion of key project deliverables Step 2: Identify the Required Resources Having listed all of the tasks required to undertake the project, you now need to identify the generic resources required to complete each task. Examples of types of resource include: full-time and part-time staff, contractors, equipment and materials. For each resource type, identify the quantity required, the delivery dates and the project tasks in the WBS that the resource will be used to help complete. Step 3: Construct a Project Schedule To construct your schedule, you need to: List the phases, activities and tasks Sequence the phases, activities and tasks Add key internal and external dependencies Allocate relevant completion timeframes Add additional contingency to mitigate risk Assign resources required to complete tasks List critical delivery milestones Specify any assumptions and constraints
9.
10.
11. Recommended Model for Enterprise Data Warehouse System KIDS Phase 11 Project E-Portal Data Warehouse Operational Data Store ODS Transactional Database Educational Stakeholder Communication Benchmarking/Decision Support District & State Reporting Day to Day Operations PK-12 Data Model for Information Management (ODE & IBM Confidential) 10/20/05
Data Integration Layer – ODS: ODS is a non-queryable centralized staging areas for storing extracted, cleansed, and transformed data, and for gathering centralized metadata for implementing an Enterprise Data Mart Architecture (EDMA), eliminating the need for another non-queryable staging area called data warehouse. Needed is a dimensionally modeled data warehouse for enterprise DSS, prepared to provide the best in query response performance and to support the most advanced OLAP functionalities.
![Enterprise Data Warehouse Fundamentals 101 KIDS Phase II Project Mojo Nwokoma Director , Enterprise Data Systems Architecture Office of Assessment & Information Services Oregon Department of Education 503-378-3600 x2242 [email_address]](https://image.slidesharecdn.com/data-warehouse101-fundamentals-120114115112-phpapp02/85/Data-warehouse-101-fundamentals-1-320.jpg)
![What is Enterprise DW/BI Solutions ,[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)