Skip to main content
The common uses are project reports and capacity estimates: how a project stands against its plan, and who likely has room for new project work.
Automatically enabled when you configure Moovila permissions in your agent workflow.

​
What it does

  • Read projects with Moovila’s own RPAX risk score, forecast date, status, owner and customer
  • Read a project’s phases and tasks, with work estimates, percent complete, dates, owners and predecessors
  • Read project budgets and the time logged against tasks
  • Read users and labor resource types, with each type’s daily task-hour target
  • Estimate each person’s capacity in the agent’s sandbox, with the rules Moovila’s Resource Capacity dashboard documents: a task’s remaining hours (its work estimate less its percent complete) spread evenly over its remaining working days, against the resource type’s daily target times the working days in the window
Neo only reads Moovila: its public API spec lists only read operations. An agent tells the technician what to change in Moovila, or, when Moovila’s PSA connector syncs the project, makes the change on that project in the PSA.

​
What the API leaves out

Moovila’s public API spec lists no field for a user’s own Target Work hours, scheduled events, calendar appointments, holidays, task assignees other than the owner, or user skills and a task’s Skills Required. So Neo’s capacity estimate uses the resource type’s target and the task owner, counts Monday to Friday as working days, and can differ from Moovila’s dashboard. Neo says so in its answer. Skills matching from Moovila is not possible.

​
Permission groups

Each group can be Disabled or Read Only. The one profile, Read Only, reads every group.

​
Setup

See Connecting Moovila to Neo.