Scoping an Atlantis integration with Aspen Mtell
An integration with Aspen Mtell is an implementation project. Confirm the required data flow, access rights and supported interfaces before treating it as part of the purchased solution. A named integration page is not proof of a prebuilt connector.
Define the records and ownership
Start with equipment identifiers, inspection observations and maintenance events. For each record, agree which system owns it, the identifier used to match it, the fields to transfer and when an update should occur. Keep the initial scope limited enough to test using representative data.
Read access and write access are different requirements. Ask the administrators of both systems to confirm the available interface, authentication method and permitted operations. Additional vendor licences or configuration may be necessary.
Test failure and reconciliation
Include duplicate records, missing identifiers, rejected updates and interrupted transfers in the acceptance test. Decide where failures are recorded and who can retry or correct them. A successful demonstration with one record does not establish that a recurring transfer is reliable.
Confirm how approved records, attachments, timestamps and status changes will be handled. Document the support boundary between Atlantis, the customer and the other software provider before the connection goes into service.