# US 2026/0311082 A1 · Workforce Realignment Based on Vulnerability Factor

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0311082 A1
- Document ID: US20260311082A1
- Status: Published application
- Kind: A1
- Application number: 19/098,856
- Filed: 2025-04-02
- Published: 2026-10-08
- Earliest claimed: 2025-04-02
- Assignees: Dell Products L.P.
- Applicants: Dell Products L.P.
- Inventors: Boris Shpilyuck; Igor Dubrovsky; Nisan Haimov; Eric Young
- Web page: https://patentgrep.com/patent/US20260311082A1

## CPC

- G06Q 10/063112: {Skill-based matching of a person or a group to a task}
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

A system can, for microservices, identify a vulnerability factor-based workforce selection policy that identifies respective numbers of developers and respective job grades of the respective developers that correspond to respective vulnerability factors. The system can identify respective technical complexity-based workforce selection policies that identify respective technical domains, respective numbers of developers, and corresponding respective skill levels for respective microservices of the microservices, identify respective technical complexity values for the respective microservices, determine the respective vulnerability factors for the respective microservices, and identify respective performance levels and respective expertise levels for respective developers from a workforce management system. The system can iterate over the respective microservices to assign the respective developers to the respective microservices, based on the vulnerability factor-based workforce selection policy, the respective technical complexity-based workforce selection policies, the respective technical complexity values, the respective vulnerability factors, the respective performance levels, and the respective expertise levels.

## Claims

### Claim 1

A system, comprising:
at least one processor; and
at least one memory that stores executable instructions that, when executed by the at least one processor, facilitate performance of operations, comprising:
for microservices in a microservices architecture, identifying a vulnerability factor-based workforce selection policy that identifies respective numbers of developers and respective job grades of the respective developers that correspond to respective vulnerability factors;
identifying respective technical complexity-based workforce selection policies that identify respective technical domains, respective numbers of developers, and corresponding respective skill levels for respective microservices of the microservices;
identifying respective technical complexity values for the respective microservices;
determining the respective vulnerability factors for the respective microservices;
identifying respective performance levels and respective expertise levels for respective developers from a workforce management system; and
iterating over the respective microservices to assign the respective developers to the respective microservices, based on the vulnerability factor-based workforce selection policy, the respective technical complexity-based workforce selection policies, the respective technical complexity values, the respective vulnerability factors, the respective performance levels, and the respective expertise levels.

### Claim 2 (depends on 1)

The system of claim 1, wherein the vulnerability factor-based workforce selection policy is determined based on user input data.

### Claim 3 (depends on 1)

The system of claim 1, wherein the vulnerability factor-based workforce selection policy identifies the respective numbers of developers and the corresponding respective skill levels for respective ranges of vulnerability factors.

### Claim 4 (depends on 1)

The system of claim 1, wherein the respective technical complexity-based workforce selection policies are determined based on user input data.

### Claim 5 (depends on 1)

The system of claim 1, wherein the respective technical complexity values comprise low complexity, moderate complexity, high complexity, and critical complexity.

### Claim 6 (depends on 1)

The system of claim 1, wherein multiple of the respective technical complexity values are assigned to at least one microservice of the microservices.

### Claim 7 (depends on 1)

The system of claim 1, wherein the respective technical complexity values correspond to the respective technical domains.

### Claim 8 (depends on 1)

The system of claim 1, wherein the respective technical complexity values are determined based on respective user input data associated with respective user accounts that are associated with ownership of the respective microservices.

### Claim 9 (depends on 8)

The system of claim 8, wherein the respective user input data is respective first user input data, and wherein at least one of the respective technical complexity values is determined based on second user input data associated with a second user account that differs from a first user account of the respective user accounts that is associated with the respective first user input data.

### Claim 10

A method, comprising:
identifying, by a system comprising at least one processor, a vulnerability factor-based workforce selection policy for microservices in a microservice architecture;
identifying, by the system, respective technical complexity-based workforce selection policies for respective microservices of the microservices;
identifying, by the system, respective technical complexity values for the respective microservices;
determining, by the system, the respective vulnerability factors for the respective microservices;
identifying, by the system, respective performance levels and respective expertise levels for respective developers from a workforce management system; and
iterating, by the system, over the respective microservices to assign the respective developers to the respective microservices, based on the vulnerability factor-based workforce selection policy, the respective technical complexity-based workforce selection policies, the respective technical complexity values, the respective vulnerability factors, the respective performance levels, and the respective expertise levels.

### Claim 11 (depends on 10)

The method of claim 10, wherein the respective vulnerability factors satisfy respective criterions of susceptibility of the respective microservices to containing errors.

### Claim 12 (depends on 10)

The method of claim 10, wherein the respective vulnerability factors are determined based on respective code complexities of the respective microservices, respective development profiles of respective contributors to the respective codebases of the respective microservices, and respective historical records of issues with the respective microservices.

### Claim 13 (depends on 10)

The method of claim 10, wherein the identifying of the respective performance levels and respective expertise levels for respective developers from the workforce management system is performed based on respective names of the respective developers and respective job grades of the respective developers.

### Claim 14 (depends on 10)

The method of claim 10, wherein the respective expertise levels are determined based on respective courses taken by the respective developers.

### Claim 15

A non-transitory computer-readable medium comprising instructions that, in response to execution, cause a system comprising at least one processor to perform operations, comprising:
ascertaining a vulnerability factor-based workforce selection policy for microservices in a microservice architecture;
ascertaining respective technical complexity-based workforce selection policies for respective microservices of the microservices;
ascertaining respective technical complexity values for the respective microservices;
determining the respective vulnerability factors for the respective microservices;
ascertaining respective performance levels and respective expertise levels for respective developers from a workforce management system; and
assigning the respective developers to the respective microservices, based on the vulnerability factor-based workforce selection policy, the respective technical complexity-based workforce selection policies, the respective technical complexity values, the respective vulnerability factors, the respective performance levels, and the respective expertise levels.

### Claim 16 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the respective developers have respective first numbers of maximum microservices assignments based on the respective performance levels, wherein the respective developers have respective second numbers of maximum microservices assignments based on the respective expertise levels, and wherein the assigning of the respective developers to the respective microservices satisfies respective maximum assignment criteria that are based on the respective first numbers of maximum microservices assignments and the respective second numbers of maximum microservices assignments.

### Claim 17 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the assigning of the respective developers to the respective microservices comprises:
creating a first mapping that associates the respective performance levels with the respective developers; and
creating a second mapping that associates the respective expertise levels with the respective developers.

### Claim 18 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the assigning of the respective developers to the respective microservices comprises:
ordering the respective microservices in a descending order according to the respective vulnerability factors, to produce an ordering; and
iterating over the respective microservices according to the ordering.

### Claim 19 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the operations further comprise:
after performing the assigning of the respective developers to the respective microservices, determining that at least one developer of the developers is not assigned to any of the microservices;
assigning the at least one developer to at least one of the microservices.

### Claim 20 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the respective developers have respective first numbers of maximum microservices assignments based on the respective performance levels, wherein the respective developers have respective second numbers of maximum microservices assignments based on the respective expertise levels, and wherein the assigning of the respective developers to the respective microservices comprises:
performing iterations of the assigning, wherein based on determining during a first iteration of the iterations that an assignment of at least one developer of the developers to the respective microservices failed,
increasing respective first values of the respective first numbers of maximum microservices assignments to produce a modified first number of maximum microservices assignments,
increasing respective second values of the respective second numbers of maximum microservices assignments to produce a modified second number of maximum microservices assignments, and
performing a second iteration based on the modified first number of maximum microservices assignments and the modified second number of maximum microservices assignments.
