A Block’s name, Reference and Year Built can be updated from within its Housing Group.
Open the required Housing Group and select the Blocks tab. Select the name of the Block you want to update.
From the Block details page, open the Options menu and select Edit Block.
The following information can be updated:
| Field | Description |
|---|---|
| Name | The name used to identify the Block. This is a required field. |
| Reference | An optional internal reference used by your organisation to identify the Block. In Asset Management reports, this is displayed as the Block’s Asset Reference and links back to the Block view. |
| Year Built | The year in which the Block was constructed. |
Make the required changes and click Update Block.
Updating the Block Reference
The Reference field can be used to align the Block with your organisation’s internal asset records or Fixed Asset Register. Affinity does not prescribe a numbering format, and the Reference is not treated as a UPRN or another externally governed identifier.
When entered, the Reference appears in the Housing Group’s Blocks list and as the Block’s Asset Reference in Asset Management reports.
The Reference is optional. It can be added, changed or left blank without preventing the Block from being included in Asset Management reports.
Adding a Missing Year Built
If the Year Built was not entered when the Block was originally created, it should be added before configuring its Asset Management information.
Affinity requires the Block’s Year Built to determine when components are expected to require replacement and when Compliance Checks will next be due. It is also required before the Block’s projected expenditure can be included within Stock Condition Costs forecasts.
If no Year Built has been recorded, the Block’s Asset Management area displays a warning and its Components and Compliance Checks cannot be configured.
Important: Use the actual construction year wherever possible. An inaccurate Year Built may result in incorrect replacement schedules and forecast costs.
Comments
0 comments
Please sign in to leave a comment.