AU2018253452A1

AU2018253452A1 - A system and method for generating an update request to update a third party data repository

Info

Publication number: AU2018253452A1
Application number: AU2018253452A
Authority: AU
Inventors: John Francis Michael Ahern
Original assignee: Infotrack Pty Ltd
Current assignee: Infotrack Pty Ltd
Priority date: 2017-10-20
Filing date: 2018-10-22
Publication date: 2019-05-16

Abstract

A SYSTEM AND METHOD FOR GENERATING AN UPDATE REQUEST TO UPDATE A THIRD PARTY DATA REPOSITORY A system 1 for generating an update request 2 to update at least one third party data repository 3. The repository 3 has a repository interface, in the form of a communications interface 4, for electronically receiving request 2 and providing a confirmation signal 6 that request 2 has been received. System 1 includes a visualization database 7 for containing a plurality of node records 9 and link records 10. Records 9 each include a plurality of editable fields 11. Database 7 also includes edit records 14 indicative of a change to one or more of editable fields 11 or 12. A visualization engine, in the form of a visualization server 15, accesses database 7 and is selectively responsive to records 9 and 10 for generating network visualization data indicating a plurality of nodes corresponding to the selected records 9 and a plurality of links between the nodes corresponding to the selected records 10. Server 15 is responsive to an update signal and records 14 for updating database 7 by updating one or more of the records. An edit engine, in the form of an edit server 21, is responsive to the selection of one of the nodes in the visualization data for allowing editing of one or more of fields 11 of the corresponding node record. Server 21 is also responsive to the editing of the one or more of fields 11 for updating edit records 14. An update engine, in the form of a main server 22, is responsive to records 14 for generating request 2. Server 22 is also responsive to signal 6 for generating the update signal. (Figure 1) 32a i bj 32n 4 3 30a 30b m 33a 33n 31a Comms 4 Interface 31b 2 1Figure r -- ----- -- -- -- -- -- - 1 Communications 60 62 Interface Software 48 63 64 38 Instructions --- 46 Memory Module Processor 4 Server 71 4 9 15 -0 21-c r 17 Server System - -I

Description

A SYSTEM AND METHOD FOR GENERATING AN UPDATE REQUEST TO UPDATE A THIRD PARTY DATA REPOSITORY

FIELD OF THE INVENTION [0001] The present invention relates to a system and method for generating an update request and more particularly to a system and method for generating an update request to update a third party data repository.

[0002] Embodiments of the invention have been particularly developed for updating third party data repositories operated by or on behalf of one or more government or public agencies. However, it will be appreciated that the invention is not limited to such a field of use and is applicable in broader contexts including, without limitation, to updating other data whether that is held in one or more private repositories, whether local or remote from the system.

BACKGROUND [0003] Any discussion of the background art throughout the specification should in no way be considered as an admission that such art is widely known or forms part of common general knowledge in the field.

[0004] The increasing use and availability of online databases and other information repositories has allowed national governments, their agencies and private companies to make more accessible to the public information about different aspects of the parties and properties being regulated or monitored by the government authorities, including information about the activities and status of those parties and properties. These databases and other information repositories are typically administered directly by the relevant government department or agency or the company concerned, and are increasingly also available for the regulated parties to access and provide updates on the regulated activities and other requirements.

[0005] The use of such databases and other information repositories has now reached a point where the initial benefits arising from the accessibility of the underlying data are being degraded as the information being collected to maintain the currency of the data is not, or cannot be, sufficiently quickly updated to reflect more recent changes associated with the entity being regulated. Accordingly, while the public is still able to access the data effectively in real-time, there is a reduced confidence about the accuracy of the data retrieved.

[0006] In part this problem of the prior art arises from the form in which the updates must be submitted and amount of information involved - that is, a large number of

2018253452 22 Oct 2018 updates need to be submitted in respect of a large number of parties to retain the currency of the data. Both these factors place increasing demands upon the underlying IT infrastructure for the databases or information repositories that are administered. This issue is compounded when regard is also had to undertaking sufficient quality control steps in vetting the accuracy, validity and integrity of the changes that are being proposed to be included in the database or other information repository.

[0007] In a specific example, in Australia the Australian Securities and Investment Commission (ASIC) is an independent Australian Commonwealth Government body which is charged with, amongst other things, the regulation of Australian corporations. ASIC administers a number of databases known as registers, which includes a register of Australian corporations (referred to as “the company register”). The company register is open to be searched by members of the public directly via an online interface or indirectly through one of a number of ASIC authorised information brokers. While some of the available information from the company register is able to be extracted freely other, typically more detailed, extracts require a prepayment to be made to ASIC.

[0008] Australian corporations undergoing predetermined changes in name, address details, directorships and other such matters are required to report details of those changes to ASIC so that the company register is updated. To gain confidence about the authenticity of the change and the source of the request for the change, the person requesting the change to the company register must be pre-registered with ASIC as being a person permitted by the company to request such changes. To qualify for such registration the person must either be a current officeholder of the company or appointed as an agent for the company by a current office holder.

[0009] As ASIC has relatively recently eliminated all paper lodgements for requests for changes to the register all the changes must be performed electronically. It is also anticipated that ASIC will continue to adopt similar electronic requests for updating other of the registers and databases it administers as it moves to electronic lodgement of all forms. This will all place a greater strain on the existing electronic options to deal efficiently with the larger volume of changes that will have to be processed in that way.

[0010] There are currently three ways for a corporation to electronically request ASIC to change the company register. The first is to initiate a company register change by completing an online form via the ASIC agent/officeholder portal. The person requesting the company register change must either be the company appointed registered agent or an officeholder for the company requesting the company record change. If the person requesting the company record change is the registered agent, then he or she must first log into the ASIC Agent Portal, and be authorised to lodge requests on behalf of the

2018253452 22 Oct 2018 company. If he or she is not authorised - that is, if a F362 (Appointment/cessation of Agent) form signed by an officeholder has not been previously lodged with ASIC - then the person will not be permitted to request the change via the ASIC Agent Portal. If, however, the person is a current officeholder of the company - in that he or she is an officeholder noted on the company register for the company - then he or she must log into the ASIC Officeholder Portal to request the change. It will be appreciated that, prior to accessing the ASIC Officeholder Portal, ASIC requires the person to be authenticated using the ASIC issued Corporate Key. The Corporate Key is a second level authentication system and is only sent to the company on either incorporation, or together with the annual company statement issued at the anniversary of the incorporation of the company. [0011] If either set of the above preconditions are satisfied, the person using the ASIC Agent Portal or the ASIC Officeholder Portal calls up a web-form containing the editable fields in the company record held with ASIC for the company. The person then manually edits the required fields of the company record and, when completed, submits the webform as a request to change to edited details. The request is processed by ASIC and, once confirmed as being accepted, ASIC updates the company register with the change. [0012] A second option to electronically request a change to the company register is the use of third party application software (a desktop application, a cloud application, or the like provided by a limited set of information brokers) that interacts with the EDGE Electronic Lodgement Protocol (referred to as “EDGE” or “EDGE registration service”) supplied by ASIC. Again, the similar prerequisites apply in that the person requesting the change to the company register must be a registered agent for the company in respect of which the changes are being requested. The agent must also be registered with ASIC for the purposes of the EDGE registration services. This registration process is detailed and requires a considerable time commitment to successfully complete. Once registered, the process of requesting a change the company register requires the agent to use a desktop computer or other network enable device to commence a communication session with the EDGE registration service. Once the session is established, and using the application software, the agent obtains, completes and submits an approved ASIC agent form (form RA71). If this is successfully submitted, the agent is then able, again via the application software, to download from the register an electronic extract of the relevant details of the company. Once the extract of the company details is obtained, the agent is able to edit one or more of the available fields using the functionality provided by executing the thirdparty application software. While the application software of each third-party provider has a different look and feel and follows different detailed flow-paths, ultimately all require the same information to comply with the requirements of the EDGE registration service.

2018253452 22 Oct 2018 [0013] Once the agent has made the required edits to reflect the desired change or changes, the agent directs that a request for a change of the company register be lodged via the application software. If ASIC approves the changes the new details are communicated to the agent via the application software.

[0014] A third option to request a change to the register is for the already appointed agent to authorise a third party to submit the lodgement on behalf of the company. This requires the third party to be authorised to take this action prior to the lodgement of the request with ASIC. The authorisation takes the form of an additional ASIC submission. The existing agent need have no function in requesting the change in the company register. The process of notifying ASIC is undertaken and determined by the third party, and that party notifies the agent of the changes once those changes have been made and confirmed by ASIC. The primary mode of communication between the agent and the third party is typically via email.

[0015] All of the available systems are relatively administratively cumbersome, time intensive and typically require accessing the relevant repository multiple times.

[0016] Accordingly, there is a need in the art for an improved system and method for generating an update request.

SUMMARY OF THE INVENTION [0017] It is an object of the present invention to overcome or ameliorate at least one of the disadvantages of the prior art, or to provide a useful alternative.

[0018] According to a first aspect of the invention there is provided a system for generating an update request to update a third party data repository, wherein the repository has a repository interface for receiving the request and providing a confirmation signal that the request has been received, and wherein the system includes:

(a) a visualization database for containing:

(i) a plurality of node records and link records, wherein one of the records includes at least one editable field; and (ii) edit records indicative of a change to one or more of the at least one editable field;

(b) a visualization engine that accesses the visualization database and which is selectively responsive to:

(i) the records for generating network visualization data indicative of a plurality of nodes and links between the nodes, wherein one of the nodes or links is derived from the one of the records; and

2018253452 22 Oct 2018 (ii) an update signal and the edit records for updating the visualization database;

(c) an edit engine that is responsive to:

(i) the selection of the one of the nodes or links indicated by the network visualization data for allowing editing of one or more of the at least one editable field; and (ii) the editing of the one or more of the at least one editable field for updating the edit records; and (d) an update engine that is responsive to:

(i) the edit records for selectively generating the update request; and (ii) the confirmation signal for generating the update signal.

[0019] In an embodiment each of the node records includes at least one editable field.

[0020] In an embodiment each of the link records includes at least one editable field.

[0021] In an embodiment not all of the node records include at least one editable field.

[0022] In an embodiment not all of the link records include at least one editable field.

[0023] In an embodiment the update engine is responsive to the edit records for generating at least one further request to update respective further repositories.

[0024] In an embodiment at least one of the further repositories is a further third party repository.

[0025] In an embodiment the system includes a query engine for querying of one or more data sources and being selectively responsive to results of the query or queries for creating, deleting or updating the node records and the link records.

[0026] In an embodiment the one or more data sources includes the third party repository.

[0027] In an embodiment the one or more data sources comprises the third party repository.

[0028] In an embodiment the update engine is responsive to a first user request from a user device for making the network visualization data available to the user device.

[0029] In an embodiment the edit engine is responsive to a second user request from the user device to update the edit records.

[0030] In an embodiment the user device includes a GUI which is responsive to: the network visualization data for visually displaying to a user of the user device a corresponding network visualization; and input provided by the user to the user device to generate the second user request.

[0031] In an embodiment the system includes an authorization engine that is responsive to the edit records for selectively generating an authorization signal, wherein

2018253452 22 Oct 2018 the update engine is responsive to the authorization signal for generating the update request.

[0032] In an embodiment the authorization engine: generates an authorization request for communicating to an authorizing party; and is responsive to a response from the authorizing party to the authorization request to selectively generate the authorization signal.

[0033] According to a second aspect of the invention there is provided a method for generating an update request to update a third party data repository, wherein the repository has a repository interface for receiving the request and providing a confirmation signal that the request has been received, and wherein the method includes the steps of:

(a) containing within a visualization database:

(b) accessing the visualization database with a visualization engine which is selectively responsive to:

(i) the records for generating network visualization data indicative of a plurality of nodes and links between the nodes, wherein one of the nodes or links is derived from the one of the records; and (ii) an update signal and the edit records for updating the visualization database;

(c) providing an edit engine that is responsive to:

(i) the selection of the one of the nodes or links indicated by the network visualization data for allowing editing of one or more of the at least one editable field; and (ii) the editing of the one or more of the at least one editable field for updating the edit records; and (d) providing an update engine that is responsive to:

[0034] According to a third aspect of the invention there is provided a system for generating an update request to update a third party data repository, wherein the repository has a repository interface for receiving the request and providing a confirmation signal that the request have been received, and wherein the system includes:

(a) a visualization database for containing:

2018253452 22 Oct 2018 (i) a plurality of node records and link records, wherein the node records each include at least one editable field; and (ii) edit records indicative of a change to one or more of the at least one editable field;

(i) the records for generating network visualization data indicating a plurality of nodes corresponding to the node records and a plurality of links between the nodes corresponding to the link records; and (ii) an update signal and the edit records for updating the visualization database;

(c) an edit engine that is responsive to:

(i) the selection of one of the nodes in the network visualization for allowing editing of one or more of the at least one editable field of the corresponding node record; and (ii) the editing of the one or more of the at least one editable field for updating the edit records; and (d) an update engine that is responsive to:

[0035] In an embodiment the link records each include at least one editable field and the edit engine is responsive to:

(a) the selection of one of the links indicated by the network visualization data for allowing editing of one or more of the at least one editable field of the corresponding link record; and (b) the editing of the one or more of the at least one editable field for updating the edit records.

[0036] According to a fourth aspect of the invention there is provided a method for generating an update request to update a third party data repository, wherein the repository has a repository interface for receiving the request and providing a confirmation signal that the request have been received, and wherein the method includes the steps of:

(a) containing within a visualization database:

(i) a plurality of node records and link records, wherein the node records each include at least one editable field; and (ii) edit records indicative of a change to one or more of the at least one editable field;

2018253452 22 Oct 2018 (b) accessing the visualization database with a visualization engine which is selectively responsive to:

(c) providing an edit engine that is responsive to:

(i) the selection of one of the nodes in the network visualization for allowing editing of one or more of the at least one editable field of the corresponding node record; and (ii) the editing of the one or more of the at least one editable field for updating the edit records; and (d) providing an update engine that is responsive to:

[0037] According to a fifth aspect of the invention there is provided a system for generating an update request to update a third party data repository, wherein the repository has a repository interface for receiving the request and providing a confirmation signal that the request have been received, and wherein the system includes:

(a) a visualization database for containing:

(i) a plurality of node records and link records, wherein the link records each include at least one editable field; and (ii) edit records indicative of a change to one or more of the at least one editable field;

(i) the records for generating network visualization data indicative of a plurality of nodes and links between the nodes; and (ii) an update signal and the edit records for updating the visualization database;

(c) an edit engine that is responsive to:

(i) the selection of the one of the links indicated by the network visualization data for allowing editing of one or more of the at least one editable field; and

2018253452 22 Oct 2018 (ii) the editing of the one or more of the at least one editable field for updating the edit records; and (d) an update engine that is responsive to:

[0038] According to a sixth aspect of the invention there is provided a method for generating an update request to update a third party data repository, wherein the repository has a repository interface for receiving the request and providing a confirmation signal that the request have been received, and wherein the method includes:

(a) containing within a visualization database:

(c) providing an edit engine that is responsive to:

(i) the selection of the one of the links indicated by the network visualization data for allowing editing of one or more of the at least one editable field; and (ii) the editing of the one or more of the at least one editable field for updating the edit records; and (d) providing an update engine that is responsive to:

[0039] According to a seventh aspect of the invention there is provided a system for updating network visualization data, the system including:

(a) a visualization database for containing:

2018253452 22 Oct 2018 (b) a visualization engine that accesses the visualization database and which is selectively responsive to:

(c) an edit engine that is responsive to:

(i) the selection of the one of the nodes or links indicated by the network visualization data for allowing editing of one or more of the at least one editable field; and (ii) the editing of the one or more of the at least one editable field for updating the edit records;

(d) a request engine for generating an update request to update a third party data repository, wherein the repository has a repository interface for receiving the request and providing a confirmation signal that the request has been received; and (e) an update engine that is responsive to:

[0040] In an embodiment the update engine is responsive to a first user request from a user device for making the network visualization data available to the user device.

[0041] In an embodiment the edit engine is responsive to a second user request from the user device to update the edit records.

[0042] In an embodiment the user device includes a GUI which is responsive to: the network visualization data for visually displaying to a user of the user device a corresponding network visualization; and input provided by the user to the user device to generate the second user request.

[0043] In an embodiment the visualization engine is responsive to the updating of the visualization database for allowing the GUI to visually display to the user a correspondingly updated network visualization.

[0044] In an embodiment the system includes an authorization engine that is responsive selectively to the edit records for generating an authorization signal, wherein the update engine is responsive to the authorization signal for generating the update request.

2018253452 22 Oct 2018 [0045] In an embodiment the authorization engine: generates an authorization request for communicating to an authorizing party; and is responsive to a response from the authorizing party to the authorization request to selectively generate the authorization signal.

[0046] According to an eighth aspect of the invention there is provided a method for updating network visualization data, the method including the steps of:

(a) containing in a visualization database:

(c) providing an edit engine that is responsive to:

(d) generating an update request with a request engine to update a third party data repository, wherein the repository has a repository interface for receiving the request and providing a confirmation signal that the request has been received; and (e) providing an update engine that is responsive to:

[0047] According to a ninth aspect of the invention there is provided a system for generating an update request to update a third party data repository, wherein the repository has a repository interface for receiving the request and the system includes:

(a) a visualization database for containing:

2018253452 22 Oct 2018 (i) a plurality of node records and link records, wherein one of the records includes at least one editable field; and (ii) edit records indicative of a change to one or more of the at least one editable field;

(b) a visualization engine that accesses the visualization database and which is selectively responsive to the records for generating network visualization data indicative of a plurality of nodes and links between the nodes, wherein one of the nodes or links is derived from the one of the records:

(c) an edit engine that is responsive to:

(d) an authorization engine that is responsive to the edit records for selectively generating an authorization signal; and (e) an update engine that is responsive to the authorization signal and the edit records for generating the update request.

[0048] In an embodiment the authorization engine:

(a) generates an authorization request for communicating to an authorizing device of an authorizing party; and (b) is responsive to a response from the authorizing device of the authorizing party to the authorization request to selectively generate the authorization signal.

[0049] In an embodiment the authorizing device includes a GUI for: presenting visually to the authorizing party the authorization request; being responsive to predetermined input to the authorizing device by the authorizing party for generating the authorizing signal. [0050] In an embodiment the predetermined input is one or more of:

(a) a signature;

(b) a password; and (c) a code.

[0051] According to a tenth aspect of the invention there is provided a method for generating an update request to update a third party data repository, wherein the repository has a repository interface for receiving the request and the method includes the steps of:

(a) containing in a visualization database:

(b) accesses the visualization database with a visualization engine which is selectively responsive to the records for generating network visualization data indicative of a plurality of nodes and links between the nodes, wherein one of the nodes or links is derived from the one of the records:

(c) providing an edit engine that is responsive to:

(d) providing an authorization engine that is responsive to the edit records for selectively generating an authorization signal; and (e) providing an update engine that is responsive to the authorization signal and the edit records for generating the update request.

[0052] According to an eleventh aspect of the invention there is provided a system for generating an update request to update a third party data repository, wherein the repository has a repository interface for receiving the request and the system includes:

(a) a visualization database for containing:

(b) a visualization engine that accesses the visualization database and which is selectively responsive to the records for generating network visualization data indicating a plurality of nodes corresponding to the node records and a plurality of links between the nodes corresponding to the link records;

(c) an edit engine that is responsive to:

(i) the selection of one of the nodes in the network visualization for allowing editing of one or more of the at least one editable field of the corresponding node record; and (ii) the editing of the one or more of the at least one editable field for updating the edit records; and

2018253452 22 Oct 2018 (d) an authorization engine that is responsive to the edit records for selectively generating an authorization signal; and (e) an update engine that is responsive to the authorization signal and the edit records for generating the update request.

[0053] In an embodiment the authorization engine:

[0054] In an embodiment the authorizing device includes a GUI for: presenting visually to the authorizing party the authorization request; being responsive to predetermined input to the authorizing device by the authorizing party for generating the authorizing signal. [0055] In an embodiment the predetermined input is one or more of:

(a) a signature;

(b) a password; and (c) a code.

[0056] According to an twelfth aspect of the invention there is provided a method for generating an update request to update a third party data repository, wherein the repository has a repository interface for receiving the request and the method includes the steps of:

(a) containing in a visualization database:

(b) accessing the visualization database with a visualization engine which is selectively responsive to the records for generating network visualization data indicating a plurality of nodes corresponding to the node records and a plurality of links between the nodes corresponding to the link records;

(c) providing an edit engine that is responsive to:

2018253452 22 Oct 2018 (d) providing an authorization engine that is responsive to the edit records for selectively generating an authorization signal; and (e) providing an update engine that is responsive to the authorization signal and the edit records for generating the update request.

[0057] Reference throughout this specification to “one embodiment”, “some embodiments” or “an embodiment” means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrases “in one embodiment”, “in some embodiments” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment, but may. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner, as would be apparent to one of ordinary skill in the art from this disclosure, in one or more embodiments.

[0058] As used herein, and unless otherwise specified, the use of the ordinal adjectives first, second, third, etc., to describe a common objects, merely indicate that different instances of like objects are being referred to, and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, in significance or importance, or in any other manner.

[0059] In the claims below and the description herein, any one of the terms “comprising”, “comprised of” or “which comprises” or the like is an open term that means “including at least the elements/features that follow, but not excluding others”. Thus, the term “comprising”, when used in the claims, should not be interpreted as being limitative to the means or elements or steps listed thereafter. For example, the scope of the expression “a device comprising A and B” should not be limited to devices consisting only of elements A and B. Any one of the terms “including” or “which includes” or “that includes”, as used herein, is also an open term that also means “including at least the elements/features that follow the term, but not excluding others”. Thus, the term “including” is synonymous with and means “comprising”.

[0060] As used herein, the term “exemplary” is used in the sense of providing examples, as opposed to indicating quality. That is, an “exemplary embodiment” is an embodiment provided as an example, as opposed to necessarily being an embodiment of exemplary quality or status.

BRIEF DESCRIPTION OF THE DRAWINGS [0061] Embodiments of the invention will now be described, by way of example only, with reference to the accompanying drawings in which:

2018253452 22 Oct 2018

Figure 1 illustrates schematically an overview of a system according to an embodiment of the invention;

Figure 2 illustrates schematically a plurality of node records stored within the system of Figure 1;

Figure 3 illustrates schematically a plurality of link records stored within the system of Figure 1;

Figure 4 illustrates schematically a plurality of edit records stored within the system of Figure 1;

Figure 5 is a schematic illustration of a user device operated by a user to interact with system 1;

Figure 6 is an example network visualisation for a Company A generated on a user device in response to receiving network visualisation data from the system of Figure 1;

Figure 7 is the network visualisation of Figure 6 with the cursor hovering over a node to display a pop-up;

Figure 8 is a further example network visualisation for a Company Test 84 Pty Ltd;

Figure 9 is a web form that defines part of a second user request to the system of Figure 1;

Figure 10 is the web form of Figure 9 that has been completed by the user;

Figure 11 is a communication provided by the system of Figure 1 to an authorising party;

Figure 12 is a schematic representation of a system according to another embodiment of the invention;

Figure 13 is a flowchart illustrating an example operation of the system of Figure 12; and

Figure 14 is a summary flowchart illustrating the operation of the system of Figure 12 for different types of update requests.

DETAILED DESCRIPTION [0062] Described herein are systems and methods for generating an update request.

2018253452 22 Oct 2018 [0063] Referring to Figure 1 there is schematically illustrated a system 1 for generating an electronic update request 2 to update at least one third party data repository 3. The repository 3 has a repository interface, in the form of a communications interface 4, for electronically receiving request 2 and providing an electronic confirmation signal 6 that request 2 has been received. System 1 includes a visualization database 7 for containing, as illustrated in Figures 2 and 3, a plurality of node records 9 (including but not limited to node records 9a, 9b, ..., 9x) and link records 10 (including but not limited to link records 10a, 10b..... 10y). Records 9 each include a plurality of editable fields 11, which are exemplarily illustrated as being Editable Field #1, Editable Field #2 and Editable Field #3. Records 10 each include a plurality of editable fields 12, which are exemplarily illustrated as being Editable Field #4, Editable Field #5 and Editable Field #6. Database 7 also includes, a illustrated in Figure 4, edit records 14 (including but not limited to records 14a, 14b..... 14z) indicative of a change to one or more of editable fields 11 or 12. A visualization engine, in the form of a visualization server 15, accesses database 7 and is selectively responsive to records 9 and 10 for generating network visualization data, typically from a subset of records 9 and 10, indicating a plurality of nodes corresponding to the selected records 9 and a plurality of links between the nodes corresponding to the selected records 10. In this embodiment, the visualisation data is stored in a graph database 17. Server 15 is responsive to an update signal and records 14 for updating the visualization database 7 by updating one or more of the records and/or deleting and/or adding one or more records. An edit engine, in the form of an edit server 21, is responsive to the selection of one of the nodes in the network visualization data for allowing editing of one or more of the editable fields 11 of the corresponding node record. Server 21 is also responsive to the editing of the one or more of editable fields 11 for updating edit records 14. An update engine, in the form of a main server 22, is responsive to records 14 for generating request 2. Server 22 is also responsive to signal 6 for generating the update signal.

[0064] Records 9 and 10 each include a plurality of fields. Those fields each represent a property of the associated node and contain data which qualifies or quantifies the property. It will be appreciated that not all of the fields need be editable fields, and that not all the records need to include at least one editable field.

[0065] Although only a single third party data repository 3 is illustrated, it will be appreciated that more than one such repository is able to be accessed and/or updated by system 1. Moreover, if an edited editable field contains data relevant to more than one repository, system 1 is able to be configured to automatically seek to update all such repositories. In alternative embodiments, user input is sought as to which of the

2018253452 22 Oct 2018 repositories should be updated with the edited data. Such separate repositories typically have separate interfaces, although not always.

[0066] In this embodiment repository 3 is managed and operated by a third party, being a government authority. That is, the control of repository 3 and its stored data is by a third party. Also, repository 3 is remotely located from system 1. In other embodiments, some or all of repository 3 is held within system 1, but the contents are still under the control of the government authority.

[0067] System 1 selectively communicates with a plurality of users 30a, 30b..... 30m (collectively referred to as users 30) that operate respective user devices, in the form of desktop computers 31a, 31b.....31m (collectively referred to as computers 31). System 1 also selectively communicates with a plurality of authorising parties 32a, 32b..... 32n (collectively referred to as parties 32) that operate respective authorising devices, in the form of smart phones 33a, 33b.....33n (collectively referred to as smart phones 33).

[0068] The function of computers 31 and smart phones 33, and other such computing devices, is to enable the respective users 30 and respective parties 32 to communicate and interact with system 1. Accordingly, users 30 are able to use respective smart phones or other computing devices, while parties 32 are able to use respective desktop or other computers, to initiate and affect that communication. Other computing devices are able to be used instead of desktop computers and smart phones. For example, the communication is able to be established with system 1 via computing devices such as tablet computers, laptop computers, notebook computers, PDAs, net-book computers, or other web-enabled or network enabled computing devices. Moreover, users 30 and parties 32 are not limited to always using the same device to access and interact with system 1 during different sessions.

[0069] System 1 includes a server system 34 having communications interface, in the form of a web interface 35, for allowing the abovementioned communications sessions to be established between each of computers 31 and smart phones 33. Although only a single interface is shown, it will be appreciated that, in other embodiments, more than one interface is used by system 1. The communications interface or interfaces are able to be an Internet connection, modem, Ethernet port, wireless network card, serial port, or the like, and will depend upon the nature and scale of system 1.

[0070] In some embodiments web interface 15 includes a website. The term “website” should be read broadly to cover substantially any source of information accessible over the Internet or another communications network (such as WAN, LAN or WLAN) via a browser application running on a client terminal. In some embodiments, a website is a source of information made available by a server and accessible over the Internet by a

2018253452 22 Oct 2018 web-browser application running on a client terminal. The web-browser application downloads code, such as HTML code, from the server. This code is executable through the web-browser on the client terminal for providing a graphical and often interactive representation of the website on the client terminal. By way of the web-browser application, a user of the client terminal (for example, users 30 and parties 32) is able to navigate between and throughout various web pages provided by the website, and access various functionalities that are provided.

[0071] Server system 34 is located in a secure facility 38 and includes a plurality of interlinked physical servers, which are representatively illustrated in Figure 1 as servers 22, 15 and 21. It will be appreciated that typically a larger number of servers are used, although in some embodiments that includes virtual servers. It will also be appreciated that any servers used (and/or for any other physical or virtual servers employed in system 1) need not be co-located with the illustrated servers and are able to be disposed at other physical or virtual locations.

[0072] Each of the servers within server system 34 includes various components to allow operation. By way of example, server 22 includes a processor 45 coupled to a memory module 46. In other embodiments distributed resources are used. For example, in one embodiment server 22 includes a plurality of distributed servers having respective storage, processing and communications resources. In another embodiment, server 22 is a virtual server and/or a cloud server and/or a hosted server.

[0073] Memory module 46 includes software instructions 48, which are executable on processor 45.

[0074] Server 22 is coupled to databases 7 and 17 (and any other databases used in facility 38). In further embodiments the databases leverage memory module 46.

[0075] System 1 also includes a client terminal within facility 38 in the form of an administrator terminal 60 that is connected to a LAN 61. Terminal 60 runs a browser and is served up web pages from server system 34 using functionality similar to the delivery of web pages to computers 31. Terminal 60 is used by a supervisor 62 to, amongst other things, gain an overview of system 1, generate reports about various operating parameters of system 1, and to provide supervisory input. A further client terminal is provided in facility 38, in the form of a developer terminal 63, which is used by a developer 64 to, amongst other things, assist with the ongoing maintenance and development of system 1. It will be appreciated that different or additional terminals are also able to be included in facility 38. It will also be appreciated that those terminals are able to be replicated by the relevant supervisor 62, developer 64 accessing system 1 remotely from facility 32.

2018253452 22 Oct 2018 [0076] System 1 is, in this embodiment, part of an online document processing and workflow system (not explicitly illustrated) into which users 30 (and others) are enrolled. This document processing and workflow system guides and allows predetermined electronic interactions between those parties and a variety of electronic documents to facilitate the transactions with which users 30 are pursuing. The document processing and workflow system also interacts with external databases, such as repository 3, to access information for use in system 1, typically at the request of one of the users 30. In this embodiment, the operator of the document processing and workflow system is one and the same as the operator of system 1. However, in other embodiments, the operators of those two systems are not the same.

[0077] Users 30 are all enrolled in system 1 to enable their ability to access the functionality that is described in this patent specification. This enrolment and access includes the individual users 30 using respective computers 31, or like devices. Whilst only three users 30 are explicitly illustrated in Figure 1 it will be appreciated that, in use, there are typically many thousands or tens of thousands or more of such users enrolled in and making use of system 1 each business day.

[0078] Users 30 individually enrol in system 1 by first using respective computers 31 to establish a communications session with system 1 and to set up an account with a user name and password. The account is able to be linked with other accounts for billings purposes, or run as a standalone account. Typically such accounts allow access to Software-as-a-Service (SaaS) functionalities and involve access fees that are based upon one or more of: a flat fee for a given period - that is, subscription based fees, and usage fees based upon individual actions and usage.

[0079] Users 30 are typically advisors or agents to companies that are listed in a company register defined by repository 3, and authorising parties 32 are typically office holders for those companies. However, a user is also able to be an office holder and, conversely, an office holder a user.

[0080] In use, a given user, for example, user 30b, uses computer 31b to initiate a session with system 1 using his or her log in details to gain access to his or her account provided by system 1. Computer 31b includes, as schematically illustrated in Figure 5, one or more input devices 70 (typically, but not limited to, a keyboard and a computer mouse) by which the user is able to provide input to computer 31b. The computer also includes a graphical user interface (GUI) 71, in the form of a visual display, for displaying information to user 31b. As will be appreciated by those skilled in the art, many other input devices are available, and many different forms of GUI are available. Computer 31b also includes a processor 72 coupled to a memory module 73 and a communications

2018253452 22 Oct 2018 interface 74, such as a wireless WiFi connection. In other embodiments different connections are utilised to gain an internet connection, be it a modem, Ethernet port, serial port, or the like, or a wireless connection other than through a WiFi network. Memory module 73 includes software instructions 75, which are executable on processor 72. These software instructions allow computer 31 b to execute a software application, such as a proprietary application or web browser application and thereby render on-screen a user interface and allow communication with system 1. This user interface also allows for the creation, viewing and administration of user profiles, access to the internal communications interface, and various other functionalities.

[0081] During the session established between computer 31b and system 1, user 30b is able to use the functionality of system 1 that is available to that user’s account. In this example, repository 3 is a company register maintained by a government authority, and user 30b is permitted to initiate company searches of repository 3 to ascertain information about companies and, assuming the required authorisation is available, to submit updates to that information. This search is initiated by user 30b submitting to system 1, via computer 31b, a first user request. This request is able to take a number of forms, the more usual of which will be described below. The result of the first user request in this embodiment is the presentation to user 30b by computer 31b of a network visualisation relevant to the selected company. This network visualisation is then used as a platform for allowing user 31b to generate a second user request that system 1 is responsive to in generating an update request for repository 3.

[0082] A first form of the first user request includes prompting system 1 to serve up a web page to computer 31b that seeks input from the user about the repository or repositories to be searched and the search term or terms to be used. For example, if user 30b wishes to undertake a company search in respect of a company named Company A Limited, the user is able to select repository 3 (either directly or indirectly) and to type into a text field in the web page the phrase “Company A” or “Company A Limited”, “Company A Ltd”, or the like. Following confirmatory user input to computer 31b the search term (or terms) is submitted to system 1 and, in turn, system 1 queries repository 3. The results of the query are received by system 1 and database 7 is updated accordingly. This update is able to overwrite any superseded node and/or link records 9 and 10, or to create new node and/or link records 9 and 10, or both. Server 15 is responsive to the relevant ones of the node and link records 9 and 10 in the updated database 7 for generating visualisation data that is included within a web page that is served up to computer 31b in response to the first user request. Computer 31b then instantiates the web page to present the visualisation data to user 30b as a network

2018253452 22 Oct 2018 representation having nodes and links between the nodes that correspond to the node and link records 9 and 10 that were originally selected from database 7 by server 15. In this example, the visualisation data contained within the web page results in the presentation to user 30b of a network visualisation 80 shown in Figure 6. Visualisation 80 includes a node 81 representing Company A, and four other nodes 82, 83, 84 and 85 representing respective office holders of Company A who, in this example, are all natural persons. In other embodiments, for example where the nodes represent shareholders or other such relationships, the nodes are able to represent corporate persons or other such legal persons. Moreover, nodes are able to represent other characteristics or entities, such as physical address details, telecommunications details, and the like.

[0083] Visualisation 80 also includes links 86, 87, 88, 89 and 90 that extend between respective pairs of nodes and which indicate the relationship of the office holders to Company A. It will be noted that more than one relationship between nodes is possible. That is, more than one link between two nodes is possible.

[0084] Another form of a first request from computer 31 b is to prompt system 1 to serve up a web page to computer 31b network visualisation data relevant to Company A and which is accessed directly from database 17. That is, repository 3 is not initially queried by system 1. Computer 31b is responsive to the network visualisation data for presenting to the user, via the GUI of computer 31b, a network visualisation. If the data contained within database 7 matches that held in repository 3, then the network visualisation will correspond with visualisation 80. It will be appreciated that the data held in database 7 has been derived, for example, from prior searches of repository 3 or other repositories.

[0085] A third form of a first user request is for computer 31b to prompt system 1 to serve up a web page to computer 31b that is then populated with network visualisation data about Company A which accessed from computer 31b (for example from a storage device associated with computer 31b). As with the immediately preceding form of the first user request, computer 31b is responsive to the network visualisation data for presenting to the user, via the GUI of computer 31b, a network representation. The visualisation data stored at computer 31b is able to be derived directly or indirectly from records 9 and 10 held in database 7, or from repository 3, or another database or databases.

[0086] A fourth form of a first user request is for computer 31b to display a network visualisation and from this prompt system 1 to serve up additional network visualisation data about Company A.

[0087] A fifth form of a first user request is for computer 31b to display to user 30b a workspace in which the user is able, by providing user input to computer 31b, to construct a network visualisation for a proposed company. That is, user 31b is able to progressively

2018253452 22 Oct 2018 build nodes and links between the nodes to define a proposed new company structure, including a proposed name, proposed addresses details, proposed director details, and the like. The workspace includes tools to assist the user build the visualisation and prompts the user for the relevant information required to sufficiently define the nodes and the links between the nodes. This form of the first user request is available to assist the user enter the details required for registration of a new company, and system 1 is then responsive to the second user request to seek registration of that proposed company through submission of the update request to repository 3.

[0088] In this embodiment, network representation 80 allows user 30b to hover the pointer (or cursor) above the nodes and links to obtain additional information about that node or link. An example of this illustrated in Figure 7, in which the cursor is hovered over node 82 and a pop-up 91 presents further information about the director S Jones. It will be appreciated that additional or other information about the director is able to be displayed in such a pop-up. The information displayed in pop-up 91 is selected as being that information most relevant to the user or which is most inspected by users of system 1 as a whole. It is intended to provide user 30b with quick access to that information which is most likely to change, such as address details, so that the user is able to quickly and easily ascertain if there is a need for an update request to be made. If user 31 desires to update any details, the cursor is moved above the pop-up and a right click selected to initiate the second user request, which will be described in more detail below.

[0089] A further example is provided in Figure 8 of a network visualisation 92 that results from a first user request from computer 31b. This visualisation is derived from a fourth form of the first user request and includes not only nodes directly linked to the company of interest (Company Test 84 Pty Ltd) but also indirectly related nodes. In further embodiments more or less nodes and associated links are able to be included.

[0090] All the visualisation data for constructing visualisation 92 is provided by system 1 and derived from node and link records 9 and 10 contained within database 7. Those node and link records 9 and 10 are derived from one or more queries of repository 3 and/or one or more other repositories.

[0091] Visualisation 92 is differently configured to visualisation 80, and the second user request is generated differently, as will be described further below. More specifically, visualisation 92 includes:

• Two nodes 93 and 94 that represent respective companies identified as “Company Test 84 Pty Ltd” and “Company Test 82 Pty Ltd”.

• Two nodes 95 and 96 that represent respective natural persons identified as “Eddie Krabs” and “Both-Person One”.

2018253452 22 Oct 2018 • Two nodes 97 and 98 that represent respective addresses.

• Links between the nodes with respective annotations to describe the relationship between the nodes between which the links extend.

[0092] Visualisation 92 is presented visually to user 30b by the GUI of computer 31b. As this visualisation provides in the illustrated instance more information to user 31b than visualisation 80, it is differently configured. In particular, when user 30b moves the cursor over one of the nodes and left clicks, a dropdown list is provided to allow the generation of an update request. In Figure 8, the cursor was placed over node 97 and left clicked to provide a dropdown list 99. This list includes a number of icons that represent functional options that are able to be selected by user 30b (by providing user input into computer 31b) to perform respective functions. One of the options is the generation of the second user request. As there is, in this example, a desire by user 31b to update the address of Company Test 84 Pty Ltd, the relevant “edit” option is selected from list 99.

[0093] In other embodiments different user inputs are provided to present the dropdown list 99 for a given node. Examples of other such inputs include hovering a cursor over the node, right clicking the node, double clicking the node, and the like.

[0094] Once the edit option is selected to change the address, computer 31b prompts systeml for a web form which, when received, is instantiated and displayed to user 30b. A suitable web form 101 is illustrative in Figure 9, and includes for Company Test 84 Pty Ltd the present company address 102 and a plurality of editable fields 103. As the recording of such a change with repository 3 will require authorisation by an office holder of Company Test 84 Pty Ltd, form 101 also includes a dropdown list 104 for allowing the selection of the one of the office holders from whom authorisation will be sought and the email address for that office holder. In this instance the director having the name BothPerson One (illustrated as Dr One in the list) is selected. In Figure 10 the editable fields in form 101 are shown in a completed state. Once all those mandatory fields are completed (and satisfy the auto-correction functionality built into form 101) the Submit button 105 becomes active and is available for selection by user 30b. The selection of button 105 results in the completed form 101 being provided to system 1 as part of the second user input. Edit server 21 is responsive to completed form 101 to update the edit records to reflect the desired change or changes.

[0095] An authorisation engine, in the form of an authorisation server 110, is responsive to the updated edit records 14, for generating an authorisation request to gain authorisation from the authorising party 32b. In this embodiment the authorisation request is sent electronically to a third party digital security provider (for example, DocuSign, Inc.) which, in response, automatically generates an electronic communication - typically in the

2018253452 22 Oct 2018 form of an email - that is sent to the nominated authorising party 32b to seek the required authorisation. In other embodiments, system 1 communicates the authorisation request directly with the party 32b.

[0096] Party 32b accesses the authorisation request, or a communication consequent to and/or derived from the authorisation request, using smart phone 33b or other user device. If party 32b approves of the change - the details of which are included in the communication - then a digital signature is able to be defined by user input to phone 33b. That digital signature is then encrypted and otherwise securely dispatched to the third party digital security provider. Following from an automated parsing of the communication including the digital signature, the third party digital security provider generates the authorisation signal, which is communicated electronically to system 1.

[0097] Server 22 is responsive to the authorisation signal for accessing the relevant edit records in database 7 and generating the update request 2 that is communicated to interface 6. As request 2 has been authorised it will be pass the vetting processes performed by the front end of repository 3 and a confirmation signal will issue from interface 4. This confirmation signal contains minimal data, and is simply a confirmation that request 2 has been received and that repository 3 will be updated. The update typically occurs within minutes of the confirmation issuing.

[0098] In response to the confirmation signal, server 22 generates the update signal. Server 15 is responsive to the update signal and the relevant edit records for updating the visualisation database 7 to reflect the update to the company’s address that has been made at repository 3. That is, the editable fields in the relevant ones of the records in database 7 are updated with the new address details. Moreover, confirmation of the update is communicated to computer 31b and network representation 92 is updated to reflect the change.

[0099] It is significant to note that server 15 uses the data in the editable fields of the edit records 14 to populate the corresponding fields of the relevant node and/or link records that are updated. That is, system 1 does not further query repository 3 for this information. Moreover, the confirmation that is provided by system 1 to computer 31b also does not communicate the details of what was changed, only that the requested change has occurred. Accordingly, in this embodiment, the updating of the network visualisation by computer 31 b is taken from locally stored or cached data.

[00100] It will be appreciated that the above described operation is able to be applied to requesting updates in many other details for the company, to allow for the registration of a new company, and to allow for deregistration of a company, amongst other things.

2018253452 22 Oct 2018 [00101] User 30b is then able to use the update visualisation as a basis for making further searches or updating further details.

[00102] In some embodiments the party responsible for repository 3 appoints one or more information brokers to facilitate use of the repository. For example, the repository administered by ASIC allows direct public access for many queries. However, for more complex and regular users it is more convenient to make use of one of the seventeen ASIC approved information brokers that have EDGE access to repository 3 and which have developed specialist interfaces to facilitate interaction with the repository. An embodiment of this nature is illustrated in Figure 12, where corresponding features are denoted with corresponding reference numerals. In particular, an information broker facility 120 is an intermediary (defined by a computer system and associated software) between a system 121 and repository 3. The facility 120 is provided and maintained by an operator that may be the same or different from the operator of system 121. The communication between system 121 and facility 120 is typically via the internet (using standard internet protocols). To increase the rate of processing, it has been found that making use of dedicated software - in the form of APIs running on system 121 - that efficient and practical operational integration between system 121 and facility 120 is able to be established. Moreover, as facility 120 has a dedicated link to repository 3 it is able to have update requests submitted more cleanly - that is, with less requirements for downloads from repository 3 - than would be required by the use of other conventional methods.

[00103] A flowchart of the exemplary steps followed by system 121 is illustrated in Figure 13. In particular, at step 200, a user, such as user 30b, uses a user device, such as a desktop computer 31b, to log into system 121. The user then at step 201 identifies and existing company or a new company and, at step 202, generates a new network visualisation or updates an existing network visualisation. If the user observes, for example, that for the company (which is represented in this embodiment by a node on the network visualisation) the address details (represented by a further node) related to a given director (who is represented by another node) need to be updated, the user selects the another node at step 203 by providing user input to the user device. This brings up the options for the user to select from, one of which is to edit the address details for another node. System 121 is responsive to this selection for accessing the relevant ones of records 9 to generate a web form that is served up to the user device and which includes a plurality of editable fields. This allows the user to update the selected ones of the editable fields at step 204 and submit the form to system 121. The system then creates edit records corresponding to the changes suggested to the editable fields and for

2018253452 22 Oct 2018 recoding other information such as the identity of the user, the time and date of submission, the name and electronic contact details for the authorising party and other details required for audit and quality control purposes. System 121 then, at step 205, identifies from the submitted web form the authorising party and the relevant contact details for that party. If that identification occurs successfully and in accordance with the rules implemented by system 121, at step 206 the system 121 communicates with the third party provider to initiate the external authorisation process. At step 207 the third party provider seeks the authorisation from the authorising party by sending an email that allows the authorising party, if approving the change, to submit a secure digital signature. If that signature is forthcoming from the authorising party, the third party provider issues the authorisation signal to system 121. Once the authorisation signal has been received, system 121 progresses to step 208 and communicates to an information broker (that is, to facility 120) to update data derived from the edit records and which is indicative of the required update. Facility 120 is responsive to the update data for preparing at step 209 the update request that is to be submitted to the data repository administered by ASIC. The information broker in this embodiment is an approved broker and has use of the EDGE service for interacting with the repository.

[00104] At step 210 the submitted request is processed by the ASIC platform and a confirmation of receipt of the request is provided electronically and automatically to facility 120. The receipt contains no information about the nature of the changes requested, but will not issue unless the changes sought have been accepted.

[00105] Once facility 120 obtains the electronic receipt from repository 3, it automatically communicates this, at step 211, to system 121. The system is responsive to that communication to reference the relevant edit records to then update the relevant node and link records. That is, the node and link records are updated to reflect the details of the change, notwithstanding that the details were not sourced directly from repository 3. This removes the need to once again query repository 3 to confirm the new details. Moreover, although the node and link records are selectively updated to reflect the confirmed change request, the network visualisation data need not be updated immediately, or at all. For example, that visualisation data is able to be deleted, and fresh visualisation data, which reflects the updates, generated later, should it be required.

[00106] System 121 also sends a confirmation signal to the user device at step 213, which allows the user device to update, at step 202, the network visualisation for the user on the user device. Again, system 121 only provides a confirmation signal and need not send all the edited details, for those details are retained on the user device.

2018253452 22 Oct 2018 [00107] In the event the details were not maintained on the user device - for example, if the initial session with system 121 ended before the confirmation signal from system 121 was provided - then it is possible to have the updated visualisation data generated and sent, either in whole or in part, to the user device.

[00108] With the network visualisation on the user device updated, the user is then able to continue using the network visualisation to request other edits, or to do other searching or analysis.

[00109] The operation of the above embodiment has been described with reference to a user, who is an agent of the company concerned, being able to edit - that is, submit a change request - with a government administered repository to affect change of an address for one of the officeholders of the company. It will be appreciated by those skilled in the art, with the benefit of the teaching herein, that other forms of edits and corresponding change requests are also able to be generated and processed with the embodiments of the invention. For example, the above embodiments also accommodate change requests for:

• A change in an address for a company.

• A change of an officeholder (for example, a change of director or company secretary) or the change of a shareholder. This includes the cessation (that is, the removing of a name) and changes to offices or roles.

• A change to shareholdings (which in the above embodiment is represented by a link between two nodes), including allocations, book values of shares, transfers and company share structures/tables.

• A change to the company name.

• A change to the company status. For example, by allowing a change request to reflect an application for voluntary deregistration.

[00110] As mentioned above, each node represents an entity or a type of information related to that entity. System 1 and 121 are responsive to the nature or type of the node for providing options to the user as to which ones of the change requests are available. For example, the options for a node representing a company will be different to those for a node representing a director. For example:

• Selecting an address node opens an Address Edit screen, with the option to change an address only. It displays the current address, and includes a field for the new address and the ability to nominate the effective date of change.

2018253452 22 Oct 2018 • Selecting a director/secretary/shareholder node opens a Stakeholder Edit screen with the option to either cease or change a role. This screen displays the current role held, an option to cease the role and to nominate the effective date of change, or the option to add an additional role not currently held, again with the ability to nominate the effective date of change.

• Selecting shareholdings (represented in this embodiment as a link between nodes) opens a share table edit screen allowing for changes to any record in the shares structure of the company.

• Selecting a company name node opens a Company Edits screen with the option to change the name of the company.

• Selecting a company name node opens a Company Edits screen with the option to voluntarily deregister the company.

[00111] It will be appreciated that many other selections and options are able to be offered in other embodiments.

[00112] Systems 1 and 121 allow the enrolled users, whether or not they are directly appointed agents for the company, to initiate the generation of a change request. This includes a one-off request, or multiple requests for updating the details for multiple entities in multiple repositories. It will be appreciated that agents are also able to use system 1 and system 121 to generate the change requests.

[00113] The safeguards included within the systems to discourage fraudulent or unscrupulous behaviours include the need to gain the authorisation from an authorised party, and the logging of all steps in the edit records or other records held within systems 1 and 121. In other embodiments different or additional safeguards are used.

[00114] In the above embodiments each change request is for a given address, name or other such detail. In some embodiments, multiple changes to a name and address are able to be communicated collectively to the authorising party and authorised with a single digital signature. In other embodiments, the multiple proposed changes are communicated to the authorising party as a single communication, but require separate digital signatures. [00115] In further embodiments, the system is responsive to the nature of the change being sought for determining the number of authorising parties that have to provide a digital signature to provide the required authorisation for the request to be generated and submitted. The relevant communications are then made to the individual authorising parties and the responses monitored and assessed prior to any change request being submitted to the repository.

2018253452 22 Oct 2018 [00116] When communicating with the user when attempting to submit a second user request, system 1 provides a pop-up or screen with text and or graphics to reiterate the full details of the changes being identified and to provide a disclosure of the legal obligations of the individual seeking to make the change. Similarly when communicating with the authorising party or parties, full details of the proposed change are communicated, together with a disclosure of the legal obligations of the individuals in authorising or not authorising the change.

[00117] The use of the above embodiments allows the user, with only a single user account - that is, the account provided by system 1 or system 121 - to undertake the actions required. This is a substantive improvement over the disparate, competing and confusing systems of the prior art. That is, the embodiments of the invention reduce the amount of data entry, duplication, administration, and effort required by an agent or officeholder to submit a change request. This in turn reduces the risk of errors in the data, and reduces the overall need for transmitting large amounts of data between parties. The preferred embodiments also provide a store of records to allow for auditing of the changes which is consistent with the records held in repository 3. These records in the embodiments are always available to current users of system 1 and 121 (if they are authorised officers or agents of the company), which often obviates the need to later query repository 3 again for that information.

[00118] In overview, the above embodiments offer the following main steps:

• Prompting a user for input, where the user operates a computer to access system 1 to request a search of the ASIC repository 3.

• Once the search is performed the results are converted to network visualisation data and a workspace is opened on the user device for the user to view a network visualisation populated by the network visualisation data.

• The user is able to select a node (or in some embodiments multiple nodes) using the user device. This then allows the user to edit one or more editable records associated with the node. That is, the network visualisation is a starting platform for the generation and submission of an update request.

• The editable fields which are edited by the user are used to create new edit records (or to update existing edit records) and are stored by system 1. In this embodiment, use is made of cloud storage. In other embodiments alternative forms of storage are used.

2018253452 22 Oct 2018 • In some embodiments, a further computer/server is notified (such as an information broker service) once the edit records are received. In this case, system 121 is responsive to the edit records for creating an XML file indicative of the changes (and other information) and which is delivered to a server of the information broker with the use of an API. In other embodiments different formats and communication methods are used.

• On receiving the XML file the server of the information broker generates the required update request and submits to the ASIC administered repository using its agent and EDGE credentials.

• The ASIC repository receives the update request and automatically verifies its acceptance or otherwise. If accepted, the backend of the repository updates the company records in the repository in accordance with the update request.

• Once the repository is updated, the frontend issues a confirmation to the server of the information broker, which then sends the same confirmation via an API to system 121.

• The node and link records are then updated, as required, to reflect that the update request has been submitted at and accepted by repository 3..

[00119] The above illustrative steps are able to be changed or substituted depending upon the nature of the updates and the repository or repositories to which those updates are to be submitted. For example, in another embodiment the XML files are captured from a webpage portal of system 1 or 121. In another embodiment, the second user request also includes an XML file to facilitate downstream processing. Accordingly, for those embodiments where the user device is likely to have limited connectivity or bandwidth, system 1 undertakes more processing at that device and at systeml itself to minimise the bandwidth limitations.

[00120] In other embodiments, system 1 includes the relevant edit records, or data derived from the edit records, in an XML file that forms part of the corresponding update request. This request is then sent directly to repository 3.

[00121] The various options and variations described above are able to be combined in other combinations, and different options offered to different users and/or in respect of different repositories.

[00122] In system 121, facility 120 makes use of software code. At least some of this code is written in the Java programming language and enables the connection of the servers within facility 120 with repository 3. In that embodiment, repository 3 is exemplarily

2018253452 22 Oct 2018 illustrated as the ASIC webservices platform. This software code performs the acts of notifying the ASIC repository of an update request to register a company, or to make a change to an existing company record. As will be appreciated by those skilled in the art, the Java programming language is written for web content to be transmitted via the use of an application programming interface (API).

[00123] System 121 also makes use of software code. At least some of this code is written in the .Net software language and executed within other software. This allows for Common Language Infrastructure (CLI), which provides a language-neutral platform for application development and execution, including functions for exception handling, garbage collection, security, and interoperability. By implementing the core aspects of .NET Framework within the scope of CLI, these functions are not tied to one language but are available across the many languages supported by the framework.

[00124] Suitable CLI technologies are implemented to allow the core code to function as desired. The exact nature of the CLI technologies used varies between embodiments.

[00125] The network visualisation workspace that is presented to the user, and which in the above embodiments forms the platform for the functionality offered, is a website application that provides the input data mechanism. As mentioned above, that input data is able to come from one or more of a variety of sources. Most typically, the input data is imported from either an ASIC extract request (obtained from querying the repository), or a new company incorporation form. However, in other embodiments alternative sources are used. The input data is initially used to update the node and link records (if that is required) and then the network visualisation data is created, as described above.

[00126] Making use of the visualisation data, including the most recent data and any historical data, allows the network visualisation presented to the user to not only display the status quo of the network visualisation, but a chronological sequence of changes to the visualisation and the ability to drill down into any of the earlier visualisations to ascertain who authorised the change and who initiated the update request. Other historical presentations and timelines are also available.

[00127] The use of the workspace and the dynamic updating (or chronological navigation) is achieved in the above embodiments using API calls between the user device and system 1 or system 121. However, the network visualisation functionality is written in React and C# .Net, and is a separate application. This functionality is deployed from a website that the user is able to access when logged into an authorised account on system 1 or system 121. The functionality to enable the second user request, however, is written in C#, .Net Core and deployed as a container in a hosting technology (in the

2018253452 22 Oct 2018 specific embodiment for system 1 the hosting technology is Rancher) and is hosted in a cloud-based system such as that offered by Amazon Web Services.

[00128] To operationally connect system 121 to facility 120 use was made of:

• An external third party provider to gain the authorisation - with the relevant applications being written in C#, .Net.

• Separate modules for both the network visualisation and the edit data, or the second user requests (the submission of the competed web form from the user device to system 121) • A third app to upload a form via API.

[00129] This in turn makes use of:

• An API between system 1 (and system 121) and the third party provider seeking the authorisation. This API also supports the second party requests.

• In the workspace on the user device, new command buttons to allow initiation of the new functionalities.

[00130] All the above applications are secured by an authentication server provided by system 1 and system 121. This provides for a single sign on, and therefore the users do not have to login to all the applications separately. The use of the third party provider to gain the authorisation (in this case the SignIT service) allows systems 1 and 121 to gain authorisation the change requests so as to satisfy the regulatory requirements. This combination removes the requirements for the users to be EDGE registered and to be registered with the regulator as an agent for the relevant.

[00131] Reference is now made to Figure 14, which is a flowchart providing an overview of the operation of a system according to an embodiment for the more common changes that result in a user initiation the generation and submission of an update request to repository 3. In describing the steps in this figure use will be made below of reference numerals in the drawings, where those reference numerals are enclosed in parenthesis and which commence with (100).

[00132] Step (100): Order Company Extract/Register New Company. A search is initiated by the user and the default action is to order a company extract from repository 3. Once the returned search is available, the user is able to click a display button (see step (102)) to display the extract in the form of a network visualisation presented in a Workspace. Alternatively, the company is able to be initially registered via the system and the display button selected to display the company registration as a visualisation in the workspace.

2018253452 22 Oct 2018 [00133] Step (101): Open the workspace. Opening the workspace involves clicking on the display button on the top left-hand screen in the search results section. In other embodiments the button is located elsewhere.

[00134] Step (102): Company details and details of relevant other entities presented to the user in a network visualisation. That is, the workspace displays a network visualisation of the company records, either from the ASIC extract or the new registration.

[00135] Step (200): Select company address node. Navigating in the workspace and clicking on a specific address node to select it or to otherwise make it active. As to the later, the relevant node is able to be active by default, for example.

[00136] Step (201): Right click. Performing a right click on the address node opens the options menu for available functions, including the request to edit the information. The menu provided is accessed from the workspace. Selecting the “Edits” options opens a new screen with the existing address details associated with that node.

[00137] Step (202): Address edit screen. The editing of editable address details is a normal text editing process. The Edit screen will display the current address of the company, including a blank field for the new address to be entered, and a date field to add the effective date of change of the address. The need to specify this date is a regulatory requirement.

[00138] Step (203): Request to change. The request for change is packaged in an XML file that can be consumed by the relevant repository.

[00139] Step (204): Confirmation from ASIC. This is provided once the update request has been submitted and automatically accepted. The relevant node, link and edit records are then updated.

[00140] Step (300): Select a director/secretary/shareholder. Navigating in the workspace and clicking on a specific stakeholder using the current invention to select it, or to otherwise make it active.

[00141] Step (301): Right click. A right click on the stakeholder node opens the options menu for the available functions including the Edits function for initiating an update request. Selecting the Edits option opens a new screen with the Stakeholder details.

[00142] Step (302): Stakeholder edit screen. The Stakeholder Edit screen displays the current role or roles of the stakeholder, together with the option to appoint the stakeholder to a new role, or have the stakeholder cease in an existing role. There is also a field to include the effective date of change of the address, which is a mandatory requirement of ASIC. This functionality is able to be extended to update/or correcting details of a stakeholder. For example, requesting a spelling correction of a name, providing correct birth details, add/remove middle names (including maiden names) and the like.

2018253452 22 Oct 2018 [00143] Step (303): Request to change. The process of the request submission is through the process of a delivery package sent from the core system of the embodiment to an information broker facility via an API. The information broker is responsive to the package for automatically preparing and sending to ASIC an update request (also including an XML file) that is suitable for consumed by the ASIC repository.

[00144] Step (304): Confirmation from ASIC. This is provided once the update request has been submitted and automatically accepted. The relevant node, link and edit records are then updated.

[00145] Step (400): Select a shareholding (a link between nodes). Navigating in the workspace and clicking on a specific shareholding displayed on a link to a shareholder node, and selecting it, or otherwise making it active.

[00146] Step (401): Right click. Within the workspace a right click on the link gives rise to a similar drop down box to that provided for nodes, although with different selections.

[00147] Step (402): Shareholdings edit. If selected this allows the user to suggest edits to the share table of the company. This data is able to be obtained from an ASIC extract, or from the new company registration form earlier completed by the user. The user is able to seek changes to the table. When doing so, the date of change is required as this is a mandatory part of any update request as required by ASIC.

[00148] Step (403): Request to change. The process of the request submission is through the process of a delivery package sent from the core system of the embodiment to an information broker facility via an API. The information broker is responsive to the package for automatically preparing and sending to ASIC an update request (also including an XML file) that is suitable for consumed by the ASIC repository.

[00149] Step (404): Confirmation from ASIC. This is provided once the update request has been submitted and automatically accepted. The relevant node, link and edit records are then updated.

[00150] Step (500): Select the company name node. Navigating in the workspace and clicking on the Company name node to select it, or to otherwise make it active.

[00151] Step (501): Right click. A right click on the Company name node opens the options menu for the available functions including the function to seek to edit the name. Selecting the edit function opens a new screen with the Company details.

[00152] Step (502): Change of company name. The new screen displays the current Company name, with tabs for additional company changes. An additional field is provided for the user to add a new Company name, with the requirement to enter the effective date of change. The inclusion of this date in an update request is a requirement from ASIC.

2018253452 22 Oct 2018 [00153] Step (503): Request to change. The process of the request submission is through the process of a delivery package sent from the core system of the embodiment to an information broker facility via an API. The information broker is responsive to the package for automatically preparing and sending to ASIC an update request (also including an XML file) that is suitable for consumed by the ASIC repository.

[00154] Step (504): Confirmation from ASIC. This is provided once the update request has been submitted and automatically accepted. The relevant node, link and edit records are then updated.

[00155] Step (510): Deregistration tab. The new screen displays the current Company name, with tabs for additional company changes. The deregistration tab displays the current Company name, with an additional field to enact a request for voluntary deregistration of the company. Such as request must be accompanied by a declaration acknowledging the proposed change, with the requirement to enter the effective date of change also applying.

[00156] Step (511): Request to change. The process of the request submission is through the process of a delivery package sent from the core system of the embodiment to an information broker facility via an API. The information broker is responsive to the package for automatically preparing and sending to ASIC an update request (also including an XML file) that is suitable for consumed by the ASIC repository.

[00157] Step (512): Confirmation from ASIC. Once the confirmation of the receipt of the update request is provided by ASIC, the system of the embodiments updates the relevant node and link records to indicate that ‘Deregistration is PENDING’.

[00158] The major advantages provided by one or more of the above embodiments include:

• Reducing the network traffic that is required with the third party repository to allow an update to occur. For example, the confirmation signal indicates that the update has been accepted. Accordingly, there is no need to further access the repository to confirm the update has been made and to communicate the details of what has been changed. The latter details are all held by the embodiment of the invention.

• Reducing the network traffic with the repository that is required for the public to gain the benefit of up-to-date information. For example, the need to access the repository more than once to gain sufficient comfort that the stored information is up-to-date is reduced. Additionally, as the user does not need to access the repository after making the change to verify it has been accurately made, the risk of slowing the response time of the repository is lessened.

2018253452 22 Oct 2018 • Reducing the access cost involved in using publicly accessible large-scale, typically government, data repositories. For example, some repositories have access charges, and the public will be better placed to contain these charges by undertaking less repeat queries of the repository to ascertain the currency of the information.

• Leveraging from locally held data for updating network visualisations once an update request has been made.

• Reducing the network traffic between the user device and the system.

• Allowing multiple repositories to be easily updated with the same change, hence minimising user input and better avoiding omission of an update to one or more of the repositories.

• Facilitating the self-reporting of updates to government repositories.

• Reducing the risk of non-compliance with local laws for company officers and other regulated entities.

• Reducing the time commitment required to make a change to the third party repository or repositories.

• The ability for one off changes to be easily made, as authorisation is able to be obtained from an authorising party by any user who is correctly enrolled in the system and who has initiated a valid session with the system.

• The ability to offer a two-way flow of information using a network visualisation. That is, when the user notices a change needs to be made, he or she does not have to open another application to affect that change. Rather, the user simply selects the relevant node or link and right clicks to obtain a menu of the available update requests that are available. Accordingly, the embodiments facilitate and encourage the making of update requests.

Conclusions and Interpretation [00159] It will be appreciated that the disclosure above provides various significant systems and methods for generating an update request.

[00160] Unless specifically stated otherwise, it is appreciated that throughout the specification terms such as processing, computing, calculating, “determining”, analyzing” or the like, refer to the action and/or processes of a computer or computing system, or similar electronic computing device, that manipulate and/or transform data

2018253452 22 Oct 2018 represented as physical, such as electronic, quantities into other data similarly represented as physical quantities.

[00161] In a similar manner, the term processor may refer to any device or portion of a device that processes electronic data - for example, from registers and/or memory - to transform that electronic data into other electronic data that, for example, may be stored in registers and/or memory. A “computer” or a “computing machine” or a “computing device” or a “networked device” or a computing platform may include one or more processors.

[00162] Reference is made in this specification to “data records” or “records”. These terms are used to describe groupings of data for storage or transmission. That is not to imply that the data need be all stored together or transmitted together, simply that the record, however stored or transmitted, provides a functional whole when assembled or accessed.

[00163] The methodologies described herein are, in one embodiment, performable by one or more processors that accept computer-readable (also called machine-readable) code defining a set of instructions that when executed by one or more of the processors carry out at least one of the methods described herein. Any processor capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken are included. Thus, one example is a typical processing system that includes one or more processors. Each processor may include one or more of a CPU, a graphics processing unit, and a programmable DSP unit. The processing system further may include a memory subsystem including main RAM and/or a static RAM, and/or ROM. A bus subsystem may be included for communicating between the components. The processing system further may be a distributed processing system with processors coupled by a network. If the processing system requires a display, such a display may be included, for example, a liquid crystal display (LCD) or a cathode ray tube (CRT) display or the like. If manual data entry is required, the processing system also includes an input device such as one or more of an alphanumeric input unit such as a keyboard, a pointing control device such as a mouse, touchpad, roll pad and so forth. The term “memory unit” as used herein, if clear from the context and unless explicitly stated otherwise, also encompasses a storage system such as a disk drive unit. The processing system in some configurations may include a sound output device, and a network interface device. The memory subsystem thus includes a computer-readable carrier medium that carries computerreadable code (for example, software, which includes application software) including a set of instructions to cause performing, when executed by one or more processors, one of more of the methods described herein. Note that when the method includes several elements - for example, several steps - no ordering of such elements is implied, unless

2018253452 22 Oct 2018 specifically stated. The software may reside in the hard disk, or may also reside, completely or at least partially, within the RAM and/or within the processor during execution thereof by the computer system. Thus, the memory and the processor also constitute computer-readable carrier medium carrying computer-readable code.

[00164] Furthermore, a computer-readable carrier medium may form, or be included in, a computer program product.

[00165] In alternative embodiments, the one or more processors operate as a standalone device or may be connected - for example, networked to other processor(s) in a networked deployment. The one or more processors may operate in the capacity of a server or a user machine (such as a user device or a client device) in server-user network environment, or as a peer machine in a peer-to-peer or distributed network environment. The one or more processors may form in part a personal computer (PC) (also referred to as a desktop computer), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a network router, a smart phone, a switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.

[00166] Note that while diagrams only show a single processor and a single memory that carries the computer-readable code, those in the art will understand that many of the components described above are included, but not explicitly shown or described, in order not to obscure the inventive aspect. For example, while only a single machine is illustrated, the term machine shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

[00167] Thus, one embodiment of each of the methods described herein is in the form of a computer-readable carrier medium carrying a set of instructions - for example, a computer program - that is for execution on one or more processors - for example, one or more processors that are part of web server arrangement. Thus, as will be appreciated by those skilled in the art, embodiments of the present invention may be embodied as a method, an apparatus such as a special purpose apparatus, an apparatus such as a data processing system, or a computer-readable carrier medium - for example, a computer program product. The computer-readable carrier medium carries computer readable code including a set of instructions that when executed on one or more processors cause the processor or processors to implement a method. Accordingly, aspects of the present invention may take the form of a method, an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of carrier medium (e.g., a computer

2018253452 22 Oct 2018 program product on a computer-readable storage medium) carrying computer-readable program code embodied in the medium.

[00168] The software may further be transmitted or received over a network via a network interface device. While the carrier medium is shown in an exemplary embodiment to be a single medium, the term carrier medium should be taken to include a single medium or multiple media - for example, a centralized or distributed database, and/or associated caches and servers - that store the one or more sets of instructions. The term carrier medium shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by one or more of the processors and that cause the one or more processors to perform any one or more of the methodologies of the present invention. A carrier medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media includes, for example, optical, magnetic disks, and magneto-optical disks. Volatile media includes dynamic memory, such as main memory. Transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise a bus subsystem. Transmission media also may also take the form of acoustic or light waves, such as those generated during radio wave and infrared data communications. For example, the term carrier medium shall accordingly be taken to include, but not be limited to, solid-state memories, a computer product embodied in optical and magnetic media; a medium bearing a propagated signal detectable by at least one processor of one or more processors and representing a set of instructions that, when executed, implement a method; and a transmission medium in a network bearing a propagated signal detectable by at least one processor of the one or more processors and representing the set of instructions.

[00169] It will be understood that the steps of methods discussed are performed in one embodiment by an appropriate processor (or processors) of a processing (i.e., computer) system executing instructions (computer-readable code) stored in storage. It will also be understood that the invention, unless specifically defined in a given claim, is not limited to any particular implementation or programming technique and that the invention may be implemented using any appropriate techniques for implementing the functionality described herein. The invention as defined by a given claim is not limited to any particular programming language or operating system unless that programming language or operating system is explicitly defined in that claim.

[00170] It should be appreciated that in the above description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, Figure, or description thereof for the purpose of

2018253452 22 Oct 2018 streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the Detailed Description are hereby expressly incorporated into this Detailed Description, with each claim standing on its own as a separate embodiment of this invention.

[00171] Furthermore, while some embodiments described herein include some but not other features included in other embodiments, combinations of features of different embodiments are meant to be within the scope of the invention, and form different embodiments, as would be understood by those skilled in the art. For example, in the following claims, any of the claimed embodiments can be used in any combination.

[00172] Furthermore, some of the embodiments are described herein as a method or combination of elements of a method that can be implemented by a processor of a computer system or by other means of carrying out the function. Thus, a processor with the necessary instructions for carrying out such a method or element of a method forms a means for carrying out the method or element of a method. Furthermore, an element described herein of an apparatus embodiment is an example of a means for carrying out the function performed by the element for the purpose of carrying out the invention.

[00173] In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In other instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description. [00174] Similarly, it is to be noted that the term “connected”, when used in the claims, should not be interpreted as being limited to direct connections only. Thus, the scope of the expression “a device A connected to a device B” should not be limited to devices or systems wherein an output of device A is directly connected to an input of device B. It means that there exists a path between an output of A and an input of B, which may be a path including other devices or means. Connected may mean that two or more elements are either: in direct physical contact, or electrical contact, or communicative contact with each other; or not in direct physical contact, or electrical contact, or communicative contact with each other but yet still co-operate or interact with each other.

[00175] Thus, while there has been described what are believed to be the preferred embodiments of the invention, those skilled in the art will recognize that other and further modifications may be made thereto without departing from the spirit of the invention, and it is intended to claim all such changes and modifications as falling within the scope of the

2018253452 22 Oct 2018 invention. Functionality may be added or deleted from the block diagrams and operations may be interchanged among functional blocks. Steps may be added or deleted to methods described within the scope of the present invention.

2018253452 22 Oct 2018

Claims

2018253452 22 Oct 2018

1. A system for generating an update request to update a third party data repository, wherein the repository has a repository interface for receiving the request and providing a confirmation signal that the request has been received, and wherein the system includes:

(a) a visualization database for containing:

(i) a plurality of node records and link records, wherein one of the records includes at least one editable field; and (ii) edit records indicative of a change to one or more of the at least one editable field;

(b) a visualization engine that accesses the visualization database and which is selectively responsive to:

(i) the records for generating network visualization data indicative of a plurality of nodes and links between the nodes, wherein one of the nodes or links is derived from the one of the records; and (ii) an update signal and the edit records for updating the visualization database;

(c) an edit engine that is responsive to:

(i) the selection of the one of the nodes or links indicated by the network visualization data for allowing editing of one or more of the at least one editable field; and (ii) the editing of the one or more of the at least one editable field for updating the edit records; and (d) an update engine that is responsive to:

(i) the edit records for selectively generating the update request; and (ii) the confirmation signal for generating the update signal.
2. A system according to claim 1 wherein each of the node records includes at least one editable field.
3. A system according to claim 1 wherein each of the link records includes at least one editable field.
4. A system according to claim 1 wherein not all of the node records include at least one editable field.
5. A system according to claim 1 wherein not all of the link records include at least one editable field.

2018253452 22 Oct 2018
6. A system according to claim 1 wherein the update engine is responsive to the edit records for generating at least one further request to update respective further repositories.
7. A system according to claim 6 wherein at least one of the further repositories is a further third party repository.
8. A system according to any one of claims 1 to 7 including a query engine for querying of one or more data sources and being selectively responsive to results of the query or queries for creating, deleting or updating the node records and the link records.
9. A system according to claim 8 wherein the one or more data sources includes the third party repository.
10. A system according to claim 9 wherein the one or more data sources comprises the third party repository.
11. A system according to any one of claims 1 to 10 wherein the update engine is responsive to a first user request from a user device for making the network visualization data available to the user device.
12. A system according to claim 11 wherein the edit engine is responsive to a second user request from the user device to update the edit records.
13. A system according to claim 12 wherein the user device includes a GUI which is responsive to: the network visualization data for visually displaying to a user of the user device a corresponding network visualization; and input provided by the user to the user device to generate the second user request.
14. A system according to any one of claims 1 to 13 including an authorization engine that is responsive to the edit records for selectively generating an authorization signal, wherein the update engine is responsive to the authorization signal for generating the update request.
15. A system according to claim 14 wherein the authorization engine: generates an authorization request for communicating to an authorizing party; and is responsive to a response from the authorizing party to the authorization request to selectively generate the authorization signal.
16. A system for generating an update request to update a third party data repository, wherein the repository has a repository interface for receiving the request and providing a confirmation signal that the request have been received, and wherein the system includes:

(a) a visualization database for containing:

2018253452 22 Oct 2018 (i) a plurality of node records and link records, wherein the node records each include at least one editable field; and (ii) edit records indicative of a change to one or more of the at least one editable field;

(b) a visualization engine that accesses the visualization database and which is selectively responsive to:

(i) the records for generating network visualization data indicating a plurality of nodes corresponding to the node records and a plurality of links between the nodes corresponding to the link records; and (ii) an update signal and the edit records for updating the visualization database;

(c) an edit engine that is responsive to:

(i) the selection of one of the nodes in the network visualization for allowing editing of one or more of the at least one editable field of the corresponding node record; and (ii) the editing of the one or more of the at least one editable field for updating the edit records; and (d) an update engine that is responsive to:

(i) the edit records for selectively generating the update request; and (ii) the confirmation signal for generating the update signal.
17. A system according to claim 16 wherein the link records each include at least one editable field and the edit engine is responsive to:

(c) the selection of one of the links indicated by the network visualization data for allowing editing of one or more of the at least one editable field of the corresponding link record; and (d) the editing of the one or more of the at least one editable field for updating the edit records.
18. A system for generating an update request to update a third party data repository, wherein the repository has a repository interface for receiving the request and providing a confirmation signal that the request have been received, and wherein the system includes:

(a) a visualization database for containing:

(i) a plurality of node records and link records, wherein the link records each include at least one editable field; and (ii) edit records indicative of a change to one or more of the at least one editable field;

2018253452 22 Oct 2018 (b) a visualization engine that accesses the visualization database and which is selectively responsive to:

(i) the records for generating network visualization data indicative of a plurality of nodes and links between the nodes; and (ii) an update signal and the edit records for updating the visualization database;

(c) an edit engine that is responsive to:

(i) the selection of the one of the links indicated by the network visualization data for allowing editing of one or more of the at least one editable field; and (ii) the editing of the one or more of the at least one editable field for updating the edit records; and (d) an update engine that is responsive to:

(i) the edit records for selectively generating the update request; and (ii) the confirmation signal for generating the update signal.
19. A system for updating network visualization data, the system including:

(a) a visualization database for containing:

(i) a plurality of node records and link records, wherein one of the records includes at least one editable field; and (ii) edit records indicative of a change to one or more of the at least one editable field;

(b) a visualization engine that accesses the visualization database and which is selectively responsive to:

(i) the records for generating network visualization data indicative of a plurality of nodes and links between the nodes, wherein one of the nodes or links is derived from the one of the records; and (ii) an update signal and the edit records for updating the visualization database;

(c) an edit engine that is responsive to:

(i) the selection of the one of the nodes or links indicated by the network visualization data for allowing editing of one or more of the at least one editable field; and (ii) the editing of the one or more of the at least one editable field for updating the edit records;

(d) a request engine for generating an update request to update a third party data repository, wherein the repository has a repository interface for receiving the

2018253452 22 Oct 2018 request and providing a confirmation signal that the request has been received; and (e) an update engine that is responsive to:

(i) the edit records for selectively generating the update request; and (ii) the confirmation signal for generating the update signal.
20. A system according to claim 19 wherein the update engine is responsive to a first user request from a user device for making the network visualization data available to the user device.
21. A system according to claim 20 wherein the edit engine is responsive to a second user request from the user device to update the edit records.
22. A system according to claim 12 wherein the user device includes a GUI which is responsive to: the network visualization data for visually displaying to a user of the user device a corresponding network visualization; and input provided by the user to the user device to generate the second user request.
23. A system according to claim 22 wherein the visualization engine is responsive to the updating of the visualization database for allowing the GUI to visually display to the user a correspondingly updated network visualization.
24. A system according to any one of claims 19 to 23 including an authorization engine that is responsive selectively to the edit records for generating an authorization signal, wherein the update engine is responsive to the authorization signal for generating the update request.
25. A system according to claim 24 wherein the authorization engine: generates an authorization request for communicating to an authorizing party; and is responsive to a response from the authorizing party to the authorization request to selectively generate the authorization signal.
26. A system for generating an update request to update a third party data repository, wherein the repository has a repository interface for receiving the request and the system includes:

(a) a visualization database for containing:

(i) a plurality of node records and link records, wherein one of the records includes at least one editable field; and (ii) edit records indicative of a change to one or more of the at least one editable field;

(b) a visualization engine that accesses the visualization database and which is selectively responsive to the records for generating network visualization data

2018253452 22 Oct 2018 indicative of a plurality of nodes and links between the nodes, wherein one of the nodes or links is derived from the one of the records:

(c) an edit engine that is responsive to:

(i) the selection of the one of the nodes or links indicated by the network visualization data for allowing editing of one or more of the at least one editable field; and (ii) the editing of the one or more of the at least one editable field for updating the edit records;

(d) an authorization engine that is responsive to the edit records for selectively generating an authorization signal; and (e) an update engine that is responsive to the authorization signal and the edit records for generating the update request.
27. A system according to claim 26 wherein the authorization engine:

generates an authorization request for communicating to an authorizing device of an authorizing party; and is responsive to a response from the authorizing device of the authorizing party to the authorization request to selectively generate the authorization signal.
28. A system according to claim 27 wherein the authorizing device includes a GUI for: presenting visually to the authorizing party the authorization request; being responsive to predetermined input to the authorizing device by the authorizing party for generating the authorizing signal.
29. A system according to claim 28 wherein the predetermined input is one or more of: a signature;

a password; and a code.
30. A system for generating an update request to update a third party data repository, wherein the repository has a repository interface for receiving the request and the system includes:

(a) a visualization database for containing:

(i) a plurality of node records and link records, wherein the node records each include at least one editable field; and (ii) edit records indicative of a change to one or more of the at least one editable field;

(b) a visualization engine that accesses the visualization database and which is selectively responsive to the records for generating network visualization data

2018253452 22 Oct 2018 indicating a plurality of nodes corresponding to the node records and a plurality of links between the nodes corresponding to the link records;

(c) an edit engine that is responsive to:

(i) the selection of one of the nodes in the network visualization for allowing editing of one or more of the at least one editable field of the corresponding node record; and (ii) the editing of the one or more of the at least one editable field for updating the edit records; and (d) an authorization engine that is responsive to the edit records for selectively generating an authorization signal; and (e) an update engine that is responsive to the authorization signal and the edit records for generating the update request.
31. A system according to claim 30 wherein the authorization engine:

generates an authorization request for communicating to an authorizing device of an authorizing party; and is responsive to a response from the authorizing device of the authorizing party to the authorization request to selectively generate the authorization signal.
32. A system according to claim 31 wherein the authorizing device includes a GUI for: presenting visually to the authorizing party the authorization request; being responsive to predetermined input to the authorizing device by the authorizing party for generating the authorizing signal.
33. A system according to claim 32 wherein the predetermined input is one or more of: a signature;