City Power Integration Project

 City Power were in need of an ESB (Enterprise Service Bus) to eliminate data silos in the whole organization and eases interaction between multiple platforms while standardizing communication with City Power’s services through management and transparency of calls through an API Management.

Challenges

 Lack of proper integration at City Power contributes to the following challenges:

• Point-to-Point connections
  • Non-standardized, and unmanaged direct point-to-point connections to transactional systems data sources.
• Increased Latency
  • Due to multiple connections to data sources, transactional systems have seen increased latency in the services they provide.
• Non-Standardized System Interaction
  • City Power allows access to systems via access to data sources those systems use because of a non-existent route to access resources within systems (e.g., webservices and APIs)
• Unvalidated data in data sources
  • Due to the lack of contracts in between systems and wrapper mechanisms that would allow pre-validation, data at systems in of low quality and missing elements they should contain.

Outcome Achieved

 ESB solution addressed City Power needs which includes seamless integration, elimination of data silos, secured single point of access to data. The solution covered the following:

1. Eliminated Point-to-Point, spaghetti code.
2. Introduced reusability of interfaces.
3. Integrated to any system.
4. Enable an Agile IT delivery approach, through DevOps (build, test, deploy).
5. Created microservices and APIs, quickly and easily for:
   1. mobile apps
   2. web apps
   3. 3rd party integration

6. Decoupling: One of the most important things that were achieved via ESB is to decouple clients from service providers.
7. Transport Protocol Conversion: Solution accepts one input protocol and communicate with another service provider on a different protocol.
8. Message Enhancement: ESB allow isolation of the client and make some basic changes to the message. For example, changing date format of incoming message or appending informational data to messages.
9. Message Transformation: ESB transform an incoming message into several outgoing formats and structure.
10. Security: ESB protect services from unauthorized access.
11. Process Choreography & Service Orchestration: ESB manage process flow and complex business services to perform a business operation. Process choreography is about business services while service orchestration is the ability to manage the coordination of their actual implementations. It is also capable of abstracting business services from actual implemented services.
12. Transaction Management: ESB enables the ability to provide a single unit of work for a business request, providing framework for coordination of multiple disparate systems.
    
    

TIBCO Tools Used

1. TIBCO Business Works
   ESB was used to create integrations processes between various City Power systems (internal and 3^rd party systems)

2. TIBCO EMS
   This is a messaging tool which transports transactions and crucial for scenarios where delivery of a transaction needs to be guaranteed.

3. TIBCO Enterprise Administrator (TEA)
   Tea is being used to monitor and administer the different integration services, it makes easy to track transactions and enables transparency regarding all the transactions flowing through City Power environment.

City Power BI & Case Management Project (To be delivered by June 2024)

City Power needed to implement a comprehensive Enterprise Business Intelligence – Big Data Analytics Platform (BI – BDAP) which will include a Data warehousing solution and a data Management Tool. The Business Intelligence – Big Data Analytics Platform shall consolidate, analyse and manage data from multiple and varied sources, including transactional data, structured and unstructured data. The platform shall provide enhanced reporting and analytical capability.

Our Process

We are developing a  management tool that will enable insightful, expedient monitoring of core business metrics