A Presentation on Business Intelligence

صفحه 1:
Welcome A Presentation on Business Intelligence June 10% 2003 by Paul Balacky & Richard Fayers THOROGOOD Get the full picture 

صفحه 2:
Topics مه سوت یه ‎Oharwtersios of‏ © * Desk loves 

صفحه 3:
Introductions - Thorogood Associates Ltd " Established (OO? us Iedepeudeu! Dusicess oteliqeus Gpevinists " @S people Oe oe loved it Loadou, Wigh Oyoowbe, Oouckester ocd rivets DCO Oirvsvht Gold OrriPied Patuer Por Dusicess Teteligeure (S pews ‏نموه‎ ta the opphcaivd oP Busicess: Aetetigeure/OLOR tecurlodies Oe parteer wits key players ta the sarket 

صفحه 4:
Chorunteristivs vP 1 

صفحه 5:
Business Intelligence © Dke ter Dustaess ‏تناها‎ (B11) is retatively ce but the itis ‏صجمم رود‎ wits a rocce of uppicaizes thot hove ‏عونا لتحم مجصطا‎ yeas; — Osvivn supper syste ws = Cxenuive IePorwaioa Opstews — Oke Badlicd Provessiay (8.0 Codd eat) 90's) or wale ‎wodelicny‏ سود ‎" his the powwersivg oP dota tote fePorevaticg ft suck a Lay teat the: busteuess is uble to cose the ‏لو ای نت یب و واه‎ ‏نت‎ ‎2 ‎ 

صفحه 6:
ke 1 ‏عسر6‎ Qustuess 4htelliqe sce 

صفحه 7:
BI Questions * Dbet oped? — Oko were our totd oder the covet? * Oku's hoppeins? = Ore pur ole yore up ‏تاره لا رنب‎ * Oh? — Ohy kwe des your dawa? "ket wal happen? = Porecwtay & Oka P Dodo "ket do 1 versa to hoppers? = Phrratery & ‏یه(‎ Gowrve: ill Dcker, Dicrovolt 

صفحه 8:
Where is Business Intelligence applied? Operctiocd PP ivieay Custower Iateractioa = ERE Reporicay * Gale ‏له‎ ‎۱ ۶ ‏سس و‎ 0 0 ‏میسن « امه«‎ 0 * 060 ‏ماده‎ ‎« Ooiviy Based Coste * نوومم ‏با‎ )من * سوه رطق « ‎"legen‏ 

صفحه 9:
OLTP v OLAP " OLTOC systews wodel provesses * OLOP Pooses ve culput ced user ‏جاع رات لت رمتسم‎ require weds - Data warehouses support business decisions by collecting, consolidating, and organizing data for reporting and analysis with tools such as online analytical processing (OLAP) and data mining. (OicroseFt) = OLOC stl requires ‏موه امه وه و‎ 

صفحه 10:
Business Intelligence Software ۰ otexgratica oP — OLOP ‏اوه لین‎ — ‏رسمه عادو المع‎ - )1( ‏نكصاصكادها جاع‎ " ‏مامت ها الاو‎ «۶ ‏عصصا اجه ما رانا‎ views "Deb deploywent 

صفحه 11:
Major BI\OLAP Vendors Orwrte ©: OLOP GHP CO Dierveokt GAL Gerver COOO & Ouse Gervices Wyperion Bssbose\ 10M Oiorvstrotecpy Cocos usicess Objevts 

صفحه 12:
State of BI at the present time " Robust, scdeuble, web deployable 01 tecurlogies are avilable "robles ure thely to he to dota cowplexiy, process ued people ® Guowesshul topleswwectaicad dewords very close Wworktey beter the bustaess wed the spstesw providers ® Chovsiey products ip us kad as ever - Dhere's w suck ftog os 0 weed Ped ste (OL@P, Query & Reporte, RDOOG, CPL, Oaks Dieses) — CRE veadors oe ofPeriay 1 

صفحه 13:
The BI market has been turned upside down in the last 4 years Oicroscht hus eutered the warket wits drocvatic ieopact Orde kos lost seocvectice ke produnts best uble to works wis DirrosvPt's phiPoren were ‏ره ور 6 نصا‎ 

صفحه 14:
1 ia @vtion 

صفحه 15:


صفحه 16:
How Many Matches Now? 

صفحه 17:
Concept Ola Cube or Pivot 03 1 Date - May 2003 Table Region - South East [Measure - Sales, ‎Crt eet is Day DOT‏ سا فد سل اس( امه تساه ‎ 

صفحه 18:


صفحه 19:
Oesina Cousiderctiivas 

صفحه 20:
Things to get right at design stage " Goope of projevt = eter tp phase projert tro by berry * ‏مایق‎ ‎= Ounership wikia he (BO oad dear yoo "Over Pore ‎expecttions becowes very Report‏ و اه موم( ‎ 

صفحه 21:
Things to get right at design stage " Gourve dota = Ov we kwe worse? = OP ea ckta fa deparde svurces cud oot ‏هجو‎ = Is tthe save level ‏مد وی‎ way be Pormuktied of a higher ‏اجه مج عمط مه‎ hott ip sourced ot - Proves = Aha ced when does the dota cet hi the Darker? = Oko level oP cdot cermin & ‏اج سا رت متس‎ = Oke & resp? 

صفحه 22:
Things to get right at design stage " Gourve dota = Ore we obey watch cuiputs tp fap = Dergtery cod cvaichiay of dota surrey = Requirewed ‏تاد ای موه ول بط وی و‎ ‏قبس اسمس ممق سق‎ = Wierachy woveweds over ‏صما‎ ‎= he weed tp restate or retaa historic view? - Divetoess oF det = Data ‏اس‎ = ALodhary oF ‏مت‎ valves oad ‏اما‎ 

صفحه 23:
Things to get right at design stage "Cee pou deliver the werl/bustaess requineweuts wits the tovls/shike ‏لاور‎ ‎= Gone thing thot look easy oe sieves ot - ‏اه مت‎ ‏و‎ hot de wot spew Roportadt to the developer ane ‏و ام‎ ‏هط‎ ‎— Porat = ‏و۳‎ ‎— Gore thro ull be stow becouse they are slow — Oven expectations 3 ها ملس - 

صفحه 24:
Things to get right at design stage عنصرامی) جر ‎Reporte‏ ® ای رون ونا توي جنا حص رودن ری — ‎OF Perec tools‏ — ‎OPPereat upproak‏ — ‎OF Perea cudiewe‏ — 

صفحه 25:
BI Design Parameters " Oubes = ‏ای(‎ of pubes — possibly dePiord by bustaess Pucctizs or seruriy = Deacber of dkveusions per cube, shared or private = Portions 0 0 00 speeds (cube processi iver) اجه امس جووو - وله امن - اه سوه م6 

صفحه 26:
BI Design Parameters میم ۰ اس راما راو عم - ماما هجو( - كيين ایس ان ازیو سل (وسحاهه) ليس ها له و تیا لووسم ‎Dewber‏ — اما وی نت لاه ,عاصطا اه طمی() - ‎Werachy chenes wer Re‏ = = Reportey ews, srecries 

صفحه 27:
BI Design Parameters ۶ Dive Onveusica — Olercaive ttre Keracchies — cdeadar, Prrcactal = 08 pericd peor — weeks wb period — Oucober oP levels 

صفحه 28:
BI Design Parameters " Diveboess oP Dott - Red-ice - Orxt day — Oveky reviews (possible weekend ty process) — Dowty reviews (woot cod provessicry) 

صفحه 29:
BI Design Parameters عسصی() " موه و ام( = سس سوسس ةا لصنق يت حاقد نا وس #القاق له وه و( ‎Ovstow rohups‏ — ‎Ove ocdiive cota‏ = ‎Previsioa, Porat‏ — 

صفحه 30:
BI Design Parameters ® Oddevloted Deusures = ‏هه و و‎ = GOL vs ‏هی )زان‎ (pre cube build us post cube bud) = Coleutated cells = ‏لو وی و و(‎ to derive the ‏ومسحجدب لتحا‎ = Cureuy exchanp rites = Dstrbated processkny opporinities (server calos ve lect side ‏(صصلت‎ ‎= @ppheatira oF DOX 

صفحه 31:
BI Design Parameters © Orite-Dack ‏نوی‎ ‎- locus \bredk buck requeweus, level oP dota eur) = Oud oy - ‏مهن‎ 

صفحه 32:
BI Design Parameters * Output requinswecis = Over report dePiiioes — Porat, youl, ‏مت‎ ‎- Dypes oP udhor ‏وه‎ ‎- ‏عو)‎ ‎- Requreweus Por priced pupu = Quouittive ve Qualiaive data pupal = @rowser\OPPie delvery — OLO® database dribikrougk to GGL Gerver — Ducober oP were — ‏موی و‎ — Geowriy 

صفحه 33:
BI Design Parameters " Gevurity — Oube — Oxvewiod — Cell evel 

صفحه 34:
To consider when building BI applications.. "| Osers coo Pull to ‏ام‎ how wurk foPo they requested — beads tr poor perceived perPorwouwe " Covoplerdiy due to horge cucber of dioeusives — users doo’ ‏امه طلست سا لحو اس لسن‎ ۱ © @erhornwowe vs storage — pvasider DOLOP/LOL@OP/ROLOO, oertke Ay versus pre-aggrequied tote 

صفحه 35:
There is a strong case for a BI strategy عنامي ‎O14 cea dive siqaiPiccat‏ روا عازن مه زرا " - crosses Pucntiocal bourdaries — presses prysmivaiocal bouedaries: تلاصا روم مرو موه امن ‎prove‏ لجم) میت مامت فاص ‎Davtca 01 upplicives way‏ " ‎1's wort) ...‏ ‎way of‏ ۱ ‎dehvertoy Kigh retuce to the short ters without wvojor upheaval‏ 

صفحه 36:
Thank you THOROGOOD Get the full picture 

A Presentation on Business Intelligence June 10th 2003 by Paul Balacky & Richard Fayers Topics  Introductions  Characteristics of a Business Intelligence Application  Demonstration  Design Issues Introductions – Thorogood Associates Ltd  Established 1987 as Independent Business Intelligence Specialists  45 people  We are located in London, High Wycombe, Manchester and Princeton USA  Microsoft Gold Certified Partner for Business Intelligence  15 years experience in the application of Business Intelligence/OLAP technologies  We partner with key players in the market www.thorogood.com Characteristics of BI Business Intelligence  The term Business Intelligence (BI) is relatively new but the it is synonymous with a range of applications that have been around for years; – Decision support systems – Executive Information Systems – On-line Analytical Processing (E.F Codd early 90’s) or multidimensional modelling  It is the conversion of data into information in such a way that the business is able to analyse the information to gain insight and take action The BI Cycle Business Int el l ig ence MEASUREMENT Source: Business Intelligence, Elizabeth Vitt ACTION ANAL YSIS INSIGHT BI Questions  What happened? – What were our total sales this month?  What’s happening? –  Are our sales going up or down, trend analysis Why? – Why have sales gone down?  What will happen? – Forecasting & What If Analysis  What do I want to happen? – Planning & Targets Source: Bill Baker, Microsoft Where is Business Intelligence applied? Operational Efficiency Customer Interaction  ERP Reporting  KPI Tracking  Sales Analysis  Sales Forecasting  Product Profitability  Risk Management  Segmentation  Cross-selling  Balanced Scorecard  Activity Based Costing  CRM Analytics  Campaign Planning  Global Sourcing  Logistics  Customer Profitability OLTP v OLAP  OLTP systems model processes  OLAP focuses on output and user reporting and analysis requirements – Data warehouses support business decisions by collecting, consolidating, and organizing data for reporting and analysis with tools such as online analytical processing (OLAP) and data mining. (Microsoft)  OLAP still requires a very formal approach Business Intelligence Software  Integration of – OLAP multi-dimensional technology – Relational database technology – Web technology  Scalability for warehousing  Flexibility, performance and business views  Web deployment Major BI\OLAP Vendors  Oracle 9i OLAP  SAP BW  Microsoft SQL Server 2000 & Analysis Services  Hyperion Essbase\IBM  Microstrategy  Cognos  Business Objects State of BI at the present time  Robust, scaleable, web deployable BI technologies are available  Problems are likely to lie in data complexity, process and people  Successful implementation demands very close working between the business and the system providers  Choosing products is as hard as ever – There’s no such thing as a green field site (OLAP, Query & Reporting, RDBMS, ETL, Data Mining) – ERP vendors are offering BI The BI market has been turned upside down in the last 4 years  Microsoft has entered the market with dramatic impact  Oracle has lost momentum  The products best able to work with Microsoft’s platform were unknown 4 years ago BI in Action How Many Matches? How Many Matches Now? Concept of a Cube or Pivot Table Product – Chocolate Date – May 2003 Region – South East Measure – Sales Date Region Product How much Chocolate did we sell in the South East in May 2003? Front-End Tools Client Server Web Client Server Web SQL MDX SQL Server 2000 Relational Database Analysis Services DTS Text Excel Informix Access Sybase SQL Server Oracle Design Considerations Things to get right at design stage  Scope of project – Better to phase project than big bang  Business unit buy-in – Ownership within the BU and clear goals  User Focus – Management of user expectations becomes very important Things to get right at design stage  Source data – Do we have access? – Often data in disparate sources and not always accessible – Is it at the same level – Budget data may be formulated at a higher summary level than actual data is sourced at – Process – How and when does the data get into the Warehouse? – What level of data cleansing & transformation will be required – Who is responsible? Things to get right at design stage  Source data – Are we able to match outputs to inputs – Merging and matching of data sources – Requirement for company wide data standards and definitions – Are there common keys? – Hierarchy movements over time – the need to restate or retain historic view? – Timeliness of data – Data volumes – Handling of missing values and relationships Things to get right at design stage  Can you deliver the user/business requirements with the tools/skills available – Some things that look easy are sometimes not – Dimension changes – Things that do not seem important to the developer are important to the business user – Format – Performance – Some things will be slow because they are slow – Manage expectations – Product limitations Things to get right at design stage  Reporting vs Analysis – They may seem the same but they are not – Different tools – Different approach – Different audience BI Design Parameters  Cubes – Number of cubes – possibly defined by business functions or security – Number of dimensions per cube, shared or private – Partitions relating to data volumes and update speeds (cube processing times) – Virtual cubes – cross functional analysis – Data storage options BI Design Parameters  Dimensions – Types of hierarchies - multiple, ragged, parent\child, balanced\ unbalanced – Size, number of members – Member properties and how these could be used (attributes) – Number of levels, children within each level – Hierarchy changes over time – Reporting views, scenarios BI Design Parameters  Time Dimension – Alternative time hierarchies – calendar, financial – 13 period year – weeks to period – Number of levels BI Design Parameters  Timeliness of Data – Real-time – Next day – Weekly reviews (possible weekend to process) – Monthly reviews (month end processing) BI Design Parameters  Measures – Methods of aggregation – Data entering cubes at differing levels required for comparisons – Custom rollups – Non additive data – Precision, format BI Design Parameters  Calculated Measures – – – – – – – Time series calculations SQL vs OLAP calculations (pre cube build vs post cube build) Calculated cells Nature of equations required to derive the calculated measures Currency exchange rates Distributed processing opportunities (server calcs vs client side calcs) Application of MDX BI Design Parameters  Write-Back requirements – Allocations\break back requirements, level of data entry – Audit log – Validation BI Design Parameters  Output requirements – – – – – – – – – – User report definitions – format, layout, precision Types of adhoc analysis Actions Requirements for printed output Quantitative vs Qualitative data output Browser\Office delivery OLAP database drill-through to SQL Server Number of users Report maintainability Security BI Design Parameters  Security – Cube – Dimension – Cell level To consider when building BI applications..  Users can fail to realise how much info they requested – leads to poor perceived performance  Complexity due to a large number of dimensions – users don’t understand the model/numbers  Hard to test because they are conceptually complex  Performance vs storage – consider MOLAP/HOLAP/ROLAP, on-the fly versus pre-aggregated data There is a strong case for a BI strategy  BI can drive significant value  It is an agile technology – crosses functional boundaries – crosses organisational boundaries – Implementation can involve many stakeholders  Tactical BI applications may deliver significant value (and prove BI’s worth) …  In a post boom business climate, BI offers a pragmatic way of delivering high return in the short term without major upheaval