A legacy systems support RFQ should help a qualified provider understand your environment, the work you need and the conditions under which it must be delivered. A short request that asks only for an hourly rate often leaves critical assumptions unstated. The result can be quotes that look comparable but cover very different responsibilities.
For CIOs, IT directors and procurement teams, a useful RFQ connects the technical estate with business priorities. It should identify what must keep operating, who approves changes and what evidence will show that the work was completed. Use the following checklist before requesting legacy systems support.
1. Describe the actual platform and dependencies
List product names, versions, operating systems, hardware models and major applications. For AIX, include the technology level and service pack if known. For Notes and Domino, identify server and client releases, NSF applications, replication and mail-routing dependencies. For HP-UX, describe the hardware, storage and any Serviceguard clustering.
Include a high-level architecture diagram if it can be shared safely. Identify dependencies such as directory services, databases, network links and backup tools. If information is incomplete, say so and ask for a discovery phase. An accurate statement of uncertainty is more useful than an unsupported assumption about compatibility.
2. Define support coverage separately from response targets
State required service hours, time zone and whether work is remote, onsite or mixed. Describe how incidents are reported and who determines their business priority. Distinguish a response target from a resolution target. A provider can acknowledge an incident before its root cause, vendor dependency or recovery path is known.
Ask how planned maintenance, after-hours work and specialist escalation are handled. If standby coverage is required, request that it be priced separately from active engineering time. Do not assume a low hourly rate includes an unlimited availability commitment.
3. Separate recurring support from project work
List the tasks you expect in the ongoing service: administration, health reviews, troubleshooting, monitoring review or documentation. Identify upgrades, migrations, recovery tests and application development as separate items where appropriate. A long-term agreement should explain how new work is estimated and approved.
For an existing internal IT team, a co-managed arrangement may be appropriate. Specify which team owns tools, access approval, vendor cases, backups and production changes. Shared support works better when responsibility is written down rather than inferred from a job title.
4. Set access and change-control requirements
Describe how approved engineers will connect, how permissions are authorized and when access expires. Identify security checks or confidentiality requirements that apply. Avoid putting passwords, private keys or restricted configuration exports into a general RFQ or inquiry form.
For changes, name the approval process, maintenance window, backup prerequisites and rollback expectations. Failover or recovery testing should have an agreed plan and application-owner participation. The RFQ should ask providers to explain what they need from your team before they can commit to the work.
5. Ask for concrete deliverables
A health review might produce an environment inventory, findings register and prioritized recommendations. An administration engagement might require a work log, incident summary and updated operating notes. A recovery exercise should produce documented observations and follow-up actions, not merely a statement that a test occurred.
Ask each bidder to identify assumptions, exclusions, named dependencies and acceptance criteria. Request a clear process for handling unexpected findings. This makes it easier to compare the work being offered and limits surprises after the engagement starts.
6. Compare the complete commercial scope
Review the hourly or fixed fee alongside included hours, minimum commitments, travel, standby, tools and licensing. Ask what happens when demand exceeds the estimate and how overtime is approved. Vendor support, software entitlements and replacement hardware may remain separate customer responsibilities.
Use release-appropriate IBM AIX documentation or Domino documentation to identify technical prerequisites. Documentation is a reference; it does not establish that a particular historical release is currently supported or that a provider has vendor authorization.
Start with a scoped conversation
ITMS2 LLC can discuss IBM AIX, HP-UX and Notes and Domino requirements. Share the platform, business priorities and desired support term through our consultation page. Scope, specialist availability, deliverables and fees are confirmed before an engagement.

