
A maintenance software provider should explain what its application does and who uses the output. A software function, maintenance decision and technical approval are different responsibilities.
Describe the product and services
Identify the legal business, product ownership, customers and deliverables. Explain implementation, migration, interfaces and configuration. State the limits of the software’s role accurately rather than implying it grants maintenance authority.
Separate software errors and security events
Ask about incorrect output, migration errors, outages and security events as distinct concerns. Describe hosting, customer data rights, outside suppliers and integrations. A cyber or technology policy name does not prove that all these exposures are covered.
Review releases and customer promises
Send contracts, support terms, availability promises and indemnities for review. Explain responsibility for new releases and customer configuration. Include data portability and access when service ends. Retain project and version records needed to explain earlier work.
Prepare the BWI review
Gather the service description, locations, property values, staff roles, agreements, current policies and factual claims history. Explain proposed changes and the date they will start.
Compare the actual limits, deductibles, exclusions, insured parties and activities. Ask which requested terms are accepted and what remains outstanding. Keep the final documents and reporting instructions with the business records.
Request a commercial aviation insurance review from BWI for the operation described above. Availability and terms require an individual review.
Continue Reading
