WO2016024871A1

WO2016024871A1 - A method of associating entities

Info

Publication number: WO2016024871A1
Application number: PCT/NZ2015/050110
Authority: WO
Inventors: Jonathan MIRKIN
Original assignee: Nomos Limited
Priority date: 2014-08-13
Filing date: 2015-08-13
Publication date: 2016-02-18
Also published as: NZ700835A; NZ628759A

Abstract

A method of associating entities by way of a computerised device is provided. The method comprises the steps of: a) providing a computerised database of entities; b) enabling a user of the device to search the database for one of the entities such that the name of that entity displays on a screen of the device in a results panel; c) enabling the user to use the device to select the entity and cause the name to appear at a build panel on the screen for defining the structure of the entity; d) enabling the user to search the database for a second entity and displaying the name thereof in the results panel; and e) enabling the user to select and cause the name of the second entity to appear in the build panel as a member of the first mentioned entity so that such membership is recorded in the database.

Description

TITLE

A Method of Associating Entities.

FIELD OF INVENTION

A preferred form of the invention relates to a method of associating entities, for example for document creation using a computerised device. BACKGROUND

Documents of various types have long been used to manage the affairs of life, including personal and business commitments. Creation of such documents can be a time consuming exercise and it is desirable to be able to simplify the process. It is an object of a preferred form of the invention to go at least some way towards addressing the above issue. While this object applies to the preferred embodiment, it should not be taken as a limit on the scope of the invention as claimed. The object of the invention per se is simply to provide the public with a useful choice. The term "comprising", if and when used in this document, should be interpreted non- exclusively. For example if used in relation to a combination of features it should not be taken as precluding the option of there being further unnamed features.

SUMMARY OF THE INVENTION

According to one aspect of the invention there is provided a method of associating entities by way of a computerised device, comprising the steps of:

a) providing a computerised database of entities;

b) enabling a user of the device to search the database for one of the entities such that the name of that entity displays on a screen of the device in a results panel;

c) enabling the user to use the device to select the entity and cause the

name to appear at a build panel on the screen for defining the structure of the entity;

d) enabling the user to search the database for a second entity and

displaying the name thereof in the results panel; and

e) enabling the user to select and cause the name of the second entity to appear in the build panel as a member of the first mentioned entity so that such membership is recorded in the database.

Optionally steps d) and e) are able to be repeated for one or more further entities so that it/they are each also allocated as a member of the first mentioned entity.

Optionally the entities in the database are selected from the group consisting of at least people, trusts, companies and societies. Optionally entities are able to be transferred to the build panel by dragging and dropping.

Optionally the second entity is a person. Optionally the membership record is used to computer generate a document naming the first entity as a subject of the document and the second entity as an authorising member of the first mentioned entity.

Optionally the second entity is a signatory for the document.

Optionally the first mentioned entity is a contracting party for the document.

Optionally the user is able to enter a new entity into the database by way of the device.

Optionally a database record is kept for the first mentioned entity so that its membership can be amended and, in the event of such change, the amended membership is recorded in the database as the current one. Optionally the results panel displays on-screen with visible boundaries. Optionally the results panel displays on-screen without visible boundaries.

Optionally the build panel displays on-screen with visible boundaries.

Optionally the build panel displays on-screen without visible boundaries Optionally when the second entity is caused to appear in the build panel at item e) it automatically displays there as a type of member dependant on the type of the first mentioned entity. Optionally the document is one of:

a) a contract of a type not mentioned below;

b) a mortgage;

c) a deed;

d) a constitution;

e) a shareholders agreement;

f) an affidavit,

g) a declaration;

h) an affirmation;

i) a lease;

j) a will;

k) a property sale and purchase agreement;

I) an easement;

m) a covenant;

n) a variation;

o) an assignment;

p) a guarantee;

q) a novation;

r) minutes;

s) a resolution;

t) an event timeline; and

u) a form.

Optionally one or more of the panels incorporates one or more sub-panels. According to a further aspect of the invention there is provided a computerised method of managing events, comprising the steps of:

(a) displaying on the screen of a computerised device a number of events

potentially relevant to a transaction in a manner that two or more of the events can be selected by the user;

(b) after a user has selected two or more of the events, the selections being computer processed and displayed onscreen as a time based symbolic hierarchy representing the transaction, each event being recorded against a date by way of software, wherein some of the dates are automatically computer calculated or can be selected and made dependant on at least another of the dates; and

(c) the hierarchy being such that a symbol representing each event can be user selected to display alpha numeric detail particularising the event.

Optionally each symbol is particular to the type of event it represents. DRAWINGS

Some preferred embodiments of the invention will described by way of example and with reference to the accompanying drawings, of which:

Figure 1 is a screen shot from a computer running software for creating a lease document;

Figure 2 is a screen shot illustrating the manner in which an entity can be

loaded into a database controlled by the software;

Figure 3 is a screen shot illustrating how the software can be used to define the structure of an entity; and

Figure 4 is a screen shot illustrating a software controlled timeline of lease events.

DETAILED DESCRIPTION

In one preferred embodiment of the invention a computerised device runs software for creating a document. The device may for example be a desktop computer, a laptop, a tablet or a smartphone. The software may be installed on the device, or the device may simply run it from the cloud.

In the example shown in figure 1 the document is for a lease. It should however be appreciated that the software can be used to create a myriad of alternative documents. The software causes a search panel 1 to appear on screen to enable a human user to search a database of entities. The database of entities is stored in persistent storage. In this regard an entity name is keyed into the search panel 1 and, if the entity searched on is recorded in the database, its name appears in a results panel 2. The user can then click on the results panel 2 and drag a node displaying the name to a build panel 3. The node is then dropped to populate the build panel 3. For example, if the node represents the landlord it is dropped into field 4 of the build panel which designates the landlord. Other fields of the build panel, for example the tenant and guarantor fields 5, 6, can be populated in the same way. In each case the name of the tenant and guarantor is located using the search panel 1 , and a corresponding node dragged and dropped from the results panel 2 to the appropriate part of the build panel 3.

Preferably the search panel 1 works on a filtering basis in that as one keys a name into it, the results panel 2 is automatically populated with entity names corresponding to the text typed. For example if only the text "Smf is typed in, the software causes all names in the database beginning "Smf to be displayed in the results panel 2, in alphabetical order - eg Smith, Smithers, Smithson, etc, etc. As more text is typed into the search panel 1 irrelevant hits are progressively filtered out and consequently not displayed. If the search ends with more than one hit displayed in the results panel, then the user can select the one wanted and drag and drop it into the build panel 3.

If an entity search gives a nil result then the software offers the user a facility to load the entity into the database. This is achieved by way of an on-screen dialogue box 7 as shown in figure 2. In the example shown, the box 7 only prompts for basic details, but in some embodiments it may prompt for more comprehensive information; for example details as to name, nationality, physical address, postal address, email address, phone number, etc. When the new entity is a company, for example, the dialogue box may prompt for its directors to be loaded. However if the directors are already recorded in the database then they can simply be searched and selected. Either way, the software creates an association in the database between the company and the directors. The new entity and any new associations are stored in the database, which is stored in persistent storage.

Figure 3 illustrates the creation of a lease document at a more advanced stage. As can be seen, "Company X' has been entered as the landlord and "The Smith Family Trust as the tenant. When Company X is dropped into the landlord field it immediately and automatically appears with its signatory directors 8 displayed. The display is hierarchical so that the directors 8 are shown as subsets or members of the company. The user does not have to specifically enter the director names 8 because they have already been associated with Company X at the time it was loaded into the database. The association remains, so that wherever the company goes, the directors follow. If a director is removed from the company, for example by dragging the name from the landlord panel and dropping it at a delete panel 9, then the association is broken and this is recorded by the software in the database and stored in persistent storage. Changes to associations are applied 'database wide' so that they only need to be done once.

With further reference to figure 3, The Smith Family Trust displays as the tenant, with its members shown in hierarchical order. The members comprise three trustees 9. One of the trustees is a company and so its directors 10 are shown as members of that company. The tenant is therefore displayed in a tree structure which enables the user to easily see and appreciate the structure of the entity being dealt with.

When all entities of the lease have been entered, the user clicks to cause the software to generate the lease document ready for signing. The software automatically populates the document with the relevant entities recorded in the relevant places (with address details if appropriate), including in signature clauses. This enables a user to more quickly and less painstakingly create the document, ie as opposed to having type in entity names and details each time a new document is created. Once created the document is stored to persistent storage.

A similar process can be followed for creating documents such as wills, in which case the entities may include the testator, the executor and witnesses. In the case of a license agreement, the entities may be the licensor and the licensee, and in the case of a mortgage they may be the mortgagee, the mortgagor and a guarantor. It should be understood that the inventive concept has applicability to a wide variety of documents and that those mentioned above are just examples.

A useful aspect of the invention is that when an entity record is generated for the database the user first selects the type of entity being created. The name of the entity is then dragged and dropped from the results panel to the build panel 3. If for example the user has selected to create a 'company' entity then the software automatically determines that the next entity dragged and dropped into the build panel 3 is a director. The director is accordingly displayed in the build panel as a subset of the company, eg in a family tree format. It is not necessary to select 'director' for the software to know that the second is intended to be a director.

Records for other entity types are generated in the same way. For example in the case of a trust selection, the first name dragged into the build panel 3 is the name of the trust. Subsequent entities dragged into the build panel are automatically allocated and displayed as trustees.

In some embodiments of the invention the software may have facility to connect the user to a third party database, for example to a Register of Companies held by a State run Companies Office, and entity details from there may be searched and displayed for selection into the document as desired.

While the invention has particular application to the creation of documents, in some embodiments it simply provides a convenient way for users to create, record and view in a family tree format a number of membership type associations between entities. For example, such embodiments can facilitate efficient entry of data into a property management database even if there is no document creation facility, or if the facility is available but only used sporadically.

In a further embodiment of the invention the software can be operated by the user to build and display an agreement entered into between entities in terms of events. In building the document, event categories can be selected. On selection, the software causes a clause corresponding to the event to be incorporated in the document. Examples of some lease events are:

• commencement date;

• possession date;

• rent payment dates;

• property inspection dates;

• rent review dates;

• lease renewal dates;

• assignment or transfer of lease rights;

• expiration date;

• etc.

When called upon, the software causes the events to display onscreen in time order, for example with a timeline as shown in figure 4. This provides an easy to appreciate single page overview, with each locus 1 1 of the timeline corresponding to one of the events. If a mouse pointer 12 is hovered over a locus then a descriptor box 13 appears and displays the exact date of the event and just what it is about. Software controlling the timeline uses the date of at least some of the events to calculate the date relevant to others of the events, and this is recorded for each event. For example 'rent due' dates will depend on the commencement date for lease, as will rent reviews. Inspection dates may be calculated dependent on when the last inspection occurred, etc. Documents relevant to some of the events, eg lease deeds of renewal, may be generated by the software and associated with the relevant locus.

Each event type may be associated with a particular colour and each locus rendered in that colour, such that a user can easily appreciate the nature of each event in the timeline.

When a locus is specifically selected (eg clicked on), the particulars for the event display onscreen. For a past event the particulars may indicate exactly what happened, for example that a rent payment totalling such and such dollars was received, or that a payment was missed, etc. The software thus provides a user with an ability to easily view a complete history of the lease arrangement, including the conduct of the parties.

Copies of documents associated with an event may be viewed on-screen by selecting them once the event itself has been chosen. For example a pdf of the lease document may be obtained via a locus relating to a 'commencement of lease' event, and a pdf of a renewal document obtained via a 'lease renewal' locus, etc. Loci for upcoming lease renewals may also be associated with user selectable documents for signing by the landlord and tenant. Documents are therefore preferably saved against the relevant locus as opposed to a general documents folder.

The software enables other document types to be generated, particularised and displayed in similar fashion. The exact mechanics will of course be modified to suit the document, but the same principle applies.

In some embodiments of the invention the timeline aspect may omit the document creation aspect and simply provide a convenient on-screen one-line display of the historical, future, missed and/or overdue steps to a transaction or a legal relationship generally. Changes or updates are entered into the underlying database of information and the software uses these to modify or update the timeline as appropriate. In some embodiments, old timelines may be called up from a data record to show how they were at a selected date or dates, prior to changes or updates. And in some embodiments a user has a facility to filter events, or in other words to select for viewing at a particular time only the sort of events the user is interested in.

While some preferred aspects of the invention have been described by way of example it should be appreciated that modifications and improvements can occur without departing from the scope of the invention.

Claims

A method of associating entities by way of a computerised device, comprising the steps of:

a) providing a computerised database of entities;

c) enabling the user to use the device to select the entity and cause the name to appear at a build panel on the screen for defining the structure of the entity;

d) enabling the user to search the database for a second entity and

displaying the name thereof in the results panel; and

2. A method according to claim 1 , wherein steps d) and e) are able to be repeated for one or more further entities so that it/they are each also allocated as a member of the first mentioned entity.

3. A method according to claim 1 or 2, wherein the entities in the database are selected from the group consisting of at least people, trusts, companies and societies.

4. A method according to claim 1 , 2 or 3, wherein entities are able to be transferred to the build panel by dragging and dropping.

5. A method according to any one of the preceding claims, wherein the second entity is a person.

6. A method according to any one of the preceding claims, comprising the step of using the membership record to computer generate a document naming the first entity as a subject of the document and the second entity as an authorising member of the first mentioned entity.

7. A method according to claim 6, wherein the second entity is a signatory for the document.

8. A method according to claim 6 or 7, wherein the first mentioned entity is a contracting party for the document.

A method according to any one of the preceding claims, wherein the user is able to enter a new entity into the database by way of the device.

10. A method according to any one of the preceding claims, wherein a database record is kept for the first mentioned entity so that its membership can be amended and, in the event of such change, the amended membership is recorded in the database as the current one.

11. A method according to any one of the preceding claims, wherein the results panel displays on-screen with visible boundaries.

12. A method according to any one of claims 1-10, wherein the results panel displays onscreen without visible boundaries.

13. A method according to any one of the preceding claims, wherein the build panel displays onscreen with visible boundaries.

14. A method according to any one of claims 1-12, wherein the build panel displays onscreen without visible boundaries 15. A method according to any one of the preceding claims, wherein when the

second entity is caused to appear in the build panel at item e) it automatically displays there as a type of member dependant on the type of the first mentioned entity.

16. A method according to claim 6, 7 or 8, or any one of claims 9-14 when read back on claim 6 directly or indirectly, wherein the document is one of:

a) a contract of a type not mentioned below;

b) a mortgage;

c) a deed;

d) a constitution;

e) a shareholders agreement;

f) an affidavit, g) a declaration;

h) an affirmation;

i) a lease;

j) a will;

k) a property sale and purchase agreement;

I) an easement;

m) a covenant;

n) a variation;

o) an assignment;

p) a guarantee;

q) a novation;

r) minutes;

s) a resolution;

t) an event timeline; and

u) a form.

17. A method according to any one of the preceding claims, wherein one or more of the panels incorporates one or more sub-panels.

18. A method according to claim 1 , substantially as herein described.

19. A method substantially as herein described with reference to the accompanying drawings.

20. A computerised method of managing events, comprising the steps of:

(a) displaying on the screen of a computerised device a number of events potentially relevant to a transaction in a manner that two or more of the events can be selected by the user;

(c) the hierarchy being such that a symbol representing each event can be user selected to display alpha numeric detail particularising the event. A computerised method of managing events according to claim 1 , wherein each symbol is particular to the type of event it represents.