| Center for Technology in Government | ||
| | ||
| Information resources for information professionals: creating a knowledge bank in New York City government Who better to lead the way in breaking down information stovepipes than the IT profession itself? Read how a vision for knowledge sharing is coming to fruition in the Big Apple.
Introduction Until recently, the City’s IT-related work was very decentralized. Each agency figured out how to meet its own needs. Today, the City’s technology policies and strategies are set by a Technology Steering Committee (TSC) established in 1998 by Executive Order. The Steering Committee is charged with "coordinating and integrating information technology systems among City agencies" and with "effective implementation of automated solutions at all levels of City government." The Steering Committee members are the Commissioner of the Department of Information Technology and Telecommunications (DOITT), who is the CIO for the City and serves as the TSC's Chair, and the Directors of the Mayor’s Office of Operations(MOO) and Office of Management and Budget (OMB). The TSC is responsible for developing and implementing a city-wide technology strategy, overseeing the creation of annual agency IT plans and budgets, approving senior IT staff hires and promotions, coordinating IT initiatives, and setting city-wide technology standards. The Office of Technology was set up within DOITT as the staff arm of the Steering Committee. Among its responsibilities are the identification of best practices in IT use and management, and serving as a clearinghouse for information to agencies. Its major challenge is the collection, categorization, analysis, coordination, and dissemination of a vast amount of information regarding NYC’s current and future information technology resources and needs, including:
Much of this information is already available, but resides in various locations throughout the City government. Traditionally, some of that information was brought together on an ad hoc basis to be used to make decisions about a particular project. One example is information collected as part of the budgeting process. Information concerning costs, benefits, project scheduling, and so on would be collected by an analyst for the purpose of making funding decisions during the budget cycle. Once decisions are made, the detailed information would be normally put away in a paper file, possibly not to be seen again until the next budget cycle. The keeper of the information is usually a staff analyst, and as analysts come and go, so did the information that was collected. Similar procedures were used to manage information about the City’s IT resources. This information was collected by the Mayor’s Office of Operations or by DOITT. Each agency would keep the information in a manner designed to fit its own processes and priorities.
Addressing the core issue
Even outside organizations, like federal and state agencies, contractors, and nonprofit service providers, are affected by these conditions. Multiple contacts, handoffs, and interpretations add time and cost to these relationships on all sides. NYC Department of Information Technology and Telecommunication’s (DOITT) Office of Technology set about to change this situation and to replace it with a knowledge management program in which:
DOITT joined the Using Information in Government Program at the Center for Technology in Government to pursue these goals. The City project leaders expressed his philosophy in this way:
The best way to break the information stovepipes is to give people access to each other across the board. You can do this not only for IT but for other professions within the Cityfor the lawyers, the fleet managers, the human resource managers, and so on." By starting with the IT community itself, DOITT hoped to demonstrate that knowledge could be organized, shared, and maintained across time. The time dimension of the idea is of growing interest and importance as New York City joins the ranks of jurisdictions with term limits for its elected officials. (The Mayor, City Comptroller, Public Advocate, and most of the City Council will be leaving office on 1/1/2002.) The partnership project with CTG engaged the Technology Steering Committee and the City operating agencies in an exploration of the information needs of the City’s IT professionals, a search for models and best practices that would guide them to create new information resources, and initial work on intranet applications that would bring these resources to the desktops of City employees.
Organizational history and culture are part of the strategy for change That information is used to make executive decisions and city-wide resource allocations. Yet, that same information could be used in new ways to serve the needs of the agencies. Because DOITT was the lead agency in this project, it could have followed either an oversight strategy or a service strategy. The operating agencies initially expected an oversight frame of reference would predominate, but in fact DOITT pursued the project as a service to agencies. Early discussions and workshops were critical points for clarification about DOITT’s motivation and intentions.
Finding out what IT professionals need to know "What important questions did you need answered during your most recent IT project?" They then clustered their answers into like groups such as questions about procurement administration, IT expertise, and getting internal buy-in. Small groups then identified the kind of information needed to answer these questions. Following a similar process, the participants also answered: "What would be the characteristics of an ideal IT planning and approval process?" "What are your worst fears about the IT planning and approval process?" "What can you do, and what do you suggest others do to achieve these ideals and prevent these fears from being realized?"
Throughout the needs identification process, DOITT was careful to stay "out of sight" at the agency meetings. The staff believed that agencies would be more forthcoming with their needs and criticisms if DOITT staff were not in the room. The agencies did indeed speak freely at every session producing a detailed list of information needs that applies to any IT organization. The list included detailed information needs for nine topics:
Staff from both operating and oversight agencies worked together for the first time in a subsequent one-day workshop to identify priority issues and to establish work groups to formulate action items that address them. As the project made the transition to this "best practices" or solutions finding phase, the oversight and operating agencies began working together in joint working meetings. In some areas, oversight agencies took the lead, in others staff from the operating agencies played central roles. Several weeks later, each work group presented the results of its research and made recommendations for next steps. They particularly identified the recommendations on their lists that they felt were immediately achievable. These were the items that were within the purview and authority of the participants. They did not need to wait for any outside approvals, changes in regulations, or other time-consuming externally-controlled steps. The full group then selected from that subset of "doable" items the ones that seemed to be the best place to start to build prototypes for gathering and sharing information. They included staffing, procurement, planning and budgeting, best practices, IT products and services, data resources, and planning and budgeting. The TSC had already established formal subcommittees in several of these areas, but agency IT people had been unaware of them or reluctant to participate. Agency experience in these more informal workshops, especially the clear evidence that DOITT was listening and acting on their concerns, encouraged more agency participation in these groups. That engagement allowed the existing subcommittees on procurement and staffing to pick up the recommendations and move forward more quickly and with more comprehensive information than they would otherwise have done.
Technology choices are shaped by both policy and infrastructure While Web sites would be useful solutions for some topics, such as information about IT products and services, they were simply not feasible. As in many large governments, more than one e-mail system was in use so no agency could communicate readily with all other agencies. That made e-mail a poor choice for sharing information. Because the procurement process is often lengthy, DOITT also knew that these new resources would come faster if existing contracts could be used to acquire the development tools and applications software. One of the City’s foremost infrastructure investments is an internal network called CityNet which was being deployed during this period of time. CityNet offered a looming ability to connect all the agencies. Further, DOITT staff discovered that suitable knowledge management software was indeed available from one of the City’s main IT vendor partners. The best choice in terms of access and sustainability, then, was to develop these as intranet applications. Today, the CityNet infrastructure backbone is in place for all agencies. While full deployment is not yet complete, it will eventually be available to all participants. Building applications that run over this network also assures that they will rest on a critical, high-priority infrastructure for years to come. In addition, the chosen development tools allow for a very modular approach to developing the knowledge resources themselves.
A modular approach in a complex political and organizational culture The GIS resource is by far the furthest along. It benefits from a long history of knowledge and information sharing among GIS users in the City. Cooperative efforts to create a city-wide base map, for example, have been under way for some time. The leader of the GIS knowledge resource is also an acknowledged and respected leader in the GIS community. By contrast, the budgeting and planning resource will take more time to develop. The effort encompasses not only the collection and organization of complex information, but serious consideration of the need to revamp the policies and processes that underlie it. Moreover, legal responsibilities and long-standing institutional roles and relationships between OMB and the other agencies limit the nature and rate of change. The procurement and IT staffing resources are in the middle range of development but for different reasons. E-procurement has become a focus not only for IT professionals, but also for political leaders. The City’s ambitious e-government agenda means that procurements must be streamlined in order for elected leaders to meet their commitments to make City services widely accessible over the Web. In the case of IT recruitment and retention, the need to find and keep well-skilled staff is a very serious problem shared across all agencies, operating and oversight alike. Despite their different roles, there is much common interest in finding solutions.
What next? In 2001, New York City residents will elect a new mayor, who, like Mayor Giuliani, will be limited to two four-year terms. Consequently, the knowledge resources that are being developed in this project are more than meets the eye. They are certainly innovations in the management of IT. They may also be exemplars for accumulating and transferring solid knowledge about the City’s operations from one administration to the next.
| | |
|
| ||
|
Copyright © 2000 Center for Technology in Government, University at Albany,SUNY, 1535 Western Avenue Albany, NY 12203 | Phone: (518) 442-3892 | Fax: (518) 442-3886 | E-mail: info@ctg.albany.edu | URL: http://www.ctg.albany.edu Date last updated: April 10, 2001 | ||