[an error occurred while processing this directive][an error occurred while processing this directive]
October - December 2005
Unlike the TAGG application, a trigger is also executed as information is being updated on existing service requests in the Siebel database. As a database connection is created on the ArcSDE Server, related information is passed from Siebel to the Java procedure stored within Oracle. The Java procedure is executed and connects to ArcSDE.
If the process being executed corresponds to a new service request, the location of the service request cannot necessarily be related to a particular parcel. In this case, the address of the service request is geocoded and this location is returned as an x,y coordinate. The Java procedure then creates a new point feature that corresponds to the new service request and assigns the necessary attributes. If the process being executed is the result of an updated service request, a corresponding point feature already exists in the service request feature class in ArcSDE. The Java procedure queries for the matching point feature and updates the attribution that was updated on the record in the Siebel database.
Both the TAGG and SAGA applications consist of two main server environments and also access a third server environment. The Tidemark Advantage and Siebel CRM databases both reside in the Oracle 9i environment. As new information is added to each database, PL/SQL code is automatically executed to access the Java procedure stored within Oracle on the ArcSDE Server, which resides in the Oracle 10g environment. The Java procedure then uses the ArcSDE 9 Java API to interact with ArcSDE. If the new permit is a new building permit, then the Java procedure also inserts address information. Finally, if any errors occur in the Java procedure, then the error information is logged in a separate database using a Web service written in Visual Basic .NET.
Better Workflows and Service
TAGG works behind the scenes in conjunction with the GIS. IndyGIS users use this application and, in the future, internal IndyGov users with authorized access to the GIS will be able to tap the application via another application, the Automated Mapping Engine. This will allow non-technical, non-GIS users to create high-quality GIS maps. TAGG benefits citizens and IndyGov employees by leveraging the permitting process with behind-the-scenes procedures that save time and money and also enable analyses of permitting trends.
SAGA is intended to assist GIS and Siebel CRM database users within the city of Indianapolis/Marion County. This target group includes users who wish to simply view/analyze the spatial data associated with service requests and those involved in maintaining the spatial data. As with TAGG, SAGA is a background process and the data created by the application is utilized by users.
The data created by SAGA will allow call center staff to better manage daily workflow by quickly displaying where existing calls have been recorded as new ones are being entered. Staff can then group calls so repeat tickets aren't generated for the same problem. This will give IndyGov a much better method for targeting existing resources and cut down on redundancy. The Siebel CRM system increases IndyGov's ability to efficiently respond to requests and provides better information on the status of requests. Residents can quickly request information or services such as pothole repairs, snow removal, or stray animal pickup.
About the Authors
Joe LaCombe is a GIS system designer for Woolpert, Inc., in Indianapolis. Molly Klimas is a technology writer based in Grand Rapids, Michigan.