Opus Inspection’s modern design utilizes a service-oriented architecture (SOA). This architecture applies defined business functionalities built as software components to create interoperable services. SOA provides a well-designed interface protocol for integrating disparate applications that is flexible enough to anticipate future change. SOA makes data available as a service and links the data access services to business rules to ensure correct data processing and verification as shown in the figure below.
Consistent with today’s typical policies and standards, all inter-system data transfer is constructed as SOA services that are utilized by uVID business functions. This includes the inspection data, which is transmitted in XML format over HTTPS via a SOA service. On entry into the uVID, business rules and data validation are applied on inserting the record into the transactional database. From there, ETL processes generate real-time data for use in the reporting database. An additional layer of data integrity validation occurs between the services and the databases. For example, the database enforces foreign key constraints to ensure relational integrity in the database.
Opus Inspection applies these same techniques and approach in sharing data with other data sources and systems. In the case that any legacy data source or system cannot operate under SOA and XML Web services, we implement additional custom interfaces atop the SOA layer to support data transfer. Our clients can choose to utilize the SOA service directly, or we can deploy a new, alternate connection between the client system and our SOA service. Thus, uVID will be ready to connect with the next generation of such systems without necessitating future changes. Our uVID system, out of the box, prepares our clients for the future.