Entering Quantities via the Productivity Editor A General best practice is to enter quantities in the time module while you are coding time for a crew.  However, there are some cases where you will need to adjust or enter quantities that are not associated with a time entry. The steps below will show you how to do this.    STEP 1 – Log in to WorkMax by entering your e-mail address and unique password (not the same as your Swinerton Password)    STEP 2 – Once you are logged in:  Click in the Insight Module Click on the Productivity Editor Tab Click on New  STEP 3 – On the new line fill out the following:  Enter your project (use search to help find it)  Enter the Phase to adjust the quantities on (you can use search here as well)  Enter your name in the “Employee” Column (this is for tracking only) Enter a zero in the Hours Column Enter the Quantities you want to adjust by. * Note, (If you can’t enter quantities, you picked a phase code that does not track quantities)  Click Save   The Unit of Measure will appear once you click “save” The original Date/Time/TZ will auto-populate. The Updated Date/Time/TZ will populate if you adjust the entry.   The device will auto-populate         STEP 4 – Click on “New” and repeat step 3 for all Quantities you would like to adjust  General Notes:  Positive or negative quantities can be entered anytime throughout the week.  Quantities entered are flexible and can be edited up to Monday morning (same as Time entries).  At 10:00am(PT) Monday morning, these quantities will be locked and copied over for entry into CMiC.  These Quantities as well as any other quantities entered on the time cards will be entered in CMiC each Thursday along with Payroll (This is to keep the Production information in CMiC aligned i.e. hours + quantity adjust at the same time) To help with sorting and reviewing edits, use the Date Box, The Search Function, and the “By Location” view (see below). 

Labor Productivity Dashboards – Integration Timing and Details   You can access the labor productivity dashboards by clicking this link. On the introduction page, you will find three filter options that allow the user to see data in different states: • Include posted data only: when this filter is selected, the report only shows the data through the last posted period. Every Wednesday night, the data for the previous week is posted from WorkMax to CMiC. If today's date is on or before Wednesday and this filter is selected, the report only shows data through the week before last week. • Include data through last week: when this filter is selected, the report shows the data through last Sunday (including the closed quantities entered on this Monday). The source of data will be a combination of CMiC (posted data) and WorkMax (unposted data*). • Include data through yesterday: when this filter is selected, the report shows the data through yesterday. The source of data will be a combination of CMiC (posted data) and WorkMax (unposted data*). The filter is set to "Include data through last week" by default. *for best results of unposted data, make sure your team is clocking in, clocking out, selecting phase codes, and assigning units daily. If any data field is missing, it will impact the accuracy of your productivity forecast.      The balance of this document will provide details on how & when the WorkMax data is available on the production dashboards.   Within WorkMax clock in’s and clock out’s are captured using Time Editor.   Quantities are captured using Time Editor or Productivity Editor. All available information from WorkMax gets integrated to Power BI Data Mart on a nightly basis. Fully completed entries will be available for analysis, partial entries may be ignored. Only phase codes in CMiC with a forecast method of “P” will be integrated over to Power BI DataMart. These are the productivity phase codes. (The forecast method for your phase codes can be found in CMiC by running the Quantity/Hours Tracking Log under Labor Productivity)  It is assumed that Quantities entered using Productivity Editor for previous week may be entered on the following Monday. Those records will still show the current week timestamp (Monday) although the quantities belong to previous week. Quantities entered by 3:00PM (PT) the following Monday will get posted to CMiC when Payroll runs the jobs cost Wednesday night. The production records from the previous week will still integrate to the Power BI Datamart up until the quantities gets posted to CMiC on Wednesday night. Once the integration notices that Quantities are posted in CMiC, it will no longer integrate them from WorkMax. Job cost posting in CMiC is a long running process and it can take up to 48 hours depending on the corrections. There will be a time difference up to 48 hours between when the quantities get posted and when hours get posted in CMiC. During this window you may potentially see skewed information from late Wednesday thru Thursday Morning in our Power BI Datamart. We look for up to 4 larger region job cost (that will cover 90% hours) files to be posted in CMiC for us to determine if hours are posted to CMiC. We have introduced hourly integration schedular on Thursdays to keep checking on when those job cost files(hours) gets posted in CMiC to help reduce this gap. a. Once the quantities get posted in CMiC for previous week, integration will ignore the posted Quantities and focus only on open quantities from the current week. If there are still previous week open quantities available in WorkMax we will not integrate those to Power BI Datamart. (as a side-note, open time will be represented in the insight module in WorkMax for 30 days before being automatically deleted, this may impact the insight module).   Missed time that gets processed from WorkMax/Workday after the respective job cost run deadline may not make it to Power BI Datamart until it is in CMiC and posts normally. Please reference the attached Integration Logic Chart for a further breakdown of when integration takes place. Please reference the attached Functional Design Document for additional details and Business process flows.