We build an SVC class into the Lifecycle Work solution, stood up with the product itself, and provide that WSDL for reference in the Subtask. This is where we turn to our old trusty friend, the Web Service (*.asmx OR *.svc). We can see the design in MM_WMS_DESIGN, Work Locations in MM_WMS_WORK_LOCATION, CUs in MM_WMS_COMPATIBLE_UNIT – we have all the pieces we need to create a fully-fledged estimate in Lifecycle.īecause Lifecycle has access to the Process database, giving us the data for an estimate in Lifecycle, we just need to come up with a way to tell Lifecycle to create the estimate. However, we need a way to move our completed design from ArcFM™ Designer to Lifecycle. The way Lifecycle is implemented in this example, we allow Lifecycle to update GIS/Process, but we don’t allow GIS to update Lifecycle. This creates a new Work Request in my Workflow Manager queue from which I can create a new design. As the Work Request is processed through its workflow in Lifecycle, we use these matching Statuses/States to keep the Work Request up to date in Designer as well. This enables the Work Request to exist in both the Lifecycle Tables as well as the Process Tables and remain in sync – at least as far as status goes. The list of potential STATEs for NODE_TYPE “WorkRequest” should exactly match the list of Work Request statuses in Lifecycle. MM_PX_STATE has STATE_ID, which we’ll be using for the insert on MM_PX_CURRENT_STATE. When we create the new row in MM_WMS_WORK_REQUEST, we’ll need to perform an insert on MM_PX_CURRENT_STATE as well to ensure that the Work Request has an initial state, which will be important for executing transitions in Workflow Manager. This step assumes some of the initial setup has already taken place. “Service Request ID” = the auto-increment (identity) primary key column on the ServiceRequest table in the Lifecycle database.May have a special naming convention to indicate the type of work being performed or other idiosyncracies “Service Request Number” = the in-house identifier for a given Work Request (Service Request).The process begins with creating a new Work Request (aka Service Request) in Lifecycle. Here is an example of how we utilize all 3 of these methods to create a new Work Request in Lifecycle Work, create a new Design in ArcFM™ Designer, and send it back to Lifecycle Work to create an Estimate. Sample – Folder Subtasks (Schneider Electric).Workflow Manager Subtasks (Schneider Electric).Making Your Subtask Version-Aware (SSP).If you haven’t made a custom ArcFM™ Subtask/AutoUpdater before, take a look at these resources to give you some ideas. ![]() Using custom-built SubTasks and AutoUpdaters, we are able to execute custom code from ArcFM™, allowing us to make calls to the exposed Web Services or perform any number of other tasks. Lifecycle is given database permissions to perform inserts and updates into the process schema, allowing for database-driven creation of Designer objects. Well, that’s exactly what we’ve done, using these three methods:īoth Lifecycle Work and Lifecycle Assets expose web services for use by GIS to directly provide information to external software. Why not integrate the two? Why not wire up the products to take a complex design built in ArcFM™ Designer and allow that information to populate an estimate in Lifecycle Work? While this may not be terrible for something like a single-CU pole replacement or an LED Upgrade, if you’re working on a large-scale upgrade, you’re not going to want to have to double up on the work to create the estimate, not only for efficiency’s sake, but also due to the possibility of user error while entering 45 work locations, all with multiple CUs and ad-hoc resources. In practice, a user may use ArcFM™ Designer to create a design for a particular job – adding Compatible Units/Construction Standards (hereafter referred to as CUs), resources, work locations, all that, and then turn to the Estimate Worksheet in Lifecycle Work to basically redo the entire design in order to get an estimate for purchasing. If you’ve worked in SSP Lifecycle before, you know that its entire mission is handling Work Requests and creating smart estimates based on the work being done. If you’ve worked in ArcFM™ Designer before, you know that a lot of it is centered around creating GIS designs that are specifically attached to a Work Request. Let’s also say you have a workforce management system. Say your GIS team is using Schneider Electric’s ArcFM™ Designer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |