Job Profile Data Model for Cross-System HRM Collaboration

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current software products lack the ability to share job profile data across different systems within an organization, hindering collaboration and efficient hiring and training processes.

Innovation Solution

A job profile data model is developed that defines a common data structure for representing job profiles, allowing customization and facilitating data sharing between various systems and entities by establishing relationships between job profiles and related entities, using XML Schema and Web services standards within a universal business application network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If separate systems are used for HRM and ERM in different divisions, then each system can maintain its own data structure and customization, but data sharing and collaboration between divisions become difficult

Engineering Contradiction:

Improvesystem customizationVSAvoiddata sharing

Core Design Contradiction:

Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent implements a universal job profile data model that serves multiple systems (HRM and ERM) across different divisions. The JobProfile class and its attributes (JobProfileId, JobTitle, Department, Skills, etc.) are designed to be universally applicable, allowing the same data structure to be used by hiring agencies, training providers, and internal HR systems, thereby enabling data sharing while maintaining adaptability through optional custom attributes.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Device complexity

If no common data model is established, then system complexity remains low and implementation is simple, but collaboration between divisions and external entities is impeded

Engineering Contradiction:

Improvedata model complexityVSAvoidcollaboration efficiency

Core Design Contradiction:

Device complexityVSEase of operation

Solution Approach 1:

The patent segments the job profile data model into distinct, well-defined components: core attributes (JobProfileId, JobTitle, Department), skill-related attributes (Skills, Competencies), and optional custom attributes. This segmentation allows each division or external entity to work with only the relevant portions of the data model, reducing the perceived complexity while enabling effective collaboration through standardized interfaces.

Inventive Principle:

Principle #1Segmentation

3Adaptability or versatility

If job profile data is not standardized, then each entity can maintain its own data format, but data transfer and integration with external companies become difficult

Engineering Contradiction:

Improvedata format flexibilityVSAvoiddata integration

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a standardized JobProfile data model as an intermediary between different systems and external entities. Instead of requiring direct integration between each system pair, all entities can exchange data through the common JobProfile structure, which acts as a mediator. This maintains data format flexibility for each entity while ensuring reliable integration through the standardized intermediate format.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS8112296B2Modeling of job profile data

Publication Date: 2012.02.07 ORACLE AMERICAN INC

AI summary

A job profile class is defined that represents a job profile and identifies relationships of the job profile with various entities related to the job profile.