What applications should leverage MOSS 2007 functionality, versus
those that require advanced ECM systems?
What is the functional comparison between MOSS2007
and advanced ECM systems?
How
should my architectural framework change as a result of bringing MOSS
2007 into the mix?
How do I control the costs of a MOSS 2007 implementation to ensure
they do not become redundant with existing ECM investments?
What are the policies that should govern implementation and administration?
What group or function should own responsibility for MOSS 2007 and
/or our existing ECM systems?
Which system should serve as my official system of record?
What about metadata and information taxonomy synchronization?
Will MOSS 2007 meet my enterprise search requirements?
How do I accelerate the implementation of solutions that leverage
both MOSs 2007 and advanced ECM solutions?
MOSS 2007 has been rolled out by many business units and workgroups
as a way of meeting their immediate, tactical content management
needs. And MOSS 2007 is likely to accelerate this dynamic, with
capabilities that simplify deployment.
In our MOSS 2007 white paper, Doculabs has compiled the top ten
questions (shown at the right) our consulting clients ask us, together
with answers that will help you to address these questions in your
own organization. Our objective is to clarify the primary capabilities
and usage scenarios that Microsoft highlights with it's introduction
of MOSS 2007: collaboration, portal, business intelligence, search,
business process and forms, and enterprise content management.
To request a copy of our SharePoint Co-existence white paper or
for more information, please contact
us.
What applications should leverage MOSS 2007 functionality, versus
those that require advanced ECM systems?