Aperto di navigazione

Building Operations Console

Setting the Application Parameters for using the Building Operations Console

Beginning with V23.1, the Building Operations Console is the default way of working for new users.

If you are upgrading from a pre-v.21.2 version, using the Building Operations Console requires an opt-in process so that you can use your data with the console.

• Upgraders can run the Use Building Operations script which automates the conversion of your data and sets the UseBldgOpsConsole and WorkRequestsOnly application parameters for you.
• If upgraders have extensive customizations, they can upgrade their data manually.
• If you are a new deployment and want to opt in to using the Building Operations Console, the steps to follow depend on how the application parameter for UseBuildingOperationsConsole is set in the database you are using to start your deployment. Beginning with V23.1, the Building Operations Console is the default working method.

For details on how to opt in, see Opting in to Using the Building Operations Console.

Application parameters for using the Building Operations Console and work orders

Note: If you have an existing deployment and are using the automated process for upgrading to the Building Operations Console, there is no need to set the UseBldgOpsConsole and WorkRequestsOnly parameters, as the workflow rule converts them for you. If you want to manually convert your data, rather than using the workflow rule, you can use the Configure Application Parameters task to set these parameters manually as described in this topic.

• The UseBldgOpsConsole application parameter determines whether the application shows the Building Operations Console, or the legacy views for submitting work requests.
• The WorkRequestsOnly parameter determines whether the console shows work orders that group work requests, or shows only work requests.
• If you run the System Administration / ARCHIBUS System Administration / ARCHIBUS Administrator - Application Configuration / Use Building Operations task to upgrade to the Building Operations Console, you make a selection for the WorkRequestsOnly parameter. The workflow rule that runs from this task uses your selection to set the UseBldgOpsConsole and the WorkRequestOnly application parameters for you.

Application parameters that are not set by the automated process to upgrade

The following parameters are not set by the automated process to upgrade to the Building Operations Console. The following describes how these parameters affect your workflow.

• ShowEquipmentOnReportProblem. This parameter determines whether or not the Equipment pane is shown on the Report Problem form. Showing equipment enables the person submitting the work request to select the equipment having a problem. If you set the parameter to No (0), the Equipment panel does not show on the Create Request form. However, you can override this setting for specific users by adding them to the security group SHOW-ALL-REQUEST-FIELDS. This enables you to give different users different capabilities according to the level of responsibility you want them to have.
• ShowProblemTypeOnReportProblem. Use this parameter to control whether Problem Types are shown on the Create Request form when users submit work requests. To show Problem Types, set this parameter to Yes (1); to hide Problem Types, set it to No (0),

  • You would hide Problem Types when you want someone other than the requestor to enter the problem type. However, be aware that if you have developed SLAs that depend on Problem Types, and you are hiding Problem Types from the user, you will need to create an SLA to handle this situation. For example, you would create a baseline Service Level Agreement with an approval step that routes the request to an approving manager who then enters the appropriate Problem Type for each request.

  • As with equipment, if you want to hide Problem Types generally, but to make them visible for specific users, you can accomplish this by assigning these users to the security group SHOW-ALL-REQUEST-FIELDS.

  See Security Groups for the Building Operations Console.

• EditEstAndSchedAfterStepComplete: The setting for this parameter determines whether or not supervisors and craftspersons are restricted from making changes to estimation and scheduling steps after these steps are completed.
  • By default, this is set to 1 so that supervisors and craftspersons do have the ability to edit estimation and scheduling after those steps are completed.
  • Set this parameter to 0 if you want estimation and scheduling data to be locked and made read-only after those steps are completed.

  For more information on how this setting affects workflow, see Estimating and Scheduling Steps.

Application Parameters to manage performance

The following application parameters affect the performance of the Building Operations Console:

• BldgOpsConsoleExpandOnOpen. Controls whether the Building Operations Console opens with its category bands expanded (slower), or collapsed (faster). For both settings (expanded or collapsed), the application shows the total count of records within each category band in parentheses next to the category band title.
• BldgOpsConsoleLoadDataOnOpen. Controls whether or not the console immediately loads Work Requests when opened (slower), or instead waits for the Filter button to be pressed (faster, as only the requests that match the filter are displayed).
• BldgOpsConsoleLoadPendingSteps. Controls whether the console immediately loads Work Requests that contain pending steps to complete. You can always load Work Request with pending steps later using the "Pending Steps" control on the Filter command.
• BldgOpsConsoleMaxRequestsPerBand. Indicates the maximum number of work requests the system will initially display per category band. If the number is less than the total number of work requests in that band, the console presents an action to view the next group.

Procedure

To set the application parameters that affect the Building Operations Console:

1. From the Process Navigator, select theSystem Administration / ARCHIBUS System Administration / ARCHIBUS Administrator - Application Configuration / Configure Application Parameters task.

   The Edit Application Parameters form appears.

2. In the Applications list, select AbBldgOpsOnDemandWork.

   The Application Parameters pane shows the On Demand application parameters.

3. To change the setting to use or not use work orders, follow these steps. Note that if you plan to use the Maintenance mobile app as part of your On Demand workflow, you must set this option to 1.

   Note: You need to set this parameter only if you are manually upgrading, rather than using the automated process provided. The automated process used by the Use Building Operations action uses your selection to set this parameter for you.  See Upgrading to the Building Operations Console.

1. Locate and select the WorkRequestsOnly parameter in the list.

   The Edit Application Parameters pane shows the setting for this parameter. A Parameter Value of 0 means that work orders are used; a Parameter Value of 1 means that work requests are not grouped into work orders.

   Note: When you select 1 (Yes) for WorkRequestsOnly, the system assigns work requests to work orders in the background, and all work requests have a one-to-one relationship with work orders. The system still uses the 'AA' status, and renames the display value for that status to 'Approved.' In this case, the 'A' status is skipped because all SLAs auto-assign work requests to work orders and go directly to the 'AA' status.

2. In the Parameter Value field, ensure that the appropriate value for your deployment.
3. Click Save.
4. To use the Building Operations Console and the associated interfaces for defining SLAs:

   Note: You need to set this parameter only if you are manually upgrading, rather than using the automated process provided. The automated process used by the Use Building Operations action uses your selection to set this parameter for you.  See Upgrading to the Building Operations Console.

1. In the Application Parameters list, locate and select the UseBldgOpsConsole parameter.

   The Edit Application Parameters pane shows the setting for this parameter. A Parameter Value of 0 means that the Building Operations Console is not used. Set this value to 1 to use the Building Operations Console.

2. In the Parameter Value field, enter the appropriate value for your deployment.
3. Click Save.
5. To show or hide equipment on the Report Problem form:
   1. In the Application Parameters list, locate and select the ShowEquipmentOnReportProblem parameter.

      The Edit Application Parameters pane shows the setting for this parameter. A Parameter value of 0 means that equipment is not shown on the form; a value of 1 means that equipment is shown.

   2. In the Parameter Value field, enter the appropriate value for your deployment.
   3. Click Save.
6. To show or hide Problem Types on the Report Problem form when submitting work requests:
   1. In the Application Parameters list, locate and select the ShowProblemTypeOnReportProblem parameter.

      The Edit Application Parameters pane shows the setting for this parameter. A Parameter value of 0 means that Problem Types are not shown on the form; a value of 1 means that Problem Types are shown.

   2. In the Parameter Value field, enter the appropriate value for your deployment.
   3. Click Save.
7. To enable / disable editing of estimating and scheduling steps once they have been entered:
   1. From the Application Parameters list, select EditEstAndSchedAfterStepComplete.
   2.  Set the Parameter Value to one of the following:
      • Enter 0 so that the estimation and scheduling data is locked and made read-only after these steps are completed.
      • Enter 1 to enable editing of estimation and scheduling data.
   3. Click Save.
8. To set parameters that affect performance:
9. From the Application Parameters list, select
   • BldgOpsConsoleExpandOnOpen.
   • BldgOpsConsoleLoadDataOnOpen
   • BldgOpsConsoleLoadPendingSteps
   • BldgOpsConsoleMaxRequestsPerBand

     See Application Parameters that affect performance for a description of these parameters.

10. Click Reload Parameters to load the new parameter values into the database.