DSaaS: UniVerse Integration

Functional Requirements: DSaaS (UniVerse Integration) #

Last Updated: October 28, 2024

See What’s Changed

Definitions and Interpretations

The following definitions apply:

Biza Guides
refers to the technical documentation hosted at https://guides.biza.io
Data Adapter
refers to the Data Adapter as specified within Biza Guides.
Data Mappings
refers to a set of rules that describe an alignment from the customer’s source system to the Data Adapter as documented in Biza Guides.
Principal
refers to a consumer whose data is being collected and shared by DSaaS via the Data Adapter API.
UniVerse
refers to the UniVerse Database configured for the Ultradata Ultracs™ 5.1 data structures.

UniVerse Router & Worker #

The DSaaS Data Router & Accelerator (DRA) tailored to the DSaaS UniVerse Integration.

Functional Requirement Category Requirement
U1 UniVerse Router & Worker Software packaging and support for UniVerse protocol connectivity.
U2 UniVerse Router & Worker Data Mappings between the UniVerse data structures and the Data Adapter specification for the purpose of fulfilling the Data Adapter functional requirements.
U3 UniVerse Router & Worker Maintenance and upgrade of Data Mappings from the UniVerse data structures to the Data Adapter specification.
U4 UniVerse Router & Worker Integration of Biza HaaS: Product Manager product detail to UniVerse product identifier for Account Information.
U5 UniVerse Router & Worker Integration Where coupled with DSaaS: Hosting, connectivity via Azure or Amazon PrivateLink, established to the prescribed UniVerse endpoint.
U7 UniVerse Router & Worker Optional add-on module by which archived Banking Transactions can be stored within a DSaaS data store and made available for CDR purposes.
U8 UniVerse Router & Worker Optional add-on module by which a username can be translated into a member ID via a BaaS API provided by the customer.
U9 UniVerse Router & Worker SIEM logging of UniVerse database read events.