Integration/API checklist for executives

As promised in our last blog, following is a checklist of important considerations for a CEO/executive for any integration/API type project.

I. Process/Data Mapping

  1. Develop workflow, process map, data map
  2. Workflow – Functional flowchart (End to end process)
  3. Process Map – High level diagram of APIs and connection
  4. Data Map – Data elements from each system or API

II. Assessment of API/Systems

  1. Obtain API and data access documentation – published or inquiry with support/technical team – not sales team
  2. Obtain access to Sandbox
  3. Bidirectional or unidirectional connectivity? One side is a closed system – what do I do? Vendor-provided options
  4. If the side receiving data in an integration doesn’t have API’s, figure out the best way to get data in. Try avoiding directly inserting records into tables. Bad practice!
  5. Import/Export options if no APIs
  6. Agree on possible data upload/download formats
  7. Road map for API or potential changes – must ask!  
  8. Case studies of other companies that used proposed APIs
  9. Agree on SLAs for throughput (e.g. 1000 TPS)
  10. How secure is the system?
  11. Data archival/purge policy

III. Technical considerations

  1. Cloud or On Premise Solution and the associated egress costs
  2. Scalable, maintainable architecture
  3. Capacity requirements – current, 2-year, 5-year
  4. Diagram of Technical Solution – Integrated w/Process Map
  5. Process to obtain API Key to facilitate transactions or use plain old login/password authentication
  6. Data formats supported (XML, JSON, plain text, other)

IV. Maintenance/support considerations

  1. Once implemented, who is going to manage & support? – internal/external
  2. IT oversight and periodic testing – Quarterly
  3. System upgrade/sunset review and API verification – As needed
  4. Contract for periodic maintenance, review, and error fixes – Quarterly
  5. Process owner data validation and procedure periodic check – Quarterly
  6. Strategic planning update to API monitoring and procedure – Annual
  7. All systems backward compatible?
  8. Telemetry – monitoring, automated health checks – must have!

 

In summary, the checklist above is not intended to be all-inclusive and rather a sample of a much larger traditional list. Assessment of stakeholder desires, level of effort, one time cost, recurring costs, and return on investment should be evaluated, balanced and monitored continually. Considerations like egress costs between data center and cloud are utmost important, and without due diligence, can easily throw integration projects over time and/or budget.

 

We would love to hear from you and welcome comments, ideas, and suggestions.  This will help everyone and make this an interactive process.