|
With the wider use of the NLPG, the creation and processing of candidate records has become ever more important.
iManage is fully equipped to deal with the creation and export of candidate records by both the emergency services and local authorities using out of area data, as well as having the tools to enable local authorities to process received records well within the ten day turn around period.
What a Receiving Authority can do:
There are several types of Candidate record that may be created both by a Receiving Authority and a Local Authority.
Create new Property
- Create new a property where one does not exist in the NLPG
- Create a new Child candidate for an existing property
- Create new, non-NLPG properties as normal within iManage and exclude from export
Create an Alternate LPI
- Creating a new LPI on existing properties will automatically be saved as candidates
Change a Property
- Changes to a BLPU or LPI will be automatically saved to your candidate list
- Changes to BLPU cross references are excluded from export
Delete a Property / LPI
- Can submit a Deletion request or a request to make that property / LPI Historic
What a Local Authority can do:
Add New Property
Add New LPI
Change Existing Property
Change Exisiting BLPU
Change Existing LPI
Delete Property
Delete LPI
There are three options when processing Candidate records:
Add Record - this will create the following:
- a new BLPU status Approved, with a UPRN allocated from the next available
- an LPI with status Approved / Preferred
- a BLPU Cross Reference with Source = 7666IA and Cross Reference = Imported Candidate key
Add LPI to Existing BLPU - this will create the following:
- an LPI with status Approved / Preferred with the UPRN from the selected BLPU
- a BLPU Cross Reference with Source = 7666IA and Cross Reference = Imported Candidate key
Reject Record - these records are flagged a status Rejected External and are included in the next NLPG Export and sent to the NLPG Hub.
Do you have a question about Symphony iManage? If so, just ask...
|
