EA Scope and Direction

I've been thinking about what my scope and direction should be. I'm a one-man team so I can't take on too much but I still need to deliver value. Here are my thoughts:

Roadmaps Drive Everything (Roadmaps are 5-year release plans for the key applications in our portfolio. They are grouped by business area)
-- Update and maintain the roadmaps
-- Meet quarterly with each area to update them
Research to stay ahead of the curve
-- This will be more challenging without any for-pay analyst services
-- Focus on Open Source technology options and research requests
Use the ARC to drive technology standardization and adherence to the Roadmaps
-- Re-launch a “kindler, gentler” ARC with new members
-- Make it smaller and lighter and leverage existing PMO docs
-- Use ARC Consultations to deliver short-term benefits to project teams
Cultivate and leverage internal standards-driving groups - CAB, Matrixed Security Team, Integration Team, Dev Standards Team.
Maintain Blueprint and One-Page Standards Document
-- New Blueprint launch Summer 2009
-- Share the One-Page Standards document in March
-- Keep the One-Page doc up-to-date and share it with everyone
Technology Sunset Planning

I'm worried that this may be too much. I'm going to have to leverage other people who may have some time. I'll build out a new ARC Core Team. Keep it small with maybe four people including myself. See if they can help with some ARC Consultations and meet weekly to discuss review strategy.