You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Polley's original charge

We should designate at least one person from each operating division (S&O, NCS, IS, ATSUS, Security) to serve as the chief architecture planner for that division.  These people should serve together on a CIT Cross Divisional Architecture Team, to be chaired by the Director of Advanced Technology and Architecture.  This team will be tasked with developing our architecture plans, standards and vetting cross-divisional IT issues.  The members of the team will each have a dotted line report to the Director of ATA for purposes of work on this team.  It is expected that the divisional architecture representatives will engage technical experts within their divisions as necessary to work on projects and issues.

Refinements

Scope:

Architecture is the high-level definition of the structure of a system, which is comprised of parts, their interrelationships, and externally visible properties.  This team will focus on Enterprise Technical Architecture which is defined as the description of the current and/or future structure of an organization's:

  1. Hardware, platforms, and hosting: servers, and where they are kept
  2. Local and wide area networks, Internet connectivity diagrams
  3. Operating Systems
  4. Infrastructure software: Application servers, DBMS, etc..

Architecture should not be approached in isolation. It is intended to address important Enterprise-wide concerns, such as:

  1. meeting stakeholder needs
  2. aligning IT with the business
  3. seamless integration and data sharing
  4. security and dependability
  5. data integrity, consistency
  6. reducing duplication

Goals:

  1. Develop and publish a model of our current Enterprise Technical Architecture
  2. Develop and and evolve and model of the desired future state
  3. Articulate evangulize  a shared vision of the future

Organizational Impact:

It will be the responsibility of the Directors to review thire program plans in the context of contributions to moving us towards the desired future.

When making decisions on resource alloaction (portolio management) SRM will place considerable weight on whether or not the project or proporal moves us towards our desired future state.

Team Makup:

One representative from each operational division will be designated Chief Architecture Panner for that division and be the primary representative on the Cross Divisional Architecture Team (CDAT).  Each representative is expected to be dedicating at least 10% of their time to this effort. They will be responsible for aquiring and maintainig knoledge of the techncial and producd architecueres used across their division.  The division  Chief Architecture Panner may tap other members of their division when specialized knowledge is required. 

Each division Director will submitt their intended representitive(s) to SRM.  SRM will make the final decision on membership. 

Use

  • No labels