Customer History best practices? (equipment, invoice history, service history)

I need some ideas on how this could or should be accomplished in MODx.

The company (an alarm system installer) wants to let their customers login to their website and see details like:

• Installed system details including purchase dates, model numbers, accessories, and some more generic items like links to related PDF manuals, etc.
• Service Call history where they can see what repairs were made, etc.
• Invoice history, along with paid/unpaid status, etc.

And perhaps some other details once they get the basics working.

So, what is the best way in MODx to store this customer specific info and then be able to spit it back out for just the logged in customer? Or is this something that will have to wait for Revolution?

I would use eform2db http://modxcms.com/forums/index.php/topic,31363.msg190208.html#msg190208

and set up a custom db tables.
+WebLogin/WebSignup +MemeberCheck etc.

Cool that looks like it might handle most of the requirements.

Another twist to the problem is that some customers have more than one system for which data needs to be displayed. Some have two or three alarms systems but then some like the local school system have as many as 10+ (high school, middle school, elementary, etc.).

How does one go about setting up a database so that a primary user account can track possibly an unlimited set of sub account data. For example:

Local School System
-Billing Address
-Contact Info

-Installed System 1
--Elementary School
--Physical Address
--Contacts at location
--System Specs
--Manual for System
--Invoices/Work Orders
--Etc.

-Installed System 2
--High School
--Physical Address
--Contacts at location
--System Specs
--Manual for System
--Invoices/Work Orders
--Etc.

(continue forever)

So how do I allow for the possibility of an unlimited amount of these to be added under a customer’s main account and still have the option for them to make changes to things like the contact info, billing address, whatever.

------------------------

Then finally, a third point to complicate things (long term goal) is that possibly I’ll need the ability to connect multiple user login accounts to the main customer account data. So that someone at the elementary school could login and view data for only their system while the admin staff or whoever could see info for everything and also make changes.

MODx EVO have awesome resource/user permissions.
Put users into user groups tie them with resource groups.
http://bobsguides.com/permissions.html

I let my web users create and update db fields with
eform2db (e.g. youtube video for their profile) then I log in as
manager and control everything with dbedit module http://modxcms.com/forums/index.php/topic,32720.0.html

Then for getting the data I use this approach http://wiki.modxcms.com/index.php/DB_query_and_Placeholders

More on this
http://modxcms.com/forums/index.php/topic,31097.msg266141.html#msg266141
http://modxcms.com/forums/index.php/topic,44426.msg266285.html#msg266285