Our Products

Electronic Bonding Appliance (EBA)

PCI developed its Electronic Bonding Appliance (EBA) solution in 2002 to satisfy the three key requirements for customer ebonding: reliability, scalability and cost-effectiveness, and has been collaborating closely with leading telecom service providers to perfect it ever since.

The EBA is a full-featured, high-performance intercompany business process integration virtual appliance for service providers and their customers. It allows service providers, customers, and trading partners to quickly, securely and cost-effectively interconnect their systems. The EBA is pre-integrated and pre-tested with the leading service providers. The EBA has predefined application interfaces and adapters such as those for ServiceNow, Remedy and HP Service Center (Peregrine) so it can be quickly integrated with the service providers’ customers.

EBA can be deployed and managed anywhere. It uses proven frameworks such as Spring Boot and Apache Camel, making it easy to configure and deploy. For example, it may be deployed in a Docker container in the Cloud, or on a Windows or Linux virtual machine within a corporate data-center. With a distributed database, the EBA can be deployed in multiple data-centers to support real-time disaster recovery.

Using Groovy and reusable modules, it not only enables rapid data and process mapping, but also data mapping changes on the fly. For process mapping, it is capable to aggregate multiple messages into one message, and split one message into multiple messages for different destinations.

ServiceNow Adapter

A ServiceNow adapter is available that allows rapid integration to ServiceNow with zero ServiceNow development work required. The adapter uses a push-pull architecture and out-of-box ServiceNow API to pull tickets and updates from ServiceNow, and push tickets and updates into ServiceNow. The only work required in ServiceNow is to give the EBA proper access to ServiceNow.

Remedy Adapter

A Remedy adapter is available that allows rapid integration to Remedy with zero Remedy development work required. The adapter uses a push-pull architecture and out-of-box Remedy API to pull tickets and updates from Remedy, and push tickets and updates into Remedy. The only work required in Remedy is to give the EBA proper access to Remedy.