Dispatching Board DELMIA Apriso 2017 Implementation Guide

Transcription

1 Dispatching Board DELMIA Apriso 2017 Implementation Guide 2016 Dassault Systèmes. Apriso, 3DEXPERIENCE, the Compass logo and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA, DELMIA, SIMULIA, GEOVIA, EXALEAD, 3D VIA, BIOVIA, NETVIBES, and 3DXCITE are commercial trademarks or registered trademarks of Dassault Systèmes or its subsidiaries in the U.S. and/or other countries. All other trademarks are owned by their respective owners. Use of any Dassault Systèmes or its subsidiaries trademarks is subject to their express written approval.

2 Dispatching Board DELMIA Apriso 2017 Implementation Guide 2 Contents 1 Introduction Abstract Overview Vocabulary 5 2 Configuration Prerequisites and Overview Upgrading from Older FlexNet/DELMIA Apriso versions with Dispatching Board SE Installed Configuration Overview Workspace Class Determination Functions Standard Operations Business Control and JavaScript Files Performance Classes 8 3 Business Components DispatchingBoardAssignmentManager Business Components DispatchingBoardManager Business Components DispatchingBoardPerformanceManager Business Components 10 4 Data Model 12 5 Configuration Workspace Class Configuration Determination Function Configuration Standard Operation Configuration Performance Class Configuration Custom KPI Value Configuration Implement the Resource Setup Time Using a Maintenance Order 18 6 Business Control and JavaScript File Configuration Workspaces Configuring Determination Functions to Map to a Particular Template Creating a Custom Workspace Package Activity Fields Behavior of the Control Configuration File Rules Mapping a Field to the Gantt Chart Converters Mapping Fields to the Flexy Gantt Chart Custom Execution Progress Calculation Custom Context Menus Table Context Menu Task Context Menu Flexy Task Context Menu Customizing the Look and Feel of the Control 35

3 Dispatching Board DELMIA Apriso 2017 Implementation Guide Cells Flexy Gantt Cells Flexy Gantt Headers Headers Size of the Controls Tooltips Workspace Details Pop-Up Window Custom Time Headers Bar Styles 39 7 Configuration Sequence Roles Security 44 8 References 45 Figures Figure 1 Configuration overview schema 6 Figure 2 Workspace Class screen 13 Figure 3 Determinations screen 14 Figure 4 Determination properties screen 14 Figure 5 Runtime Values screen, Determination values configuration grid 15 Figure 6 Performance Class screen 17 Figure 7 Determination values screen for APR_DB_GetWorkSpaceThemeFile 20 Figure 8 Selecting Standard Operations for Determination 41 Figure 9 Determining the "Create" Standard Operation 41 Figure 10 Determining the "Load" Standard Operation 41 Figure 11 Determining the "Apply" Standard Operation 41 Figure 12 Determining the Theme folder 42

4 Dispatching Board DELMIA Apriso 2017 Implementation Guide 4 1 Introduction 1.1 Abstract The purpose of this document is to describe the Dispatching Board and its configuration and administration The audience for this document is the personnel responsible for implementing and managing the Dispatching Board solution. The document s scope includes configuration prerequisites and procedures, Business Components, the data model, Business Control and JavaScript file configuration, and administration and customization of the Dispatching Board solution. For more information on using Dispatching Board, refer to the Dispatching Board Workspace Classes Business Process Flow Guide and the Dispatching Board Online Help. 1.2 Overview The Dispatching Board can be used to: Visualize production situations Manually model hypothetical situations and see the business impact Apply schedules that have been prepared manually Manage unexpected situations while modeling different ways of solving problems that arise With the Dispatching Board, you can quickly react to unexpected events that appear on the shop floor. You can also simulate the possible ways of solving any problem that has been indicated (e.g., unexpected downtime for a machine or the appearance of a new order). Dispatching Board can be positioned as an extension to DELMIA Apriso applications (Warehouse, Production, Quality, Maintenance, Time & Labor), a shop floor extension for Enterprise Planning Systems, or a place where reactions to unexpected events can be performed. It can be used as a standalone solution that presents data on the same Gantt chart from multiple modules (e.g., Warehouse, Production, Quality, Maintenance, Time & Labor). Additionally, Dispatching Board can be used as an extension to the detailed dispatching of a particular resource. The point of the Dispatching Board solution is to work next to transactional DELMIA Apriso tables in order to model business situations that have no influence on the DELMIA Apriso transactional tables and to apply a new schedule when it is ready. Any Standard Operation can be invoked directly from the screen used to manage a production schedule. The Dispatching Board solution keeps the architecture based on the Gantt control that is embedded in a Standard Operation with an interaction similar to other Process Builder controls (in style, look and feel, user interactions, etc.). The new Gantt control parameterization will be modified to support HTML.

5 Dispatching Board DELMIA Apriso 2017 Implementation Guide 5 The Dispatching Board solution makes available an easy recompilation to 4.0/4.5. Dispatching Board and the standard DELMIA Apriso thin client requirements (that is, with a browser-agnostic HTML interface) are aligned. 1.3 Vocabulary Workspace Class a template that defines data filtering, formatting, and permitted user activities. This item is predefined during the configuration phase. Workspace a container which can include all of the activities and resources from a chosen date range based on Workspace Class conditions. The user can create multiple Workspaces in order to model business situations in many ways. Performance Class defines the indicators that are used to calculate the performance values for every Workspace during Performance Calculation.

6 Dispatching Board DELMIA Apriso 2017 Implementation Guide 6 2 Configuration Prerequisites and Overview 2.1 Upgrading from Older FlexNet/DELMIA Apriso versions with Dispatching Board SE Installed When upgrading from an older FlexNet/DELMIA Apriso version that has Dispatching Board SE installed, after uninstalling the old FlexNet/DELMIA Apriso version but before installing DELMIA Apriso 2016 (or later), it is necessary to remove all the old DLLs from GAC. This is because the SE version assembly will not be removed via the uninstall. If this is not done and errors occur in Process Builder regarding Dispatching Board-related BCs, it is necessary to remove the assembly from GAC and run the Post-Upgrade Utility again to load the correct information into the database. 2.2 Configuration Overview Workspace Class Determination Functions Standard Operations APR_DB_GetCreateWorkSpaceOprName APR_DB.CreateUpdateWorkspace <Workspace Class Name> <Workspace Class Name> APR_DB_GetLoadWorkSpaceOprName APR_DB_GetApplyWorkSpaceOprName APR_DB.LoadWorkspace <Workspace Class Name> APR_DB.ApplyWorkspace <Workspace Class Name> APR_DB_GetWorkSpaceThemeFIle JavaScript Files <Theme folder name> including files: _defaultresource, _table, App, Rules, scriptresources Business Control APR_DB.OpenViewer Standard Operations invoked through context menu Figure 1 Configuration overview schema You can define an unlimited number of Workspace Classes, Standard Operations, and JavaScript files to be used in Dispatching Board. Every combination of these elements as configured in the pattern in the schema above represents a different view of a business case. The Workspace Class connects everything through Determination Functions and determines which Standard Operations are used as well as the look of the Business Control. The Business Control is embedded in the APR_DB.OpenViewer Standard Operation. There are also many Standard Operations invoked from the Business Control context menu.

7 Dispatching Board DELMIA Apriso 2017 Implementation Guide 7 Configuration of the Dispatching Board can be done by navigating to the Performance Class and Workspace Class screens in the DELMIA Apriso Desktop Client (ADC). It is important to be aware that Dispatching Board works in parallel to DELMIA Apriso tables, and the only connection points between Dispatching Board and DELMIA Apriso occur when loading data into the Dispatching Board tables and applying the data changes back to the DELMIA Apriso tables Workspace Class The Workspace Class links through a Determination Function the specific behavior defined in the Standard Operation and the Business Control configuration included in the JavaScript file. Based on the Workspace Class, the user can also define a link with user Roles, which involves defining securities. For more information, please see 7.1 Roles and 7.2 Security. A new Workspace Class can be created during implementation in the Workspace Class screen in the ADC. For more information, see 5.1 Workspace Class Configuration. Workspace Classes available out-of-the-box are installed through GPM packages. For information on the out-of-the-box Workspace Classes of the Dispatching Board solution, please see the Dispatching Board Workspace Classes Business Process Flow Guide Determination Functions After the Workspace Class is configured, the Determination Functions can be configured. The Determinations define the links between the Standard Operations and the JavaScript file with a Workspace Class. There are four Determinations for Dispatching Board that are available out-of-the-box: APR_DB_GetCreateWorkSpaceOprName APR_DB_GetLoadWorkSpaceOprName APR_DB_GetApplyWorkSpaceOprName APR_DB_GetWorkSpaceThemeFile For more information, see 5.2 Determination Function Configuration Standard Operations In a Standard Operation, the user can include business logic and detailed Dispatching Board function behavior, because each Standard Operation represents a different situation that can be performed on the Dispatching Board. The user can also include parameter default values and specific flow changes. For each Workspace Class, the following Standard Operations are used: APR_DB.CreateUpdate<Workspace Class name>ws APR_DB.Load<Workspace Class name> APR_DB.Apply<Workspace Class name> For more information, see 5.3 Standard Operation Configuration.

8 Dispatching Board DELMIA Apriso 2017 Implementation Guide Business Control and JavaScript Files The Business Control is responsible for displaying the Workspace as defined by the JavaScript file. It is embedded in the APR_DB.OpenViewer Standard Operation. JavaScript files are responsible for the way the Business Controls are displayed. One Workspace Class has to link with one JavaScript file, but one JavaScript file can link with many Workspace Classes. For more information, see 5.4 Performance Class Configuration as well as Adding a Context Menu to Open a Maintenance Calendar Performance Classes Performance Classes define the indicators that are used to calculate the performance values for every Workspace. Performance Classes evaluate these performance values when a Performance Calculation is needed on the Management screen in the Dispatching Board. These performance values can later be compared between several different Workspaces. The Performance Classes correspond to the DispatchingBoardPerformanceManager Business Components. For more information on the use of Performance Classes in Performance Calculation, refer to the Dispatching Board Online Help. For more information on Performance Classes, see 5.4 Performance Class Configuration.

9 Dispatching Board DELMIA Apriso 2017 Implementation Guide 9 3 Business Components The Business Components used in Dispatching Board manage the Dispatching Board flows. Additionally, each Performance Class has its own Business Component used to calculate indicator values. For more information on these Business Components, see the Business Components Documentation. 3.1 DispatchingBoardAssignmentManager Business Components Name CreateAssignment DeleteAssignment FindQualifyAssignmentByEmployeeSkill FindQualifyAssignmentByResourceClass Description Creates assignments for a Workspace. Deletes all of the assignments in a Workspace. Automatically assigns an activity to the first matched employee who has the configured skill. Automatically assigns an activity to the first matched resource that has the configured resource class. 3.2 DispatchingBoardManager Business Components Name ApplyResourceActivities ApplyWDResourceActivities ApplyWeighHeaderActivities ApplyWipOperations ApplyWipOrders ApplyWorkCenterResourceActivities CleanWorkSpace CreateActivityDependencies Description Applies the assignment changes from Dispatching Board back to a DELMIA Apriso table (WIP_REQ_RESOURCE). Applies the assignment changes from Dispatching Board back to a DELMIA Apriso table (WEIGH_HEADER). Applies the activity changes back to a DELMIA Apriso table (WEIGH_HEADER). Applies the activity changes back to a DELMIA Apriso table (WIP_ORDER). Applies the activity changes back to a DELMIA Apriso table (WIP_ORDER). Applies the assignment changes from Dispatching Board back to a DELMIA Apriso table (WIP_OPERATION). Removes all of the data from the specified Workspace and cleans all of the linked records. Creates dependencies between activities.

10 Dispatching Board DELMIA Apriso 2017 Implementation Guide 10 CreateActivityWeighHeaders Creates an activity from the Weigh Header. CreateActivityWipOperations Creates an activity from a WIP Operation. CreateActivityWipOrders Creates an activity from a WIP Order. CreateActivityWipOrdersAndWipOperations Creates an activity from a WIP Order and a WIP Operation. CreateResourceActivities Creates an assignment between an activity and a resource. CreateResourceEmployees Creates an assignment between an activity and a resource (Employee). CreateResourceEquipments Creates an assignment between an activity and a resource (Equipment). CreateResourceWorkCenters Creates an assignment between an activity and a resource (Work Center). CreateWorkSpace Creates a Workspace. CreateWorkingTime Creates the time schedule of a Workspace from a Work Center Calendar. DeleteWorkSpace Deletes a Workspace record. DuplicateWorkSpace Duplicates a Workspace with the linked activities, resources, and assignment relationships between activities and resources. GetWorkSpaceByName Gets the Workspace record by the Workspace name and employee. If there is no matching record, it will return an error. QueryWorkSpaceByName Queries if a Workspace exists with the inputted Workspace name and employee. If there is no matching record, it will return 0 for WorkSpaceID. UpdateWorkSpace Updates the Workspace. 3.3 DispatchingBoardPerformanceManager Business Components Name AverageEarliness AverageLateness AverageProcessingTime AverageTardiness AverageWeighedEarliness AverageWeighedLateness AverageWeighedProcessingTime AverageWeighedTardiness EarlyActivities LateActivities Description The average earliness time in hours. The average lateness time in hours. The average processing time in hours. The average tardiness time in hours. The average weighed earliness time in hours. The average weighed lateness time in hours. The average weighed processing time in hours. The average weighed tardiness time in hours. The number of early activities. The number of late activities.

11 Dispatching Board DELMIA Apriso 2017 Implementation Guide 11 MaximumEarliness MaximumLateness ResourceUtilizationPercentage ResourceUtilizationTime TotalEarliness TotalLateness TotalProcessingTime TotalTardiness TotalWeighedEarliness TotalWeighedLateness TotalWeighedProcessingTime TotalWeighedTardiness The maximum earliness time in hours. The maximum lateness time in hours. The resource utilization as a percentage of the total available time. The resource utilization time in hours. The total earliness time in hours. The total lateness time in hours. The total processing time in hours. The total tardiness time in hours. The total weighed earliness time in hours. The total weighed lateness time in hours. The total weighed processing time in hours.. The total weighed tardiness time in hours. For details on the system processing of these Business Component methods, see the Business Components Documentation.

12 Dispatching Board DELMIA Apriso 2017 Implementation Guide 12 4 Data Model The data model consists of the following tables: Table Name DB_WORKSPACE_CLASS DB_WORKSPACE DB_ACTIVITY Description This table stores information about the Workspace Classes. This table stores information about the Workspaces. This table stores information about activities. It can load any type of records as the tasks in a Workspace. DB_ACTIVITY_DEPENDENCY This table stores information about the dependencies between two activities. A dependency can be: SS Start to Start SF Start to Finish FS Finish to Start FF Finish to Finish DB_RESOURCE This table stores information about the resources within Dispatching Board. It can include any type of data to be assigned to an activity. DB_RESOURCE_ACTIVITY This table stores information about resource activities. A resource activity describes the assignment relationship between a resource and an activity. DB_PERFORMANCE_CLASS This table stores information about the Performance Class. The Performance Class is a formula of the different performances of a Workspace. DB_PERFORMANCE This table stores information about the calculated performance results of a Workspace. DB_WORKING_TIME This table stores information about the work schedule of a Workspace. DISPATCH_SEQUENCE_TYPE This table specifies the valid types of DISPATCH_SEQUENCE. The contents of this table cannot be changed by the user. DISPATCH_SEQUENCE This table specifies additional constraints for dispatching orders, WIP Orders, Operations, and tasks that are not described in the WIP_OPERATION_SEQUENCE table. Further details on the Dispatching Board database model are available in the Database Documentation.

13 Dispatching Board DELMIA Apriso 2017 Implementation Guide 13 5 Configuration 5.1 Workspace Class Configuration A new Workspace Class can be configured by navigating to the Workspace Class screen in the ADC and then clicking (Add). The Workspace Class screen will then appear, where a name and description of the Workspace Class must be provided. Figure 2 Workspace Class screen Altering the additional fields (such as User 1, User1, etc.) for out-of-the-box Workspace Classes is not recommended. However, these fields can be used during the implementation of new Workspace Classes. For example, to change the look of the Dispatching Board control, Inputs will be needed to connect to a specific Workspace Class, and these Inputs can be defined in these fields. Values can be populated for the new Workspace Class or for an activity or resource in the Workspace Class (depending on the implementation for such options). In another example, certain order types can be loaded by setting the value in an additional field and then setting a Standard Operation to take the value from this field (e.g., order type 1, which is a production order). The value in the field can be changed if necessary (while the Standard Operation remains unchanged). 5.2 Determination Function Configuration The Determination Functions link the Workspace Class with each Standard Operation. The Determinations can be accessed for each Workspace Class by clicking

14 Dispatching Board DELMIA Apriso 2017 Implementation Guide 14 in the bottom-left corner of the Workspace Class screen (see Figure 2), which will bring up the Determinations screen: Figure 3 Determinations screen There are four Determinations for Dispatching Board that are available out-of-the-box: APR_DB_GetCreateWorkSpaceOprName defines the link between the Workspace Class and the Standard Operation for the creation of a new Workspace APR_DB_GetLoadWorkSpaceOprName defines the link between the Workspace Class and the Standard Operation for the loading of data into the Workspace APR_DB_GetApplyWorkSpaceOprName defines the link between the Workspace Class and the Standard Operation for the application of changes made in the Workspace to DELMIA Apriso tables APR_DB_GetWorkSpaceThemeFile defines the link between the Workspace Class and the JavaScript file that defines how the control looks To configure the Determination Functions, a new value must be added for each Workspace Class that is being created. To do this, highlight a Determination and view its properties by clicking (Properties), which will bring up the Determination properties screen: Figure 4 Determination properties screen Click in order to view the Runtime Values screen. On this screen, the values of the Determination can be edited in the Determination values grid:

15 Dispatching Board DELMIA Apriso 2017 Implementation Guide 15 Figure 5 Runtime Values screen, Determination values configuration grid 5.3 Standard Operation Configuration For every Workspace Class, the following Standard Operations are used: APR_DB.CreateUpdate<Workspace Class name>ws This Standard Operation is invoked when creating or updating a Workspace. The Standard Operation gets a snapshot of the DELMIA Apriso tables. APR_DB.Load<Workspace Class name> This Standard Operation is invoked when loading data into a previously created Workspace via the definition of the Workspace. The Standard Operation refreshes the Dispatching Board table with DELMIA Apriso data. APR_DB.Apply<Workspace Class name> This Standard Operation is invoked when applying the modified data from Dispatching Board tables to back to the master data in DELMIA Apriso transactional tables. The developer can define what data needs to be applied and how it will be applied. Depending on the Workspace Class being used, different Standard Operations can be used under different conditions. For example, if the user wants to schedule only one type of order, a Standard Operation can be configured to set the default value for the order type. This order type can be set in a Standard Operation as a strict value or it can be populated (e.g., from an additional field defined for the Workspace Class, as described in 5.1 Workspace Class Configuration). The following Standard Operations are available out-of-the-box for use during the configuration: Standard Operation APR_DB.AftCalculatePerformace APR_DB.AftCreateResourceActivity APR_DB.AftUpdateActivity APR_DB.AftUpdateWorkSpace Description An extension point invoked inside APR_DB.CalculatePerformance. An extension point invoked on the server side after creating a dependency. An extension point invoked on the server side after updating an activity. An extension point invoked on the server side after updating a Workspace.

16 Dispatching Board DELMIA Apriso 2017 Implementation Guide 16 APR_DB.Apply Applies the changes in Dispatching Board back to DELMIA Apriso tables. APR_DB.Assignment Removes all of the existing assignments and then finds the qualified employee/resource for each activity to be assigned to. APR_DB.BefDeleteResourceActivity An extension point invoked on the server side before deleting a dependency. APR_DB.BefUpdateActivity An extension pint, invoked on the server side before updating an activity. APR_DB.BefUpdateWorkSpace An extension point invoked on the server side before updating a Workspace. APR_DB.CalculatePerformance Calculates the performance values for the selected Workspace. APR_DB.ClearWorkSpace Clears all of the activities, resources, and assignments for the selected Workspace. APR_DB.Compare The screen for comparing the performance indicators of selected Workspaces. APR_DB.CompareChart The screen for showing a comparison chart of selected Workspaces. APR_DB.Create The screen for creating a Workspace using APR_DB.GetCreateWorkSpaceOprFUID to find the corresponding Standard Operation for the selected Workspace Class. APR_DB.DeleteWorkSpace Invokes the DeleteWorkSpace BC method in order to delete the selected Workspace. APR_DB.DispatchingBoard The main screen. APR_DB.Duplicate The screen for duplicating the selected Workspace. APR_DB.GetActivity Gets the activity data with the inputted activity ID. APR_DB.GetApplyWorkSpaceOprFUID Gets the runtime value of the Apply Standard Operation of the selected Workspace Class from the APR_DB.GetApplyWorkSpaceOprName Determination Function. APR_DB.GetCreateWorkSpaceOprFUID Gets the runtime value of the Create Standard Operation of the selected Workspace Class from the APR_DB.GetCreateWorkSpaceOprName Determination Function. APR_DB.GetLoadWorkSpaceOprFUID Gets the runtime value of the Load Standard Operation of the selected Workspace Class from the APR_DB.GetLoadWorkSpaceOprName Determination Function. APR_DB.GetResourceFile Gets the runtime value of the Apply Standard Operation of the selected Workspace Class from the APR_DB.GetWorkSpaceThemeFile Determination Function.

17 Dispatching Board DELMIA Apriso 2017 Implementation Guide 17 APR_DB.GetWipOrder APR_DB.GetWorkSpace APR_DB.GetWorkSpaceClass APR_DB.HideEmployee APR_DB.HideMachine APR_DB.Load APR_DB.LoadWCSchedule APR_DB.OpenViewer APR_DB.Performance APR_DB.ShowAllResources APR_DB.ShowMessage APR_DB.SplitWipOrder APR_DB.Update Gets the WIP Order data for the inputted WIP Order No. Gets the Workspace data for the inputted Workspace ID. Gets the Workspace Class data for the inputted Workspace Class ID. Sets the hidden flag to true for all employee resource types in the selected Workspace. Sets the hidden flag to true for all machine resource types in the selected Workspace. Uses APR_DB.GetLoadWorkSpaceOprFUID to find the corresponding Standard Operation to load data for the selected Workspace Class. Loads the working schedule for the selected Workspace. The screen for displaying the Dispatching Board Business Control with the selected Workspace. The screen for displaying the performance data for the selected Workspace. Sets the hidden flag to false for all of the resources for the selected Workspace. Error message configuration. Invoked from the context menu on the Dispatching Board control. The screen for modifying the Workspace. 5.4 Performance Class Configuration A new Performance Class can be configured by navigating to Performance Class in the ADC and then clicking (Add). Figure 6 Performance Class screen The fields for configuring a Performance Class include Name, UOM, and Description. After defining a new Performance Class, it must be linked with a new Business Component inside the APR_DB.CalculatePerformance Standard Operation that defines how the indicator

18 Dispatching Board DELMIA Apriso 2017 Implementation Guide 18 is calculated (that is, for each performance indicator, there is one Business Component from the DispatchingBoardPerformanceManager BC class). Each BC then takes WorkSpaceID as a parameter, for which it will calculate the performance metrics. 5.5 Custom KPI Value Configuration To link a customized KPI to a Performance Calculation: 1 Add a new Performance Class as described in 5.4 Performance Class Configuration. The name of the Performance Class should be the name of the new custom KPI. a Defining the UOM code is optional. 2 Go to Process Builder and open the APR_DB.CalculatePerformance Standard Operation. 3 In the CalculatePerformance Step of the Standard Operation, add a new Function to implement the custom KPI logic calculation via the specified Workspace or to invoke another Standard Operation that will implement the calculation of the custom KPI and create/update the performance record in the database. 5.6 Implement the Resource Setup Time Using a Maintenance Order 1 After the assignment, implement APR_DB.AftUpdateWorkSpace from the extension point. When clicking Save, the system will invoke this Standard Operation after updating the data in the database. With any new assignment, the system will create an assignment record in the DB_RESOURCE_ACTIVITY table for the specified Workspace. 2 Select the assigned tasks from the DB_RESOURCE_ACTIVITY table and, according to each assigned task, create a corresponding Maintenance Order in the database with the assigned resource setup time (and also add the record to WIP_REQ_RESOURCE as an assignment). 3 The following steps can refer to any load Operations: a Select the newly created Maintenance Order and invoke the CreateActivityWipOrders or CreateActivityWipOperations Business Component in order to load the newly created Maintenance Order into the Workspace. b Select the assignment from WIP_REQ_RESOURCE and invoke the CreateResourceActivities BC to create the resource activity record in the database.

19 Dispatching Board DELMIA Apriso 2017 Implementation Guide 19 6 Business Control and JavaScript File Configuration The Business Control is responsible for displaying the Workspace as defined by the JavaScript file. It is embedded in the APR_DB.OpenViewer Standard Operation. 6.1 Workspaces A Workspace package can be defined as a collection of files contained in the folder where the Dispatching Board is installed. Each of these files serves a purpose: _defaultresource.tmpl.cshtml the cell look and feel and data mapping _table.tmpl.cshtml the header look and feel, translation, and data mapping app.config the basic preferences for the control rules.xml the rules to be evaluated for the taskbar control scriptresources.cshtml the custom data mapping, custom pop-up menus, converters, and custom time headers The templates are usually installed at: <drive>\program Files\Dassault Systemes\DELMIA Apriso 2017\WebSite\DispatchingBoard\Views\GanttTemplates. The Dispatching Board comes with four default templates: DispatchingResource (default) ProductionOrderEmployee ProductionOrderEquipment ProductionOrderWorkCenter Configuring Determination Functions to Map to a Particular Template 1 In the Determinations screen (for details, see Determination Function Configuration), open the APR_DB_GetWorkSpaceThemeFile Determination Function and click. 1 On this screen, the user can change the template that each Workspace Class can use:

20 Dispatching Board DELMIA Apriso 2017 Implementation Guide 20 Figure 7 Determination values screen for APR_DB_GetWorkSpaceThemeFile Some Workspaces have the default template mapped, which will resolve to the DispatchResource template. ResourceLocationValue is case-sensitive. The valid ResourceLocations can be found in the following folder: <drive>\program Files\Dassault Systemes\DELMIA Apriso 2017\WebSite\DispatchingBoard\Views\GanttTemplates Creating a Custom Workspace Package 1 Copy the DispatchingResource folder from: <drive>\program Files\Dassault Systemes\DELMIA Apriso 2017\WebSite\DispatchingBoard\Views\GanttTemplates. 2 Name the folder with a different template name. 3 Map the template and the Workspace Class to the Determination Function to make use of the new template. 6.2 Activity Fields An activity is the main entity for the control. Each activity will have a set of fields that the control can read and map. These fields can be used to map or evaluate rules. The available fields are: Field ID WorkSpaceID Name Description IndentLevel BreakdownStructureCode Type

21 Dispatching Board DELMIA Apriso 2017 Implementation Guide 21 StartDate Date This field is editable in runtime. If you want to display a task in the Dispatching Board that can be scheduled, this field must be populated. DurationInSeconds This field is editable in runtime. If you want to display a task in the Dispatching Board that can be scheduled, this field must be populated. EndDate PercentageCompleted Date This field is editable in runtime. DueDate Date This field is editable in runtime. WipOrderNo WipOrderType WipOrderTypeDescription OprSequenceNo LocationID Location ProductID ProductNo ProductDescription OrderQuantity CompletedQuantity Priority This field is editable in runtime. UomCode Status StatusDescription ParentWipOrderNo ParentWipOrderType ParentOprSequenceNo ProductionLineNo

22 Dispatching Board DELMIA Apriso 2017 Implementation Guide 22 ResourceID ResourceName ResourceTypeDescription ResourceClass ResourceClassDescription EquipmentID EquipmentName Facility OrderNo OrderType OrderTypeDescription OrderLineNo SerialNo LotNo ContainerNo ProgressStatus ProgressStatusDescription ProjectCode InventoryShortageDate Date WeighHeaderID Comment WorkCenter WBSCode TaskID Role SkillID EmployeeID EmployeeNo EmployeeName Department Team Shift PayRule WorkPeriod AllowChangeDuration Boolean AllowChangeStartDate Boolean AllowChangeProgress Boolean AllowAssignment Boolean ReadOnly Boolean IsHeld Boolean NoLaterThan Date

23 Dispatching Board DELMIA Apriso 2017 Implementation Guide 23 NoEarlierThan Date HasError Boolean LookName BrushName OriginalStartDate Date OriginalEndDate Date OriginalDurationInSeconds User1 User2 User3 User4 User5 User6 User7 User8 UserInt1 UserInt2 UserInt3 UserInt4 UserInt5 UserInt6 UserInt7 UserInt8 UserDate1 Date UserDate2 Date UserDate3 Date UserDate4 Date UserDate5 Date UserDate6 Date UserDate7 Date UserDate8 Date UserBoolean1 Boolean UserBoolean2 Boolean UserBoolean3 Boolean UserBoolean4 Boolean UserBoolean5 Boolean UserBoolean6 Boolean UserBoolean7 Boolean UserBoolean8 Boolean UserImage1 UserImage2

24 Dispatching Board DELMIA Apriso 2017 Implementation Guide 24 UserImage3 UserImage4 UserImage5 UserImage6 UserImage7 UserImage8 SortOrder PreferredStartTime 6.3 Behavior of the Control Configuration File The app.config file will control how the chart displays the initial data on the screen, hides the histogram, and enables read-only mode. <?xml version="1.0"?> <configuration> <appsettings> <!--Change this propery to decide the OnLoad option, if not specified, the default value will be 3 //1 - First Activity //2 - Last Activity //3 - Middle of the WorkSpace //4 - Current Date --> <add key="onloadscrollto" value="3" /> <!--Hide Histogram true false --> <add key="hidehistogram" value="false" /> <!--Is Read Only true false --> <add key="isreadonly" value="false"/> <!--Hide Employee filter true false --> <add key= hideemployee value= true /> <!--Hide WorkCenter filter true false --> <add key= hideworkcenter value= true />

25 Dispatching Board DELMIA Apriso 2017 Implementation Guide 25 <!--Hide Equipment filter true false --> <add key= hideequipment value= true /> </appsettings> </configuration> The onloadscrollto value controls which initial day to show on the chart. The possible values are: 1 date of the first activity 2 date of the last activity 3 date in the middle of the Workspace 4 the current date By default, the date will be in the middle of the Workspace dates. The hidehistogram value controls if the histogram should be visible or not on the control. The isreadonly value controls if the control should be read-only, meaning that the user is able to adjust the data but not to save it, as the options will not be present. The hideemployee, hideworkcenter, and hideequipment values control if the Employee, Work Center, and Equipment filter buttons should be visible or not in the Resources section of the control. The default for each is true Rules <?xml version="1.0" encoding="utf-8"?> <DispatchingBoardRules> <Rules> <Rule> <Priority>1</Priority> <LeftSide>EndDate</LeftSide> <RightSide>DueDate</RightSide> <Comparer>greaterorequal</Comparer> <Style>redbar_style taskbar-style</style> <AlternateStyle>greenbar_style taskbar-style</alternatestyle> </Rule> </Rules> </DispatchingBoardRules> The rules.xml file controls how the task will be displayed when certain conditions are met. The components of a rule are as follows: Priority this is the order of the execution of the rule evaluation, which has to be numeric and at least be one rule LeftSide can be any of the available fields for evaluation RightSide can be any of the available fields for evaluation (a date, an integer, or a Boolean value) The date must be in the MM/DD/YYYY format, and a Boolean value can be true or false.

26 Dispatching Board DELMIA Apriso 2017 Implementation Guide 26 Comparer this is the logical Operation that will be performed against the left side and right side Style the bar style to be chosen if the rule is true AlternateStyl the bar style to be chosen if the rule is false These are the values that Comparer can take (which are case-sensitive): lessthan greaterthan lessorequal greaterorequal equals different These are the values that Style and AlternateStyle can take: greenbar_style taskbar-style yellowbar_style taskbar-style redbar_style taskbar-style bluebar_style taskbar-style Additional styles can be created. For more information, see 6.11 Bar Styles. Limitations Rule evaluation is in the form of (LeftSide) Operator (RightSide), wherein the LeftSide type (integer, Boolean, or date) must match the type on the RightSide. Multiple Rules Multiple rules can be necessary and part of the same set. The user can add additional rules. They will be evaluated only if <AlternateStyle> is not present in the first set of rules but is present in the last rule. A rule node should always contain <AlternateStyle/> if an alternate style is not specified. <?xml version="1.0" encoding="utf-8"?> <DispatchingBoardRules> <Rules> <Rule> <Priority>1</Priority> <LeftSide>EndDate</LeftSide> <RightSide>DueDate</RightSide> <Comparer>greaterorequal</Comparer> <Style>redbar_style taskbar-style</style> <AlternateStyle/> </Rule> <Rule> <Priority>2</Priority> <LeftSide>EndDate</LeftSide> <RightSide>02/02/2015</RightSide> <Comparer>equals</Comparer> <Style>redbar_style taskbar-style</style> <AlternateStyle>bluebar_style taskbar-style</alternatestyle> </Rule> </Rules>

27 Dispatching Board DELMIA Apriso 2017 Implementation Guide 27 </DispatchingBoardRules> In the example above, if EndDate is greater or equal than DueDate, the rule will be evaluated a as false. If AlternateStyle is empty, it will evaluate the next rule on the priority list. For the second rule, if EndDate is equal to 02/02/2015, then it will show a red bar style, and if false it will show a blue bar. The scriptresources.cshtml File The scriptresources.cshtml file controls the custom JavaScript logic for each Workspace Class. 6.4 Mapping a Field to the Gantt Chart In this example, a custom UOM field will be added to the Gantt chart: 1 Open the _table.tmpl.cshtml file and add this code snippet: //Activity Table Column collection <!-- This collection contains the column definitions for the table on the left of the gantt. --> ((Columns)ViewData["ActivityColumns"]).Add(new Column() { field = "Activity.Name", title = LiteralHelper.GetMediumDescription(DispatchingBoardActivityColumnLiterals.Na me), width = 200, iseditable = false, //editor = "<input data-bind='nameeditor:activity.name' />", clienttemplate = "projectganttnametemplate" ); ((Columns)ViewData["ActivityColumns"]).Add(new Column() { field = "Activity.WipOrderNo", title = LiteralHelper.GetMediumDescription(DispatchingBoardActivityColumnLiterals.Wi porderno), width = 100, iseditable = false, //template = "<div>${data.activity.datasource.wiporderno()</div>" clienttemplate = "wipordernocolumntmplate" ); ((Columns)ViewData["ActivityColumns"]).Add(new Column() { field = "Activity.DataSource.ProductDescription()", title = LiteralHelper.GetMediumDescription(DispatchingBoardActivityColumnLiterals.Pr oductdescription), width = 100, iseditable = false//, //clienttemplate = "productdescriptioncolumntmplate" );

28 Dispatching Board DELMIA Apriso 2017 Implementation Guide 28 The ID and data template naming pattern have data-iseditable set to false. If this is set to true, the field becomes a text-editor after it is double clicked. 2 Open the _defaultresource.tmpl.cshtml file and add this code snippet: <script id="projectganttnametemplate" type="text/x-jquery-tmpl"> <div class="rq-grid-expand-indentwidth" style="height: 1px; width: ${data.indentwidthpx"></div> <div style="width: 12px; display: ${data.isparent? "block" :"none" " class="arrowcontainer"> <div onclick="expanderonclick(this,event)" id="arrow" class="${ data.isexpanded? " rq-grid-expand-arrow rq-grid-collapse-arrow": "rq-gridexpand-arrow" rq-ignore-click"></div> </div> <div class="rq-grid-expander-text">${data.activity.activityname</div> </script> <script id="wipordernocolumntmplate" type="text/x-jquery-tmpl"> <div>${data.activity.datasource.wiporderno()</div> </script> Note the naming pattern and that the name matches what was entered in the _table.tmpl.cshtml file. 3 The mapping happens with the PropName attribute, wherein PropName can be any of the fields from the available activity fields. 6.5 Converters Sometimes it is necessary to transform the data before rendering it into the chart. In order to do this, the user can write their own converter. In this example, a date format will be transformed into a short date: 1 Open the scriptresources.cshtml file and locate the duedatecolumn binding. Note that this field has a custom converter named ShortDateConverter. var $duedatecolumn = $("div.duedatecol", tr); if ($duedatecolumn.length == 1) { $duedatecolumn.bindcelltodata({ PropName: "DueDate", Source: data.activity.datasource, Converter: ShortDateConverter ); 2 The converter can be added in the same file: var shortdateformat = Date.CultureInfo.formatPatterns.shortDate; ShortDateConverter = { Convert: function (value, src, tar) { if (value!= null) { return value.to(shortdateformat);

29 Dispatching Board DELMIA Apriso 2017 Implementation Guide 29 The convert method will take the value and then return the transformed value. The values can be casted to different types as long the boxing and unboxing of the values is valid. 6.6 Mapping Fields to the Flexy Gantt Chart The mapping of fields for the Flexy Gantt Chart is done with converters. In this example, the production line field will be mapped: 1 Open the _table.tmpl.cshtml file and locate flexytable: //Resource Table Column collection <!-- This collection contains the column definitions for the table on the left of the gantt. --> --> <table id="flexytable"> <thead> <tr> 2 Copy the code snippet representing the production line header: ((Columns)ViewData["ResourceColumns"]).Add(new Column() { field = "Name", title = LiteralHelper.GetMediumDescription(DispatchingBoardResourceColumnLiterals.Na me), width = 110, iseditable = false, clienttemplate = "flexyganttnamecolumntemplate" ); ((Columns)ViewData["ResourceColumns"]).Add(new Column() { //field = "", title = LiteralHelper.GetMediumDescription(DispatchingBoardResourceColumnLiterals.Ca pacity), width = 110, iseditable = false, clienttemplate = "capacityflexycolumntemplate" ); 3 Open the _defaultresource.tmpl.cshtml file and copy the code snippet representing the production line header: <!-- Resource table column template--> <script id="flexyganttnamecolumntemplate" type="text/x-jquery-tmpl"> <div class="rq-grid-expand-indentwidth" style="height: 1px; width: ${RadiantQ.Gantt.LevelToIndentWidth(data.Level(), data.isparenttype())px"></div> <div style="width: 12px; display: ${data.isparenttype()? "block" : "none" " class="arrowcontainer">

30 Dispatching Board DELMIA Apriso 2017 Implementation Guide 30 <div onclick="expanderonclick(this,event)" id="arrow" class="${data.hierarchicalitem.isexpanded()? "rq-grid-expand-arrow rq-gridcollapse-arrow": "rq-grid-expand-arrow" rq-ignore-click"></div> </div> <div class="rq-grid-expander-text">${fgnameconverter(data)</div> </script> <script id="capacityflexycolumntemplate" type="text/x-jquery-tmpl"> <div>${(data.data()["capacity"] == null)?"":data.data()["capacity"]</div> </script> <script id="productionlineflexycolumntemplate" type="text/x-jquery-tmpl"> <div>${(data.data()["user3"] == null)?"":data.data()["user3"]</div> </script> <script id="nextmaintenancedateflexycolumntemplate" type="text/x-jquerytmpl"> <div>${(data.data()["nextmaintenancedate"] == null)?"":formatdate(data.data()["nextmaintenancedate"],"mm/dd/yyyy")</div> </script> 4 In the scriptresources.cshtml file, create the converter: productionlineconverter = function (flexynodedata) { var data; if (flexynodedata) data = flexynodedata.data(); else data = this.data; if (data["productionlineno"]) return data["productionlineno"]; ; return; Note that data[ ProductionLineNo ] is doing the mapping, and this value can be any field from the available activity fields. 6.7 Custom Execution Progress Calculation It is possible to modify the way in which the Execution Progress field displayed in tooltips for each task is calculated. To do this, open the scriptresources.cshtml file and find the CustomProgressCalculation function. By default, the CustomProgressCalculation function returns the percentage completed value from the database: function CustomProgressCalulation(activity) {

31 Dispatching Board DELMIA Apriso 2017 Implementation Guide 31 return activity.datasource.percentagecompleted(); To implement a custom calculation of the percentage completed value, uncomment and modify the second example given in the function: function CustomProgressCalulation(activity) { var totaleffort = RQTimeSpan.Zero_M(); var completedeffort = RQTimeSpan.Zero_M(); for (var i = 0; i < activity.childactivities_m().length; i++) { var child = activity.childactivities_m()[i]; var childeffort = child.cumulativeeffort_m(); totaleffort = totaleffort.add(childeffort); completedeffort = completedeffort.add(rqtimespan.fromticks(childeffort.ticks_m() * (child.progresspercent_m() / 100))); if (totaleffort == RQTimeSpan.Zero_M()) return 0.0; else return (completedeffort.ticks_m() / totaleffort.ticks_m()) * 100.0; 6.8 Custom Context Menus There are three types of context menus: Table Task Flexy Task The Dispatching Board solution supports custom context menus for PCs as well as Android and Windows mobile devices Table Context Menu To add a custom table context menu, open the scriptresources.cshtml file and locate the projectganttcontextmenuitems function. projectganttcontextmenuitems(ganttcontrol) { var tablecontextmenu = ganttcontrol.tablecontextmenu; This variable holds all of the Menu Items for the table: var tablemenuitems = [ In order to add more items, the following will need to be added to the collection: { keyname: name to display, name: name to display, callback: function (key, opt) { var datacontext = $(opt.$trigger[0].parentelement).data(); var selecteditem = ganttcontrol.selecteditem;

32 Dispatching Board DELMIA Apriso 2017 Implementation Guide 32 var ganttchart = $ganttchart.data("ganttchart") $gant tchart.data("radiantqganttchart"); //Custom Logic The name to display and custom logic are the variable sections. The name to display controls the name that the menu will show. Custom logic can be any valid JavaScript or jquery code that corresponds to this menu. If it is necessary to access a relative of the clicked row, it can be extracted from the datacontext object as datacontext.griditem.activity.availablefield, wherein AVAILABLEFIELD is an available activity field Task Context Menu To add a custom table context menu, open the scriptresources.cshtml file and locate the projectganttcontextmenuitems function. function projectganttcontextmenuitems(ganttcontrol) { var tablecontextmenu = ganttcontrol.tablecontextmenu; This variable holds all of the Menu Items for the table: var taskmenuitems = [ In order to add more items, the following will need to be added to the collection: { keyname: name to display, name: name to display, callback: function (key, opt) { var datacontext = $(opt.$trigger[0].parentelement).data().gantttaskitembar; //Custom Logic The name to display and custom logic are the variable sections. The name to display controls the name that the menu will show. Custom logic can be any valid JavaScript or jquery code that corresponds to this menu. If it is necessary to access a relative of the clicked row, it can be extracted from the datacontext object as datacontext.availablefield, wherein AVAILABLEFIELD is an available activity field Flexy Task Context Menu To add a custom table context menu, open the scriptresources.cshtml file and locate the flexyganttcontextmenuitems function. function flexyganttcontextmenuitems(gantt) { This variable holds all of the Menu Items for the table: var tablemenuitems = [

33 Dispatching Board DELMIA Apriso 2017 Implementation Guide 33 In order to add more items, the following will need to be added to the collection: { keyname: name to display, name: name to display, callback: function (key, opt) { var datacontext = $(opt.$trigger[0].parentelement).data(); var selecteditem = ganttcontrol.selecteditem; var ganttchart = $ganttchart.data("ganttchart") $gant tchart.data("radiantqganttchart"); //Custom Logic The name to display and custom logic are the variable sections. The name to display controls the name that the menu will show. Custom logic can be any valid JavaScript or jquery code that corresponds to this menu. If it is necessary to access a relative of the clicked row, it can be extracted from the datacontext object as datacontext.griditem.activity.availablefield, wherein AVAILABLEFIELD is an available activity field. Adding a Context Menu to Open a Maintenance Calendar 1 Copy the FlexPart URL of the Maintenance Calendar:

34 Dispatching Board DELMIA Apriso 2017 Implementation Guide 34 2 Add the context menu as follows (a general context menu is being used as an example): function generalcontextmenuitems() { //example how to add general context menu item to each control var activitychartcontextmenu = new RadiantQ.ContextMenuImpl.ContextMenu('.rq-gc-chartArea-div'); activitychartcontextmenuitems = [ { keyname: "MaintenanceCalendar", name: "Maintenance Calendar", callback: function (key, opt) { if (opt.$trigger.parents('.rqganttbase').data('ganttcontrol')!= undefined) { window.open( <FlexPart URL>,, "width=800,height=600"); ]; activitychartcontextmenu.addnewitems(activitychartcontextmenuitems, false); 3 The Maintenance Calendar context menu is now available when the configured workspace is opened and it can be accessed from the order schedule visualization screen:

35 Dispatching Board DELMIA Apriso 2017 Implementation Guide 35 4 Additionally, because Maintenance Calendar is an M&M screen, a new screen will be opened with this link: Clicking the link will invoke the Maintenance Calendar screen in the ADC. 6.9 Customizing the Look and Feel of the Control Customizing the look and feel of the control can be done with two separate files: _defaultresource.tmpl.cshtml controls the look for each cell on the table for both Gantt and Flexy Gantt charts _table.tmpl.cshtml controls the headers on the table for both Gantt and Flexy Gantt charts Cells Open the _defaultresource.tmpl.cshtml file and locate the name that matches the cell that is to be modified from the data-template attribute from the _table.tmpl.cshtml file. In our example, we are modifying the namecol header that has an associated data-template named namecolumn-tmpl. To change the look and feel of the cell, the contained div element will need to be modified and a custom CSS style will need to be added. In the following example, the size of the cell text has been changed to 12px: <script id="resourcenameflexycolumn-tmpl" type="text/x-jquery-tmpl"> <td class="ui-widget-content"> <div class="resourcenameflexycol" style="font-size: 12px;"> </div> </td> </script> The same logic for changing the Flexy Gantt chart applies.

36 Dispatching Board DELMIA Apriso 2017 Implementation Guide Flexy Gantt Cells Find the flexytable table in the _table.tmpl.cshtml file: <table id="flexytable"> <thead> <tr> Different th elements control the headers for the Flexy Gantt Chart. In this example, the width has been changed to 100px: <th id="resourcenameflexycol" style="width: 100px;" datatemplate="#resourcenameflexycolumn-tmpl" data-iseditable="false"> <script type="text/javascript"> $("th#resourcenameflexycol").empty().append(window["radi antq_resources"]); </script> </th> Flexy Gantt Headers Find the flexytable table in the _table.tmpl.cshtml file: <table id="flexytable"> <thead> <tr> Different th elements control the headers for the Flexy Gantt Chart. In this example, the width has been changed to 100px: <th id="resourcenameflexycol" style="width: 100px;" datatemplate="#resourcenameflexycolumn-tmpl" data-iseditable="false"> <script type="text/javascript"> $("th#resourcenameflexycol").empty().append(window["radi antq_resources"]); </script> </th> Headers To modify the Gantt chart, open the _table.tmpl.cshtml file and locate the table with the ID of gantttable. <table id="gantttable"> <thead> <tr id="table-headerrow"> Below the table-header tr-row, there are multiple th elements. Each th element is mapped to an individual field. In order to modify the look and field of the header, you will need to modify the style attribute of the th elements using CSS. In the following example, the width of the header is set to 200px: <th id="namecol" style="width: 200px;" data-template="#namecolumn-tmpl" data-iseditable="false"> <script type="text/javascript"> $("th#namecol").empty().append(window["radiantq_namestri ng"]);

37 Dispatching Board DELMIA Apriso 2017 Implementation Guide 37 </script> </th> Size of the Controls To change the size of the controls, edit this file: <drive>\program Files\Dassault Systemes\DELMIA Apriso 2017\WebSite\DispatchingBoard\Content\Styles\main.css. #gantt_content { height: 600px; visibility: hidden; display: none; #gantt_container { height: 50%; visibility: hidden; #gantt_container1 { height: 50%; visibility: hidden; The gantt_content style is the holder for both controls, and it is expressed in pixels. The other two container styles are represented in percentages relative to the holder. When changing the size of a control, it must be changed first with the gantt_content style and then with the percentages. The visibility attribute must not be changed Tooltips To change the look and feel of the tooltip that appears when the use hovers over the taskbar, edit the Index.cshtml file, which is usually located at: <drive>\program Files\Dassault Systemes\DELMIA Apriso 2017\WebSite\DispatchingBoard\ view\home\index. Make a backup of the file before editing. When editing, the following code snippet will be found: <!--The template for the custom tooltip. --> <script id="fgtasktooltiptemplate" type="text/x-jquery-tmpl"> <div class='tasktooltip'> <div align='center'>${window["flexnet_nametooltip"]: ${FGnameConverter()</div> <div> <span>${window["flexnet_starttimetooltip"]: ${FGstartTimeTooltipConverter() </span></br> <span>${window["flexnet_endtimetooltip"]: ${FGendTimeTooltipConverter() </span> </div> </div> </script>

38 Dispatching Board DELMIA Apriso 2017 Implementation Guide 38 How the tooltip looks can be changed by editing the HTML and CSS. Do not remove the ${window[name] and converter functions, as they are responsible for binding the data to the tooltip Workspace Details Pop-Up Window To customize the Workspace Details pop-up window, configure the _defaultresource.tmpl.cshtml within each Workspace Class folder: <!--The template for the custom filter detail. --> <script id="workspacedetailtemplate" type="text/x-jquery-tmpl"> <div class='detailtable'> <span>work Center:${$data.Data.WorkCenter</span></br> <span>order Type:${$data.Data.User1</span></br> <span>process:${$data.data.user2</span> </div> </script> 6.10 Custom Time Headers In the scriptresources.cshtml file, headers to be shown at runtime can be added and removed. By default, five headers will be active for both charts. Five is the maximum number of headers allowed for each chart. The number of headers on one chart must match the number of headers on the other chart. The headers must be in order, from the largest time scale to the smallest. The headers must not contain gaps between them (that is, months must follow weeks, weeks must follow days, etc.). At least one header must be present on both charts. $(document).ready(function () { ); availableheadercollection.push(monthheaderline()); availableheadercollection.push(weekheaderline()); availableheadercollection.push(dayheaderline()); availableheadercollection.push(hourheaderline()); availableheadercollection.push(minuteheaderline()); availableheadercollectionflexy.push(monthheaderline()); availableheadercollectionflexy.push(weekheaderline()); availableheadercollectionflexy.push(dayheaderline()); availableheadercollectionflexy.push(hourheaderline()); availableheadercollectionflexy.push(minuteheaderline());

39 Dispatching Board DELMIA Apriso 2017 Implementation Guide Bar Styles Styles for bars can be added and modified. In the barstyles.css file located at <drive>\program Files\Dassault Systemes\DELMIA Apriso 2017\WebSite\DispatchingBoard\Scripts\rqgantt\styles, these four styles can be found:.greenbar_style { height: 20px; background-image: url(images/greenbar.png)!important; -moz-background-size: 100% 100%!important; -o-background-size: 100% 100%!important; -webkit-background-size: 100% 100%!important; background-size: 100% 100%!important; background-repeat: no-repeat!important; border: 1px solid green!important; border-radius: 7px!important; float: left!important; position: absolute!important; z-index: 10!important;.yellowbar_style { height: 20px; background-image: url(images/yellowbar.png)!important; -moz-background-size: 100% 100%!important; -o-background-size: 100% 100%!important; -webkit-background-size: 100% 100%!important; background-size: 100% 100%!important; background-repeat: no-repeat!important; border: 1px solid yellow!important; border-radius: 7px!important; float: left!important; position: absolute!important; z-index: 10!important;.redbar_style { height: 20px; background-image: url(images/redbar.png)!important; -moz-background-size: 100% 100%!important; -o-background-size: 100% 100%!important; -webkit-background-size: 100% 100%!important; background-size: 100% 100%!important; background-repeat: no-repeat!important; border: 1px solid red!important; border-radius: 7px!important; float: left!important; position: absolute!important; z-index: 10!important;.bluebar_style { height: 20px; background-image: url(images/taskbar.png); -moz-background-size: 100% 100%!important; background-size: 100% 100%!important;

40 Dispatching Board DELMIA Apriso 2017 Implementation Guide 40 background-repeat: no-repeat!important; border: 1px solid #050DFA!important; border-radius: 7px!important; float: left!important; position: absolute!important; z-index: 10!important; To change the background, create a custom.png with the dimensions of 110x17 pixels, and then replace the background-image value with the custom image. If a new style is added, the jquery.fn.rqgantt.js file located at <drive>\program Files\Dassault Systemes\DELMIA Apriso 2017\WebSite\DispatchingBoard\Scripts\flexnet\rqgantt will need to be modified in order to include the new style on the removeclass list. // DragAndDrop code Starts function OnTaskBarLoad(taskItemControl) { var activity = taskitemcontrol.options.activityview.activity; var classname = evaluaterule(activity.datasource); //remove all possible styles $(this).removeclass("greenbar_style taskbar-style rq-gc-taskbar ); $(this).removeclass("yellowbar_style taskbar-style rq-gc-taskbar"); $(this).removeclass("redbar_style taskbar-style rq-gc-taskbar"); $(this).removeclass("bluebar_style taskbar-style rq-gc-taskbar"); $(this).addclass(classname); // Create a Draggable of rendered bar. // Here datacontext(this) is a taskbar element. if (subscribedraggablebar) subscribedraggablebar(this); function OnFGTaskBarLoad(taskItemControl) { var task = taskitemcontrol.options.data; var classname = evaluaterule(task); //remove all possible styles $(this).removeclass("greenbar_style taskbar-style rq-gc-taskbar"); $(this).removeclass("yellowbar_style taskbar-style rq-gc-taskbar"); $(this).removeclass("redbar_style taskbar-style rq-gc-taskbar"); $(this).removeclass("bluebar_style taskbar-style rq-gc-taskbar"); $(this).addclass(classname);

41 Dispatching Board DELMIA Apriso 2017 Implementation Guide 41 7 Configuration Sequence 1 Create the Workspace Class (see 5.1 Workspace Class Configuration). 2 Configure the Create, Load, and Apply Standard Operations and the Theme folder of the Workspace Class (see 5.3 Standard Operation Configuration). 3 To configure the Determination Functions, use the configured Standard Operations and the Theme folder: Figure 8 Selecting Standard Operations for Determination Figure 9 Determining the "Create" Standard Operation Figure 10 Determining the "Load" Standard Operation Figure 11 Determining the "Apply" Standard Operation

42 Dispatching Board DELMIA Apriso 2017 Implementation Guide 42 Figure 12 Determining the Theme folder 4 Configure the theme of the Workspace Class including the table template, color rules template, and context menu template (for more information, see Adding a Context Menu to Open a Maintenance Calendar. 7.1 Roles Roles have to be linked with Menu Items and employees. To define Roles, navigate to the Role screen in the ADC. One Role can be linked with many employees and many Menu Items in order to, for example, provide access to three different Dispatching Board functions. The Dispatching Board Roles provided out-of-the-box are: Role Dispatching Board Administrator Description Allows the user to change the global configuration settings (this role is targeted at Application Implementation Specialists only). To implement (suggested usage), configure this Role to enable modification of the Determinations for each Workspace Class (e.g., the load/create/apply/template Operations). Dispatching Board Inspection Planner Allows the user to see and modify the schedules of all inspection orders for all Work Centers and resources. To implement (suggested usage), create a Workspace Class for this scenario and add logic to APR_DB.Create (which contains the Create Workspace screen) so that only a user with this Role can create such a Workspace Class.