Orange County NC Website
Browse       Search
Orange County information Technologies <br />8. The County version will include maintenance options to allow <br />the user to create and updatelmodify records that exist in the <br />application as implied in the Project Scope and Specification 1. <br />9. Patriot will create an interface with the current GIS system to <br />allow the data to automatically be available in the PIN <br />- __�__._ - -- ----------- -___ -- kpp ficatiarrand -wilj -not require- double - data- entr- y.- V1Lip- need - - - -- <br />data entry in the PIN Application as well. (See PIN <br />Application Data model for a full list of parcel attributes)The <br />PIN Application still needs to have the manual capability to <br />create, update and fix records in case something fails in GIS or <br />if there is an error while keying in the information in GIS. Also <br />straight transfers would happen in the PIN Application. What <br />we really need is some type of spatial view created between the <br />two systems (The County is responsible for this spatial view) <br />so that you can see what is in the PIN Application while using <br />the GIS application. Also GIS will allow editable relationship <br />classes so that the vector data and certain attributes can reside <br />in one table (in the GIS database) and other attributes can <br />reside in a totally different database (PIN Application), most <br />likely in some sort of holding table till it is processed and <br />committed. This interface will work with SyncPro to pull the <br />GIS data into the PIN Applccation so that the parcel record can - <br />be processed and then the PIN Application the PIN <br />Application will provide info to update the other system) will <br />update AssessPro, Permits, AmCAD and Web. <br />10. Patriot will need to create a process to designate new PINs that <br />come in from GIS to be assigned to the correct staff to look at <br />i and process. We will need something like the status/work flow <br />that exists in AssessPro. <br />11. Convert existing PIN History data from County's current <br />system as implied in specification 2. County will provide a <br />sample of the PIN data that is to be converted. <br />PIN Assumptions: - <br />PIN -The Parcel Identifier Number (PIN) is a geo -coded unique 1D for real property or other <br />.I geographical features. It is created by paring the unique X,Y values at a parcel's centroid or other <br />selected geo - feature, and is based on the state plane coordinate system = <br />PYN Creation - The PIN is currently created by the County's GIS system and manually entered = <br />into the legacy system that performs all parcel maintenance. The new PIN Application will need <br />I to receive PIN(s) and several other attributes from GIS, and administrative sheets needed for <br />recording with real property documents that create new parcels (deed, plat). The new application <br />will need to perform }parcel merge appropriate status changes <br />to existing and new PIN's involved (active, inactive, Preassigned) deMnding on what has been <br />pushed over from GIS. The Use Cases show that the split or merge is done in mapping, and <br />Page 7 of 8 I1 /9/20095 r'S 009 PIMS Project <br />