Shared rules, different business needs
We establish common document, metadata and access rules while giving teams the workspaces and processes appropriate to their roles.
Document management for complex organisations
More departments, systems and documents need a consistent approach. We design a document platform that fits your infrastructure and operating model.
Capacity based on real demand
We assess document volumes, concurrent use and integration traffic. The proposed infrastructure is checked against agreed usage scenarios.
Availability and recovery
With your IT team, we define backup, recovery, monitoring and maintenance requirements. These become part of both the architecture and the operating procedures.
Controlled change
We document custom extensions and dependencies on other systems. Upgrades include checks of critical processes and a recovery plan if a change causes problems.
Users and applications / Identity and roles → Document API / Application services → Availability and scaling / Data and document layer → Backup and recovery / Access and audit. High availability does not replace backups or tested recovery.
Frequently asked questions
Who can see sensitive documents?
Access is configured by role, group and application. Checks should include previews, exports, service accounts and role changes. Hiding a menu link is not an access control.
Cloud or on-premises?
Consider data sensitivity, availability, integration, operating capacity and cost. Compare backup, recovery and exit arrangements as well. Public-sector projects also need to check the rules for the specific cloud offering.
What affects implementation cost and timing?
Applications, users, interfaces, data quality and customisation all matter. A proposal should distinguish licences, implementation, migration and support. A useful schedule also accounts for the customer's preparation and participation.
What happens when a connected system is unavailable?
The integration should record failure, distinguish temporary issues and support safe retry. Depending on the scenario, use a queue or a controlled error response. Keep track of what has already been processed.
What support response times do you offer?
Response times, service hours, priorities and escalation are defined in the support contract. They reflect the system's importance and responsibilities shared by the customer, ALTAIR and other suppliers.
What should system handover include?
Configuration, interfaces, roles, operating procedures and custom-extension documentation, as well as the application. Agree administrator access, backup, support and upgrade arrangements in the requirements.