Skip to main content

Jan
31
2010

"Now to define the simplest basic requirement for handling unstructured processes –enabling processes with emergent models – i.e. the participants are building up the models as they execute process instances (perhaps with some loosely defined guideline or best practice as a starting point). I will claim the ability to do that is at odds with the basic definition of BPM, since it precludes a model based approach."

jisi.dreamblog.jp/2575.html
- Preview

bpm processes adhoc unstructuredprocesses humanprocesses

    • The participants change the general model (either the model or the rules) – this is very dangerous, and the more rigorous and complex the model the greater the chance to screw up something big time. It also doesn’t make sense since this really might be a one-off execution.
    • The participants have their own “local” copy of the process and they modify that. Still would be a lot of work for the participants, but there would also be all kinds of issues of multiple models existing for the “same” process – how to reconcile the changes, how do you store and access variants on a given model etc.
    • The participants do things “outside” the existing  model.
      1. It is outside the model, but under the control of the BPM engine.  This requires a whole set of new capabilities for the engine. The engine will need to be something much different than a standard BPM (BPEL or BPMN) execution engine. The engine will need to become something VERY different (I would think encompass something much closer to a collaboration tool) – and then of course figure out how to reconcile that back into the original process. It opens a whole can of worms from an execution perspective – and it certainly isn’t anything like BPM today.
      2. It is outside the model, and not under the control of the BPM. If this happens all the time then the model is not worth much, and neither is the engine.  So why start with the model at all?
  • Unstructured, ad-hoc human processes can’t be modeled (or at least in any cost effective way) so current BPM tools can’t really handle them. Managing human processes requires a different, complementary set of technologies – and a different mindset.
Aug
9
2009

ECM enables controlled, repeatable content publication processes, whereas social software empowers rapid, collaborative creation and sharing of content. There is a place for both in large enterprises. Sameer’s suggestion was that social software be used for authoring, sharing, and collecting feedback on draft documents or content chunks before they are formally published and widely distributed. ECM systems may then be used to publish the final, vetted content and manage it throughout the content lifecycle.

lehawes.wordpress.com/...ocess-and-ad-hoc-collaboration
- Preview

Ecm businessprocess socialsoftware enterprise2.0 adhoc collaboration adhoccollaboration process peoplecentrism ERP

1 - 3 of 3
Showing 20▼ items per page

Selected Tags

Related Tags

Highlighter, Sticky notes, Tagging, Groups and Network: integrated suite dramatically boosting research productivity. Learn more »

Join Diigo
Move to top