Skip to main content
Planning & scheduling engine

Every resource in the right place, at the right time.

Crona helps plan operations where everything competes for the same resources. It searches for feasible plans within the model and constraints you define, and points to conditions worth reviewing when it cannot find one. You can describe what changed in natural language.

What Crona solves

An optimization solver brought to real operations. The engine computes the proposal within the model, and AI helps people interact with it.

Plans for better decisions

Solve time depends on problem size, data, and objectives. You can review an intermediate solution or give the solver more time to explore alternatives.

Explicit constraints

Shifts, skills, preferences, and maintenance windows become part of the model. If the conditions do not admit a plan, Crona helps identify the conflict for review.

Context-aware replanning

When absences, emergencies, or last-minute changes occur, you can evaluate a new proposal from the current state and compare what changes.

Before & after

The difference between covering and deciding

With the same team and rules, Crona lets you compare assignments, costs, and priorities before confirming a plan.

How do I plan weekly shifts and coverage?

Assigned staffing / required staffing per shift.

Feasible plan ready to execute

Coverage conflicts

9 → 0

Overtime hrs / week

42 → 18

Last-minute changes

14 → 4

Manual plan

ShiftMonTueWedThuFri
Morning
3/2
1/2
2/2
1/2
2/2
Afternoon
1/2
1/2
0/2
1/2
1/2
Night
1/1
2/1
1/1
1/1
0/1

Optimized plan

ShiftMonTueWedThuFri
Morning
2/2
2/2
2/2
2/2
2/2
Afternoon
2/2
2/2
2/2
2/2
2/2
Night
1/1
1/1
1/1
1/1
1/1

Automatic replanning after a disruption

Tuesday 1:20 pm · Key technician unexpectedly absentNew plan in 42 seconds
  • Activates the shift's backup technician
  • Reassigns committed visits
  • Resequences the rest of the week

The AI layer

Talk to Crona

The solver computes a proposal within the model. AI can serve as an interface for describing changes and reviewing alternatives in natural language.

  • Tell it what changed

    «The morning technician called in sick», «an urgent request arrived». Crona can evaluate a new proposal from the state you have modeled.

  • In the channels you already use

    The interface can adapt to the work channel we define for the case, together with the controls needed to review each proposal.

  • A contextual interface

    AI translates a request into the model, the solver computes, and the response shows which proposal was evaluated and under what conditions.

Crona in your chat
The afternoon technician called in sick and the 3:00 pm task moved up an hour.
Illustrative proposal: Maria covers the afternoon shift within her working hours. Equipment 2 is ready at 2:00 pm and the 4:30 pm inspection moves to station 4. Review the proposal before confirming it.

Illustrative: this shows how a request could be translated into the model and returned as an explained proposal.

Examples of resources and constraints

People, tasks, and capacity in one model

Crona models scarce resources, priorities, and time-based rules. Healthcare is one illustrative example, alongside field operations, services, and production:

People and shifts

Assign people according to availability, skills, working hours, and service priorities.

Equipment and maintenance

Coordinate equipment, maintenance windows, and tasks while keeping available capacity in view.

Tasks and priorities

Sequence tasks around urgency, dependencies, timing, and the resources that can perform them.

Appointments and capacity

Schedule requests into time windows and limited resources while making trade-offs visible.

Shared resources

Allocate stations, vehicles, rooms, or other resources across activities competing for them.

Changes and exceptions

Evaluate absences, urgent requests, and new constraints while keeping current work in view.

One approach for different operations

The same approach can model field shifts, production lines, services, and other allocation problems. Applicability depends on the case's data, objectives, and constraints.

An integration that fits your operation

Integration depends on your data, systems, and operating requirements. We can define an initial scope, test the model alongside your current process, and agree on a deployment path.

  • Change control to coordinate updates to the same plan
  • Security and access requirements defined for your context
  • Monitoring to review system status and solve time
  • Connection to your systems and work channels within the agreed scope
Your operation: demand, resources, rules
Crona: optimization solver
Feasible, explainable plan within the model

FAQ

Frequently asked questions

What operations teams ask us before evaluating a case.

Planning, allocation, and scheduling problems where people, equipment, tasks, capacity, skills, and time constraints interact. Healthcare can be an example, but it does not define the engine's scope.

A better way to plan your operation

Tell us which decision repeats, which resources constrain it, and what you want to improve. We will evaluate the case with your own data.

Let's talk