Oh goodness there is a lot of information here! Make a fresh cup of coffee / tea and then come back to read this.

This is the control center for all entity properties. The settings function the same for all entity types.

General Settings

This tab varies based on the entity. Here is a run-down of all the options you may see:

Constraint Countdown Formatting Rules

Configure the rules that drive conditional formatting (colors) for Constraints.

Users will see these color rules under Tools > Open Constraints > Grid View > Countdown Column.

Mask Settings

Configure codes for work packages, documents, and vendor data.

Naming conventions for the items will be auto-generated based on this configuration.
All auto-generated item numbers will be based on the Starting Sequence Number.
Check the Required Auto-Generation to remove users' ability to enter this number manually.

O3 recommends you contact us for assistance in this configuration. Email [email protected].

Data Requirements

Configure which fields are required to add a new entity item.

System Required - nope, you cannot change this. O3 requires these data fields for back-end identification.
Always Required - yes, you get to add other required fields besides the System Required to enforce your company's data standards. New items cannot be created without these required fields completed.
Required for Data Complete - this drives the dashboard measurement widgets called "data completion." Users can add a new item without completing the fields in this category, however, the dashboard widget will score it as incomplete. This is a good option to use when the process for initial creation calls for limited fields, but the end product should have more details to be considered complete or healthy.

Statuses

Control the status process options for the entity.

State - Optional configuration to accompany a status. These are pre-configured statuses that AUTOMATICALLY update dates in work packages (Ex: a status with a state of "Ready for Review" will update the "Ready for Review Date" in the work package . NOTE: States are hard-coded in O3 and cannot be modified.
Sort Order - Determine the sequence of items in the drop-down list.
Pre-Conditions - Requirements to enter the status.
Allowed Transitions - Drive the other statuses available once this status has been completed. Ex: Allow a status for an IWP to transition from "Initialized" to either "In Progress" or "In Development." This keeps users from skipping steps. Also an option to make transitions automatic.
Constraints - Option to automatically create a Constraint once the work package enters this status. Ex: automatically create a Safety Document Constraint once the IWP reached the "In Development" status.
Approvals - Option to automatically create an Approval once the work package enters this status. Ex: automatically create a Quality Approval once the IWP reached the "In Review" status.

Approval Types

Control the approval process with these options for each approval type:

Submitter Role - Only users assigned to this role can submit the approval type.
Approver Role - Only users assigned to this role can approve the approval type.
Status - You can skip this. Seriously. It does nothing.
Sort Order - Determines the sequence of items in the drop-down list.
Requires Assignment for Completion - Approvals must have an assignee in order to be completed.
Auto-Create - Approval is created as soon as the entity is created. Saves time!
Restrict Completion to Assignee - Only the assignee has the power to complete the Approval.

Constraint Types

Control the constraint process using these configurations:

Stage - Nifty way to group constraint types. This does not drive any status or dates.
Editor Roles - Only users assigned to this Role can edit and complete the Constraint.
Require Assignment for Completion - Constraint must have an assignee in order to be completed.
Restrict Completion to Assignee - Only the assignee has the power to complete the Constraint.
Hard Constraint - Entity cannot reach a "closed" state / status if a Hard Constraint is open. Constraints that are not hard are considered "Soft" and do not require completion.
Auto-Create - Constraint is created as soon as the entity is created. Saves time!

Delay Types

Delays are used to report on reasons that Work Packages are not complete or delivered on time. Delays are best used for non-planned events such as inclement weather.

Control the types of delays available for the entity:

Stage - Nifty way to group Delay Types. This does not drive any status or dates.
Editor Role - Only users assigned to this Role can edit the Delay.
Sort Order - Determine the sequence of items in the drop-down list.

Development Step Types

Control the steps required to complete a work package. Creating steps also allows you to measure completion of packages.

Sort Order - Determine the sequence of items in the drop-down list.
Auto-Create - Development Step is created as soon as the entity is created. Saves time! NOTE: this is not based on status.

Execution Task Types

Control the steps required to complete the task. Execution Tasks are most commonly used to track progression of field work.

Task Steps - these should be ordered to reflect the actual sequence of work.
Weight - these are the points that drive the execution completion percentage widget on dashboards. Tips: this works best if the total weight points equal 100.

Purposes

Control the purposes for the entity. A purpose is used to compliment descriptions, but is controlled via a drop-down list (whereas a Description is free text).

Purposes can be used as an additional category for a package (ex: underground work, aboveground work).