System Implementation Project Approach

Transcription

1 System Implementatin Prject Apprach Phase I Current State Analysis Gal: Dcument current state peratins and categrize current state prcedures and reprting assets as: Deliverables: Mandatry Internal Reprting Assets External Cmpliance Reprting Assets Redundant Reprting Assets Reprting Assets that require manual, pst-prductin transfrmatin Scheduled (Practive) Prcedures (Manual and Autmated) Unscheduled (Reactive) Prcedures (Manual and Autmated) Prcedures that can nt be executed due t insufficient reprting Individual prcedures that culd / shuld be cmbined int a single wrk stream Fitness-Fr-Use Dcument ( FFU ) Defines what the future state system shuld d fr end users and hw end users will interact with the system. This is a nn-technical dcument which details the pint and purpse f the future state infrmatin reprting and Business Intelligence system Phase II Future State Detail Definitin Gal: Deliverables: Define details f future-state reprting services (supply) and end-user needs (demand) Definitin f required reprting assets (Reprts, Dashbards, Screcards, Alerts, Warnings) Definitin f desktp user ad-hc reprting requirements and pprtunities Narrative detailing infrmatin reprting system infrastructure and supprt mdel fr same Narrative detailing Gvernance Mdel, Data Steward rle and Security Prtcls Definitin f Data Quality Measure and Assessment prcedures Technical Specificatin Dcument ( Tech Spec ) Technical dcument which Includes the architecture and prfile f the data surce(s), ETL requirements t ensure high-quality data at the surce(s), user interface requirements, security and firewall cnfiguratin and test case scenaris Apprved, detailed Prject Timeline

2 Phase III Prgramming, Develpment and Testing Gal: Cmplete develpment, installatin, testing and burn-in f hardware and sftware necessary t supprt infrmatin delivery system services and user needs. Specific cmpnents t be addressed in this phase include but are nt limited t: Deliverables: Primary data surce(s) including data warehuses, data marts, data stres, thirdparty sftware applicatins and external data feeds Hardware necessary t hst all layers in the stack (Please refer t The Infrmatin Delivery Technlgy Stack cntained herein) Metadata Cnnectivity layer Sftware t supprt Reprting Interface, Query Prcessing, Reprt Frmatting and Delivery Release 1 Canned Reprts prmted t prductin Series 1 Canned Reprts tested and ready fr deplyment int prductin envirnment Phase IV Reprting Asset Release & Deplyment Gal: Release reprting assets t end users. Deliverables: Release 1 Canned Reprts available via bth Push and Pull delivery Release 2 Dashbards and Screcards available via bth Push and Pull delivery; Alerts and Warnings available via Push delivery Release 3 Ad Hc reprting asset creatin available at the end-user desktp Release 4 Subscriptin delivery mdel available fr apprpriate assets End-user facing Reprts, Screcards, Dashbards, Warnings, Alerts and ad-hc desktp reprting functinality This phase may repeat as (Phase IVa, IVb, IVc etc.) where staged and staggered asset releases are scheduled Cpyright Bellateq, Ltd All Rights Reserved

3 Prject Methdlgy It is recmmended that the implementatin team use a gated, cascade / waterfall apprach when preparing t deply an Infrmatin Delivery and Business Intelligence System. There are tw primary reasns fr this. First due t the nature f the end state deliverables intermediate reviews f partially cmpleted assets (the Agile apprach) is nt recmmended. Unlike sftware that can be partially cmpleted with sme functinality available fr review and ther features still under develpment, Reprts, Screcards, Dashbards, Alerts and Warnings are difficult fr end users t evaluate when they are nly partially cmplete r partially functining. Secnd Until users have had an pprtunity t experience the pwer and flexibility f a welldesigned system in a Prductin envirnment, it is difficult fr them t visualize the breadth f capabilities available in the future state. By deplying a few assets and enabling users t get cmfrtable with their use, and the system verall, users are better prepared t help define mre cmplicated assets as their thinking will nt be limited t the capabilities f the current-state system but will be expanded t include the new functinality f the future-state system. Think Frward, Wrk Backward The mst successful Infrmatin Delivery and Business Intelligence prjects are thse that begin with the end-state deliverables and wrk backward t the data surces that supprt thse assets. With that in mind, the fllwing prjects D s and Dn ts are prvided. DO Start current-state evaluatin and future-state definitin phase f the prject by categrizing current-state prcesses as thse that (1) shuld be retained as-is, (2) shuld be discntinued, (3) shuld be mdified r (4) are nt currently pssible due t infrmatin delivery limitatins Identify nt mre than a dzen infrmatin assets that impact current state prcess effectiveness and/r efficiency; these assets will cmprise the Release 1 assets Give users time t get cmfrtable with the system while develping an understanding f its capabilities by wrking with a small sample f infrmatin assets (The Release 1 assets) befre starting develpment f the mre cmplicated reprts, dashbards, screcards, warnings and alerts Separate all user requests fr end-state deliverables int categries f Required fr On-Ging Operatins, Required fr Cmpliance, Requested fr Imprved Effectiveness 1 and Requested fr Imprved Efficiency 2. Prceed with asset develpment and deplyment based n a mutually agreed upn priritizatin f these fur categries f assets DON T Start the current-state evaluatin and future-state definitin phase f the prject by evaluating every current-state reprting asset as thse assets, their cntent, flexibility and value are driven by the system currently in place as ppsed t the system that is being designed fr the future-state Attempt t reprduce every current-state reprting asset and release them en mass as sn as the new system is running in prductin Attempt t create every reprt, dashbard, screcard, alert and warning that the users request as they have nt had time t gain an understanding f hw the current system wrks, what its capabilities are and hw thse capabilities can drive imprved perating prcedures and reprting assets Have individual users f each infrmatin asset drive the priritizatin f develpment as what s gd fr a small grup f users may nt be what s best fr the Enterprise as a whle 1 Effectiveness is a measure f the ability t get a jb dne such that the desired utcme / results / deliverables are achieved. Assets Requested fr Effectiveness facilitate prcedures that result in the desired utcme where such may nt be pssible given current-state infrmatin delivery capabilities. (Effectiveness = Getting the jb dne) 2 Efficiency is a measure f the financial and human resurce csts required t effectively execute a prcess r wrk stream. Assets Requested fr Efficiency facilitate financial / human resurce cst reductins during the curse f effective peratins. (Efficiency = Reducing the cst f getting the jb dne.) Cpyright Bellateq, Ltd All Rights Reserved

4 Prject Flw The graphic belw demnstrates the relatinship f the initial building blck Data t the final prduct End-State Deliverables. Data Warehuse Specific Data Elements Calculatins Reprt Frmat & Layut End-State Deliverable Thrughut this dcument, Data has been defined as the starting pint the fundamental building blck f all infrmatin and Business Intelligence. Given that, it wuld seem bvius t begin an Infrmatin Delivery & Business Intelligence prject by defining the data prfiles and architecture fr the central data surce / data warehuse(s). Frm a prject flw perspective hwever, the ppsite is true; start at the end with the end-state deliverable and wrk backwards twards the data itself. This is t ensure that end users cnsider the future-state frm a perspective f what is pssible in the new system as ppsed t being limited t cnsidering nly what is pssible tday. Asset design shuld be driven by what s mst effective and efficient as ppsed t what data is currently available. With this Think-Frward-Wrk-Backward cncept in mind, the fllwing prject wrk flw is recmmended: 1. Wrk with end users t define and dcument the end-state deliverables (Infrmatin Assets) that they require t be as effective and efficient as pssible 2. Cmpse rugh drafts f the end state deliverables and review these with the end users t ensure that these assets, nce develped, will meet their needs and fulfill their requirements 3. Dcument the calculatins, algrithms, manipulatins, transfrmatins and enhancements that are required in rder t have the cntent necessary t create the asset that was drafted in step 2 abve 4. Dcument which data elements are necessary inputs t the calculatins, algrithms, manipulatins, transfrmatins and enhancements defined in step 3 abve 5. Dcument the data flw, prfile and architecture f the surce data warehuse such that the required data elements as defined in step 4 are available t supprt the required end state deliverables 1 Fllwing this prcess flw will help t ensure that the ultimate result f the prject are deliverables that imprve effectiveness and increase efficiency and nt merely different frms f the same ld thing that may lk better but d little t imprve business and/r reduce cst. 1 If requisite data is nt available, it must be determined why data required t ensure maximum effectiveness and efficiency is nt readily available. The answer may drive changes and enhancements t the data mining r ETL prcedures. Cpyright Bellateq, Ltd All Rights Reserved

5 High Level Prject Timeline High-Level Timeline Assumptins The fllwing assumptins regarding The Enterprise are made in supprt f the High Level Timeline presented previusly herein: The Enterprise intends t implement a brand new Infrmatin Delivery / Business Intelligence system n newly acquired hardware running newly acquired sftware The Enterprise intends t define and implement a new, centralized Data Strage Structure t serve as the hst f the Data Layer referenced in the Infrmatin Delivery Stack detailed n page previusly herein The Enterprise intends t rll ut all six classes f Infrmatin Assets: Reprts, Screcards, Dashbards, Alerts, Warnings and Ad Hc Desktp Reprting. The planned asset library cnsists f the fllwing: Up t 20 Detail, Summary and Exceptin Reprts f medium cmplexity Up t 8 Executive Screcards and/r Dashbards Up t 20 defined Alerts and/r Warnings Ad-Hc Desktp Reprting fr up t 4 Pwer Users Cpyright Bellateq, Ltd All Rights Reserved

6 At the time f prject cmmencement, the Enterprise des have a Gvernance Mdel in place and Data Stewards are named and empwered t enfrce that mdel At the time f prject cmmencement, the Enterprise des have Data Quality measures and rutine review prcedures in place The fllwing assumptins regarding engagement persnnel are made in supprt f the High Level Timeline cntained herein: This Infrmatin Delivery and Business Intelligence engagement will be staffed by at least three full-time persnnel. These persnnel will have, cumulatively and at minimum, the fllwing skills and capabilities: End User Needs Analysis Cllectin and Dcumentatin Data Warehuse Strategy and Management Definitin Infrmatin Delivery Asset Design Data Architecture and ETL Design Business Intelligence Sftware Setup and Cnfiguratin Gvernance and Data Quality Strategy Metadata Layer Definitin and Setup Excellent written and verbal cmmunicatin skills tailred t business peratins and executive persnnel in additin t Infrmatin Technlgy persnnel The prject s full-time persnnel will be assisted by Enterprise persnnel with subject matter expertise related t: The Enterprise s specific data warehusing and business intelligence hardware infrastructure Enterprise Intranet / Extranet / Internet prtal t be used by the Infrmatin Delivery and Business Intelligence system Enterprise standard perating prcedures and internal cntrls Cpyright Bellateq, Ltd All Rights Reserved

7 Appendix A Glssary Term - A - Accuracy Agile Apprach Alert Algrithms Asset Definitin A measure f Data Quality. An bjective evaluatin f the level f defect r degree f errr. Precisin and Accuracy are synnyms when discussing Data Quality A prject management methdlgy based n cnstant interactin between the prject team and user cmmunity where prgress is reviewed and pririties updated cnstantly based n changing prject frces and user demand High-level message frm Infrmatin Delivery and Business Intelligence system that predicted future state, based n current peratins, may nt be within acceptable threshlds Cllectin f specifically defined rules, steps and prcesses, t be executed in a specified cadence in rder t slve a prblem Any end-user facing utput f an Infrmatin Delivery and Business Intelligence system. Assets cnsist f Reprts, Screcards, Dashbards, Alerts and Warnings - B - Business Intelligence BI. The third level f maturity in the Data Maturity Mdel. Business Intelligence is the cmparative result f infrmatin t internal and external metrics - C - Calculatins Cncatenatin Current State Arithmetic peratins applied t numeric Data in rder t cnvert it int Infrmatin Methd f textual data manipulatin where multiple strings and/r sub-strings frm multiple alpha-numeric data fields are cmbined t create a new text string. Cncatenatin is the ppsite f Parsing. Systems, peratins, prcesses and wrk flws as defined and in frce at the current time - D - Dashbard Graphic, dynamic representatin f current peratins updated cntinuusly Data Data Architecture A specific characteristic and/r result f an actin, wrk flw, prcess r peratin The underlying structural cmpsitin f a data strage unit. Data Architecture dcumentatin represents the blue print used t build and supprt data structures including databases, data warehuses, data stres Cpyright Bellateq, Ltd All Rights Reserved

8 Term Data Freshness Data Mart Definitin and data marts. A Data Architecture defines the characterics and requirements f all data elements within a data strage unit. A measure f hw recently data has been updated with regards t the mst recent peratins cycle. The mre time that elapses between updates the less Fresh data is cnsidered and the lwer the verall data quality measure as less Fresh data is cnsidered less accurate A cllectin f data elements gruped accrding t a cmmn jb functin Data Prfile Data Steward Data Stre Specific details regarding the characteristics (Type, Frmat, Picture, Default Value) f each field within a database Architecture Individual empwered t enfrce and versee the administratin f a Gvernance Mdel A cllectin f data elements gruped accrding t a cmmn reprting asset Data Structure Data Update Data Warehuse The definitin and cnfiguratin f and relatinship between Data Warehuses, Data Stres and Data Marts A revisin f existing data and additin f new data t a data strage unit based n all peratins and wrk flws that have been executed since the last Data Update A cllectin f data elements gruped accrding t functin Deliverable See Asset Delivery Mvement f an Asset frm the surce system t the end user Dwnstream Flw Flw f data frm its native surce system t a central strage facility (ften a Data Warehuse) and the flw f assets frm the central streage facility t end users. Data that ges frm its native surce t a warehuse is said t flw Dwnstream. - E - Effectiveness Efficiency A measure f ne s ability t cmplete a wrk stream, peratin, prcess r functin such that the end result is the anticipated / expected current state and/r Asset. And peratin can be Effective irrespective f whether r nt it is efficient. A measure f the human and financial csts required fr a wrk stream, peratin, prcess r functin t be Effective. An peratin may be Effective withut being Efficient, but it can nt be Efficient withut being Effective. Cpyright Bellateq, Ltd All Rights Reserved

9 Term End-User End State ETL Definitin Cnsumer f assets generated by and delivered frm the Infrmatin Delivery and Business Intelligence System. System, peratins, prcesses and wrk flws prjected t be in frce as f the cmpletin f specified prject r wrk stream. Extractin, Transfrmatin and Lading f data as it flws Dwnstream frm it s native surce t a centralized data strage facility Event A metaphysical state f being inside the Enterprise that has significance within the Infrmatin Delivery and Business Intelligence System. Als see Trigger - F - Firewall Frmat Future State A system f related security measures and access devices within a technlgical envirnment in place t cntrl and mnitr access t data elements Physical presentatin design f assets; Placement and presentatin details f Reprts, Screcards and Dashbards. Als see Layut. Systems, peratins, prcesses and wrk flws prjected t be in frce as f a pint in time that has nt yet ccurred but is still t ccur - G - Gated Apprach A prject management methdlgy based n interim interactins between the prject team and user cmmunity. The ccurrence f these interactins is tied t the accmplishment f certain gals r the cmpletin f sme phase f design f an end-state asset Gvernance A system f security measures, data quality measures, data management prcesses, user passwrd prtcls and technlgy standards administered and verseen by Data Stewards - I - Infrmatin Numeric, Date and Time Data elements that have been manipulated accrding t arithmetic and/r statistic peratins. Textual Data elements that have been manipulated accrding t alphanumeric manipulatins including Cncatenatin and Parsing Infrmatin Asset See Asset - L - Layut The physical cnfiguratin and design f f an Infrmatin Asset. Als see Frmat Cpyright Bellateq, Ltd All Rights Reserved

10 - M - Metadata Term Definitin A cmpnent f the Infrmatin Delivery and Business Intelligence system that translates user requests fr infrmatin and BI int executable queries. The Metadata cmpnent translates end-user speak int cmputer-speak Metric Mining A unit f measure defined by an Enterprise as an indicatin f prcess, peratins r wrk stream results and/r impact Cllecting data elements frm the results f peratins, prcedures r wrk streams - P - Parameters Bundaries set t cntrl Data, Infrmatin and Business Intelligence cntent presented in Reprting Assets. Parameters may be numeric, textual r date/time in frmat and are ften prvided in pairs with ne upper and ne lwer bundary. Exceptins include single parameters prvided when a standard deviatin is allwed as a qualificatin fr cntent inclusin Parsing Prtal Pull Delivery Separating a single textual string int multiple textual strings. Parsing is the ppsite f Cncatenatin. A gateway thrugh which end users can access bth the Presentatin Layer and certain Infrmatin Assets. Intranet Prtals are cntained within a private internal netwrk while Extranet and Internet Prtals are available fr use t authrized users utside the Enterprise. Methd f presenting Infrmatin Assets accrding t a specific user request Push Delivery Methd f presenting Infrmatin Assets autmatically t end users irrespective f a specific request - Q - Query Cmmands and parameters passed t a data surce resulting in the extractin f a sub-set f data that is valid given the limits f acceptability defined by the parameters - R - Relevance A measure f Data Quality. A subjective evaluatin f the degree f impact Data, Infrmatin r Business Intelligence can have at a pint in time Reprt A type f Infrmatin Asset. Detail Reprts cntain specified data elements fr all recrds that fall within the defined selectin range. Summary Reprts cntain statistically and arithmetically calculated Infrmatin that present a macr view f the cntent f a related Detail Reprt. Exceptin Reprts display specific data elements fr recrds that fall utside the defined selectin range. Cpyright Bellateq, Ltd All Rights Reserved

11 Term Definitin - S - Screcard Security Steward A type f Infrmatin Asset. A static, numeric and textual summarized representatin f the results f actins, wrk streams, peratins r prcesses executed during a previus time perid. Prtectin f the Intellectual Assets that are Data, Infrmatin, Business Intelligence and the calculatins, methds and prcesses by which they are created. See Data Steward Strategy Subject Matter Expert Subscriptin Delivery Cllectin f actins, wrk streams and prcesses designed t accmplish a defined end state Individual with deep level f understanding and extensive experience in a specific area f business peratins r functin Methd f presenting Infrmatin Assets t end users where the asset is autmatically Pushed t the end user based n the specific delivery details included in a Subscriptin. A Subscriptin is a user request fr infrmatin that is issued nce by the end user and then retained within the system and repeated accrding t a prescribed cadence - T - Timeliness A measure f Data Quality. A subjective cmparative evaluatin between when an Infrmatin Asset is received by an end user and when that Asset may impact the end user s actins, decisins and/r wrk streams. Trigger An metaphysical state that, nce achieved, will cause an actin r series f events t ccur. Please als see Event - U - Upstream Flw Flw f data frm end users t a central data strage facility. Data that is manually entered int the system is said t flw Upstream. - W - Warning High-level message frm Infrmatin Delivery and Business Intelligence system that current-state is nt within acceptable threshlds Cpyright Bellateq, Ltd All Rights Reserved