Advanced Search
Search Results
97 total results found
6.6. Data governance
To clearly identify the responsibilities of each user, you will find below a responsibility matrix (RACI - Responsible, Accountable, Consulted, Informed). Definitions: Responsible (R): The role that is responsible for executing the task / activity. Accounta...
6.7. Fair usage (access limitations)
The goal of the NRVC is to created a shared, reliable and fair data source of vertical cabling data. Therefore it is important to guarantee that each user of the NRVC not only consumes the available data but also contributes to it. To promote a fair usage of t...
6.8. Automatic data approvals and deletion
Keeping multiple versions of the system physical links information in the NRVC has some side effects that allow us to implement automated data approval and data deletion processes that we will describe below. In the figure above each row of data rep...
6.9. Manual reviews and audits
Once a year data will be manually reviewed and Audited. The review will be done by an internal Analyst that is a domain expert, whereas the Audit can be performed by either an internal or an external auditor. Data Review The purpose of the review is to perfo...
6.10. Consistency checks
This section is meant to be used and completed during the entire lifetime of the project. All consistency checks that are not part of the global architecture concepts will be listed here for completeness and documentation purposes. These are the checks that w...
8. Data architecture
In this section we will present the data architecture chosen for the Vertical Cabling data. The introduction will be kept very high-level and the detailed fields of each entity will be presented in the Data Structure section below. Our main objectives and gui...
9. API Proposal
You will find below a link to the latest version of the swagger file that contains all entities manipulated by the system and the API calls associated with them. The swagger includes the roles that have access to each API call. https://prod.rncv.lu/backend/ap...
7.1. User management processes
User creation process f an organisation requires a new user, two possible scenarios arise, either the organisation already exists in the system, or a new organisation needs to be created. New organisation For new organisations the request needs to be send...
7.2. Create missing address process
Name Create Missing Address Request Purpose Allow Editors to add missing addresses to the system, so that they are not blocked during the data ingestion processes. Linked user stories 4.28. Editor - Create temporary address APIs u...
7.3. Create missing address for existing site or block process
Name Create missing address for existing site or block process Purpose Allow Editors to add missing addresses for an existing site or block to the system, so that they are not blocked during the data ingestion processes. Linked user sto...
7.4. Address ingestion via the ETL process
The background colors of the above image are to be interpreted as: purple: the core application a.k.a. backend that will be built in the context of this project green: supporting systems that will be used in the context of this project blue: tru...
7.5. Send update vertical cabling request process
Name Send update vertical cabling request process Purpose Allow Editors to send an update request for a vertical cabling entry between two equipments Linked user stories 4.46. Editor - Send an update vertical cabling request A...
7.6. Approve update vertical cabling request
Name Approve update vertical cabling request Purpose Allow Approvers to validate an update request for a vertical cabling entry between two equipments Linked user stories 4.51. Approver - Approve or reject update vertical cabling req...
7.7. Approve delete site request
Name Approve delete site request Purpose Allow Approver to validate a site delete request Linked user stories 4.33. Editor - Delete a site 4.47. Approver - Approve deleted site request 4.52. Organisation Approver - Approve deleted ...
7.8. Approve delete block request
Name Approve delete block request Purpose Allow Approver to validate a block delete request Linked user stories 3.36. Editor - Delete a block 4.48. Approver - Approve deleted block request 4.53. Organisation Approver - Approve dele...
7.9. Approve delete unit request
Name Approve delete unit request Purpose Allow Approver to validate a unit delete request Linked user stories 4.39. Editor - Delete a unit 4.49. Approver - Approve deleted unit request 4.54. Organisation Approver - Approve deleted ...
7.10. Approve delete equipment request
Name Approve delete equipment request Purpose Allow Approver to validate an equipment delete request Linked user stories 4.42. Editor - Delete an equipment 4.50. Approver - Approve deleted equipment request 4.55. Organisation Appro...