Gebruiksaanwijzing /service van het product V2.3 van de fabrikant IBM
Ga naar pagina of 62
Image and Workflow Library: FlowMark V2.3 Design Guidelines Bob Stegmaier Mike Ebbers Tomislav Begovac International Technical Support Organization http://www.
.
International Technical Support Organization Image and Workflow Library: FlowMark V2.3 Design Guidelines February 1998 SG24-4613-02.
Take Note! Before using this information and the product it supports, be sure to read the general information in Appendix C, “Special Notices” on page 29. Third Edition (February 1998) This edition applies to Version 2 Release 3 of IBM FlowMark, Program Number 5697-216 for use with the OS/2, Windows NT and AIX Operating Systems.
Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v The Team That Wrote This Redbook ......................... v Comments Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi Chapter 1.
A.3 Data Containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 A.4 Other Things . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Appendix B. The FlowMark Internet Site .................... 2 7 Appendix C.
Preface This redbook tells you how to design your FlowMark processes to optimize performance, capacity and resource utilization. This version has been updated for IBM FlowMark V2.
Comments Welcome Your comments are important to us! We want our redbooks to be as helpful as possible. Please send us your comments about this or other redbooks in one of the following ways: Fax the evaluation form found in “ITSO Redbook Evaluation” on page 51 to the fax number shown on the form.
Chapter 1. Introduction and Overview Workflow management helps you manage and control your business processes, pinpoint areas for improvement, and streamline your procedures for speedier cycles and shorter response times.
The Staff Definition facility is used for the definition of staff personnel to which activities could be assigned. It maintains information about people, skill levels, roles, organizations, their relationships and their authorizations.
Chapter 2. Importance of Process Design The design of your processes is critical to the project and to your business. It must be done well. You should expect to refine your processes on an ongoing basis. Since FlowMark provides data in the audit trail on process performance, you can more easily find the weak points in the processes.
2.2 Understand the Basis: FlowMark V2.3 The suggestions in this redbook are based on FlowMark as it is implemented in Version 2 Release 3, the generally available (GA) level of code.
Chapter 3. Client/Server Can Mean Multiple Servers While FlowMark is a client/server tool, do not limit your thinking and design to a single server. You should consider capacity and performance in you.
The expectation in this concept is that each server and database combination are independent of any other. There is no communication between FlowMark servers. However, this solution could, over time, be combined with the following option. Have processes on one or more servers perform subprocesses on other servers.
Chapter 4. How Big is a Process? How big should a process be? How much of the business should it encompass? How many activities should it contain? The answer lies somewhere between bigger than the head of a pin and smaller than a galaxy. Again, there are no hard-and-fast rules, but some guidelines can help.
two-activity processes (or subprocesses) need to be questioned as they will entail this overhead, which is much more than just “inline” activities. On the other hand, a very large process, with many activities and long paths that are infrequently used because of the transition conditions, can impact database size.
Chapter 5. Starting and Deleting Process Instances The most obvious way to start a FlowMark process is to open your process list, copy a process template and start the instance manually. But it is probably better to provide a simple FlowMark API program to do that.
Write a program that calls the ExmDeleteProcess API. You can use this API to explicitly delete individual instances whenever you wish, based on such things as time and date or other criteria external to FlowMark processing. The finishing and subsequent deletion of process instances is at least as resource intensive as creating an instance.
Chapter 6. How Big is an Activity? How much work should an activity represent? How long should a user take to complete an activity? For activities that involve the user interacting with a program, thi.
Here is an example. A new customer comes to your retail business. You would like to keep the customer for a long time so, as part of the “new customer process,” you gather information into a database. The process design has the following activity steps: 1.
Chapter 7. How Many People Do I Assign to an Activity? There are many options in FlowMark to help assign activities to different people. These are quite helpful in getting the job done. But do not go overboard, giving everything to everyone. Think about the implications.
If there is some front end program that uses FlowMark API calls to create and start process instances, have it divide the work in a round robin way: one for team A, then team B, then team C, then back to A.
Chapter 8. When Do I Use an Activity Block? An activity block is a construct that allows you to group several activities together. Its major functions are: To reduce clutter at a higher level. This lets you have a cleaner big picture at upper levels of your process.
16 FlowMark V2.3 Design Guidelines.
Chapter 9. When Do I Use a Subprocess? A subprocess is really just a process, but it is called by another (parent) process. It has functions similar to an activity block, but it can do more for you.
leave the activities inline. If there is a low probability of needing the function, a subprocess is preferable. Also, with subprocesses there are also the considerations of ease of use and having a reusable object. You must make the trade-offs. 18 FlowMark V2.
Chapter 10. Data Container Usage The FlowMark data container is used to pass information from activity to activity within the process. It also controls the flow within the process when data fields are used in transition conditions. The terminology used is “process-relevant data.
20 FlowMark V2.3 Design Guidelines.
Chapter 11. Using FlowMark Functions Wisely There are many functions in FlowMark that can influence system performance but are not directly related to process design.
To see the exact possibilities, or to help train your users, do the following, starting from the Runtime client icons: For work lists, select the work list icon, then the specific work list. Open settings, and go to the Activities page. You can do this for each work list if you have multiples.
arrays of data container items. The effects of large data containers was discussed in Chapter 10, “Data Container Usage” on page 19. Chapter 11. Using FlowMark Functions Wisely 23.
24 FlowMark V2.3 Design Guidelines.
Appendix A. Factors Influencing the Size of a FlowMark Data Base When you design your process in FlowMark Buildtime, you create a process model. You then translate this model and create a process template. This is a bit like compiling a program. The template contains the rules and other information necessary to run an instance of the process.
A.2 Results of Staff Resolution When FlowMark determines that a particular activity should be run, it goes through a function called staff resolution. This function determines who should have this activity as "ready" on their work list.
Appendix B. The FlowMark Internet Site If you would like more information on FlowMark, visit the Internet site: http://www.software.ibm.com/ad/flowmark Here you will find lots of information on what is happening in the world of FlowMark, frequently updated.
28 FlowMark V2.3 Design Guidelines.
Appendix C. Special Notices This publication was written to give system architects more information to plan for the number of servers needed for their FlowMark system, and to design it for better performance. The information in this publication is not intended as the specification of any programming interfaces that are provided by FlowMark.
The following terms are trademarks of the International Business Machines Corporation in the United States and/or other countries: The following terms are trademarks of other companies: C-bus is a trademark of Corollary, Inc. Java and HotJava are trademarks of Sun Microsystems, Incorporated.
Appendix D. Related Publications The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this redbook. D.1 International Technical Support Organization Publications For information on ordering these ITSO publications see “How to Get ITSO Redbooks” on page 33.
32 FlowMark V2.3 Design Guidelines.
How to Get ITSO Redbooks This section explains how both customers and IBM employees can find out about ITSO redbooks, CD-ROMs, workshops, and residencies. A form for ordering books and CD-ROMs is also provided. This information was current at the time of publication, but is continually subject to change.
How Customers Can Get ITSO Redbooks Customers may request ITSO deliverables (redbooks, BookManager BOOKs, and CD-ROMs) and information about redbooks, workshops, and residencies in the following ways:.
IBM Redbook Order Form Please send me the following: Title Order Number Quantity First name Last name Company Address City Postal code Country Telephone number Telefax number VAT number Ø Invoice to .
36 FlowMark V2.3 Design Guidelines.
Glossary Note: This glossary defines terms and abbreviations for IBM FlowMark. For more information about the differences and other terms, not defined here, refer to the respective publication as listed in Appendix D, “Related Publications” on page 31.
bar code . Industry standard pattern of vertical lines. You can use bar codes to indicate the beginning of a new folder, the beginning of a new document, or to provide a value to be used in indexing the folder or the document. base product . The product that provides the functionality required for the operation, for example, FlowMark, Lotus Notes.
change management bus . On the ALOVC, a continuum of repetitive and unpredictable processes for enabling customers to request and affect changes (for example, a proposal, a contract, or an order at any time during the relationship). child organization .
when a customer places an order to when the customer receives the product). D DASD . Direct Access Storage Device. A device in which access time is effectively independent of the location of the data. data bus . On an ALOVC or a LLOVC, a logical set of data.
entity . A thing or object of importance to a business about which the business wants to keep information, such as customer or product. event flow . In process-based applications, including FlowMark, an event flow is part of the control flow. It triggers the continuation of activities that are in a wait status.
such as an order, a shipping document, or an invoice. Information flows can use various media, such as FAX machines, telephones, or electronic mail, which can be represented on the LOVCs by icons. See also data flow , material flow , and control flow .
loop . A loop is an iteration of activities on a PLOVC or JLOVC. There are two sets of exit criteria for a loop: 1. One set contains the criteria for exiting the loop through the normal flow when the exit conditions are met.
O opportunity area (OA) . A point in a process or process path where possibilities, advantages, or other positive factors can help an enterprise meet its goals. organization . An administrative unit of an enterprise. In FlowMark: organization is one of the criteria that can be used to dynamically assign activities to people.
process diagram . A graphical representation of a process or process path that shows all its components. process instance . In FlowMark: an executable copy of a process template in Runtime.
Runtime client . In FlowMark: the user interface for working with process templates, process instances, work lists, and work items. See also Runtime . S screen layout . The design and specifications of the image that the user sees on the screen of a system.
order cycle time. The time line shows both actual (As Is) and target (To Be) times. To Be . The desired state of a process or process path: how it could be or should be. See also As Is . To Be view . A chart or diagram showing the desired state of a process or process path.
48 FlowMark V2.3 Design Guidelines.
Index A activity 1, 3, 6, 7, 8, 11, 12, 13, 14, 15, 17, 19 automatic 12 block 1, 15 networks 1 notebook 13 staff pages 13 volumes 11 activity block 2 activity, automatically started 1 activity, unatte.
headquarters 5, 6 I impact 3, 6, 11, 14, 19, 22 include 19, 21 input container 6 instance 3 K knowledge workers 11 L LAN 3 load balancing 13 M memory (swapping) 6 monitor 9 N navigation 1, 19 navigati.
server (continued) multiple (continued) no communication 6 subprocess 6 OS/2 5 planning 5 regional 5 registration 2 single 5 step up 5 Unix 5 Server Definition facility 2 shutdown 21 signoff 21 signon.
52 FlowMark V2.3 Design Guidelines.
ITSO Redbook Evaluation Image and Workflow Library: FlowMark V2.3 Design Guidelines SG24-4613-02 Your feedback is very important to help us maintain the quality of ITSO redbooks. Please complete this questionnaire and return it using one of the following methods: Use the online evaluation form found at http://www.
SG24-4613-02 Printed in the U.S.A. Image and Workflow Library: FlowMark V2.3 Design Guidelines SG24-4613-02.
Een belangrijk punt na aankoop van elk apparaat IBM V2.3 (of zelfs voordat je het koopt) is om de handleiding te lezen. Dit moeten wij doen vanwege een paar simpele redenen:
Als u nog geen IBM V2.3 heb gekocht dan nu is een goed moment om kennis te maken met de basisgegevens van het product. Eerst kijk dan naar de eerste pagina\'s van de handleiding, die je hierboven vindt. Je moet daar de belangrijkste technische gegevens IBM V2.3 vinden. Op dit manier kan je controleren of het apparaat aan jouw behoeften voldoet. Op de volgende pagina's van de handleiding IBM V2.3 leer je over alle kenmerken van het product en krijg je informatie over de werking. De informatie die je over IBM V2.3 krijgt, zal je zeker helpen om een besluit over de aankoop te nemen.
In een situatie waarin je al een beziter van IBM V2.3 bent, maar toch heb je de instructies niet gelezen, moet je het doen voor de hierboven beschreven redenen. Je zult dan weten of je goed de alle beschikbare functies heb gebruikt, en of je fouten heb gemaakt die het leven van de IBM V2.3 kunnen verkorten.
Maar de belangrijkste taak van de handleiding is om de gebruiker bij het oplossen van problemen te helpen met IBM V2.3 . Bijna altijd, zal je daar het vinden Troubleshooting met de meest voorkomende storingen en defecten #MANUAl# samen met de instructies over hun opplosinge. Zelfs als je zelf niet kan om het probleem op te lossen, zal de instructie je de weg wijzen naar verdere andere procedure, bijv. door contact met de klantenservice of het dichtstbijzijnde servicecentrum.
