Designing processes - EMC Community Network

More documents

Recommendations

Info

Prototyping overview Prototyping overview Technical solutions that include Business Activity Monitor and other applications of xCP (Process Builder, Forms Builder, TaskSpace) take time to design and deploy to end users. When a project is completed a fully designed, tested, and monitored process is deployed to users who complete real work. Dashboards are populated when users start and work with their processes. Dashboards can also be populated with data from test processes (ones yet to be deployed) but the process designer is still responsible for designing a fully functional process. How then, is it possible to design a mock dashboard that includes a variety of dashboard features, without having a fully developed process This answer is to design a dashboard prototype. Dashboard prototypes are designed in TaskSpace, and contain reports designed in Process Reporting Services (PRS). The simple reports (this document does not include adding Crystal Reports to a dashboard) display example data that you populate while a number of small processes run. This data is formatted to appear as bar charts, pie charts, line graphs, and dial gauges. Prototypes can also include multi- and single drill-down reports. Designing prototype dashboards serves a few functions. First, prototypes are used by internal resources of organizations deploying BAM. xCP projects that require planning and designing prototypes help project members determine which reports are important. Prototyping is also a good way of helping to define some of the process data requirements. Since a prototype dashboard can contain business data reports, key business attributes should be included in your data model, and flagged for monitoring. Dashboard prototypes can also be demonstrated to either internal or external audiences to obtain valuable feedback prior to actual deployment. Prototypes are an excellent method for demonstrating the concepts and value of process monitoring. Whatever the goal, this approach assumes that the prototype designer has a basic understanding of Process Builder, TaskSpace, and Business Activity Monitor. This documentation does not replace the Process Builder User Guide or the Business Activity Monitor Implementation Guide. It is assumed that you are already familiar with those technologies. This appendix explains how to easily design prototype dashboards that can be used for planning and demonstrations. The audience for this information is: • an EMC partner that is engaged with a client that wants to see proof that BAM dashboards can be designed to meet their needs • an EMC customer that is involved in the planning phase of an implementation and wants to see prototype BAM dashboards without going through an entire xCP deployment • a pre-sales resource Note: The procedures provided in this document provide actual data that you can enter. If you follow this approach you will design the Finance Corp prototype dashboard in its entirety. Or, you can apply the approach described to your own situation, and attempt to build your own prototype dashboard. Understanding the example The example used throughout this document focuses on a fictitious company called Finance Corp. Finance Corp is in the process of building an automated approach to the New Account Opening process. As part of the planning, Finance Corp is designing a BAM dashboard prototype that includes reports about their New Account Opening process. The dashboard prototype includes six dashlets: 122 EMC Documentum xCelerated Composition Platform Version 1.6 Best Practices Guide
Prototyping Business Activity Monitor dashboards Finance Corp is also interested in demonstrating the following dashboard capabilities: • single drill-down reports • multi-drill-down reports • Service Level Agreement (SLAs) The dashboard is conceptually divided into two parts. The contents of the New Account Applications report and the Alert List and Process Diagram dashlets are each related to a real, but mock process called New Account Applications. Understanding the approach to prototyping, page 124 addresses the role and design of the New Account Applications process. In addition, each of these three dashlets are designed with entities that are shipped with BAM which means they can be applied to all demonstration scenarios. • New Account Applications — this report is designed with the Process Execution entity. • Alert List — this dashlet displays information about processes or activities that meet an alert condition defined in PRS. Defining alerts in PRS is not included in this document. Refer to the Business Activity Monitor Implementation Guide for more information on alerting. • Process Diagram — this dashlet displays the progress of a single process instance when a process is selected in the New Account Applications report. The remaining three dashlets in this dashboard contain four business data reports. Four different business data reports can be viewed because the New Accounts this Week report is configured as a single drill-down report that displays the New Accounts by Customer Type report when any of the bars are clicked in the source report. The most important point to understand about business data reports is that they are designed with report entities that reflect the name and structure of SDTs defined in Process Builder. • New Account Process — this report is formatted as a dial gauge that displays average process duration. • New Accounts Opened this Week — this report is formatted as a bar chart that counts the number of new accounts opened in each country within the last week. • New Accounts By Customer Type — this report is formatted as a pie chart and is configured as the target report in a single drill-down report. It is linked to the New Accounts Opened this Week report. EMC Documentum xCelerated Composition Platform Version 1.6 Best Practices Guide 123
Page 1 and 2:
EMC ® Documentum ® xCelerated Com
Page 3 and 4:
Table of Contents Chapter 1 Overvie
Page 5:
Table of Contents Chapter 8 Cleanin
Page 8 and 9:
Preface 8 EMC Documentum xCelerated
Page 10 and 11:
Overview • Provides security and
Page 12 and 13:
Overview 12 EMC Documentum xCelerat
Page 14 and 15:
Product Overview Documentum ECM pla
Page 16 and 17:
Product Overview Process automation
Page 18 and 19:
Planning and Designing the Applicat
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Creating the Data Model submitter_a
Page 32 and 33:
Creating the Data Model should occu
Page 34 and 35:
Designing the Process Defining acti
Page 36 and 37:
Designing the Process The transitio
Page 38 and 39:
Designing the Process 2. Add a seco
Page 40 and 41:
Designing the Process The end resul
Page 42 and 43:
Designing the Process To copy all v
Page 44 and 45:
Designing the Process because the i
Page 46 and 47:
Designing the Process 3. On the Tim
Page 48 and 49:
Designing the Process 48 EMC Docume
Page 50 and 51:
Designing the Process Inter-process
Page 52 and 53:
Designing the Process In the HTTP I
Page 54 and 55:
Designing the Process For the child
Page 56 and 57:
Designing the Process at or right a
Page 58 and 59:
Designing the Process Enabling repo
Page 60 and 61:
Designing the Process Performance a
Page 62 and 63:
Designing the Process 62 EMC Docume
Page 64 and 65:
Creating the User Interface mind th
Page 66 and 67:
Creating the User Interface Figure
Page 68 and 69:
Creating the User Interface 4. Sele
Page 70 and 71:
Creating the User Interface Figure
Page 72 and 73: Creating the User Interface Figure
Page 76 and 77: Creating the User Interface Adaptor
Page 80 and 81: Creating the User Interface 5. Spec
Page 82 and 83: Creating the User Interface 1. Open
Page 84 and 85: Creating the User Interface 11. In
Page 86 and 87: Creating the User Interface Working
Page 88 and 89: Creating the User Interface 88 EMC
Page 90 and 91: Monitoring Business Activity • pu
Page 92 and 93: Monitoring Business Activity (PRS).
Page 94 and 95: Monitoring Business Activity • Us
Page 96 and 97: Performance and Scalability System
Page 98 and 99: Performance and Scalability Factors
Page 100 and 101: Performance and Scalability Skill-s
Page 102 and 103: Performance and Scalability
Page 104 and 105: Performance and Scalability If regi
Page 106 and 107: Performance and Scalability 106 EMC
Page 108 and 109: Deploying the Application At deploy
Page 110 and 111: Deploying the Application 110 EMC D
Page 112 and 113: Archiving the Application • When
Page 114 and 115: Archiving the Application b. Log in
Page 116 and 117: Archiving the Application 5. Create
Page 118 and 119: Archiving the Application h. Select
Page 120 and 121: Archiving the Application 120 EMC D
Page 124 and 125: Understanding the approach to proto
Page 126 and 127: Create and run the New Account Appl
Page 128 and 129: Designing the New Account Applicati
Page 130 and 131: Designing the New Account Applicati
Page 132 and 133: Design dashboard and add dashlets 1
Page 134 and 135: Design dashboard and add dashlets 1
Page 136 and 137: Process Duration alert 3. From the
Page 138 and 139: Process Duration alert 17. On the k
Page 140 and 141: Designing the New Account Process -
Page 142 and 143: Designing the New Account Process -
Page 144 and 145: Running the Average Duration proces
Page 146 and 147: Designing the Average Duration repo
Page 148 and 149: Designing the New Account by Custom
Page 150 and 151: Designing the New Accounts by Custo
Page 152 and 153: Designing the New Accounts Opened t
Page 158 and 159: Designing the New Accounts Opened L
Page 160 and 161: Completing the prototype dashboard
Page 163 and 164: Index A activities count children,
Page 165: Index designing activity triggers,
show all

Designing processes - EMC Community Network

Create successful ePaper yourself

Delete template?

Save as template?