Only one or two are enough for the solution’s maintenance.

Overall, I rate the solution a nine out of ten.

I rate the solution a ten out of ten. It is a good add-on if you are using SAP products. The most prevalent integrations that can be seen in the product are SAP, Salesforce, Oracle, and Office 365. 

OpenText Content Manager is a leading ECM solution in the market that offers vast functionalities ranging from case management to document storage and workflows. The tool has its own hardships with areas related to development, implementation, and high costs, especially compared to other products in the market.

I rate the overall tool an eight out of ten.

We are very pleased with HPE Records Manager.

I am an end user. My peers guide me whenever I face issues with the solution. People wanting to use the solution must go through the demo and try to understand the software before deploying. Overall, I rate the product an eight out of ten.

If security is a major concern, like with Kubernetes, and budget is not a problem, then OpenText is a good solution. If you have a budget constraint and want medium-level security, or if the information is not critical or synthetic, then SharePoint is a better option than OpenText. Also, SharePoint is better if you are looking for no customization.

Overall, I rate the solution an eight out of ten.

It's a great product. But HPE needs to step away from the commercial interest and really help us to get what it is that we are looking for. It always comes with a price, but it looks that it's not just a tick in the box. We want to really see it end-to-end that it's going to work for us as well.

I would advise any organisation to really define what their information management business requirements and end-user requirements might be, noting that they are not going to line up. Additionally, it's important to include in that assessment what the format of that information will be in. Accessibility and transfer of information are also highly important for some organisations.

Due to very limited use in the industry, vendor and contract support are hard to find. We are using a consultant on the East coast which is four time zones away. 

There is more call for this product in Australia. The development of the product has moved to the UK. 

US support will probably remain spotty. 

This product has changed hands twice, from Tower to HP and then to Micro Focus. This has made support more difficult for us. 

Setup within the system is important. We have many users that really dislike the system, and I believe much of that has been due to setup and training. 

Know what you are doing from an information management (IM) perspective. The IT side of it is easy. If you get the IM components wrong, or not optimised, then you usually become part of the problem that the solution is trying to solve.

It always takes more time and money.

Firstly, plan, plan, plan: Hire a good business analyst and assess how your users work, what type of content they create and how you want it structured. Planning your content structure is integral to a successful implementation. Ask yourselves the questions: How do users want to search for content? How do users create content? How do users collaborate/share content? Then ensure you have a good migration plan to transfer content from your current system to your new one.

Secondly, training: Training your users comprehensively, to the point of confidence, will see a much larger user uptake. If they are unsure of themselves, they will not use the product.

Thirdly, infrastructure: Make sure you have good, reliable hardware for your Content Manager servers and database servers, and that your network is stable and fast.

Fourthly, change management: Different things could work for you here. Examples of things that I see work are constant, positive communication prior to implementation; lock down shared drives and easy migration to new system; top level-down migration. Management buy-in is integral and they need to use the product. If they do, then their staff will follow.

One advantage of this product is that it allows us to determine our own structure. Some insurance document management solutions require you to follow their structure. This has advantages and disadvantages, and you really need to understand and plan how you want to organize your data.

Organize your information in a way that makes sense for daily activities and working with documents. Do not fall into the trap of organizing data for searching. We have a few structures that have grown difficult for day-to-day work because they are optimized for searches that rarely occur.

Go for it. It works reliably for average-sized organizational structures.

Be very clear with functional and non-functional requirements. Set forth minimum mandatory baseline business requirements in order to meet overall EDRMS objectives, aligned with the Principles and Functional Requirements for Records in Digital Office Environments and compliance. Also identify non-mandatory features deemed desirable but not mandatory.

In addition:

• Provide the organisation functional requirements specific to the use and operation of the EDRMS.
• Detail the relevant standards and specifications applicable to the efficient management of public/private records – NAA or PROV.
• Provide the mapping and traceability between the Business Requirement and NAA standard/business and specification with the functional use case as context.
• Provide guidance to vendors in the implementation of the EDRMS system, testing and user acceptance testing.

All requirements should be uniquely identified for tracking purposes and have a business priority assigned to provide an understanding of business importance.

The priorities should be derived from an EDRMS strategy to ensure consistency across business units. A code should be provided to indicate EDRMS’s (Vendors) ability to meet the business, compliance and functional requirements. There should be clear traceability in their ability to meet expectations. What is their ability to meet functional and non-functional requirement statements? Can they fully meet, partially meet, conditionally meet, solution not concluded, cannot deliver, etc.

Stipulate your complexity model to identify what requires complex customization, requires complex configuration, requires minor configuration or is an out of the box requirement. Identifying these components will make it easy to manage the vendor's deliverables and gives the business a better grasp on the monetary bottom line expectation and where the money is being allocated to. Create transparency where you can.

You can’t pre-plan enough on how you want to organize the records. The more planning you put into the implementation, the more you will get from the product. Don’t discount the amount of hand-holding and change management your organization might need.

Look for vendors or partners in your area to offer advice.

Fully understand the impact of how you set up the system; for example, the internal locations directory, security groups, security/access on different levels (classification, folder).

The entire organization makes use of the solution and this is primarily done by those in charge of records management. 

The organization comprises 500 people. 

My advice to others is that they cannot go wrong with the solution. It is the stable and secure Content Manager product available. 

I rate Micro Focus Content Manager as a seven out of ten. 

This is a wonderful product with many options. We have never been disappointed by it.

There are serious considerations of compliance for the product role. HPE TRIM has limitations beyond a document repository.