Architecting the Office of Chief Information Officer

e-CIO is an "eat your own dog food" effort to architect the OCIO from the layers of business, Application, Data and Technology. The goal is to establish a common OCIO reference architecture for every OCIO

OCIO Business Architecture

From EA aspect, OCIO is a line of business where EA and IT management are the business functions

OCIO Process Architecture

From EA aspect, IT management and governance processes are considered as the OCIO business processes organized by the four domains of CobiT

  • Planning & organize
  • Acquire & implement
  • Delivery & Support
  • Monitor & evaluate
  • OCIO Application Architecture

    From EA aspect, IT managment tools are considered as the OCIO application systems. e-cio identify the existing tool vendors and suggest a collaborative effort from vendors to achieve a holistic solution.

  • EA tools
  • Applicatioin tools
  • Operation tools
  • Evaluation tools

    OCIO Data Architecture

    From EA aspect, EA meata model and CMDB are considered as the OCIO data architecture

  • EADB
  • PMDB
  • CMDB
  • EVDB
  • OCIO Technology Infrastructure

    The OCIO technology infrastructure serve as the entry point of Enterprise Information Technology infrastructure


    References

    The EA seeds from Roy Roebuck

    Sep 08, 2008

    Thanks for Roy Roebuck's generosity to share his EA work with the EA community in the notion of “Johnny Appleseed”. e-CIO will benefit greatly by leveraging on his works to achieve the purpose of OCIO Reference Architecture.

    There is nothing new under the sun, EA is also not as new as we thought. I am fortunate to recognize the Roy Roebuck EA's work before EA is known.

    Enterprise Management Architecture (EMA) and General Endeavor Management (GEM) Approaches

    Publications of Roy Roebuck

    Supported By One World Information System (OWIS)















    Posted by ecio under General
    1 Comment

    Why e-cio.org

    Jun 25, 2008

    e-CIO.org is a nonprofit organization to establish a common reference architecture for the Office of Chief Information Officer (OCIO) Line of Business (LOB). It is based on the concept to consider that Office of Chief Inforamtion Officer as a line of business The OCIO apply the enterprise architecture analysis in the layer of business , data , application and technology to eat their own dog food. IT governance and management processes are considered as the business processes; The IT managment tools are considered as the OCIO application systems; and the IT managment data are considered as the OCIO data architecture. The OCIO refereence architecrure is established to eliminate the redundant OCIO architecture effort by each organization.

    Wikipedia defines that

    “A reference architecture provides a proven template solution for an architecture for a particular domain. It also provides a common vocabulary with which to discuss implementations, often with the aim to stress commonality”

    The OCIO LOB reference architecture provides a proven template solution for the OCIO Line of business. It provides a common vocabulary with which many IT management tool provider can offer service oriented IT management parts for the integrated OCIO automation solution.

    e-CIO adopt Enterprise Architecture approach to analyze the OCIO Line of Business in the layers of business architecture, data architecture, application architecture and the technology architecture and establish a reference architecture via collaboration from different institution and vendors. It is suggested based on the following reason

    e-cio is the pivital LOB for information age. It enable the enterprise to make transition from the current stovepipe culture to the enterprise architecture culture.

    ocio lob

    The ecio value chain

    cio value



    Enable federated approach

    Most organization take the federated EA approach. A standard OCIO LOB reference architecture enable the integration of federated EA organization.

    Minimize the burden of governance

    OCIO must minimize the burden of governance by taking advantage of technology evolution and architected solution.

    Enable vendors to provide service oriented solution

    Vendors provide stovepipe IT management solution due lack of common standards. The OCIO LOB reference architecture establish the common standards in the areas of business function, data, application services for the vendor to provide IT management services. The OCIO LOB reference architecture only suggest the common services and building blocks.

    Eliminate the redundant effort of OCIO automation

    The OCIO LOB reference model enable e-CIO with minimum effort due to the limited resources. Most of OCIO have very limited budget because it is not considered as a business unit to generate tangible enterprise business goal.

    Eat your own dog food

    Although OCIO is responsible to aling technology with business and overcome the challenge of stovepipe system , most OCIO has not yet make transition to EA enviroment. The OCIO governance and IT managment systems are independent, Saying "do what I say and not what I do" does not serve well to get buy-in from the stakeholders.




    Posted by ecio under General
    4 Comments