AU2017100189A4 - Data management method and system - Google Patents

Abstract

DATA MANAGEMENT METHOD AND SYSTEM Abstract Disclosed herein are an online method and system for managing asset data. The method comprises the steps of: storing in an asset data management system a customer profile for a registered customer, said customer profile including a set of attributes pertaining to an asset owned by said registered customer; uploading asset information to said asset data management system, via a communications network coupled to said asset data management system; and sending a notification to said registered customer in advance of a deadline associated with said vehicle, based on at least one of said attributes or said asset information. - 2/22 CD* 0OC) z a,. CC,, 0 -a* 40 - 0 C\J c,'Jj co' Caaj Cc~c' ( 31 C) C'\J 0) C,'j PSN P002AU Dspecf cation drawings. vsd

Description

2017100189 17 Feb 2017

AUSTRALIA

Patents Act 1990

Innovation Patent Specification

Title: DATA MANAGEMENT METHOD AND SYSTEM

Applicant(s): Cardia Patterson Inventor(s): Cardia Patterson Agent: ©COTTERS Patent & Trade Mark Attorneys The following is a full description of the invention which sets forth the best method known to the applicant of performing it. PSNP002AUD1 - specification.docx 2 2017100189 17 Feb 2017

DATA MANAGEMENT METHOD AND SYSTEM

Related Application [0001] The present application is related to Australian Innovation Patent No. 2016100766 filed 26 May 2016, the entire content of which is incorporated by reference as if fully set forth herein.

Technical Field [0002] The present disclosure relates to a data management method and system. In particular, the present disclosure relates to a data management method and system for storing data relating to an asset.

Background [0003] In the modern world, there is often a need to record and retain information relating to various assets. Such information may include, for example, purchase receipts, warranty registrations, service history records and the like. For valuable assets, such as automobiles, boats, and houses, insurance and registration details may need to be not only recorded, but maintained through period renewal procedures. Such renewal procedures may simply involve payment of a fee by a specified due date. In more complex scenarios, such as in relation to automobiles over a certain age in some jurisdictions, it may be necessary to perform a periodic inspection or audit of the asset in order to maintain registration of the automobile.

[0004] Automobiles and real estate are generally the most expensive assets owned by consumers. Most jurisdictions require automobiles to be registered and insured, with annual renewal fees commonplace. Similarly, real estate is often subject to local government rates and taxes, which must be paid periodically in a timely manner.

[0005] It is becoming increasingly difficult to maintain accurate records in relation to multiple assets. As assets are acquired, transferred, lost, retired, sold, and disposed of, it is easy for an owner to lose or misplace all of the relevant information pertaining to each asset. For common consumer items, such as whitegoods and the like, misplacing a purchase receipt or warranty registration card may result in the owner being unable to obtain a replacement or repair for a faulty appliance. Flowever, failure to maintain registration and insurance of an automobile or boat may result in penalty or fine, PSNP002AUD1 specification.docx 3 2017100189 17 Feb 2017 including loss of licence, along with invalidation of any insurance policy associated with the asset.

[0006] For more valuable assets, such as cars and real estate, it is not uncommon for people to forget their finance provider and their insurance provider, particularly as those service providers may change during ownership of the respective asset.

[0007] In looking to maintain an asset, it is often difficult to identify a suitable service provider, such as a mechanic or spare parts supplier. Further, customers are not always able to identify sources of promotions or deals that might be relevant to their assets.

[0008] Thus, a need exists to provide an improved method and system for managing data relating to one or more assets owned by a user.

Summary [0009] The present disclosure relates to an asset data management method and system. The asset data management system provides a central repository for storing information pertaining to a set of assets owned by a user.

[0010] A first aspect of the present disclosure provides an online method for managing asset data, comprising the steps of: storing in an asset data management system a customer profile for a registered customer, said customer profile including a set of attributes pertaining to an asset owned by said registered customer; uploading asset information to said asset data management system, via a communications network coupled to said asset data management system; and sending a notification to said registered customer in advance of a deadline associated with said vehicle, based on at least one of said attributes or said asset information.

[0011] A second aspect of the present disclosure provides an asset data management system comprising: a server coupled to a communications network, said server including: a template database for storing user interface templates for display to a screen of a user computing device; a customer database for storing a customer profile associated with a registered user of said asset data management system, said customer profile including asset information relating to an asset owned by the registered user; PSNP002AUD1 - spedfication.de 4 2017100189 17 Feb 2017 a notifications module configured to send notifications to said registered users, based on said asset information; and a user computing device coupled to said server via a communications network, said user computing device executing a software application to perform the steps of: uploading asset information to said customer database, said asset information selected from the group consisting of contracts, receipts, photos, and documents; and receiving user input from said registered user accessing said user computing device; wherein said notifications module transmits a notification to said user computing device in advance of a deadline associated with said asset, based on said asset information.

[0012] According to another aspect, the present disclosure provides an apparatus for implementing any one of the aforementioned methods.

[0013] According to another aspect, the present disclosure provides a computer program product including a computer readable medium having recorded thereon a computer program for implementing any one of the methods described above.

[0014] Other aspects of the present disclosure are also provided.

Brief Description of the Drawings [0015] One or more embodiments of the present disclosure will now be described by way of specific example(s) with reference to the accompanying drawings, in which: [0016] Fig. 1 is a flow diagram of an asset data management method in accordance with the present disclosure; [0017] Fig. 2 is a schematic representation of a system on which one or more embodiments of the present disclosure may be practised; [0018] Fig. 3 is a schematic block diagram representation of a system that includes a general purpose computer on which one or more embodiments of the present disclosure may be practised; [0019] Fig. 4 is a schematic block diagram representation of a system that includes a general smartphone on which one or more embodiments of the present disclosure may be practised; PSNP002AUD1 - specification.docx 5 2017100189 17 Feb 2017 [0020] [0021] [0022] [0023] [0024] [0025] [0026] [0027] [0028] [0029] [0030] [0031] [0032] [0033] [0034] [0035] [0036] [0037]

Fig. 5 is a screenshot of a home page for an imotor app;

Fig. 6 is a screenshot of a secondary page of the imotor app;

Fig. 7 is a screenshot of a page within the imotor app;

Fig. 8 is a screenshot showing an alternative version of the page of Fig. 7; Fig. 9 is a screenshot of a Car Contract page within the imotor app;

Fig. 10 is a screenshot of a Registration page within the imotor app;

Fig. 11 is a screenshot of a Car Insurance page within the imotor app;

Fig. 12 is a screenshot of a CTP Registration page within the imotor app;

Fig. 13 is a screenshot of a Service page within the imotor app;

Fig. 14 is a screenshot of a Finance page within the imotor app;

Fig. 15 is a screenshot of a Finance interface within the imotor app;

Fig. 16 is a screenshot of a Loan page within the imotor app;

Fig. 17 is a screenshot of a Roadside page within the imotor app;

Fig. 18 is a screenshot of a Tolls & Fines page within the imotor app;

Fig. 19 is a screenshot of a Warranty page within the imotor app;

Fig. 20 is a screenshot of an imotor Helper page within the imotor app; Fig. 21 is a screenshot of a What's New page within the imotor app; and Fig. 22 is a screenshot of an Add Offer page within the imotor app.

Detailed Description [0038] Method steps or features in the accompanying drawings that have the same reference numerals are to be considered to have the same function(s) or operation(s), unless the contrary intention is expressed or implied.

Overview [0039] The present disclosure provides an asset data management method and system. The asset data management system provides a central repository for storing information pertaining to a set of assets owned by a user. Throughout this specification, examples of the asset data management system will be provided relating to automobiles. However it will be appreciated that the asset data management system may be used in relation to PSNP002AUD1 - specification.docx 6 2017100189 17 Feb 2017 any type of asset, including, for example, but not limited to, automobiles (including cars, trucks, motorcycles, and the like), boats, real estate, jewellery, and the like.

[0040] In one arrangement, an asset data management system is implemented using a server coupled to a communications network. A user is able to communicate with the server via a computing device coupled to the communications network. In one implementation, the server is associated with a software application ("app") executing on the computing device accessed by the user. For example, the app may be executing on a smartphone using the iOS operating system by Apple Inc. or the Android operating system by Google Inc. In another implementation, the server is associated with a website that the user can access via a browser executing on the computing device.

[0041] The user is able to upload originals or copies of receipts, contracts, photos, and important details relating to the asset to the server. In one arrangement, the server monitors deadlines relating to the asset, such as registration and insurance renewals.

[0042] In one arrangement, the server includes a payment portal through which the user can effect payment of fees and charges relating to the asset, such as the aforementioned registration and insurance renewals, as well as service fees, tolls, finance, infringements, and the like.

[0043] In another arrangement, the server includes a trading portal, which facilitates transactions between registered customers and registered service providers. Such a trading portal enables a customer to buy, sell, or trade personal assets, such as vehicles and car parts, as well as providing a forum through which service providers may advertise items for sale and/or promotional offers.

[0044] One instance of an asset data management system in accordance with the present disclosure relates to motor vehicles and is referred to herein as "imotor". imotor makes the consumer experience of owning a vehicle exciting and effortless, imotor assists the customer with all the tedious chores of owning an automotive. In one implementation, imotor includes utility essentials for registration, insurance reminder payments, reminders for payment functions and monthly payment plans for those customers who like to budget.

[0045] imotor is a platform that is configured to assist owners with all aspects and phases of vehicle ownership, from small needs, such as a car repair, to a customer PSNP002AUD1 - specification.docx 7 2017100189 17 Feb 2017 wanting to replace their car for a new ride, and all-round service with automotive service providers, including all of the big auto brands.

[0046] In one implementation, imotor includes a "Best Deal!" retailing service; including new, demonstrator and used cars, through to genuine manufacturers of parts & accessories, servicing, finance and insurance, registration renewals, roadside, shopping and auto parts.

[0047] In one implementation, imotor asks consumers to click and refer to the picture of their car contract that is already loaded in their inbox screen, such as through being displayed within an app on a display screen of a computing device accessed by the consumer. Forwarding this picture contract allows the imotor platform to value their car, based on stored values of comparable vehicles or an external database, find better insurance or finance package or even upgrade a deal for the customer.

[0048] In one implementation, imotor provides assistance with everyday servicing issues - from windscreens repairs, tyres, wheel alignments, batteries and brake tests and through to road worthy certificates (Safety Certificates), by facilitating contact between customers (e.g., car owners) and service providers.

[0049] The imotor platform saves time and reduces customer liabilities that might otherwise arise from forgetting to pay registration, insurance, tolls, infringement penalties, and the like, imotor also assists customers to find a car, car parts, insurance, and finance, imotor also assists customers with insurance claims, including storing photos, details, and documentary evidence relating to such claims.

[0050] The imotor platform provides a user with a platform that can schedule and manage timely future appointment bookings, such as car services and registration inspections, payment and receipt functionality, and reminders for forthcoming deadlines.

Description of Embodiments [0051] Fig. 2 is a schematic block diagram representation of an administration system 200 in accordance with the present disclosure. The administration system 200 includes an asset management data management system 201 coupled to a communications network 205. The communication network 205 may be implemented using a dedicated communications link, a local area network (LAN), a wide area network (WAN), the Internet, a telecommunications network, or any combination thereof. ion.docx PSNP002AUD1 8 2017100189 17 Feb 2017 [0052] The asset data management system 201 is presented as a single functional component. However, it will be appreciated that the asset data management system 201 may be implemented using one or more computing devices co-located in a single premises or distributed across a networked computing environment. In particular, the asset data management system may be implemented using one or more computing devices.

[0053] The administration system 200 also includes a user computing device 210 coupled to the communications network 205 and accessible by a user 202 in order to interact with the asset data management system 201. The user computing device 210 may be implemented using any suitable device, including, but not limited to, a personal computer, laptop, notebook, smartphone, tablet computing device, phablet computing device, or the like. In the example of Fig. 2, the user computing device 210 is coupled to a printer 215, a camera 235, and a user database 225. It will be appreciated that one or more such devices may be incorporated into the computing device itself, such as a smartphone with an integrated camera.

[0054] The administration system 200 also includes a set of service providers 280, 290 coupled to the asset data management system 201 via the communications network 205. Such service providers may include, for example, insurance companies, insurance brokers, government registration authorities, such as the NSW Roads and Maritime Services, car dealers, boat dealers, real estate agents, automobile repair shops, automobile spare parts shops, and the like.

[0055] In the example of Fig. 2, the asset data management system 201 is implemented using a server 240 coupled to a database 270. The database 270 may be internal or external to the server 240 and may be used to store historical records, transaction records, archived records, and the like. The database 270 may also represent online commercial databases, such as those maintained by automobile manufacturers, government agencies, insurance companies, and the like. The server 240 includes a plurality of modules for performing the functionality of the asset data management system 201. In the example of Fig. 2, the server 240 includes a template database 242 for storing a set of user interface templates for display to the user computing device 210 accessed by the user 202. Such templates may be uploaded from the asset data management system to the user computing device when the user 202 installs an asset data management app on the user computing device 210. Alternatively, the server 240 PSNP002AUD1 - specification.docx 9 2017100189 17 Feb 2017 serves the templates when presenting a graphical user interface to a browser executing on a processor of the user computing device 210.

[0056] The server 240 also includes a customer database 244 for storing information about each customer registered with the asset data management system 201. In one arrangement, the customer database 244 stores a user profile for each such registered user. The user profile includes a set of attributes pertaining to the user and one or more assets associated with the user. In one example, the attributes include user name, user contact details, username, and user password. When the asset data management system is applied to automobiles, the attributes may include, for example, but are not limited to, vehicle make, vehicle model, vehicle build date, vehicle registration, receipts, vehicle insurance, vehicle finance, and the like.

[0057] The asset data management system 240 also includes a service provider database 246, which stores a service provider profile for each service provider 280, 290 registered with the asset data management system 240. Each service provider profile includes a set of service provider attributes, such as service provider contact details, service provider registration details, and the like.

[0058] The asset data management system 240 also includes a notifications module 248, which functions as a scheduling calendar, and an accounts module 205. The template database 242, the customer database 244, the service provider database 246, the notifications module 248, and the accounts module 250 exchange information via a bus 252. The accounts module 250 monitors payments made by the customer 202 and the service providers 280, 290 registered with the system 201. In one implementation, the accounts module 250 acts as a payment gateway to facilitate secure electronic payments by the customer 202 to the service providers 280, 290. Such an electronic payment gateway enables the customer 202 to access the asset data management system 201 to monitor asset information and also make payments in a single place.

Thus, the asset data management system 201 provides a "one-stop" shop for asset management.

[0059] In one arrangement, the asset data management system 240 provides approved service providers 280, 290 with limited access to data from the customer database 244 to assist the service providers 280, 290 to provide high levels of customer service to existing customers and the opportunity to retain and/or attract customers through promotions, reminders, event information, and specials. PSNP002AUD1 - specificatjon.docx 10 2017100189 17 Feb 2017 [0060] The notifications module 248 receives information from the customer database 244 and the service provider database 246 and creates a calendar of forthcoming deadlines. Based on a predefined schedule, the notifications module 248 sends reminder messages to the user 202 regarding forthcoming deadlines pertaining to the assets associated with the user 202 and recorded in the customer database 244.

Such reminder messages may be sent via email, short message service (SMS) text message to the user, instant message within the app executing on the computing device 210, dashboard message appearing on an interface of the app executing on the user computing device 210 or viewable in a browser executing on the user computing device 210, or any combination thereof.

[0061] Fig. 1 is a flow diagram of a method 100 illustrating a simple embodiment of an asset data management system. The method 100 begins at a Start step 105 and proceeds to step 110, at which customer, such as the user 202 of Fig. 2, uses the user computing device 210 to access and register with an online asset data management system, such as the asset data management system 201.

[0062] In a following step 110, the customer 202 uploads data relating to an asset owned by the customer 202. In one example, the asset is a car and the data includes registration details, insurance details, and service history. The customer 202 is also able to upload any receipts, contracts, and other documentation relating to the car. Such receipts may include, for example, but are not limited to, purchase receipt for the car, contract with the car dealership from which the car was purchased, insurance disclosure statement, insurance contract, warranty details, receipts relating to tyres, consumables, services, and the like, registration certificate, fuel receipts, and the like. The uploaded data may be electronic receipts issued by a service provider, scanned receipts or documents, photos of documents, data entered into a user interface of the system 201, or any other electronic means of uploading data.

[0063] Control passes from step 115 to step 120, in which the asset data management system 201 dockets deadlines relating to the asset, using the notifications module 248.

In one implementation, the customer 202 enters the deadlines manually, through a graphical user interface displayed on the computing device being accessed by the user.

In another implementation, a processor (not shown) of the server 240 retrieves information from the customer database 244 and/or the service provider database 246 to determine the deadlines. For example, a car registration may be payable annually, in PSNP002AUD1 - specificatjon.docx 11 2017100189 17 Feb 2017 which case the processor determines the next registration payment deadline based on an entered or scanned registration certificate relating to the car.

[0064] Returning to Fig. 1, control passes from step 120 to step 125, in which one or more service providers 280, 290 register with the asset data management system 201.

In one example, an automobile service centre 280 provides information relating to a service conducted on the car and sends a service appointment to the asset data management system 201 to be stored by the asset data management system in relation to the customer's car.

[0065] In a next step 130, the customer 202 or one of the service providers 280, 290 performs an action in relation to an asset and uploads information to the asset data management system 201 via the communications network 205. The asset data management system 201 updates one or more of the customer database 244, and the service provider database 246. In step 135, the asset data management system 201 updates the notifications module 248. In step 140, the asset data management system 201 sends a notification originating from the notification module 248 to the customer 202, either to inform the user of a change of status relating to their asset, such as their car has been serviced, or to alert the customer 202 that a deadline is approaching for an action in relation to the asset, such as a scheduled service, payment of registration or insurance. In one implementation, the asset data management system 201 takes the customer 202 to an external URL Link page outside the app to make the requisite payment or provide the necessary details. In an alternative implementation, the accounts module 250 of the system 201 provides a payment portal that establishes a link to the external URL of the entity to which the payment is to be made or arranges an electronic funds transfer to that entity. The method then returns to step 130 and loops.

[0066] The asset data management system of the present disclosure may be practised using a computing device, such as a general purpose computer or computer server.

Fig. 3 is a schematic block diagram of a system 300 that includes a general purpose computer 310. The general purpose computer 310 includes a plurality of components, including: a processor 312, a memory 314, a storage medium 316, input/output (I/O) interfaces 320, and input/output (I/O) ports 322. Components of the general purpose computer 310 generally communicate using one or more buses 348.

[0067] The memory 314 may be implemented using Random Access Memory (RAM), Read Only Memory (ROM), or a combination thereof. The storage medium 316 may be PSNP002AUD1 - specification.docx 12 2017100189 17 Feb 2017 implemented as one or more of a hard disk drive, a solid state "flash" drive, an optical disk drive, or other storage means. The storage medium 316 may be utilised to store one or more computer programs, including an operating system, software applications, and data. In one mode of operation, instructions from one or more computer programs stored in the storage medium 316 are loaded into the memory 314 via the bus 348. Instructions loaded into the memory 314 are then made available via the bus 348 or other means for execution by the processor 312 to implement a mode of operation in accordance with the executed instructions.

[0068] One or more peripheral devices may be coupled to the general purpose computer 310 via the I/O ports 322. In the example of Fig. 3, the general purpose computer 310 is coupled to each of a speaker 324, a camera 326, a display device 330, an input device 332, a printer 334, and an external storage medium 336. The speaker 324 may be implemented using one or more speakers, such as in a stereo or surround sound system. In the example in which the general purpose computer 310 is utilised to implement the customer computing device 210, one or more peripheral devices may relate to the printer 215, camera 235, or database 225 connected to the I/O ports 322. In the example in which the general purpose computer 310 is used to implement the server 240, one or more peripheral devices may relate to the external database 270.

[0069] The camera 326 may be a webcam, or other still or video digital camera, and may download and upload information to and from the general purpose computer 310 via the I/O ports 322, dependent upon the particular implementation. For example, images recorded by the camera 326 may be uploaded to the storage medium 316 of the general purpose computer 310. Similarly, images stored on the storage medium 316 may be downloaded to a memory or storage medium of the camera 326. The camera 326 may include a lens system, a sensor unit, and a recording medium.

[0070] The display device 330 may be a computer monitor, such as a cathode ray tube screen, plasma screen, or liquid crystal display (LCD) screen. The display 330 may receive information from the computer 310 in a conventional manner, wherein the information is presented on the display device 330 for viewing by a user. The display device 330 may optionally be implemented using a touch screen to enable a user to provide input to the general purpose computer 310. The touch screen may be, for example, a capacitive touch screen, a resistive touchscreen, a surface acoustic wave touchscreen, or the like. PSNP002AUD1 - spedfication.de 13 2017100189 17 Feb 2017 [0071] The input device 332 may be a keyboard, a mouse, a stylus, drawing tablet, or any combination thereof, for receiving input from a user. The external storage medium 336 may include an external hard disk drive (HDD), an optical drive, a floppy disk drive, a flash drive, solid state drive (SSD), or any combination thereof and may be implemented as a single instance or multiple instances of any one or more of those devices. For example, the external storage medium 336 may be implemented as an array of hard disk drives.

[0072] The I/O interfaces 320 facilitate the exchange of information between the general purpose computing device 310 and other computing devices. The I/O interfaces may be implemented using an internal or external modem, an Ethernet connection, or the like, to enable coupling to a transmission medium. In the example of Fig. 3, the I/O interfaces 322 are coupled to a communications network 338 and directly to a computing device 342. The computing device 342 is shown as a personal computer, but may be equally be practised using a smartphone, laptop, or a tablet device. Direct communication between the general purpose computer 310 and the computing device 342 may be implemented using a wireless or wired transmission link.

[0073] The communications network 338 may be implemented using one or more wired or wireless transmission links and may include, for example, a dedicated communications link, a local area network (LAN), a wide area network (WAN), the Internet, a telecommunications network, or any combination thereof. A telecommunications network may include, but is not limited to, a telephony network, such as a Public Switch Telephony Network (PSTN), a mobile telephone cellular network, a short message service (SMS) network, or any combination thereof. The general purpose computer 310 is able to communicate via the communications network 338 to other computing devices connected to the communications network 338, such as the mobile telephone handset 344, the touchscreen smartphone 346, the personal computer 340, and the computing device 342.

[0074] One or more instances of the general purpose computer 310 may be utilised to implement a server acting as a central repository and processor to implement an asset data management system in accordance with the present disclosure. In such an embodiment, the memory 314 and storage 316 are utilised to store data relating to customers, assets, scheduled appointments and payment deadlines, and service providers. Software for implementing the asset data management system is stored in one or both of the memory 314 and storage 316 for execution on the processor 312. The

PSNP002AL 14 2017100189 17 Feb 2017 software includes computer program code for implementing method steps in accordance with the method of asset data management described herein.

[0075] Fig. 4 is a schematic block diagram of a system 400 on which one or more aspects of an asset data management method and system of the present disclosure may be practised. The system 400 includes a portable computing device in the form of a smartphone 410, which may be used by a registered user of the asset data management system 201 in Fig. 2, such as the customer 202. The smartphone 410 includes a plurality of components, including: a processor 412, a memory 414, a storage medium 416, a battery 418, an antenna 420, a radio frequency (RF) transmitter and receiver 422, a subscriber identity module (SIM) card 424, a speaker 426, an input device 428, a camera 430, a display 432, and a wireless transmitter and receiver 434. Components of the smartphone 410 generally communicate using one or more bus connections 448 or other connections therebetween. The smartphone 410 also includes a wired connection 445 for coupling to a power outlet to recharge the battery 418 or for connection to a computing device, such as the general purpose computer 310 of Fig. 3. The wired connection 445 may include one or more connectors and may be adapted to enable uploading and downloading of content from and to the memory 414 and SIM card 424.

[0076] The smartphone 410 may include many other functional components, such as an audio digital-to-analogue and analogue-to-digital converter and an amplifier, but those components are omitted for the purpose of clarity. However, such components would be readily known and understood by a person skilled in the relevant art.

[0077] The memory 414 may include Random Access Memory (RAM), Read Only Memory (ROM), or a combination thereof. The storage medium 416 may be implemented as one or more of a solid state "flash" drive, a removable storage medium, such as a Secure Digital (SD) or microSD card, or other storage means. The storage medium 416 may be utilised to store one or more computer programs, including an operating system, software applications, and data. In one mode of operation, instructions from one or more computer programs stored in the storage medium 416 are loaded into the memory 414 via the bus 448. Instructions loaded into the memory 414 are then made available via the bus 448 or other means for execution by the processor 412 to implement a mode of operation in accordance with the executed instructions. PSNP002AUD1 - specificatjon.docx 15 2017100189 17 Feb 2017 [0078] The smartphone 410 also includes an application programming interface (API) module 436, which enables programmers to write software applications to execute on the processor 412. Such applications include a plurality of instructions that may be pre-installed in the memory 414 or downloaded to the memory 414 from an external source, via the RF transmitter and receiver 422 operating in association with the antenna 420 or via the wired connection 445.

[0079] The smartphone 410 further includes a Global Positioning System (GPS) location module 438. The GPS location module 438 is used to determine a geographical position of the smartphone 410, based on GPS satellites, cellular telephone tower triangulation, or a combination thereof. The determined geographical position may then be made available to one or more programs or applications running on the processor 412.

[0080] The wireless transmitter and receiver 434 may be utilised to communicate wirelessly with external peripheral devices via Bluetooth, infrared, or other wireless protocol. In the example of Fig. 4, the smartphone 410 is coupled to each of a printer 440, an external storage medium 444, and a computing device 442. The computing device 442 may be implemented, for example, using the general purpose computer 310 of Fig. 3.

[0081] The camera 426 may include one or more still or video digital cameras adapted to capture and record to the memory 414 or the SIM card 424 still images or video images, or a combination thereof. The camera 426 may include a lens system, a sensor unit, and a recording medium. A user of the smartphone 410 may upload the recorded images to another computer device or peripheral device using the wireless transmitter and receiver 434, the RF transmitter and receiver 422, or the wired connection 445.

[0082] In one example, the display device 432 is implemented using a liquid crystal display (LCD) screen. The display 432 is used to display content to a user of the smartphone 410. The display 432 may optionally be implemented using a touch screen, such as a capacitive touch screen or resistive touchscreen, to enable a user to provide input to the smartphone 410.

[0083] The input device 428 may be a keyboard, a stylus, or microphone, for example, for receiving input from a user. In the case in which the input device 428 is a keyboard, the keyboard may be implemented as an arrangement of physical keys located on the smartphone 610. Alternatively, the keyboard may be a virtual keyboard displayed on the display device 432. PSNP002AUD1 - specification.docx 16 2017100189 17 Feb 2017 [0084] The SIM card 424 is utilised to store an International Mobile Subscriber Identity (IMSI) and a related key used to identify and authenticate the user on a cellular network to which the user has subscribed. The SIM card 424 is generally a removable card that can be used interchangeably on different smartphone or cellular telephone devices. The SIM card 424 can be used to store contacts associated with the user, including names and telephone numbers. The SIM card 424 can also provide storage for pictures and videos. Alternatively, contacts can be stored on the memory 414.

[0085] The RF transmitter and receiver 422, in association with the antenna 420, enable the exchange of information between the smartphone 410 and other computing devices via a communications network 490. In the example of Fig. 4, RF transmitter and receiver 422 enable the smartphone 410 to communicate via the communications network 490 with a cellular telephone handset 450, a smartphone or tablet device 452, a computing device 454 and the computing device 442. The computing devices 454 and 442 are shown as personal computers, but each may be equally be practised using a smartphone, laptop, or a tablet device.

[0086] The communications network 490 may be implemented using one or more wired or wireless transmission links and may include, for example, a cellular telephony network, a dedicated communications link, a local area network (LAN), a wide area network (WAN), the Internet, a telecommunications network, or any combination thereof. A telecommunications network may include, but is not limited to, a telephony network, such as a Public Switch Telephony Network (PSTN), a cellular (mobile) telephone cellular network, a short message service (SMS) network, or any combination thereof.

[0087] Figs 5 to 22 are screenshots depicting example screenshots displayed on a display device of the computing device 210 and illustrating various functionality of an asset data management system "IMotor" in accordance with the present disclosure. The IMotor implementation is presented in the context of motor vehicles, but it will be readily apparent to those skilled in the art that the functionality may be readily applied to other assets, such as real estate, boats, jet skis, jewellery, and the like.

[0088] The imotor app stores records of receipts and contracts pertaining to motor vehicle ownership, while protecting the customer from forgetting very important vehicle utilities that need regular attention.

[0089] The imotor app has a set of functions, wherein each function relates to one or more utilities that are required when owning an automobile. In one implementation, the PSNP002AUD1 - specification.docx 17 2017100189 17 Feb 2017 imotor app includes a set of 11 functions, each accessible via a corresponding button on a home page. The functions are associated with one or more timers or calendar entries that alert people of upcoming expiring dates and payments needed to renew certain car reg istration/i nsura nces/fina nee payments.

[0090] Fig. 5 is a screenshot of a home page 500 for the imotor app. The home page 500 includes a single button by which the customer 202 can access the app. While the example of Figs 5 to 22 depicts the imotor asset data management system as being implemented as an app executing on a smartphone, the system may equally be practised as a web-based system with the user interface presented via browser pages.

[0091] Fig. 6 is a screenshot of a secondary page 600 showing contact details in an upper region, including icons to call the imotor administration, visit an associated imotor website, or send feedback. A lower region depicts icons relating to a Main menu, New Sales, Pre-Owned Sales, Parts, Collision Centre, and Contact Us.

[0092] Fig. 7 is a screenshot of a page 700 presented to a customer 202 that has logged in to the imotor app and presents the customer 202 with a range of functions. An upper set of icons relates to: User Profile, Change Password, and Logout. A lower set of icons provides the customer 202 with access to the following functions: • Car Contract; • Registration; • Insurance; • CTP (Compulsory Third Party) Insurance; • Finance; • Service; • Roadside Assistance; • Tolls & Fines; and • Warranty.

[0093] Fig. 8 is a screenshot 800 showing an alternative version of the page 700 of Fig. 7.

Car Contract [0094] The Car Contract function enables the customer 202 to upload details relating to a car owned by the customer 202, such as contracts, vehicle identifiers, and fuel receipts. The details may be uploaded in the form of a photo of a vehicle contract, a screenshot of PSNP002AUD1 - specification.doex 18 2017100189 17 Feb 2017 an electronic contract document, or the like. Alternatively, or in addition thereto, the customer 202 may enter relevant vehicle details to be stored in the customer database 264. Such vehicle details may include, for example: • Vehicle Identification Number (VIN); • engine details; • year details; • maker details; • model details; and • receipt details.

[0095] Fig. 9 is a screenshot of a Car Contract page 900, whereby the customer 202 has entered a VIN of WBSKG92050E423206, a vehicle year of 2010, a maker of BMW, and a model of M3. The Car Contract page 900 also provides functionality to upload contracts and receipts.

Registration [0096] Fig. 10 is a screenshot of a Registration page 1000, which provides functionality to enable the customer 202 to pay registration, generate reminders, and upload registration details. In the example of Fig. 10, on the Registration page 1000 the customer 202 has entered details relating to NSW RTA Registration, a payment URL of "http://www.service.nsw.gov.au7se..", a phone number of 132213, a registration number of DDG07J, a registration expiry date of 7 July 2017, and an amount due for registration of $900. These fields can be pre-filled using information stored in the customer database 244, template database 242, and/or obtained from relevant registration authorities. The customer 202 is also able to store receipts in relation to registration payments and certificates.

[0097] In one implementation, the Registration page 1000 provides a payment function that facilitates direct payment to a registration service provider, such as the NSW RTA Registration. In one implementation, imotor is configured to operate nationally throughout Australia, but provides state-specific contextual data. The contextual data may be based on information provided by the user, such as residential address or registration company/authority. Alternatively, the contextual data may be based on geolocation information derived from the computing device 210. The records of registration payment can then be stored in the customer database 244. PSNP002AUD1 - specificatjon.docx 19 2017100189 17 Feb 2017

Car Insurance [0098] Fig. 11 is a screenshot of a Car Insurance page 1100. The Car Insurance page 1100 includes information relating to car insurance, including a policy number, expiry date, amount due, insurance company, payment URL, and phone number. The Car Insurance page 1100 also provides functionality to upload insurance details into the customer database 244, including photos relating to a claim, such as may occur in relation to an accident. The Car Insurance page 1100 also provides functionality to enable the customer 202 to pay the insurance policy or shop around for a new insurance policy. If the customer 202 presses the button to shop around for a new insurance policy, the system 201 uses information derived from the service providers 280, 290 to provide insurance policy information to the customer 202.

[0099] In one implementation, the Car Insurance page 1100 includes functionality to send future reminders originating from the notifications module 248 to the customer 202 and to schedule a booking for a required service or inspection. In one implementation, the Car Insurance page 1100 provides a comparison table for a set of car insurance service providers, so that the customer 202 can readily compare benefits and pricing across those car insurance service providers.

[00100] In one implementation, the Car Insurance page 1100 provides a payment function that facilitates direct payment to a car insurance provider. The Car Insurance page 1100 also enables the customer 202 to record and store associated receipts and insurance policy documents in the customer database 244. CTP Insurance Registration [00101] In some jurisdictions, registration of a motor vehicle can only occur in conjunction with a customer 202 obtaining a Compulsory Third Party (CTP) insurance policy. Fig. 12 is a screenshot of a CTP Registration page 1200, which includes information relating to policy number, expiry date, amount due, CTP insurance company, payment URL, phone number. The CTP Registration page 1200 also provides functionality to enable the customer 202 to pay the CTP insurance policy or shop around for a new CTP insurance policy.

[00102] In one implementation, the CTP Registration page 1200 includes functionality to send future reminders from the notifications module 248 to the customer 202 and to schedule a booking for a required service or inspection. In one implementation, the CTP Registration page 1200 provides a comparison table for a set of CTP service providers, so PSNP002AUD1 - specification.docx 20 2017100189 17 Feb 2017 that the customer 202 can readily compare benefits and pricing across those CTP service providers.

[00103] In one implementation, the CTP Registration page 1200 provides a payment function that facilitates direct payment to a CTP insurance provider. The CTP Registration page 1200 also enables the customer 202 to record and store associated receipts and insurance policy documents in the customer database 244.

Service [00104] Fig. 13 is a screenshot of a Service page 1300, which includes information relating to a next scheduled service date, type of service, service URL, service centre/dealership, and phone number. The Service page 1300 enables the customer 202 to schedule a service and upload receipts. The Service page 1300 can also provide service reminders generated by the notifications module 248. The Service page 1300 also provides buttons by which the customer 202 can add service receipts to the customer database 244 and shop for parts.

[00105] The Service page 1300 optionally includes a link to a service dealership provider page. The customer 202 is able to upload details regarding a current mechanic, book a future service appointment, or seek a quote from local service providers. In one implementation, service providers 280, 290 include one or more local car mechanics who can either respond to a request for a quote from the customer 202 or otherwise advertise scheduled service rates for display on the Service page 1300 or via a link on the Service page 1300.

Finance [00106] Fig. 14 is a screenshot of a Finance page 1400, which includes information relating to finance associated with a vehicle. The Finance page 1400 enables a customer 202 to upload finance contracts and can generate payment reminders and calculate loan repayments and refinancing. The Finance page 1400 includes a car contract number, company name through which the car has been financed, payment URL, company phone number, payment due amount, payment term, and payment day. The Finance page 1400 provides an interface to enable the Customer to upload photos or other details of a finance contract. Optionally, the Finance page 1400 provides a button to apply for a loan, such as via the system 201 to one or more of the service providers 280, 290. PSNP002AUD1 21 2017100189 17 Feb 2017 [00107] The Finance page 1400 is configured to send reminder notifications regarding current and future payments and payment schedules through the functions of the notifications module 248. The Finance page 1400 also enables the customer 202 to upload and store receipts, contracts, and the like to the customer database 244.

[00108] Fig. 15 is a screenshot of a Finance interface 1500, which provides a customer 202 with access to: apply for a loan; obtain a vehicle valuation; and calculate a loan. In one implementation, the Finance page 1400 and/or the Finance interface 1500 optionally include a comparison table of finance options offered by one or more service providers 280, 290. In another implementation, the Finance page 1400 and/or the Finance interface 1500 include advertisements from one or more finance service providers, wherein the advertisements may include links to websites associated with those finance service providers.

Calculate Loan EMI

[00109] Fig. 16 is a screenshot of a Loan page 1600, which calculates a loan equated monthly instalment (EMI). In the example of Fig. 16, a proposed loan amount is $100,000 at an interest rate of 10% over a 20 month loan term. The calculated EMI is $5,472.04 and Total Payments equal $109,440.84, with Total Interest Payable of $9,440.83. The Loan page 1600 also provides a graphical representation, in the form of a pie chart, of the relative size of the payable interest to the principal of the loan.

Roadside Assistance [00110] Fig. 17 is a screenshot of a Roadside page 1700, which includes information relating to roadside assistance associated with a vehicle. In this example, the Roadside page 1700 includes information that includes a policy number, expiry date, amount due, roadside assistance company, payment URL, phone number, type(s) of roadside cover, and number of years. The Roadside page 1700 also includes functionality to store receipts associated with roadside assistance in the customer database 244, as well as functionality to enable the customer to pay now and shop for other roadside assistance offers.

Tolls & Fines [00111] Fig. 18 is a screenshot of a Tolls & Fines page 1800, which includes information relating to tolls and fines associated with a vehicle and provides functionality to pay tolls and fines, upload documentation relating to an infringement, and manage expiry dates. The Tolls & Fines page 1800 includes details of an electronic toll tag supplier, a payment PSNP002AUD1 - specification.docx 22 2017100189 17 Feb 2017 URL, a phone number, a tolls customer accounts, an infringement notice number, an expiry date, and amount due. The Tolls & Fines page 1800 also provides access to a payment portal to pay tolls, fines, or other infringement penalties.

[00112] The Tolls & Fines page 1800 further provides functionality by which the customer 202 can upload receipts and other relevant information. Such relevant information may include, for example, photos associated with a fine or infringement notice, including photos of street signs, lane markings, and the like. The photos may be uploaded by the customer 202 or retrieved from a database associated with an authority responsible for issuing the fine/infringement notice. In another embodiment, the Tolls & Fines page 1800 provides a link to a mapping function, such as Google Maps, to enable the customer 202 to view a location in which a fine or infringement was imposed. The customer 202 can use the mapping function to view street signs, road markings, obstructions, and the like and save any relevant photos or images to the system 201.

[00113] The Tolls & Fines page 1800 optionally sends reminder notifications to the customer 202 as the deadline for payment or other action in relation to a toll/fine/infringement notice draws near.

Warranty [00114] Fig. 19 is a screenshot of a Warranty page 1900, which includes information relating to warranty associated with a vehicle. The Warranty page 1900 sends reminders regarding deadlines or renewal dates from the notifications module 248 to the customer 202 and provides an interface by which the customer 202 can establish and maintain contact details and upload warranty information in the customer database 244. The Warranty page 1900 includes warranty policy number, expiry date, warranty company, payment URL, phone number, types of warranty, warranty year, and functionality to pay any outstanding amount and upload receipts. The Warranty page 1900 includes functionality to generate reminder notifications and calendar entries regarding forthcoming payments, inspections, servicing, and the like. The Warranty page 1900 may also include information regarding past claim history, along with photos, reports, recall notices, or other documentary evidence. imotor Helper [00115] Fig. 20 is a screenshot of an imotor Helper page 2000, which is a help interface for the customer 202. In the example of Fig. 20, the imotor Helper page 2000 includes options for the customer 202 to seek assistance with respect to: PSNP002AUD1 - specification.docx 23 2017100189 17 Feb 2017 • A better deal on finance; • Upgrading a car; • Valuing a car; • Needing better insurance; • Needing better CTP; • Warranty; • Car Repair; and • Service.

[00116] The imotor Helper page 2000 assists customers to find a more competitive deal on insurance, finance, car purchase price, or car valuation. The imotor Helper page 2000 generates customer referrals. A customer 202 accessing the imotor Helper page 2000 can be connected to an imotor representative, via the system 201. Such an imotor representative can either address the query from the customer 202 directly or connect the customer 202 to an appropriate delegate from a service provider, such as a finance or insurance broker.

What's New [00117] Fig. 21 is a screenshot of a What's New page 2100, which provides an interface to enable the customer 202 to browse vehicles and automotive products available for sale. In one implementation, vehicles and products available for sale are presented in a grid-type arrangement, with a scrolling/search function. The customer 202 may apply one or more filters, such as, for example, relating to make, model, year, mileage, minimum price, maximum price, new/used/demo, location, and the like.

[00118] The What's New page 2100 optionally includes a button that initiates a request to the system 201, whereby the system 201 identifies an authorised representative to contact the customer 202 in response to the request. The authorised representative may be selected from a stored list of such representatives, whereby identification of the authorised representative may be based on one or more attributes associated with a stored profile associated with each of those representatives.

[00119] The What's New page 1200 also provides a platform for automotive retailers and service providers to advertise products, sales, and promotional offers. The customer 202 is also able to upload photos of a car or automobile part, whereby the system 201 sends the photos to wholesalers and/or finance brokers, as appropriate, to provide information to the customer 202. PSNP002AUD1 - specification.docx 24 2017100189 17 Feb 2017 [00120] The system 201 also provides a messaging system, which allows registered customers to communicate with each other via the app, website dashboard, email, SMS, or other electronic messaging system, in relation to products offered for sale through the What's New page 2100. The system 201 optionally charges service providers 280, 290 and customers advertising on the What's New page 2100 a predefined fee, which is managed by the accounts module 250. Payment for products sold through the What's New page 2100 may be made directly from the buyer to the seller, or may occur through a payment gateway maintained by the system 201.

Add Offer [00121] Fig. 22 is a screenshot of an Add Offer page 2200, which provides an interface to enable the customer 202 to offer a vehicle or parts for sale. The Add Offer page 2200 includes details such as category, product title, start date, location, description, phone number, and amount.

Industrial Applicability [00122] The arrangements described are applicable to the retail and service industries and particularly for the automotive industry.

[00123] The foregoing describes only some embodiments of the present invention, and modifications and/or changes can be made thereto without departing from the scope and spirit of the invention, the embodiments being illustrative and not restrictive.

[00124] In the context of this specification, the word "comprising" and its associated grammatical constructions mean "including principally but not necessarily solely" or "having" or "including", and not "consisting only of". Variations of the word "comprising", such as "comprise" and "comprises" have correspondingly varied meanings.

[00125] As used throughout this specification, unless otherwise specified, the use of ordinal adjectives "first", "second", "third", "fourth", etc., to describe common or related objects, indicates that reference is being made to different instances of those common or related objects, and is not intended to imply that the objects so described must be provided or positioned in a given order or sequence, either temporally, spatially, in ranking, or in any other manner.

[00126] Although the invention has been described with reference to specific examples, it will be appreciated by those skilled in the art that the invention may be embodied in many other forms. >n.dc

PSNP002AUC

Claims (5)

1. The claims defining the invention are as follows:

   1. An online method for managing asset data, comprising the steps of: storing in an asset data management system a customer profile for a registered customer, said customer profile including a set of attributes pertaining to an asset owned by said registered customer; uploading asset information to said asset data management system, via a communications network coupled to said asset data management system; and sending a notification to said registered customer in advance of a deadline associated with said vehicle, based on at least one of said attributes or said asset information.
2. 2. The method according to claim 1, wherein said asset is a vehicle and said asset information includes at least one of sales contract, warranty information, service information, toll information, fine information, sales information, and insurance information.
3. 3. The method according to claim 2, wherein said set of attributes includes at least one of vehicle identification number (VIN), registration number, vehicle manufacturer, and model.
4. 4. The method according to claim 1, wherein said asset is selected from the group consisting of vehicles, boats, jet skis, real estate, and jewellery.
5. 5. An asset data management system comprising: a server coupled to a communications network, said server including: a template database for storing user interface templates for display to a screen of a user computing device; a customer database for storing a customer profile associated with a registered user of said asset data management system, said customer profile including asset information relating to an asset owned by the registered user; a notifications module configured to send notifications to said registered users, based on said asset information; and a user computing device coupled to said server via a communications network, said user computing device executing a software application to perform the steps of: uploading asset information to said customer database, said asset information selected from the group consisting of contracts, receipts, photos, and documents; and receiving user input from said registered user accessing said user computing device; wherein said notifications module transmits a notification to said user computing device in advance of a deadline associated with said asset, based on said asset information.