MINUTES OF THE INFORMAL MEETING OF THE JOHNSON COUNTY BOARD OF SUPERVISORS:
FEBRUARY 28, 2000
REPORT FROM FARRAGUT SYSTEMS, INC. VICE PRESIDENT WILLIAM CAMPBELL AND GIS CONSULTANT JEFF HANSON: GEOGRAPHIC INFORMATION SYSTEM NEEDS ASSESSMENT FOR JOHNSON COUNTY
TABLE OF CONTENTS
Chairperson Stutsman called the joint meeting of the Johnson County Board of Supervisors and the GIS Subcommittee of the Computer Committee to order in the Johnson County Administration Building at 1:12 p.m. Supervisors present were: Jonathan Jordahl, Mike Lehman, and Sally Stutsman; absent: Charles Duffy and Carol Thompson. GIS Committee members present: Supervisors: Lehman and Stutsman; Deputy County Assessor Bill Greazel; County Auditor’s Office: Auditor Tom Slockett, Deputies Chris Kahle and Mark Kistler, and Map Delineator Gale Kramer; Information Services: Director Jean Schultz, Deputy Director Gary Yoder, Network Administrator Bill Horning, and GIS Committee Chair Fred Brown; Planning and Zoning Administrator Rick Dvorak, Department of Public Health: Director Graham Dameron and Disease Prevention Specialist Elizabeth Miller, SEATS Assistant Director Burnell Chadek, and Secondary Roads Assistant Engineer Al Miller.
Recessed at 1:13 p.m.; reconvened at 1:24 p.m.
Introductions were made. William Campbell and Jeff Hanson of Farragut Systems, Inc., Longmont, Colorado, presented the draft version of the Geographic Information Systems (GIS) Needs Assessment to the Board and the GIS Committee. Following summary points outlining the report is the discussion regarding those points.
Farragut Systems, Inc. Vice President William Campbell: Just a couple of quick notes. I’m primarily going to turn this over to Jeff and let him talk about the report. We’re basically going to go through pretty much all of the information in here. But I wanted to talk a little bit about what the process is that we’re going to end up following. I provided, the report that you have in your hands, at least some of you did, we provided soft copies of the departmental reports early in the process, and each one of those things that we reviewed individually by the departments, we’ve incorporated those comments back into this version. Now those departmental reports actually formed the basis of the information gathering phase of this and they’re all in section 2. So again, if you read through section 2, you’ve seen a lot of it. Now, the recommendations themselves, and what we proposed, how you guys roll out GIS starts in section 3. So that’s really the meat of the report for you, sections 3 through 9. A couple of quick notes. In a report like this there are always going to be changes. There are going to be changes that you guys request of us over the next couple of days. You guys are going to notice some things in there that you may object to or something similar to that. This is part of the process. You end up, you take a good shot at this thing, you guys take a look and there might be bits and pieces of this report that you may take objection to. You may look at it and say, you’re categorizing this thing as a low priority and shoving off developing for 3 or 4 years. That wasn’t our attempt. We want to see development take place (inaudible) sooner. That’s fine. There is some natural give and take when we deliver a report like this. We’ve taken a good clear shot of it. We’ve put it onto a 4-year implementation cycle. Now clearly, that depends on budget. There’s nothing to say that you can’t compress that time frame or you can’t extend it out. But that seems like a reasonable time frame to try to implement. With that in mind, I’d like to, kind of turn it over to Jeff and let him start to go through the report. A quick note, we found a couple of typos in here, so if you find any more, please let us know. Also again, there are going to be some modifications over the next couple of days. Our plan is to provide you with a final copy at the end of this week. We would like to send you back the final copy on Friday. So that would 15 bound versions. Again clearly, we’re probably going to pick up some changes in this meeting, we’re probably also going to pick some modifications to it on Wednesday as well. Another final note is that a report like this can’t be considered as static. When you guys finally get this thing and hire a GIS coordinator and you’ve got to periodically go back to the implementation plan and do some updates. Technologies change and your budget can change. If we would have put out a report like this 3 years ago, we would have completely ignored Web-based mapping because the tools just weren’t in place to do it well. They’re out there now. In another 3 or 4 years there’s likely to be a lot better tools out there for other types of applications. So it may be that one of these applications we put in here and labeled low priority, all of a sudden a base ArcInfo product covers them in another year. Again, you can’t consider this a static report. You have to periodically go back to it, review it, look at the assumptions, look at the technology as well and make modifications. Gives you a blueprint, but a 4 year technology blueprint changes a lot. So with that I’ll turn… yes?
Slockett: We do have some modifications. I was just wondering what process we should use. It’s not necessarily going to be productive to point them out right now.
Farragut Systems, Inc. GIS Consultant Jeff Hanson: Wednesday morning is…
Brown: 8:30 to 11, we have a meeting scheduled with Jeff. At that time we can bring up any changes we need to make in the document and express them there.
Hanson: If you think something is unclear or you’re not quite sure of…
Campbell: Or if you disagree with the priorities, we will be taking a first crack at priorities. That’s bound to occur.
Slockett: Just some definitions and things.
Campbell: OK.
Slockett: Tasks of our, duties of our office and so forth that need to be tweaked a little bit.
Campbell: OK. Send it over to Jeff.
Develop Implementation Plan
Hanson: I’ll present. Bill will be pitching in as we go. I’m just going to, the first few slides are just project overview of what we’ve done to date. The scope of the project, I’ll start with requirements gathering, and that’s when we conducted the needs analysis interviews. Those were conducted December 14th through the 20th 1999. The analysis phase, which we’ve been working on since those interviews were conducted were broken out into characterize and prioritize the applications, characterize the data requirements for those applications, OK. We’re providing staff development and training recommendations, develop GIS software recommendations, schedules and benchmarks, which is, I think, section 8, which is the implementation plan, and that’s a 4 year plan we’re proposing. And then there’s a section 9, organizational strategies and responsibilities. That wasn’t part of the contract, but I’ve gone ahead and written that up, so we just went ahead and included it.
Campbell: We messed up. It was dropped as part of the contract, but we ended up, Jeff and I did not communicate on, and we ended up writing it (inaudible).
Hanson: There was a lot discussion, so it’s in there. Then today’s presentation, documentation presentation, with a follow-up Wednesday with the GIS Committee.
Dameron: We got something free?
Hanson: Yes.
?: So far.
Campbell: Nothing is really for free.
Jordahl: There may be some implications later.
Hanson: The methodology that Farragut Systems uses for an implementation plan or a needs analysis is to begin with the department interviews. What we are looking at is your information needs and your application needs. We want to determine what determine what applications are required by each department to help them with their business processes. From the application needs, we then can go down and identify what users are those applications serving. What existing skill sets exist in that department, and how can we leverage those skills when we roll out the applications and implement GIS within the department. We prioritize those applications. High, we’ve got a high, medium and low priorities, and then we determine application requirements. A key component of that is the data. What data do you need to support the applications that you’ve identified as high priority or as a priority in your department. In conjunction with that there are software requirements. What software platform are we going to deploy these applications in? Then the (inaudible) would take into the hardware platforms, the networking environment, what training’s involved for your staff, and what type of rollout schedule or implementation plan applies for that application. Then from that information we develop an implementation plan, which is your schedules and benchmarks.
Departmental Interviews
Hanson: The user needs analysis in December, these are the departments that we had formal interviews with. Each department ranged from one hour to up to 4 hours. Actually we spent 8 hours with the Auditor. We spent an extra 4 hours going over the parcel management workflow. Workflow was not specifically part of the contract for us to present, but there are discussions in there and it’s part of the plan about when to address that in the parcel management process. In the interviews, each department was asked specific questions regarding their current data uses. What data are you maintaining now or you might have in CAD or GIS format? What data do you wish you had? Or what are your requirements based on your application needs. To identify what applications the GIS needs the department perceived they had or currently had. What were your software requirements, who were your potential GIS users, and what workflow issues you had. The responses and summaries for each department are in the first, or section 2 of the report.
Department High-level Mid-Level Low-Level Total
Auditor 11 5 5 21
County Assessor 1 6 3 10
Iowa City Assessor 3 0 0 3
Ambulance 6 2 0 8
Health 8 3 0 11
Information Services 0 0 4 4
Planning and Zoning 3 2 1 6
Recorder 8 0 0 8
SEATS 5 1 0 6
Secondary Roads 12 4 3 19
Sheriff 3 0 0 3
Totals 60 23 16 99
GIS User Classes - Implementation
Hanson: During the interviews, and we’re going to be talking a lot about the user classes. It drives the training and the application development. For the interview process, when we first came in, we just broke it into 3 general classes, a high-end user, a mid-level user, and a low-level user. Your high end user is someone who is going to occasionally use the GIS, that might be coming in through a Web browser. Just doing some quick queries, trying to locate a parcel, trying to see how something is zoned, finding something by address. Your mid level user, is going to do, they are going to perform queries, some analysis and display and might use reporting and mapping as part of the daily decision making process of the department. They may also perform a limited amount of database maintenance. By database maintenance we are referring to either adding spatial features, updating spatial features, or doing some database work, updating maps. Changing an owner name, changing information on water well or wastewater systems, and zoning apps. So these mid level users might be a little more involved in the database use than just kind of looking at it. They might through a custom interface be creating maps. Your low-level user is someone who is dedicated to the database development. Mark, Chris, the people in the Auditor’s have been doing a lot of parcel management. The guy in zoning who has been doing a lot of the CAD work for Zoning, Secondary Roads, people using the Eagle Point software and AutoCAD. They’re hands on. They’re really getting into the guts of the GIS, the data, the software, all the real low level technical needs are addressed by those people. They also assist with the specification of application requirements and the design of map products.
Slockett: Could you just explain a little bit why, how you, why you named them like you did, because I could see naming them exactly flip-flop way.
Hanson: I always say high level is not using it quite as much. They’re just, they don’t have as much training or experience, they just want to start something up and find something and look at it.
Slockett: OK.
Hanson: I just say lower is closer to the technology.
Slockett: OK.
Campbell: But you’re right. I’ve seen them flip-flopped.
Hanson: Yes. We use these, again, for the interviews, just at that point, when you first start talking to a department, to keep broad categories. You’ll see in the report that we break them out into more formal definitions. Based on those interviews, the County departments have identified about 99 potential GIS users. This is the breakout by department. You can see the Auditor has 21 potential, the Assessor 10, Health had 11, and then within that high, mid, and low level users. That’s actually a fairly large number of potential users. That does not include the general public or external users, like (inaudible). For the implementation plan then, we’ve taken those 3 broad categories and broken them into 5 more formal definitions of the user classes. These user classes are used in defining the applications and prioritizing the applications. It’s also used in the implementation plan and for data requirements. The GIS specialist is your low level user. That’s someone who is going to get trained in ArcInfo. They’re going to be working at an ArcInfo workstation, and doing parcel splits and combinations, entering zoning information, doing road design. He’s someone who will be using ArcInfo, maybe AutoCAD, maybe custom mapping maintenance applications, a third party product like NovaLIS Parcel Manager. They’re going to be down working in the GIS products. They’ll need to advanced training. It’s also probably the smallest class of users.
Jordahl: I’d like to suggest, for your phrasing of this in the future, that it might be more expressive to talk about a deep level of user than a low. The low is sort of pejorative, you know, you’re just not really very good, or something, when in fact these are the most technically trained people. FYI.
Hanson: Right. Your advanced GIS user is someone that will be doing analysis and mapping capabilities. They might be doing some data maintenance. They are more likely to be working through, say, an ArcView interface, or a forms-based application for a spatial or for a relational database. They will be managing data, not to the degree that a GIS specialist will. They will be making maps to maybe help them to define application requirements for your department. Maybe doing some map design for the department. Your advanced GIS user- we are going to get the training later- would take some formal training classes, probably in ArcView, the formal 2 day ArcView training class. Your specialized GIS user is someone who is only going to be working through an application interface. They might make a map, but it’s going to be through a custom interface. They probably aren’t going to be doing any type of database maintenance. They’ll do a query, display information, set content, maybe generate a tabular report and then print a map and take it to a meeting for the department. That type of user usually gets training just on the application. Not to the same degree, they probably would not attend an ArcView training. The general County user would be someone who would just come in now and then do, it’s equivalent to the high end user. They’ll come in and want to locate a parcel. Find out what it’s zoning is, who owns it, what’s the address. Then your external user is the public, the developers, people now who are coming to the counter, looking up information. They are more than likely going to be using the Web browser, the Web
interface.
Hanson: The next step was to identify application priorities. We’ve broken these into high priority applications, County-wide applications, departmental applications and then low priority applications. The high priority applications are directed towards database maintenance and mapping, and then query and view. The high priority applications are targeted for the GIS specialist user class. You want to get these guys the tools to start maintaining the database, mapping the database, producing the maps that the County is either mandated by the State to produce, or that the County departments are using on a regular basis. Your plat maps, your ownership transfer maps, your subdivision maps, that type of thing. The query and view, on the other hand, targets your largest class of users, which is the general County user and external user, public user. So we’re getting the GIS deployed out so people can start looking at it and becoming familiar with it.
Campbell: This is similar to how we approach a lot of these. We try to get the most bang for the buck early. If you look at trying to deploy an application, a simple query and view based Web mapping application, it gets out to the most number of users faster. So people can get onto the Web, pull up the parcel, look at the zoning on that parcel, look at the address, that kind of application. Generally, what we’ve found is that usually (inaudible) 60 to 80% of the users within a County or municipality (inaudible) application (inaudible). Simple viewing application, bringing it in off the Web browser bringing it off Internet Explorer, having the whole address search routine, so you can look up an address, look at the parcel by PIN number, by owner name, that type of thing. That satisfies a fair amount of users. So the idea in this is to get the most bang for the buck the quickest. Get the tools in place to take care of your data and get the tools out there so that the general County level user can get in there and look at data. The other thing that we do here by focusing on 4 different classes of application by priority, County-wide, departmental and low priority, is you can have a heck of a GIS set-up, just… these are in order of priority. You can have a heck of a GIS setup by just attacking the first couple of these. If funding gets stretched out or funding gets cut somewhere down the road, you’ve still got your database and you’ve still got a high priority application there so that people can look at your data. If you never get to the departmental applications because of finding cuts somewhere down the road, you’ve still got yourself a good, workable system. So that’s one of the reasons we also try to get the broadest applications out first.
Jordahl: How soon would that be possible to have out? Because when we budgeted this thing, we basically cut out the Web-based application in the first year, thinking, well, we’re going to be developing this during the first year, we wouldn’t be able to put it out anyway, so let’s fund that in the second year. Are you saying we could have that Web-based map of the County out there within a few months?
Campbell: You could. It depends on the priorities. Right now we’ve got them established in terms of the high priorities in the first 12 months.
Hanson: It’s in the implementation plan.
Campbell: Database is first 12 months and the high priority applications the first 24 months.
Jordahl: So we could still get around the funding.
Campbell: Yes. It’s nice to do that as soon as you can. There have been a lot of GIS’s out there that have failed for lack of getting data out to the user. The sooner you can get useful information out there to somebody, the sooner they can start dialing the parcel, start using the data, the more they’re going to pull out of it.
Hanson: You can go pull something up through your browser instead of trying to find the map (inaudible). You get people familiar with the GIS. The County-wide applications are requirements that span multiple departments. Those requirements are general mapping application. You want to make a map, you can choose what the content is. I want to turn on these spatial features, I want to maybe link these databases and I want to make a map, and I can customize that map with different page size and orientation. I can also query a data and create a report if I wanted to. Other, we’re going to go into these in more detail. There’s the mailing label application, just for public notifications, and then the general data maintenance. One thing we do in our application philosophy is, as we go from the database maintenance and mapping, give the tools to the specialists, get the general viewing out, as we start moving into County-wide and departmental, those applications can be developed form the core applications or the underlying code in the previous priorities applications. If you develop a parcel maintenance application, say for the Auditor’s Department, to do their splits, combinations, entering subdivisions, as we migrate to what we call the data maintenance, which is the more generalized maintenance tool, a lot of the tools developed for that parcel maintenance can be incorporated into that data maintenance. It’s a corporate philosophy we have called spiral development, where you just keep laying the building blocks and building the applications as you go out. The applications in the County-wide, the general mapping, and general data maintenance, as we move into departmental applications, and these are the specialized requirements of individual departments, if we did a water well and wastewater system tracking system, a lot of the code that went into that general mapping could probably be pulled into that application and maybe just deliver it as an ArcView extension or MapObjects plug-in. So you’re not going to keep redesigning the wheel, rewriting code, you’re going to be taking that technology previously developed for County-wide and start taking that and making modules for the different departments. So, it should save on the application development costs. But the departmental, where all the specialized requirements of the individual departments, these are applications that other departments maybe will not use. They might. But it’s really targeting a single department. Part of that, the specialized requirements doing further database development. If you want a water well, wastewater system, you need to take the information that’s on those location cards and get them the spatial formula. If there’s a zoning management and integrated building permit system, you’ve got to convert the Zoning data that’s in AutoCAD format into the central database, the SDE or ArcInfo coverages. There’s database development associated with those applications. Then, low priority applications are ones that have significant dependencies. Either there’s a lot of database development, they’ll demand some workflow re-engineering, the integrated parcel and real estate application, which we’ve set as low priority. That’s going to take a lot of workflow reengineering. It might be dependent. It’d be dependent on if the data is there. The E911 application. You’ve got to have a good address database in place before you roll out that application. So, the high priority applications we’ve identified are the parcel maintenance interface. Once you start developing the parcel database, given the number of subdivisions and deeds that you’re processing, and the increasing number, you’re going to need a maintenance (inaudible). You do not want to translate this data to an ArcInfo format and then one year later go back and start trying to catch up with the splits, the combinations, the new subdivisions. You need to have that in place and the parcel layer, the parcel related layers are probably going to be your base layers for your GIS. Everyone’s going to want to look at parcel information and they’re going to want to look at correct parcel information, and current parcel information. So you need to have that maintenance interface in place. That can be an application developed from scratch or something bought off the shelf, like the NovaLIS module. Parcel mapping. This application is going to target your requirements for your State mandated maps. Your plat and subdivision maps. Your transfer book maps. I think those could be automated. If that’s an automated application where you can go out and recreate those maps and send to them a queue and plot them, you’re going to save time for your GIS specialist in the Auditor’s Office, because they’re going to be pretty busy folks. So you’re kind of freeing up resources then. The internal web map then is targeting your largest class of general County users. You want to get something out to them, shortly after that database has been developed or right before the completion of that database development. As that database is starting to become finalized people are going to start having a demand to look at the information. Then, the public information web map, which would be developed off of the internal web map.
Campbell: The big difference is in the public information Web map is realistically the amount of data that’s out there. They’re typically the same type of application. There is typically a lot of times (inaudible). You may simplify it a little bit for the external user because they can’t walk down the hall and ding on somebody and ask them how to use it. But, in general, it’s the same applications built off of (inaudible) technology. But, what you often do is restrict the amount of data that’s out there on the external (inaudible). You may have data that’s not available to the public. You don’t want it available to the public.
Hanson: There has been some discussion of setting up a fee, being a subscription service, for that information. That would be part of the design of the public information web data. If you want to allow some information to be provided to the general public, it’s going to cost them so much a year. County-wide applications would be the general mapping application. About every department indicated they want to make maps of the data. This type of application is just for customized or generic query, view, display, reporting, and mapping. You can go in and say, I’m going to look at this area. I want to set this area of interest. I want to look at this spatial content. I might want to see this type of annotation or information from a database on the map and then I need for just an internal departmental meeting this afternoon and I just want a B-sized landscape plot. Or you might need and D-size, you might need an A-size. It’s just a custom map application. The mailing labels, that’s basically for the public notification. I need to notify everybody within 500 feet of this parcel. Just basically it can be a couple buttons. Click, set some perimeters and the mailing labels are sent off to the printer. Then, a customized data maintenance interface, that would be built from your parcel maintenance and that’s to incorporate the data that’s not in the AutoCAD drawing files, which contains the parcel related information. This type of interface should incorporate AutoCAD files, so Secondary Roads is either going to transfer something to the Auditor’s or convert it in to the GIS, you have an interface to help you do that. It should handle GPS input. It should handle shape files. It should handle, if you had to actually go out and digitize information, create new information, maybe even some coordinate geometry or COGO entry. But, it’s going to be much more generic than the parcel. So, it’s going to build from the tools in the parcel maintenance, but it’s going to allow other departments to go in and do some data maintenance.
Campbell: Just a quick note. Jeff may have mentioned it. We talked about building on previous applications. There’s also another component to this as well. Just because you see something up here listed as a new application, doesn’t mean it needs to be developed from scratch. A lot of these commercial off-the-shelf packages (inaudible) at least a subset of what you’re looking for. For example, parcel maintenance application. You guys are just getting started with ArcInfo. You’re in pretty good shape when you don’t have any unnecessary bias towards GIS, ArcInfo-based parcel management software. There’s stuff that’s off the shelf out there that we could evaluate. It saves costs (inaudible), things like NovaLIS; SDS has another package. They run on top of the ArcInfo product. Just because you see something called an application doesn’t necessarily imply that you’re developing this thing from scratch.
Hanson: Departmental applications. These came out of the interviews. The water well and wastewater tracking system, a spatially enabled pavement management system, and I know some of that, some pavement management systems are available third party. It’s just getting them integrated with your GIS or integrated with your GIS data. Part of the database development phase is translating the road and street centerlines in the GIS format, pavement management system. Integrated GIS and Zoning Management, the Emergency Medical Service Response System for the Ambulance Department. That’s an application where they can enter the response locations, input some attribute information, calculate distances to hospitals, that type of thing. Just give them a little, an interface in their department to do something really specific for managing those responses. Also, that application has some mapping components in it. Then the voter and election tracking system for the Auditor’s Office. Low priority, and again, these are applications that have dependencies for this database development dependencies, some workflow re-engineering dependencies, and maybe some political considerations within the County and when to approach this and how best to approach this. Integrated GIS and Real Estate/CAMA system. This is an application where when a split, combination is processed, the real estate database is updated at the same time from the same workstation by a single user. So we’re going to collapse that process down into a single step process. That details… there’s an attachment… is that correct?
Campbell: There’s’ an attachment, that they did not get, that’s included in the current copies of what you have under Attachment A, I believe.
Hanson: It was included in your reports.
Campbell: Which was a white paper, a white paper we put together for a conference that details the integration of GIS and CAMA and the various models that can be used to accomplish that. A quick note on that, it’s the area we’re doing a lot of work in these days, on integrating GIS and CAMA. While I’m not going to under-emphasize the amount of work that’s entailed to put that together primarily because a lot of your processes, how you currently do parcel management go out the window. They have to be redesigned. There has to be new levels of cooperation between departments that sometimes doesn’t exist in a locality. There’s a fair amount of up-front work that needs to be done before you can implement some kind of an application like that. But we do bring it up because it’s a pretty hot area, in that, potentially, if you have the database side, the CAMA side and the GIS side being updated at the same time, all of the sudden, you run out of issues with your data being obsolete. All of the sudden, you’ve streamlined your parcel maintenance procedures. There are some distinct advantages to it, but we run into as many places that aren’t ever going to do it as we do have that want to do it.
Hanson: That would include the addressing component Zoning, the Assessor, and Auditor work on, and the transfer maps, the ones you transfer maps.
Slockett: And Treasurer, on addressing, too. That would be great to integrate some of these things.
Hanson: Right.
Dameron: What is CAMA?
Campbell: CAMA. Computer Aided Mass Appraisal. I can never remember computer aided or computer assisted.
Hanson: For Johnson County, it’s going to be more targeting the real estate, because the way your assessors work with the real estate databases. In a lot of counties, what you guys call your Real Estate, that’s all in one CAMA system. Now, you have a work flow where your CAMA system is used to do the evaluations, but that data’s pumped in, back to the Real Estate once a year with real estate changes going to the CAMA system weekly.
?: I see.
Hanson: It’s kind of a division there. Something that I overlook, on those dependencies for these priority applications, of large dependency for the counties, what databases are migrating to SQL Server environment? With zoning and building permits, I think, are on their way there or are going to be soon. The Real Estate Database, I think Jean indicated that through an ODBC connection, it really hampers the performance is that correct, on the HD3000?
Schultz: If you want to do it straight there, yes.
Hanson: Whether or not that gets migrated to the SQL Server environment, that’s a huge issue. Most of the people doing that type of integration are running their CAMA systems now in Oracle or SQL Server or Sybase. The integrated GIS and building permits. This would be… we have several clients now that actually can manage their building permits through a GIS interface if they wanted to. There’s still that database component. They can do scheduling of the permitting process and just tracking where the open permits are, conditional permits are, that type of thing, through the GIS interface. E911 incident mapping. Most departments, if not every department, wants an address database, better addressing. The Zoning Department’s already made a huge step towards standardizing addresses in the County. That application’s dependent on the development of an address database. The integrated GIS and Sign View for the Secondary Roads Department. Plan Review Tracking System. That’s usually a pretty involved application where you try and flow out the whole planning review process through (inaudible) building both the database component and the spatial component. I know a place like Colorado Springs has what they call the, I think it’s the Development Automated System, where plan reviews are submitted digitally in either AutoCAD or Intergraph format. The whole flow through the different phases of council meetings or board meetings is tracked through that system, linking to the documents or the drawing files, so you can incorporate all that in one tracking system. It actually given to the City in digital format and it goes through the planners and the engineers, whoever needs to review a certain plan, it’s all done electronically. That, again, gets into workflow issues. You could also scale that back and just make it a database application with maybe a MapObjects component, just sort of located where this development is taking place, and showing the proposed lots or whatever you’re looking at. Different levels of implementation (inaudible). The integrated scanned document system. This is linking the parcel database, or the address database to the documents the Recorder’s currently scanning. Their COTT and Paperclip system. The will require a PPN number link over to those document management systems, and through that PPN, click on a parcel and pull up the deed or historical information. Then the Health Risks System for the Health Department for the communicable diseases, the food born illnesses, and the animal bites, that type of thing.