The initial setup is easy, requiring at least three people: a technical consultant, a functional consultant, and a project manager. The setup takes at least eight to twelve weeks, depending on the scope of the customer.

I rate the initial setup an eight out of ten, where one is difficult, and ten is easy.

The tool's deployment is moderate. You need to do two to three separate installations. The process is easy, where you must create and deploy packages. 

The product's initial setup phase was a little difficult because of the resources available.

I rate the product's initial setup phase a five on a scale of one to ten, where one is a difficult setup phase, and ten is an easy setup phase as it was a process with medium complexity.

The solution is deployed in the cloud and on an on-premises model. The product supports the services of all the clouds.

The solution can be deployed in two to three months.

We had a great Value Added Reseller (VAR) in place. They handled the initial setup and configuration wonderfully.

The initial setup was not difficult, but we needed a little bit of background knowledge to deploy the solution.

We've had it for a year now, and since we started implementation it has been, to say softly, a nightmare. I don't know what the complexity of the tool is, or if it is the environment, but we really have had big trouble.

HPE CM is a highly customisable product. If it is rolled out ‘out of the box’, it is quite simple. However, like most organisations, we need it to do certain things. Defining record types, business classifications, security classifications, locations, additional fields will never be an easy task. If we were to have a do-over, I think we could have had a little more rigour around what was necessary and what was not, which could result in a much cleaner end product.

We contracted it out to avoid problems with complexity.

Initial setup was straightforward.

Setup was complex because we were migrating from a custom “in-house” product to an “off-the-shelf” product.

Technical side: Initial software setup would benefit from specialist involvement. The documentation is comprehensive, so it’s not absolutely necessary to engage a specialist as long as all the documentation is read and understood. For experienced installers, the setup is actually very straightforward and can be done anywhere from a half a day to a few weeks (depending on existing infrastructure, database access and complexity of system). I would recommend specialist knowledge for software/schema upgrades to prevent potential loss of data.

Content structure and administration: A successful implementation requires an experienced Content Manager business analyst and administrator. Planning the management of content before you start is integral, and a good business analyst will be able to identify the functions and activities of your organization and structure your Content Manager environment accordingly. Setting up appropriate security classifications, security caveats, business classifications schemes, record types and locations structure would benefit from a Content Manager administration expert.

The initial setup was somewhat straightforward. Our only major issue was that the guidelines for setting up our document stores were not geared to scalability.

Initial setup was straightforward and clear.

Initial setup is always complex to get all integrated processes/technology/software working together. For example, Adlib software will poll exchange mailboxes to ingest and process emails and create conversion and content metadata XML output as well as PDFA documents including native formats. OpenText OCC will poll the HNAS drive to ingest the output files that Adlib produced and to OCR all documents and create full text index to extract all metadata and them apply customization code that ingests the Adlib conversion metadata and merge the OCR content metadata then output the transformed XML with the PDF files ready for the next step.

Any content management software will then poll the output directory and ingest all files into the ECM system to store in a database record management system. Paper documents digitized by an external provider were transferred via secure FTP to a shared drive which the ECM system utilities would also poll to ingest and create the records in the EDRMS.

The initial setup was complex.

Initial software setup is straightforward, though quite a lot of preparation is required for the information management processes. As the software is very customizable, the actual configuration for business use requires a lot of input from information management staff.

• Issues with setting up and getting the retention schedule triggers to work: The help menu was not helpful and this was not a part of the basic configuration that was initially set up with the consultants.
• Management of multiple offices of primary responsibility (OPR): In our system, we have multiple OPRs, and HPE RM clients were using the owner to manage only one OPR.

The deployment took six months and our implementation strategy was that of a cloud-based service package.

It was an easy installation.