Object Array Tag Indexing for Web Service Data Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional industrial control systems are unable to directly consume data in XML or JSON formats from web services, requiring developers to write complex algorithms to extract and transform data into tag-based structures, which is inefficient and requires new scripts for format changes.
Innovation Solution
An operations integration processor and engine that parses web service responses to identify objects and values, generating unique tag names for direct addressing in industrial control systems, eliminating the need for manual script writing and enabling seamless integration of data from diverse sources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional industrial control systems directly consume XML or JSON data from web services, then data integration capability is improved, but system complexity increases because developers must write complex algorithms to extract and transform data into tag-based structures
Solution Approach 1:
The patent introduces an intermediary component (data integration engine or adapter) that sits between the web service data source and the industrial control system. This intermediary automatically performs the complex extraction and transformation of XML/JSON data into tag-based structures, allowing the control system to consume web service data without developers needing to write complex algorithms. The intermediary handles the complexity internally while presenting a simple interface to the control system.
Solution Approach 2:
The system enables self-service by allowing the data integration mechanism to automatically adapt to different XML/JSON formats without requiring manual script writing for each format change. The integration engine autonomously parses, extracts, and transforms data from diverse web service formats into the required tag-based structure, eliminating the need for developers to repeatedly write and maintain transformation scripts.
2Adaptability or versatility
If developers write complex algorithms to extract and transform web service data, then data can be integrated into control systems, but application engineering effort increases and requires frequent script updates for format changes
Solution Approach 1:
The data integration engine performs self-service by automatically adapting to different data formats without requiring manual intervention. When web service data formats change, the engine autonomously parses the new format, identifies the data structure, and generates appropriate transformation logic, eliminating the need for developers to write and update scripts for each format change.
Solution Approach 2:
The system implements dynamic adaptation where the data integration mechanism can automatically adjust to changing data formats in real-time. The integration engine dynamically generates or modifies extraction and transformation algorithms based on the actual data structure received from web services, allowing the system to handle format changes without requiring pre-written scripts or manual reconfiguration.
3Adaptability or versatility
If manual script writing is required for each data format, then data extraction can be customized, but maintenance burden increases and integration efficiency decreases
Solution Approach 1:
The integration engine provides self-service by automatically generating customized data extraction and transformation logic based on the incoming data format. Instead of requiring developers to manually write scripts for each format, the engine autonomously analyzes the data structure and creates the appropriate extraction rules, maintaining full customization capability while eliminating manual script writing overhead.
Solution Approach 2:
The data integration engine implements a universal solution that can handle multiple different data formats (XML, JSON, and potentially others) through a single unified mechanism. This multi-functional engine eliminates the need for separate custom scripts for each format, allowing the same integration component to adaptively process diverse data sources while maintaining customization through automatic format detection and transformation.
Data Source
AI summary
An operations integration processor generating tag names from an array of objects in a language-independent data format different than a tag format for integration with a tag-based control and data acquisition system. The operations integration processor receives a response from a web service and parses the response to identify one or more objects and corresponding values in the array contained in the response. The response includes an array of objects and is in a language-independent data format different than a tag format. The processor configures a selected object of the array to act as a unique index for the array of objects and generates one or more tag names from the parsed response. The tag names each represent a tag having at least one of an object and a value associated with it based on the information provided in the response. The generated tag names include the selected object in an array index part thereof.