Michael - As always, great insight. I believe that SOA doesn't include BPM, BI, Performance Management, I.T. Governance, Enterprise Architecture, etc.
SOA should facilitate master views of shared logic and data and enable a more scalable governance model. If SOA is done correctly, it should make it easier for your BPM to monitor operational activities while clean master data will enable Business Intelligence systems to analyze the business. IMHO, if you want to align business and I.T. use BPM, BI, etc. If you want to align your internal systems - use EA frameworks and good ole fashion SOA! In regard to relegating ownership, I have an oversimplified view. I.T. shops need to adopt an EA framework, undergo an SOA transformation, implement I.T. and SOA Governance, replace poor I.T. leaders and last but not least, show continual success for a sustained period of time to ensure that the program isn't undone. Easier said than done, eh? Jeff --- In [email protected], Michael Poulin <[EMAIL PROTECTED]> wrote: > > I think, this point of view substitutes one thing with another. SOA is not about how well you do your service (while it is important for the service provider) but why you do it at all? What for? The quality comes next. When one understands that SOA sets business rules of the game - bad/poor service leads to getting out of business - then s/he would know how to govern it, how to do alignment. > > It would be interesting to ask the author and mentioned gentleman - how to reach the point in organisation where all file owners agree to delegate their files to the "Filing Room clerks"? How to overcome ownership and relationship problems in IT and in business? > > - Michael > Gervas Douglas <[EMAIL PROTECTED]> wrote: << Using SOA to Align I.T. with Itself > > After much consideration, I've come to the conclusion that SOA is best > suited to facilitate "I.T. and I.T. Alignment" (not Business and I.T. > Alignment). That is to say, SOA (from an enterprise architecture > perspective) is better suited to align internal I.T. efforts with > other internal I.T. efforts. This might sound like common sense (and > hopefully it is), but SOA is fundamentally about sharing common logic > and data while facilitating accurate and complete client side > consumptions. > > I had a conversation with a gentleman the other day. I'll paraphrase > his comments... he asked me to imagine an enterprise without computers > or software systems. Instead, it had one Filing Room that people went > to when they needed to store or retrieve data. > > At the front of the Filing Room were people working the Service > Counter to fulfill your requests. In the back of the room were Filing > Clerks who kept the filing system organized. > > In this model it was assumed that the people in the Filing Room did a > good job of organizing their files, as to ensure that when a customer > asked for "all customers", they didn't have to go to 5 different > Filing Cabinets. It was the responsibility of the Filing Clerk to > facilitate Master File Management. The Chief Filing Officer was > responsible for making sure that the Filing Cabinets stayed organized > and on occasion were reorganized. > > The "Service" in SOA is the new filing cabinet. Our SOA Governance > Teams will work the front counter taking requests and also verify that > they filing clerks do their job correctly. They must ensure that the > portfolio of filing cabinets stay organized and avoid duplicate filing > systems. And ultimately, the CIO must be held responsible for the > state of the Filing Room. > > SOA is not a holistic EA framework, but it will provide the taxonomy > and organizational structure to become the foundation for a single > enterprise system of services.>> > > In cas eyou have not gone there, you can read Jeff's blog at: > > http://schneider.blogspot.com/ > > Gervas > > > > > > > --------------------------------- > Pinpoint customers who are looking for what you sell. >
