Val Oveson, State CIO, has asked me to chair a group to develop the tactical implementation plan that will enable us to achieve objectives outlined in the most recent Utah Strategic IT Plan for the first of seven goals. The goal is the delivery of online (eGov) services. The fourth of four objectives is: Collaborate with federal and local agencies to bring services, products and information online. We will begin this discussion at the Product Management Council on August 13th.
As I begin to ponder this objective, I thought of developing an enterprise collaboration model, one that would identify how we are currently collaborating - not only with federal and local agencies, but also among ourselves (state agencies) and with other business partners. Then identify what is effective, why and how, what can be done to increase the overall effectiveness of collaboration within the enterprise and how it can impact the delivery of services to citizens and other customers of government services. In the past, I have made several attempts to organize and enhance this type of cross-agency, vertically and horizontally integrated collaboration. Probably the biggest effort was during the two years prior to the Y2K rollover when we attempted to insure that all aspects of government and society were adequately prepared (I was the State Y2K coordinator). The effort was significant, but it worked as people came together who had never worked together before in ways that they had never done before. And then it was over and we forgot.
What can we do to make this kind of focused effort happen dynamically to quickly create online services and solutions that extend vertically across government. We need data, organization, strategy, energy....
The OASIS Object Management Group issued a "Web Services for Enterprise Collaboration" RFP last year that touches on some very interesting concepts. The goal is to improve enterprise collaboration in the following areas:
(1) High level support for understanding and documenting collaborative business processes. (2) Loose coupling between independent parties in a collaboration (3) Tighter cohesion in the software development life-cycle between design and implementation processes and artifacts. (4) Consistency in the way WSDL is used to implement collaboration. (5) A standard way to use UML for web services WSDL specifications. (6) Enhanced WSDL support for asynchronous interactions based on CCA semantics. (7) Automation of the development process from design to implementation. (8) Faster, more deterministic development processes. (9) Ability to adapt to changing business requirements. (10) Ability to adapt to multiple and changing infrastructure technologies. (11)Full life-cycle tool support...
In a way, we might consider OASIS itself as an effort to improve collaboration of the global enterprise in order to develop a framework for global IT initiatives.
Predominant tools for collaboration within the State enterprise (current practice):
- phone conversations (one-to-one and teleconference)
- websites (some collaborative websites such as PATH, weblogs)
- wireless communications
- project management tools
- Instant messaging services (Groupwise and AIM)
- Streaming video
Food for thought - references
Questions to be answered:
- What groups already exist?
- How can we extend the momentum of the PMC into enhancement of our collaborative activities with local and federal partners?
- What is the role of UII in this effort? ITS? the PMC? ACIO Council? GIS Council? the cabinet? the enterprise project management process?
- Are there advanced systems of enterprise collaboration that we are not taking advantage of?
I'm not quite sure yet where these thoughts are leading me, but I hope it is well beyond the simple creation of an Intergovernmental IT Council which we did several years ago. It didn't persist.
- Project level collaboration
- Business process collaboration
- Systems-level collaboration
- Idea sharing and generation
- Creating virtual dynamic networks
- Creation of key repositories
Read this article from Portfolio Knowledge