| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| reference:system-architecture [2025/09/03 18:33] – [4. System architecture overview diagram] runarbe | reference:system-architecture [2025/09/09 22:03] (current) – [7. API layer] runarbe |
|---|
| |
| ===== ===== | ===== ===== |
| |
| |
| ===== 3. Systems Needed to Manage and Use NAS Data ===== | ===== 3. Systems Needed to Manage and Use NAS Data ===== |
| The business of street addressing is a complex set of interrelated managerial, planning, technical and engineering/civil works tasks that involves a broad range of distinctive end-users. The diagram below provides an overview of all the components that are required for the efficient operation and flow of data in the addressing system. | The business of street addressing is a complex set of interrelated managerial, planning, technical and engineering/civil works tasks that involves a broad range of distinctive end-users. The diagram below provides an overview of all the components that are required for the efficient operation and flow of data in the addressing system. |
| |
| {{ :wiki:reference:system:addressing-system-integration-architecturev003.png?direct&800x442 }} | {{ :wiki:reference:system:addressing-system-integration-architecturev003_1.png?direct&800x444 }} |
| |
| The diagram can be read both bottom up and top down. From the point of view of technical resources, the preferred reading direction is bottom up, for people who find themselves in end-user roles, it is more easily read from top to bottom. | The diagram can be read both bottom up and top down. From the point of view of technical resources, the preferred reading direction is bottom up, for people who find themselves in end-user roles, it is more easily read from top to bottom. |
| * Documentation for the [[:reference:system-architecture:signage-data-model|sign management data model]] (to be supplied by future appointed vendor) | * Documentation for the [[:reference:system-architecture:signage-data-model|sign management data model]] (to be supplied by future appointed vendor) |
| |
| ==== 5.3 Naming data model ==== | ==== 5.3 Name collection data model ==== |
| | |
| | * Documentation for the [[:reference:system-architecture:name-collection-data-model|naming data model]] (to be supplied by existing vendor) |
| | |
| | ==== 5.4 Name allocation data model ==== |
| | |
| | * Documentation for the [[:reference:system-architecture:naming-allocation-data-model|naming data model]] (to be supplied by existing vendor) |
| | |
| | ==== 5.5 Field verification application data model ==== |
| | |
| | * Documentation for the [[:reference:system-architecture:field-verification-data-model|naming data model]] (to be supplied by existing vendor) |
| |
| * Documentation for the [[:reference:system-architecture:naming-data-model|naming data model]] (to be supplied by existing vendor) | |
| |
| ===== 6. Data Layer ===== | ===== 6. Data Layer ===== |
| |
| * [[:reference:system-architecture:authentication-api|Authentication API]] | * [[:reference:system-architecture:authentication-api|Authentication API]] |
| * [[:reference:system-architecture:address-editing-and-query-api|Address Editing and Query API]] | * [[:reference:system-architecture:address-editing-and-query-api|Address editing API]] |
| | * [[:reference:system-architecture:address-integration-api|Address Integration API]] (vendor to be appointed by by competitive tender) |
| * [[:reference:system-architecture:naming-api|Naming API]] (to be supplied by existing vendor) | * [[:reference:system-architecture:naming-api|Naming API]] (to be supplied by existing vendor) |
| * [[:reference:system-architecture:signage-api|Signage API]] (implemenation to be determined through competitive tender) | * [[:reference:system-architecture:signage-api|Signage API]] (vendor to be appointed by by competitive tender) |
| |
| |
| Below, you will find technical and functional requirements for the following applications | Below, you will find technical and functional requirements for the following applications |
| |
| * [[:reference:system-architecture:address-editing-application|Web based data creation and editing client]] | * [[:reference:system-architecture:address-editing-application|Address editing application]] |
| * [[:reference:system-architecture:street-naming-application|Street naming application]] | * [[:reference:system-architecture:street-naming-application|Street naming application]] |
| * [[:reference:system-architecture:mobile-field-verification-application|Mobile field verification application]] | * [[:reference:system-architecture:mobile-field-verification-application|Mobile field verification application]] |
| * [[:reference:system-architecture:addressing-viewer-and-search-application|Addressing viewer and search application]] | * [[:reference:system-architecture:addressing-viewer-and-search-application|Addressing viewer and search application]] |
| * [[:reference:system-architecture:addressing-wiki|Addressing WIKI]] | * [[:reference:system-architecture:addressing-wiki|Addressing WIKI]] |
| | |
| |
| ===== 9. Infrastructure layer ===== | ===== 9. Infrastructure layer ===== |
| |
| * [[:reference:system-architecture:infrastructure|Technical infrastructure specification]] | * [[:reference:system-architecture:infrastructure|Technical infrastructure specification]] |
| |
| |
| ===== 10. Emerging technologies and future proofing ===== | ===== 10. Emerging technologies and future proofing ===== |
| |
| * [[:reference:system-architecture:integrations|Categorised list of value-added integrations of addressing data]] | * [[:reference:system-architecture:integrations|Categorised list of value-added integrations of addressing data]] |
| |
| |
| ===== 14. Data Quality Framework ===== | ===== 14. Data Quality Framework ===== |
| |
| * [[:reference:system-architecture:data-quality|Data quality]] | * [[:reference:system-architecture:data-quality|Data quality]] |
| |
| |
| ===== 15. Transitional Arrangements ===== | ===== 15. Transitional Arrangements ===== |
