Granted Patent B2

US 12,411,815 · App. 17/493,443 · Granted Sep 9, 2025

Inventors: Michael Polen (Tampa, FL); Zoran Navratil (Colorado Springs, CO); Maria Nina Abaya (Elkridge, MD)

Assignee: Allstate Insurance Company

G06F16/211G06Q10/067

Abstract

Claims (76)

1. A system comprising:

a central repository system comprising a processor, a subset design and simplification layer configured to directly generate one or more generated subset schemas from one or more canonical models without creation of an intermediate respective canonical model fragment for each generated subset schema, and a memory communicatively coupled to the processor, wherein one or more computer-readable instructions are stored in the memory;

the one or more canonical models managed by the central repository system,

wherein the one or more canonical models comprise one or more structured elements, and

wherein the one or more structured elements comprise one or more simple elements; and

the one or more generated subset schemas, wherein the one or more generated subset schemas comprise one or more elements based on the one or more structured elements or the one or more simple elements from the one or more canonical models, wherein the one or more elements of the one or more generated subset schemas are forward engineered from at least one canonical model of the one or more canonical models;

wherein the one or more computer-readable instructions are executable by the processor such that the central repository system is configured to design, record, and generate the one or more generated subset schemas by further applying one or more simplification rules of the simplification layer to a generated subset schema of the one or more generated subset schemas to generate a simplified generated subset schema as a new product flattened to comply with the at least one canonical model and consume fewer processing resources than when not flattened, the new product comprising one or more of applications, executables, or application programming interfaces as a customized new schema, wherein said forward engineering comprises generation of the new product by the one or more canonical models of the central repository system, wherein the generation of the new product comprises a direct design of the customized new schema through said forward engineering.

2. The system of claim 1 , wherein the central repository system is configured to facilitate the design, the recording, and the generation of the one or more generated subset schemas by:

generating at least one of a collapse of an associative element, a reduction to cardinality of a relationship between two structured elements, a collapse of a 1:1 element, a collapse of a supertype element, a collapse of a subtype element, or a collapse of a repeating end branch element into an array.

3. The system of claim 1 , wherein the central repository system is configured to said design, said record, and said generate the one or more generated subset schemas by managing content synchronization rules between selected subset schemas of the one or more generated subset schemas wherein the content synchronization rules perform at least two of:

govern content integrity between an independent subset schema and a dependent subset schema;

govern content integrity of two overlapping subset schemas;

govern content integrity between two content equivalent subset schema;

govern content integrity between two mutually exclusive subset schemas; and

enforce layout simplification compatibility between a plurality of the selected subset schemas.

4. The system of claim 1 , wherein the central repository system being a design and sourcing system to said forward-engineer and generate the one or more generated subset schemas from the one or more canonical models enables the central repository system to create and store internal data object mappings and record simplifications applied to a subset schema wherein the central repository system is operable to programmatically generate data object mappings and data object transformation logic between data objects in the one or more generated subset schemas and their corresponding data objects in the one or more canonical models.

5. The system of claim 1 , wherein the central repository system is configured to broker data exchange between any two generated subset schemas of the one or more generated subset schemas using the programmatically generated data object mappings and the data object transformation logic.

6. The system of claim 1 , wherein the central repository system is configured to manage content of the one or more generated subset schemas wherein the managing the content comprises including data objects from an enterprise model in combination with data objects from one or more local models.

7. The system of claim 6 , wherein the managing the content comprises sanctioning and promoting a data object from a local model to an enterprise model.

8. The system of claim 1 , wherein the central repository system is configured to customize a customized subset schema layout wherein the customized subset schema layout may include a repeating structured element a plurality of times wherein each instance of the repeating structured element may be comprised of different simple elements.

9. The system of claim 8 , wherein the customizing the customized subset schema layout comprises dynamic complex types to enable the inclusion of the repeating structured elements, wherein each repeating structured element in the customized subset schema layout can be comprised of different simple elements.

10. The system of claim 8 , wherein the customized subset schema layout comprises a custom team element configured to group data objects from across any combination of one or more local models and an enterprise model.

11. The system of claim 8 , wherein the customizing the customized subset schema layout comprises substituting a structured element with an element pointer.

12. The system of claim 1 , wherein the central repository system is configured to manage a plurality of role names for an element wherein the plurality of role names promote contextual naming and usage of data objects and allow for tracking implementation of an underlying enterprise element while supporting precise contextual support.

13. The system of claim 12 , wherein the plurality of role names enable a structured element to comprise a simple element a plurality of times.

14. The system of claim 1 , wherein the central repository system is configured to manage enhanced metadata to enable the central repository system to generate a relational data model of a subset schema wherein the generated relational data model is operable to include at least eight of: independent entities, dependent entities, associative entities, supertype entities, subtype entities, subtype groupings, subtype grouping type, subtype grouping members, bi-directional relationships between entities, relationship cardinality of relationships between entities, relationship optionality of relationships between entities, parent-to-child relationship phrases, child-to-parent relationship phrases, attributes, attribute data types, primary keys, alternate keys, business keys, and foreign keys.

15. The system of claim 14 , wherein the subset schema represented by the generated relational data model is a simplified subset schema forward engineered by the central repository system from the one or more canonical models.

16. The system of claim 1 , wherein the central repository system is configured to manage data quality rules through a governship process wherein each element of an enterprise model is subject to at least two of: a governed state, a compliance state and a programmatically assigned element definition state.

17. The system of claim 16 , wherein the data quality rules further manage a subset implementation state for each subset schema defined in the central repository system through production implementation rules wherein the subset implementation state of the subset schema is a variable to the programmatically assigned element definition state of each enterprise element the subset schema comprises.

18. The system of claim 16 , wherein the data quality rules allow for the one or more generated subset schemas to contain enterprise compliant elements in combination with authorized enterprise non-compliant elements.

19. The system of claim 18 , wherein the data quality rules support recording of replacement elements and resolution plans for non-compliant elements.

20. The system of claim 1 , wherein the central repository system is configured to record sample values of data objects and display the sample values in a central repository interface to drive efficient object selection.

21. The system of claim 1 , wherein the central repository system is configured to:

record sample value streams for the one or more generated subset schemas; and

generate sample data records compliant with the one or more generated subset schemas.

22. The system of claim 1 , wherein the central repository system is configured to produce a generated subset schema of the one or more generated subset schemas in a plurality of executable formats wherein the plurality of executable formats comprise at least one of:

Avro Schema Definition;

JavaScript Object Notation (JSON) Schema Definition;

Java Class Definition;

XML Schema Definition (XSD);

.Net Class Definition; or

Data Definition Language.

23. A method comprising:

operating a central repository system comprising a subset design and simplification layer configured to directly generate one or more generated subset schemas from one or more canonical models without creation of an intermediate respective canonical model fragment for each generated subset schema, to manage the one or more canonical models;

applying, by the central repository system, one or more simplification rules of the simplification layer to a generated subset schema of the one or more generated subset schemas to generate a simplified generated subset schema, wherein the simplified generated subset schema comprises one or more elements of the one or more generated subset schemas that are forward engineered from at least one canonical model of the one or more canonical models managed by the central repository system; and

generating the simplified generated subset schema as a new product flattened to comply with the at least one canonical model and consume fewer processing resources than when not flattened, the new product comprising a customized new schema in one or more executable formats, wherein the new product comprises one or more of applications, executables, or application programming interfaces, wherein said forward engineering comprises generation of the new product by the one or more canonical models of the central repository system, wherein the generation of the new product comprises direct design of the customized new schema through said forward engineering.

24. The method of claim 23 , wherein the one or more executable formats include at least one of:

Avro Schema Definition;

JavaScript Object Notation (JSON) Schema Definition;

Java Class Definition;

XML Schema Definition (XSD);

.Net Class Definition; or

Data Definition Language.

25. The method of claim 23 wherein the one or more simplification rules comprises at least two of:

collapsing an associative element;

reducing cardinality of a relationship between two structured elements;

collapsing a 1:1 element;

collapsing a supertype element;

collapsing a subtype element; or

collapsing a repeating end branch element into an array.

26. The method of claim 25 , wherein the central repository system is configured to enforce layout simplification compatibility between a plurality of selected subset schemas of the one or more generated subset schemas.

27. The method of claim 23 , wherein the central repository system is a design and sourcing system to said forward-engineer and generate the simplified generated subset schema enabling the central repository system to programmatically generate data object mappings and data object transformation logic between data objects in the simplified generated subset schema and their corresponding data objects in the one more canonical models.

28. The method of claim 27 , wherein the central repository system is configured to broker data exchange between generated subset schemas of the one or more generated subset schemas by using the programmatically generated data object mappings and the data object transformation logic generated by the central repository system.

29. The method of claim 27 , wherein the central repository system is configured to:

manage enhanced metadata; and

generate a relational data model of the simplified generated subset schema.

30. The method of claim 27 , wherein the central repository system is configured to:

record sample value streams for the simplified generated subset schema; and

generate sample data records compliant with the simplified subset schema.

31. A method comprising:

directly designing, recording, and generating one or more generated subset schemas from one or more canonical models via a subset design and simplification layer of a central repository without creation of an intermediate respective canonical model fragment for each generated subset schema, to manage the one or more canonical models, wherein

the one or more canonical models are managed by the central repository system and comprise one or more structured elements, and wherein the one or more structured elements comprise one or more simple elements, and

the one or more generated subset schemas comprise one or more elements based on the structured elements or the one or more simple elements from the one or more canonical models;

forward engineering the one or more elements of the one or more generated subset schemas from at least one canonical model of the one or more canonical models;

further applying one or more simplification rules of the simplification layer to a generated subset schema of the one or more generated subset schemas to generate a simplified generated subset schema; and

generating the simplified generated subset schema as a new product flattened to comply with the at least one canonical model and consume fewer processing resources than when not flattened, the new product comprising a customized new schema in one or more executable formats, wherein the new product comprises one or more of applications, executables, or application programming interfaces, wherein said forward engineering comprises generation of the new product by the one or more canonical models of the central repository system, wherein the generation of the new product comprises direct design of the customized new schema through said forward engineering.

Assignments (1)

Continuity (1)

References Cited (69)