Core concepts

Deepleex is a system for planning and executing tasks/projects: you define the work, describe the resources (teams, people, roles, skills, schedules), and the system helps forecast deadlines and optimize resource allocation (this is the core of AI planning / AI-driven planning), while also monitoring execution and detecting conflicts.

Core logic

What a piece of work is built from Everything is usually structured in this chain:

• Project — the container for everything: work structure, team, files, chats, plan, analytics.
• Work hierarchy — a way to organize project content “on shelves”. In Deepleex you can structure it like this: project → section → requirement → task → work.
• Phase / Stage — a major milestone or part of the project, onto which you break down tasks to build a work plan by stages.
• Work plan (roadmap) — the selected view / assembly of activities and stages, according to which the system calculates deadlines / workload / budget.

Key entities (what you actually work with)

• Requirement — “what needs to be delivered” (often in the form of text + attachments). Can be broken down into tasks/works.
• Task — the unit of management that needs to be completed (usually has status, assignee, deadlines, effort estimate).
• Work — a more granular / atomic part of a task (convenient for detailed planning and more precise scheduling).
• Activity — a universal “work unit” (internal generalization of everything that is planned and moves through statuses; tasks/works often live as activities inside the plan).
• Resource storage — place for project files/artifacts (attachments, specifications, documents, etc.).

Team and resources

• Team — set of participants involved in the project/plan.
• Participant — a person (and in the system’s concept — in the future an “executor” can also be AI/program/device if registered as a resource).
• Profile / Role — “who they are in the project” (e.g. analyst, developer, tester) and what permissions they have.
• Skill — competence that can be taken into account when assigning work.
• Qualification — skill level/category (e.g. junior/middle/senior or point-based scale).
• Productivity — how fast a participant completes work (affects deadlines).
• Efficiency — actual performance metric (how well they meet the estimate/plan).
• Permissions — access rights to projects/entities/actions.

Planning

• AI planning / AI-driven planning — mode in which the system helps to:
  • forecast completion dates
  • optimize resource allocation
  • highlight conflicts and bottlenecks
• Effort / Labor intensity — estimate of work volume (hours/days/story points/conditional units).
• Work schedules — availability of participant/team (working days, shifts, vacations, constraints).
• Schedule conflict — situation when the same time slot is “sold twice” or work does not fit into available capacity.
• Gantt chart — time-based visualization of the plan (by phases/activities).

Execution: statuses and control

• Status model — set of states that tasks/activities go through (e.g. “To Do”, “In Progress”, “Blocked”, “Done”).
• Kanban — view of activities by status columns for daily management.
• Timesheets / time tracking — entering actual time spent, to compare plan vs. actual.
• Plan budget — cost calculation of execution (considering participant rates and effort), as well as overruns/savings.

Signals and “smart hints”

• Signal / Request — system event or trigger that requires attention (conflicts, risks, blockers, inconsistencies).
• “Requires attention” — list of problem areas: overload, availability conflict, risk of missing deadline, etc.
• Recommendations — suggestions from the system (e.g. propose team composition to meet deadline/budget, or suggest better work breakdown/sequencing).

Scenarios and processes

• Business process scenario — template/regulations describing how work is usually created and flows.
• Task creation from scenarios — quick launch of typical projects / work packages.
• Custom task states — ability to configure your own status workflow (if enabled in configuration).

Communication

• Global project chat — general channel for the entire project.
• Chats inside activities — discussions directly “inside the work”, for coordination and escalations.