OpenText Managed Services

The Vendor is required to provide to continue the administration, management, and support, and to perform potential enhancement work of Department OpenText system in a government cloud environment. 
- The system must be compliant with all federal and state laws, including HIPAA compliance, if requested by a participating department Division, and provide documentation from accrediting source upon request.
- Department use OpenText in the Azure government cloud environment to efficiently manage and streamline various business processes, in addition to storing critical digital documents containing Personally Identifiable Information (PII).
- The OpenText solution provides an interface for the scanning, processing, analysis, document workflows, and storage of large volumes of documents and images in various formats.
- The system must be capable of storing content files in multiple document file types either by the software or the underlying file system, including:
•    Microsoft Office document formats
•    Adobe Acrobat PDF files
•    TIFF image files
•    JPEG image files
•    PNG image files
•    GIS files image files
•    Audio files
•    Video files
•    Text files
•    SQL files
•    CSV files
•    “R” file format
•    Access files (mdb)
•    PYTHON
•    MYSQL
•    ARCGIS
•    Tableau workbooks
•    DWG and other CAD files
- The system must identify orphaned document submissions at the file level and route them to an exceptions folder, initiating exception workflow tasks.
- The system must maintain audit tracking of all access and changes made by end‐users.
- The system must preserve the original document(s) and maintain version control for changes made throughout processing.
- The system must allow the configuration of document version control on a per‐file or per‐folder basis for those situations where version control is not required.
- The system must contain editing features such as:
•    Addition or deletion of annotations within files,
•    Visual enhancement for readability,
•    Redaction of original information contained on the document,
•    Highlighting.
- The system must be capable of supporting a mass migration of data in or out of the cloud storage.
- The system must provide a management tool to allow for the compilation and delivery of records to external entities with secured (non‐public) access, including an audit utility to track when external users have accessed records.
- The front‐end and back‐end of the content management system must be independent for end-of-contract transition.
- The system must be able to export contained data to external applications or alternate cloud environment through API(s), Web Services, or other mechanisms while maintaining data integrity and metadata.

- Contract Period/Term: 5 years
- Questions/Inquires Deadline: December 09, 2025