Ramses is still under active development, and this documentation is still being written.
As Ramses is able to (automatically) estimate the time needed for the production of the individual assets and shots, it can help you plan the production, and keep track of the time needed to produce any project.
At the step level, default estimations can be set to be used on shots and assets, depending on the difficulty of their productions. Then, each individual estimation can be customized for a finer evaluation of the time needed for the production.
To establish a realistic schedule, it is important to be able to estimate the time needed to produce the project, as well as tracking the production to adjust these estimations if needed.
Ramses helps you to quickly estimate this time needed, and then helps you to make it as precise as you need.
The unit used for estimations by Ramses is the day (which can be divided into smaller parts of a day if you need). Counting in days is precise enough for planning a production, and this way you don’t need to know exactly how many hours are (actually) worked in a day.
But when Ramses tracks the production, the data it gathers is actually in… Seconds. To make things simpler, the time spent on each task is actually displayed and calculated in hours. Time tracking can’t be done in days like the estimation, as the user may work on many different tasks the same day. Consequently, Ramses needs to be able to convert the actual hours spent on a task to days to be able to compare this value with the estimation (and warn you if you’re late). As it would not really make sense to define an arbitrary number of hours per work day (as Ramses measures actual time spent, but never knows if the user is eating, going to the toilets, sick or just working as he should without any break (that’s a joke)), Ramses rounds all that data to fractionnal days; this makes the measurement of the time spent less precise for individual tasks, but works quite well globally for the whole project, and thus to compare with estimations; the algorithm should work no matter what the official duration of a working day is (if it’s more than 5-6 hours and less than 12).
There’s no way with Ramses to link the production tracking data to individual users (meaning that there’s no easy way to build statistics about users or compare their productivity). That’s by design, don’t ask for it.
For each step, it is possible to set a default estimation which will be used for all assets and shots.
This estimation, usually set in days of work, can vary with the difficulty for the production of each specific asset or shot; Ramses lets you define an estimation for five predefined levels of difficulty: very easy, easy, medium, hard, very hard.
This default estimation is used to automatically evaluate the time needed for the production of the whole step, depending on the assets or shots which have to be produced, at first based on a medium difficulty. Adjusting the difficulty per shot or asset will then automatically update the global estimation to raise the precision.
For the production of shots, the estimations can also be optionnaly and automatically multiplied by the duration of the shot, so that the estimation can be made per second instead of per shot, and also by the number of assets used by the shot, for example to multiply the estimation by the number of characters in the shot.
Asset and shots estimations
The estimation set by default by the step and automatically computed based on the number of assets, the duration and the difficulty can always be individually overriden for each shot and asset, for a more precise control on the estimations.
This is done through the Production Tracking
Based on the estimations, Ramses evaluates the number of days of work needed to complete the work on each step for all assets and shots.
It is then easier to prepare the production planning and establish a schedule, by assigning days of work to users and steps.
Ramses will keep track of the number of days already assigned and missing (or extra) days to help you plan the production.
In case of lateness on the production of a step (shown by Ramses), it means the quantity or the diffuclty of the work was underestimated; all that needs to be done is then to adjust the estimations at the step level to update all assets and shots estimations, then check if the schedule can still be respected, or assign more users or days of work to the step.