The organization is currently working with OpenText products mainly. In the organization, another team is working with IBM as well, but more focus is on OpenText currently. The organization works with basically any content management solution OpenText has. OpenText Information Archive is not currently being used with integrated records management that has been set up. If deletion is needed, it is done manually. Overall, retention policy is seen as a very strong capability and customers are really using it in every single installation. Retention policy is one thing and security, such as security clearance applied on top of standard access rights, is the second part used almost in every single solution. From time to time it might be integrated with others such as SAP ILM, but the majority of those are independent and are managed for customers. It works and really complies with all the regulations that need to be met and also legal requirements. Metadata is crucial as OpenText Information Archive is a strong metadata-driven application. Metadata is used for multiple purposes such as searching, web reports, and visualization. Capabilities have even been implemented to use metadata for access control. If status is changed, access control automatically changes for people who should have access to that and removes it for those who should not. Metadata conceptually is the basis of work with content management. The structure in a tree-like form is just the additional form. Of course, it needs to be stored somehow, but metadata is most frequently used for many visualizations for customers. Many customers are using cloud. The first solution is installing on-premises solutions on their own cloud infrastructure as IaaS. The majority of customers are usually using Azure for whatever reason. If this is a public cloud, customers are usually not asking for infrastructure from the vendor perspective, just for location because it should be EU-based cloud data center. That is the only preference. For private cloud, customers also do not have usually preferences. However, if they have their own infrastructure, they are usually running on Azure. A partnership with OpenText exists. The overall review rating for this solution is 9 out of 10.
CTO - SVP Products and Services at a tech services company with 11-50 employees
Reseller
Oct 11, 2022
I rate this solution an eight out of ten. I would advise others to start with one or two key projects and build on them over time instead of trying to do too much at once. Like most technology projects, pick an application you need to archive and start building on that. There is usually one project that drives the need, and once it's in your environment, other business owners will need it and want to use it for other applications.
File Archiving involves the efficient storage, retrieval, and management of digital files to enhance operational workflow and regulatory compliance for organizations.Leading File Archiving solutions offer robust platforms for data organization, ensuring that businesses can store vast data volumes while maintaining quick retrieval capabilities. Users value these solutions for their ease of integration with existing IT infrastructure and the ability to scale as the organization grows. Effective...
The organization is currently working with OpenText products mainly. In the organization, another team is working with IBM as well, but more focus is on OpenText currently. The organization works with basically any content management solution OpenText has. OpenText Information Archive is not currently being used with integrated records management that has been set up. If deletion is needed, it is done manually. Overall, retention policy is seen as a very strong capability and customers are really using it in every single installation. Retention policy is one thing and security, such as security clearance applied on top of standard access rights, is the second part used almost in every single solution. From time to time it might be integrated with others such as SAP ILM, but the majority of those are independent and are managed for customers. It works and really complies with all the regulations that need to be met and also legal requirements. Metadata is crucial as OpenText Information Archive is a strong metadata-driven application. Metadata is used for multiple purposes such as searching, web reports, and visualization. Capabilities have even been implemented to use metadata for access control. If status is changed, access control automatically changes for people who should have access to that and removes it for those who should not. Metadata conceptually is the basis of work with content management. The structure in a tree-like form is just the additional form. Of course, it needs to be stored somehow, but metadata is most frequently used for many visualizations for customers. Many customers are using cloud. The first solution is installing on-premises solutions on their own cloud infrastructure as IaaS. The majority of customers are usually using Azure for whatever reason. If this is a public cloud, customers are usually not asking for infrastructure from the vendor perspective, just for location because it should be EU-based cloud data center. That is the only preference. For private cloud, customers also do not have usually preferences. However, if they have their own infrastructure, they are usually running on Azure. A partnership with OpenText exists. The overall review rating for this solution is 9 out of 10.
I rate this solution an eight out of ten. I would advise others to start with one or two key projects and build on them over time instead of trying to do too much at once. Like most technology projects, pick an application you need to archive and start building on that. There is usually one project that drives the need, and once it's in your environment, other business owners will need it and want to use it for other applications.