Creating a Discipline

Project Disciplines reside in projects, therefore projects must first exist, see Creating A Project to get this done prior to creating project disciplines.

Project Disciplines hold the measure of works to be completed in a project. Odin sequences work relationships between other types of work using these disciplines. In an example where Odin is set to make a coffee, boiling water would be one of the first Disciplines, pouring the milk would be last and adding sugar would be in between them, this is the Chronological Order. Odin can get immensely complex with these relationships drawing multiple dependency lines to any singlular or combinational Discipline group. It will then enforce the designated time frames and/or time margins in this relationship across the matrix of dependency lines, ensuring that the Project Disciplines constrainted to numerous others will be worked only when all constraints have been released.

Odin becomes incredibly powerful with this information and will schedule the works accordingly to represent an achievable and ideal timeline where the order of operations isn't broken and in turn prevents wasted time, wasted efforts and risks to the utmost degree set by the organization profile. Odin conducts this everytime it automatically schedules works (using all updates received at that point in time) to alter the future plan so the ideal timeline is kept and the requirement to juggle operational dependency standards, any mix of delays, prompt completions, resource constraints and cascading projects is easily acquired and provided to the business without the armies of adminstration. To dictate these relationships.

Importantly Odin goes even further, with the Advanced Features in Disciplines Odin has the ability to recover broken timelines, late projects and direct resources to projects in strenously constrained conditions to secure timely completions. It will conduct all this effort while applying the operational recommendations and/or needs that the organization is a custom to.

To Create a discipline, navigate to /projects, and follow the below steps

  1. Select a project by clicking the checkbox and then clicking edit
  2. Scroll down to the Disciplines and Tasks
  3. Select the tab Resourcing and then Click Create
  4. A sidebar will appear on the right, fill the details below and Save

Required filling

  1. Discipline Name - used as a reference throughout Odin
  2. Description - used to describe the works involved and will be represented in different parts of Odin for reference and understanding od scope

Optional filling

  1. Proposed Work - Planned or proposed works for the Discipline, defaults to 0. May be accumulated automatically by Odin when creating Tasks See Creating a Task for more information
  2. Completed Work - Completed works, may be updated at a later date but does not initiate automatic ledger creation. Any values set here must have ledgers manually created to represent the monetary values. Only Task updates initiate automatic ledger creation, defaults to 0
  3. Multiplying Rate - Multiplier applied to profits and expenditures upon completion of works, defaults to 1. The multiplying rate is highly efficient when quoting a project under nominal rates but the organization would like to increase margins on specific disciplines because of specific hazards or circumstances without creating new sets charging rates. All automatically created ledgers will have total values equal to quantity x rates applied x Multiplying Rate, defaults to 1
  4. Chronological Order - The order in which the discipline is to be performed in comparison to the other disciplines in this project. If Workflow relationships exist and Operational Regime is set to Workflows, Workflow relationships will be evaluated and in any conflict of relationship, the Workflow relationship will be executed as the driver not the Chronological Order, defaults to count of current count of disciplines + 1
  5. Strict|Proposed Start - Start date of the project, the project will not be scheduled to start until this date. Selecting strict will ensure the project is started on this date unless all resources are completely constrained and aren't able to be altered in such a way that enables previous project constraints to met while starting the project on this strict date. In the case where there is no resolve the schedule will be set to its first possible date and the organization must force the project into a higher priority position to signal the importance of it superceeding others, defaults to Un-Checked - Off
  6. Strict|Proposed End - End date of the project, the project will be scheduled to end on this date. Selecting strict will push Odin to re-schedule the project if it falls late so this date is met. If all resources are completely constrained and aren't able to be altered in such a way that enables previous project constraints to be met, Odin will set the schedule to complete this project as fast as possible. To enable a better schedule the organization must force the project into a higher priority position to signal the importance of it superceeding others, defaults to Un-Checked - Off
  7. Consolidate Start Date - Optimizes for disciplines works to be started in simultaneous states with other disciplines to consolidate the spent time on a project instead of it being sporadic through the schedule of other projects. Ideal for a concentrated effort but can cause lower daily efficiencies in resource workloads as a day of work in between other projects could amount to appreciable project gains, defaults to Checked - On
  8. Consistent Resources - Attempts to keep multi-disciplinary resources on this project keeping the resource count on this project as low as possible, defaults to Un-Checked - Off
  9. Recovery Permission - Gives Odin permissions to interchange user selected resources to Recover the project when running late, while its first option is always to keep the original resources intwined with the project it may be ideal for the whole of the schedule and the specific project to interchange the resource with faster options, defaults to Checked - On
  10. Auto-Assign Tasks - Assigns created tasks in priority to resources of its choosing. Manual administrative assigment will otherwise be required, defaults to Checked - On
  11. Operational Regime - Consectuive will force the Chronological Order of each Discipline to be obeyed. Workflows will force the Workflow relationships to be obeyed, defaults to Consecutive
  12. Environmental Rating - The hazard rating of the environment. Odin will acknowledge the delay in hazardous environments by forecasting in excess time for the resource to complete their activities. Practically compensating for slowed completions in their activities. This rating will be the multiple of extra time to be allocated, defaults to 1
  13. Resource Combination Limit - The total maximum resource count allowed on this discipline. Ideal if its desired the discipline work doesn't dispearse excessively and keep resource cross over to a maximum threshold, defaults to 1

Creating a Discipline (Smart Option A.)

If a similiar project already exist in the list, Odin can clone these to make the discipline with the same attributes and work. Once cloned you may edit these to tweak them to their particular grade

  1. Select a discipline
  2. Click Clone in the right sidebar
  3. Tweak as desired
  4. Finally click Save