Robert Julius Condemi

Enterprise-wide Information Technology Architecture

Delivering Controlled Change


Value - Development - Methodology - Document Description

Information Technology Architecture Development


Description

In today's competitive environment, effective and efficient use of information technology must be the focus in building successful organization strategies.   Organizations need to begin the process of creating such an information infrastructure by creating comprehensive Enterprise-wide Information Technology Architecture (EWITA) as the map, guiding direction for future information technology decisions.  I assist organizations in creating such an Information Technology Architecture and technology strategic plan.

Product Use

The rate of change in the business and processes of distributed complex organizations is accelerating.   Organizations driven by competitive pressure need to offer better customer service, increase operational efficiency, and realize the benefits of integrated enterprise knowledge.

The enabling Information Technology (IT) is not evolving and adapting rapidly enough to support these changing business requirements.  What is needed is an adaptive technical infrastructure, a fundamental rethinking of the IT development process, and an IT organization structured for the future. IT development must be driven top-down by the business through an Enterprise-wide Information Architecture (EIA).   This EIA provides the required guidelines and standards.  In addition, EIA provides the infrastructure for communication paths, interoperability mechanisms, technology support, and development processes for success.

Through the efforts to create an Enterprise Architecture and infrastructure plan, the IT organization will become better aligned with the business units.  Thus focusing on a common business vision and structure to respond rapidly to changing business requirements.  Such an adaptive infrastructure creates the Information Technology environment required by businesses to maintain a sustainable competitive advantage for the future.

Approach

Typically, I apply a top down process model in collaborating with you to ensure that your Information Technology environment aligns with the directions and requirements of your business.

 

Phase I: Identifying the Business Drivers and Information Requirements

The process of defining such an information environment begins with an understanding of:

I review existing documentation and conduct interviews with the essential individuals that can provide insights into one or more of these topics and issues.

We leverage any strategic documents that your organization has already created and work closely with your team on this effort.  In our discussions, we explore the processes, technology, and issues that drive each department, the interaction among departments, the sharing of information, and the vision each has for the strategic use of Information Technology.  The discussions reveal issues with your current IT infrastructure and the requirements for the future as defined by the business drivers.

 

Phase II: Documenting Business Drivers and Architecture Requirements

After the initial meeting(s) I work with you to understand your current IT environment, initiatives, and long term plans.  The interviews, group discussions, and existing documentation help provide the information necessary for me to establish an understanding of your existing application technology systems and current operational issues.  In addition, the processes by which, or through which, your staff uses such.

This project phase documents the current state and processing issues.   It results in a defined set of business drivers and technology vision that drive the development of Conceptual Architecture principles.   Working with you, I document your business drivers and future vision for your organization.  We then map these business directives to a set of business information requirements and desired Information Architecture characteristics.  This is your Business Drivers and Architecture Requirements deliverables.

 

Phase III: Creating and Documenting the Conceptual Architecture Framework

We then create the Conceptual Architecture principles from these business information requirements and industry best practices and trends.  We use industry best practices and trends as frameworks, guidelines, standards, and structures.   This creates conceptual principles that apply across all technology domains (component principles of model used in Phase IV).  Focuse is on: applications, data, infrastructure, and management.  Based on industry experiences we can separate hype from reality and guide you in the right direction.  This deliverable document is your Conceptual Architecture.

 

Phase IV: Creating and Documenting the Domain Architectures

Having the foundation in place, we then explore the Domains (components of this model) including but not limited to:

 

Phase V: Gap Analysis, Strategic Plan and Initiative Options

I next work with you to perform a gap analysis.  This creates a strategic plan detailing initiatives, migration, and transition options.  In this effort, we explore how best to leverage the investment in the current legacy technology while migrating to the new adaptable vision infrastructure.  This planning effort includes organizational issues as well as technology ones.  It results in a prioritized set of project initiatives that help effectively move your organization towards your future infrastructure state under the guidance of the Technical Architecture.

Summary Of Deliverables



Robert Julius Condemi

P O Box 604

Upton, New York 11973-0604

Tel ... 516 909 RJC1 / (7521)

E-Mail comments and inquiries to

rjc@robertcondemi.com

 

go back...   ...go forward

go to RJC Information Services Integrator / Enterprise-wide Information Technology Architecture...

go to Robert Julius Condemi Home Page...