
In questi due giorni si nota un forte incremento sul numero degli accessi e delle pagine viste.



WebSphere Business Modeler possiede le migliori capacità di simulazione disponibili nel mercato, così sarà possibile aggiungere un nuovo livello di analisi alla definizione dei vostri processi.
La semplicità e velocità di Blueprint combinata con le funzioni di simulazione ad alto livello di WBM !!!
Molto bello!!!!!
Troverete questa nuova funzione nella videata di Export Data di Blueprint.
Per provare Blueprint gratis e senza impegni cliccate qui

Ciò è sicuramente vero ma come si vede da questo schemino ripreso da un blog russo (tutto il mondo paese!)

non sempre è colpa loro !!!
Cerchiamo quindi di dotarci di strumenti che sopportino lo sviluppo "iterativo" invece che quello classico a cascata e li faremo contenti.
Una domanda frequente che ci viene posta è sulla differenza tra coreografia e orchestrazione; vediamo di provare a dare due definizioni che possano chiarire il concetto.
Per prima cosa osservo che le due parole sono state scelte in modo accurato e rendono l'idea.
Orchestrazione: (come nel caso di una orchestra) esiste un direttore (sistema centrale) che dice agli orchestrali (servizi o sistemi remoti) cosa fare; la sincronizzazione è gestita centralmente
Coreografia: in questo caso, come nel caso di un corpo di ballo, ogni ballerino (sistema remoto/servizio) sa cosa deve fare e si sincronizza con gli altri ballerini per eseguire i propri passi. Quindi ogni singolo sistema remoto/servizio conosce casa fare e chi chiamare alla fine della propria attività

In un recente studio della società WinterGreen che ha analizzato i trend del mercato BPM & SOA si dice:
"Business process management (BPM) and services oriented architecture engine markets at $1.8 billion for licenses, maintenance, and services in 2008 are expected to reach $6.2 billion by 2015"


I would list them in reverse of the order Lombardi has listed them in their announcement:
First, increased notification options to keep you abreast of process modeling updates in your domain. Of course, I’d like to see an RSS feed as an option rather than just email-focused options, but combining the email notifications with a good email filter and you can get about the same result.
Second, additional properties to track against the activities of your process. Identifying systems, cycle time, cost, etc. That’s great… but by itself it is just documentation…
Third, leveraging those properties for heat-mapping and analysis of your process. This is actually the whiz-bang feature of the release, and shows how a small incremental improvement on a good foundation can really change the way you look at a tool. Prior to the analysis/heat-map, odds are you might just enter the data because it is “the right thing to do” to document the process for posterity (or for yourself). Now you have a reason to do it that is for the analysis of improvement opportunities. I’ll point out, however, that without reading the release note, it would have been easy to open Blueprint and not even notice the “Analyze” button, and the fact that you can choose which attribute to base your heat map on is easy to miss. But analysis mode works equally well on the process mapping view as well as the BPMN diagramming view.
What’s exciting about this release is that it offers a real reason to capture valuable data about your process… and it also opens the door for feeding information from your executing processes in Teamworks back to Blueprint for analysis (technical challenges remain, but it becomes increasingly obvious that this can be done)
"
Sabato scorso è stata messa in linea una nuova release di Blueprint. Ecco qui di seguito le novità:
The October ‘09 update is now available on blueprint.lombardi.com! This release has some exciting enhancements that I think will make Blueprint an even more valuable tool for discovering and sharing your processes. We’ve added a new process analysis mode, several new properties to the Blueprint documentation template, email notifications for changes happening to your processes, and a many more improvements based upon your feedback.
Let’s take a look the enhancements in detail:

You can find the Analyze button in the toolbar whenever you’re viewing a process. Give it a try and let us know what you think!




All of these new properties can be heat mapped onto the diagram using the new analysis mode, which can be extremely powerful. Need to highlight areas of your process with unaddressed risk points? How about the areas that will be affected when you decommission one of your legacy applications? What about the non-value added parts that are wasting money? Analysis mode can make answering all of these questions a snap.

You can choose which emails you’re subscribed to on your user settings page, which you can bring up by clicking your name at the top of the page in Blueprint. Give them a try and let us know what you think!

Un recente report di Forrester Research si è concentrato sul tema dei sistemi ERP maturi, per non dire obsoleti, che molti CIO si ritrovano come eredità di gestioni precedenti.
"La 'madre di tutti i problemi', scrive Forrester, è che il business evolve più velocemente del software ERP, sia in termini tecnologici che di best practice supportate.
Molti dei CIO intervistati da Forrester descrivono una situazione di scarsa standardizzazione ERP nelle loro aziende, con SAP e Oracle nella sede centrale e nelle divisioni e filiali più grandi, e il software di fornitori midmarket come QAD e Infor nelle sedi più piccole"
Bene utilizzare BPM come orchestratore delle varie instanze permette di gestire al meglio un ambiente con vari ERP senza spendere una fortuna per le integrazioni.


"This morning, the August ‘09 update went live on blueprint.lombardi.com! The team has been hard at work over the past month and I think you’ll be very happy with the latest improvements. We’ve improved the portability of your processes with the first shipping implementation of the BPMN 2.0 export format, added full text search across all of your process data, and made substantial usability improvements to Blueprint’s activity feeds based upon your feedback.
Let’s take a look the enhancements in detail:

And don’t forget: Blueprint also supports XPDL 2.1 to give you the maximum flexibility with your models today.




Our design team has been listening to your feedback and as a result we’ve introduced significant improvements to the usability of the feeds. They are much more readable now, making it even easier to skim them for the information you need. Similar entries are rolled up to save space and reduce clutter, the times of updates are always visible to give you better context, and filtering options have been expanded and improved. Try it out and keep the feedback coming! """







Un filmato vale più di molte poroleProcess Improvement is Everybody's Business
Our newest update moves Blueprint from being a great modeling tool to being the place for everyone in your organization to go for business improvement conversations. We've leveraged social networking concepts to facilitate the discussion about how each person can make their job better. Everyone can see and be notified about changes that are relevant to their work, discover relationships between what they do and the rest of the organization, and contribute feedback and suggestions to the community.
Product Tour: If you would like a detailed walk-through of the product, check out the 38-minute webinar and Q&A Blueprint Sr. Product Manager Dave Marquard recently conducted introducing Blueprint and the Spring '09 release.
Feature Details: For your reference, here are the details behind Blueprint's latest features:








It’s hard to describe how excited we are about the launch of Teamworks 7 at Lombardi. The excitement isn’t just about the big-picture value it will bring - it is about the advancements we have made in this release will make a difference to the people that are building processes in Teamworks day after day. Let me give you a few examples.
We’ve made it easier for authors that are just beginning to use Teamworks. How many times have you installed a new software product that gave you overwhelming numbers of buttons and menu options while providing no insight in how to use it?
The Authoring Environment in Teamworks 7 is redesigned to remove a lot of the noise and early confusion without losing the features that power authors need. You can see this from the completely new skin, simplified menus, and the way that Teamworks automatically organizes your process assets.
In addition, all authors now build their process assets within the context of one process app (project) at a time, which ensures that no one is changing assets that aren’t related to their projects.
There are a considerable number of changes we made to simplify some of the common authoring tasks while matching current best practices within the Teamworks community. For example, we simplified the way that integrations to external systems work by removing the need to create separate integration definition and connector components.
We have also introduced Teamworks Service types, including Human Services, Integration Services, Rule Services, and several others. This helps authors from making modeling mistakes like placing a service intended for human interaction into a system swimlane. We have also enhanced the data mapping capabilities to allow you to change activity implementations without having to redo your input/output data mappings.
We also added a lot of great new features that help new and experienced users alike. Many of these features like back-in-time, toolkits, and automated deployment are highlighted on our website, so please take a look there to see some examples of how these work. Our focus in adding these new features was to make sure that we added them in a way that makes sense for BPM and a model-driven architecture. We didn’t just bolt-on a version control system and tools designed to manage text-based code; we completely rethought how to manage changes to your process model as your processes evolve in a way that preserves the ability to build and iterate quickly.
Many of the features in Teamworks 7 were designed and built by people that have been on implementation teams for BPM projects and understand the challenges that many of you face each day. We think this release marks a major step forward BPM and for the experience of those that build processes every day. Let us know what you think.
Leggete nel link (mark a major step forward BPM) cosa dice Phil Gilbert nel suo blog.

Come sapete il tradizionale incontro con gli utenti di Lombardi quest'anno si svolge online.
