Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  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 maintain a model of our current Enterprise Technical Architecture
  2. Develop and and evolve and , publish and  evolve a model of the desired future state
  3. Articulate evangulize  evangelize a shared vision of the future
  4. Encourage architectural consistency and coherence across divisions

Organizational Impact:

  1. It will be the responsibility of the Directors to review their division program plans in the context of contributions to moving us towards the desired future.
  2. When making decisions on resource allocation (portfolio management) SRM will place considerable weight on whether or not the project or proposal moves us towards our desired future state.

...

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

...