To create a project, navigate to /projects and click the Create button.
The below details will need to be filled before clicking save
Project Name- used as a reference throughout Odin
Location- used to determine travel times between sites for scheduling daily workloads to teams
Material Store- used to reference material pick up locations (when creating materials for projects the store locations will default to this place)
Priority- used to set the priority in which projects should be worked on. The default value is the 1 step increment of the amount of projects existing when the project is created
Feasible Start- used to determine when project works can start and resources can be assigned. The default value is the project creation date
Feasible End- used to determine when project works need to be completed by resources. The default value sis the
Feasible Start+ 3 months (84 days = 28 x 3)
Handover- used to determine when documents should be handed over to the client. The default value is
Feasible End+ 28 days
Liability Release- used to identify when liabilities of project work are no longer the resources or the clients. The default value is
Feasible End+ 365 days
Contract- used to determine the group of financial rates and financial time frames to automatically apply on running completions of work. The default (
Disconnected Ledgers) means no financial options will be automatically applied during the recording of completed works and they will all need to be manually set or created. See Creating A Contract to make groups of finanical rates and time frames
Work Zone- used to identify the geographical zoning where the project is based
Completed Date- used to mark the actual completion date of the project. This will remove the project from the main list but is easily accessible by using the
Optionsbutton in the main project list
Contacts- used to identify contacts for the project. Very useful for foreman, supervisory or engineer level contacts as these are represented in the /updates and become available to resources working on the projects
Files- used to store files and link them specifically to this project. Each file has a limit of 100 mb but can be increased if the expectation is going to be greater. Please contact our support team if you wish for this to be increased. A vast range of file types may be uploaded, if any get rejected please contact our support team and we'll look into making that file type supported. These files also become available to resources working on the projects and it is not suitable for financial data as it is permissioned to be available to the lowest level of workers. Financial file uploads may be kept in /financials
Project Document Links- used to reference information on the web to the projects. Can be used to store links to external platforms like Dropbox, OneDrive and Google Drive
Creating a Discipline - Disciplines are the next level down from a project and represent a type of work as explained in Creating an Organization Discipline. The disciplines created here specifically relate to this project. All works on a project that want to be recorded must reside in a discipline but Odin has automatic ways of creating these via
Tasks described below so they do not need to be pre-filled before getting particular and granular.
Creating a Task - Tasks are the next level down from a discipline and represent a small portion of work to be performed. Tasks are usually a type of work (a discipline) and when related to each other they will absorb the financial and time constraints of the discipline. Once related, Odin will re-align the discipline on the project to absorb that amount in its quantities. Where tasks have been created and related to a type of discipline that does not exist on the project but does exist on other projects, Odin will create the discipline automatically. There is no need to create project disciplines if tasks are ideally preferred, Odin will build the discipline with default parameters which can be later configured.
If similiar projects already exist in the list, Odin can clone these to make projects with the same attributes and workloads. These may be used for a number of reasons, as tests or as new projects. Once cloned you may edit these to tweak them to their particular grade. If you structure your projects and tasks cleanly this can save a lot of time.