Define the support boundary before an incident occurs
Fortra support and maintenance is an MMC service enquiry whose scope should be explicit about products, versions, activities and coverage. A general promise of support is difficult to operate when the manufacturer, customer infrastructure team and application owner each control different dependencies.
Build an asset and entitlement schedule, then distinguish manufacturer technical support from MMC assistance. Identify planned maintenance, configuration help and fault coordination requirements. Response arrangements, attendance, escalation and exclusions must be stated in the contract; they should not be inferred from a product-page enquiry link.
Create an actionable request and maintenance process
Agree how faults are raised, what evidence can be shared safely and who approves disruptive actions. The operating team needs access to version and configuration records without sending credentials through an ordinary support message. Planned work should include prerequisites, backup checks and validation with the service owner.
Reporting should explain actions, unresolved causes and the next owner rather than merely closing a ticket. For Dubai, Abu Dhabi or multi-site UAE work, distinguish remote activities from visits and include access arrangements. MMC can scope agreed support tasks; continuous monitoring, emergency response and extensive custom work need separate confirmation.
Evidence to request for this scope
- List covered assets, versions, manufacturer entitlements and MMC responsibilities.
- Agree request channels, evidence handling, change approval and escalation.
- State maintenance activities, coverage periods, exclusions and any on-site arrangements in writing.