+ ideaMatrix is
+ one read+write
BlackBerry data image to
+ one read+write server
data image,
+ referenceMatrix is
+ one master read+write
server image,
+ one master read+write
BlackBerry image, and
+ many read-only
BlackBerry images,
+ knowledgeMatrix is
+ one master read+write
server image,
+ many read+write server
images, and
+ many read+write
BlackBerry images with
+ a sophisticated
collision resolution engine on the server.
Why are todoMatrix and ideaMatrix separate
products?
Because of the user interface similarities, we are
sometimes asked why todoMatrix and ideaMatrix are different products.
From a logical use perspective, people use the applications to hold
different stacks of data. ideaMatrix is used for lasting information
that a person wants to keep into the future. todoMatrix is usually
full of short-term items that get cycled out relatively quickly. For
example, a person might create a folder in ideaMatrix that is an outline of
a project. Within the folder, he might keep a log of conversations he
had, as well as e-mails that were received and send. When he needs to
call someone, he adds a task in todoMatrix to remind himself to make the
call on Tuesday, but after Tuesday has come and gone, that tasks can easily
be deleted. There is no reason to keep a lasting record of the
hundreds of small urgencies that surround a project, but there is great
reason to remember an e-mail that changed contract terms or a pricing quote.
From a technical perspective, the short answer
is that the underlying Matrix database is tuned and configured very
differently while maintaining similar user interface screens, with a goal of
reducing the time it takes to become a power user. todoMatrix is made
to work well with short data records and has a large number of related
fields with each record to accomplish functions such as delegation and
multiple alerts. The result is a quick and nimble task manager.
ideaMatrix on the other hand, chains many records together in the database
to give the user the ability to store and work with very large notes (this
chaining is invisible to the user).
Both todoMatrix and ideaMatrix are tuned to
accomplish their primary task efficiently and their tasks are in truth,
substantially different. By producing two applications, REXwireless
can achieve best-in-class in two areas - if we were to try to make one
application to fit all, compromises would be introduced in both arenas and
result in a watered down software package that would not be world-class at
either goal.
Why are ideaMatrix, referenceMatrix, and
knowledgeMatrix separate products?
ReferenceMatrix and KnowledgeMatrix are
group versions of ideaMatrix, also serving different purposes.
ReferenceMatrix is great for procedures, checklists, forms, and
documentation that change often but need the added attention of centralized
administrator / gatekeeper editing and control. KnowledgeMatrix is a
free-for-all, where a team is working together and collaborating on a daily
basis. It really does not make much sense to use a product that does
not fit what a person or a team is trying to accomplish.
Because of the user/client side of
referenceMatrix and knowledgeMatrix is essentially the same as ideaMatrix,
please use the ideaMatrix documentation for user level functionality on
these two products.
Please select the documentation you would like to
review:
REXwireless Frequently Asked Questions (FAQ)
todoMatrix
2007 professional
ideaMatrix
2007 professional |
