Semantic Database for Cloud Service Onboarding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing employee onboarding systems lack a well-defined structure and are too general, making it challenging to efficiently manage the provisioning and ongoing administration of software services across various vendors and interfaces.
Innovation Solution
A centralized IT service management system that utilizes a semantic database to link user accounts across different cloud services, reducing the need for repeated input of user information and enhancing the management of access rights and security levels.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If conventional employee onboarding systems are used, then basic automation of repetitive tasks is provided, but the systems lack a well-defined structure and are too general to efficiently manage provisioning and ongoing administration of software services across various vendors and interfaces
Solution Approach 1:
The patent segments the onboarding system into distinct modular components: a semantic database layer for structured data storage, an integration layer for vendor-specific connections, and application layers for specific onboarding scenarios. This segmentation provides both automation capabilities and clear structural definition, resolving the contradiction between automation extent and structure definition.
Solution Approach 2:
The patent introduces semantic data models and standardized parameters that transform unstructured vendor-specific data into structured, queryable information. By changing the parameter representation from generic to semantic, the system achieves both automation and structural organization simultaneously.
2Adaptability or versatility
If multiple cloud services from different vendors are integrated, then comprehensive service management is achieved, but varying user interfaces and data formats require high overhead to manage
Solution Approach 1:
The patent introduces a semantic database as an intermediary layer between multiple cloud service vendors and the onboarding system. This mediator translates and standardizes varying vendor interfaces and data formats into a unified semantic model, enabling multi-vendor integration while reducing management overhead through centralized data normalization.
Solution Approach 2:
The semantic data model serves as a universal interface that can represent data from any vendor in a standardized format. This multi-functional approach allows the system to handle diverse cloud services through a single unified framework, reducing the need for vendor-specific management logic.
3Ease of operation
If user accounts across different cloud services are manually managed, then individual service configuration is possible, but repeated input of user information is required and access rights management becomes inefficient
Solution Approach 1:
The patent implements preliminary action by creating a centralized semantic database that stores user information and access rights in a standardized format before provisioning to any cloud service. This pre-processing of data eliminates the need for repeated information input when configuring individual services, while maintaining configuration flexibility through the semantic model.
Solution Approach 2:
The system creates and maintains a master copy of user information in the semantic database, which can then be efficiently copied and transformed for provisioning to multiple cloud services. This copying approach eliminates repeated manual input while preserving the ability to configure individual service-specific parameters.
Data Source
AI summary
An information retrieval method for cloud service administration is provided. The method may include establishing a connection with a semantic database. In some embodiments, the semantic database is configured to store information for different cloud services, and the information includes information regarding a first cloud service and information regarding a second cloud service. In some embodiments, the information regarding the first cloud service includes a first entity information and the information regarding the second cloud service includes a second entity information. The method further includes transmitting to the semantic database a request to obtain information regarding an asset. Then the method may include receiving from the semantic database an indication that first entity information and the second entity information being linked and being both related to the asset.