...
One representative from each operational division will be designated Chief Architecture Planner for that division and be the primary representative on the Cross Divisional Architecture Team (CDAT). Each representative is expected to dedicate at least 10% of their time to this effort. They will be responsible for acquiring and maintaining knowledge of the technical and product architectures used across their division. They will also be responsible for informing CDAT about any projects or decisions that effect the enterprise technical architecture. A division may contribute additional resources to CDAT, however, there will be a single Chief Architecture Planner for each division. The division Chief Architecture Planner is expected tap other members of their division when specialized knowledge is required.
Each division Director will submit their intended representative to SRM. SRM will make the final decision on membership.
Reporting Relationship:
I still think that setting up he dotted line relationship to the Director of ATA would give the Chief Architecture Planners an enhanced sense of independence, responsibility and importance, however, if you guys can't live with it I will back down. Feel free to put some words in here.
Suggested Approach:
Start with a product, such as BlackBoard, and trace the architectural dependencies.