Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Contents
CONTENTS .....................................................................................................................................................................3 BPM AND BUSINESS PROCESSES..................................................................................................................................4 THE GOAL: BETTER BUSINESS PROCESSES.............................................................................................................................4 REACHING THE GOAL: BPM TECHNOLOGIES..........................................................................................................................4 CONNECTING PEOPLE: HUMAN WORKFLOW..........................................................................................................5 HUMAN WORKFLOW WITH WINDOWS SHAREPOINT SERVICES AND OFFICE SHAREPOINT SERVER 2007 .................................6 MICROSOFT TOOLS FOR CREATING HUMAN WORKFLOWS .....................................................................................................7 CONNECTING SOFTWARE: SYSTEM WORKFLOW...................................................................................................9 SYSTEM WORKFLOW WITH BIZTALK SERVER....................................................................................................................... 0 MICROSOFT TOOLS FOR CREATING SYSTEM WORKFLOWS ................................................................................................... AN ASIDE: WINDOWS WORKFLOW FOUNDATION.................................................................................................12 USING HUMAN AND SYSTEM WORKFLOW TOGETHER.......................................................................................13 COMBINING WINDOWS SHAREPOINT SERVICES AND BIZTALK SERVER................................................................................. ! PARTNER SOLUTIONS........................................................................................................................................................... 4 AUTOMATING COMPLEX DECISIONS: BUSINESS RULES ENGINES....................................................................1 THE BIZTALK SERVER BUSINESS RULES ENGINE ................................................................................................................. " RULES IN WINDOWS WORKFLOW FOUNDATION................................................................................................................... " PARTNER SOLUTIONS........................................................................................................................................................... # TRACKING BUSINESS PROCESSES: BUSINESS ACTI!ITY MONITORING...........................................................21 DESCRIBING BUSINESS PROCESSES..........................................................................................................................24 CONCLUSION.................................................................................................................................................................. 25 FOR FURTHER READING..............................................................................................................................................25 ABOUT THE AUTHOR....................................................................................................................................................2"
'echnologies for defining and e/ec ting h !an (or+flo(s, (hich are processes that connect people. $roviding a to!ated s pport for h !an,oriented processes is a f nda!ental aspect of #$M, as are the graphical tools sed to define those processes.
'echnologies for defining and e/ec ting syste! (or+flo(s, (hich are processes that connect soft(are. 3 pporting these a to!ated interactions a!ong applications is another f nda!ental part of #$M, and it again incl des graphical tools to define those interactions. .ntegration technologies are often incl ded here as (ell, s ch as adapters for connecting to diverse syste!s and tools for defining data transfor!ations. 'he ability to co!bine h !an and syste! (or+flo(s is also i!portant, since !any b siness processes involve both. # siness r les engines "#*5s%. .f decisions !ade by a b siness process can be e/pressed as a set of r les, a #*5 can fre- ently be sed to !a+e those decisions in soft(are. Doing this can help decision !a+ing be faster, cheaper, and !ore consistent. # siness activity !onitoring "#AM%. 'he people (ho rely on a b siness process can often benefit fro! visibility into c rrently r nning instances of that process. #AM provides this visibility, e/posing relevant infor!ation abo t r nning processes in ter!s that are !eaningf l to the infor!ation (or+ers (ho se it. $rocess description tools0 6aving a clear nderstanding of a b siness process co!!only starts (ith a pict re of that process. 7raphical tools for ill strating the actions and relationships in a process are sef l for creating this pict re.
Microsoft2s pri!ary #$M technologies fit - ite (ell into these five categories. 'hose technologies are the follo(ing0
6 !an (or+flo(0 Windo(s 3hare$oint 3ervices and 8ffice 3hare$oint 3erver. 3yste! (or+flo(0 #i)'al+ 3erver, (hich provides integration services as (ell. .t can also be sed (ith Windo(s 3hare$oint 3ervices and other prod cts to create co!bined h !an and syste! (or+flo(s. # siness r les engine0 #i)'al+ 3erver2s #*5. Microsoft also provides a r les engine (ith Windo(s Wor+flo( 1o ndation, part of the .95' 1ra!e(or+ :.0. # siness activity !onitoring0 #i)'al+ 3erver2s #AM, together (ith technologies s ch as Microsoft 5/cel and 8ffice $erfor!ance$oint 3erver for displaying #AM infor!ation. $rocess description tools0 Microsoft 4isio.
Microsoft2s #$M technologies are directly sef l for i!proving b siness processes. .n - ite a fe( cases, ho(ever, organi)ations can also benefit fro! co!ple!entary prod cts that others have b ilt for Microsoft2s #$M platfor!. 1or e/a!ple, Microsoft partners s ch as Ascentn, $9Msoft, and 3o rcecode, ;2.net all allo( creating co!bined h !an and syste! (or+flo(s (ith capabilities beyond (hat Microsoft provides. 3i!ilarly, prod cts fro! .n* le, * le# rst, and others provide i!proved tools for (or+ing (ith Microsoft b siness r les technologies. <nderstanding #$M technology in the Microsoft (orld re- ires nderstanding (hat Microsoft itself offers and ho( .34 partners enhance those offerings. Accordingly, this paper describes both.
a n !ber of (ays. $roviding for!ali)ed s pport helps !a+e processes !ore repeatable, !a+ing s re that the sa!e steps are carried o t each ti!e. .t can also !a+e the !echanics of the process, s ch as ro ting a doc !ent and collecting approvals, significantly si!pler. =et even a to!ated (or+flo(s need so!e fle/ibility. 6andling n s al cases>e/ceptions>is essential, as is allo(ing people to change their !inds in the !iddle of the process. 6 !an (or+flo( is applicable to !any different b siness processes. Doc !ent approval is the !ost co!!on in !any organi)ations, b t !ore co!ple/ scenarios are also in (idespread se. Whatever it2s sed for, the f nda!ental technology re- ired is ! ch the sa!e.
"u#an $or%flow with $indows 'harePoint 'ervices and Office 'harePoint 'erver 2(()
'he latest release of Windo(s 3hare$oint 3ervices, Microsoft2s flagship collaboration soft(are, incl des b ilt,in s pport for e/ec ting h !an (or+flo(s. Developers can create (or+flo(s for this environ!ent sing 4is al 3t dio, (hile infor!ation (or+ers can se a ne( tool called 3hare$oint Designer 2007. Microsoft 8ffice 3hare$oint 3erver 2007, part of the 2007 Microsoft 8ffice syste!, b ilds on the basic capabilities of Windo(s 3hare$oint 3ervices, adding pre,defined (or+flo(s and !ore. 'his section provides an overvie( of these technologies. 'he easiest (ay to nderstand ho( Windo(s 3hare$oint 3ervices s pports h !an (or+flo( is to (al+ thro gh a scenario. 'he fig re belo( sho(s a slightly si!plified ill stration of doc !ent approval sing a 3hare$oint (or+flo(.
1) Initiate workflow
Workflow Initiator
') (eview doc%&ent ") A##rove or re$ect doc%&ent
Workflow Participants
'r e to its role as collaboration soft(are, Windo(s 3hare$oint 3ervices lets sers create sites, each of (hich can contain document libraries and lists. A doc !ent library !ight contain a collection of Word doc !ents, $D1 files, or other things, (hile a list is ? st a collection of ite!s. *ather than reinvent ne( concepts, the h !an (or+flo( capabilities in Windo(s 3hare$oint 3ervices b ild on these basics. .n this e/a!ple, the (or+flo( allo(s a n !ber of participants to approve or re?ect a doc !ent stored in a doc !ent library. 'o start this (or+flo(, the initiator ses .nternet 5/plorer or another Web bro(ser to select the doc !ent, then chooses an e/isting (or+flo( definition to e/ec te "step @%. Wor+flo(s can also be started a to!atically, s ch as by adding a ne( doc !ent to a doc !ent library. 6o(ever it2s done, Windo(s 3hare$oint 3ervices no( begins e/ec ting the (or+flo(.
*
'o let (or+flo( participants +no( that they have so!ething to do, the (or+flo( adds a tas+ to each participant2s tas+ list "step 2%. 'his tas+ list is ? st an ordinary 3hare$oint list>there2s nothing special abo t it>that2s sed to let a r nning (or+flo( infor! participants of (aiting tas+s. 5ach participant then chec+s his or her tas+ list sing a Web bro(ser or Microsoft 8 tloo+ 2007 "step :%, and finds a re- est to revie( this doc !ent. 5ach participant can revie( the doc !ent "step A%, then interact directly (ith the r nning (or+flo( thro gh a c sto! for! to indicate approval or re?ection "step B%, perhaps adding co!!ents. 8nce all of the (or+flo(2s participants have done this, the (or+flo( infor!s the initiator that it2s done. 'his e/a!ple o!its several possibilities. 'he (or+flo(2s initiator !ight be able to c sto!i)e the (or+flo(2s behavior, for e/a!ple, s ch as by controlling (hether the participants are assigned tas+s se- entially or all at once. .t !ight also be possible to change a partic lar (or+flo( instance (hile it2s r nning, s ch as by adding another person to the list of approvers. 3till, this si!ple ill stration sho(s the basics of h !an (or+flo( s pport in Windo(s 3hare$oint 3ervices today. 8ffice 3hare$oint 3erver b ilds on these services to provide !ore (or+flo( options. <nli+e Windo(s 3hare$oint 3ervices, (hich is a standard co!ponent of Windo(s 3erver 200:, 8ffice 3hare$oint 3erver is a separately licensed prod ct. 8rgani)ations that choose to se it have !ore (or+flo( capabilities, incl ding the follo(ing0
'he ability to interact (ith (or+flo(s directly fro! 8ffice 2007 applications. As described earlier, Windo(s 3hare$oint 3ervices alone !ostly s pports interacting (ith (or+flo(s thro gh a bro(ser. 'he ability to define the for!s a (or+flo( displays sing .nfo$ath. Wor+flo(s b ilt solely on Windo(s 3hare$oint 3ervices rely on for!s created (ith A3$.95'. A gro p of c sto!i)able pre,defined (or+flo(s for doc !ent approval and other p rposes.
Along (ith these h !an (or+flo( additions, 8ffice 3hare$oint 3erver also provides a range of other f nctions, incl ding doc !ent !anage!ent, broad search capabilities, s pport for blogs and (i+is, and !ore.
More co!ple/ (or+flo(s or those (ith !ore options, s ch as allo(ing changes to a r nning (or+flo(, can be created sing 4is al 3t dio. 'his developer,targeted tool ta+es a significantly !ore general approach, sing activities to describe a (or+flo(2s steps. As the screen shot belo( sho(s, a (or+flo(2s logic can be defined graphically by dragging and dropping activities onto a design s rface. A developer can also create a Windo(s 3hare$oint 3ervices (or+flo( entirely in code> sing this graphical tool isn2t re- ired.
6 !an (or+flo( technology can i!prove !any b siness processes, and it2s (idely sed today. Adding s pport for this technology directly into Windo(s, as Windo(s 3hare$oint 3ervices 2007 does, is li+ely to !a+e it even !ore pop lar. # t b siness processes often depend on soft(are, too. A to!ating the interactions a!ong this soft(are can i!prove those processes as (ell. 6o( Microsoft technologies provide this is described ne/t.
of business process automation. Whatever ter!s are sed, the goal is al(ays the sa!e0 better b siness processes. 3yste! (or+flo( can i!prove a b siness in a n !ber of (ays. A to!ating e/isting !an al (or+ can !a+e processes faster and !ore acc rate. 3ynchroni)ing infor!ation across different applications can ens re that everybody sees the sa!e vie( of c sto!ers, patients, or anything else this organi)ation (or+s (ith. A to!ating lin+s bet(een organi)ations, s ch as (ith electronic data interchange "5D.%, can significantly i!prove the reliability of ordering, pay!ent, and other cross,organi)ational e/changes. All of these process i!prove!ents rely on integration technologies, and all can be driven by syste! (or+flo(.
!i"Talk Server
Orchestration
2) (e*%est PO
) (et%rn PO
Inventory pplication
$%P pplication
#ulfillment pplication
'he syste! (or+flo( itself>the logic that controls this process>is i!ple!ented in a #i)'al+ orchestration, as sho(n above. #eca se different applications represent infor!ation in different (ays, #i)'al+ 3erver also provides data transformation tools to !ap bet(een these diverse data for!ats. And since a variety of approaches are sed to co!! nicate (ith applications, #i)'al+ 3erver relies on adapters to i!ple!ent different options. 'he prod ct incl des adapters for co!! nication via - e es, via Web services, thro gh the Windo(s file syste!, and sing other technologies. Microsoft also provides adapters for interacting (ith pop lar pac+aged applications, s ch as those fro! 3A$ and 8racle. .n this e/a!ple, s ppose an inventory application deter!ines that so!e ite! needs to be reordered. .t sends an order re- est to #i)'al+ 3erver via an appropriate adapter "step @%. 'his re- est starts an orchestration, (hich then creates a !essage re- esting a p rchase order "$8% for this ne( ite! and sends it to this organi)ation2s 5*$ application "step 2%. As al(ays, co!! nication bet(een #i)'al+
.(
3erver and this application relies on so!e adapter, and #i)'al+ 3erver also perfor!s any re- ired data transfor!ation. 9e/t, the 5*$ application creates the p rchase order and sends it bac+ to #i)'al+ 3erver "step :%. 8nce this !essage is received, the orchestration creates another !essage to act ally place the order, then sends it to the f lfill!ent application "step A%. All three of the applications sed in this process !ight be inside the sa!e organi)ation, !a+ing this an e/a!ple of enterprise application integration. .t2s also possible that, say, the f lfill!ent application is located at a s pplier fir!, (hich !a+es that part of the process - alify as b siness,to,b siness integration. .n either case, the syste! (or+flo( i!ple!ents the controlling logic for this process, (hile each of the applications the (or+flo( relies on carries o t its o(n responsibilities.
Along (ith this developer,foc sed tool, #i)'al+ 3erver also provides a 4isio,hosted design tool. Called the 8rchestration Designer for # siness Analysts, it2s ai!ed at less technically oriented people. 8rchestrations created (ith this tool can be i!ported into the 4is al 3t dio,hosted tool sho(n above. A b siness analyst !ight define the process sed in a syste! (or+flo(, for e/a!ple, then pass this
..
definition to a developer. 'he developer can then add the technical details re- ired to !a+e the orchestration e/ec table.
!i"Talk Server
Orchestration
Workflow
2) (e*%est PO
) (et%rn PO
Inventory pplication
$%P pplication
#ulfillment pplication
'he first three steps in this scenario are the sa!e as in the syste! (or+flo( e/a!ple sho(n earlier0 the inventory application sends an order re- est to #i)'al+ 3erver "step @%, and #i)'al+ 3erver re- ests "step 2% and receives "step :% a p rchase order fro! the 5*$ application. 9o(, ho(ever, let2s ass !e
.3
that the $8 a!o nt is s fficient to re- ire approval fro! a gro p of !anagers at this fir!. A h !an (or+flo( i!ple!ented sing Windo(s 3hare$oint 3ervices is sed to !a+e this decision. 8nce the orchestration has deter!ined that this $8 re- ires !anagerial approval, it ses a 3hare$oint adapter to add a doc !ent to a partic lar doc !ent library "step A%. As !entioned earlier, adding a ne( doc !ent to a library can a to!atically trigger e/ec tion of a 3hare$oint (or+flo(, (hich is e/actly (hat happens here. 'his (or+flo( then e/ec tes as described earlier, adding tas+s to the participants2 tas+ lists. 5ach participant approves or re?ects the order "step B%, and once all responses are in, the (or+flo( adds infor!ation to the doc !ent previo sly created in this doc !ent library by the orchestration, an action not sho(n in this fig re. #i)'al+ 3erver2s 3hare$oint adapter retrieves this !odified doc !ent, so!ething that2s also not sho(n, and if the order is approved, contacts the f lfill!ent application to place it "step C%. Co!bining h !an and syste! (or+flo( is the right approach for i!proving a n !ber of b siness processes. As this e/a!ple sho(s, Windo(s 3hare$oint 3ervices and #i)'al+ 3erver can be sed together to acco!plish this. '(o distinct (or+flo(s ! st be defined, sing t(o different design tools, and those (or+flo(s (ill be e/ec ted by t(o separate (or+flo( engines. 3till, this co!bination can be sed for b siness processes that re- ire both +inds of (or+flo(.
Partner 'olutions
3everal Microsoft partners provide (ays to connect their #$M technologies (ith Microsoft2s, offering alternative approaches to creating co!bined h !an and syste! (or+flo(s. 'his section loo+s at so!e of these partners, providing a brief description of ho( each one co!ple!ents (hat Microsoft provides. Ascentn Ascentn Agile$oint, b ilt on the .95' 1ra!e(or+ and other Windo(s technologies, is foc sed entirely on h !an (or+flo(. Accordingly, the prod ct relies on #i)'al+ 3erver for syste! (or+flo( and integration. As the screen shot belo( ill strates, Ascentn2s 4isio,based tool for defining processes, called 5nvision, can incl de a #i)'al+ orchestration directly (ithin an Agile$oint (or+flo(. While the orchestration2s logic can2t be !odified in this tool, it is possible to define #i)'al+ endpoints and config re the orchestration in other (ays.
.4
1or b siness processes that need both syste! and h !an (or+flo(, co!bining #i)'al+ 3erver (ith Agile$oint in this (ay can !a+e sense. While #i)'al+ 3erver addresses the syste! (or+flo( and integration aspects of the proble!, Agile$oint offers s pport for h !an (or+flo( that goes beyond (hat2s possible (ith Windo(s 3hare$oint 3ervices. A!ong the things this prod ct provides, for e/a!ple, are the ability to add ne( participants in ne( roles (hile a (or+flo( is r nning and to display different for!s based on a participant2s role. P2Msoft 'he forthco!ing release of $9Msoft2s #$M offering, called 35F<59C5 and d e by !id,2007, is b ilt on Windo(s Wor+flo( 1o ndation. 'his prod ct foc ses pri!arily on h !an (or+flo(, and li+e 3hare$oint (or+flo(s, 35F<59C5 (or+flo(s can interact (ith people thro gh a Windo(s 3hare$oint 3ervices interface, thro gh 8 tloo+, and in other (ays. 35F<59C5 provides its o(n e/ec tion environ!ent, ho(ever>its (or+flo(s don2t r n inside Windo(s 3hare$oint 3ervices. And (hile the pre,defined (or+flo(s incl ded in 8ffice 3hare$oint 3erver s pport basic doc !ent approval and other relatively straightfor(ard processes, $9Msoft targets a !ore co!ple/ set of scenarios. <nli+e 3hare$oint (or+flo(s, for instance, 35F<59C5 allo(s a tas+ to be ro ted to (hoever c rrently has the shortest - e e of (aiting ite!s or broadcast to all sers b t processed only by the first ser (ho handles it. 'o create (or+flo(s, $9Msoft provides a (eb,based design tool called 35F<59C5 3t dio. 'his tool incl des a large n !ber of (i)ards, each intended to help an infor!ation (or+er !ore easily define so!e aspect of a process. <nder the covers, these (i)ards create W1 (or+flo(s sing both standard W1 activities and $9Msoft2s c sto! activities. 'he tool also provides (i)ards that allo( an infor!ation (or+er to e/a!ine available #i)'al+ orchestrations, then define a connection that e/changes data (ith this orchestration via Web services. 'he screen shot belo( sho(s an e/a!ple of ho( this loo+s.
.&
$9Msoft2s c sto! activities can also be sed by developers to create 35F<59C5 (or+flo(s directly in 4is al 3t dio. As (ith !any #$M prod cts, the goal is to provide tools for both technical staff and !ore b siness,oriented people. 'ource ode3425net 1oc sed pri!arily on defining and e/ec ting h !an (or+flo(s, 3o rceCode2s ;2.net relies on #i)'al+ 3erver for syste! (or+flo(s. 'he prod ct2s forthco!ing release, codena!ed G#lac+ $earlH and sched led to be available by !id,2007, provides a 4is al 3t dio,hosted designer that developers can se to do this. Written sing Windo(s $resentation 1o ndation, this designer lets a developer add a #i)'al+ orchestration to a (or+flo(, then config re so!e aspects of the interaction bet(een the orchestration and the h !an (or+flo(. #lac+ $earl also ses Microsoft2s #$M technologies in other (ays. 'he prod ct2s native h !an (or+flo(s are e/ec ted sing Windo(s Wor+flo( 1o ndation, and it incl des a designer that lets infor!ation (or+ers define these (or+flo(s. 'his tool, a si!ple e/a!ple of (hich is sho(n belo(, can be sed to create either native #lac+ $earl (or+flo(s or (or+flo(s that r n in Windo(s 3hare$oint 3ervices. <nli+e Microsoft2s 3hare$oint Designer, #lac+ $earl2s ADAI,based approach provides a !ore traditional graphical vie( of a b siness process. C sto!ers (ho have 8ffice 3hare$oint 3erver installed can also se this tool to create 3hare$oint (or+flo(s that display .nfo$ath for!s, so!ething that2s not possible (ith 3hare$oint Designer.
.*
.)
!i"Talk Server
Orchestration
2) (e*%est PO
) (et%rn PO
Inventory pplication
$%P pplication
#ulfillment pplication
As the fig re ill strates, the first three steps re!ain the sa!e as in the previo s scenarios. 'he decision to approve or re?ect a high,val e order, ho(ever, is !ade by the #i)'al+ 3erver #*5 "step A% rather than by people. 'he #*5 is invo+ed directly fro! the r nning orchestration, ret rning the res lt of its eval ation. As before, the order is then placed only if it (as approved "step B%. .f the r les nderlying this decision can be e/pressed ob?ectively and acc rately, the benefit to the b siness process is clear0 decision !a+ing (ill be faster and !ore consistent. .t !ight also be !ore transparent, since the r les are no( available in an e/ternal for!at>they2re no longer stored solely in people2s heads. As this e/a!ple sho(s, a #*5 !ight be able to replace decisions !ade by people in a b siness process. .t2s also possible for a process to se both decision,!a+ing approaches. .n the e/a!ple sho(n here, for instance, s ppose that the decision criteria for so!e +inds of orders can2t be co!pletely capt red in for!ali)ed r les. .t2s possible that along (ith the steps sho(n above, the process (o ld also incl de a h !an (or+flo(, perhaps i!ple!ented sing Windo(s 3hare$oint 3ervices. While a #*5 !ight so!eti!es replace decisions !ade by people, the t(o can also be sed together.
r les engine relies on a si!pler approach that2s !eant to be easier to se. 7iven that it2s part of the .95' 1ra!e(or+ :.0, it2s fair to characteri)e the W1 r les engine as a developer,foc sed technology, and so Microsoft has tried to !a+e it !ore approachable by typical Windo(s developers. And since the .95' 1ra!e(or+ :.0 is a standard part of Windo(s, the co!pany2s decision to !a+e s pport for r les a standard part of the platfor! see!s certain to !a+e this technology !ore (idely sed.
Partner 'olutions
#i)'al+ 3erver provides a tool called the # siness * le Co!poser for creating and !odifying #*5 r les. While this tool !ight be sed by b siness people, it2s typically a better fit for developers. 'he W1 r les engine also incl des basic r le a thoring tools, once again targeting developers. 'his section loo+s at alternative partner,provided tools that can be sed (ith Microsoft2s b siness r le technologies. .t2s (orth noting that so!e of the !ore broadly foc sed #$M vendors !entioned earlier also provide r les,related tools. $9Msoft, for instance, provides a W1 activity for invo+ing #i)'al+2s #*5, along (ith graphical tools for defining r les in either the #*5 or the W1 r les engine. 3i!ilarly, 3o rceCode,;2.net provides a #i)'al+ * les Co!poser for creating #*5 r les, then allo(s r nning the #*5 (ith a ;2.net (or+flo(. 'his section describes only partners that foc s specifically on b siness r les technology. RuleBurst .f the goal is to let b siness people create and !odify r les, and it often is, then (hy not let the! do this in the environ!ents that are !ost fa!iliar to the!& 'his is the rationale behind * le# rst2s approach to (or+ing (ith b siness r les. <sing the co!pany2s prod cts, an infor!ation (or+er can create r les in Microsoft Word, Microsoft 5/cel, or Microsoft 4isio. As the Word e/a!ple belo( sho(s, these r les are created in so!ething - ite close to nat ral lang age, helping b siness people !ore easily create and !odify the!.
.,
8nce a set of r les is defined in this (ay, it can be i!ported into * le# rst 3t dio, a tool that targets developers, then co!piled into the for!at re- ired by the #i)'al+ #*5. * le# rst also provides tools that help r le creators test r le sets, search the!, and !ore. All of these have the sa!e intent0 provide a !ore b siness,friendly approach to (or+ing (ith r les. 9nRule While * le# rst offers tools for the #i)'al+ #*5, .n* le provides tools that let b siness sers and developers create r les for the W1 r les engine. 'he screen shot belo( sho(s the r le a thoring tool for the co!pany2s .n* le for Windo(s Wor+flo( 1o ndation. As this e/a!ple sho(s, r les can be e/pressed in lang age that2s reasonably close to nor!al speech, allo(ing non,specialists to (or+ (ith r les technology.
2(
# siness r les engines have traditionally been sed to address so!e(hat speciali)ed proble!s, s ch as credit scoring and ins rance nder(riting. Microsoft2s decision to incl de the W1 r les engine in the .95' 1ra!e(or+ has the potential to change this, allo(ing r les,based sol tions to be sed in a broader set of scenarios. =et !a+ing r les !ore (idely sed re- ires good tools, and so co!panies s ch as * le# rst and .n* le have an i!portant role to play.
.nfrastr ct re for collecting infor!ation abo t in,progress b siness processes. #eca se these processes !ight rely on ! ltiple applications, this infrastr ct re ! st be sable (ith !ore than ? st a single (or+flo( technology. 'ools that let infor!ation (or+ers access that infor!ation. Different people (ill (ant to se #AM data in different (ays, and so the tools they se !ight be - ite diverse. 3o!e typical e/a!ples incl de dashboards that provide real,ti!e display of critical data, reporting services that present historical trends, and co!!on des+top tools s ch as spreadsheet applications.
2.
3ince the technology re- ired for #AM crosses diverse areas, it sho ldn2t be s rprising that it involves a n !ber of different Microsoft prod cts. 'hose prod cts can be gro ped into the t(o categories ? st described0
.nfrastr ct re for collecting infor!ation abo t r nning processes. 'his technology is licensed as part of #i)'al+ 3erver. Ei+e the #*5, ho(ever, the #AM infrastr ct re can be sed (ith both #i)'al+ orchestrations and any application b ilt on the .95' 1ra!e(or+. 'ools that let infor!ation (or+ers access that infor!ation. Whatever application the #AM data co!es fro!, it2s al(ays stored in a 3FE 3erver database, typically in a ! lti,di!ensional c be. 'his !eans that any tool capable of (or+ing (ith 3FE 3erver c bes can access and display #AM data. 'he !ost i!portant of these for #AM incl de Microsoft 5/cel, 8ffice $erfor!ance$oint 3erver, #i)'al+ 3erver2s #AM $ortal, and 3FE 3erver *eporting 3ervices. 8ther Microsoft prod cts can also be sed, s ch as 4isio, as can prod cts fro! other vendors.
'he fig re belo( gives a si!ple vie( of #AM in the Microsoft (orld, sho(ing the f nda!ental technologies in both of these categories.
Infor&ation Workers
&icrosoft $'cel
Other Clients
! & Services
!i"Talk Server
Orchestration ! & Database Data Transformation dapters BAM .ata BAM .ata
pplication (
! & Client PI
pplication )
! & Client PI
As the fig re sho(s, #i)'al+ orchestrations can directly generate #AM events and data, all of (hich are sent into a co!!on #AM database. #i)'al+ 3erver also incl des a tool called the 'rac+ing $rofile 5ditor that lets a developer config re an orchestration to send the desired infor!ation to this database. Along (ith b ilt,in s pport for sing #AM (ith orchestrations, #i)'al+ 3erver also provides a #AM client A$. that can be sed (ith any .95' application. "9o #i)'al+ 3erver license is re- ired for applications that se this #AM A$..% .n the e/a!ple sho(n above, for instance, the #AM A$. is sed by t(o other applications to send data to the #AM database. 'he prod ct2s ne/t release, #i)'al+ 3erver 200C *2, (ill add b ilt,in
22
s pport for sing #AM (ith applications b ilt on Windo(s Co!! nication 1o ndation or Windo(s Wor+flo( 1o ndation. Altho gh this forthco!ing W1 s pport for #AM isn2t sable (ith h !an (or+flo(s b ilt on Windo(s 3hare$oint 3ervices, it is possible to se the standard #AM client A$. (ith c sto! 3hare$oint (or+flo(s. 6o(ever it gets to the #AM database, data is al(ays stored in tables and c bes. C bes are !ost co!!only sed in data (areho ses, and so they2re typically seen as a b siness intelligence technology. =et #AM can also be vie(ed in this light0 .t2s real,ti!e b siness intelligence. 'he infor!ation in the c bes is accessible via a set of #AM (eb services, as sho(n in the fig re, and different clients are free to do different things (ith this infor!ation. An 5/cel ser, for instance, !ight read it into a pivot table, then create a graphical vie( of the aspects of this process that she (ishes to see. "#i)'al+ 3erver provides an 5/cel add,in to !a+e this easier to do.% 'his vie( can be pdated as often as necessary, allo(ing real, ti!e !onitoring of the b siness process. 8ther tools can display the data in other (ays. 8ffice $erfor!ance$oint 3erver, for e/a!ple, !ight display #AM data generated by one or !ore b siness processes as part of a dashboard. 'he screen shot belo( sho(s an ill stration of ho( this !ight loo+ sing $erfor!ance$oint2s # siness 3corecard Manager.
When it2s done (ell, an a to!ated b siness process that ses #AM can provide !ore infor!ation to the people (ho depend on it than if it (ere a !an al process. $eople don2t al(ays have the ti!e or the inclination to respond to stat s re- ests, b t (ell,designed soft(are does. .!proving b siness processes
23
(ith #$M technologies hinges on !a+ing the! !ore a to!ated, (hich i!plies an increasingly i!portant role for #AM.
6o(ever it2s done, acc rately describing a b siness process is an i!portant step in i!proving it. 4isio is perhaps today2s !ost (idely sed general,p rpose dra(ing tool, and so it2s not s rprising that this pop larity e/tends to doc !enting b siness processes.
24
onclusion
#$M has gone !ainstrea!. As its technologies contin e to spread, !ore and !ore organi)ations (ill se the! to !a+e b siness processes faster, less error,prone, and !ore reliable. 5ven in co!panies (hose b siness leaders haven2t e!braced a process,oriented perspective, #$M technologies can provide significant val e in a variety of .' pro?ects. Microsoft2s #$M offerings ai! at s pporting this !ove. Many c sto!ers rely solely on these technologies, (hile others also se the !ore speciali)ed prod cts provided by Microsoft2s .34 partners. .n both cases, the res lt is the sa!e0 better b siness processes and i!proved b siness res lts.
http0JJ(((.!icrosoft.co!Jbp!
<nderstanding Wor+flo( in Windo(s 3hare$oint 3ervices and the 2007 Microsoft 8ffice 3yste!0
http0JJdo(nload.!icrosoft.co!Jdo(nloadJ5JBJAJ5BA@D0BC,B77M,AD#@,LA1A, LA5CCAALCACAJ<nderstanding.doc
http0JJ!sdn2.!icrosoft.co!Jen, sJlibraryJaaAM02@B.asp/
Ascentn0
http0JJ(((.ascentn.co!
$9Msoft0
http0JJ(((.pn!soft.co!
3o rcecode,;20
http0JJ(((.+2(or+flo(.co!
* le# rst0
2&
.n* le0
http0JJ(((.inr le.co!
2*