• Review existing governance process
• Identify key result areas for the integration team
• Identification of all governance processes in scope
• Identification of areas of tools automation
• Documents the mission, goals, and objectives
• Define team roles and responsibilities. Completely separate development from operational roles. Identify API consumer, API provider and API Operation teams. Identify API governance roles. Identify Data sources, data consumers, integration frequency, size, data owners & data security classification details.
• Define Operating processes & models. Describes how team interacts with other teams (e.g.: project team) and responsibility of each team in the delivery life cycle
• Define templates, forms and checklists to support the operating process (e.g. release management tools, capacity management, DevOps tools, checklist & processes)
• Define Standards and Guidelines

SOA

• Define SOA integration patterns
• Define service identification guideline (service ID, naming standards, service registry e.g.: register service name, description, source, target, owner, integration platform, documentation link etc. into SOA team SharePoint site)
• Develop guideline for integration technology selection (i.e.: when to choose API vs ESB based on integration criteria)
  Enhance current integration guideline for all the integration technologies that are used in the organisation (e.g.: SAP PI/PO, approved non- ESB/standalone Connectors, ETL)
• Enhance current integration guideline to include common frameworks (error handling, auditing etc.) and ensure alignment across integration technology
• Logging and monitoring guidelines: support proactive monitoring (e.g., strategies to integrate with incident management tool)

API

• Define API integration Patterns
• Schema Design & API Design, naming Guidelines API Security guidelines
• API Data sharing , data security guidelines Mobile app, IoT, API analytics and monitoring Guidelines
• API documentation, Community management guidelines

Data integration

• Data integration patterns & recipes
• Include data quality checking as part of guideline
• Define support processes for developing and maintaining data integration
• Develop guidelines / selection criteria for traditional data integration tools vs Hadoop/map- reduce/HDFS/big data tools
• SLA guidelines on how to track and communicate the SLA report to the management (e.g.: green status if the uptime of integration service is >95% and number of error incident caused by integration <10%)
• Knowledge management guidelines (e.g.: what to be included in technical specification, API documentation etc.; use of team SharePoint to hold functional and technical document and have it linked with integration registry)
• Communications Plan describes the strategy to increase awareness about SOA team governance and processes (e.g.: functional document, technical document, support procedure, performance report, testing result, service catalog and integration services registration etc.)
• Develop integration platform maintenance policy (periodical server/service restart, approval authority, patching schedule etc.)
• Community engagement plan -how to create a thriving ecosystem around TNB APIs. Business Models, private, public and partner APIs. Define measurable key result areas, metrics for team
• Continuous improvement plan