e-cio.org

The e-cio effort is to architect the Office of the Chief Information Officer business in a holistic enterprise architecture approach via LEA Enterprise Map. OCIO is not all about technology, they also should streamline their budget, acquisition, program management and governance process processes with technology cycle as described in the US OMB 25 POINT IMPLEMENTATION PLAN TO REFORM FEDERAL INFORMATION TECHNOLOGY MANAGEMENT.

The e-cio effort stream line the OCIO business processes and align integrated and consolidate automation solution to establish an robust OCIO capability in supporting all the other business units in the enterprise. Most OCIO still relies on stovepipe and labor intensive solution in budgeting, procurement , project management and governance. Under the rapid technology evolution , the out of date OCIO business practices have become a major obstacle to align with technology cycle. To keep up with rapid technology cycle, the OCIO have to review their policies and process in budgeting, capital planning and investment control, acquisition and project management. And further to align integrated automation solution with proper human resources.

This e-cio efforts architect the OCIO by adopting the LEA Enterprise Mapping approach. It architect the OCIO businesses, application, data and technology on architecture drawing as traditional architect do. On the enterprise map, The architects and stakeholder can design the OCIO architecture in a collaborative approach in a very human centric manner. Human can not manage well on what they can not see

The OCIO Enterprise map visualize the logical enterprise which identify the business functions, and processes. Most importantly, it identify the how the business function related to each other similar to a floor plan in a building design. It constitute the OCIO business architecture and allow the architect the OCIO application architecture to take advantage of integrated automation solution and also design the OCIO organization and human resources to support the OCIO business need. In addition, the enterprise map also describe the OCIO context to illustrate the OCIO business environment related to CEO, CFO and other organization.

In the discussion of evolutionary Metada/EA tool requirement ,

RoyRoebuck suggest to consider using an open-schema metadata modeling and repository tool, that is also open-source and free. One such tool is
onecmdb.

It is designed as an object-oriented configuration management tool for IT service management in compliance with ITIL3. It comes with data models for asset management and configuration item management, and has a content management module for documentation outside the metamodel
and its models.

OCIO Enterprise Architecture Map to render the OCIO big picture.




PDF file for detail

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)

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.

6.0 THE E-CIO ORAGANIZATION

The e-CIO organization is suggested at www.e-cio.org to facilitate the establishment of e-CIO architecture patterns and standards. The e-CIO organization is a proponent of in the school of stone soup. It facilitate the collaboration from both CIOs and IT management system vendor to make the soup of CIO architecture patterns and standards for the CIO community to share. The organization establish the CIO architecture framework and collect the straw man to intrigue the CIOs and the IT management system vendor for collaboration.

6.1 The CIO architecture patterns and standard place holder

The organization establishes the e-CIO patterns and standards place holder to facilitate the collaboration from common interest group. For example : The data model standards include the place holder for system catalog , the business process, the function, the location data model standards. The OCIO architecture patterns and standards are establish with inputs from the industry .

6.2 Leverage on existing industry standards

e-CIO leverage on established IT management and governance standard to establish the OCIO architecture pattern and standards. This include such as the ITIL standard and the COBIT standard. ITIL is

The Information Technology Infrastructure Library (ITIL®) is a framework of best practice approaches intended to facilitate the delivery of high quality information technology (IT) services. ITIL outlines an extensive set of management procedures that are intended to support businesses in achieving both high financial quality and value in IT operations. These procedures are supplier-independent and have been developed to provide guidance across the breadth of IT infrastructure, development, and operations.

The Control Objectives for Information and related Technology (COBIT) is a set of best practices (framework) for information technology (IT) management created by the Information Systems Audit and Control Association (ISACA), and the IT Governance Institute (ITGI) in 1992.

6.3 Establish CIO architecture patterns and standard via consensus

The organization establish the standards via the process of consensus which assure the standards is what the stakeholder need rather than been imposed upon. The proposes CIO standards subject to comments and suggestions by the stakeholders. Under the CIO architecture standard framework, the organization provide an item as the place holder with propose standards. Each item under the content management software allows comments and vote from stakeholders to become the standard. The thread of comments in each item serve as the records to sustain the legitimacy of the consensus standards.

6.4 The continues effort to extend and maintain the CIO architecture standards

e-CIO organization is suggested as the body to incorporate and maintain CIO architecture to keep up the need of all the CIO offices. It should establish a change management process which include the governing process on the revise, update, insertion, and delete of the CIO architecture standards under the framework.

6.5 The organization to certify the IT management system

The organization is suggested to certify the compliance of COTS components in plugging in to the common CIO architecture. To implement the CIO architecture, the CIO establish the CIO infrastructure first and acquire the COTS IT management components to plug in to the CIO infrastructure . Instead of each CIO office to find out the integration of COTS IT management components on their own, The e-cio organization can establish an integration lab to certify the compliance. The certification effort is a black and white decision based on whether it works or not in the lab environment