talmanassociates.comtalmanassociates.com/samples/CMSAnaly… · XLS file · Web view ·...

Page 1 of 151

Content Management Questions

Section Question Interpretation Notes WeightBusiness Profile

3

Customer Profiles

3

Version Upgrade Policy

3

Binding Agreements

3

References

3

Typical Project Project/Staff

2

What factors are necessary to ensure a successful deployment? 4

This questionnaire is based on the criteria for selecting a CMS recommended in Chapter 16 of Content Management Bible by Bob Boiko. Some of the questions may or may not apply to Intel's immediate needs, but vendor responses to all of the questions will help us determine the power, scope and flexibility of cometing products. Please review the questions below, and make any changes you see fit to reflect Intel's needs or interests. I would also like to get a feeling for the relative importance of each question. For each question, please rank from 1 to 10 based on your area of expertise. A rating of 0 will eliminate the question from consideration.Note that the pages in this spreadsheet are interlinked. You only need to change the question in this page and it will be reflected in all pages. If you need to add a question, contact Mike Talman.

BusinessCriteria How long have you been in the CM business and have been

producing the proposed product. What kind of growth have you seen?

It's important to know how much expertise in CM the company has. We may be surprised at how small even some of the major players are. But more important is their CM experience.

Please supply profiles of completed and ongoing corporate Intranet installations. Which use the current version and which use earlier releases?

We want to know where their software is targetted. If they can send us the profiles of the accounts that they see as key to their success, we can decide whether we fit their profile. If, on the other hand, we're nothing like their target customer, are we looking at the right product?

What is your version upgrade policy, including how new releases, upcoming features, hot fixes, betas, and patches are communicated to customers and released. How often should we expect updates or upgrades and how much will they cost.

Given that next versions are going to be needed (a near certainty), we should ask vendors about their upgrade policy. Most of this will be left to ITSP, but we need to get an idea of upgrade costs/policies.

For issues that come up that aren't resolved in the current version but are promised in future versions, what sorts of binding agreements or penalties are you willing to take on?

These binding agreements are one way to ensure that the vendor is serious about what's in the next version. This is another area for ITSP negotiation.

Please supply at least three references (both business and technical, if possible) of customers who are currently using your product.

Ask for references at the sites of the projects that are like ours. If possible, the references should include a business as well as a technical contact.

Describe the general steps involved in an implementation of your product.

Does it seem overly simplified or does it differ widely from our workflow process?Does the vendor offer any particular wisdom that shows that they've seen and surmounted a lot of problems?

Page 2 of 151

Typical Project

4

4

4

What professional services does your company provide?

2

2

2

Development environment

4

5

What APIs are provided as standard with your product?

6

8

7

7

What's the typical time frame for a deployment and what can be done to minimize the time and effort required?

Does the vendor's timeframe include the full customization that probably needs to be programmed in or just general installation and some basic template setup?

Provide an example of project plans and deliverables from projects that are close in scope to ours.

The response tells us whether the vendor's completed projects like ours, how organized the project process is, and how strong the deliverables are.

Describe the various project roles (both your own staff and your customers') and the numbers of people involved in each role. Describe what roles people had before the implementation and how their roles changed after implementation.

How complete and realistic are these lists? Do they miss any categories?

Many CMS product companies can provide full service, from design to maintenance. Each, however, has its own particular way of doing so. Keep in mind that the majority of a CM project lies OUTSIDE the software.

For a project such as ours, what sort of professional services do you recommend?

Try to get past a description of the standard services packages that the company offers, to the particular project composition that it sees for IT Storefront.

Can you provide a list of your service staff positions and their billing rates?

What staff (if any) can they provide on a contract basis to assist during deployment?

What development languages and tools were used to create your product?

Should be a standard language that we have staff to customize the product. C++, Java, etc.

Please provide an overview of the ways programmers can customize or extend your product, including the languages and tools needed.

We especially need to see how well we can create alternative workflows within Savvion.

An extensive, well-documented API is preferred. Best is that the company builds its own user interface from the same API so that we can make sure that it's well tested and provides complete coverage of the product's functions.

What skills and tools are needed to create and modify basic templates for authoring, submitting, and publishing content?

Basic templates shouldn't require programming skills. Ideally, the tools are those that a person who can use a graphical HTML editor can easily learn and use.

What skills and tools are needed to extend and integrate templates beyond basic content inclusion and layout?

Nonproprietary development languages and tools are preferred. We want a wide variety of people to be able to create templates. If a programmer is required to create page layouts, we'll have trouble.

What languages and tools does your system support for automating administrative functions?

We want to hear that all the administrative functions of the product, including workflow, user administration, database management, and reporting, can be called independently by us, using Web technologies that we want to use (ASP, JSP, CORBA, COM, J2EE, and the like).

Page 3 of 151

Typical Project

7

Localization

5

5

4

7

3

Can you version and track changes at the element level?8

3

5

TrainingPlease provide an overview of the training that you provide.

5

5

What languages and tools does your system support for automating content authoring and acquisition?

At the very least, we should be able to modify collection Web-based forms and embed them in our own Web applications. It's better if the product offers out-of-the-box integrations with the authoring tools that we need. Principally: Word, Excel, PowerPoint, DreamWeaver, Visio, etc. We should be able to extend and modify these tools, using the programming languages that we prefer.

Please provide an overview of how your product supports publication localization. What specific tools and processes do you provide?

The overview ought to tell us how well the company understands localization and how deep its support for it is. This is expecially important for overseas locations. Getting Asian and European sites to contribute more to the IT Storefront is highly valuable.

How is translated content produced and synchronized with the source content?

Ideally, the system maintains linkages between translated components to manage updates. It must be capable of handling content in different languages, including support for double-byte character sets or Unicode, international date formats, and global currencies. The screens that the content maintainers use must be easily translatable into different languages

Are there any facilities in your product for multiple selection images or other media?

We will need various versions of graphics and other media that are localized for various regions.

Please give a full example, with references and URLs, of a customer that has successfully used your system to create a global localization and translation solution.

A successful implementation by a customer who agrees to be a reference is a strong point in the company's favor.

Do you have any translation aids in your product, or do you integrate with any?

Translation aids help us put the master and translated versions of content side by side for comparison and difference checking.

It's really helpful to be able to send some component elements for localization separately from others that don't need to be localized.

Is there template functionality for sniffing the origin nation and redirecting?

The CMS should be capable of reading HTTP headers and helping you decide the region of origin of Web visitors.

Do you provide multilingual UI for content contributors and producers?

Our international contributors will need, and are certain to appreciate, anything that we can do to localize their CMS interface.

The company must have put effort and resources into training and ensure that it's professionally delivered. Should also provide materials and curricula for Intel training.

What's the availability and cost of training, and how frequently is it offered?

We want to make sure that the training schedule doesn't affect our implementation timing.

Page 4 of 151

Typical Project

Is training held at your site or ours? Must offer on-site training. 7What CMS staff positions do you train for?

6

Technical Support

7

Do you provide support, or do you work with any partners?

6

We will need global 24/7 support. 7

In what languages is support available? Should cover most of Intel Corp.'s geographic diversity. 6What's the guaranteed response time for a support request? 6

6

What kinds of self-help facilities do you provide?

8

8

7

6

4

There's almost always end-user and administrator training, but is there training for developers, managers, information architects, IT staff, or designers?

Please provide an overview of the technical support that you provide.

Has the company put effort and resources into support and that is it professionally delivered?If the company's small, it's better if it's partnered with a larger support organization that can bring its support up to enterprise levels. On the other hand, we want to see that the company can provide the specific expertise to the partner to augment the partner's ability to address problems.

What's the geographic coverage of support, and at what hours is it available?

How willing is the company to guarantee anything having to do with support?

Is there a single point of contact for support, or do people need to know whom to call for what?

A single point of contact with fast triage and routing to the appropriate contact is preferred.FAQs, known bugs and workarounds, and tutorials for beginners can save a lot of money for the support organization. Can those facilities be syndicated through Intel's Intranet?

What guaranteed expertise is available on the first call, and what are the escalation procedures? How high in the technical organization can an issue be escalated?

The optimum cost-effective solution is to have enough skill on the first call to correctly route the problem. We want to see that, from the first call, there's problem tracking and a logical and reasonable set of criteria for escalating to each new level of expertise.

Describe your support licensing plans and associated costs. Do you offer a pay-as-you-go plan as well as contracts?

We may prefer a cost-per-use model that you can charge back to business units rather than a fixed fee.

What comes as part of the purchase price and what are the costs associated with ongoing support after the initial purchase and installation?

The extent of services for setup and the cost of ongoing support can vary. We need to take into consideration the "total cost of ownership," not just the initial purchase price.

Are there any provisions for downtime or loss of revenue from systems impaired by a CMS bug?

This sort of seriousness may be necessary. A willingness to enter into this sort of agreement shows that the company has extreme confidence in its system (or isn't smart enough to know that these sorts of agreements put it at financial risk).

Page 5 of 151

Typical Project

5

DeploymentWhat operating systems does your product run on? Should cover current versions of Win2K and XP Professional. 5

6

IE5.X 7

6

8

7

5

Collection Authoring

5

How wide is the support? What software and hardware is covered?

How are problems that may be outside the CMS software supported? Are extensions using the standard API supported? Are template bugs supported? Are platform, operating system, Web application server, and database and network connectivity issues supported? For issues that aren't supported, how is it determined where the problem lies and how does Intel's staff then tie into the appropriate other support organization?

What operating systems are required on the client machines for the database client and authoring tools? Describe any client-side software needed to use the system.

All basic functionality should be available through a Web interface so that the client needs only a Web browser. Client software should be available, but not required, as a supplement to a browser interface to enable a richer and more responsive UI.

Which Web browsers are supported for authoring, management, and administrative functions?Describe the skills and size of the team needed to successfully deploy and maintain your product.

An open-ended question that we can use to assess the company's process and savvy on this issue.

What models do you employ for distributing the management and publishing environments across business units that aren't in the same facility?

We want people to contribute from around the world and for them to publish locally. We want to assess how the CMS can help us keep this distributed environment organized and minimize redundancy.

Is your system best deployed inside or outside a firewall? Describe the difference in requirements or performance if your system is deployed inside or outside a firewall.

This question helps get at the distinctions of using this system for an intranet vs. an Internet site. It also uncovers any problems that we may experience with remote contributors accessing the CMS.

Describe the process that you'd use to deploy your system across an organization with a structure such as ours.

Another open-ended question to see how well the company can understand and provide for our specific environment. We want to add a list of the significant factors that are present in our organization.

Do you ship with any specific authoring tools? If so, which one(s)?

Only a few CMS products ship with authoring tools (word processors, image-creation tools, HTML editors, and so on). Although it's helpful to know whether the product includes these tools, it's probably more important to find out whether the product supports the wide variety of authoring tools being used at Intel.

Page 6 of 151

Collection

With what third-party authoring tools do you directly integrate?

8

What file formats can your CMS repository store?

9

7

9

9

8

7

7

7

8

Direct integration means that some aspect of the CMS appears within the authoring tool. Some CMS products create a menu within a particular authoring tool, for example, so that authors can save content to and retrieve content from the CMS repository.

Many CMS products can manage files that are authored in any tool. Of course, they generally don't manage the content within these files. In other words, the CMS serves as a document management system for files that it can't interpret.

If you do support multiple file formats, how much categorization, indexing and metadata can the CMS apply to those files. Or, alternatively, are there third-party add-ons which can accomplish such tasks.

Some CMS products have pretty much full document management capabilities. MSCMS, for example, does not do this, but there are third party products like Q-Docs that add the functionality. This and the previous question will determine how much we can count on it to replace and expand DocLib

What file formats can your product recognize and convert to XML or database records?

In this case, we're interested in the product's capability to open foreign file formats and parse them. The result is generally either XML that can be stored in an XML repository or relational database records with the full content of the source file in them. Some products, for example, take the text that you write in Microsoft Word and convert it automatically into XML for storage in the product's repository.

Please describe how a novice content contributor could author the textual content for a Web page and include graphics or other types of media to go along with the text.

We want the system to be simple enough for beginners and casual authors to create simple pages with little or no help.

Please give an overview of your Web-based form system for content input.

Almost all products now have a Web interface for content entry. Some may have a non-Web system as well that has fuller functionality than the Web-based forms.

Do you enable rich HTML or XML editing within the fields on your Web-based forms?

Some products include a little editing environment right in a Web-based form so that authors can format information as they type it.

Can Web-based forms show different sets of elements based on the user's permissions?

In other words, can we personalize input forms so that different people see different parts of the same content component, based on what we want them to enter?

What support do your forms offer for linking and uploading images and other media?

We want to ensure that it's easy to add media and associate it with textual content.

Can your forms be automatically created from a DTD or database schema?

Some products autogenerate Web-based forms from the structures that we've previously defined, saving a lot of work.

Page 7 of 151

Collection

7

Can your forms represent hierarchical relationships?

7

8

7

Can authors view a revision and workflow history for their work? 6

Can authors perform a spelling check on their work?6

7

AcquisitionWith what acquisition tools does your product ship?

5

With what third-party acquisition tools do you integrate?6

9

Can your Web-based forms be extended or modified by additional HTML or other programming?

This is an important factor, because it's likely that we'll want to customize forms and need additional features. Ideally, the forms can be customized by using a nonproprietary programming language.

All products enable us to put a set of fields on a Web-based form. A few also enable us to nest some fields within others. This is really handy for entering the titles and text in sections and subsections.

Can authors create content while they're not connected and then submit it later?

In other words, can we use the CMS authoring tools "offline," a handy feature for authors who don't work on-site or for contributors who travel frequently?

Can authors preview content as it may appear in publications, before they finally submit it?

A preview function is extremely helpful and streamlines content creation and quality assurance workflows considerably.

An audit trail of workflow for each component is helpful for accountability as well as content troubleshooting.A nice feature to have, although rare in CMS tools. Usually, spellchecking is done before the content is placed in the CMS.

Describe the training expectations required for new content contributors.

The system should require minimal training for novice or casual contributors. We should expect some training requirements for more advanced authors.

Some products include advanced tools for scanning content sources and automatically capturing content. Some have syndication tools that enable us automatically to accept incoming syndication feeds.

Most of the larger companies have strategic relationships with other companies (often, content syndicators) to augment their abilities to acquire content automatically.

How would we migrate our existing Web sites and other publications into your system?

Is there an automated process to import an existing Web site, or does it require an in-depth content analysis and restructuring into predefined content structures? Are there any tools at all for migrating publication types other than Web-based ones? This could be especially important to us, as we have LOTS of content to convert. Even if it would require extensive proofing, an automated system could save a lot of time and money.

Page 8 of 151

Collection

7

Conversion

6

With what third-party conversion tools do you integrate?

5

6

Metadata

8

7

7

Can you define mandatory and optional metatags?7

6

Can your product automatically retrieve records from a database available locally and turn them into content components in your repository? Can these downloads be scheduled to happen periodically, with no human intervention?

The company may depend on standard programming to accomplish this, but it should demonstrate that its people understand the issue and have worked through it. We may have a product catalog database, for example, and want to create new components after new products are added to the database.

Does your product ship with any conversion tools? If so, please describe their capabilities.

Products really vary on this count. Some have no converters at all. Others have a wide range of built-in tools for text and media conversion.The answer to this question ought to give us a feeling for how well the company understands conversion. Does it have any partners there? Does it have an idea of how conversion fits into the process?

How does your product support on-the-fly conversion of text and media on a Web site?

As pages are requested, can the product retrieve content and convert it to the appropriate format? If so, we can store our media in one format and have it converted only if it's requested in another format. This isn't typical functionality, but some products can do it.

Does your product include or integrate with any metadata management tools?

Some products include auto-discovery and taxonomy creation tools that help us design metadata lists and automatically find metadata in the files that we process.

Can you automatically apply metadata values to content based on its type or location?

Some products enable us to choose a directory or other branch and batch-apply a metadata value to it. In addition, some can supply default values for metadata fields, based on the type of content being tagged.

Does your product have any tools for helping the administrator combine or split metadata fields that currently exist in the system?

We may need to combine two similar metadata fields into one (for example, we may decide to merge an author field and a contributor field into one field) or split one field into two. (A single status field may need to be split into a publishing status field and an archive status field, to give us more control.)

This may be done in the Web-based form interface, but it may also be possible to do it globally for all uses of a particular metadata field.

Can you pull metadata lists from other sources, such as a database or a flat file?

We want to see, for example, if the product enables us to draw our list of products automatically out of a database and present them in a Web-based form. This may not be germane, as that's what we have Commerce Server for, as well as Savvion.

Page 9 of 151

Collection

6

8

Does your product tie into any accepted standards for metadata?

8

7

Management Storage

7

7

8

This may not be necessary, but let's ask it.

5

8

Can you write metadata lists to other external files and databases?

We want to see whether the product enables us, for example, to add to the list of products and then periodically export the updated list to the database in which it originated.

Can you automatically bring up metadata lists or values for periodic expiration or review?

As part of managing our metadata system, we need to periodically review the validity of lists or values and either update or delete them. If we do, it's nice to have a tool that helps us update all the content that's affected by the change that we're making.

The Dublin Core Metadata Initiative and a host of other industry-specific metadata systems are being created and revised. At some point, we may want to use one or more of them. Can the CMS help us or does it stand in our way?

Does your product support all types of metadata types in the repository and metadata fields in your collection forms?

Should support a majority of types among the following for maximum flexibility, : Free Text, Constrained Text, Pattern Text, BLOBS, Boolean, Closed Lists, Open Lists, Unique IDs, References, Outline Lists, Compound Fields.

How do you store content? In a relational database? An object database? A file system? A hybrid of the preceding types?

We want to know how the company structures its content storage to know whether it's compatible with our infrastructure requirements and can handle the sorts of content that we intend to manage.

Describe how your system stores the following content relationships: multiple hierarchies, multiple indexes, cross references between components and between publication pages, and sequences.

These are all the access structures that we need to store and access. All decent CMS products enable us to build a hierarchy. See how well the products that we survey do at building more than one hierarchy for the same set of components.

Does your content repository support extended character sets (double-byte) as well as international date and currency formats?

This is a must to localize in Asian or other double-byte languages.

If your repository system supports XML DTDs or schemas, can you create one DTD for the entire repository? Can you create multiple DTDs that are enforced for part of the overall structure of the repository?

Does your product have the capability to check the validity of links and media references that appear within text fields in the repository?

In many systems, the hyperlinks and media references (such as an <IMG> tag in HTML) that are embedded in the middle of a block of text go unnoticed and can be broken without any clue. It's important that the software enable us to track these links and references even inside paragraphs of text.

Page 10 of 151

Management

7

Administration

6

7

6

Important to be able to track these. 9

Important that it hook into ADS for user roles and rights. 9

7

WorkflowWhat workflow tools does your product include?

7

6

7

8

What indexing and searching does your repository support? Does searching respect security?

A good answer includes rich indexing and querying, metadata (keyword) searching, full-text searching, proximity searching, and relevance ranking of search results, as well as the capability to exclude results that a user doesn't have rights to see.

In what ways can your system enable nontechnical business users to manage their own content?

This is an open-ended question designed to give the company a chance to address ease-of-use issues and how it caters to novice or casual users.

Please describe the utilities provided for system administration and operations personnel to effectively manage and support the system. Please identify any administrative functions, such as configuring workflows or publishing schedules and so on, that can't be accomplished through Web-based tools.

Ideally, all administration should use Web-based tools. If there are some administrative functions that require other software, we need to know about them. This also directly relates to Savvion as our chosen workflow tool.

Can you do a global search and replace throughout the repository?

The CMS should support search and replace through free text and metatags, assuming that appropriate permissions and security rights are observed.

Can you automatically verify and manage broken internal and external links?What user roles and rights model do you use, and what tools do you provide for managing and manipulating them?What's your approach to data synchronization and replication across multiple databases? At what level is synchronization managed and communicated?

It's unlikely that it does a lot of this automatically. Instead, we're most likely to get replication tools that we must control to ensure synchronization.

We're looking for the vendor's description of its workflow tools. We need a good overview here to compare w/Savvion and determine where conflicts and overlaps may occur.

With what workflow tools does your product integrate? What support do you provide for the integration?

Must integrate with Savvion and the company should answer all the questions in this table from a support perspective, as opposed to an implementation perspective. We want to make sure that events and content status transitions in the CMS can correctly trigger events in Savvion.

Please describe the internal or external inputs that can be used to trigger workflow steps.

Look for the capability to trigger workflow steps by an external process, such as an e-mail message arriving or a file being added to a directory.

Please describe how your system handles the configuration of user roles for workflows.

We want to see that the product has strong user interface that gives administrators complete and easy access to the functions that the product offers.

Page 11 of 151

Management

Do you support parallel as well as sequential workflows?7

7

6

6

6

4

8

Can you add comments at the end of each workflow stage? 7

Do you maintain an audit trail for all workflow processes? 7

7

Can we stop or redirect workflows in process? 6

In a parallel workflow, two people work on an item at the same time. In a sequential workflow, one person finishes before the other begins.

Please describe the range of system activities (such as content submission or deletion) that can be supported by workflows.

We want to find out whether the system can handle requests for content, content submission, content addition, deletion, edits for existing content and content bundles, content reviews, content approvals, content migration, migration approval, and so on.

Please describe the content or system attributes that can be used to drive the rules for automated workflow routing.

In other words, what can the system look at in deciding what to do next with a piece of content? (Submitter, content type, and status are some of the usual attributes.) The best answer is that the workflow module can use any piece of metadata that we create.

Please explain or demonstrate the process for creating or modifying a workflow process.

We want to make sure that creation of workflows doesn't require programming skills. The slickest systems have a visual workflow designer with drag-and-drop manipulation of processes. Make sure that either the interface is very complete or that it's extendable. More overlap with Savvion here.

What types of content collection, content management, content publishing, and administrative activities can be handled by an automated workflow process?

We want to know whether the workflow module can handle all authoring and publishing requests, including content submission, content addition, deletions and edits, content review/edits, content approvals, content migration, publishing, and testing.

Do you have the capability to include an external service provider (HTML provider, graphics, or translation services) in the workflow?

We want to make sure that the workflow tools can manage people with only a slow Internet connection to the CMS, no access to the LAN through our firewall, or only an e-mail connection .

Can you view all content that's in a particular state for a particular user?

The best systems have rich queues that show each user what task he must accomplish.This is a handy feature to have. (If not built-in, we probably want to customize the system to include a comments field.)Can we roll back a piece of content to any step by selecting that step in the audit trail.

Using your product, can you integrate e-mail into the workflow processes?

Some systems can run the entire workflow process through e-mail. Users receive notifications in their inboxes and then click links in their messages to complete tasks in the CMS.

Is there an administrative override to automated workflow processes?

Page 12 of 151

Management

At what content level can you create workflows?

7

Integration

6

8

8

5

Version ControlCan users check content into and out of your repository? This is the most basic form of version control. 7

8

7

How is locking handled if content is checked out?6

Need rollback at the site, page and component levels.

8

Most systems can attach a workflow to a file. The better ones can attach a workflow to a component (or whatever name are given components in the product). The best ones can attach a workflow to a particular element of a component. The body element, for example, can have a localization workflow attached to it to make sure that it gets translated. The rest of the component may not need to participate in that workflow.

What capabilities does your system have out of the box and with additional programming to connect to and share data with other databases?

The best case is a nontechnical interface for connecting to simple databases that can be used by administrators, plus the capability for the connection to be extended by programmers using a standard language.

Can you launch other applications from within your system? If so, how? What outside applications are supported?

Many products integrate with Microsoft Office products and Adobe Acrobat. The CMS product also may be capable of launching any viewing and editing tool that the system recognizes based on a file extension.

Do you follow any open standards for data access and data sharing?

Some products follow the XML schema or other open standards such as ODBC for data exchange.

Is it possible to export the entire content of the repository to some standard format. This includes:* content of all topics* links (hypertext links, related topics, etc)* metadata* global taxonomies or topic maps* structural information (including topic hierarchy)

Sufficient information must be provided to allow simple migration of the content into another CMS, or equivalent system.

Does your product save earlier versions of content that can be restored later if necessary?

Make sure that it's reasonably easy for a user with permissions to restore the previous version without the need of a database administrator.

What level of granularity is supported for checking content in and out?

File level is most common; component level is the most useful; and element level check-in and check-out is necessary for more complex tasks, such as localization and collaborative authoring.

We should have the option to lock the component being checked out and possibly also its siblings or parents in the repository hierarchy.

Describe the different levels of granularity at which content can be rolled back to an earlier version. How do you support rollback of a complete site, an individual page, or a single content component?

Page 13 of 151

Management

7

Reporting

8

7

These sorts of reports are very useful to publication teams.6

Disaster recovery

8

7

6

Security

9

Do you support a hierarchical security model? 7

Critical for proprietary information.8

Performance

Can you perform differencing between two versions of the same content?

The best system enables us to put two versions side by side and compare each change.

Describe the logging capabilities of your system. What types of activities can be monitored, for both content producers and consumers? How would you track usage by user, group, or geographic area?

We should be able to track and log users, their time of access, and actions performed (such as downloading a particular version of a file or checking out/editing a file). We should also be able to track system usage by user, group, geographic area, and so on. We should know what kind of logging the CMS provides for staff activities.

Describe the workflow tracking reports that your system can generate.

Workflow reports that are most commonly used show each component or document and its workflow status, along with other supporting information. We would prefer reports that show all components that are at a particular workflow stage.

Can your product generate a complete site map of the Web sites that it produces, including page names and statistics (size, components, and so on)?

What features does your system support for content archiving and disaster recovery?

Features to look for are versioning, rollback, and automated backups. These features may be part of the database software that the CMS uses but could be controlled from the CMS administrative interface.

Can you provide any statistics on the failure rate of your product, such as average time between failures or the average percentage of system availability?

Some can provide this information and others can't. It's a good question to ask as we get to checking references.

Describe any functional and architectural features of your product that are optimized to maximize the reliability of your system.

This is an open-ended question to give the company a chance to brief us on its reliability. Some companies can provide technical white papers that describe their system architecture and reliability features.

Describe how your system can leverage existing operating system or directory services security profiles to avoid needing to re-create definitions and duplicate security maintenance. With what servers and services can you integrate?

Must be able to use existing Intel security mapping and directory services such as Rialto and ADS.

We need the capability to group users and have them inherit permissions from parent groups.

Can your product help us enforce intellectual property rights and security permissions by controlling the capability to publish media?

Page 14 of 151

Management

6

8

8

7

Publishing TemplatingDescribe your overall approach to publication templating? This is our chance to get an overview. 5

5

7

6

Not all products can do this. 7

7

6

5

Describe the minimum and recommended hardware, software, and network requirements of your product at the level of usage that we expect.

Important to determine the initial installation requirements for the full IT Storefront implementation.

Please provide examples and references that demonstrate your system's capability to scale to an enterprise-wide, global implementation. These examples should illustrate your capability to scale to multiple instances on multiple servers, to scale beyond a single Web farm, and to fully support load balancing.

Must be extremely scalable, as IT Storefront grows and becomes a model for an enterprise-wide intranet solution.

Describe any data size or performance limitations of the content repository. Include any known limitations, such as maximum number of rules, number of unique components that can be stored, number of concurrent content contributors that can be supported, or number of concurrent content consumers that can be supported.

Make sure that we check these capacity limits for staff as well as for concurrent audience users of IT Storefront..

Describe your mechanism for content replication to regional sites.

Replication usually consists of a master version and copies that are distributed regionally to improve performance.

What programming languages can be used to develop Web templates?

The right answer is the languages that we use. Barring that, open languages that have a wide skill base in the programmer world are the best choices.

Do you support developing templates for non-HTML publications?

Sadly, most don't. One day, CMS products will support templates in word processing and graphical layout program formats as well. We should find out what sort of materials IT is producing beyond the Web and see what we can make fit.

Can your system process templates in a batch mode, producing complete static sites?

In other words, can the CMS render a static, Web-based publication as well as serve dynamic sites?

Can your system process templates on demand, producing dynamic sites?Can your system mix batch and on-demand processing to produce sites that are partly static and partly dynamic?

Ideally, we want to produce as much of a publication as possible statically for performance and robustness, but still produce other parts dynamically for the flexibility that it offers.

Describe the methods that you support for dynamically creating site navigation components. How are searches, links, a table of contents, or other navigational aids built by logic in the templating system?

We want to see that there are some tools for this but, moreover, that the system is open enough to enable us to extend it to whatever navigation that we may want to produce.

Does your system support the concept of component and navigation templates? If so, how?

Refer to "Publications and Templates (in Chapter 22)," for more information.

Page 15 of 151

Publishing

7

How is personalization accomplished in your templates?8

Content deployment

8

With Savvion, this looks like it could be redundant. 7

6

5

6

Can your product automatically deploy files referenced in a field?8

8

Can you publish on a set schedule without manual intervention?8

Publication platformsCan your system produce broadcast e-mail? 8

Can your system create individualized e-mail messages?

8

How can your system be used to produce print publications? We need to research various print publishing needs within IT. 6

Do your templates support integration with outside systems? If so, how?

Some tools may be provided, but we really want to make sure that the CMS doesn't get in your way as we do this ourselves in Commerce Server and SavvionThis is a very open-ended question that ought to yield a general discussion of the product's personalization tools and integrations.

How can your system be used to deploy content files to remote Web servers?

This is the basic deployment functionality. Surprisingly, many products expect you to do this with third-party products.

How can your product be used to deploy database records to remote databases?Describe or demonstrate a scenario illustrating how content is deployed from a staging server to a production server.

This may or may not be necessary, but a staging environment would provide an extra level of approval for final publishing.

How can your system deploy appropriate content to various destinations, based on properties of the content?

We may, for example, want to key on various values within content components (language, for example) to determine which server to deploy the content to. Can the CMS help us here, or do you need to write your own routines?

Does your product enable you to assign default values for file directories based on content type?

It's useful to have all pages of a particular type deploy automatically to a particular output directory.If a file (an image, say) is referenced inside text that's being published, it's a good idea to have the CMS deploy the file to avoid a broken reference.

Can you set the publish and expiration dates of content to be published?

It's useful if we can have the CMS automatically release and remove content based on the rules that you establish.This is what we need for small, frequently published material daily e-mail broadcasts and syndications to other systems, for example).

The system should be capable of integrating to our e-mail system and pushing content to it. As opposed to bulk e-mail, in which the same message is sent to a lot of people, individualized e-mail is where a lot of different messages are sent to one or a few people each. This capability ties the personalization functionality to the e-mail creation functionality.

Page 16 of 151

Publishing

Can your system syndicate content?

7

Not necessary, but MS Help may have some uses. Also4

PDF is good for downloads that can't be modified by the user. 7

PersonalizationDoes your product ship with any personalization tools? 7

8

8

7

6

7

8

7

7

Can your system perform collaborative filtering?6

Syndication capabilities include creating format-neutral (generally XML) content chunks and deploying them to FTP sites, remote servers, or to mass storage devices (hard drives, CD-ROMs, DVDs, and the like).

Can your system create content for proprietary electronic formats, such as Microsoft Help, Macromedia Director, or other CD-ROM platforms?Can your system create downloadable documents in Portable Document Format (PDF) or other proprietary formats?

Some don't, although most don't easily admit it. Others have extensive offerings.

Does your product integrate with any third-party personalization tools?

Most at least have marketing alliances with personalization companies. Look for documented integrations.

What kind of user interface do you provide for creating and modifying personalization rules?

Some products have very well-developed point-and-click interfaces for rule building. Others require a programmer to code the personalization rules - not a good long-term solution.

Describe or demonstrate the process for defining personalized experiences. What skills and training are needed to work with your personalization engine?

See whether you can get a concise description of the overall approach to personalization that includes a discussion of how it's actually accomplished.

How does your system facilitate the collection and storage of user profile data?

Some products have functions for monitoring the user's actions and their responses to questions and then storing the results in an accessible profile - but don't count on it.

What forms of data are accessible to your personalization engine?

Good answers include user session data, HTTP header information, page history, all content metadata, user profiles inside or outside the CMS repository, user groupings, and personalization rules.

What facilities do you have for producing individualized print publications or other non-Web personalizations?

Most of the action today is in dynamic HTML page building. The same tools could be used to make any other kind of personalized publication, provided that there's template support for the publication format that you need.

Do searches, links, a table of contents, or other navigational aids reflect the personalized content that's available to a specific user? If so, how does it work?

For relatively sophisticated personalizations, the system should be able to modify these access structures automatically, based on the personalization rules.

What sort of personalization rule-building process and user interface do you employ?

Some products have well-developed user interfaces for point-and-click personalization rule building.Collaborative filtering is the process where the system recommends content based on requests of similar users (an approach popularized by Amazon.com).

Page 17 of 151

Publishing

7

7

5

Publication integrations

8

Media and asset management systems 2OS User registries 9ERP systems 5Customer relationship management systems 3Catalog management systems. Should work with MS Commerce Server 8Surveys and questionnaires 6Web access and security tools 9Data logging and mining tools 6

9

Decision tree tools 4

2

Bulletin board and threaded discussion systems 3Event planning and registration tools 4Webcasts and streaming technologies 8E-commerce and financial transactions systems 9

6

9

Web servers and Web application servers 8Web UI

Please outline the kinds of personalizations that are possible based on user profiles.

This is an open question that gets the company to talk about how personalization interacts with profiles. The product may enable us to define profiles, for example, and then target content to them.

Please outline the kinds of personalizations that are possible based on a user's actions on a Web site.

This is also called behavior-based personalization. Some systems track a user's behavior and modify the subsequent pages accordingly.

Can your system facilitate the creation or running of push campaigns?

In a push campaign, the system actively presents certain content on a Web page or in another form to a group of selected users for a specified period of time.

Please list applications in the following categories with which your software has successfully integrated:

Should integrate well with our other systems, both in-place and projected

Document management systems: Specifically do you have a component or add-on that can act as a document management system.

Important for the DocLib team. We may eventually want to upgrade DocLib to a more robust document management system.

Workflow integration systems. Essential: Savvion workflow tool.

Download packaging tools (which automatically bundle together and compress electronic content for efficient download)

Conversion systems for on-the-fly conversion of content (for example, from XML to HTML).Custom database applications and custom programming objects.

Page 18 of 151

Publishing

7

6

This is important stuff for personalization and customization. 8

Web architectureWhich Web servers are supported by your product? IIS is essential 8Does your product include a proprietary Web application server?

2

With what Web application servers does your product integrate?

8

What databases can your system use? SQL Server 2000 and Oracle 8How does your system facilitate or perform content caching?

6

6

We'd need support from the CMS for this. 5

5

Probably there's some integration effort needed.8

List the LDAP servers with which your system can integrate. 5

What types of searching and indexing capabilities can be made available to an end user viewing a Web site produced by your system?

Searching isn't necessarily performed by the CMS. For static sites, a standard third-party search engine may be fine. For dynamic sites that are produced by the CMS on the fly, you need integration between third-party search engines and the CMS search functions.

What particular support do you have for producing browser-independent Web pages?

Some products include browser sniffers and supporting code to make serving browser-specific pages easier.

Does your product support user-session management, including cookies or database caching of user profiles?

Some products still do have their own application servers. You want to make sure that the product doesn't lock us into its own application server but enables us to integrate to one of the better commercial application servers.

For any product that we expect to use for more than the next year, the company needs at least to have plans for how it intends to integrate it with industry-standard application servers.

Caching can happen at many levels. We need to understand the difference between the caching models used by the various contenders. Make sure, too, that the company can demonstrate Web-server performance commensurate with the amount of traffic that we expect.

How does your system facilitate or perform database connection pooling?

This may be handled completely outside the CMS. Know which parts are performed within the CMS and which parts depend on a third-party application server.

How does your system facilitate or perform server load balancing?How does your system facilitate or perform user session management?

Does the system rely on cookies, or does it provide other methods of tracking user sessions?

Can your system leverage user-profile information stored in directory services? Is any custom development needed to implement this functionality?

This is a concern if you're using LDAP services in your environment.

Page 19 of 151

Content Management QuestionnaireSection Question Microsoft Content Management Server

Business Profile

Customer Profiles

Version Upgrade PolicyIntel Licenses all of Microsoft's products

Binding AgreementsNo binding agreements

References


BusinessCriteria How long have you been in the CM

business and have been producing the proposed product. What kind of growth have you seen?

Microsoft acquired NCompass Labs in May of 2001, adding Ncompass Resolution 4.0 to its product line. Renamed MS Content Management Server, the new version, MSCMS 2002, is currently in Beta testing. NCompass Labs, a private company, was founded in February 1996.


MSCMS is installed at around 125 sites, including the Associated Press, Fujitsu Systems Business of America Inc., Johnson & Johnson Inc., Marriott International Inc., Texaco Inc. and Verizon Communications.




Describe the general steps involved in an implementation of your product.What factors are necessary to ensure a successful deployment?

Page 20 of 151

Typical Project





What professional services does your company provide?For a project such as ours, what sort of professional services do you recommend?




What APIs are provided as standard with your product?What skills and tools are needed to create and modify basic templates for authoring, submitting, and publishing content?


Page 21 of 151

Typical Project

Localization

Training

Is training held at your site or ours?








Can you version and track changes at the element level?Is there template functionality for sniffing the origin nation and redirecting?


Please provide an overview of the training that you provide.What's the availability and cost of training, and how frequently is it offered?

What CMS staff positions do you train for?

Page 22 of 151

Typical Project

Technical Support

In what languages is support available?

Deployment

Please provide an overview of the technical support that you provide.Do you provide support, or do you work with any partners?What's the geographic coverage of support, and at what hours is it available?

What's the guaranteed response time for a support request?Is there a single point of contact for support, or do people need to know whom to call for what?

What kinds of self-help facilities do you provide?What guaranteed expertise is available on the first call, and what are the escalation procedures? How high in the technical organization can an issue be escalated?





What operating systems does your product run on?

Page 23 of 151

Typical Project



Which Web browsers are supported for authoring, management, and administrative functions?

Describe the skills and size of the team needed to successfully deploy and maintain your product.




Do you ship with any specific authoring tools? If so, which one(s)?With what third-party authoring tools do you directly integrate?What file formats can your CMS repository store?If you do support multiple file formats, how much categorization, indexing and metadata can the CMS apply to those files. Or, alternatively, are there third-party add-ons which can accomplish such tasks.


Page 24 of 151

Collection

Acquisition


Please give an overview of your Web-based form system for content input.Do you enable rich HTML or XML editing within the fields on your Web-based forms?





Can your forms represent hierarchical relationships?Can authors create content while they're not connected and then submit it later?


Can authors view a revision and workflow history for their work?Can authors perform a spelling check on their work?Describe the training expectations required for new content contributors.

With what acquisition tools does your product ship?With what third-party acquisition tools do you integrate?

Page 25 of 151

Collection

Conversion

Metadata




With what third-party conversion tools do you integrate?How does your product support on-the-fly conversion of text and media on a Web site?




Can you define mandatory and optional metatags?Can you pull metadata lists from other sources, such as a database or a flat file?

Can you write metadata lists to other external files and databases?Can you automatically bring up metadata lists or values for periodic expiration or review?

Page 26 of 151

Collection

Management Storage

Administration

Does your product tie into any accepted standards for metadata?Does your product support all types of metadata types in the repository and metadata fields in your collection forms?








Page 27 of 151

Management

Workflow


Can you do a global search and replace throughout the repository?Can you automatically verify and manage broken internal and external links?

What user roles and rights model do you use, and what tools do you provide for managing and manipulating them?

What's your approach to data synchronization and replication across multiple databases? At what level is synchronization managed and communicated?

What workflow tools does your product include?With what workflow tools does your product integrate? What support do you provide for the integration?



Do you support parallel as well as sequential workflows?

Page 28 of 151

Management

Integration






Can you view all content that's in a particular state for a particular user?Can you add comments at the end of each workflow stage?Do you maintain an audit trail for all workflow processes?Using your product, can you integrate e-mail into the workflow processes?Is there an administrative override to automated workflow processes?At what content level can you create workflows?


Page 29 of 151

Management

Version Control

Reporting


Do you follow any open standards for data access and data sharing?Is it possible to export the entire content of the repository to some standard format. This includes:* content of all topics* links (hypertext links, related topics, etc)* metadata* global taxonomies or topic maps* structural information (including topic hierarchy)

Can users check content into and out of your repository?Does your product save earlier versions of content that can be restored later if necessary?

What level of granularity is supported for checking content in and out?How is locking handled if content is checked out?Describe the different levels of granularity at which content can be rolled back to an earlier version. How do you support rollback of a complete site, an individual page, or a single content component?


Page 30 of 151

Management

Disaster recovery

Security








Do you support a hierarchical security model?Can your product help us enforce intellectual property rights and security permissions by controlling the capability to publish media?

Page 31 of 151

Management

Performance

Publishing Templating





Describe your overall approach to publication templating?What programming languages can be used to develop Web templates?Do you support developing templates for non-HTML publications?


Page 32 of 151

Publishing

Content deployment

Can your system process templates on demand, producing dynamic sites?

Can your system mix batch and on-demand processing to produce sites that are partly static and partly dynamic?




How is personalization accomplished in your templates?


How can your product be used to deploy database records to remote databases?

Describe or demonstrate a scenario illustrating how content is deployed from a staging server to a production server.



Can your product automatically deploy files referenced in a field?

Page 33 of 151

Publishing

Publication platforms


Personalization


Can you publish on a set schedule without manual intervention?

Can your system produce broadcast e-mail?Can your system create individualized e-mail messages?How can your system be used to produce print publications?

Can your system create content for proprietary electronic formats, such as Microsoft Help, Macromedia Director, or other CD-ROM platforms?

Can your system create downloadable documents in Portable Document Format (PDF) or other proprietary formats?

Does your product ship with any personalization tools?Does your product integrate with any third-party personalization tools?What kind of user interface do you provide for creating and modifying personalization rules?




Page 34 of 151

Publishing

Publication integrations

Media and asset management systems

OS User registriesERP systems

Catalog management systems. Surveys and questionnairesWeb access and security tools




Can your system perform collaborative filtering?Please outline the kinds of personalizations that are possible based on user profiles.





Customer relationship management systems

Page 35 of 151

Publishing

Data logging and mining tools

Decision tree tools

Event planning and registration toolsWebcasts and streaming technologies

Web UI

Web architecture



Bulletin board and threaded discussion systems

E-commerce and financial transactions systemsConversion systems for on-the-fly conversion of content (for example, from XML to HTML).

Custom database applications and custom programming objects.Web servers and Web application servers




Which Web servers are supported by your product?Does your product include a proprietary Web application server?With what Web application servers does your product integrate?

Page 36 of 151

Publishing

What databases can your system use?

How does your system facilitate or perform content caching?How does your system facilitate or perform database connection pooling?

How does your system facilitate or perform server load balancing?How does your system facilitate or perform user session management?Can your system leverage user-profile information stored in directory services? Is any custom development needed to implement this functionality?

List the LDAP servers with which your system can integrate.

Page 37 of 151

Content Management QuestionnaireSection Question Interwoven TeamSite

Business Profile

Customer Profiles

Version Upgrade Policy

Binding Agreements

References


How long have you been in the CM business and have been producing the proposed product. What kind of growth have you seen?

Interwoven was founded in 1995 and the first pure-play supplier of content management software. Interwoven TeamSite, Interwoven's flagship product, first shipped in 1997.


Corporate intranet customers include Agile, Airbus, Aon Corporation, Commonwealth of Massachusetts, Compaq Inline, Deere & Company, Oakland County, MI, St. Jude Medical, State of California. Success stories are available -- please contact your territory sales manager. Interwoven recently released TeamSite 5.5.2 and the majority of customers are planning upgrades to this version by the end of the year. Over 1000 installed base.


Interwoven averages one major release every 12-14 months. Interwoven averages between 2 to 3 minor “point” releases between major product releases. Whenever Interwoven releases a new version of software, it is generally available to its customers. Interwoven will provide a copy of same software to the customer at no additional charge so long as customer is enrolled in a Maintenance Services Program. Interwoven can also deliver new releases to customers electronically. Product release notes as well as updated documentation are available prior to new version release. Notes and documentation release dates are dependent on software version or upgrade type, but do precede the release of the software. Software updates and patches can be downloaded from the password protected customer download site, which may be assessed at http://support.interwoven.com/. Each customer staff member who is a registered support contact can set their e-mail preferences to be notified of new releases.


Interwoven committed to the satisfaction and delight of our customers. With respect to binding agreements and penalties, Interwoven prefers to evaluate each situation and negotiate accordingly. Please communicate with your territory sales manager the scope of the legal language Intel desires.


Intel - NGIP Next Generation Internet Program HP (Compaq) WW Intranet Sun - Intranet (MySales, Marketing Portal) Cisco - Cisco Connection Online, Technical Assistance Center, eLearning, eSales

Describe the general steps involved in an implementation of your product.

TeamSite implementations can be executed by Interwoven’s Client Services Organization (CSO) or an appropriate consulting partner. Interwoven offers several pre-packaged service offerings. The baseline services pack includes product installation, configuration, and setup of one “branch.”

Page 38 of 151

Typical Project

Sample Statement of Work (SOW) attached.

Development environmentTeamSite is developed using Java, C++, and COM.

What factors are necessary to ensure a successful deployment?

During our implementation, we explore your requirements in a Joint Application Development Session. Here we determine your organization’s content scenarios and determine success criteria. From this information, we develop our test plan and testing scenarios. From our testing scenarios, we develop test scripts. Our consultants have standard test checklists available to them. The technical consultants will run through the standard test checklist as well as run through your organization’s specific test scenario requirements. During our customer’s implementation, a certain amount of time will be devoted to validating the implementation. After the product has been implemented based on the customer’s requirements, the next phase in the implementation methodology is testing. We spend a significant amount of time making sure the customer’s needs have been met.


There are many factors that affect a TeamSite implementation. For example -- size of implementation, global implications, system architecture, and number of trained resources from the client organization. TeamSite installations typically take anywhere between 10-30 days.



There are many factors that determine the number of people required to implement Interwoven software. Typically, an Interwoven implementation is composed of 1-2 full-time Interwoven Architectural Consultant(s) or Consultants per initiative, a Senior Consultant as needed, and an Interwoven Consulting Manager for all project meetings. This is a small percentage of our consulting team. The customer is required to designate a Project Manager (typically 50% of a Full Time Employee) and a TeamSite Administrator (typically 25% of a Full Time Employee). During the first few weeks, we request that the Project Manager have a System Administrator available (for Network and Operating System configuration).


Interwoven has extensive hands-on experience in implementing the most advanced content infrastructure solutions in the most efficient manner. Our experience results from implementing over 1000 customers that vary in size and industry and working with dozens of technology partners. From our extensive domain expertise and proven methodologies, our consulting organization has pre-packaged our consulting services. We have our TeamSite Standard Pack implementation, which will provide your organization with the foundation for your content infrastructure system. We also have pre-defined extended implementation packs and add-on modules to enhance your system. The TeamSite Standard Pack implementation is the basic offering and is a required component before any add-on modules may be selected.


Our Professional Services would use of standard processes to tailor a program for Intel. These processes have the experience of Enterprise deployments within 44 of the Fortune 100 Companies.


Interwoven’s consulting services offers pre-packaged implementation and configuration packages, as well as rated consultants to specific engagements. Rate structures are dependent on the type of work required. Please contact your territory sales manager for current rates.


Page 39 of 151

Typical Project

Localization


TeamSite provides several access options -- Java, Perl, Visual Basic/COM, Web Services/SOAP, File System Interface, and Command Line Programs. TeamSite is a very flexible and modular architecture. The product is very configurable, from adding custom menu items to creating your own XML based templates. Our professional services team has used the programming interfaces to create hundreds of modular customizations that can perform operations that a handful of our hundreds of customers may need. Customers are allowed access to our Knowledge Base of common customizations. We have partnerships with many third-party vendors who have experience customizing TeamSite to work with their tools (for example foreign language translation).


TeamSite offers several application integration options -- Java OpenAPI, Perl, Visual Basic/COM, Web Services/SOAP, File System Interface, and Command Line Programs.


TeamSite Templating offers two basic templates with flexible creation and modification options -- Data Capture Templates and Presentation Templates. Data Capture Templates can be authored in XML or users can visually create Data Capture Templates in Macromedia’s Dreamweaver. Presentation templates can be authored in any Web authoring tool and can be visually created using Macromedia’s Dreamweaver. Additionally, TeamSite offers a Visual Template Builder within the TeamSite interface.


TeamSite allows the non-technical user to extend and integrate templates through the Visual Template Builder or any authoring tool, such as Dreamweaver or FrontPage.


TeamSite poses no restrictions on the automation of administrative functions. TeamSite's open, standards-based architecture and support for several languages (Java, Perl, SOAP, Visual Basic/COM) can enable this automation through integration with any tool.


TeamSite workflow enables the automation of any or all parts of the content lifecycle, from creation and acquisition to deployment into production.


TeamSite is fully internationalized (I18N) and supports content in any encoding schema, such as Unicode/UTF8. Many TeamSite installations have incorporated localization (L10N) as part of the workflow. Additionally, TeamSite's unique branching technology enables our customers to manage multiple initiatives from a single TeamSite server -- typically customers utilize branching to manage multiple language sites. Moreover, productized integration modules have been developed for integration with leading globalization management systems (GMS), including GlobalSight, Trados, eTranslate, and Idiom.


TeamSite provides side-by-side differencing tools for comparison between two pieces of content. TeamSite users can compare their original source content to localized content using this tool.


TeamSite manages all content in its native format, without the need for retrofit, including multiple selection images and other media.


http://www.compaq.de/produkte/workstation/?BV_SessionID=@@@@0171993920.1028306270@@@@&BV_EngineID=fadceiejkdhdbejcifcmicih.0


TeamSite can include a localization step as part of the workflow process. TeamSite integrates seamlessly with leading globalization management systems, including Trados, GlobalSight, SDL, Idiom, and eTranslate.

Page 40 of 151

Typical Project

TeamSite versions all content, at both the asset and whole site / project level.

Training


Technical Support

Can you version and track changes at the element level?Is there template functionality for sniffing the origin nation and redirecting?

TeamSite does not directly affect the live production site(s), though it fully supports personalization functionality in production. TeamSite resides in the development environment, managing all global content. The actual delivery of that content to specific end users based on origin nation is handled in production through an application server or personalization engine.


TeamSite is currently localized in four languages -- English, French, German, and Japanese. Future language support include Spanish, Simplified Chinese, and Korean.

Please provide an overview of the training that you provide.

Interwoven recognizes that the purchase of software is only part of an overall strategy for a definitive enterprise content management implementation. Education and training also has a key role to play in both the successful implementation and ongoing optimization of such a purchase. At Interwoven, we have developed a reputation for providing quality instruction at all levels - from end user to system administrators and developers - and take pride in the professionalism and expertise of our instructors. Interwoven provides an extensive education offering in a variety of learning formats - lecture combined with hands-on lab exercises, simulated project studies, on-line learning, and Train-the-Trainer. Taught as a series or offered individually, courses are targeted to a wide audience ranging from content contributors and end users to administrators and developers and include such topics as how to use TeamSite, templating, workflow development, TeamSite architecture and deployments.


Training at Interwoven training centers are available on a regular basis. Courses can also be taught on-site or at local 3rd party training centers, typically with no more than 4-6 weeks notice, provided minimum hardware and software requirements can be met. TeamSite also offers Web-based training and Train-the-Trainer programs. Training costs at Interwoven centers are per student and start at $500. Training costs for on-site are per class and start at $2,000. Web-based training is per student and starts at $150.

A full slate of classes is regularly available at our Interwoven training centers located in Ascot (Berkshire), U.K.; Sunnyvale, CA; Bethesda, MD; Burlington, MA; and Chicago, IL. In addition, courses can also be taught either on-site at your offices or at local third party training centers. Additionally, Web-based training satisfied the need for a large volume of basic level training over a wide geographic distribution and with minimal cost.


Series and classes offered today include: § Project Administration series -- Using TeamSite, TeamSite Project Administration, TeamSite Workflow Fundamentals and Developing TeamSite Templates § System Administration series -- Using TeamSite, TeamSite System Administration (2 days - Windows or UNIX platform), TeamSite OpenDeploy (2 days - Windows or UNIX platform) § Developer series -- Using TeamSite, Developing TeamSite Templates, Advanced TeamSite Template Development, TeamSite Workflow Fundamentals§ Advanced classes -- TeamSite Workflow Developer (2 days), TeamSite DataDeploy (2 days)§ Specialty classes -- Introduction to Interwoven MetaTagger, MetaTagger Administration; Introduction to Interwoven TeamXML, TeamXML Administration

Page 41 of 151

Typical Project

Interwoven typically provided Interwoven product support.



Interwoven offers two technical support options, Standard Care and Premium Care. Interwoven has 50 support staff worldwide with additional Engineering staff located in North America. Interwoven offers seamless support for the global enterprise. All of its centers are interlinked with the communication tools and our escalation process to ensure that the appropriate resources are applied within the shortest time possible. Interwoven’s support structure and rapid escalation process ensures expertise is close at hand and effective for quick resolution of the problem. Management escalation can take place at any point in the case cycle. Finally Interwoven has direct and rapid technical escalation in the core engineering team to clear the most stubborn issues.

Do you provide support, or do you work with any partners?What's the geographic coverage of support, and at what hours is it available?

Interwoven maintains support centers through the Americas, Europe, and Asia-Pacific. The Standard Care Service Window is open Monday through Friday (excluding major holidays) between 5:00 a.m. and 5:00 p.m. Pacific Time. The Premium Care Service Window is open twenty-four hours a day, seven days a week, including holidays.

Interwoven offers support in the following languages -- English, Mandarin, Japanese, German, Dutch, Spanish, French.

What's the guaranteed response time for a support request?

For Standard Care, once a Case has been received, a Response will be issued within two business hours unless the Case has been submitted via email or the Web. In that event, a Response will be returned within two business days. A Question will receive a Response within two business days from the receipt of the request. For Premium Care, once a Case has been received, a Response will be issued within one business hour, unless the Case has been submitted via email or the Web. In that event, a Response will be returned within one business day. A Question will receive a Response within one business day from the receipt of the request.


Standard Care Customers are entitled to two Internal Technical Representatives who may contact the Interwoven Technical Support Organization (TSO). A Case may be reported by telephone, e-mail or via the TSO Web site. Premium Care Customers are entitled to four Internal Technical Representatives who may contact the Interwoven Technical Support Organization (TSO). A Case may be reported by telephone, pager, e-mail or via the TSO Web site.


For non-urgent technical question, Interwoven offers a support Web site (http://support.interwoven.com), where customers can access and track their support cases, download new releases and patches and get information about upcoming user forums. These services are available to customers at each of the support levels.


Support calls received (including email requests) are logged into an incident reporting system that issues and maintains a trouble ticket. Trouble tickets are updated in an ongoing manner and can be viewed on the support Web site. Typically, Tech Support identifies new product issues via telephone and or e-mail request from a client, and then opens a case. Once a case has been opened, Tech Support issues and updates a “Trouble Ticket" for that case. Customers may monitor the status of their case by viewing the Support Web site. Recognizing that each case is different, Tech Support categorizes each case according to its origin, and determines whether the issue is due to a product bug, product configuration/enhancement variable, or is merely a “how to” question. Once the nature of problem has been determined, Tech Support works to provide a resolution, which may include; an answer to the clients question, configuration recommendations, as well as temporary or permanent work around a bug issue. Some cases may be escalated to Engineering for product enhancement, review, or modification. All product enhancement requests that have been received by Tech Support are recorded and are appropriately distributed.

Page 42 of 151

Typical Project

Provisions can be negotiated to the satisfaction of both parties during the contract phase.

Support covers all Interwoven software products.

DeploymentTeamSite runs on Sun Solaris, MS Windows NT/2000, and IBM AIX.



TeamSite's maintenance is renewed on an annual basis. Our list price for standard software maintenance is 18% (annually) of the net price of the software. Our list price for premium software maintenance is 25% (annually) of the net price of the software.


Customers pay annual maintenance fees for Standard or Premium Care. Additionally, whenever Interwoven releases a new version of software, it is generally available to its customers. Interwoven will provide a copy of same software to the customer at no additional charge so long as customer is enrolled in a Maintenance Services Program.



What operating systems does your product run on?What operating systems are required on the client machines for the database client and authoring tools? Describe any client-side software needed to use the system.

Supported Client Platforms:Microsoft Windows 9X, Windows NT, Windows 2000Sun Solaris 2.6, Solaris 7 (32-bit), Solaris 8 (32-bit)Macintosh 7.5 and above

Interwoven TeamSite Front-Office Support:Microsoft Office 2000, Word 97, Microsoft Windows Explorer, Adobe GoLive 5.0, Macromedia Dreamweaver 3.0 and 4.0

WorkflowBuilder Support:Microsoft Windows 9X, Windows NT, Windows 2000


Browser Support:Netscape 4.7x+, Internet Explorer 4.x, 5.0+, 6.0+


Typically, TeamSite requires a systems administrator. Administrators should typically be familiar with production servers, basic Solaris, Windows, or AIX operations, and regular expression syntax.


TeamSite is fully accessible through the browser-based user interface, regardless of location. TeamSite's MultiStore repositories allow for up to 8 distributed repositories for a single TeamSite instance.


Because TeamSite generally houses a business' critical enterprise content, TeamSite installations are inside the firewall. TeamSite resides entirely in the development environment.


Our consulting service organization will build a plan and deployment scenario based upon our experience with 44 of the Fortune 100 companies

Page 43 of 151

Collection

TeamSite offers a WYSIWYG editing tool directly in the TeamSite user interface.


Out-of-the-box, Interwoven’s product set supports all content authoring tools without exception. Supported authoring tools include, but are not limited to: DreamWeaver, FrontPage, Adobe Go-Live, Notepad, MS Word, MS Project, Visio, Robohelp, and Photoshop. Each contributor can use the authoring tools with which he or she is familiar.


TeamSite Front-Office provides business users with an easy-to-use interface for creating and publishing content directly to TeamSite from Microsoft Office applications, Windows Explorer, Dreamweaver, GoLive, and other common desktop applications.


TeamSite supports all content in its native format, without the need for retrofit. There are no restrictions to the type of content supported -- TeamSite also manages code. The Interwoven product set supports all types of content out-of-the-box including, but not limited to: XML, XSL, HTML, WML, XHTML, WAV, GIF, JPEG, ASP, JSP, JHTML, MP3, MOV, PDF, DOC, XLS, PPT, and CSS.


Interwoven supports metadata of all content stored in the Content Management system. Metadata is entirely customer-defined and supports attributes such as keywords, content launch dates, content expiration dates, author information, and other customer-described attributes. Metadata is stored as XML. Metadata can be captured during content creation through Interwoven's data capture form. Metadata capture can be made mandatory or optional with optional field level validation. MetaTagger is Interwoven's content intelligence software. It allows our clients to automatically or semi-automatically classify and add metadata to all asset types based on pre-defined taxonomies. MetaTagger can tag content automatically at the time content is submitted into TeamSite, or at anytime during the workflow process. MetaTagger allows businesses to evaluate, classify, summarize, and apply rich business-driven metadata to content, making it for portals, search, syndication, and custom applications.


Interwoven offers an optional product called OpenTransform for content conversion. OpenTransform is a world-class rendering server-side technology that transforms and renders some 185 proprietary file formats into open, extensible formats, such as XML and MS Word. OpenTransform can transform documents authored using the office product suites from Microsoft, Lotus, Corel, and Sun Microsystems and other popular applications included Acrobat, FrameMaker, FrameMaker+SGML, Quark, AutoCAD, Photoshop, Illustrator, PageMaker, and Visio.


TeamSite supports all industry-standard (i.e. DreamWeaver, FrontPage, Homesite, Adobe Go-Live, Notepad, MS Word, etc.) authoring tools. New contributors accelerate down the learning curve because they are not forced to learn a new proprietary authoring tool. TeamSite's file system interface supports ALL editing tools - no exception. Additionally, TeamSite Templating allows non-technical content contributors an easy-to-use authoring environment that enables them to simply “fill in the blanks” using a forms-based interface. TeamSite Templating gives users the ability to create structured content as XML, which allows for the re-purposing of content across multiple publishing scenarios. Moreover, TeamSite Front-Office provides business users with an easy-to-use interface for creating and publishing content directly to TeamSite from Microsoft Office applications, Windows Explorer, and other common desktop applications.


TeamSite Templating is an XML-based publishing solution that empowers all members of an enterprise to contribute structured content to the Web through easy-to-use, easy-to-create templates. TeamSite is built upon the concept of the separation of content from presentation. Interwoven’s next-generation XML architecture enables organizations to capture XML content and publish to multiple Web applications.


Page 44 of 151

Collection

TeamSite templates are completely customizable based on user permissions.

TeamSite users can link to images and other media directly will completing the template.

TeamSite templates can be created from a DTD and/or database schema.

TeamSite templates can be additionally extended and modified through HTML and other programming.

TeamSite allows for the automatic call of spell checking applications anywhere in the workflow.

Typically, one day of "Using TeamSite" training is efficient for new content contributors.

AcquisitionTeamSite can integrate with any and all acquisition tools.

Conversion






TeamSite Templating fully supports hierarchical relationships. TeamSite also supports nested templates.


TeamSite authors can create using their authoring tool of choice, without the need to be logged into TeamSite.


Through virtualization, TeamSite enables the production environment to be "virtualized" in a user specific workarea so that changes to the website can be viewed in context before the change is sent through workflow for approval and deployment into production. This is more than just a "preview" of what the site would look like - it is a "virtualized" working website in development that enables all changes to be viewed and tested prior to the workflow approval process. QA is pushed much earlier in the process so mistakes can be corrected earlier.

Can authors view a revision and workflow history for their work?

TeamSite allows users to establish audit trails by viewing the full revision history of any file. The History command will display the state of a file at each time that it was submitted to the staging area, including statistics such as the time and date it was modified and who modified it.

Can authors perform a spelling check on their work?Describe the training expectations required for new content contributors.

With what acquisition tools does your product ship?With what third-party acquisition tools do you integrate?

TeamSite's open, standards-based architecture supports integration to all acquisition tools. TeamSite offers several integration options -- Java, Perl, Visual Basic/COM, Web Services/SOAP, File System Interface, and Command Line Programs.


Existing content can be migrated into TeamSite with an operation as simple as a drag and drop command.


TeamSite's hybrid architecture enables access to all content, regardless of whether it resides in a database, file system, or object repository. Customer content can be in any form or type including database, file system, metadata and object content (e.g. XML). TeamSite also manages and accesses content in other native sources, such as a shared file system, direct database integration, digital asset stores, object storage systems, Documentum, FileNet, Lotus Notes, and hundreds of other environments.

Page 45 of 151

Collection

Metadata

Metadata capture can be made mandatory or optional with optional field level validation.

TeamSite supports the import of metadata from other sources.

Metadata can be deployed to external files and databases through OpenDeploy.




TeamSite's open, standards-based architecture supports integration to all conversion tools. TeamSite offers several integration options -- Java, Perl, Visual Basic/COM, Web Services/SOAP, File System Interface, and Command Line Programs.


TeamSite fully supports on-the-fly conversion of text and media in production. Please note that TeamSite resides entirely in the development environment, supporting on-the-fly functionality in production. TeamSite manages dynamic content and can integrate with all application servers and personalization engines.


Interwoven supports metadata of all content stored in the Content Management system. Metadata is entirely customer-defined and supports attributes such as keywords, content launch dates, content expiration dates, author information, and other customer-described attributes. Metadata is stored as XML. Additionally, this metadata can automatically or on demand be replicated into any ODBC/JDBC compliant database. TeamSite persists its metadata framework (locking state, workflow state, creation dates, modification times, etc.) as a backing store on the file system.


Interwoven MetaTagger automates the process of applying complete and consistent metadata to enterprise content assets. Based on industry-standard or custom controlled vocabularies, MetaTagger suggests appropriate metadata for content assets that can then be stored, versioned, managed, and deployed using TeamSite. With MetaTagger, you can achieve superior results in run-time search, personalization, syndication and portal applications.


Existing metadata can be brought into TeamSite, allowing for modification by TeamSite administrators through the metadata capture form.

Can you define mandatory and optional metatags?Can you pull metadata lists from other sources, such as a database or a flat file?

Can you write metadata lists to other external files and databases?Can you automatically bring up metadata lists or values for periodic expiration or review?

Automatic bring up of metadata lists can be made mandatory in the workflow process. Workflow can also dictate processes based on expiration and/or review dates.


TeamSite captures metadata and stores it as XML. This metadata can be kept in its original format or can be transformed into RDF or any other format. The types of metadata fields captured is completely configurable so you could start with a well-known standard like Dublin Core and add your own custom elements.


Interwoven supports metadata of all content stored in the Content Management system. Metadata is entirely customer-defined and supports attributes such as keywords, content launch dates, content expiration dates, author information, and other customer-described attributes. Metadata is stored as XML.

Page 46 of 151

Management Storage

Administration


TeamSite stores customer content in a highly scalable object repository. The customer content can be in any form or type including database, file system, metadata and object content (e.g. XML). The object repository maintains the content structure and tracks the change of all content. It manages many other core CM capabilities such as workflow / business process, versioning, metadata, search and testing etc. The customer content is preserved as its native format in the repository. TeamSite also manages and accesses content in other native sources, such as a shared file system, direct database integration, digital asset stores, object storage systems, Documentum, FileNet, Lotus Notes, and hundreds of other environments. TeamSite manages all content in its native format, requiring no retrofitting. TeamSite persists its metadata framework (locking state, workflow state, creation dates, modification times, etc.) as a backing store on the file system.


Content relationships can be defined via metadata and organized via the file system structure using branches, workareas, and folders.


TeamSite is fully internationalized (I18N) and supports content in any encoding schema, such as Unicode/UTF8.


TeamSite poses no restrictions on the creation and number of DTDs or schemas, which are fully supported in the system.


Interwoven provides link checking via the SCE tab, where each content owner can easily check for broken links within a specific page through TeamSite’s integrated link checker. Additionally, TeamSite allows for the automatic call of link checking applications anywhere in the workflow.


TeamSite has its own integrated metadata search. There are no restrictions as to the type(s) of search engine(s) a site might want to use. Many TeamSite installations have integrated industry standard search engines, such as Verity and Inktomi, into the TeamSite environment. TeamSite has custom scripts that call the search engine to automatically update the search index, so that information is immediately registered with the engine and searchable. Additionally, users can search TeamSite just like they search their personal hard drive. Windows users can simply click "start->find->files & folders", point the search at their TeamSite mount, and run their keyword query. And since they’re using the Windows search mechanism, they can scope their search based on specific file types, size, modified dates, etc. They can click on any of the search results and start editing.

Page 47 of 151

Management

Workflow

Workflows can be configured for automatic triggering based on TeamSite events.


TeamSite is fundamentally architected to enable non-technical business users to manage their own content. TeamSite provides an intuitive, browser-based user interface for non-technical users, utilizing a file system structure, which resembles Windows Explorer. Additionally, TeamSite workflow guides content from creation to deployment, enabling pre-defined processes for non-technical users. Moreover, non-technical users can create content using TeamSite Templating's easy-to-use forms or through their authoring tools of choice, including a tight integration with Microsoft Office applications through TeamSite Front-Office.


TeamSite provides an administrator's interface through the browser, where administrators can configure workflows, add and delete users, schedule deployments, etc. Additionally, TeamSite offers a visual workflow builder, allowing administrators to create complex workflows with simple drag and drop techniques.


TeamSite allows for the automatic call of global search and replace applications anywhere in the workflow. TeamSite offer several application integration options -- Java, Perl, Visual Basic/COM, File System Interface, Command Line Programs, and Web Services/SOAP.

Can you automatically verify and manage broken internal and external links?



Access to TeamSite and the content TeamSite is managing can easily be controlled through OS Security, LDAP, and/or Active Directory. Additionally, TeamSite supports secure user roles, which allow different levels of access and responsibility within TeamSite, to include content submission, review and approval of Web content, and the eventual deployment of that content to the production Web site.


DataDeploy enables the synchronization of XML content and metadata from TeamSite to industry-standard relational databases. This gives TeamSite users access to up-to-date database content, and allows enterprises to distribute content to run-time repositories of industry-leading e-business applications.

What workflow tools does your product include?

TeamSite WorkflowBuilder provides a rich graphical user interface that enables users to visually design complex workflows. Users can simply drag and drop task modules and connect them with the appropriate transition objects to form the desired workflows.


TeamSite's open, standards-based architecture supports integration to workflow tools. TeamSite offer several application integration options -- Java, Perl, Visual Basic/COM, File System Interface, Command Line Programs, and Web Services/SOAP.



User roles relative to workflows can be configured using the WorkflowBuilder or Command Line Programs.

Page 48 of 151

Management

Comments can be added at each workflow stage.

Workflows can be created at the asset level.

Integration


TeamSite supports both simple (standard create-approval-submittal) and complex (multiple approvals, parallel) workflows. A number of standard workflows come out-of-the-box to be used as a starting point for more complex workflows to be built from.


TeamSite workflow can manage any process that Intel has in place or would like to have in place. Workflow capabilities allow you to manage the various tasks that guide the development of content from creation through final publication. The TeamSite workflow engine is a general workflow configuration that can be used repeatedly. Each workflow model describes a process, which may include user tasks and a wide variety of automated tasks.


TeamSite workflows allows for the incorporation of business rules to support the routing process. TeamSite poses no restrictions on workflow functionality.


Workflows can be created or modified through the WorkflowBuilder. Users can simply drag and drop task modules and connect them with the appropriate transition objects to form the desired workflows.


TeamSite workflows guide the entire lifecycle of content, from creation to approval or eventual deployment into production.


Because TeamSite is fully accessible through the browser-based user interface for authorized users, there are no restrictions as to the user base. Many TeamSite installations use external providers, such as localization firms, creative agencies, etc., as part of the workflow process.


TeamSite's Global Report Center can generate custom reports for TeamSite administrators, including content status based on user.

Can you add comments at the end of each workflow stage?Do you maintain an audit trail for all workflow processes?

TeamSite maintains an audit trail for all system events, including workflow processes. TeamSite's Global Report Center can generate custom reports based on TeamSite events.


The TeamSite workflow engine can notify users of tasks via e-mail and through the task list in the user GUI interface. If other types of notification are needed, the workflow process has the ability to call out to external programs or applications.


TeamSite users with the appropriate permissions have the ability to by-pass workflow for specific content items.



TeamSite can access any ODBC/JDBC compliant databases, including but not limited to Oracle, IBM DB2, MS SQL Server, Informix, and Sybase. Additionally, DataDeploy enables the synchronization of XML content and metadata from TeamSite to industry-standard relational databases. This gives TeamSite users access to up-to-date database content, and allows enterprises to distribute content to run-time repositories of industry-leading e-business applications.


TeamSite supports the automatic launch of 3rd party of applications anywhere in the workflow. TeamSite offers several application integration options -- Java, Perl, Visual Basic/COM, Command Line Programs, File System Interface, and Web Services/SOAP.

Page 49 of 151

Management

More information is needed to address the question. We look forward to discussing this in greater detail.

Version Control

Content is checked in and out at the asset level.


TeamSite is founded on an open, standards-based architecture. Our products are, of course, based on core standards such as HTTP, URLs, XML, and SOAP. Interwoven is also stepping up to our responsibility as the industry leader to ensure that the new standards affecting all the customers and vendors in the content infrastructure industry are developed in an open, consensus-based process. In order to fulfill that responsibility, we sponsor and participate in the globally respected standards bodies including the World Wide Web Consortium (W3C), the Organization for the Advancement of Structured Information Standards (OASIS), the IDEAlliance, and the Internet Engineering Task Force (IETF). Our staff not only participate in the activities of these bodies, we are frequently the leaders of the groups or the editors of the specifications.


Can users check content into and out of your repository?

TeamSite provides for check-in/check-out of all content. Checked out content is designated through the TeamSite user interface.


TeamSite versions all content, at both the asset and whole site level. TeamSite users can roll back to previous versions at any time.

What level of granularity is supported for checking content in and out?How is locking handled if content is checked out?

TeamSite supports concurrent development with three locking models. One of them prevents users from working on the same content at the same time. The next type is where contributors are notified of status, but are allowed to still work on files that are checked out. TeamSite has one more locking model to support parallel development of files. Essentially this model allows for multiple contributors to work on a file while maintaining a lock on the submission of the file. This allows for the contributors to push content to staging in a specific set of steps to maintain the premise of one file/version in the Staging area. Each contributor looking to submit is presented with a merge tool, if another person has modified the file before them. The merge tool is a three pane, source code level tool that allows the user to see the original file, the version submitted last, and the version they are attempting to submit. Changes are merged and the file is submitted, completing the parallel paths of development by bringing the separate paths together.


Because TeamSite versions all content, at both the asset and whole site level, roll back to previous versions can be at those same levels.

Page 50 of 151

Management

Reporting

TeamSite poses no restrictions on the generation of site maps with 3rd party tools.

Disaster recovery

Security


There are 3 comparison tools: a) Visual Differencing- provides side-by-side comparison of any two files. b) Source Differencing- provides a line-by-line comparison of the source of any page. c) Merging- in the optional write locking model, administrators can compare 3 files- two different versions from two different workareas as well as a comparison with the staging area version.


TeamSite keeps a real-time log of every event that occurs within the system. This log can be used to track the development of files, the activities of users, or the development of the site as a whole. It can also be used to establish ISO 9000 compliance, or as a reference for customizing and fine-tuning TeamSite. Events that appear in the log can be used as triggers for custom scripts.


TeamSite's analytics are provided through the Global Report Center. The Global Report Center provides a tool for business users to determine all information relevant to the development and creation of all types of content, process workflows, and content deployment to production systems. Global Report Center is a fully integrated HTML page running in the browser-based client environment. It interfaces into a TeamSite log history database, or can be extended to interface into any RDBMS. It maintains a log of all content, assignments, deployments, submissions and changes by individuals. The Global Report Centers reports can be forwarded to interested users via email, or the graphical user interface can be restricted to allow only certain individuals, based on their user status, to access this functionality.



Because TeamSite versions all content, at both the asset and whole site level, content archiving is fully supported for previous versions. Content can be archived in TeamSite's MultiStore repositories or downloaded via a 3rd archiving solution. Additionally, TeamSite recommends the use of 3rd party backup solutions for disaster recovery.


Interwoven TeamSite is a best-of-breed product that integrates seamlessly with our customers' specific infrastructures, including such technologies as application servers, databases, personalization engines, etc. Therefore, because these configurations vary by customer, there exist many external factors independent of TeamSite that affect such metrics as MTBF and MTTR. Please coordinate with your Territory Sales Manager for specific examples.


TeamSite is architected for high performance and scalability with its advanced repository. TeamSite's open, standards-based architecture enables high reliability by allowing for integration with Intel's existing and future infrastructures.


User authentication can be accomplished in a number of different ways: users can be authenticated through standard OS permissions (i.e., Solaris or NT), users can be authenticated through LDAP, and users can be authenticated through Windows active directory. Interwoven provides two facilities for customization and additional development: Interwoven’s OpenAPI supports customization and integration through Java, and Interwoven’s Content Services supports customization and integration through a SOAP protocol (i.e., XML over HTTP).

Page 51 of 151

Management

TeamSite fully supports a hierarchical security model.

The capability to publish media can be allowed or restricted through the user of secure user roles.

Performance

Publishing Templating

Do you support a hierarchical security model?Can your product help us enforce intellectual property rights and security permissions by controlling the capability to publish media?


Hard Disk Requirements: Sun Solaris: 650 MB for Interwoven TeamSite, plus 10x site size recommended; Microsoft Windows NT and 2000: 500 MB for Interwoven TeamSite, plus 10x site size recommended. A TeamSite Sizing Guide can be provided upon request -- please contact your territory sales manager.


Intel - NGIP Next Generation Internet Program HP (Compaq) WW Intranet Cisco-Cisco Connection Online, eLearning, Cisco Technical Assistance Center, Cisco eSales Sun - Intranet (MySales, CMO Portal) Internet (Sun.com- SunOne)


TeamSite is architected for high performance and scalability with its advanced repository. For example, Cisco Systems manages more than 50 million assets in TeamSite and has over 4000 licensed users. Charles Schwab and General Electric also have TeamSite installations with 1000’s of users. Additionally, an individual TeamSite server can manage multiple Web sites. The product does not inherently limit the number of Web sites that can be managed by an individual TeamSite server. In fact, Credit Suisse First Boston deploys content to 1100 servers for 3300 sites. TeamSite poses no restrictions on users or content, except for disk space limitations on servers.


Interwoven OpenDeploy is an enterprise-class content replication software that provides the secure, flexible, scalable solution your organization needs for cross-platform, transactional content transfer to multiple servers. With OpenDeploy, you can distribute content from development server to numerous production servers, distribute content to business partners, and schedule, automate and synchronize content deployment across the Internet.

Describe your overall approach to publication templating?

TeamSite Templating is an XML-based publishing solution that empowers all members of your organization to contribute to the Web through templates that are both easy to create and easy to use, helping reduce time-to-Web. By separating form from content, non-technical staff can capture and edit in a Word-like fashion while outputting to versatile XML. Templating is a key enabler of content re-use.


TeamSite Templating separates content from presentation with data capture templates and presentation templates. Data Capture Templates can be authored in XML or users can visually create Data Capture Templates in Macromedia’s Dreamweaver. Presentation templates can be authored in any Web authoring tool and can be visually created using Macromedia’s Dreamweaver.

Page 52 of 151

Publishing

TeamSite Templating supports batch processing to create static sites.

TeamSite Templating fully supports dynamic content, utilizing database-driven content.

Content deployment

Content type can be defined via metadata, enabling the assignment for default values for file directories.


TeamSite Templating presentation templates are used to render content into any output format, including, but not limited to: HTML, WML, JSP and ASP.




TeamSite offers a hybrid architecture that enables universal access to content, regardless of whether it resides in a database or file system. TeamSite Templating fully supports static and dynamic content.


Please note that TeamSite resides entirely in the development environment and poses no restrictions on dynamic content delivery in the production environment. TeamSite Templating supports the on-the-fly generation of pages with ANY application server. This can also be used in conjunction with personalization capability to provide a highly dynamic and tailored experience.


TeamSite Templating fully supports component and navigation templates. TeamSite Templating poses no restrictions on the type(s) of templates utilized.


TeamSite's open, standards-based architecture supports integration with outside systems. TeamSite offers several application integration options -- Java, Web Services/SOAP, Perl, Visual Basic/COM, File System Interface, and Command Line Programs.


TeamSite Templating works with all application servers and personalization engines to deliver on-the-fly generation of pages. TeamSite can handle all content, both static and dynamic, to support personalized pages. TeamSite virtualization capabilities allow users to preview content in the context of the entire site.






Interwoven OpenDeploy can deploy content from TeamSite's staging area into a production server automatically based on workflow, ad hoc through the OpenDeploy user interface, or through a scheduler.


OpenDeploy is completely flexible and can deploy specific content to specific targets based on workflow and metadata. Properties of content can be defined via metadata.


Page 53 of 151

Publishing

Publication platforms


Personalization


Interwoven OpenDeploy can deploy any content automatically based on pre-defined workflow or metadata.


Publish and expiration dates can be defined via metadata. OpenDeploy can deploy content into production based on metadata attributes.


Interwoven OpenDeploy contains a list scheduler which publishes automatically based on a pre-defined schedule.

Can your system produce broadcast e-mail?

TeamSite can manage content for delivery in any format. TeamSite manages all content in its native format, so no retrofitting is required.


The TeamSite workflow engine can notify users of tasks via e-mail and through the task list in the user GUI interface. Personalized comments can be included. If other types of notification are needed, the workflow process has the ability to call out to external programs or applications.

How can your system be used to produce print publications?

TeamSite can manage and prepare for delivery in any format, including for print. Because TeamSite manages all content in its native format, there are no restrictions on print output formats.

Interwoven offers an optional product called OpenSyndicate. Interwoven OpenSyndicate™ provides enterprise-class content syndication based on business rules driven by content metadata. OpenSyndicate enables global enterprise customers to deliver content to a network of partners, suppliers, distributors, and geographically located content subscribers. With OpenSyndicate, enterprise content owners will have better flexibility to deliver the right content to the right audience without loss of control.


TeamSite poses no restrictions on the type(s) of content it can manage. TeamSite manages all content in its native format, so absolutely no retrofitting is required.


Interwoven offers an optional product called OpenTransform for content conversion. OpenTransform is a world-class rendering server-side technology that transforms and renders some 185 proprietary file formats into open, extensible formats, such as XML and PDF.

Does your product ship with any personalization tools?

Interwoven remains agnostic relative to personalization tool vendors and does not ship with a specific personalization tool.


TeamSite's open, standards-based architecture supports integration to any 3rd party personalization tool. Interwoven also offers productized integrations modules with leading personalization engines, including ATG Dynamo, BEA WebLogic, and IBM WebSphere. Interwoven TeamTurbo streamlines enterprise deployment of Web properties by connecting TeamSite content management software and the leading personalization engines. Moreover, Interwoven’s Content Intelligence has been designed to improve the quality of personalization results. Through consistent, categorization-based tagging as part of the workflow, companies can be sure that their content does not disappear into the myriad of other content items. Through tagging content in a systematic, categorized manner, the ability to retrieve quality content can be massively increased.


TeamSite is accessible through the browser-based user interface. Interwoven TeamTurbo provides a standard set of integration points that enables enterprises to easily manage dynamic Web content such as applications, personalization rules and targeting rules. TeamSite capabilities - virtualization, parallel development, versioning and workflow - are enabled for dynamic content through Interwoven TeamTurbo.

Page 54 of 151

Publishing

This is handled through the personalization engine chosen.

TeamSite manages any kind of data, so this is dependent on the personalization engine chosen.

TeamSite poses no restrictions on the type of non-Web formats desired.




Publication integrationsPlease see below.




User profile data collection is handled through the personalization engine. User profile data is typically stored in a database, that TeamSite can access.

What forms of data are accessible to your personalization engine?What facilities do you have for producing individualized print publications or other non-Web personalizations?


Deliver of personalized information to end-users is handled through the application server or personalization engine. TeamSite fully supports all personalization initiatives from the development environment.



This is handled through the personalization engine chosen. TeamSite poses no restrictions on the kinds of personalization possible.



This is handled through the personalization engine chosen. TeamSite fully supports push campaigns from the development environment.



Interwoven offers an optional product called Content Provider for TeamSite. Content Provider for TeamSite provides TeamSite a means to data extraction from legacy content repositories. Out of the box, Content Provider can extract from NTFS, Lotus Notes, FileNet, IBM, and Documentum repositories. Content Provider’s APIs can be used to create other bridges to other repositories if needed.

Companies like Adobe, Artesia, Equilibrium, IBM, Media Bin, Screaming Media and Virage have all integrated Interwoven ECM into a wide range of complex media applications.

Page 55 of 151

Publishing

OS User registries

ERP systems

Catalog management systems.

Surveys and questionnaires TeamSite's open, standards-based architecture supports integration to all surveys and questionnaires.

Web access and security tools TeamSite has integrated with Netegrity SiteMinder.Data logging and mining tools

Decision tree tools TeamSite's open, standards-based architecture supports all decision tree tools.TeamSite's open, standards-based architecture supports download packaging tools.

TeamSite poses no restrictions on bulletin board and discussion systems in production.

Event planning and registration tools TeamSite poses no restrictions on event planning and registration tools in production.Webcasts and streaming technologies TeamSite poses no restrictions on Webcasts and streaming technologies in production.

TeamSite has integrated with custom database applications and programming objects.

Web UI


Dynamically generated sources can be made available to TeamSite for testing and staging processes. TeamSite includes a proxy service that handles all requests to an external ERP system. TeamSite supports all ERP systems, such as SAP, PeopleSoft, etc.


TeamSite has integrated with Siebel Systems CRM. TeamSite's open, standards-based architecture supports all CRM systems.TeamSite's open, standards-based architecture integrates with all catalog management system, including MS Commerce Server.

TeamSite's open, standards-based architecture poses no restrictions on data logging and mining tools in the production environment.


TeamSite Workflow provides the ability to be called from as well as call to other systems, including workflow systems. TeamSite Workflow can be through a Java API, command line tool, TeamSite GUI or URLs.



E-commerce and financial transactions systems

TeamSite's open, standards-based architecture supports all e-commerce and financial transaction systems.

Conversion systems for on-the-fly conversion of content (for example, from XML to HTML).

Interwoven offers OpenTransform, for the conversion of content. Additionally, TeamSite Templating is an XML-based solution that produces HTML output.

Custom database applications and custom programming objects.Web servers and Web application servers

TeamSite poses no restrictions on Web servers and Web application servers. OpenDeploy can deploy content to any Web server, such as IIS and Netscape. Additionally, TeamTurbo offers productized integrations to popular application servers, such as ATG Dynamo, IBM WebSphere, and BEA WebLogic.

Page 56 of 151

Publishing

Web architectureTeamSite supports all Web servers without exception.

No, TeamSite remains agnostic.


TeamSite poses no restrictions on content caching in production.

TeamSite poses no restrictions on load balancing in production.

TeamSite poses no restrictions on user session management in production.

TeamSite poses no restrictions on LDAP integration. Most large customer use the product with LDAP.


TeamSite poses no restrictions on searching and indexing in production. TeamSite's content intelligence has been developed to enhance search results. Additionally, Interwoven’s Content Intelligence has been designed to improve the quality of search engine results. Through consistent, taxonomy based tagging as part of the workflow, companies can be sure that their content does not disappear into the myriad of other content items. Through tagging the content in a systematic, taxonomy-based manner the ability to retrieve content can be massively increased.


TeamSite manages and deploys content in its native format, posing no restrictions on the type(s) of content desired.


TeamSite resides entirely in the development environment and poses no restrictions on session management, cookies, or caching in production.

Which Web servers are supported by your product?Does your product include a proprietary Web application server?With what Web application servers does your product integrate?

TeamSite integrates with any application server. Interwoven TeamTurbo provides productized integrations to popular application servers, including ATG Dynamo, BEA WebLogic, and IBM WebSphere.

TeamSite supports all JDBC compliant databases, including Oracle, IBM DB2, MS SQL Server, Informix, Sybase, etc.

How does your system facilitate or perform content caching?How does your system facilitate or perform database connection pooling?

Interwoven Applications interface through API's to standard database drivers If the specific database drivers support database connection pooling then TeamSite will support database pooling.

How does your system facilitate or perform server load balancing?How does your system facilitate or perform user session management?Can your system leverage user-profile information stored in directory services? Is any custom development needed to implement this functionality?

TeamSite fully supports and can leverage user-profile information stored in directory services. TeamSite authentication can be managed through OS security, LDAP, and/or Active Directory.


Page 57 of 151

Content Management QuestionnaireSection Question Documentum

Business Criteria Business Profile

Customer ProfilesNo response

Version Upgrade PolicyNo response

Binding AgreementsNo response

ReferencesNo response

Project/StaffNo response

Typical Project No response

No response

No response

No response

No response

No response

No response


How long have you been in the CM business and have been producing the proposed product. What kind of growth have you seen?

Documentum is a leading provider of content management solutions, with the proven experience and superior technology that uniquely qualifies us as content management experts. With offices around the world and serving more than 1,500 of the largest businesses, Documentum has established a tradition of excellence in meeting customer requirements since 1990. Documentum 4i WCM (Web Content Management) Edition extends Documentum's traditional document-management tools into the CM arena.





Describe the general steps involved in an implementation of your product.What factors are necessary to ensure a successful deployment?What's the typical time frame for a deployment and what can be done to minimize the time and effort required?



What professional services does your company provide?For a project such as ours, what sort of professional services do you recommend?


Page 58 of 151

Typical Project

No response

Not sure what is meant by this question. Need further clarification.

Localization


Documentum has engineers working simultaneously on a range of hardware and software to develop our products. Individual features can be developed on any of our supported platforms and "ported" to the others during our check-in and build process. The order of certification and release of platforms is then a function of priorities set by Product Management based on anticipated market demand. We write mainly in C++ and Java.


All Documentum functionality is available through our DFC (documentum foundation classes). This provides access through Java and COM. Customers can easily use SOAP to access our API, or build higher level functionality using our API and expose through SOAP. Using any of the standard development environments (e..g. IBM Web Services Development Kit) you can expose WSDL defintions of these APIs. These can then be deployed to UDDI registries. We have a number of customers using SOAP and Web Services with Documentum today. We are actively involved and founding member of many of the standards initiatives of web services (UDDI, OASIS, W3C).


Documentum comes with an extensive open API set. Documentum’s API supports the programming tools contained within Microsoft’s Visual Studio namely MS Visual Basic, MS C++ and MS J++. The API set is provided as both a set of customizable COM objects and a set of Java objects that opens virtually all sever functionality to the system developer.



Documentum Web Publisher provides a variety of methods for users to author content. For authors who need off-line access, Web Publisher allows existing content to be checked out and edited while not connected to the network. If so configured, the content would be edited in an authoring tool that the user is familiar with, such as Word or Excel for casual authors or Dreamweaver for web-knowledgeable authors. Changed or newly created content could be synchronized with the repository on the authors next network connection and could start a process workflow to be approved and published. For on-line users, Web Publisher also offers the ability to use our Template Editor. This provides a simple authoring interface that limits the capabilities of an author in changing “look and feel” of a web page, but allows him to edit or create new content as required.

Templates could be created in Notes for content authors and the resulting data file could be automatically inserted into the repository starting a process workflow. This would involve customization on the Notes side and could leverage Documentum’s eConnector for Notes as a way to import content to the repository from Notes. The benefit of this method would be the



Not sure what is meant by this question. Need further clarification.Regarding content aquisition, if your organization uses WebPublisher’s globalization functionality, then you can create, edit, and publish multiple translations of a Web site. The different translations of a content file all share the same name. When they appear together in a file list, they are differentiated by the language designated for each. For example, a category might have three content files called WinterWear.htm, one in German, one in English, and one in Japanese. The language is specified for each. The locale is the language and region of a given Web site. You determine to which Web site a translation is published by assigning the translation a locale. A fallback rule defines an alternate language that can be published to a Web site when a content file is not available in the site’s designated language. Fallback rules allow your organization to publish a Web site in its entirety, even if not all the content has yet been translated.

Page 59 of 151

Typical Project

No response


WebPublisher’s globalization functionality lets you create, edit, and publish multiple translations of a Web site. All the translations of a given content file are located in the same category in the EDIT PAGE tab and share the same name, but they are differentiated by the locales designated in their language properties. A locale is a combination of a language and a region or country. The locale determines the Web site to which the file is published. For example, a category might have three content files called WinterWear.htm, one in German, one in English, and one in Japanese. If viewing content files in the list of categories, you can filter the view to display all translations of a file or just one translation. You can also view all the translations available for a given file by clicking the Add/manage translations link in file details. WebPublisher displays the possible translations and displays a check mark next to actual translations. You can view a translation in read-only mode by clicking the translation’s language in the LANGUAGE USED column.

In the following figure, translations in German and French are possible but do not yet exist.How is translated content produced and synchronized with the source content?

You can create a translation either manually or via a workflow. In both cases, WebPublisher creates a new content file with the same name as the original content file. If you create a translation manually, you can populate the new file with the content from the original file, which would then be used to create the translation, or with imported content, usually content that has already been translated. If you create a translation via a workflow, the workflow populates the new file with the content from the original file and then sends the new file to the first user in the workflow. The user who performs the translation does so based on the content sent. Depending on the configuration of the workflow, WebPublisher might promote translations of a file only when all translations are ready. Or WebPublisher might promote each translation separately. The workflow might let you email a file that is to be translated to a translator outside your organization.


This question is a little vague. For content users authoring new web content using Documentum's WebPublisher Template Editor, authoring templates can be created that allow authors to select multiple images as well as other media sources such audio and video files.

If your organization uses WebPublisher’s Media Services, you can transform an image’s format or appearance without having to know how to use graphics software. Media Services lets you generate transformed renditions of graphics by providing you with transformation profiles. The transformation profile tells Media Services what transformation to perform. For example, a transformation profile could generate a thumbnail, optimize an image, or add a text overlay. You apply a transformation profile when performing the procedure for Adding a Rendition, this can be executed from within the WebPublisher Editor. For example, suppose you want to resize an image. You add a rendition and select the Resize profile. The profile prompts you for new height and width. You fill in the new dimensions, and Media Services creates the desired rendition.

Media Services includes a set of standard transformation profiles that cover common Please give a full example, with references and URLs, of a customer that has successfully used your system to create a global localization and translation solution.


Documentum partners with world class auto conversion tools to deliver first draft conversions that help reduce the time and effort necessary to generate localized versions of the web pages. Once generated, the localized versions can be routed through the appropriate review and approval process to ensure accurate and consistent messages are delivered to all the international sites.

Can you version and track changes at the element level?

Every time an object is versioned Documentum creates a new instance of that same object thus also versioning the attributes. WebPublisher keeps track of different versions of a file. Every time you save a file to the Docbase, WebPublisher saves the file as a new version and gives the file an incremental version number. The latest version is the version displayed in file lists. When you edit, review or process a file, you use the current version. WebPublisher also retains all previous versions. WebPublisher lets you view past versions, delete past versions, and reinstate a past version to make it the current version. If you reinstate a version, it becomes the version that is displayed in file lists and that is used in editing, reviewing, and processing.


Yes. WebPublisher allows administrators to select "Where Used" allowing the admin / developer to see all the content pages created from a particular template.

Page 60 of 151

Typical Project

TrainingNo response

No response

Is training held at your site or ours? No responseNo response

Technical SupportNo response

No response

No response

In what languages is support available? No response

No response

No response

No response

No response

No response

No response

No response

No response

Deployment


Documentum 4i eContent Server supports the UTF-8 encoding of the Unicode character set. If the RDBMS also is set to UTF-8, this will technically enable handling of content and metadata in any of the Unicode-supported languages. The eContent Server is able to handle characters and content in nearly any of the world’s common languages. To do this, the eContent Server has been 1) enhanced with internationalization features, and 2) enhanced to connect with databases that utilize a language encoding standard, called UTF-8, along with multi-byte and varying-width optimization. These capabilities, in combination with a distributed set of replicated eContent Servers, allow Documentum to provide an exclusive combination of globally distributed universal language support. Enhanced internationalization allows the eContent Server to process characters from nearly all languages. In addition, the eContent Server can be changed, or localized, to work with almost all other languages. Any eContent Server language can be provided by Documentum’s consultants, Documentum’s Partners, third-party organizations or individual customers.

Please provide an overview of the training that you provide.What's the availability and cost of training, and how frequently is it offered?


Please provide an overview of the technical support that you provide.Do you provide support, or do you work with any partners?What's the geographic coverage of support, and at what hours is it available?

What's the guaranteed response time for a support request?Is there a single point of contact for support, or do people need to know whom to call for what?

What kinds of self-help facilities do you provide?What guaranteed expertise is available on the first call, and what are the escalation procedures? How high in the technical organization can an issue be escalated?






Documentum operates on Solaris 2.6, Solaris 7 (2.7) & 8 (2.8), HP-UX 11.00, AIX 4.3.3, Linux Redhat 6.2 in the UNIX environment. Documentum operates on NT 4.0 SP5 & SP6a, Window 2000 w/ SP1 & SP2 in the Microsoft environment.


Documentum operates on NT 4.0 SP5 & SP6a, Window 2000 w/ SP1 & SP2 in the Microsoft environment.Documentum operates on Solaris 2.6, Solaris 7 (2.7) & 8 (2.8), HP-UX 11.00, AIX 4.3.3, Linux Redhat 6.2 in the UNIX environment.

Page 61 of 151

Typical Project

Depends on the size of the implementation.

Doesn't matter. Webcache targets can be deployed both within and outside the firewall.

Intel has not provided Documentum with this information.

Authoring

Collection

No response


Documentum supports MS IE 4.0.1 SP2 & IE 5.0 - 5.x & IE 6.0 or Navigator/Communicator 4.5 & 4.7 as web browser platforms.



The Documentum Server can be configured to have multiple server processes spread across several server boxes managing one repository for load balancing. In addition to load balancing, the Documentum Server supports distributed content to keep the content files closer to the area where it’s needed to reduce network traffic. The Documentum Server also supports replication from one repository to another repository. Each repository can have it’s own box and can share or have it’s own instance of the RDBMS. The Documentum system can store and manage all your content in one logical repository. The logical repository may actually be several Documentum repositories acting as a federation. This enables you to replicate content between repositories, search and workflow across repositories and share your business rules between repositories. Also, tables from other applications can be registered thereby making that content accessible to Documentum.




WebPublisher provides a forms-based web editor for creating web content. A With Documentum 4i, content contributors can choose their preferred desktop authoring tools and application suites, including Macromedia Dreamweaver, Microsoft Office, and Lotus Notes. Integration with popular Web authoring environments enables professional site designers and developers to easily create and maintain the Web site, navigation elements, and publishing templates.

Documentum FTP Integrators ™ enables content contribution from any Web authoring tool that supports ftp stan-dards. In addition, valuable contribution options are enabled through Documentum eConnectors ™ , which provide integrations with ERP applications. Contribution from across the distributed enterprise With the scalable Documentum 4I architecture, you effectively capture valuable content from thousands of global contributors located within and beyond your enterprise environment. Thissupport for large-scale Internet deployments presents a significant technical advantage over content management solutions designed for a department or small workgroup.


Documentum integrates with more than 200 different applications. Out of the box integrations including MS Office Suite, Dreamweaver, Homesite, MS Exchange, Exporer, Arbortext Epic, Xmetal, etc…


All content is stored in native format in the repository. Documentum will support all known file types, as well as having the ability to define new file types as they come into existance. A full list of over 300 files types are defined to Documentum out-of-the-box and can be provided if needed.


Documentum Content Intelligence Services (CIS) is an extension to the core Documentum Content Server that automates and controls the enrichment and organization of enterprise content based on powerful information extraction, conceptual classification, business analysis, and metadata and taxonomy management capabilities. In simpler terms, CIS takes unstructured content and adds attributes (or metadata) to turn it into intelligent, structured content to enable more accurate searching, easier navigation, and more effective personalization of enterprise content.


Page 62 of 151

Collection

Yes

Still researching and waiting for a response from engineering.

Yes.

Yes.

Yes.

Yes.


Documentum provides templates in the WebPublisher client to allow non-technical users with the ability to create HTML or XML content. Additionally, with over 200 out of the box integrations, users may continue to use the tools they are already familiar with, including MS Word. This gives uses a mix of web-based or thick-client based interfaces to complete thier work.Step 1: Author selects the desired category and authoring template.Step 2: Author enters a name, description, effective and expiration date.Step 3: Author enters desired text, selects the appropriate graphic and then previews his/her page to see how it will appear when published.Step 4: Using multiple xsl style sheets the author can preview their content to see how it will appear before publishing.


Documentum’s WebPublisher product allows non-technical users to author XML and HTML-based content using existing templates. The Web Developer creates standard XML templates that are related to both a rules file as well as an XSL style sheet. The templates are then associated to the appropriate categories within the system. Through a browser the user/content contributor selects the template from the category, the Web Content Editor automatically presents the user with the appropriate options based on the defined rules. The system automatically generates an HTML rendition of the content for publishing to the web.

The Web Content Editor allows the author to focus only on entering the appropriate content while the rules file and XSL define the structure and formatting of the content. This process allows for the standardization of the look and feel of the site as well as the reuse of the content by applying different publishing templates


Yes, WebPublisher templates provide a simple, non-technical interface for content authors to create and edit both HTMl and XML content.


Content can be setup to allow access and updating rights to only specific users or groups. Full security can be enforced or relaxed to allow these users and groups the rights to edit portions of your template or content. Security can be changed down to an object level, and these changes can happen automatically through the Lifecycle of the content.




Yes. HTML wrappers can be associated with authoring templates for controlling formatting and presentation.

Can your forms represent hierarchical relationships?Can authors create content while they're not connected and then submit it later?

Yes. Documentum handles offline content creation in a number of ways. Typical authors can be provided with templates in the repository to create or edit content. An author choosing to create new content would select a template. A copy of the template would be checked out and copied to his hard disk. An author editing existing content would select that content and check out the rendition of the content in his authoring tool format. For example, an author wanting to edit a web page component that was authored in Word would check out the Word doc file and could then edit it offline. When reconnected to the network, the author would check in his changed copy and continue the production process.


Can authors view a revision and workflow history for their work?Can authors perform a spelling check on their work?

Page 63 of 151

Collection

Acquisition


Conversion


When limited training is a requirement, we often suggest our Template Editor. This editor allows an author to enter or edit specific elements of a web page. It was built to be provided with little or no training. The rules that the template editor follows when presenting a data template to be filled out are configurable by template. Template Editor can greatly limit the variability in content entry so that you can ensure your site and page look & feel remain in your control. Template Editor does, however, require a network connection to the repository server.

With what acquisition tools does your product ship?

Documentum provides its own aquisition technology. Documentum's Content Aggregation Services allows companies to automatically collect content into their existing content management infrastructure from various external sources, including other repositories, file systems, databases, and Web sites. With Content Aggregation Services, companies can acquire content from many different sources and then, leveraging the Documentum enterprise content management platform, repurpose that information through portals, Web sites, and other content applications, to the benefit of their customers, partners, and employees. Some of the applications in which Documentum Content Aggregation Services can play a key role include:Employee portals that repurpose content from external sources to provide timely information about weather, traffic, cultural activities, and stock indexes-Multimedia Web sites that offer rich digital content from partners-Manufacturing portals that aggregate product specifications from suppliers-Airline sites offering hotel and rental car information-Financial institutions that display information on mortgages, mutual funds, commodities, and SEC filings

With what third-party acquisition tools do you integrate?How would we migrate our existing Web sites and other publications into your system?

Content may be imported into the repository using various import file options. These import methods can occur singularly, in groups, or in bulk and batch methods. Various UI's can be utilized to import content. Documentum has an ftp ntegrator that allows all ftp compliant applications to directly access our repository including: Dreamweaver, Homesite, etc. Our DocLoader product is available to facilitate the bulk importing of full content stores or from other content and web content management systems. All import methods mentioned are supported in both testing or production environments. As mentioned, we have the ability to easily import entire existing sites or content management systems. FTP Integrator allows tools like Dreamweaver or Homesite to push an entire site into Documentum at once. The site structure will be mirrored in Documentum. DocLoader is a tool that can enable the rapid and controlled bulkloading of any kind of content objects from legacy and external sources into a Documentum repository. Thousands of objects can be migrated in a single batch, and Documentum attributes can be automatically populated and defined during import. DocLoader can be used to populate the Documentum repository in an initial deployment, or to update content objects and attributes on an ongoing basis.


Documentum can readily import the content from diverse enterprise applications, as well as itself, directly into the content repository when required and export content components to external databases as needed. If needed, external database tables can be registered with Documentum and accessed through Documentum's ODBC Gateway.

Page 64 of 151

Collection


Metadata

Yes.

Yes. Documentum Administrator allows administrators to perform table joins etc…

Yes.


Media Services is a Server based product offering that enables companies to manage complex rich media assets for the Enterprise using a common content management platform.Features1. Automatic creation of thumbnails2. Automatic / Ad hoc creation of additional renditions on registration of media (transformations).3. Examples of transformations include:· transforming to a different format (i.e. .bmp to .gif)· resizing· cropping· text layering (adding a text field on top of an existing image)· flipping / rotating· graphic optimization4. Support for profiles that provide definition of transformation by format type.5. Audit trail of media transformations6. File formats supported through a Media Plug-in architecture 7. Support for streaming of audio and video files8. Rich Media exposed to production lifecycles and workflow.

Benefits1. One system to manage rich media, as well as web content, XML content and documents.2. Centralized creation – local presentation. Rich media can be made available to a wider audience in the organization.3. Media production can be subject to enterprise lifecycles and workflow.4. Media reuse and repurposing can be improved.5. Best of breed media plug-in technology to keep up to date with new file formats and capabilities.

With what third-party conversion tools do you integrate?How does your product support on-the-fly conversion of text and media on a Web site?

Web Publisher is flexible in how separate content components may be transformed into output files. Components, or layers, can be under independent control. Web Publisher provides the ability to have different authors create or edit their assigned “chunks” of content. Once the chunks are created, Web Publisher can do three different things with them: they can be published as is for an Application Server to build pages from, they can be immediately transformed within Documentum into a “final output format” which can be published to the Application/Web Server, or they can be transformed within Documentum at a later time (when publishing) to bind more current information to the content.

Documentum provides for central control of presentation and transformation templates. Related templates can be bundled into solution segments and managed together. Templates are under version control, including check-in/-out and the ability to reinstate previous versions. Site and page template bundles can be put through an approval process which would result in making approved templates available for users.

The In-Context Editor can be configured to give an editor or author a view of the content


Documentum Content Intelligence Services (CIS) is an extension to the core Documentum Content Server that automates and controls the enrichment and organization of enterprise content based on powerful information extraction, conceptual classification, business analysis, and metadata and taxonomy management capabilities. Unlike point solutions that focus on tagging or categorizing Web content only, CIS is fully integrated with the Documentum platform and enables rich tagging, and categorization for all of your content management initiatives, including enterprise document management, XML component management, and Web content management. In simpler terms, CIS takes unstructured content and adds attributes (or metadata) to turn it into intelligent, structured content to enable more accurate searching, easier navigation, and more effective personalization of enterprise content. Key Features · Information Extraction - Enhances productivity by extracting actionable metadata from new or existing content to enable effective and thorough auto-tagging, classification, and database population.· Conceptual Classification - Determines what content is “about” to enable richer associations and expand searchability.· Business Analysis - Automatically analyzes content to reflect your company’s specific business



Can you define mandatory and optional metatags?

Page 65 of 151

Collection

Yes.

Yes.

Yes.

This would be determined or limited by the underlying database.

Storage

Management



Metadata is stored in the RDBMS but is managed by the repository server. To access the metadata customers can use our APIs, our search technology, or our reporting technology. Documentum offers a number of published APIs for accessing content and metadata in the repository. One possible method of pulling metadata from the repository would be to write migration code. The code could provide the metadata and content to another content management system.

Search technology could also be used. Search results could include file lists, along with metadata information, and could be saved as files. These files could be used to load metadata into another content management system and assign it to the correct content.

Yet a third method would be to use Documentum’s Reporting Gateway. Reporting Gateway makes metadata in Documentum 4i available through ODBC to reporting tools such as Microsoft Excel, Access, Crystal Reports, and Business Objects. These tools could be used to capture metadata to provide to another content management tool if needed.


Does your product tie into any accepted standards for metadata?Does your product support all types of metadata types in the repository and metadata fields in your collection forms?


Metadata is stored in the RDBMS but is managed by the repository server. To access the metadata customers can use our APIs, our search technology, or our reporting technology.


One of the challenges in link management is to ensure that if an object is moved or renamed, all links to that object are not broken. The Documentum WCM solution provides this functionality through a level of indirection: all links in a document that refer to another object within the docbase will be replaced by a unique identifier that will remain constant even if the target of the link is moved or renamed. Link normalization significantly improves the mundane and error prone process of managing links. The time once spent on maintaining links can be utilized to build cutting edge sites.


Documentum 4i eContent Server supports the UTF-8 encoding of the Unicode character set. If the RDBMS also is set to UTF-8, this will technically enable handling of content and metadata in any of the Unicode-supported languages. The eContent Server is able to handle characters and content in nearly any of the world’s common languages. To do this, the eContent Server has been 1) enhanced with internationalization features, and 2) enhanced to connect with databases that utilize a language encoding standard, called UTF-8, along with multi-byte and varying-width optimization. These capabilities, in combination with a distributed set of replicated eContent Servers, allow Documentum to provide an exclusive combination of globally distributed universal language support. Enhanced internationalization allows the eContent Server to process characters from nearly all languages. In addition, the eContent Server can be changed, or localized, to work with almost all other languages. Any eContent Server language can be provided by Documentum’s consultants, Documentum’s Partners, third-party organizations or individual customers.

Page 66 of 151

Management

Administration

Yes.


XML ProcessingDocumentum processes XML documents at the time of import into the repository or at any later time. The processing of XML documents is configurable allowing users to specify a different set of actions for different types of XML documents. There are many operations an XML application can perform when processing an XML document, including validation, chunking, import of links, storage of components, metadata population, access control list (ACL) and lifecycle assignment, and extended processing. Particularly important are chunking and validation.The XML content validation is essential to ensure that the stored XML document is well formed to deliver on its ultimate promise — reusability. Documentum provides the native capability to validate XML documents during import into the repository. This process can validate the document against the DTD (Document Type Definition) or schema to verify the components, attributes, structure, and types and values used in the XML document as well as validate against specified data dictionaries.

Documentum keeps DTDs and schemas as objects in the repository, providing the same type Does your product have the capability to check the validity of links and media references that appear within text fields in the repository?

When capturing existing intra and inter page links upon content import the Document WCM solution provides a spider like process for verifying, importing, and attributing the linked files.



The client products provide a search interface that not only makes it easy for the beginner, but also for the advanced user. The intent of the search interfaces is to make construction of searches very easy, no matter if the query is simple or complex in nature. Search features such as proximity searching, phrase searching, “sounds like”, and “fuzzy logic” will be accessible by the click of a button or filling in a field. Users will not have to know the Verity ‘topic’ language to construct these kinds of searches (although this option will still be available for those that desire it). Searches can be performed against both metadata as well as content. Documentum security is enforced at all times when searching content within the Documentum repository.

Documentum’s 4i Content Personalization Server (CIS) is fully integrated with the WebPublisher content contribution client. CPS provides suggested metadata values to the user in real time. When published to webcache, these values can be pushed as metadata or imbedded HTML tags.



For administrators, the client interface is web-based. This is an exciting new interface that replaces the administration capabilities previously provided through our full client. The features included in the web-based administration tool are:

· User/Group Management -- create, modify, delete, change status (active/inactive, global/local), rename. This also includes import of existing LDAP user/group definitions provided lists are in the LDAP-compliant LDIF file format.· Format Management -- create, modify, delete· Template Management -- create, modify, delete· Location Objects -- create, modify, delete, move, validate· Server Config Objects -- view, create, modify, copy, delete· Docbase Config Objects -- view, modify· Output Devices -- create, modify, mark as default, delete· Methods -- create, modify, delete, run· Jobs (Agents) -- create, modify, delete, run, view, view log· Mount Points -- create, modify, delete, validate, move· Types -- create, modify, drop, display information, add/remove full text indexing

· Content Management (File stores, BLOB stores, Linked stores, external stores, distributed stores) -- create, modify,Can you do a global search and replace

throughout the repository?

Page 67 of 151

Management

Workflow

Yes.


One of the challenges in link management is to ensure that when objects are moved or renamed, all links to that object are not broken. The current solution provides this functionality through a level of indirection: all links in a document that refer to another object within the docbase are replaced by a unique identifier that will remain constant even if the target of the link is moved or renamed. Link normalization significantly improves the mundane and error prone process of managing links.


Documentum 4I offers a range of functionality that is dynamically tailored to match the roles and requirements of different users in the enterprise. Deployed using either standard Web browsers or desktop applications, the right capabilities are automatically made available based on user privileges. For content contributors, Documentum offers robust client functionality for creation, review, release, and control of business-critical content. For content consumers that will access and apply knowledge to accomplish business tasks, Documentum 4I includes a Web client that provides an easy-to-use portal. With Documentum’s client family, your knowledge workers have seamless access to the content they need, using the tool of their choice: a Web browser, a desktop application such as Microsoft Word, or even Microsoft Windows Explorer.


Documentum doesn’t limit how the DBMS manages its data. Documentum itself offers replication and data distribution. Replication is offered both for whole objects or just for the content contained in an object.


Documentum has inherent, server-based workflows that can be configured to support delegated content creation. Content can be authored in tools like MS Word, and rendered into flexible formats such as XML. XML can be intelligently authored via web-based authoring tools, either within our product UI's (User Interface's) or with third-party editing tools. Delegation can occur via manual or automated processes within Documentums workflow and lifecycle services. No programming is required to maintain connectivity or release levels with the workflow engine. The Documentum workflow engine has been integrated and included with the server since release 1.0 of the product. As a result, no effort is required to maintain release versions of the repository software with the workflow, and all workflow functionalities are completely available at all times.


The WfMC – The Workflow Management Coalition. The WfMC has defined a framework for the establishing a workflow standard. This framework includes five categories of interoperability and communication standards that will allow multiple workflow products to coexist and inter-operate within a user’s environment. Documentum participates as a member of the steering and technical committees. Our current workflow product has been developed in accordance with these WfMC standards. Documentum has been a member for 6 years.


In addition to the workflow engine, Documentum provides a life cycle manager to promote a document through its stages. For example, a document may be automatically promoted and moved to a new location as it passes from Draft to Approved to Released to Retired. At each phase, the security access to the document may be automatically changed to meet the access requirements of that stage. The lifecycle may be tied to the workflow manager to synchronize the actions on the document as it is promoted through the workflow.

Engagement Services is a multi-protocol server that extends process automation and workflow across trading networks beyond the firewall, and enables organizations accelerate inter-enterprise transactions to dramatically increase efficiency and strengthen strategic partnerships. This product extends the platform to enable a new breed of inter-enterprise applications making the supply chain a shared responsibility between the buyer, supplier and marketplace.The basic premise of B2B content management solutions can be categorized into four stages namely aggregation, B2B Exchanges (collaboration), publishing (syndication), and efficient content management.

Engagement Server enables the content aggregation process of the organizations allowing Please describe how your system handles the configuration of user roles for workflows.

WebPublisher provides workflow routing to promote and approve content out of the box. A developer or developers can define approval workflows for web content. These workflows can either be specific to individual departments or subset defined by Intel or there can be generic workflows that are resolved to individual user’s supervisors, etc. based on Documentum’s Alias set functionality.


Page 68 of 151

Management

Yes

Yes

Yes

Yes

Yes

Yes

Contributor, Coordinator and Administrator

Integration


Workflow capabilities, through the workflow manager, include:1. Creation of simple or complex workflows.2. Creation of workflow templates that may be reused and launched from the Web or from the desktop client.3. Use of conditional routing, so that tasks can automatically be forwarded according to business rules and document properties.4. Unattended tasks, which allows certain tasks execute automatically, rather than a manual user step.5. Reassignment tasks, which allows a task to be reassigned to a designated alternate in the event the original user is unavailable.6. Branching to sub-tasks.7. Routing to a group of users, in which either one member or all members are responsible for a task.8. Dynamic assignment of recipients upon the start of the workflow or at the start of a task.9. Ability to send a single document, folder or set of documents.10. Notification of task events, such as receipt of a task, completion of a task, overdue task, or schedule notification.11. Assignment of a proxy recipient when not available to perform tasks. (Desktop client feature).


Conditional routing can be done based on any attribute. Documentum's workflow engine even allows if then statements based on attribute values that can determine the routing of a specific package.


Workflows are treated as separate objects and can be checked-out, checked-in, versioned, have security applied to them. Documentum provides a graphical user interface with drag and drop capability.


Documentum's workflow engine can incorporate automated activities within a workflow that can launch any executable. For example:-rendering content to a different format such as PDF or HTML-promoting a document from one lifecycle state to another thus modifying attributes, changing location, security, etc...-publishing content-sending out notifications


Can you view all content that's in a particular state for a particular user?Can you add comments at the end of each workflow stage?Do you maintain an audit trail for all workflow processes?Using your product, can you integrate e-mail into the workflow processes?Is there an administrative override to automated workflow processes?At what content level can you create workflows?


The Documentum Foundation Class (DFC) is a robust interface layer within our server that allows web servers and client applications to dynamically access Repository content. The DFC is fully extensible and allows Application Servers and our Rightsite Servers to rapidly serve content and database information to Internet, Extranet and Intranet users as needed. DFC provides a common foundation for Documentum’s Client applications, Desktop Client and Developer Studio, as well interoperability for as-needed custom applications using COM and Java objects.

Web developers have a wide variety of options available to them today. There are multiple development platforms, as well as development tools. Documentum's Web Development Kit (WDK) has been developed to utilize the Java platform due to its maturity in the marketplace. A Microsoft version of this product will be developed upon the .NET platform once it is available.WDK leverages the investment in Java ServerPages (JSP). JSP is a server-side scripting environment that is used to create and run dynamic, interactive web applications. With JSP, you can combine HTML pages and script commands to create interactive web pages or powerful Web-based applications.Developers who wish to extend the Java classes

Page 69 of 151

Management

Version ControlYes.

Yes.

Yes

Reporting


Once file type of the external application is registered with the eContent Server, that particular application will automatically launch when a user cjeck out that file for editing or perhaps even viewing.


Documentum 4i provides an Open Data Base Connectivity (ODBC) gateway for interfacing with ODBC-compliant third party reporting tools like Crystal Reports. This feature enables Documentum customers to create custom reports against the Docbase RDBMS. Documentum provides connectivity with BEA Weblogic, ATG Dynamo and other J2EE compliant servers, either with our WebCache, which can publish content to http, application and commerce servers, and metadata to a JDBC compliant database, or with live connections to Documentum repositories using Documentum's JDBC driver.

Documentum’s Reporting Gateway. Reporting Gateway makes metadata in Documentum 4i available through ODBC to reporting tools such as Microsoft Excel, Access, Crystal Reports, and Business Objects. These tools could be used to capture metadata to provide to another content management tool if needed.


FtpIntegrator is an FTP integration to common web authoring tools. It has been certified against Dreamweaver, but should work with any authoring tool utilizing FTP such as FrontPage and HomeSite. It allows users working in Dreamweaver to seamlessly check-in and check-out objects from the Documentum repository. The user works with Dreamweaver in the same way that they are accustomed, however, behind the scenes Dreamweaver is synchronizing the Documentum repository through FTP.This integration allows for both the creation and modification of files as well as a bulk import directly into the Documentum system. It’s as easy as selecting the directory on the filesystem and selecting put in Dreamweaver. Behind the scenes the ftpIntegrator is creating all of the necessary objects within Documentum.The ftpIntegrator requires no client installation as it utilizes an FTP server.ftpIntegrator is a direct integration between the Documentum WebPublisher content repository and any Web authoring tool that supports file transfer protocol over a TCP/IP network. It allows users to use client applications, such as Macromedia Dreamweaver, Homesite and

Can users check content into and out of your repository?Does your product save earlier versions of content that can be restored later if necessary?


XML Documents can be automatically parsed, stored, and managed at configurable levels of granularity. These components are then easily reused across other content. Documentum is able to manage the relationships and links between components and version control at the defined component levels. These links can be both at a peer-to-peer as well as parent-child level.

How is locking handled if content is checked out?

For checkout transactions, the eCS writes the checkout lock to the RDBMS rather than using an RDBMS transaction. This approach is optimal for enterprise content management transactions because lock duration is typically in hours & days whereas RDBMS are in seconds to minutes.


Versioning and rollback. Web Publisher manages version control of content and components. For instance, version 2.1 may be currently published to your production web site, version 3.3 may be going through an approval workflow to be published as part of a package when approved, and version 4.0 may be being edited for the next release. Web Publisher makes these versions available for “diffing”, or viewing the changes. Previous versions of files may also be reinstated as current by users with appropriate rights. Web Publisher can also include multiple related files, for instance all files that comprise a single page, into a package called a change set. A change set may be routed through approval workflow, with the correct versions of final documents being published at the end. Change sets may also be rolled back. In addition, Web Publisher can retain snapshots of web sites, called editions. Previous editions may be quickly rolled back.Archiving. In addition to the previous rollback capabilities, Documentum 4i provides the ability to archive items. Archival can be based on any metadata and/or retirement dates subject to retention schedules. Archived files can be stored in other file storage, such as optical disk or tape. Metadata may be kept within the repository for archived files, so that they can still be


Page 70 of 151

Management

Investigating

Disaster recovery


Security

Yes.


Documentum 4i eContent Server’s auditing support allows you to initiate automatic auditing for any system event. When an audited system event occurs, eContent Server automatically generates the audit trail entry. Documentum provides a large set of system events. These events are associated with API methods, business policies, workflows, and jobs. For example, you can audit:· All occurrences of a particular event on a given object or given object type· All occurrences of a particular event in the Docbase, regardless of the object to which it occurs· All workflow-related events in the Docbase· All occurrences of a particular workflow event for all workflows started from a given process definition· All executions of a particular job· All events in the DocbaseAutomatic auditing is initiated through Documentum Administrator or using the Audit method. Applications can audit user-defined events. User-defined events are operations that you, as an application developer or system administrator, define as an event. If you want to audit user-defined events, the application must recognize when the event occurs and create the audit trail entry to record its occurrence. For example, suppose you want to track who connects to a repository. You can write an application that creates an audit trail entry whenever a user is authenticated successfully.Describe the workflow tracking reports

that your system can generate.All workflow activities, in fact, all content related activities, are individually maintained in the database for ease of analysis and reporting. Documentum provides a very comprehensive audit trail capability that can be tied to every operation performed on a docbase object. This includes any related business policy triggers, workflow state changes, attribute modifications and access entries. Several standard reports are available, and any desired report can be created with the Documentum Reporting Gateway and third party reporting tools such as Business Object, Crystal Reports, etc.



The eContent Server can be configured to have “server sets” which provide automatic failover if one should have problems. The eContent Server also supports Microsoft’s operating system clustering capability. With clustering, if any machine fails, rollover occurs at the operating system level to an active Windows machine. The eContent Server now supports clustering on both Microsoft NT and Windows 2000 operating systems.





Security within Documentum 4i is managed using the underlying operating system’s password control mechanism. This not only avoids the need to maintain passwords in multiple systems, but also allows use of operating system facilities to maintain passwords such as automatic password aging. Once a user has been authenticated and is logged in, Documentum then applies different levels of access to each content object, container or a combination of both. Access Control Lists (ACL’s) are then used to control who has access to which content asset. Unlike the common owner/group/world security model, ACL’s enable object security models to be defined and applied to content that reflect real world business requirements. The ACL can be applied on creation or can be applied manually. The ACLs can be re-used and inherited by sub classifications of content types. Every piece of unstructured content, whether text, XML, Office document, Rich Media Asset such as an audio or video stream or other digital asset has an ACL applied to it. The ACL is a powerful feature.

Documentum 4i allows multilevel system administration privileges to be defined for users. Do you support a hierarchical security model?

Page 71 of 151

Management

Documentum is in the process of adding this functionality.

PerformanceIntel's level of usage has not been provided.

Templating

Publishing

Yes

Yes

Yes




Scaling the WCM Edition:The WCM Edition allows a company to manage its Internet Web content and deliver it to the website as content and meta-data to ensure great performance and scalability. This software has several major components: Content Authoring, Site Delivery Services, and access software for dynamic content/attribute retrieval from Internet users. That is, it can be characterized typically by the hardware/software needed on either side of the Internet “firewall” and the software that connects them. These pieces are outlined below.

Management of the content going into the Website is accomplished by the Documentum WebPublisher application. In order to correctly size the WCM application, it is important to understand that this application is Web-based and uses the services of RightSite, the eContent Server, Autorender, and Content Personalization Services. Hence, for the most part, sizing and scaling users and content in a Webpublisher implementation is like sizing traditional Documentum applications. One difference is that Autorender, an optional piece of the 4i family, is a highly integrated into the WebPublisher application. The main service it provides is to automatically convert


Examples of Documentum’s scalability include Delta Airlines, currently taking 10 Million hits per day on its Delta.com site, Ford Motor Company, currently implementing a 156,000 user Intranet solution and Old Mutual, who are currently implementing a solution that was benchmarked to 101 Million objects, the largest Content Management benchmark ever undertaken anywhere in the world.

This benchmark report is included in the Appendix of this response The objective of the benchmark was to gather multi-user response time data on an extremely large docbase on a high end HP V-class system. In this test, 100,000,000 documents were loaded and 2,000 users/hour were run against this configuration. The test demonstrates first, that Documentum 4i can handle input rates that exceed even the most demanding customer loads. Secondly, it demonstrates that excellent response times can be achieved for thousands of users operating on this large docbase.


Documentum's ContentCaster includes a user interface to configure deployments, and it contains Transmitter and Tuner modules to handle the transmission and receipt of data. ContentCaster transmits the cached Web site directly to one or more production Web servers. Alternatively, it transmits the cached Web site to a traditional proxy server (for firewall protection) or a ContentCaster proxy, which caches the transmitted Web site. This improves transmission performance to remote production Web servers.


The Web Publisher Editor helps eliminate these delays by simplifying the Web content creation process. A "fill-in-the-blanks" form matches the content entered with a presentation template designed and controlled by the Web team. Separating the content from the presentation enables site designers to re-brand or re-purpose content across multiple sites. This enables Intel to dynamically assemble and deliver the same content to multiple sites, even if those sites have different screen layouts and navigation.


HTML, MS Word. Documentum also fully supports XML/XSLT based content templates that would provide the desired functionality. XSLT templates can utilize Java to provide computational capabilities, or other functionality that basic XSLT will not support.




Page 72 of 151

Publishing



Content deployment


Yes


While Web Publisher allows for content format and design to be combined where it makes sense (usually to import and manage an existing web site that will be decommissioned), we provide and promote the ability to separate content format, design, and business logic. For content to be authored in a third party authoring tool, like Microsoft Word or FrontPage, Web Publisher will provide the author an input template (if required) and format the output through a separate presentation template (if required). For XML-based content authored through our own Template Editor, three different templates are involved. First, the content data template is provided. This includes default information and will store the content that the author adds in an XML format. A second template is used to determine which data the author can edit, and the rules he has in editing. This template includes some business rules. A third template, or series of templates, will control the presentation of the content. In addition to these templates, Web Publisher also uses Workflow templates to provide your business logic to the authoring/approval/publishing process.




Question is a little vague, need further clarification. Metadata can be either manually or automatically tagged within Documentum. Once tagged, content and its associated metadata can be published to Documentum's WebCache where it can then be leveraged and utilized by a personalization server.


Documentum 4i WCM edition includes a caching component called WebCache. The WebCache moves the content and attributes to the other side of the fire. The Webcache is integrated into the Webpublisher in that single object pushes of content and attributes are done by WebPublisher users. The Webcache software consists of two parts: a source transmitter and a target receiver. The larger part of system resources are consumed by the Source transmitter. Since the transmitter is coupled tightly with the eContent Server it can scale with additional users in the same fashion that eContent servers do: adding more eContent servers for the repository will provide more Webcache transmitters.

Documentum WebCache™ provides a highly scalable, high performance access to repository controlled content, and its metadata, for staging and production deployment. Metadata stored in WebCache can be updated independently from the content, allowing you to redirect searches and re-purpose content instantly. WebCache is based on industry standard file system protocols and supports integration with any application or commerce server.




Web Content that is managed in a Documentum 4i repository is placed under lifecycle management upon import. This applies to static as well as dynamic content. Typical states for pieces of content (including data, images, source code, web pages, etc.) are WIP, STAGING and ACTIVE Content objects that make up a website that is managed by Documentum can have many versions in the repository. Only the version marked as "Active" will be deployed to the production website. So if any piece of content is "backed out" or expired from the production website, it is marked "WIP" and can either be permanently retired or edited and promoted to "Active" again. The existing active content on the production website remains available and is subject to the same lifecycle business rules. Documentum also supports the ability to take a snapshot of an entire website at a point in time - called an "edition". When this is done, Documentum records the "edition" as pointers to the active version of all content on the site at that moment. The WebPublisher administrator client also has a "synchronize" button that enables him to synchronize WIP, STAGING, and Production websites according to the current status of the content objects.


Yes. When setting up and configuring publishing jobs, parameters can be set so that that the Webcache target is based on a specific attribute value.

Page 73 of 151

Publishing

Yes.


Yes.

Yes.

Publication platformsYes.


Can your system syndicate content? Yes.Still researching and waiting for a response from engineering.

Personalization


Can your product automatically deploy files referenced in a field?Can you set the publish and expiration dates of content to be published?


Can your system produce broadcast e-mail?Can your system create individualized e-mail messages?How can your system be used to produce print publications?

XMLStoring XML and harnessing content management facilities such as workflow and library services is key to ensure content consistency, reusability and accuracy. The real value comes when the content that it represents is disseminated to consumers. XML content can be dynamically reassembled into personalised content for the appropriate channel using XSL style sheets and workflow ensuring that only trusted and approved content makes it to the consumer. With Documentum’s XSLT support you can transform XML to HTML for web presentation or enable other types of multi-channel publishing such as XML to WML for delivering content to wireless devices. By making changes to the XSL style sheets you can change your web site on the fly and globally update the look and feel for each target device. By creating XML content once and leveraging it everywhere, content is now working for you, enabling a richer user experience for your customers, employees and business partners – they get the content they need. AutorenderPro, an optional piece of the 4i family, is a highly integrated into the WebPublisher application. The main service it provides is to automatically convert Webpublisher-managed documents into PDF or HTML. The Autorender polls a work queue for each Repository it



AutorenderPro, an optional piece of the 4i family, is a highly integrated into the WebPublisher application. The main service it provides is to automatically convert Webpublisher-managed documents into PDF or HTML. The Autorender polls a work queue for each Repository it services. So one Autorender server can serve multiple repositories and in addition, multiple Autorender servers can be setup to serve a single repository (when the capacity of one Autorender machine has been exceeded). The Content Personalization Services (CPS) service is also optionally integrated into WebPublisher to provide for auto-attributing of content and auto-linking of documents.


Documentum's Content Intelligence Services can automatically, classify and categorize content.


Yes. The eConnector for BEA is the first of eConnectors to the Best of Breed Commerce platforms. The BEA Commerce Platform includes a App Server, Personalization Server and Transaction Server. The development of solutions using BEA’s platform is still owned by the web team as it is very code/java centric. It allows the BEA commerce platform to utilize content published by the Web Cache or to pull content directly from the repository. The eConnector for JDBC is used as the basis for the eConnector for BEA WebLogic.Integration with BEA's application server can occur in one of several different ways. By writing JSP pages or servlets that access the content and its associated metadata through the Web Cache, sites can be built that target this content based on matching up user profiles with content profiles. Also, since the Web Logic servers are fundamentally Java 2 compliant servers, it is also possible to access data within either the Web Cache or the live docbase using Documentum's JDBC driver. Documentum also integrates with the Web Logic Commerce/PersonalizationServer 2.0 by making content in the Web Cache or live docbase available for personalized delivery using Web Logic Commerce Server's administration console. For example, one can visually build pages and rules that include content in the


Documentum can automatically tag the content. Personalization rules are configured on the selected app server.

Page 74 of 151

Publishing

Investigating-May need further clarification.


Still researching.

Publication integrationsPlease see below.

Absolutely.

Media and asset management systems Yes.

OS User registries Yes.ERP systems Yes.

Yes.

Catalog management systems. Can be done.Surveys and questionnaires Investigating-May need further clarification.Web access and security tools Yes.Data logging and mining tools Yes.


Decision tree tools

Investigating. May need further clarification.


Documentum does not provide a personalization engine. Documentum can automatically tag and categorize content so that it can be intelligently used by a personalization app server.



















Investigating. Documentum comes with an extensive open API set. Documentum’s API supports the programming tools contained within Microsoft’s Visual Studio namely MS Visual Basic, MS C++ and MS J++. The API set is provided as both a set of customizable COM objects and a set of Java objects that opens virtually all sever functionality to the system developer.


Page 75 of 151

Publishing

Event planning and registration tools

Webcasts and streaming technologies Yes.

Yes.

Web UI


Web architectureMS IIS Server 4.0 and 5.0, and Netscape iPlanet 4.1 and 6.0.

What databases can your system use? Oracle, SQL, Sybase, DB2, Informix


Yes. Documentum recently purchased eRoom and is in the process of integrating eRoom. Documentum and eRoom have a successful history of integration between the two.


E-commerce and financial transactions systemsConversion systems for on-the-fly conversion of content (for example, from XML to HTML).

Yes. Using XSLT style sheets. Documentum's Autorender Pro product can be used to automatically render Office documents to both PDF and HTML.

Custom database applications and custom programming objects.


Web servers and Web application servers

Documentum provides connectivity with BEA Weblogic, ATG Dynamo and other J2EE compliant servers, either with our WebCache, which can publish content to http, application and commerce servers, and metadata to a JDBC compliant database, or with live connections to Documentum repositories using Documentum's JDBC driver.


Currently Documentum only indexes content that's maintained within the repository. Once published out to WebCache, end users can search the metadata that has been published. If needed suctomers can leverage a third-party for indexing content that has been published.



By default, when a client requests a connection to a server, the system attempts to connect and if it fails, the system makes another connection attempt immediately. If the second fails also, the system tries to connect to another server if another is available. If no other server is active, the client receives an error message.Similarly, if a client session times out, the system automatically reconnects the client the next time the client asks for a Docbase operation. Password validation is performed irrespective of whether a session has timed out or is connecting for the first time. You can configure the time interval between connection attempts and the number of connection retries. To change these intervals, you set the connect_retry_interval and connect_retry_limit parameters, respectively, in the client’s dmcl.ini file.

Which Web servers are supported by your product?Does your product include a proprietary Web application server?

Documentum 4i does include Documentum's proprietary RightSite App Server, however, with Documentum 5 scheduled for release at the end of September customers can use any J2EE App server.


Documentum offers integration with Web Application Servers from ATG, BEA, IBM and other J2EE app servers.

Page 76 of 151

Publishing

Yes.

No response

How does your system facilitate or perform content caching?

The eContent server has several caches used to conserve on operations like DBMS interactions, CPU cycles, and network operations. Most of the caches are small ( less than 1M byte ) and bounded by the number of objects. By far the most dominant memory usage by the eContent server lies with its “global type cache”. This cache holds structures used to enable fast access to the DBMS tables that make up a type’s instances. The size of this cache is limited by the number of types in the system. The amount of real memory consumed is determined by the number ofinstances/types that are accessed. Although this cache is called the “global” cache, it primarily functions as a per-session access structure. Each eContent process/thread will have its own copy.

Documentum 4i WCM edition includes a caching component called WebCache. The WebCache moves the content and attributes to the other side of the fire. The Webcache is integrated into the Webpublisher in that single object pushes of content and attributes are done by WebPublisher users. The Webcache software consists of two parts: a source transmitter and a target receiver. The larger part of system resources are consumed by the Source transmitter. Since the transmitter is coupled tightly with the eContent Server it can


Connection PoolingConnection pooling allows applications to reuse Docbase sessions. When connection pooling is enabled, the client library creates a connection pool when an API session is started. Each new Docbase session is registered with the connection pool. When a user disconnects from a session, the session is held in the pool to be used the next time the user or a different user requests a connection to the Docbase. How many times any particular connection can be re-used is configurable.Connection pooling uses login tickets to provide faster user authentication. When a user logs in, eContent Server determines whether the user has a login ticket and, if not, returns a ticket for that user. The ticket is stored in a client-side cache and used whenever the user requests another connection to the Docbase. The number of tickets that can be cached and the length of time for which each ticket is valid are configurable. Using connection pooling provides performance benefits for applications that execute frequent connects and disconnects with Docbases. For example, a web-based client application that services many users can make use of connection pooling to provide optimal performance for users.

How does your system facilitate or perform server load balancing?

Load balancing is maintained across all active eContent Servers.Documentum’s fault tolerant capability allows administrators to connect eContent Servers on different machines to a single . This feature, called Server Sets, helps ensure high availability because if any eContent Server goes down, clients are automatically routed to an active eContent Server. Server Sets can be created on both homogeneous UNIX and Windows operating systems. Alternatively, the eContent Server now supports Microsoft’s operating system clustering capability. With clustering, if any machine fails, rollover occurs at the operating system level to an active Windows machine. The eContent Server now supports clustering on both Microsoft NT and Windows 2000 operating systems.

How does your system facilitate or perform user session management?




Page 77 of 151

Content Management Comparison Matrix

Section Question Microsoft Documentum Interwoven Weight Interpretation NotesBusiness Profile

3

Score 1 3 5 Winner: InterwovenCustomer Profiles

No response

3

Score 3 0 5 Winner: Interwoven

Grade: (0 = Does not meet requirements/No response; 1 = Meets requirements with extensive/difficult customization; 3 = Meets requirements with relatively simple customization; 5 = Meets requirements out-of-the-box) X Weight (Scale from 0-10) = Total Score

BusinessCriteria How long have you been

in the CM business and have been producing the proposed product. What kind of growth have you seen?

Microsoft acquired NCompass Labs in May of 2001, adding Ncompass Resolution 4.0 to its product line. Renamed MS Content Management Server, the new version, MSCMS 2002, is currently in Beta testing. NCompass Labs, a private company, was founded in February 1996.

Documentum is a leading provider of content management solutions, with the proven experience and superior technology that uniquely qualifies us as content management experts. With offices around the world and serving more than 1,500 of the largest businesses, Documentum has established a tradition of excellence in meeting customer requirements since 1990. Documentum 4i WCM (Web Content Management) Edition extends Documentum's traditional document-management tools into the CM arena.

Interwoven was founded in 1995 and the first pure-play supplier of content management software. Interwoven TeamSite, Interwoven's flagship product, first shipped in 1997.

It's important to know how much expertise in CM the company has. We may be surprised at how small even some of the major players are. But more important is their CM experience.


MSCMS is installed at around 125 sites, including the Associated Press, Fujitsu Systems Business of America Inc., Johnson & Johnson Inc., Marriott International Inc., Texaco Inc. and Verizon Communications.

Corporate intranet customers include Agile, Airbus, Aon Corporation, Commonwealth of Massachusetts, Compaq Inline, Deere & Company, Oakland County, MI, St. Jude Medical, State of California. Success stories are available -- please contact your territory sales manager. Interwoven recently released TeamSite 5.5.2 and the majority of customers are planning upgrades to this version by the end of the year. Over 1000 installed base.

We want to know where their software is targetted. If they can send us the profiles of the accounts that they see as key to their success, we can decide whether we fit their profile. If, on the other hand, we're nothing like their target customer, are we looking at the right product?

Page 78 of 151

Version Upgrade PolicyNo response

3

Score 5 0 3 Winner: Microsoft Binding Agreements

No binding agreements No response

3

Score 0 0 1 Winner: InterwovenReferences

0 No response

3


BusinessCriteria


Intel Licenses all of Microsoft's products

Interwoven averages one major release every 12-14 months. Interwoven averages between 2 to 3 minor “point” releases between major product releases. Whenever Interwoven releases a new version of software, it is generally available to its customers. Interwoven will provide a copy of same software to the customer at no additional charge so long as customer is enrolled in a Maintenance Services Program. Interwoven can also deliver new releases to customers electronically. Product release notes as well as updated documentation are available prior to new version release. Notes and documentation release dates are dependent on software version or upgrade type, but do precede the release of the software. Software updates and patches can be downloaded from the password protected customer download site,

Given that next versions are going to be needed (a near certainty), we should ask vendors about their upgrade policy. Most of this will be left to ITSP, but we need to get an idea of upgrade costs/policies.


Interwoven committed to the satisfaction and delight of our customers. With respect to binding agreements and penalties, Interwoven prefers to evaluate each situation and negotiate accordingly. Please communicate with your territory sales manager the scope of the legal language Intel desires.

These binding agreements are one way to ensure that the vendor is serious about what's in the next version. This is another area for ITSP negotiation.


Intel - NGIP Next Generation Internet Program HP (Compaq) WW Intranet Sun - Intranet (MySales,

Ask for references at the sites of the projects that are like ours. If possible, the references should include a business as well as a technical contact.

Page 79 of 151

Project/Staff0 No response

2

Score 0 0 1 Winner: Interwoven0 No response

4


4


Typical Project Describe the general

steps involved in an implementation of your product.

TeamSite implementations can be executed by Interwoven’s Client Services Organization (CSO) or an appropriate consulting partner. Interwoven offers several pre-packaged service offerings. The baseline services pack includes product installation, configuration, and setup of one “branch.”

Does it seem overly simplified or does it differ widely from our workflow process?

What factors are necessary to ensure a successful deployment?

During our implementation, we explore your requirements in a Joint Application Development Session. Here we determine your organization’s content scenarios and determine success criteria. From this information, we develop our test plan and testing scenarios. From our testing scenarios, we develop test scripts. Our consultants have standard test checklists available to them. The technical consultants will run through the standard test checklist as well as run through your organization’s specific test scenario requirements. During our customer’s implementation, a certain amount of time will be devoted to validating the implementation. After the product has been implemented based on the customer’s requirements, the next phase in the implementation methodology is testing. We spend a significant amount of time making

Does the vendor offer any particular wisdom that shows that they've seen and surmounted a lot of problems?


There are many factors that affect a TeamSite implementation. For example -- size of implementation, global implications, system architecture, and number of trained resources from the client organization. TeamSite installations typically take anywhere between 10-30 days.

Does the vendor's timeframe include the full customization that probably needs to be programmed in or just general installation and some basic template setup?

Page 80 of 151

0 No response

4


4


Typical Project


Sample Statement of Work (SOW) attached.

The response tells us whether the vendor's completed projects like ours, how organized the project process is, and how strong the deliverables are.


There are many factors that determine the number of people required to implement Interwoven software. Typically, an Interwoven implementation is composed of 1-2 full-time Interwoven Architectural Consultant(s) or Consultants per initiative, a Senior Consultant as needed, and an Interwoven Consulting Manager for all project meetings. This is a small percentage of our consulting team. The customer is required to designate a Project Manager (typically 50% of a Full Time Employee) and a TeamSite Administrator (typically 25% of a Full Time Employee). During the first few weeks, we request that the Project Manager have a System Administrator available (for Network and Operating System configuration).

How complete and realistic are these lists? Do they miss any categories?

Page 81 of 151

0 No response

2


2


2

Score 0 0 3 Winner: InterwovenDevelopment environment

Typical Project


Interwoven has extensive hands-on experience in implementing the most advanced content infrastructure solutions in the most efficient manner. Our experience results from implementing over 1000 customers that vary in size and industry and working with dozens of technology partners. From our extensive domain expertise and proven methodologies, our consulting organization has pre-packaged our consulting services. We have our TeamSite Standard Pack implementation, which will provide your organization with the foundation for your content infrastructure system. We also have pre-defined extended implementation packs and add-on modules to enhance your system. The TeamSite Standard Pack implementation is the basic offering and is a required component before any add-on modules may be

Many CMS product companies can provide full service, from design to maintenance. Each, however, has its own particular way of doing so. Keep in mind that the majority of a CM project lies OUTSIDE the software.


Our Professional Services would use of standard processes to tailor a program for Intel. These processes have the experience of Enterprise deployments within 44 of the Fortune 100 Companies.

Try to get past a description of the standard services packages that the company offers, to the particular project composition that it sees for IT Storefront.


Interwoven’s consulting services offers pre-packaged implementation and configuration packages, as well as rated consultants to specific engagements. Rate structures are dependent on the type of work required. Please contact your territory sales manager for current rates.

What staff (if any) can they provide on a contract basis to assist during deployment?

Page 82 of 151

C++, C#, COM

4

Score 5 3 3 Winner: Microsoft 0

5


Typical Project


Documentum has engineers working simultaneously on a range of hardware and software to develop our products. Individual features can be developed on any of our supported platforms and "ported" to the others during our check-in and build process. The order of certification and release of platforms is then a function of priorities set by Product Management based on anticipated market demand. We write mainly in C++ and Java.

TeamSite is developed using Java, C++, and COM.

Should be a standard language that we have staff to customize the product. C++, Java, etc.


All Documentum functionality is available through our DFC (documentum foundation classes). This provides access through Java and COM. Customers can easily use SOAP to access our API, or build higher level functionality using our API and expose through SOAP. Using any of the standard development environments (e..g. IBM Web Services Development Kit) you can expose WSDL defintions of these APIs. These can then be deployed to UDDI registries. We have a number of customers using SOAP and Web Services with Documentum today. We are actively involved and founding member of many of the standards initiatives of web services (UDDI, OASIS, W3C).

TeamSite provides several access options -- Java, Perl, Visual Basic/COM, Web Services/SOAP, File System Interface, and Command Line Programs. TeamSite is a very flexible and modular architecture. The product is very configurable, from adding custom menu items to creating your own XML based templates. Our professional services team has used the programming interfaces to create hundreds of modular customizations that can perform operations that a handful of our hundreds of customers may need. Customers are allowed access to our Knowledge Base of common customizations. We have partnerships with many third-party vendors who have experience customizing TeamSite to work with their tools (for example foreign language translation).

We especially need to see how well we can create alternative workflows within Savvion.

Page 83 of 151

.NET

6

Score 5 5 5 Winner: Even No response

8


Typical Project


Documentum comes with an extensive open API set. Documentum’s API supports the programming tools contained within Microsoft’s Visual Studio namely MS Visual Basic, MS C++ and MS J++. The API set is provided as both a set of customizable COM objects and a set of Java objects that opens virtually all sever functionality to the system developer.

TeamSite offers several application integration options -- Java OpenAPI, Perl, Visual Basic/COM, Web Services/SOAP, File System Interface, and Command Line Programs.

An extensive, well-documented API is preferred. Best is that the company builds its own user interface from the same API so that we can make sure that it's well tested and provides complete coverage of the product's functions.


Proficiency in Visual Studio.NET, Visual Basic, C# and/or VBScript

TeamSite Templating offers two basic templates with flexible creation and modification options -- Data Capture Templates and Presentation Templates. Data Capture Templates can be authored in XML or users can visually create Data Capture Templates in Macromedia’s Dreamweaver. Presentation templates can be authored in any Web authoring tool and can be visually created using Macromedia’s Dreamweaver. Additionally, TeamSite offers a Visual Template Builder within the TeamSite interface.

Basic templates shouldn't require programming skills. Ideally, the tools are those that a person who can use a graphical HTML editor can easily learn and use.

Page 84 of 151

Programming required

7

Score 3 5 5 Winner: DOC+ IWOV Unknown

7


Typical Project


Documentum Web Publisher provides a variety of methods for users to author content. For authors who need off-line access, Web Publisher allows existing content to be checked out and edited while not connected to the network. If so configured, the content would be edited in an authoring tool that the user is familiar with, such as Word or Excel for casual authors or Dreamweaver for web-knowledgeable authors. Changed or newly created content could be synchronized with the repository on the authors next network connection and could start a process workflow to be approved and published. For on-line users, Web Publisher also offers the ability to use our Template Editor. This provides a simple authoring interface that limits the capabilities of an author in changing “look and feel” of a web page, but allows him

TeamSite allows the non-technical user to extend and integrate templates through the Visual Template Builder or any authoring tool, such as Dreamweaver or FrontPage.

Nonproprietary development languages and tools are preferred. We want a wide variety of people to be able to create templates. If a programmer is required to create page layouts, we'll have trouble.



TeamSite poses no restrictions on the automation of administrative functions. TeamSite's open, standards-based architecture and support for several languages (Java, Perl, SOAP, Visual Basic/COM) can enable this automation through integration with any tool.

We want to hear that all the administrative functions of the product, including workflow, user administration, database management, and reporting, can be called independently by us, using Web technologies that we want to use (ASP, JSP, CORBA, COM, J2EE, and the like).

Page 85 of 151

Unknown

7

Score 0 3 5 Winner: InterwovenLocalization

5

Score 1 5 5 Winner: DOC+ IWOV

Typical Project


Not sure what is meant by this question. Need further clarification.Regarding content aquisition, if your organization uses WebPublisher’s globalization functionality, then you can create, edit, and publish multiple translations of a Web site. The different translations of a content file all share the same name. When they appear together in a file list, they are differentiated by the language designated for each. For example, a category might have three content files called WinterWear.htm, one in German, one in English, and one in Japanese. The language is specified for each. The locale is the language and region of a given Web site. You determine to which Web site a translation is published by assigning the translation a locale. A fallback rule defines an alternate language that can be published to a Web site when a

TeamSite workflow enables the automation of any or all parts of the content lifecycle, from creation and acquisition to deployment into production.

At the very least, we should be able to modify collection Web-based forms and embed them in our own Web applications. It's better if the product offers out-of-the-box integrations with the authoring tools that we need. Principally: Word, Excel, PowerPoint, DreamWeaver, Visio, etc. We should be able to extend and modify these tools, using the programming languages that we prefer.


Microsoft partners with several 3rd-party vendors to providelocalization and globalization services

WebPublisher’s globalization functionality lets you create, edit, and publish multiple translations of a Web site. All the translations of a given content file are located in the same category in the EDIT PAGE tab and share the same name, but they are differentiated by the locales designated in their language properties. A locale is a combination of a language and a region or country. The locale determines the Web site to which the file is published. For example, a category might have three content files called WinterWear.htm, one in German, one in English, and one in Japanese. If viewing content files in the list of categories, you can filter the view to display all translations of a file or just one translation. You can also view all the translations available for a given file by clicking the Add/manage translations link in file details. WebPublisher displays the

TeamSite is fully internationalized (I18N) and supports content in any encoding schema, such as Unicode/UTF8. Many TeamSite installations have incorporated localization (L10N) as part of the workflow. Additionally, TeamSite's unique branching technology enables our customers to manage multiple initiatives from a single TeamSite server -- typically customers utilize branching to manage multiple language sites. Moreover, productized integration modules have been developed for integration with leading globalization management systems (GMS), including GlobalSight, Trados, eTranslate, and Idiom.

The overview ought to tell us how well the company understands localization and how deep its support for it is. This is expecially important for overseas locations. Getting Asian and European sites to contribute more to the IT Storefront is highly valuable.

Page 86 of 151

No synchronization

5

Score 0 3 3 Winner: DOC+ IWOV 0

4


Typical Project


You can create a translation either manually or via a workflow. In both cases, WebPublisher creates a new content file with the same name as the original content file. If you create a translation manually, you can populate the new file with the content from the original file, which would then be used to create the translation, or with imported content, usually content that has already been translated. If you create a translation via a workflow, the workflow populates the new file with the content from the original file and then sends the new file to the first user in the workflow. The user who performs the translation does so based on the content sent. Depending on the configuration of the workflow, WebPublisher might promote translations of a file only when all translations are ready. Or WebPublisher might promote each translation separately. The workflow might let you email a file

TeamSite provides side-by-side differencing tools for comparison between two pieces of content. TeamSite users can compare their original source content to localized content using this tool.

Ideally, the system maintains linkages between translated components to manage updates. It must be capable of handling content in different languages, including support for double-byte character sets or Unicode, international date formats, and global currencies. The screens that the content maintainers use must be easily translatable into different languages


This question is a little vague. For content users authoring new web content using Documentum's WebPublisher Template Editor, authoring templates can be created that allow authors to select multiple images as well as other media sources such audio and video files.

If your organization uses WebPublisher’s Media Services, you can transform an image’s format or appearance without having to know how to use graphics software. Media Services lets you generate transformed renditions of graphics by providing you with transformation profiles. The transformation profile tells Media Services what transformation to perform. For example, a transformation profile could generate a thumbnail, optimize an image, or add a text overlay. You apply a transformation profile when

TeamSite manages all content in its native format, without the need for retrofit, including multiple selection images and other media.

We will need various versions of graphics and other media that are localized for various regions.

Page 87 of 151

0 No response

7

Score 0 0 5 Winner: Interwoven0

3

Score 0 5 5 Winner: DOC+ IWOV Yes

8

Score 5 5 5 Winner: Even

Typical Project


http://www.compaq.de/produkte/workstation/?BV_SessionID=@@@@0171993920.1028306270@@@@&BV_EngineID=fadceiejkdhdbejcifcmicih.0

A successful implementation by a customer who agrees to be a reference is a strong point in the company's favor.


Documentum partners with world class auto conversion tools to deliver first draft conversions that help reduce the time and effort necessary to generate localized versions of the web pages. Once generated, the localized versions can be routed through the appropriate review and approval process to ensure accurate and consistent messages are delivered to all the international sites.

TeamSite can include a localization step as part of the workflow process. TeamSite integrates seamlessly with leading globalization management systems, including Trados, GlobalSight, SDL, Idiom, and eTranslate.

Translation aids help us put the master and translated versions of content side by side for comparison and difference checking.

Can you version and track changes at the element level?

Every time an object is versioned Documentum creates a new instance of that same object thus also versioning the attributes. WebPublisher keeps track of different versions of a file. Every time you save a file to the Docbase, WebPublisher saves the file as a new version and gives the file an incremental version number. The latest version is the version displayed in file lists. When you edit, review or process a file, you use the current version. WebPublisher also retains all previous versions. WebPublisher lets you view past versions, delete past versions, and reinstate a past version to make it the current version. If you reinstate a version, it becomes the version that is displayed in file lists and that is used in editing, reviewing, and processing.

TeamSite versions all content, at both the asset and whole site / project level.

It's really helpful to be able to send some component elements for localization separately from others that don't need to be localized.

Page 88 of 151

0

3

Score 0 0 0 Winner: Even Not without extensive customization

5


Typical Project


Yes. WebPublisher allows administrators to select "Where Used" allowing the admin / developer to see all the content pages created from a particular template.

TeamSite does not directly affect the live production site(s), though it fully supports personalization functionality in production. TeamSite resides in the development environment, managing all global content. The actual delivery of that content to specific end users based on origin nation is handled in production through an application server or personalization engine.

The CMS should be capable of reading HTTP headers and helping you decide the region of origin of Web visitors.


Documentum 4i eContent Server supports the UTF-8 encoding of the Unicode character set. If the RDBMS also is set to UTF-8, this will technically enable handling of content and metadata in any of the Unicode-supported languages. The eContent Server is able to handle characters and content in nearly any of the world’s common languages. To do this, the eContent Server has been 1) enhanced with internationalization features, and 2) enhanced to connect with databases that utilize a language encoding standard, called UTF-8, along with multi-byte and varying-width optimization. These capabilities, in combination with a distributed set of replicated eContent Servers, allow Documentum to provide an exclusive combination of globally distributed universal language support. Enhanced internationalization allows the

TeamSite is currently localized in four languages -- English, French, German, and Japanese. Future language support include Spanish, Simplified Chinese, and Korean.

Our international contributors will need, and are certain to appreciate, anything that we can do to localize their CMS interface.

Page 89 of 151

TrainingNo response

5

Score 5 0 5 Winner: MS + IWOV0 No response

5

Score 3 0 3 Winner: MS + IWOV

Typical Project

Please provide an overview of the training that you provide.

Extensive training , webcasts and seminars available

Interwoven recognizes that the purchase of software is only part of an overall strategy for a definitive enterprise content management implementation. Education and training also has a key role to play in both the successful implementation and ongoing optimization of such a purchase. At Interwoven, we have developed a reputation for providing quality instruction at all levels - from end user to system administrators and developers - and take pride in the professionalism and expertise of our instructors. Interwoven provides an extensive education offering in a variety of learning formats - lecture combined with hands-on lab exercises, simulated project studies, on-line learning, and Train-the-Trainer. Taught as a series or offered individually, courses are targeted to a wide audience ranging from content contributors and end users to

The company must have put effort and resources into training and ensure that it's professionally delivered. Should also provide materials and curricula for Intel training.


Training at Interwoven training centers are available on a regular basis. Courses can also be taught on-site or at local 3rd party training centers, typically with no more than 4-6 weeks notice, provided minimum hardware and software requirements can be met. TeamSite also offers Web-based training and Train-the-Trainer programs. Training costs at Interwoven centers are per student and start at $500. Training costs for on-site are per class and start at $2,000. Web-based training is per student and starts at $150.

We want to make sure that the training schedule doesn't affect our implementation timing.

Page 90 of 151

0 No response

7

Must offer on-site training.

Score 5 0 5 Winner: MS + IWOVDeveloper, Administrator, etc No response

6


Typical Project


A full slate of classes is regularly available at our Interwoven training centers located in Ascot (Berkshire), U.K.; Sunnyvale, CA; Bethesda, MD; Burlington, MA; and Chicago, IL. In addition, courses can also be taught either on-site at your offices or at local third party training centers. Additionally, Web-based training satisfied the need for a large volume of basic level training over a wide geographic distribution and with minimal cost.


Series and classes offered today include: § Project Administration series -- Using TeamSite, TeamSite Project Administration, TeamSite Workflow Fundamentals and Developing TeamSite Templates § System Administration series -- Using TeamSite, TeamSite System Administration (2 days - Windows or UNIX platform), TeamSite OpenDeploy (2 days - Windows or UNIX platform) § Developer series -- Using TeamSite, Developing TeamSite Templates, Advanced TeamSite Template Development, TeamSite Workflow Fundamentals§ Advanced classes -- TeamSite Workflow Developer (2 days), TeamSite DataDeploy (2 days)§ Specialty classes -- Introduction to Interwoven MetaTagger, MetaTagger Administration; Introduction to Interwoven TeamXML, TeamXML

There's almost always end-user and administrator training, but is there training for developers, managers, information architects, IT staff, or designers?

Page 91 of 151

Technical SupportNo response

7

Score 5 0 5 Winner: MS + IWOVOwn support No response

6

Score 5 0 0 Winner: Microsoft 24/7 No response

7


Typical Project


Standard Intel tech support and escalation

Interwoven offers two technical support options, Standard Care and Premium Care. Interwoven has 50 support staff worldwide with additional Engineering staff located in North America. Interwoven offers seamless support for the global enterprise. All of its centers are interlinked with the communication tools and our escalation process to ensure that the appropriate resources are applied within the shortest time possible. Interwoven’s support structure and rapid escalation process ensures expertise is close at hand and effective for quick resolution of the problem. Management escalation can take place at any point in the case cycle. Finally Interwoven has direct and rapid technical escalation in the core engineering team to clear the most stubborn issues.

Has the company put effort and resources into support and that is it professionally delivered?

Do you provide support, or do you work with any partners?

Interwoven typically provided Interwoven product support.

If the company's small, it's better if it's partnered with a larger support organization that can bring its support up to enterprise levels. On the other hand, we want to see that the company can provide the specific expertise to the partner to augment the partner's ability to address problems.

What's the geographic coverage of support, and at what hours is it available?

Interwoven maintains support centers through the Americas, Europe, and Asia-Pacific. The Standard Care Service Window is open Monday through Friday (excluding major holidays) between 5:00 a.m. and 5:00 p.m. Pacific Time. The Premium Care Service Window is open twenty-four hours a day, seven days a week, including holidays.

We will need global 24/7 support.

Page 92 of 151

0 No response

6

Score 5 0 5 Winner: MS + IWOV0 No response

6

Score 5 0 5 Winner: MS + IWOVIntel Product Manager Karin Gasch No response

6

Score 5 0 3 Winner: Microsoft

Typical Project


Interwoven offers support in the following languages -- English, Mandarin, Japanese, German, Dutch, Spanish, French.

Should cover most of Intel Corp.'s geographic diversity.

What's the guaranteed response time for a support request?

For Standard Care, once a Case has been received, a Response will be issued within two business hours unless the Case has been submitted via email or the Web. In that event, a Response will be returned within two business days. A Question will receive a Response within two business days from the receipt of the request. For Premium Care, once a Case has been received, a Response will be issued within one business hour, unless the Case has been submitted via email or the Web. In that event, a Response will be returned within one business day. A Question will receive a Response within one business day from the receipt of the request.

How willing is the company to guarantee anything having to do with support?


Standard Care Customers are entitled to two Internal Technical Representatives who may contact the Interwoven Technical Support Organization (TSO). A Case may be reported by telephone, e-mail or via the TSO Web site. Premium Care Customers are entitled to four Internal Technical Representatives who may contact the Interwoven Technical Support Organization (TSO). A Case may be reported by telephone, pager, e-mail or via the TSO Web site.

A single point of contact with fast triage and routing to the appropriate contact is preferred.

Page 93 of 151

Knowledge Base, etc No response

8

Score 3 0 3 Winner: MS + IWOVNo response

8

Score 5 0 5 Winner: MS + IWOVIt's Microsoft No response

7

Score 5 0 3 Winner: Microsoft

Typical Project


For non-urgent technical question, Interwoven offers a support Web site (http://support.interwoven.com), where customers can access and track their support cases, download new releases and patches and get information about upcoming user forums. These services are available to customers at each of the support levels.

FAQs, known bugs and workarounds, and tutorials for beginners can save a lot of money for the support organization. Can those facilities be syndicated through Intel's Intranet?


Same as al other Microsoft products

Support calls received (including email requests) are logged into an incident reporting system that issues and maintains a trouble ticket. Trouble tickets are updated in an ongoing manner and can be viewed on the support Web site. Typically, Tech Support identifies new product issues via telephone and or e-mail request from a client, and then opens a case. Once a case has been opened, Tech Support issues and updates a “Trouble Ticket" for that case. Customers may monitor the status of their case by viewing the Support Web site. Recognizing that each case is different, Tech Support categorizes each case according to its origin, and determines whether the issue is due to a product bug, product configuration/enhancement variable, or is merely a “how to” question. Once the nature of problem has been determined,

The optimum cost-effective solution is to have enough skill on the first call to correctly route the problem. We want to see that, from the first call, there's problem tracking and a logical and reasonable set of criteria for escalating to each new level of expertise.


TeamSite's maintenance is renewed on an annual basis. Our list price for standard software maintenance is 18% (annually) of the net price of the software. Our list price for premium software maintenance is 25% (annually) of the net price of the software.

We may prefer a cost-per-use model that you can charge back to business units rather than a fixed fee.

Page 94 of 151

Ditto No response

6

Score 5 0 5 Winner: MS + IWOVNo No response

4

Score 0 0 5 Winner: InterwovenMS Products only No response

5

Score 3 0 3 Winner: MS + IWOVDeployment

MS Products only

5


Typical Project


Customers pay annual maintenance fees for Standard or Premium Care. Additionally, whenever Interwoven releases a new version of software, it is generally available to its customers. Interwoven will provide a copy of same software to the customer at no additional charge so long as customer is enrolled in a Maintenance Services Program.

The extent of services for setup and the cost of ongoing support can vary. We need to take into consideration the "total cost of ownership," not just the initial purchase price.


Provisions can be negotiated to the satisfaction of both parties during the contract phase.

This sort of seriousness may be necessary. A willingness to enter into this sort of agreement shows that the company has extreme confidence in its system (or isn't smart enough to know that these sorts of agreements put it at financial risk).


Support covers all Interwoven software products.

How are problems that may be outside the CMS software supported? Are extensions using the standard API supported? Are template bugs supported? Are platform, operating system, Web application server, and database and network connectivity issues supported? For issues that aren't supported, how is it determined where the problem lies and how does Intel's staff then tie into the appropriate other support organization?


Documentum operates on Solaris 2.6, Solaris 7 (2.7) & 8 (2.8), HP-UX 11.00, AIX 4.3.3, Linux Redhat 6.2 in the UNIX environment. Documentum operates on NT 4.0 SP5 & SP6a, Window 2000 w/ SP1 & SP2 in the Microsoft environment.

TeamSite runs on Sun Solaris, MS Windows NT/2000, and IBM AIX.

Should cover current versions of Win2K and XP Professional.

Page 95 of 151

6


Typical Project


Win 2000 or Win XP OS, MS CMS (Full Install), Visual Studio .NET, SQL Server. Very top-heavy for template development

Documentum operates on NT 4.0 SP5 & SP6a, Window 2000 w/ SP1 & SP2 in the Microsoft environment.Documentum operates on Solaris 2.6, Solaris 7 (2.7) & 8 (2.8), HP-UX 11.00, AIX 4.3.3, Linux Redhat 6.2 in the UNIX environment.

Supported Client Platforms:Microsoft Windows 9X, Windows NT, Windows 2000Sun Solaris 2.6, Solaris 7 (32-bit), Solaris 8 (32-bit)Macintosh 7.5 and above

Interwoven TeamSite Front-Office Support:Microsoft Office 2000, Word 97, Microsoft Windows Explorer, Adobe GoLive 5.0, Macromedia Dreamweaver 3.0 and 4.0

WorkflowBuilder Support:Microsoft Windows 9X, Windows NT, Windows 2000

All basic functionality should be available through a Web interface so that the client needs only a Web browser. Client software should be available, but not required, as a supplement to a browser interface to enable a richer and more responsive UI.

Page 96 of 151

0

7

IE5.X

Score 5 5 5 Winner: Even 0

6


8

Score 0 5 3 Winner: Documentum 0

7


Typical Project


Documentum supports MS IE 4.0.1 SP2 & IE 5.0 - 5.x & IE 6.0 or Navigator/Communicator 4.5 & 4.7 as web browser platforms.

Browser Support:Netscape 4.7x+, Internet Explorer 4.x, 5.0+, 6.0+


Depends on the size of the implementation.

Typically, TeamSite requires a systems administrator. Administrators should typically be familiar with production servers, basic Solaris, Windows, or AIX operations, and regular expression syntax.

An open-ended question that we can use to assess the company's process and savvy on this issue.


The Documentum Server can be configured to have multiple server processes spread across several server boxes managing one repository for load balancing. In addition to load balancing, the Documentum Server supports distributed content to keep the content files closer to the area where it’s needed to reduce network traffic. The Documentum Server also supports replication from one repository to another repository. Each repository can have it’s own box and can share or have it’s own instance of the RDBMS. The Documentum system can store and manage all your content in one logical repository. The logical repository may actually be several Documentum repositories acting as a federation. This enables you to replicate content between repositories, search and workflow across repositories and share your

TeamSite is fully accessible through the browser-based user interface, regardless of location. TeamSite's MultiStore repositories allow for up to 8 distributed repositories for a single TeamSite instance.

We want people to contribute from around the world and for them to publish locally. We want to assess how the CMS can help us keep this distributed environment organized and minimize redundancy.


Doesn't matter. Webcache targets can be deployed both within and outside the firewall.

Because TeamSite generally houses a business' critical enterprise content, TeamSite installations are inside the firewall. TeamSite resides entirely in the development environment.

This question helps get at the distinctions of using this system for an intranet vs. an Internet site. It also uncovers any problems that we may experience with remote contributors accessing the CMS.

Page 97 of 151

0

5

Score 0 3 3 Winner: DOC+ IWOV Collection Authoring

0

5


8


Typical Project


Intel has not provided Documentum with this information.

Our consulting service organization will build a plan and deployment scenario based upon our experience with 44 of the Fortune 100 companies

Another open-ended question to see how well the company can understand and provide for our specific environment. We want to add a list of the significant factors that are present in our organization.


WebPublisher provides a forms-based web editor for creating web content. A With Documentum 4i, content contributors can choose their preferred desktop authoring tools and application suites, including Macromedia Dreamweaver, Microsoft Office, and Lotus Notes. Integration with popular Web authoring environments enables professional site designers and developers to easily create and maintain the Web site, navigation elements, and publishing templates.

Documentum FTP Integrators ™ enables content contribution from any Web authoring tool that supports ftp stan-dards. In addition, valuable contribution options are enabled through Documentum eConnectors ™ , which provide integrations with ERP applications. Contribution from across the distributed enterprise With the

Out-of-the-box, Interwoven’s product set supports all content authoring tools without exception. Supported authoring tools include, but are not limited to: DreamWeaver, FrontPage, Adobe Go-Live, Notepad, MS Word, MS Project, Visio, Robohelp, and Photoshop. Each contributor can use the authoring tools with which he or she is familiar.

Only a few CMS products ship with authoring tools (word processors, image-creation tools, HTML editors, and so on). Although it's helpful to know whether the product includes these tools, it's probably more important to find out whether the product supports the wide variety of authoring tools being used at Intel.


Documentum integrates with more than 200 different applications. Out of the box integrations including MS Office Suite, Dreamweaver, Homesite, MS Exchange, Exporer, Arbortext Epic, Xmetal, etc…

TeamSite Front-Office provides business users with an easy-to-use interface for creating and publishing content directly to TeamSite from Microsoft Office applications, Windows Explorer, Dreamweaver, GoLive, and other common desktop applications.

Direct integration means that some aspect of the CMS appears within the authoring tool. Some CMS products create a menu within a particular authoring tool, for example, so that authors can save content to and retrieve content from the CMS repository.

Page 98 of 151

Collection

0

9


7



All content is stored in native format in the repository. Documentum will support all known file types, as well as having the ability to define new file types as they come into existance. A full list of over 300 files types are defined to Documentum out-of-the-box and can be provided if needed.

TeamSite supports all content in its native format, without the need for retrofit. There are no restrictions to the type of content supported -- TeamSite also manages code. The Interwoven product set supports all types of content out-of-the-box including, but not limited to: XML, XSL, HTML, WML, XHTML, WAV, GIF, JPEG, ASP, JSP, JHTML, MP3, MOV, PDF, DOC, XLS, PPT, and CSS.

Many CMS products can manage files that are authored in any tool. Of course, they generally don't manage the content within these files. In other words, the CMS serves as a document management system for files that it can't interpret.


Documentum Content Intelligence Services (CIS) is an extension to the core Documentum Content Server that automates and controls the enrichment and organization of enterprise content based on powerful information extraction, conceptual classification, business analysis, and metadata and taxonomy management capabilities. In simpler terms, CIS takes unstructured content and adds attributes (or metadata) to turn it into intelligent, structured content to enable more accurate searching, easier navigation, and more effective personalization of enterprise content.

Interwoven supports metadata of all content stored in the Content Management system. Metadata is entirely customer-defined and supports attributes such as keywords, content launch dates, content expiration dates, author information, and other customer-described attributes. Metadata is stored as XML. Metadata can be captured during content creation through Interwoven's data capture form. Metadata capture can be made mandatory or optional with optional field level validation. MetaTagger is Interwoven's content intelligence software. It allows our clients to automatically or semi-automatically classify and add metadata to all asset types based on pre-defined taxonomies. MetaTagger can tag content automatically at the time content is submitted into TeamSite, or at anytime during the workflow process. MetaTagger allows

Some CMS products have pretty much full document management capabilities. MSCMS, for example, does not do this, but there are third party products like Q-Docs that add the functionality. This and the previous question will determine how much we can count on it to replace and expand DocLib

Page 99 of 151

Collection

0 No response

9


9




In this case, we're interested in the product's capability to open foreign file formats and parse them. The result is generally either XML that can be stored in an XML repository or relational database records with the full content of the source file in them. Some products, for example, take the text that you write in Microsoft Word and convert it automatically into XML for storage in the product's repository.


Documentum provides templates in the WebPublisher client to allow non-technical users with the ability to create HTML or XML content. Additionally, with over 200 out of the box integrations, users may continue to use the tools they are already familiar with, including MS Word. This gives uses a mix of web-based or thick-client based interfaces to complete thier work.Step 1: Author selects the desired category and authoring template.Step 2: Author enters a name, description, effective and expiration date.Step 3: Author enters desired text, selects the appropriate graphic and then previews his/her page to see how it will appear when published.Step 4: Using multiple xsl style sheets the author can preview their content to see how it will appear before publishing.

TeamSite supports all industry-standard (i.e. DreamWeaver, FrontPage, Homesite, Adobe Go-Live, Notepad, MS Word, etc.) authoring tools. New contributors accelerate down the learning curve because they are not forced to learn a new proprietary authoring tool. TeamSite's file system interface supports ALL editing tools - no exception. Additionally, TeamSite Templating allows non-technical content contributors an easy-to-use authoring environment that enables them to simply “fill in the blanks” using a forms-based interface. TeamSite Templating gives users the ability to create structured content as XML, which allows for the re-purposing of content across multiple publishing scenarios. Moreover, TeamSite Front-Office provides business users with an easy-to-use interface for creating and publishing content directly to TeamSite from Microsoft

We want the system to be simple enough for beginners and casual authors to create simple pages with little or no help.

Page 100 of 151

Collection

0

8


7


7

Score 0 5 5 Winner: DOC+ IWOV 0 Yes

7



Documentum’s WebPublisher product allows non-technical users to author XML and HTML-based content using existing templates. The Web Developer creates standard XML templates that are related to both a rules file as well as an XSL style sheet. The templates are then associated to the appropriate categories within the system. Through a browser the user/content contributor selects the template from the category, the Web Content Editor automatically presents the user with the appropriate options based on the defined rules. The system automatically generates an HTML rendition of the content for publishing to the web.

The Web Content Editor allows the author to focus only on entering the appropriate content while the rules file and XSL define the structure and formatting of the content. This

TeamSite Templating is an XML-based publishing solution that empowers all members of an enterprise to contribute structured content to the Web through easy-to-use, easy-to-create templates. TeamSite is built upon the concept of the separation of content from presentation. Interwoven’s next-generation XML architecture enables organizations to capture XML content and publish to multiple Web applications.

Almost all products now have a Web interface for content entry. Some may have a non-Web system as well that has fuller functionality than the Web-based forms.


Yes, WebPublisher templates provide a simple, non-technical interface for content authors to create and edit both HTMl and XML content.

TeamSite offers a WYSIWYG editing tool directly in the TeamSite user interface.

Some products include a little editing environment right in a Web-based form so that authors can format information as they type it.


Content can be setup to allow access and updating rights to only specific users or groups. Full security can be enforced or relaxed to allow these users and groups the rights to edit portions of your template or content. Security can be changed down to an object level, and these changes can happen automatically through the Lifecycle of the content.

TeamSite templates are completely customizable based on user permissions.

In other words, can we personalize input forms so that different people see different parts of the same content component, based on what we want them to enter?


TeamSite users can link to images and other media directly will completing the template.

We want to ensure that it's easy to add media and associate it with textual content.

Page 101 of 151

Collection

0

8


7

Score 0 5 5 Winner: DOC+ IWOV 0 Yes.

7


8




TeamSite templates can be created from a DTD and/or database schema.

Some products autogenerate Web-based forms from the structures that we've previously defined, saving a lot of work.


Yes. HTML wrappers can be associated with authoring templates for controlling formatting and presentation.

TeamSite templates can be additionally extended and modified through HTML and other programming.

This is an important factor, because it's likely that we'll want to customize forms and need additional features. Ideally, the forms can be customized by using a nonproprietary programming language.


TeamSite Templating fully supports hierarchical relationships. TeamSite also supports nested templates.

All products enable us to put a set of fields on a Web-based form. A few also enable us to nest some fields within others. This is really handy for entering the titles and text in sections and subsections.


Yes. Documentum handles offline content creation in a number of ways. Typical authors can be provided with templates in the repository to create or edit content. An author choosing to create new content would select a template. A copy of the template would be checked out and copied to his hard disk. An author editing existing content would select that content and check out the rendition of the content in his authoring tool format. For example, an author wanting to edit a web page component that was authored in Word would check out the Word doc file and could then edit it offline. When reconnected to the network, the author would check in his changed copy and continue the production process.

TeamSite authors can create using their authoring tool of choice, without the need to be logged into TeamSite.

In other words, can we use the CMS authoring tools "offline," a handy feature for authors who don't work on-site or for contributors who travel frequently?

Page 102 of 151

Collection

0 Yes.

7

Score 0 3 5 Winner: Interwoven0 Yes.

6


6



Through virtualization, TeamSite enables the production environment to be "virtualized" in a user specific workarea so that changes to the website can be viewed in context before the change is sent through workflow for approval and deployment into production. This is more than just a "preview" of what the site would look like - it is a "virtualized" working website in development that enables all changes to be viewed and tested prior to the workflow approval process. QA is pushed much earlier in the process so mistakes can be corrected earlier.

A preview function is extremely helpful and streamlines content creation and quality assurance workflows considerably.

Can authors view a revision and workflow history for their work?

TeamSite allows users to establish audit trails by viewing the full revision history of any file. The History command will display the state of a file at each time that it was submitted to the staging area, including statistics such as the time and date it was modified and who modified it.

An audit trail of workflow for each component is helpful for accountability as well as content troubleshooting.

Can authors perform a spelling check on their work?

TeamSite allows for the automatic call of spell checking applications anywhere in the workflow.

A nice feature to have, although rare in CMS tools. Usually, spellchecking is done before the content is placed in the CMS.

Page 103 of 151

Collection

0

7



When limited training is a requirement, we often suggest our Template Editor. This editor allows an author to enter or edit specific elements of a web page. It was built to be provided with little or no training. The rules that the template editor follows when presenting a data template to be filled out are configurable by template. Template Editor can greatly limit the variability in content entry so that you can ensure your site and page look & feel remain in your control. Template Editor does, however, require a network connection to the repository server.

Typically, one day of "Using TeamSite" training is efficient for new content contributors.

The system should require minimal training for novice or casual contributors. We should expect some training requirements for more advanced authors.

Page 104 of 151

Collection

Acquisition0

5


6


With what acquisition tools does your product ship?

Documentum provides its own aquisition technology. Documentum's Content Aggregation Services allows companies to automatically collect content into their existing content management infrastructure from various external sources, including other repositories, file systems, databases, and Web sites. With Content Aggregation Services, companies can acquire content from many different sources and then, leveraging the Documentum enterprise content management platform, repurpose that information through portals, Web sites, and other content applications, to the benefit of their customers, partners, and employees. Some of the applications in which Documentum Content Aggregation Services can play a key role include:Employee portals that repurpose content from external sources to

TeamSite can integrate with any and all acquisition tools.

Some products include advanced tools for scanning content sources and automatically capturing content. Some have syndication tools that enable us automatically to accept incoming syndication feeds.

With what third-party acquisition tools do you integrate?


TeamSite's open, standards-based architecture supports integration to all acquisition tools. TeamSite offers several integration options -- Java, Perl, Visual Basic/COM, Web Services/SOAP, File System Interface, and Command Line Programs.

Most of the larger companies have strategic relationships with other companies (often, content syndicators) to augment their abilities to acquire content automatically.

Page 105 of 151

Collection

0

9


7



Content may be imported into the repository using various import file options. These import methods can occur singularly, in groups, or in bulk and batch methods. Various UI's can be utilized to import content. Documentum has an ftp ntegrator that allows all ftp compliant applications to directly access our repository including: Dreamweaver, Homesite, etc. Our DocLoader product is available to facilitate the bulk importing of full content stores or from other content and web content management systems. All import methods mentioned are supported in both testing or production environments. As mentioned, we have the ability to easily import entire existing sites or content management systems. FTP Integrator allows tools like Dreamweaver or Homesite to push an entire site into Documentum at once. The site structure will be

Existing content can be migrated into TeamSite with an operation as simple as a drag and drop command.

Is there an automated process to import an existing Web site, or does it require an in-depth content analysis and restructuring into predefined content structures? Are there any tools at all for migrating publication types other than Web-based ones? This could be especially important to us, as we have LOTS of content to convert. Even if it would require extensive proofing, an automated system could save a lot of time and money.


Documentum can readily import the content from diverse enterprise applications, as well as itself, directly into the content repository when required and export content components to external databases as needed. If needed, external database tables can be registered with Documentum and accessed through Documentum's ODBC Gateway.

TeamSite's hybrid architecture enables access to all content, regardless of whether it resides in a database, file system, or object repository. Customer content can be in any form or type including database, file system, metadata and object content (e.g. XML). TeamSite also manages and accesses content in other native sources, such as a shared file system, direct database integration, digital asset stores, object storage systems, Documentum, FileNet, Lotus Notes, and hundreds of other environments.

The company may depend on standard programming to accomplish this, but it should demonstrate that its people understand the issue and have worked through it. We may have a product catalog database, for example, and want to create new components after new products are added to the database.

Page 106 of 151

Collection

Conversion0

6


5



Media Services is a Server based product offering that enables companies to manage complex rich media assets for the Enterprise using a common content management platform.Features1. Automatic creation of thumbnails2. Automatic / Ad hoc creation of additional renditions on registration of media (transformations).3. Examples of transformations include:· transforming to a different format (i.e. .bmp to .gif)· resizing· cropping· text layering (adding a text field on top of an existing image)· flipping / rotating· graphic optimization4. Support for profiles that provide definition of transformation by format type.5. Audit trail of media transformations


Products really vary on this count. Some have no converters at all. Others have a wide range of built-in tools for text and media conversion.



TeamSite's open, standards-based architecture supports integration to all conversion tools. TeamSite offers several integration options -- Java, Perl, Visual Basic/COM, Web Services/SOAP, File System Interface, and Command Line Programs.

The answer to this question ought to give us a feeling for how well the company understands conversion. Does it have any partners there? Does it have an idea of how conversion fits into the process?

Page 107 of 151

Collection

0

6



Web Publisher is flexible in how separate content components may be transformed into output files. Components, or layers, can be under independent control. Web Publisher provides the ability to have different authors create or edit their assigned “chunks” of content. Once the chunks are created, Web Publisher can do three different things with them: they can be published as is for an Application Server to build pages from, they can be immediately transformed within Documentum into a “final output format” which can be published to the Application/Web Server, or they can be transformed within Documentum at a later time (when publishing) to bind more current information to the content.

Documentum provides for central control of presentation and transformation templates. Related templates can be bundled into

TeamSite fully supports on-the-fly conversion of text and media in production. Please note that TeamSite resides entirely in the development environment, supporting on-the-fly functionality in production. TeamSite manages dynamic content and can integrate with all application servers and personalization engines.

As pages are requested, can the product retrieve content and convert it to the appropriate format? If so, we can store our media in one format and have it converted only if it's requested in another format. This isn't typical functionality, but some products can do it.

Page 108 of 151

Collection

Metadata0

8


7



Documentum Content Intelligence Services (CIS) is an extension to the core Documentum Content Server that automates and controls the enrichment and organization of enterprise content based on powerful information extraction, conceptual classification, business analysis, and metadata and taxonomy management capabilities. Unlike point solutions that focus on tagging or categorizing Web content only, CIS is fully integrated with the Documentum platform and enables rich tagging, and categorization for all of your content management initiatives, including enterprise document management, XML component management, and Web content management. In simpler terms, CIS takes unstructured content and adds attributes (or metadata) to turn it into intelligent, structured content to enable more accurate searching, easier

Interwoven supports metadata of all content stored in the Content Management system. Metadata is entirely customer-defined and supports attributes such as keywords, content launch dates, content expiration dates, author information, and other customer-described attributes. Metadata is stored as XML. Additionally, this metadata can automatically or on demand be replicated into any ODBC/JDBC compliant database. TeamSite persists its metadata framework (locking state, workflow state, creation dates, modification times, etc.) as a backing store on the file system.

Some products include auto-discovery and taxonomy creation tools that help us design metadata lists and automatically find metadata in the files that we process.


Interwoven MetaTagger automates the process of applying complete and consistent metadata to enterprise content assets. Based on industry-standard or custom controlled vocabularies, MetaTagger suggests appropriate metadata for content assets that can then be stored, versioned, managed, and deployed using TeamSite. With MetaTagger, you can achieve superior results in run-time search, personalization, syndication and portal applications.

Some products enable us to choose a directory or other branch and batch-apply a metadata value to it. In addition, some can supply default values for metadata fields, based on the type of content being tagged.

Page 109 of 151

Collection

0

7


7


6


6



Yes. Documentum Administrator allows administrators to perform table joins etc…

Existing metadata can be brought into TeamSite, allowing for modification by TeamSite administrators through the metadata capture form.

We may need to combine two similar metadata fields into one (for example, we may decide to merge an author field and a contributor field into one field) or split one field into two. (A single status field may need to be split into a publishing status field and an archive status field, to give us more control.)

Can you define mandatory and optional metatags?

Metadata capture can be made mandatory or optional with optional field level validation.

This may be done in the Web-based form interface, but it may also be possible to do it globally for all uses of a particular metadata field.


TeamSite supports the import of metadata from other sources.

We want to see, for example, if the product enables us to draw our list of products automatically out of a database and present them in a Web-based form. This may not be germane, as that's what we have Commerce Server for, as well as Savvion.


Metadata is stored in the RDBMS but is managed by the repository server. To access the metadata customers can use our APIs, our search technology, or our reporting technology. Documentum offers a number of published APIs for accessing content and metadata in the repository. One possible method of pulling metadata from the repository would be to write migration code. The code could provide the metadata and content to another content management system.

Search technology could also be used. Search results could include file lists, along with metadata information, and could be saved as files. These files could be used to load metadata into another content management system and assign it to the correct content.

Yet a third method would be to use

Metadata can be deployed to external files and databases through OpenDeploy.

We want to see whether the product enables us, for example, to add to the list of products and then periodically export the updated list to the database in which it originated.

Page 110 of 151

Collection

0 Yes.

8


8


7



Automatic bring up of metadata lists can be made mandatory in the workflow process. Workflow can also dictate processes based on expiration and/or review dates.

As part of managing our metadata system, we need to periodically review the validity of lists or values and either update or delete them. If we do, it's nice to have a tool that helps us update all the content that's affected by the change that we're making.


TeamSite captures metadata and stores it as XML. This metadata can be kept in its original format or can be transformed into RDF or any other format. The types of metadata fields captured is completely configurable so you could start with a well-known standard like Dublin Core and add your own custom elements.

The Dublin Core Metadata Initiative and a host of other industry-specific metadata systems are being created and revised. At some point, we may want to use one or more of them. Can the CMS help us or does it stand in our way?


This would be determined or limited by the underlying database.

Interwoven supports metadata of all content stored in the Content Management system. Metadata is entirely customer-defined and supports attributes such as keywords, content launch dates, content expiration dates, author information, and other customer-described attributes. Metadata is stored as XML.

Should support a majority of types among the following for maximum flexibility, : Free Text, Constrained Text, Pattern Text, BLOBS, Boolean, Closed Lists, Open Lists, Unique IDs, References, Outline Lists, Compound Fields.

Page 111 of 151

Storage0

7


7


Management How do you store

content? In a relational database? An object database? A file system? A hybrid of the preceding types?

Metadata is stored in the RDBMS but is managed by the repository server. To access the metadata customers can use our APIs, our search technology, or our reporting technology.

TeamSite stores customer content in a highly scalable object repository. The customer content can be in any form or type including database, file system, metadata and object content (e.g. XML). The object repository maintains the content structure and tracks the change of all content. It manages many other core CM capabilities such as workflow / business process, versioning, metadata, search and testing etc. The customer content is preserved as its native format in the repository. TeamSite also manages and accesses content in other native sources, such as a shared file system, direct database integration, digital asset stores, object storage systems, Documentum, FileNet, Lotus Notes, and hundreds of other environments. TeamSite manages all content in its native format, requiring no retrofitting. TeamSite persists its metadata framework

We want to know how the company structures its content storage to know whether it's compatible with our infrastructure requirements and can handle the sorts of content that we intend to manage.



Content relationships can be defined via metadata and organized via the file system structure using branches, workareas, and folders.

These are all the access structures that we need to store and access. All decent CMS products enable us to build a hierarchy. See how well the products that we survey do at building more than one hierarchy for the same set of components.

Page 112 of 151

0

8


5


Management


Documentum 4i eContent Server supports the UTF-8 encoding of the Unicode character set. If the RDBMS also is set to UTF-8, this will technically enable handling of content and metadata in any of the Unicode-supported languages. The eContent Server is able to handle characters and content in nearly any of the world’s common languages. To do this, the eContent Server has been 1) enhanced with internationalization features, and 2) enhanced to connect with databases that utilize a language encoding standard, called UTF-8, along with multi-byte and varying-width optimization. These capabilities, in combination with a distributed set of replicated eContent Servers, allow Documentum to provide an exclusive combination of globally distributed universal language support. Enhanced internationalization allows the

TeamSite is fully internationalized (I18N) and supports content in any encoding schema, such as Unicode/UTF8.

This is a must to localize in Asian or other double-byte languages.


XML ProcessingDocumentum processes XML documents at the time of import into the repository or at any later time. The processing of XML documents is configurable allowing users to specify a different set of actions for different types of XML documents. There are many operations an XML application can perform when processing an XML document, including validation, chunking, import of links, storage of components, metadata population, access control list (ACL) and lifecycle assignment, and extended processing. Particularly important are chunking and validation.The XML content validation is essential to ensure that the stored XML document is well formed to deliver on its ultimate promise — reusability. Documentum provides the native capability to validate XML documents during import into the repository. This process can

TeamSite poses no restrictions on the creation and number of DTDs or schemas, which are fully supported in the system.

This may not be necessary, but let's ask it.

Page 113 of 151

0

8


7


Management


When capturing existing intra and inter page links upon content import the Document WCM solution provides a spider like process for verifying, importing, and attributing the linked files.



In many systems, the hyperlinks and media references (such as an <IMG> tag in HTML) that are embedded in the middle of a block of text go unnoticed and can be broken without any clue. It's important that the software enable us to track these links and references even inside paragraphs of text.


The client products provide a search interface that not only makes it easy for the beginner, but also for the advanced user. The intent of the search interfaces is to make construction of searches very easy, no matter if the query is simple or complex in nature. Search features such as proximity searching, phrase searching, “sounds like”, and “fuzzy logic” will be accessible by the click of a button or filling in a field. Users will not have to know the Verity ‘topic’ language to construct these kinds of searches (although this option will still be available for those that desire it). Searches can be performed against both metadata as well as content. Documentum security is enforced at all times when searching content within the Documentum repository.

Documentum’s 4i Content Personalization Server (CIS) is fully integrated with the WebPublisher content contribution client. CPS provides suggested metadata values to the user in real time. When published to webcache, these values can be pushed as metadata or imbedded HTML tags.

TeamSite has its own integrated metadata search. There are no restrictions as to the type(s) of search engine(s) a site might want to use. Many TeamSite installations have integrated industry standard search engines, such as Verity and Inktomi, into the TeamSite environment. TeamSite has custom scripts that call the search engine to automatically update the search index, so that information is immediately registered with the engine and searchable. Additionally, users can search TeamSite just like they search their personal hard drive. Windows users can simply click "start->find->files & folders", point the search at their TeamSite mount, and run their keyword query. And since they’re using the Windows search mechanism, they can scope their search based on specific file types, size, modified dates, etc. They can click on any of the search results and start editing.

A good answer includes rich indexing and querying, metadata (keyword) searching, full-text searching, proximity searching, and relevance ranking of search results, as well as the capability to exclude results that a user doesn't have rights to see.

Page 114 of 151

Administration0 0

6


7


Management


TeamSite is fundamentally architected to enable non-technical business users to manage their own content. TeamSite provides an intuitive, browser-based user interface for non-technical users, utilizing a file system structure, which resembles Windows Explorer. Additionally, TeamSite workflow guides content from creation to deployment, enabling pre-defined processes for non-technical users. Moreover, non-technical users can create content using TeamSite Templating's easy-to-use forms or through their authoring tools of choice, including a tight integration with Microsoft Office applications through TeamSite Front-Office.

This is an open-ended question designed to give the company a chance to address ease-of-use issues and how it caters to novice or casual users.


For administrators, the client interface is web-based. This is an exciting new interface that replaces the administration capabilities previously provided through our full client. The features included in the web-based administration tool are:

· User/Group Management -- create, modify, delete, change status (active/inactive, global/local), rename. This also includes import of existing LDAP user/group definitions provided lists are in the LDAP-compliant LDIF file format.· Format Management -- create, modify, delete· Template Management -- create, modify, delete· Location Objects -- create, modify, delete, move, validate· Server Config Objects -- view, create, modify, copy, delete· Docbase Config Objects -- view, modify· Output Devices -- create, modify, mark as default, delete· Methods -- create, modify, delete, run· Jobs (Agents) -- create, modify, delete, run, view, view log· Mount Points -- create, modify, delete, validate, move· Types -- create, modify, drop, display

TeamSite provides an administrator's interface through the browser, where administrators can configure workflows, add and delete users, schedule deployments, etc. Additionally, TeamSite offers a visual workflow builder, allowing administrators to create complex workflows with simple drag and drop techniques.

Ideally, all administration should use Web-based tools. If there are some administrative functions that require other software, we need to know about them. This also directly relates to Savvion as our chosen workflow tool.

Page 115 of 151

0 Yes.

6


9


7


Management


TeamSite allows for the automatic call of global search and replace applications anywhere in the workflow. TeamSite offer several application integration options -- Java, Perl, Visual Basic/COM, File System Interface, Command Line Programs, and Web Services/SOAP.

The CMS should support search and replace through free text and metatags, assuming that appropriate permissions and security rights are observed.


One of the challenges in link management is to ensure that when objects are moved or renamed, all links to that object are not broken. The current solution provides this functionality through a level of indirection: all links in a document that refer to another object within the docbase are replaced by a unique identifier that will remain constant even if the target of the link is moved or renamed. Link normalization significantly improves the mundane and error prone process of managing links.


Important to be able to track these.


Documentum 4I offers a range of functionality that is dynamically tailored to match the roles and requirements of different users in the enterprise. Deployed using either standard Web browsers or desktop applications, the right capabilities are automatically made available based on user privileges. For content contributors, Documentum offers robust client functionality for creation, review, release, and control of business-critical content. For content consumers that will access and apply knowledge to accomplish business tasks, Documentum 4I includes a Web client that provides an easy-to-use portal. With Documentum’s client family, your knowledge workers have seamless access to the content they need, using the tool of their choice: a Web browser, a desktop application such as Microsoft Word, or even Microsoft Windows Explorer.

Access to TeamSite and the content TeamSite is managing can easily be controlled through OS Security, LDAP, and/or Active Directory. Additionally, TeamSite supports secure user roles, which allow different levels of access and responsibility within TeamSite, to include content submission, review and approval of Web content, and the eventual deployment of that content to the production Web site.

Important that it hook into ADS for user roles and rights.

Page 116 of 151

0

0

Score 0 3 5 Winner: Even Workflow

0

7

Score 0 3 5Winner: Interwoven

Management


Documentum doesn’t limit how the DBMS manages its data. Documentum itself offers replication and data distribution. Replication is offered both for whole objects or just for the content contained in an object.


It's unlikely that it does a lot of this automatically. Instead, we're most likely to get replication tools that we must control to ensure synchronization.


Documentum has inherent, server-based workflows that can be configured to support delegated content creation. Content can be authored in tools like MS Word, and rendered into flexible formats such as XML. XML can be intelligently authored via web-based authoring tools, either within our product UI's (User Interface's) or with third-party editing tools. Delegation can occur via manual or automated processes within Documentums workflow and lifecycle services. No programming is required to maintain connectivity or release levels with the workflow engine. The Documentum workflow engine has been integrated and included with the server since release 1.0 of the product. As a result, no effort is required to maintain release versions of the repository software with the workflow, and all workflow functionalities are completely available at all times.

TeamSite WorkflowBuilder provides a rich graphical user interface that enables users to visually design complex workflows. Users can simply drag and drop task modules and connect them with the appropriate transition objects to form the desired workflows.

We're looking for the vendor's description of its workflow tools. We need a good overview here to compare w/Savvion and determine where conflicts and overlaps may occur.

Page 117 of 151

0

6

Score 0 3 3Winner: DOC+ IWOV

0

7


Management


The WfMC – The Workflow Management Coalition. The WfMC has defined a framework for the establishing a workflow standard. This framework includes five categories of interoperability and communication standards that will allow multiple workflow products to coexist and inter-operate within a user’s environment. Documentum participates as a member of the steering and technical committees. Our current workflow product has been developed in accordance with these WfMC standards. Documentum has been a member for 6 years.

TeamSite's open, standards-based architecture supports integration to workflow tools. TeamSite offer several application integration options -- Java, Perl, Visual Basic/COM, File System Interface, Command Line Programs, and Web Services/SOAP.

Must integrate with Savvion and the company should answer all the questions in this table from a support perspective, as opposed to an implementation perspective. We want to make sure that events and content status transitions in the CMS can correctly trigger events in Savvion.


In addition to the workflow engine, Documentum provides a life cycle manager to promote a document through its stages. For example, a document may be automatically promoted and moved to a new location as it passes from Draft to Approved to Released to Retired. At each phase, the security access to the document may be automatically changed to meet the access requirements of that stage. The lifecycle may be tied to the workflow manager to synchronize the actions on the document as it is promoted through the workflow.

Engagement Services is a multi-protocol server that extends process automation and workflow across trading networks beyond the firewall, and enables organizations accelerate inter-enterprise transactions to dramatically increase efficiency and strengthen strategic partnerships. This product extends the platform to enable a new breed of inter-enterprise applications making the supply chain a shared responsibility between the buyer, supplier and marketplace.The basic premise of B2B content management solutions can be categorized into four stages namely aggregation, B2B Exchanges

Workflows can be configured for automatic triggering based on TeamSite events.

Look for the capability to trigger workflow steps by an external process, such as an e-mail message arriving or a file being added to a directory.

Page 118 of 151

0

8


0 Yes.

7


0

7

Management


WebPublisher provides workflow routing to promote and approve content out of the box. A developer or developers can define approval workflows for web content. These workflows can either be specific to individual departments or subset defined by Intel or there can be generic workflows that are resolved to individual user’s supervisors, etc. based on Documentum’s Alias set functionality.

User roles relative to workflows can be configured using the WorkflowBuilder or Command Line Programs.

We want to see that the product has strong user interface that gives administrators complete and easy access to the functions that the product offers.


TeamSite supports both simple (standard create-approval-submittal) and complex (multiple approvals, parallel) workflows. A number of standard workflows come out-of-the-box to be used as a starting point for more complex workflows to be built from.

In a parallel workflow, two people work on an item at the same time. In a sequential workflow, one person finishes before the other begins.


Workflow capabilities, through the workflow manager, include:1. Creation of simple or complex workflows.2. Creation of workflow templates that may be reused and launched from the Web or from the desktop client.3. Use of conditional routing, so that tasks can automatically be forwarded according to business rules and document properties.4. Unattended tasks, which allows certain tasks execute automatically, rather than a manual user step.5. Reassignment tasks, which allows a task to be reassigned to a designated alternate in the event the original user is unavailable.6. Branching to sub-tasks.7. Routing to a group of users, in which either one member or all members are responsible for a task.8. Dynamic assignment of recipients upon the start of the

TeamSite workflow can manage any process that Intel has in place or would like to have in place. Workflow capabilities allow you to manage the various tasks that guide the development of content from creation through final publication. The TeamSite workflow engine is a general workflow configuration that can be used repeatedly. Each workflow model describes a process, which may include user tasks and a wide variety of automated tasks.

We want to find out whether the system can handle requests for content, content submission, content addition, deletion, edits for existing content and content bundles, content reviews, content approvals, content migration, migration approval, and so on.

Page 119 of 151


0

6


0

6


0

6


0 Yes

4

Management


Conditional routing can be done based on any attribute. Documentum's workflow engine even allows if then statements based on attribute values that can determine the routing of a specific package.

TeamSite workflows allows for the incorporation of business rules to support the routing process. TeamSite poses no restrictions on workflow functionality.

In other words, what can the system look at in deciding what to do next with a piece of content? (Submitter, content type, and status are some of the usual attributes.) The best answer is that the workflow module can use any piece of metadata that we create.


Workflows are treated as separate objects and can be checked-out, checked-in, versioned, have security applied to them. Documentum provides a graphical user interface with drag and drop capability.

Workflows can be created or modified through the WorkflowBuilder. Users can simply drag and drop task modules and connect them with the appropriate transition objects to form the desired workflows.

We want to make sure that creation of workflows doesn't require programming skills. The slickest systems have a visual workflow designer with drag-and-drop manipulation of processes. Make sure that either the interface is very complete or that it's extendable. More overlap with Savvion here.


Documentum's workflow engine can incorporate automated activities within a workflow that can launch any executable. For example:-rendering content to a different format such as PDF or HTML-promoting a document from one lifecycle state to another thus modifying attributes, changing location, security, etc...-publishing content-sending out notifications

TeamSite workflows guide the entire lifecycle of content, from creation to approval or eventual deployment into production.

We want to know whether the workflow module can handle all authoring and publishing requests, including content submission, content addition, deletions and edits, content review/edits, content approvals, content migration, publishing, and testing.


Because TeamSite is fully accessible through the browser-based user interface for authorized users, there are no restrictions as to the user base. Many TeamSite installations use external providers, such as localization firms, creative agencies, etc., as part of the workflow process.

We want to make sure that the workflow tools can manage people with only a slow Internet connection to the CMS, no access to the LAN through our firewall, or only an e-mail connection .

Page 120 of 151


0 Yes

8


0 Yes

7


0 Yes

7


0 Yes

7


0 Yes

6


Management


TeamSite's Global Report Center can generate custom reports for TeamSite administrators, including content status based on user.

The best systems have rich queues that show each user what task he must accomplish.

Can you add comments at the end of each workflow stage?

Comments can be added at each workflow stage.

This is a handy feature to have. (If not built-in, we probably want to customize the system to include a comments field.)

Do you maintain an audit trail for all workflow processes?

TeamSite maintains an audit trail for all system events, including workflow processes. TeamSite's Global Report Center can generate custom reports based on TeamSite events.

Can we roll back a piece of content to any step by selecting that step in the audit trail.


The TeamSite workflow engine can notify users of tasks via e-mail and through the task list in the user GUI interface. If other types of notification are needed, the workflow process has the ability to call out to external programs or applications.

Some systems can run the entire workflow process through e-mail. Users receive notifications in their inboxes and then click links in their messages to complete tasks in the CMS.


TeamSite users with the appropriate permissions have the ability to by-pass workflow for specific content items.

Can we stop or redirect workflows in process?

Page 121 of 151

0

7


Integration0

6


Management


Contributor, Coordinator and Administrator

Workflows can be created at the asset level.

Most systems can attach a workflow to a file. The better ones can attach a workflow to a component (or whatever name are given components in the product). The best ones can attach a workflow to a particular element of a component. The body element, for example, can have a localization workflow attached to it to make sure that it gets translated. The rest of the component may not need to participate in that workflow.


The Documentum Foundation Class (DFC) is a robust interface layer within our server that allows web servers and client applications to dynamically access Repository content. The DFC is fully extensible and allows Application Servers and our Rightsite Servers to rapidly serve content and database information to Internet, Extranet and Intranet users as needed. DFC provides a common foundation for Documentum’s Client applications, Desktop Client and Developer Studio, as well interoperability for as-needed custom applications using COM and Java objects.

Web developers have a wide variety of options available to them today. There are multiple development platforms, as well as development tools. Documentum's Web Development Kit (WDK) has been developed to utilize the Java platform due to its maturity in the marketplace. A Microsoft version of this product will be developed upon the .NET platform once it is available.WDK leverages the investment in Java ServerPages (JSP). JSP is a server-side scripting environment that is used to create and run dynamic, interactive web applications. With JSP, you can combine HTML pages and script commands to create interactive web pages or powerful Web-based applications.Developers who wish to extend the Java classes that come with WDK can do

TeamSite can access any ODBC/JDBC compliant databases, including but not limited to Oracle, IBM DB2, MS SQL Server, Informix, and Sybase. Additionally, DataDeploy enables the synchronization of XML content and metadata from TeamSite to industry-standard relational databases. This gives TeamSite users access to up-to-date database content, and allows enterprises to distribute content to run-time repositories of industry-leading e-business applications.

The best case is a nontechnical interface for connecting to simple databases that can be used by administrators, plus the capability for the connection to be extended by programmers using a standard language.

Page 122 of 151

0

8


0

8


Management


Once file type of the external application is registered with the eContent Server, that particular application will automatically launch when a user cjeck out that file for editing or perhaps even viewing.

TeamSite supports the automatic launch of 3rd party of applications anywhere in the workflow. TeamSite offers several application integration options -- Java, Perl, Visual Basic/COM, Command Line Programs, File System Interface, and Web Services/SOAP.

Many products integrate with Microsoft Office products and Adobe Acrobat. The CMS product also may be capable of launching any viewing and editing tool that the system recognizes based on a file extension.


Documentum 4i provides an Open Data Base Connectivity (ODBC) gateway for interfacing with ODBC-compliant third party reporting tools like Crystal Reports. This feature enables Documentum customers to create custom reports against the Docbase RDBMS. Documentum provides connectivity with BEA Weblogic, ATG Dynamo and other J2EE compliant servers, either with our WebCache, which can publish content to http, application and commerce servers, and metadata to a JDBC compliant database, or with live connections to Documentum repositories using Documentum's JDBC driver.

Documentum’s Reporting Gateway. Reporting Gateway makes metadata in Documentum 4i available through ODBC to reporting tools such as Microsoft Excel, Access, Crystal Reports, and Business Objects. These tools

TeamSite is founded on an open, standards-based architecture. Our products are, of course, based on core standards such as HTTP, URLs, XML, and SOAP. Interwoven is also stepping up to our responsibility as the industry leader to ensure that the new standards affecting all the customers and vendors in the content infrastructure industry are developed in an open, consensus-based process. In order to fulfill that responsibility, we sponsor and participate in the globally respected standards bodies including the World Wide Web Consortium (W3C), the Organization for the Advancement of Structured Information Standards (OASIS), the IDEAlliance, and the Internet Engineering Task Force (IETF). Our staff not only participate in the activities of these bodies, we are frequently the leaders of the groups or the editors of the specifications.

Some products follow the XML schema or other open standards such as ODBC for data exchange.

Page 123 of 151

0

5


Version Control0 Yes.

7


0 Yes.

8


Management


FtpIntegrator is an FTP integration to common web authoring tools. It has been certified against Dreamweaver, but should work with any authoring tool utilizing FTP such as FrontPage and HomeSite. It allows users working in Dreamweaver to seamlessly check-in and check-out objects from the Documentum repository. The user works with Dreamweaver in the same way that they are accustomed, however, behind the scenes Dreamweaver is synchronizing the Documentum repository through FTP.This integration allows for both the creation and modification of files as well as a bulk import directly into the Documentum system. It’s as easy as selecting the directory on the filesystem and selecting put in Dreamweaver. Behind the scenes the ftpIntegrator is creating all of the necessary objects within Documentum.The ftpIntegrator

More information is needed to address the question. We look forward to discussing this in greater detail.

Sufficient information must be provided to allow simple migration of the content into another CMS, or equivalent system.

Can users check content into and out of your repository?

TeamSite provides for check-in/check-out of all content. Checked out content is designated through the TeamSite user interface.

This is the most basic form of version control.


TeamSite versions all content, at both the asset and whole site level. TeamSite users can roll back to previous versions at any time.

Make sure that it's reasonably easy for a user with permissions to restore the previous version without the need of a database administrator.

Page 124 of 151

0

7


0

6


Management


XML Documents can be automatically parsed, stored, and managed at configurable levels of granularity. These components are then easily reused across other content. Documentum is able to manage the relationships and links between components and version control at the defined component levels. These links can be both at a peer-to-peer as well as parent-child level.

Content is checked in and out at the asset level.

File level is most common; component level is the most useful; and element level check-in and check-out is necessary for more complex tasks, such as localization and collaborative authoring.

How is locking handled if content is checked out?

For checkout transactions, the eCS writes the checkout lock to the RDBMS rather than using an RDBMS transaction. This approach is optimal for enterprise content management transactions because lock duration is typically in hours & days whereas RDBMS are in seconds to minutes.

TeamSite supports concurrent development with three locking models. One of them prevents users from working on the same content at the same time. The next type is where contributors are notified of status, but are allowed to still work on files that are checked out. TeamSite has one more locking model to support parallel development of files. Essentially this model allows for multiple contributors to work on a file while maintaining a lock on the submission of the file. This allows for the contributors to push content to staging in a specific set of steps to maintain the premise of one file/version in the Staging area. Each contributor looking to submit is presented with a merge tool, if another person has modified the file before them. The merge tool is a three pane, source code level tool that allows the user to see the original file, the version submitted

We should have the option to lock the component being checked out and possibly also its siblings or parents in the repository hierarchy.

Page 125 of 151

0

8


0 Yes

7


Reporting

Management


Versioning and rollback. Web Publisher manages version control of content and components. For instance, version 2.1 may be currently published to your production web site, version 3.3 may be going through an approval workflow to be published as part of a package when approved, and version 4.0 may be being edited for the next release. Web Publisher makes these versions available for “diffing”, or viewing the changes. Previous versions of files may also be reinstated as current by users with appropriate rights. Web Publisher can also include multiple related files, for instance all files that comprise a single page, into a package called a change set. A change set may be routed through approval workflow, with the correct versions of final documents being published at the end. Change sets may also be rolled back. In addition, Web Publisher can retain

Because TeamSite versions all content, at both the asset and whole site level, roll back to previous versions can be at those same levels.

Need rollback at the site, page and component levels.


There are 3 comparison tools: a) Visual Differencing- provides side-by-side comparison of any two files. b) Source Differencing- provides a line-by-line comparison of the source of any page. c) Merging- in the optional write locking model, administrators can compare 3 files- two different versions from two different workareas as well as a comparison with the staging area version.

The best system enables us to put two versions side by side and compare each change.

Page 126 of 151

0

8


0

7


Management


Documentum 4i eContent Server’s auditing support allows you to initiate automatic auditing for any system event. When an audited system event occurs, eContent Server automatically generates the audit trail entry. Documentum provides a large set of system events. These events are associated with API methods, business policies, workflows, and jobs. For example, you can audit:· All occurrences of a particular event on a given object or given object type· All occurrences of a particular event in the Docbase, regardless of the object to which it occurs· All workflow-related events in the Docbase· All occurrences of a particular workflow event for all workflows started from a given process definition· All executions of a particular job· All events in the Docbase

TeamSite keeps a real-time log of every event that occurs within the system. This log can be used to track the development of files, the activities of users, or the development of the site as a whole. It can also be used to establish ISO 9000 compliance, or as a reference for customizing and fine-tuning TeamSite. Events that appear in the log can be used as triggers for custom scripts.

We should be able to track and log users, their time of access, and actions performed (such as downloading a particular version of a file or checking out/editing a file). We should also be able to track system usage by user, group, geographic area, and so on. We should know what kind of logging the CMS provides for staff activities.


All workflow activities, in fact, all content related activities, are individually maintained in the database for ease of analysis and reporting. Documentum provides a very comprehensive audit trail capability that can be tied to every operation performed on a docbase object. This includes any related business policy triggers, workflow state changes, attribute modifications and access entries. Several standard reports are available, and any desired report can be created with the Documentum Reporting Gateway and third party reporting tools such as Business Object, Crystal Reports, etc.

TeamSite's analytics are provided through the Global Report Center. The Global Report Center provides a tool for business users to determine all information relevant to the development and creation of all types of content, process workflows, and content deployment to production systems. Global Report Center is a fully integrated HTML page running in the browser-based client environment. It interfaces into a TeamSite log history database, or can be extended to interface into any RDBMS. It maintains a log of all content, assignments, deployments, submissions and changes by individuals. The Global Report Centers reports can be forwarded to interested users via email, or the graphical user interface can be restricted to allow only certain individuals, based on their user status, to access this functionality.

Workflow reports that are most commonly used show each component or document and its workflow status, along with other supporting information. We would prefer reports that show all components that are at a particular workflow stage.

Page 127 of 151

0 Investigating

6


Disaster recovery0

8


0

7


Management


TeamSite poses no restrictions on the generation of site maps with 3rd party tools.

These sorts of reports are very useful to publication teams.



Because TeamSite versions all content, at both the asset and whole site level, content archiving is fully supported for previous versions. Content can be archived in TeamSite's MultiStore repositories or downloaded via a 3rd archiving solution. Additionally, TeamSite recommends the use of 3rd party backup solutions for disaster recovery.

Features to look for are versioning, rollback, and automated backups. These features may be part of the database software that the CMS uses but could be controlled from the CMS administrative interface.



Interwoven TeamSite is a best-of-breed product that integrates seamlessly with our customers' specific infrastructures, including such technologies as application servers, databases, personalization engines, etc. Therefore, because these configurations vary by customer, there exist many external factors independent of TeamSite that affect such metrics as MTBF and MTTR. Please coordinate with your Territory Sales Manager for specific examples.

Some can provide this information and others can't. It's a good question to ask as we get to checking references.

Page 128 of 151

0

6


Security

Management



TeamSite is architected for high performance and scalability with its advanced repository. TeamSite's open, standards-based architecture enables high reliability by allowing for integration with Intel's existing and future infrastructures.

This is an open-ended question to give the company a chance to brief us on its reliability. Some companies can provide technical white papers that describe their system architecture and reliability features.

Page 129 of 151

0

9


0 Yes.7


0

8


Performance0

6

Management


Security within Documentum 4i is managed using the underlying operating system’s password control mechanism. This not only avoids the need to maintain passwords in multiple systems, but also allows use of operating system facilities to maintain passwords such as automatic password aging. Once a user has been authenticated and is logged in, Documentum then applies different levels of access to each content object, container or a combination of both. Access Control Lists (ACL’s) are then used to control who has access to which content asset. Unlike the common owner/group/world security model, ACL’s enable object security models to be defined and applied to content that reflect real world business requirements. The ACL can be applied on creation or can be applied manually. The ACLs can be re-used and inherited by sub


Must be able to use existing Intel security mapping and directory services such as Rialto and ADS.

Do you support a hierarchical security model?

TeamSite fully supports a hierarchical security model.

We need the capability to group users and have them inherit permissions from parent groups.


Documentum is in the process of adding this functionality.

The capability to publish media can be allowed or restricted through the user of secure user roles.

Critical for proprietary information.


Intel's level of usage has not been provided.

Hard Disk Requirements: Sun Solaris: 650 MB for Interwoven TeamSite, plus 10x site size recommended; Microsoft Windows NT and 2000: 500 MB for Interwoven TeamSite, plus 10x site size recommended. A TeamSite Sizing Guide can be provided upon request -- please contact your territory sales manager.

Important to determine the initial installation requirements for the full IT Storefront implementation.

Page 130 of 151


0

8


0

8

Management


Scaling the WCM Edition:The WCM Edition allows a company to manage its Internet Web content and deliver it to the website as content and meta-data to ensure great performance and scalability. This software has several major components: Content Authoring, Site Delivery Services, and access software for dynamic content/attribute retrieval from Internet users. That is, it can be characterized typically by the hardware/software needed on either side of the Internet “firewall” and the software that connects them. These pieces are outlined below.

Management of the content going into the Website is accomplished by the Documentum WebPublisher application. In order to correctly size the WCM application, it is important to understand that this application is Web-based and uses

Intel - NGIP Next Generation Internet Program HP (Compaq) WW Intranet Cisco-Cisco Connection Online, eLearning, Cisco Technical Assistance Center, Cisco eSales Sun - Intranet (MySales, CMO Portal) Internet (Sun.com- SunOne)

Must be extremely scalable, as IT Storefront grows and becomes a model for an enterprise-wide intranet solution.


Examples of Documentum’s scalability include Delta Airlines, currently taking 10 Million hits per day on its Delta.com site, Ford Motor Company, currently implementing a 156,000 user Intranet solution and Old Mutual, who are currently implementing a solution that was benchmarked to 101 Million objects, the largest Content Management benchmark ever undertaken anywhere in the world.

This benchmark report is included in the Appendix of this response The objective of the benchmark was to gather multi-user response time data on an extremely large docbase on a high end HP V-class system. In this test, 100,000,000 documents were loaded and 2,000 users/hour were run against this configuration. The test demonstrates first, that Documentum 4i can handle input

TeamSite is architected for high performance and scalability with its advanced repository. For example, Cisco Systems manages more than 50 million assets in TeamSite and has over 4000 licensed users. Charles Schwab and General Electric also have TeamSite installations with 1000’s of users. Additionally, an individual TeamSite server can manage multiple Web sites. The product does not inherently limit the number of Web sites that can be managed by an individual TeamSite server. In fact, Credit Suisse First Boston deploys content to 1100 servers for 3300 sites. TeamSite poses no restrictions on users or content, except for disk space limitations on servers.

Make sure that we check these capacity limits for staff as well as for concurrent audience users of IT Storefront..

Page 131 of 151


0

7


TemplatingPublishing 0

5


Management


Documentum's ContentCaster includes a user interface to configure deployments, and it contains Transmitter and Tuner modules to handle the transmission and receipt of data. ContentCaster transmits the cached Web site directly to one or more production Web servers. Alternatively, it transmits the cached Web site to a traditional proxy server (for firewall protection) or a ContentCaster proxy, which caches the transmitted Web site. This improves transmission performance to remote production Web servers.


Replication usually consists of a master version and copies that are distributed regionally to improve performance.


The Web Publisher Editor helps eliminate these delays by simplifying the Web content creation process. A "fill-in-the-blanks" form matches the content entered with a presentation template designed and controlled by the Web team. Separating the content from the presentation enables site designers to re-brand or re-purpose content across multiple sites. This enables Intel to dynamically assemble and deliver the same content to multiple sites, even if those sites have different screen layouts and navigation.

TeamSite Templating is an XML-based publishing solution that empowers all members of your organization to contribute to the Web through templates that are both easy to create and easy to use, helping reduce time-to-Web. By separating form from content, non-technical staff can capture and edit in a Word-like fashion while outputting to versatile XML. Templating is a key enabler of content re-use.

This is our chance to get an overview.

Page 132 of 151

Publishing

0

5


0 Yes

7


0 Yes

6


0 Yes

7

Not all products can do this.


0

7



HTML, MS Word. Documentum also fully supports XML/XSLT based content templates that would provide the desired functionality. XSLT templates can utilize Java to provide computational capabilities, or other functionality that basic XSLT will not support.

TeamSite Templating separates content from presentation with data capture templates and presentation templates. Data Capture Templates can be authored in XML or users can visually create Data Capture Templates in Macromedia’s Dreamweaver. Presentation templates can be authored in any Web authoring tool and can be visually created using Macromedia’s Dreamweaver.

The right answer is the languages that we use. Barring that, open languages that have a wide skill base in the programmer world are the best choices.


TeamSite Templating presentation templates are used to render content into any output format, including, but not limited to: HTML, WML, JSP and ASP.

Sadly, most don't. One day, CMS products will support templates in word processing and graphical layout program formats as well. We should find out what sort of materials IT is producing beyond the Web and see what we can make fit.


TeamSite Templating supports batch processing to create static sites.

In other words, can the CMS render a static, Web-based publication as well as serve dynamic sites?


TeamSite Templating fully supports dynamic content, utilizing database-driven content.


Yes TeamSite offers a hybrid architecture that enables universal access to content, regardless of whether it resides in a database or file system. TeamSite Templating fully supports static and dynamic content.

Ideally, we want to produce as much of a publication as possible statically for performance and robustness, but still produce other parts dynamically for the flexibility that it offers.

Page 133 of 151

Publishing

0

6

Score 0 0 0 Winner: Even 0

5


0

7



While Web Publisher allows for content format and design to be combined where it makes sense (usually to import and manage an existing web site that will be decommissioned), we provide and promote the ability to separate content format, design, and business logic. For content to be authored in a third party authoring tool, like Microsoft Word or FrontPage, Web Publisher will provide the author an input template (if required) and format the output through a separate presentation template (if required). For XML-based content authored through our own Template Editor, three different templates are involved. First, the content data template is provided. This includes default information and will store the content that the author adds in an XML format. A second template is used to determine which data the author can edit, and the rules he

Please note that TeamSite resides entirely in the development environment and poses no restrictions on dynamic content delivery in the production environment. TeamSite Templating supports the on-the-fly generation of pages with ANY application server. This can also be used in conjunction with personalization capability to provide a highly dynamic and tailored experience.

We want to see that there are some tools for this but, moreover, that the system is open enough to enable us to extend it to whatever navigation that we may want to produce.



TeamSite Templating fully supports component and navigation templates. TeamSite Templating poses no restrictions on the type(s) of templates utilized.

Refer to "Publications and Templates (in Chapter 22)," for more information.



TeamSite's open, standards-based architecture supports integration with outside systems. TeamSite offers several application integration options -- Java, Web Services/SOAP, Perl, Visual Basic/COM, File System Interface, and Command Line Programs.

Some tools may be provided, but we really want to make sure that the CMS doesn't get in your way as we do this ourselves in Commerce Server and Savvion

Page 134 of 151

Publishing

0

8


Content deployment0

8



Question is a little vague, need further clarification. Metadata can be either manually or automatically tagged within Documentum. Once tagged, content and its associated metadata can be published to Documentum's WebCache where it can then be leveraged and utilized by a personalization server.

TeamSite Templating works with all application servers and personalization engines to deliver on-the-fly generation of pages. TeamSite can handle all content, both static and dynamic, to support personalized pages. TeamSite virtualization capabilities allow users to preview content in the context of the entire site.

This is a very open-ended question that ought to yield a general discussion of the product's personalization tools and integrations.


Documentum 4i WCM edition includes a caching component called WebCache. The WebCache moves the content and attributes to the other side of the fire. The Webcache is integrated into the Webpublisher in that single object pushes of content and attributes are done by WebPublisher users. The Webcache software consists of two parts: a source transmitter and a target receiver. The larger part of system resources are consumed by the Source transmitter. Since the transmitter is coupled tightly with the eContent Server it can scale with additional users in the same fashion that eContent servers do: adding more eContent servers for the repository will provide more Webcache transmitters.

Documentum WebCache™ provides a highly scalable, high performance access to repository controlled content, and its


This is the basic deployment functionality. Surprisingly, many products expect you to do this with third-party products.

Page 135 of 151

Publishing

0

7


0

6


0

5





With Savvion, this looks like it could be redundant.


Web Content that is managed in a Documentum 4i repository is placed under lifecycle management upon import. This applies to static as well as dynamic content. Typical states for pieces of content (including data, images, source code, web pages, etc.) are WIP, STAGING and ACTIVE Content objects that make up a website that is managed by Documentum can have many versions in the repository. Only the version marked as "Active" will be deployed to the production website. So if any piece of content is "backed out" or expired from the production website, it is marked "WIP" and can either be permanently retired or edited and promoted to "Active" again. The existing active content on the production website remains available and is subject to the same lifecycle business rules. Documentum also supports the ability to take a snapshot of an

Interwoven OpenDeploy can deploy content from TeamSite's staging area into a production server automatically based on workflow, ad hoc through the OpenDeploy user interface, or through a scheduler.

This may or may not be necessary, but a staging environment would provide an extra level of approval for final publishing.


Yes. When setting up and configuring publishing jobs, parameters can be set so that that the Webcache target is based on a specific attribute value.

OpenDeploy is completely flexible and can deploy specific content to specific targets based on workflow and metadata. Properties of content can be defined via metadata.

We may, for example, want to key on various values within content components (language, for example) to determine which server to deploy the content to. Can the CMS help us here, or do you need to write your own routines?

Page 136 of 151

Publishing

0 Yes.

6


0

8


0 Yes.

8


0 Yes.

8


Publication platforms0 Yes.

8


0

8



Content type can be defined via metadata, enabling the assignment for default values for file directories.

It's useful to have all pages of a particular type deploy automatically to a particular output directory.



Interwoven OpenDeploy can deploy any content automatically based on pre-defined workflow or metadata.

If a file (an image, say) is referenced inside text that's being published, it's a good idea to have the CMS deploy the file to avoid a broken reference.


Publish and expiration dates can be defined via metadata. OpenDeploy can deploy content into production based on metadata attributes.

It's useful if we can have the CMS automatically release and remove content based on the rules that you establish.


Interwoven OpenDeploy contains a list scheduler which publishes automatically based on a pre-defined schedule.

This is what we need for small, frequently published material daily e-mail broadcasts and syndications to other systems, for example).

Can your system produce broadcast e-mail?

TeamSite can manage content for delivery in any format. TeamSite manages all content in its native format, so no retrofitting is required.

The system should be capable of integrating to our e-mail system and pushing content to it.



The TeamSite workflow engine can notify users of tasks via e-mail and through the task list in the user GUI interface. Personalized comments can be included. If other types of notification are needed, the workflow process has the ability to call out to external programs or applications.

As opposed to bulk e-mail, in which the same message is sent to a lot of people, individualized e-mail is where a lot of different messages are sent to one or a few people each. This capability ties the personalization functionality to the e-mail creation functionality.

Page 137 of 151

Publishing

0

6


0 Yes.

7


How can your system be used to produce print publications?

XMLStoring XML and harnessing content management facilities such as workflow and library services is key to ensure content consistency, reusability and accuracy. The real value comes when the content that it represents is disseminated to consumers. XML content can be dynamically reassembled into personalised content for the appropriate channel using XSL style sheets and workflow ensuring that only trusted and approved content makes it to the consumer. With Documentum’s XSLT support you can transform XML to HTML for web presentation or enable other types of multi-channel publishing such as XML to WML for delivering content to wireless devices. By making changes to the XSL style sheets you can change your web site on the fly and globally update the look and feel for each target device. By creating

TeamSite can manage and prepare for delivery in any format, including for print. Because TeamSite manages all content in its native format, there are no restrictions on print output formats.

We need to research various print publishing needs within IT.


Interwoven offers an optional product called OpenSyndicate. Interwoven OpenSyndicate™ provides enterprise-class content syndication based on business rules driven by content metadata. OpenSyndicate enables global enterprise customers to deliver content to a network of partners, suppliers, distributors, and geographically located content subscribers. With OpenSyndicate, enterprise content owners will have better flexibility to deliver the right content to the right audience without loss of control.

Syndication capabilities include creating format-neutral (generally XML) content chunks and deploying them to FTP sites, remote servers, or to mass storage devices (hard drives, CD-ROMs, DVDs, and the like).

Page 138 of 151

Publishing

0

4


0

7


Personalization



TeamSite poses no restrictions on the type(s) of content it can manage. TeamSite manages all content in its native format, so absolutely no retrofitting is required.

Not necessary, but MS Help may have some uses. Also


AutorenderPro, an optional piece of the 4i family, is a highly integrated into the WebPublisher application. The main service it provides is to automatically convert Webpublisher-managed documents into PDF or HTML. The Autorender polls a work queue for each Repository it services. So one Autorender server can serve multiple repositories and in addition, multiple Autorender servers can be setup to serve a single repository (when the capacity of one Autorender machine has been exceeded). The Content Personalization Services (CPS) service is also optionally integrated into WebPublisher to provide for auto-attributing of content and auto-linking of documents.

Interwoven offers an optional product called OpenTransform for content conversion. OpenTransform is a world-class rendering server-side technology that transforms and renders some 185 proprietary file formats into open, extensible formats, such as XML and PDF.

PDF is good for downloads that can't be modified by the user.

Page 139 of 151

Publishing

0

7

Score 0 3 1Winner: Documentum

0

8


0

8



Documentum's Content Intelligence Services can automatically, classify and categorize content.

Interwoven remains agnostic relative to personalization tool vendors and does not ship with a specific personalization tool.

Some don't, although most don't easily admit it. Others have extensive offerings.


Yes. The eConnector for BEA is the first of eConnectors to the Best of Breed Commerce platforms. The BEA Commerce Platform includes a App Server, Personalization Server and Transaction Server. The development of solutions using BEA’s platform is still owned by the web team as it is very code/java centric. It allows the BEA commerce platform to utilize content published by the Web Cache or to pull content directly from the repository. The eConnector for JDBC is used as the basis for the eConnector for BEA WebLogic.Integration with BEA's application server can occur in one of several different ways. By writing JSP pages or servlets that access the content and its associated metadata through the Web Cache, sites can be built that target this content based on matching up user profiles with

TeamSite's open, standards-based architecture supports integration to any 3rd party personalization tool. Interwoven also offers productized integrations modules with leading personalization engines, including ATG Dynamo, BEA WebLogic, and IBM WebSphere. Interwoven TeamTurbo streamlines enterprise deployment of Web properties by connecting TeamSite content management software and the leading personalization engines. Moreover, Interwoven’s Content Intelligence has been designed to improve the quality of personalization results. Through consistent, categorization-based tagging as part of the workflow, companies can be sure that their content does not disappear into the myriad of other content items. Through tagging content in a systematic, categorized manner, the ability to retrieve quality content can be massively increased.

Most at least have marketing alliances with personalization companies. Look for documented integrations.


Documentum can automatically tag the content. Personalization rules are configured on the selected app server.

TeamSite is accessible through the browser-based user interface. Interwoven TeamTurbo provides a standard set of integration points that enables enterprises to easily manage dynamic Web content such as applications, personalization rules and targeting rules. TeamSite capabilities - virtualization, parallel development, versioning and workflow - are enabled for dynamic content through Interwoven TeamTurbo.

Some products have very well-developed point-and-click interfaces for rule building. Others require a programmer to code the personalization rules - not a good long-term solution.

Page 140 of 151

Publishing

0

7


0

6


0

7


0

8


0

7





See whether you can get a concise description of the overall approach to personalization that includes a discussion of how it's actually accomplished.



User profile data collection is handled through the personalization engine. User profile data is typically stored in a database, that TeamSite can access.

Some products have functions for monitoring the user's actions and their responses to questions and then storing the results in an accessible profile - but don't count on it.



TeamSite manages any kind of data, so this is dependent on the personalization engine chosen.

Good answers include user session data, HTTP header information, page history, all content metadata, user profiles inside or outside the CMS repository, user groupings, and personalization rules.



TeamSite poses no restrictions on the type of non-Web formats desired.

Most of the action today is in dynamic HTML page building. The same tools could be used to make any other kind of personalized publication, provided that there's template support for the publication format that you need.



Deliver of personalized information to end-users is handled through the application server or personalization engine. TeamSite fully supports all personalization initiatives from the development environment.

For relatively sophisticated personalizations, the system should be able to modify these access structures automatically, based on the personalization rules.

Page 141 of 151

Publishing

0

7


0

6


0

7


0

7


0 Still researching.

5


Publication integrations0 Please see below. Please see below.

0





Some products have well-developed user interfaces for point-and-click personalization rule building.

Can your system perform collaborative filtering?



Collaborative filtering is the process where the system recommends content based on requests of similar users (an approach popularized by Amazon.com).

Please outline the kinds of personalizations that are possible based on user profiles.


This is handled through the personalization engine chosen. TeamSite poses no restrictions on the kinds of personalization possible.

This is an open question that gets the company to talk about how personalization interacts with profiles. The product may enable us to define profiles, for example, and then target content to them.




This is also called behavior-based personalization. Some systems track a user's behavior and modify the subsequent pages accordingly.


This is handled through the personalization engine chosen. TeamSite fully supports push campaigns from the development environment.

In a push campaign, the system actively presents certain content on a Web page or in another form to a group of selected users for a specified period of time.


Should integrate well with our other systems, both in-place and projected

Page 142 of 151

Publishing

0 Absolutely.

8


0 Yes.

2

0


OS User registries 0 Yes.

9

0



Interwoven offers an optional product called Content Provider for TeamSite. Content Provider for TeamSite provides TeamSite a means to data extraction from legacy content repositories. Out of the box, Content Provider can extract from NTFS, Lotus Notes, FileNet, IBM, and Documentum repositories. Content Provider’s APIs can be used to create other bridges to other repositories if needed.

Important for the DocLib team. We may eventually want to upgrade DocLib to a more robust document management system.


Companies like Adobe, Artesia, Equilibrium, IBM, Media Bin, Screaming Media and Virage have all integrated Interwoven ECM into a wide range of complex media applications.


Page 143 of 151

Publishing

ERP systems 0 Yes.

5

0


0 Yes.

3

0


0 Can be done.

8


0

6

0


0 Yes. 90


0 Yes.

6

0


Dynamically generated sources can be made available to TeamSite for testing and staging processes. TeamSite includes a proxy service that handles all requests to an external ERP system. TeamSite supports all ERP systems, such as SAP, PeopleSoft, etc.


TeamSite has integrated with Siebel Systems CRM. TeamSite's open, standards-based architecture supports all CRM systems.

Catalog management systems.

TeamSite's open, standards-based architecture integrates with all catalog management system, including MS Commerce Server.

Should work with MS Commerce Server

Surveys and questionnaires


TeamSite's open, standards-based architecture supports integration to all surveys and questionnaires.

Web access and security tools

TeamSite has integrated with Netegrity SiteMinder.

Data logging and mining tools

TeamSite's open, standards-based architecture poses no restrictions on data logging and mining tools in the production environment.

Page 144 of 151

Publishing

0

9

0


Decision tree tools 0

4

0


0

2

0


0

3

0




TeamSite Workflow provides the ability to be called from as well as call to other systems, including workflow systems. TeamSite Workflow can be through a Java API, command line tool, TeamSite GUI or URLs.


TeamSite's open, standards-based architecture supports all decision tree tools.


Investigating. May need further clarification.

TeamSite's open, standards-based architecture supports download packaging tools.


Yes. Documentum recently purchased eRoom and is in the process of integrating eRoom. Documentum and eRoom have a successful history of integration between the two.

TeamSite poses no restrictions on bulletin board and discussion systems in production.

Page 145 of 151

Publishing

0

4

0


0 Yes.8

0


0 Yes.

9

0


0

6

0


0

9

0

Event planning and registration tools


TeamSite poses no restrictions on event planning and registration tools in production.

Webcasts and streaming technologies

TeamSite poses no restrictions on Webcasts and streaming technologies in production.

E-commerce and financial transactions systems

TeamSite's open, standards-based architecture supports all e-commerce and financial transaction systems.

Conversion systems for on-the-fly conversion of content (for example, from XML to HTML).

Yes. Using XSLT style sheets. Documentum's Autorender Pro product can be used to automatically render Office documents to both PDF and HTML.

Interwoven offers OpenTransform, for the conversion of content. Additionally, TeamSite Templating is an XML-based solution that produces HTML output.

Custom database applications and custom programming objects.


TeamSite has integrated with custom database applications and programming objects.

Page 146 of 151

Publishing


0

8

0


Web UI

Web servers and Web application servers

Documentum provides connectivity with BEA Weblogic, ATG Dynamo and other J2EE compliant servers, either with our WebCache, which can publish content to http, application and commerce servers, and metadata to a JDBC compliant database, or with live connections to Documentum repositories using Documentum's JDBC driver.

TeamSite poses no restrictions on Web servers and Web application servers. OpenDeploy can deploy content to any Web server, such as IIS and Netscape. Additionally, TeamTurbo offers productized integrations to popular application servers, such as ATG Dynamo, IBM WebSphere, and BEA WebLogic.

Page 147 of 151

Publishing

0

7


0

6


0

8



Currently Documentum only indexes content that's maintained within the repository. Once published out to WebCache, end users can search the metadata that has been published. If needed suctomers can leverage a third-party for indexing content that has been published.

TeamSite poses no restrictions on searching and indexing in production. TeamSite's content intelligence has been developed to enhance search results. Additionally, Interwoven’s Content Intelligence has been designed to improve the quality of search engine results. Through consistent, taxonomy based tagging as part of the workflow, companies can be sure that their content does not disappear into the myriad of other content items. Through tagging the content in a systematic, taxonomy-based manner the ability to retrieve content can be massively increased.

Searching isn't necessarily performed by the CMS. For static sites, a standard third-party search engine may be fine. For dynamic sites that are produced by the CMS on the fly, you need integration between third-party search engines and the CMS search functions.



TeamSite manages and deploys content in its native format, posing no restrictions on the type(s) of content desired.

Some products include browser sniffers and supporting code to make serving browser-specific pages easier.



TeamSite resides entirely in the development environment and poses no restrictions on session management, cookies, or caching in production.

This is important stuff for personalization and customization.

Page 148 of 151

Publishing

Web architecture0

8IIS is essential


0 No, TeamSite remains agnostic.

2


0

8


0

8

SQL Server 2000 and Oracle


Which Web servers are supported by your product?

MS IIS Server 4.0 and 5.0, and Netscape iPlanet 4.1 and 6.0.

TeamSite supports all Web servers without exception.

Does your product include a proprietary Web application server?

Documentum 4i does include Documentum's proprietary RightSite App Server, however, with Documentum 5 scheduled for release at the end of September customers can use any J2EE App server.

Some products still do have their own application servers. You want to make sure that the product doesn't lock us into its own application server but enables us to integrate to one of the better commercial application servers.


Documentum offers integration with Web Application Servers from ATG, BEA, IBM and other J2EE app servers.

TeamSite integrates with any application server. Interwoven TeamTurbo provides productized integrations to popular application servers, including ATG Dynamo, BEA WebLogic, and IBM WebSphere.

For any product that we expect to use for more than the next year, the company needs at least to have plans for how it intends to integrate it with industry-standard application servers.


Oracle, SQL, Sybase, DB2, Informix

TeamSite supports all JDBC compliant databases, including Oracle, IBM DB2, MS SQL Server, Informix, Sybase, etc.

D429

Michael Talman: Does this mean we will need to use Documentum 5, so that we have access to MS Commerce Server?

Page 149 of 151

Publishing

0

6


0

6


How does your system facilitate or perform content caching?

The eContent server has several caches used to conserve on operations like DBMS interactions, CPU cycles, and network operations. Most of the caches are small ( less than 1M byte ) and bounded by the number of objects. By far the most dominant memory usage by the eContent server lies with its “global type cache”. This cache holds structures used to enable fast access to the DBMS tables that make up a type’s instances. The size of this cache is limited by the number of types in the system. The amount of real memory consumed is determined by the number ofinstances/types that are accessed. Although this cache is called the “global” cache, it primarily functions as a per-session access structure. Each eContent process/thread will have its own copy.

Documentum 4i WCM edition

TeamSite poses no restrictions on content caching in production.

Caching can happen at many levels. We need to understand the difference between the caching models used by the various contenders. Make sure, too, that the company can demonstrate Web-server performance commensurate with the amount of traffic that we expect.


Connection PoolingConnection pooling allows applications to reuse Docbase sessions. When connection pooling is enabled, the client library creates a connection pool when an API session is started. Each new Docbase session is registered with the connection pool. When a user disconnects from a session, the session is held in the pool to be used the next time the user or a different user requests a connection to the Docbase. How many times any particular connection can be re-used is configurable.Connection pooling uses login tickets to provide faster user authentication. When a user logs in, eContent Server determines whether the user has a login ticket and, if not, returns a ticket for that user. The ticket is stored in a client-side cache and used whenever the user requests another connection to the Docbase.

Interwoven Applications interface through API's to standard database drivers If the specific database drivers support database connection pooling then TeamSite will support database pooling.

This may be handled completely outside the CMS. Know which parts are performed within the CMS and which parts depend on a third-party application server.

Page 150 of 151

Publishing

0

5


0

5


How does your system facilitate or perform server load balancing?

Load balancing is maintained across all active eContent Servers.Documentum’s fault tolerant capability allows administrators to connect eContent Servers on different machines to a single . This feature, called Server Sets, helps ensure high availability because if any eContent Server goes down, clients are automatically routed to an active eContent Server. Server Sets can be created on both homogeneous UNIX and Windows operating systems. Alternatively, the eContent Server now supports Microsoft’s operating system clustering capability. With clustering, if any machine fails, rollover occurs at the operating system level to an active Windows machine. The eContent Server now supports clustering on both Microsoft NT and Windows 2000 operating systems.

TeamSite poses no restrictions on load balancing in production.

We'd need support from the CMS for this.

How does your system facilitate or perform user session management?


TeamSite poses no restrictions on user session management in production.

Does the system rely on cookies, or does it provide other methods of tracking user sessions?

Page 151 of 151

Publishing

0 Yes.

8


0 No response

5


###

Scoring

Point Totals 684 3986 5408

6.34 ###

Percentage Score 10.5 61.2 83.0


TeamSite fully supports and can leverage user-profile information stored in directory services. TeamSite authentication can be managed through OS security, LDAP, and/or Active Directory.

Probably there's some integration effort needed.


TeamSite poses no restrictions on LDAP integration. Most large customer use the product with LDAP.

This is a concern if you're using LDAP services in your environment.

Avg. Weight

6.34Overall Points Winner:

Interwoven

Overall Score Winner: Interwoven

Date post:	17-May-2018
Category:	Documents
Upload:	doandien
View:	213 times
Download:	0 times