[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [bcm] Brochure Draft; An opportunity to put into practice the BCM process
David,
I think you got most of it digested very well. However, SAIL is not a consulting gig, but a architecture resource center where re-usable solution templates are applied to betten enable the mapping of business needs to technical solutions via a lexicon. Service Component Templates are used throughout the process, and not just a bi-product. SAIL will adopt a series of methods that will be shared by the COI, and will become the defacto standard for those engaging SAIL. We have not specific tool in mind however, nor technology.
So, lets meet soon to discuss if there is interest. The white paper might provide more detail for you; www.ICHnet.org/sail.htm
john
John Weiler CTO ICH Architecture Resource Center +1-703-768-0400 (v) +1-703-863-3766 (cell) +1-703-765-9295 (fx) www.ICHnet.org www.SecurE-Biz.net
``And let it be noted that there is no more delicate matter to take in hand, nor more dangerous to conduct, nor more doubtful in its success, than to set up as the leader in the introduction of changes. For he who innovates will have for his enemies all those who are well off under the existing order of things, and only lukewarm supporters in those who might be better off under the new.'' Niccolò Machiavelli 1513 -----Original Message-----
John,
I'm just trying to understand the landscape from the SAIL PPT you sent around.
SAIL seems to me to be a toolkit for "How to do consulting to the government", and especially on agency level large projects - defining the requirements and the focus at a 70,000ft level. Comparing and contrasting - one particular focus of BCM - netcentric agile information systems - does not appear to be factored in the SAIL PPT as a main outcome from the projects reviewed.
BCM it seems is what happens after you have done SAIL and now need to find a way to realize the plan itself at the practical level. That is exactly where we are on the eprXML project - providing pieces to augment the deployment - and enable the business line managers to take ownership of the business rules and linking and switching controls of the day to day operations.
Also providing the means to have a agnostic deployment of technologies that cooperate and interoperate by applying the BCM principles and key technology aspects of templates, dynamic context, and choice points. And of coruse in the erpXML case - leveraging legacy systems by improving interoperability.
Also BCM is providing a method that is assimulatable directly by practitioners themselves throughout a Community of Interest - by providing the roadmap and the catalogue of pre-built templates and artifacts they can take and use.
SAIL on the other hand appears to feature significant hand-holding by SAIL experts who manage the process of using SAIL for a client.
So in summary - I would say that once a SAIL process has finished - then the Phase 2 becomes using BCM to deliver the actual systems.
Therefore the area of overlap is - how much can be garnered and deduced during the SAIL process to facilitate the following BCM stage?
Clearly identifying the community of interest, the stakeholders, the business goals and the authoritative sources, collaboration roles and products and services are things that SAIL and BCM share. So this is most of all the Conceptual Layer outputs - and so part of the SAIL process would be to provide those aspects of BCM templates.
However - once this is done - then BCM really takes over from there and allows the line managers to complete the job the executives and directors have shaped. BCM at this point is a method that practitioners then take on as their own, and embrace it as their modus operandi.
Thanks, DW.
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]