tech tech
IDmission Ada lovelance

We honor Ada Lovelace, nee Byron, the world’s first programmer.

Lord Byron’s only child, Ada was encouraged to follow her interests in mathematics and logic, because her mother wanted to protect her from following the “insanity” of her father. Ada worked on Charles Baggage’s general purpose mechanical computer – then known as the “analytical engine”, in the 1840s. She wrote extensive notes on her ideas for how the analytical engine could be used, including what is now recognized as the first algorithm intended to be carried out by the mechanical computer.

Ada – our cloud based platform is the core of our technology. INFORM connects to Ada over its API – as can other 3rd party applications. Ada comes with a service bus that enables it to connect to enterprise Systems of Record and 3rd party databases on demand.

Ada – Customer Centric Platform

IDmission Ada Customer Centric Platform

Click for more

Ada enables access to its capabilities via an API. This API is laid out as a business view of Ada’s world.

The CUSTOMER is at the core Ada – and hence the first API business object. CUSTOMERS have attributes, a Name, Date of Birth, a Social Security (or some other unique identifier) Number, Addresses, etc. The customer facing UI can collect the data required by this REQUEST and send to Ada as a CREATE_CUSTOMER_REQUEST – Ada will go through a sequence of steps, determine if the CUSTOMER already exists, determine if the data is sufficient, connect to 3rd parties to validate the data – and ON_BOARD the customer as a new CUSTOMER on Ada as well as on the Enterprise Core.

The second API Business Objects is the MERCHANT (the Service Provider) – similarly MERCHANTS have attributes, Name of Business, Address, Merchant Category Codes, Type of Payments accepted, etc.

When a CUSTOMER interacts with a MERCHANT, value is exchanged and a TRANSACTION results. This is the third Ada API Business Object. TRANSACTION Attributes include, Type of Transaction (Cash, Card, Check, Wallet etc.), Amount of Transaction, etc.

The MERCHANT needs to keep the CUSTOMER engaged so that the customer life cycle can be extend and the MERCHANT can enjoy a larger share of the CUSTOMER’S wallet. This requires ability to communicate value to the CUSTOMER (Specials, Offers) and increase Customer stickiness (Loyalty). MERCHANTS (or Service Providers) interact with CUSTOMERS in self service or via EMPLOYEES (or agents). These EMPLOYEES use APPLICATIONS on Point of Service DEVICES.

Thus, other Ada API business objects are: OFFERS, LOYALTY, EMPLOYEE, DATA, APPLICATIONS, DEVICES.

Each request on the API can require a series of sophisticated software steps to be executed before the results become available. These steps are carried out by reusable SOFTWARE COMPONENTS contained in the Ada toolkit. For example, on boarding a CUSTOMER may be executed by capturing an image of their ID document. This ID document will need to be normalized (de-skewed, straightened, cropped) using Machine Vision, then snippets of the image created so that OCR can be used to extract customer data (Name, Date of Birth, ID Number, Expiry Date, Address etc.).

MACHINE VISION, a BIOMETRIC ENGINE (capable of enrolling and authenticating Fingerprint, Face, IRIS, Voice), Optical Character Recognition (OCR), Intelligent Character Recognition (ICR), Document Capture and Management, Workflow Management, a BACK OFFICE and REPORTING Suite are examples of Ada reusable SOFTWARE COMPONENTS.

Ada is often required to connect to 3rd Party Systems, or to the Enterprise Core for purposes of data verification, augmentation or simply to deposit data into a System of Record.

Ada comes equipped with an Enterprise Service Bus and a large library of Adapters to enable this integration efficiently and easily. Building a new adapter is easily accomplished as well. IDmission routinely connects to 3rd parties as part of it’s own roadmap or at business requests – typically each certification is accomplished in a matter of a few days.