- The client implemented OpenText in 2005 with a heavy emphasis on repeating folder structure and minimal metadata
- The client’s OpenText environment was at version 10.0 on Windows Server 2008 and performance was affecting business productivity
- Due to the increase in information over the years, the original design for the Property Folder taxonomy had begun to breakdown
- Multiple repeating structures throughout the Enterprise made information impossible to find
- Each department maintained copies of the same content and there was no longer a single source of truth for corporate records
Solution
- Performed an upgrade of Content Server from 10.0 to Content Server 16
- Post upgrade performed a taxonomy redesign, and created a single Property location at the Enterprise for all corporate property records
- In place migration and metadata application for all property content from the 18 disparate locations in CS to the new Property structure
- Custom integration with Yardi to sync property metadata from Yardi to Content Server
- Created a custom WebReports dashboard for users to quickly locate property records from within Content Server
Benefits & ROI
- Client initiative to decommission OpenText Content Server was rescinded post solution rollout
- The custom Dashboard opened the OT repository up to the entire business population, and most end users were not familiar with OpenText and were hesitant to use the system
- Overall system performance and ongoing maintenance managed by APS has given the client the confidence to extend ECM within the organization
- Leveraging the Yardi metadata for the property records in Content Server has increased overall business productivity and allowed the Records Management department to better manage the records in Content Server
