2015-01-20

CAFM the first year Part 5

Back in November (~checking calendar~ Holy cannoli! How it is the end of January already!?!?) I began a series of articles on how I've adjusted in my new role.
While I have spent my entire career in a post-occupancy setting, coordinating CAD/BIM and technology projects on an Engineering team for a large medical facility is much different than administering a CAFM/CMMS for an equally large (though much more far-flung) office environment.

This is my final installment in that series, tasks which I have begun working on, and which I will continue to plow through. I will link to the other articles at the bottom of this post.



Goal Setting
I won't bore you with any more talk of goal-setting after my last article. But, of course, I managed to tie my personal goal up into one of the goals for my department. We aim to improve our stewardship of the assets in our care this year, by changing the way that we track and monitor them (in some cases that means collecting more data, in others, it just means taking time to analyze that data to see what bubbles to the top and can inform our choices. Applied analytics or organizational informatics is what this is... oh, yeah, big data, baby!).

Data Auditing
My personal aspiration is to audit every SQL data table in my Archibus installation.
585 tables. I've audited 26 so far.
That is a bit misleading, though. I might open a table to see what it contains, and detect where the data gaps are. But, a true audit will only come about when I reference tables against each other. That is a little harder to track, but, I have a future post in mind about how to streamline this for long-term use.

Examples (skip this if you're not a hopeless nerd who gets off on organizing and trending massive datasets, seriously, I won't be offended)
Our real estate manager routinely runs reports on our active leases. I can't even conceive of all of the metrics she has established for these, but, one of the more important data points when querying for her report is whether a lease is active or inactive. Her regular audits and established processes ensure this data is always kept accurate.
However, each of these leases is also assigned to a building. I found by looking at the building table that no one was currently marking when a building was no longer being used. This was evidently done by another employee in the past. This can have repercussions in all of our modules. So, I created a process to address this, and had myself inserted into the move notifications, so, the project manager who moves us from one location to another sends out a mass email to those who need to know, which now includes me. At the appointed time, I mark the building inactive and move the Work Requestor employees from the old building to the new one, ensuring maintenance and other records are applied to the correct location.

I mentioned in Part 3 of this series, that I detected some problems in our maintenance KPIs (key performance indicators), in that there were too many generic work requests, which could have fit into existing categories for more granular and accurate tracking. Making things easier for the (non-maintenance) work requestors involved paring the main list of problem types from 32 down to 16, and renaming some to be more clear (such as switching 'Mechanical' to 'Heating & Cooling'), and adding sub-types for common issues.
As we were having this discussion, we actually talked about having keys made, which we did outsource, but, after I asked our corporate facilities manager how much we spent on that, she got a quote for a key machine and we saw the ROI was at 18 months. Bam, now one of the guys makes keys in-house for us, saving both money and time (that's like $^2, right?).
That is analytics informing business decisions and process change. Beauty.

I recently streamlined the room types table, but, it could probably still use a bit more tightening up, I need to consult with our corporate facility manager and vp before I make any further changes, as they are the experts on how our buildings are currently used and might be in the future.

I mentioned above how I will only have a complete audit when I reference some of the tables against one another. For example, I can look at the rooms database and see if there is a space number which isn't linked to a dwg (an orphaned space designator after a renovation, or a number manually entered during an employee move which doesn't actually exist?), and I can look at the employee table and ensure all information is filled in. But, it isn't until I pull these two tables together that I see that maybe there are three employees assigned to one cube, and I know we're not THAT crowded. That is the point where we chase down possible causes and implement new procedures, or tweak the views where users input data.

Rather than going on and on with similar examples and possibilities, I'll wrap up now.

Have you done some data auditing? Did it help you prevent mistakes? Save you money? Cause you to outsource or bring new functions in-house?


http://mistressofthedorkness.blogspot.com/2014/11/cafm-first-year-part-1.html
Upgrading Archibus from release 18.1 to 21.1, and after some unresolved errors, ultimately to version 21.2. Migrating data, forms and users, documenting as I learned about our processes.

http://mistressofthedorkness.blogspot.com/2014/11/cafm-first-year-part-2.html
Learning how our real estate team works and customizing a form with numerous panels, in order to keep the information together and easily accessible... and the crazy unexpected and hard to reproduce errors that slowed us down for a few weeks.
It's important to build good rapport with your users and remind them to report errors as soon as they happen (good users try to work around problems, but, that doesn't solve them).

http://mistressofthedorkness.blogspot.com/2014/11/cafm-first-year-part-3.html
Adding 500 branches to our CMMS (for work orders, we'll tackle preventative maintenance later on, the branch team is still streamlining our hvac contracts and working up standard procedures for our equipment) and creating a simple end user tutorial on entering work requests.
The whole branch team now has an SLA and is using the new Operations Console in WebCentral, but, I still need to migrate our corporate team from the old pages, their user roles and VPA restrictions will need to be wiped and started over, as there is a lot of customization on their current settings which prevent their seeing content in the new Console.

http://mistressofthedorkness.blogspot.com/2014/11/cafm-first-year-part-4.html
Archibus's bread and butter is space asset management. Migrating tasks and functions from the thick client to WebCentral and introducing the Space Console and making plans to capture common spaces not currently polylined.

2015-01-17

Setting a goal you can actually achieve

I have never been the type to set resolutions on New Year's Day, though if it is an effective motivator, I fully support all who do.

With everyone's talk of goals recently, I have been reminded of goal-setting at work (which we complete by October 1st). 

If any of you have done goal-setting in the corporate environment, you might be familiar with the SMART acronym. The guideline that prompts us to make our goals; specific, measurable, attainable, realistic, and time-bound.


I have underlying motivators all the time; complete a pet project at work, find interesting side-gigs, obtain a new job, pay off debt, save for retirement. 
Admittedly, I am a details person, I usually see the trees and not the forest. Baby steps are what have moved me along my journey to reach each milestone in my life. I do NOT usually make my goals time-bound, though, and could really stand to work on that.

So, I'd like to encourage you to think about any 'wishes', 'desires', 'dreams', you may have. 
Turn those wants into something actionable!

Want a new job?
Be specific about what that really means.
Obtain a role focused on "project management" for a "company with a good family atmosphere or work life balance" in "a city I would like to move to" paying at least "$67,000 a year with decent benefits" by "January 1st of 2016."

There are things you can do to increase your chances of receiving a job offer. Those can be measurable.
Attend at least five networking events.
Update my resume (and portfolio, if applicable).
Send my resume to three trusted friends for review and feedback.
Update my resume based on that feedback.
Visit all online accounts and ensure they are up to date, so potential employers can contact me (LinkedIn, AUGI, other professional organizations, social accounts... link them all to the same *personal* email account, so contacts from your network can be in touch consistently also update your job title/duties and headshots so they are current).
Write three articles for "industry publication and/or guest post on industry blog".
Practice public speaking.
Obtain a certification.

Now, some of these could actually be goals in their own right, but, I'm just attempting to get you to brainstorm for now. 
Maybe your goal for this year should really be to "raise my professional profile" and next year will be "to obtain a new role". 
If you feel your next dream job isn't attainable until you get more practice speaking or take additional training, then adjust your goals to focus on those steps first. Hosting lunch & learns, speaking at a LUG, recording a podcast, joining toastmasters, etc can help you be a better speaker and raise your profile.

Are your to-do list items relevant and realistic?
If you want to be a data analyst, you might want a Revit MEP certification, but, it isn't really relevant to your goal. And, while you might want an MCSE to help obtain a role as an IT Manager, if you don't have the time and money for a course and studying and testing, it might not be a realistic task for now.

And, of course, just like most writers and project managers, I am useless without a deadline. Your checkpoints need to be time-bound.
Organize the things that will move you toward getting that job offer, and set deadlines for yourself.
Don't wait until summer to begin attending networking events, because they're sparsely scheduled and attended while folks are doing family vacations, so, spring is probably a better starting point.

Goal setting

I use job searching as my example for goal-setting, because almost all of us have gone through the process more than once and can identify with it.
Maybe your goal is to change a major process at work, or switch software platforms, or start a personal hobby to take your mind off of work.

Whatever your goal may be, you can reach it, if you organize your thoughts and provide yourself some checkpoints to keep you motivated and moving forward.

Any goal-setting or goal-checking advice? I'd love to hear what works for you.

2014-12-28

OT: Lord of the Rings punwar

If you've been here to my blog, you can identify two of my great loves fairly easily... Puns and Lord of the Rings.

Back in October, I posted a LOTR joke on Facebook (after it completely flopped at work), and, because I have the most awesome friends on the planet, it spiraled into the world's best punwar. I think it is worthy of preserving for posterity:


Melanie Stone: I sometimes forget I'm no longer surrounded by nerds.
A couple of my coworkers were complaining of being cold, and two others said they were warm.
When my opinion was solicited, I firmly stated that it was so hot in here, I just saw two hobbits walk past and throw a ring at me.
~crickets~

Jesse Dowling: Whatch' you talkin' bout Baggins's?

MS: Just making literary references, it's a bad hobbit of mine.

Chris Benner: No matter how hard I try, your pun humor simply dwarfs mine!

MS: You're so kind. I can't seem to help mys elf.

JD: Oh no you didn't! IT takes a lot of Goll-um... to start a pun war like that.

MS: Oh no I did ent?
Oh yes I did!

CB: you just keep dragon 'em out of nowhere...

MS: My bad sense of humor is the Oliphaunt in the room.
I am such a huge dorc.

JD: This could turn in to a real Eye-Saur-on this thread...

CB: you really should learn to con troll yourself.

MS: Singin Eoh, where's my Lego
las

JD: that really Stings.

MS: Nice earWormtongue, eh? Here's another:
If you like it then you shoulda put a GlamdRing on it!
Oh oh oh oh oh oh

Daron Denton: One does not simply change the thermostat.

JD: It's getting so thick in here it's like Smaug.

DD: It's bad, for Shire.

MS: It's not that big of a bombadil.

DD: All this banter gives mithril. 

MS: It's not Faramie to be this witty, is it?

DD: Are you baggins for attention?

CB: Should we all take an Otho to stop?

DD: Don't tell me you're getting Sauron all these exchanges?!?!

CB: I'm just afraid if I go to far someone might Mordor me.

Jason Wagner: Haha.. Wait until its time for Tauntaun marker jokes!!

MS: You'll all orthanc me for this later.

CB: Yawn... this is starting to boromir me...

Steve Bennett: The Hobbit: Decimation of Language.

MS: Aryagorn to stop reading now?

CB: ... was looking for a way to use that one!

MS: Shoulda kept looking. As you know, not all those who wander are lost.

SB: I'll only stop reading if you have one pun to bind them all.

CB: I've heard that somewhere... ah well, the road goes ever on...

MS: My eyes are starting to tirith with laughter.

DD: Well, now that Samwiseguy defiled this beautiful masterpiece with StarWars posts, the moment has passed.

MS: His attempt was better than luke warm.

Robert Green: You're still surrounded by nerds HERE!

MS: ~smiles~ I needed the Company, that's why I came here... It's like being in a cozy hole in the ground.

JW: All of these posts are precious...

Michael Drozda: It TOOK me awhile but I'm catching on...

MS: I wish I had a Brandybuck every time it Took me awhile. ;)

MD:

Shannon Stone: Ahh, MY sister! Melanie, every time I think I must be the biggest nerd alive - you remind me that I cannot compete with your nerd knowledge.

MS: Shannon, it's so nice that you envy my vast superiority. Or my vast posteriority, whichever.
These punwars are a gray haven for a nerd like me.

SS: I definitely envy both!

MS: Minas is pretty impressive, isn't it?

SB: YOU SHALL NOT SURPASS MELANIE!!!!

MS: Say u man. 
Not that I'll argue, cause if I did, arwen by a landslide.

Diane Fioretti: I am a nerd but wouldn't get that one either. I get what a hobbit is but have never seen the movies or read the books.

MS: We are no longer friends.

SB: So much for that^^^ fellowship...

MS: Ah, she'll give me a ring and we'll be as cool as Caradhras.

Scott Wilcox: One does not simply make LOTR puns.


My friends and family and I love trivia games, so, if you haven't tried Lord of the Rings Trivial Pursuit, I recommend that. It IS based on the movies, not the books, so that makes it more challenging for all of us. 
I have always wanted their version of Middle-Earth Risk, and The Battle of Pelennor Fields, but I just so couldn't justify another one. Heh. 

One of my AUGI friends was kind enough to send me a Lord of the Rings chess set, and it is one of my favorite sets ever!

2014 Polls and Surveys Roundup

At the end of the year, I reflect on the events I've attended and the work I've done. One of my favorite side projects is my monthly column in HotNews (orange button in the righthand column), which are inspired by the Polls and Surveys run on the AUGI site. Thank you to all of the members who have taken the time to contribute data for the community!



Review of the 2012 polls and surveys
Review of the 2013 polls and surveys
http://www.augi.com/library/poll-2013-surveys-in-review

January
When did you join AUGI?

February
Job searches and talent retention

March
Poll: Are you, or will you be soon, conducting a search for a new job?
(Annual poll, containing historic data.)

April
Poll: Have you ever drafted by hand?

June
Survey: Industry & Product Communities, with a focus on Marine industries

July
Poll: Do you participate in the AUGI Annual Survey? (If not, why?)

August
Survey: The average AUGI member 


September
Poll: Are you attending Autodesk University 2014?

Survey: Annual Survey 
Demographics, salary, job security, job satisfaction, workplace mobility, disciplines, markets served, cloud adoption and connectivity

October
Survey: Salary Survey Supplement
(historical data, pay by job title)

November
Poll: Is your boss older than you?

December
Poll: Do you have a fear of speaking in public?

2014-12-18

OT: Spreading Joy

Anyone who knows me, knows how much I hate shopping 10 months of the year, and how much I absolutely loathe it the other 2 months.

Today, I had to hit Sam's on the way home. Ugh, full gas station ($2.01 though, not bad), and full parking lot.
I dreaded going inside, with distracted shoppers and hungry samplers blocking the aisles. Grrrrr!!!

Then, I looked at my headband.

You see, today was ugly sweater day at the office, and I don't wear sweaters, so, I picked up a headband with a couple wobbly sparkly Christmas trees on it to wear at work today.

I resolutely stuck the headband back on and headed into the madding crowd.

People would be walking around, distracted and concentrating... then they'd see a grown woman with this stupid headgear on and just start smiling or giggling.

I'll admit, I was concentrating on my own shopping a few times and totally forgot I was even wearing the thing... then someone would smile broadly at me or give me a thumbs up, and I'd start grinning again.

Good move, made my shopping a lot more pleasant. 

2014-11-26

CAFM the first year Part 4

Part 4 of 5, my walk down memory lane, surviving my first year as an Archibus Administrator.

Space Management 
Ah, space management. Kind of the backbone of the asset and maintenance management infrastructure. I can't say this is 100% complete, because there are many future plans involving this module.

But, for my purposes of checking off the to-do list, integrating new features into the workflow and migrating away from the thick client, I will proceed anyway.

The major task, faced by me and our business partners, was ensuring that every function available in the desktop client was duplicated in WebCentral. Followed by the introduction of the new Space Console.
After poring through and cross-referencing, we created a new process, which encompassed all of the required tasks, and adjusted some report output files to match more closely with how our office works.

The corporate facilities manager is in charge of planning moves, getting all new employee information into Archibus, and about 50,000 other things. 
Full scale data audits can be time-consuming, though she does them on a somewhat regular basis, to ensure our occupancy plans are up to date. That is one great thing about the space console, instant and visual verification of slices of data.
While I was demonstrating the features for her, we did notice on the occupancy highlights of a floor, that a cube was double-booked. Closer examination revealed that the new employee had been assigned to a cube which was known to be vacant, but, the usual notification of an employee departing had not occurred as it should have. There are half a dozen different data points whose consistency is easily observable on a floor plan as a pattern aberration. I am happy this will make tracking down these rare system hiccups so much more intuitive.

As for my part, I noted soon after I began, only the rooms have been 'polylined' and tracked in the system, but, not the circulation space. In order to realize every vision, we must accurately capture all of the spaces. I am just beginning the process, which actually shouldn't take too long, it's just been tough to find the time to get started.

This is really the most well-documented and talked about feature of an IWMS, so, I won't prattle on.



To be continued... my first year concludes with goal-setting for the coming annual cycle, primarily driven by data auditing and developing a roadmap of my own, after having tried to bring to life the visions of my coworkers.

2014-11-23

CAFM: The first year Part 3

My last two posts have been reminiscing over my first year in my new role. Upgrading our IWMS, creating new roles, and supporting our lease management team. That took me about halfway through.

Maintenance 
The first big task for the maintenance module was adding our branches to the system. Our seven corporate buildings have been utilizing the CMMS (computerized maintenance management system) for years, but our hundreds of branch offices around the country haven't been tracked as formally.

Importing new employee records (assigned to the respective branch buildings) and users (work requestors) into the system is a pretty simple matter. However, we have an additional level of security, being an access portal hosted by our Archibus business partner. We could not create the linked accounts en masse there. However, I used excel to populate the necessary data, which I cut and pasted during account creation. Woof.

I worked with the specialist in charge of taking the branches' trouble tickets, to lay out a basic workflow and sync it up with the new Archibus Operations SLA I created.
Once she was comfortable with the process, I pushed it into our production environment, along with the new Operations Console. I really enjoy the consoles in the newer release, they combine steps which used to reside on half a dozen different tasks.
I put together a tutorial for the potential new branch users, just to make getting them up to speed quick and easy.
And, as an editor, I always recommend having a second set of eyes look over your documentation. My Manager has been working with these users for years and was able to provide feedback on where I might want to provide clarification or remove unnecessary detail.

Now, the next roadblock is actually still on my to-do list. Our corporate operations folks are still using the old forms. They don't see work requests in the console yet, I need to replace the old existing SLA's. There is actually so much custom code on the old views that we can't quite figure out the process, so I need to schedule some interviews with the mechanics and ask them as much as I can about their current workflows.

But, along the lines with this, and a bit of a preview of my Part 5 post... Our managers have reports (KPI, key performance indicators) to produce for leadership on a regular basis. As I smooth out the other bumps, I'll be taking over some of these reporting tasks. The first one I've taken on is presentation slides on how many and what types of work orders are completed at corporate and the man-hours dedicated to each.
These orders are entered in by one team, and I noticed that 30% of the requests were entered as "general" (unclassified).

So, I analyzed all of the detailed descriptions in these random requests, and noticed many of them could have been placed under existing categories, if those categories had been named a bit more clearly. I also detected a few common themes and easy groupings for new classifications.
Archibus work requests have a basic work type, but, can also be given subtypes. These are more important when you've got a larger staff and specific workers assigned to them, but, if you want to track time and costs easily and accurately, even those with small staffs can utilize the subtypes.

From a software UI (user interface) perspective, I need to shorten the list of options and ensure the language is understandable to the end user. 
For example, we have a category called Mechanical, which someone with my engineering background knows refers to HVAC issues. However, that is not common knowledge to the dozen or so people outside of Facilities who enter these in for our building occupants. If I rename that category Heating/Cooling, they'll understand the category without throwing off our maintenance technicians. Reducing the 'probtype' choices in our request form from 32 to 15 will make it a quicker proposition.

Now, the sub tasks are something I could suggest based upon analysis of the user data, but, they could be influenced by how work is performed, or billed, or otherwise categorized.

I got clearance from the AVP over maintenance, but, I'm circling back around with all of the maintenance technicians to ensure that we capture as many ideas as possible on the first pass, so we're not making repeated changes, which could be a pain point for our end users.

Now, one super obvious thing I haven't covered here yet is Preventative Maintenance, and PM checklists, and inventory, etc. That will be a future topic, you know, once I tackle it. It's in baby stages right now.

To be continued... up next is space management, followed by data auditing and developing a roadmap of my own, after trying to bring to life the visions I'd been handed.

CAFM: The first year Part 2

Yesterday, I talked about easing into my new role supporting Facilities with Archibus. Getting started and surviving my first system upgrade.

Lease Module
The first task on my plate was pushing out some new features in the Lease module. I began with reviewing their current processes and some ideas they had for improvement. 

Bearing in mind that I know *nothing* about managing or reconciling or renewing leases. My FM experience has been in maintenance and engineering and only began to touch upon the space and occupancy management aspects a few times, when I became involved peripherally with the departments who handled our Medicare reimbursements.

Going from what I heard the Lease Manager and her staff discuss day to day, I examined the Processes available in WebCentral (a big reason for this upgrade was to get more users onto WebCentral and away from the desktop client, which we access via Citrix) with an eye toward removing unused entries and adding in new ones.

My consultant pointed out to me a new view that would eventually replace a totally custom view which my company had had built years ago. Rather than accessing data for leases in five or six different views, they were cobbled together and accessed through a single page. But, it was old technology and custom and didn't report in the LOG the way the standard forms did, when errors occurred. So, it had to go. With something closer to out-of-the-box, it would be more predictable, and would prove easier to upgrade the next time around. The new view would also provide direct access to the background data (buildings, cities, sites etc), which had only been accessible previously through yet more views, which many hadn't had been granted access to.

I relied heavily upon the Lease Manager at this point, explaining to me which data was most important to her team. The challenge to me, of course, was discovering which table each type of data resided in and how to display it. 
The challenge being, not the display of data, but, the creation of new records. For example, I could get a building's address table to display the necessary fields with existing lease records, but, if I were to create a new lease record, it would fail because the address field was technically blank until said record was saved. The challenges of accessing a transactional system (SQL) with a dynamic interface (html).

There are "panels" within this new view, which each basically point to a different database, and are all coordinated by the lease code, the only data point common to each database table.
She may not have been able to articulate how the data interacted behind the scenes, but, that's not remotely expected nor important. Far more valuable to me were her explanations of why they needed each piece and how it was used. I learned an unbelievable amount about the process from the handful of informal meetings we had, hashing this out.

The system, as it was being used, was so customized in the older version, in order to provide features which did not technically exist within Archibus at the time, that it was a little difficult to rework existing data to fit into the newer structure (which does possess most of the desired capabilities).
I had to rely heavily upon our business partner at that time, to make changes and track down bugs.

This is really when I would've benefitted from that System Integrator class I mentioned previously. The interplay between the numerous SQL data tables, the Archibus AXVW's, and the supporting JavaScript files is rather complex, and I've no shame in admitting I was sorely unprepared for the challenge. I assisted our consultant whenever I could, but, did a lot of observing, too.

Now, as a nice, cold-bath-style introduction to being a dedicated SysAdmin, we had a sporadic bug with one of the panels. It kept breaking the view. For months we tried to track it down; most days it worked, some days it didn't. Each of us involved tried various modifications to the view, from top to bottom, but, the error would eventually crop up again.

One of my strengths, and what eventually led me abandon my desire to complete a degree in mechanical engineering and switch to computer science, is troubleshooting. I fiddle with stuff until I discover what is broken, and I find a solution to resolve it or a way to work around it. It's kinda what I do, no matter what software or hardware I'm supporting at the time.

It was unbelievably frustrating for everyone involved. None of the other customers using this same view had experienced anything like this.
Keeping the data logger on all the time, to try to record evidence of the problem, slowed the whole system down for users of any module.

We tried various browsers, my boss and I had IT ensure we all had the same version of js installed. 
One suggestion that we never did try was to upgrade Tomcat, but, before doing that, we had the consultant's programmer recreate the offending panel from scratch, which finally worked.

It was then a challenge to get our very busy users back into the new form, when they'd gotten used to going back to the old one with which they were familiar, even with the other bugs it displayed (such as unexpectedly logging users out of the system).

I have been writing about CAFM/CMMS/IWMS systems for over a decade now, and one thing has always been clear... there is no out-of-the-box system in production. 
We all start out with the same pieces, but, we tailor it constantly to fit our needs. This can mean a very challenging support environment and I can't speak highly enough of those who are capable of working so capably with it.

It's important to build a good rapport and mutual respect between users and supporters of systems. So, when those with the extensive knowledge of the data within the system notice aberrations, they are reporting them immediately and clearly, and the supporters can gauge how serious those issues are, and become familiar enough with the workflow, so that a minor bug doesn't become a work stoppage issue.

It was a wild ride for all involved, I'll admit. But, every person in our process was keen to work hard to put it behind us. You need multiple SME's here, use them all.
And let's ignore the costs for now, because neither customization nor support are free, nor should they be. As the technical rep for the client, it's up to me to balance requests and needs and implementations.

My time spent managing technology projects also long ago proved to me the importance of pre-planning projects, knowing what is and isn't covered in your estimate and contract is vital to budgeting.

To be continued... maintenance is up next, then space management, followed by data auditing and developing a roadmap of my own, after trying to bring to life the visions I'd been handed.

CAFM: The first year Part 1

I recently (October) celebrated my first anniversary with my new company. While I do miss the unique puzzles faced in facilities engineering, there are plenty of riddles to occupy me in my current role.

I can't say I wasn't petrified to start over somewhere new, after over 13 years on my previous team, but, it is kind of exciting to begin again, this time with the benefit of experience, education and a modicum of confidence.

Slow Start
It has been a busy year, with the promise of much more in the pipeline.
But, the start was a bit slow for me, I'll admit. The SysAdmin training I was hoping to get in November was canceled and moved to February, and I couldn't do much until our upgrade from Archibus 18.1 to 21.1 was complete. Obviously, I've had similar training and experience with FMDesktop and IBM Maximo, but, each system is organized much differently on the back end and you don't want to start blindly tinkering.

Until the new system was installed and ready for me to start testing, I was assisting our corporate facilities manager with moves, renovations and new employee management. She didn't have too much downtime, but, when it was a little slower, she showed me some of our power-consumption data and talked about wanting to find the time to analyze it and propose energy-savings projects.
That allowed me to get used to our data, some employees and their departments and divisions.
I even got to save them a little time and money by laying out alternate plan ideas before formally requesting our architect to draw them up.

During this time, I also took any notes compiled by our consultant from interviews with our facilities department heads, expressing their pain points and goals for our IWMS. I formalized and organized the workflow portion into clear processes and procedures, filling in some holes as I walked through it. As I took on some tasks for accessing and managing the system, I documented that as well.
I believe my years as a technical editor really prepared me for capturing steps and providing clarity during projects like this.

Part of the benefit of very clear documentation is that I learn it more deeply, another benefit is that my company knows that if I ever leave, they won't have to start from scratch or recreate the wheel. My last few months at the hospital, I was constantly thinking of little details to write down for my eventual replacement, how things were set up and why. It had never occurred to me to explain those things to anyone, but, it would be helpful to someone coming in blind. Prior to my presence, the engineering team had had trouble keeping anyone on for long, and no wonder, the scope of work and the scale of the campus is enough to intimidate anyone. 
An unexpected bonus of this busy work? We were recently asked to compile a processes and procedures manual for our whole department. Easy peasy for me. Woohoo.

The Migration
The first stage of the upgrade for me was user experience testing. I logged into our Dev environment as each user role, to ensure the views showed and operated as expected. The next step was to recreate the user Roles. Many folks had random tasks assigned to them over time, which made duplicating permissions unnecessarily complex, and also enabled the possibility of pulling multiple licenses at a time by a single user (if the same process is assigned to a role and to an individual).

This is where the fun started. Processes weren't properly cascading from the roles to the users. I couldn't figure out why, and assumed it was nothing more than my inexperience to blame. Bumped it to my consultants and none of them could see a reason either. They bumped it to Archibus support and they couldn't figure out why either.

So, we upgraded from 21.1 to 21.2 and began testing again.

I was able to take the Archibus System Administrator training then. Though the winter trip to Boston did leave me with a cold and eventually bronchitis, it was worth it. The Archibus employees and instructors were all fantastic. I learned about setting up the system from scratch and the necessary tweaks there, then essentials of creating new tasks, processes, roles and reports. When I started asking questions, I even got a little preview of the topics covered in their System Integration course (which I still desperately want to take).

There were some bad hiccups when we flipped the switch, with some user accounts unable to log into WebCentral. That was a really great introduction to my new users, who hadn't gotten a chance to meet me yet. Most of the user accounts were back in business after clearing their cache (challenge number one, providing the correct instructions for cache-clearing when your part-time system users don't realize what a browser is, nor which one they're using. I settled for instructions marked with the browser logos.), but, some of the others... again, the problem couldn't be easily detected through the expected settings and permissions. Our business partner was able to rectify the remaining account problems for me.


Once the users had settled in and gotten used to the look of the newer version, they appreciated the autofill and search options when filling in forms.

To be continued... This post is getting a bit lengthy, so I will break it up over a few articles. Each of our user groups needed to have their modules and processes assessed. Lease, maintenance and space, primarily.

2014-11-07

Archibus Task Highlighting Error

A few weeks ago, I posted a tip about using HTML in Archibus WebCentral order to highlight tasks in the Process Navigator.

http://mistressofthedorkness.blogspot.com/2014/05/archibus-task-highlighting-in-process.html

I have been meaning to post a little caveat to that tip. I often encourage my users to add their most frequent views to the Favorites list. HOWEVER, I discovered that tasks which have additional code tags around them, cannot be added to the favorites list.

Please beware of this limitation when adding html to your tasks.