reference:system-architecture
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| reference:system-architecture [2025/08/27 06:41] – [14. Data Quality Framework] runarbe | reference:system-architecture [2025/09/09 22:03] (current) – [7. API layer] runarbe | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| This document provides an overview of all the elements that are required to operate the addressing system data infrastructure. | This document provides an overview of all the elements that are required to operate the addressing system data infrastructure. | ||
| - | ===== 1. Scope of the System Architecture | + | ===== 1. Scope of the Specification ===== |
| The scope of this document encompasses the essential requirements for the creation, maintenance, | The scope of this document encompasses the essential requirements for the creation, maintenance, | ||
| Line 15: | Line 15: | ||
| High-value integrations with government and private sector entities are proposed. Such integrations would allow for improved service delivery in the public sector, such as in emergency response and utility management. In the private sector, it could enhance commercial operations, logistics, and customer service practices by providing accurate and reliable address information. These partnerships are vital for maximizing the benefits of the National Addressing System, promoting efficiency, and facilitating economic and infrastructural development. | High-value integrations with government and private sector entities are proposed. Such integrations would allow for improved service delivery in the public sector, such as in emergency response and utility management. In the private sector, it could enhance commercial operations, logistics, and customer service practices by providing accurate and reliable address information. These partnerships are vital for maximizing the benefits of the National Addressing System, promoting efficiency, and facilitating economic and infrastructural development. | ||
| - | ===== 2. The Purpose of Integrating Addresses | + | ===== |
| - | + | ||
| - | The integration of addresses into other systems serves several essential purposes, primarily aimed at creating value for individuals, | + | |
| - | + | ||
| - | The concept of " | + | |
| - | + | ||
| - | In addition to tangible measures, the notion of an improved addressing system further extends to being just, fair, and equitable, providing benefits across various sectors. The system should also be accessible, facilitating easier operations, and its visual presentation should be designed for aesthetic appeal, or at the very least not to scare off users. | + | |
| - | + | ||
| - | To illustrate the value added by integrated address systems, consider several examples. They allow for precise specification of delivery locations, ensuring parcels reach their intended destinations efficiently. The system also aids in identifying the location of individuals or entities, such as querying the whereabouts of " | + | |
| - | + | ||
| - | Additionally, | + | |
| ===== 3. Systems Needed to Manage and Use NAS Data ===== | ===== 3. Systems Needed to Manage and Use NAS Data ===== | ||
| Line 47: | Line 37: | ||
| The business of street addressing is a complex set of interrelated managerial, planning, technical and engineering/ | The business of street addressing is a complex set of interrelated managerial, planning, technical and engineering/ | ||
| - | {{ : | + | {{ : |
| 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. | ||
| Line 68: | Line 58: | ||
| * Documentation for the [[: | * Documentation for the [[: | ||
| - | ==== 5.3 Naming | + | ==== 5.3 Name collection |
| + | |||
| + | * Documentation for the [[: | ||
| + | |||
| + | ==== 5.4 Name allocation data model ==== | ||
| + | |||
| + | * Documentation for the [[: | ||
| + | |||
| + | ==== 5.5 Field verification application data model ==== | ||
| + | |||
| + | * Documentation for the [[: | ||
| - | * Documentation for the [[: | ||
| ===== 6. Data Layer ===== | ===== 6. Data Layer ===== | ||
| Line 111: | Line 110: | ||
| * [[: | * [[: | ||
| - | * [[: | + | * [[: |
| + | * [[: | ||
| * [[: | * [[: | ||
| - | * [[: | + | * [[: |
| Line 120: | Line 120: | ||
| Below, you will find technical and functional requirements for the following applications | Below, you will find technical and functional requirements for the following applications | ||
| - | * [[: | + | * [[: |
| * [[: | * [[: | ||
| * [[: | * [[: | ||
| Line 127: | Line 127: | ||
| * [[: | * [[: | ||
| * [[: | * [[: | ||
| + | |||
| ===== 9. Infrastructure layer ===== | ===== 9. Infrastructure layer ===== | ||
| Line 135: | Line 136: | ||
| * [[: | * [[: | ||
| - | |||
| ===== 10. Emerging technologies and future proofing ===== | ===== 10. Emerging technologies and future proofing ===== | ||
| Line 205: | Line 205: | ||
| Integration refers to the incorporation of addressing systems into various operational, | Integration refers to the incorporation of addressing systems into various operational, | ||
| + | |||
| + | ==== 13.1 The Purpose of Integrating Addressing into other systems ==== | ||
| + | |||
| + | The integration of addresses into other systems serves several essential purposes, primarily aimed at creating value for individuals, | ||
| + | |||
| + | The concept of " | ||
| + | |||
| + | In addition to tangible measures, the notion of an improved addressing system further extends to being just, fair, and equitable, providing benefits across various sectors. The system should also be accessible, facilitating easier operations, and its visual presentation should be designed for aesthetic appeal, or at the very least not to scare off users. | ||
| + | |||
| + | To illustrate the value added by integrated address systems, consider several examples. They allow for precise specification of delivery locations, ensuring parcels reach their intended destinations efficiently. The system also aids in identifying the location of individuals or entities, such as querying the whereabouts of " | ||
| + | |||
| + | Additionally, | ||
| + | |||
| + | ==== 13.2 How integrations will be done ==== | ||
| Integration processes will be executed by business owners, not by the Ministry of Housing, Urban Planning. MoHUP will support by providing data access, adapting services, and facilitating systems. While MoHUP may promote integration and encourage business owners to recognise its benefits, ultimate responsibility rests on the business owners. Given the sensitivity of critical systems, business owners must perceive the value of integration for it to proceed independently. | Integration processes will be executed by business owners, not by the Ministry of Housing, Urban Planning. MoHUP will support by providing data access, adapting services, and facilitating systems. While MoHUP may promote integration and encourage business owners to recognise its benefits, ultimate responsibility rests on the business owners. Given the sensitivity of critical systems, business owners must perceive the value of integration for it to proceed independently. | ||
| Many business systems are already structured to accommodate addressing, particularly the newly implemented international formats. MoHUP' | Many business systems are already structured to accommodate addressing, particularly the newly implemented international formats. MoHUP' | ||
| + | |||
| + | ==== 13.3 Proposed integrations ==== | ||
| * [[: | * [[: | ||
| - | |||
| ===== 14. Data Quality Framework ===== | ===== 14. Data Quality Framework ===== | ||
| Line 218: | Line 233: | ||
| * [[: | * [[: | ||
| - | |||
| ===== 15. Transitional Arrangements ===== | ===== 15. Transitional Arrangements ===== | ||
reference/system-architecture.1756276868.txt.gz · Last modified: by runarbe
