{"id":386,"date":"2022-06-27T12:38:11","date_gmt":"2022-06-27T16:38:11","guid":{"rendered":"https:\/\/blog.uvm.edu\/iwms\/?p=386"},"modified":"2023-02-17T11:44:32","modified_gmt":"2023-02-17T16:44:32","slug":"integration-testing-training-in-that-order","status":"publish","type":"post","link":"https:\/\/blog.uvm.edu\/iwms\/2022\/06\/27\/integration-testing-training-in-that-order\/","title":{"rendered":"Integration, Testing, & Training\u2013In that order"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Planon and a myriad of UVM\u2019s other software programs (e.g., Peoplesoft, Kronos) must be able to \u201ctalk to one another<\/em>\u201d for data and information to be pulled into or pushed out of Planon in a useful and accurate way.  Integration<\/a><\/strong> is a fancy way of saying this, and the magic of getting software to work well together relies on behind-the-scenes efforts by the Enterprise Technology Services department, spearheaded by the talented duo of Christian Behr and Justin Banker on UVM’s Enterprise Application Services team .<\/p>\n\n\n\n

The Core Team and Planon have wrapped up the Integration Design steps this past month. All Integration Design documents have been signed off, including: Purchasing (i.e., how Planon and Peoplesoft talk<\/em> back & forth about what we buy, how much we buy, our vendors, and when they are paid); Kronos\/HR Payroll (i.e. how Planon and Kronos talk <\/em>to each other to accurately record hourly employees\u2019 time & attendance and to accurately capture \u201ceffort\u201d billed against work orders. This integration also pulls in all the data about employees and students who may be users of the Planon system; and Fuel Card (i.e., how Planon will talk to the Voyager Fleet Commander credit card system so we can track fuel purchases for UVM-owned vehicles (\u201cassets\u201d) in the same place where vehicle operations & maintenance records are kept.<\/p>\n\n\n\n

Our next big step before a real testing<\/a> <\/strong>version of the software is available is uploading real and existing data from FAMIS. This data upload includes all floor plan drawings, property and space data, asset information, etc. (Hence, the reason that Campus Planning has been pushing departments to complete their annual space inventory in a timely fashion).<\/p>\n\n\n\n

Thinking ahead to training<\/strong> in the fall, we are considering various methods to effectively get users on board. People have suggested a written manual, a set of \u201cmini-manuals,\u201d and short video tutorials linked to a website or ETS\u2019s IT Knowledgebase. Training might include an initial series of MS Teams meetings where participants can login to Planon themselves and follow along, or perhaps regularly scheduled \u201cdrop-in help\u201d hour each week. We know many users would like to have a \u201csandbox\u201d environment to learn the new software (without risk of breaking it!) There seems to be consensus that in-person trainings inside a computer lab would not<\/em><\/strong> be well attended.<\/p>\n\n\n\n

Lastly, looking way ahead to Phases 2 and 3 implementation of Planon, the Core team has held initial  conversations with stakeholders involved in EHS (Environmental Health and Safety) functionality, Sustainability Tracking functions, and the eventual replacement of the ResLife Fixit app with Planon.<\/p>\n\n\n\n

Monthly Q&A Open Forums are scheduled for June, July and August.<\/p>\n\n\n\n

Stay tuned.
~The IWMS Core Implementation Team<\/p>\n","protected":false},"excerpt":{"rendered":"

Planon and a myriad of UVM\u2019s other software programs (e.g., Peoplesoft, Kronos) must be able to \u201ctalk to one another\u201d for data and information to be pulled into or pushed out of Planon in a useful and accurate way.  Integration is a fancy way of saying this, and the magic of getting software to work … <\/p>\n

Continue reading “Integration, Testing, & Training\u2013In that order”<\/span><\/a><\/p>\n","protected":false},"author":2984,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-386","post","type-post","status-publish","format-standard","hentry","category-uncategorized","entry"],"featured_image_src":null,"featured_image_src_square":null,"author_info":{"display_name":"espiegel","author_link":"https:\/\/blog.uvm.edu\/iwms\/author\/espiegel\/"},"_links":{"self":[{"href":"https:\/\/blog.uvm.edu\/iwms\/wp-json\/wp\/v2\/posts\/386","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.uvm.edu\/iwms\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.uvm.edu\/iwms\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.uvm.edu\/iwms\/wp-json\/wp\/v2\/users\/2984"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.uvm.edu\/iwms\/wp-json\/wp\/v2\/comments?post=386"}],"version-history":[{"count":5,"href":"https:\/\/blog.uvm.edu\/iwms\/wp-json\/wp\/v2\/posts\/386\/revisions"}],"predecessor-version":[{"id":471,"href":"https:\/\/blog.uvm.edu\/iwms\/wp-json\/wp\/v2\/posts\/386\/revisions\/471"}],"wp:attachment":[{"href":"https:\/\/blog.uvm.edu\/iwms\/wp-json\/wp\/v2\/media?parent=386"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.uvm.edu\/iwms\/wp-json\/wp\/v2\/categories?post=386"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.uvm.edu\/iwms\/wp-json\/wp\/v2\/tags?post=386"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}