sarah_manning
ServiceNow Employee

etta wilson.jpg

By Etta Wilson

ServiceNow Architect and Administrator

CareFusion


We're extremely fortunate to have a guest blogger today. Etta Wilson, ServiceNow Architect and Administrator at CareFusion, shares her story of transformation with PPM.

Etta has been with CareFusion since 2011 and it was her own personal experiences that brought her to the company.

You can find Etta on LinkedIn.


. . .


Inspired by our recent one year anniversary launching ServiceNow PPM — which has completely transformed our approach to project portfolio management here at CareFusion — I'd like to share our experiences and encourage additional discussion among like-minded enthusiasts.

First, a little about CareFusion and my own personal journey here.  

At CareFusion, we are united in our vision to improve the safety and lower the cost of healthcare for generations to come. Our 16,650 worldwide employees are passionate about healthcare and helping those that deliver it - from the hospital pharmacy to the nursing floor, the operating room to the patient bedside. Even prior to when I joined the company, I was a user of the equipment while I was taking care of my mother — she had Lou Gehrig's disease. I saw firsthand that the products we develop improved my mom's quality of life, especially given her devastating illness, so what we do is very close to my heart.

I'm part of the Service Management team, which includes the PMO, Change Control, Internal IT Communications/Collaboration and ServiceNow Design and Administration.   We sit within the IT organization.   Our PMO deals with not just IT projects — we are responsible for many business-level and global projects as well.


What a Difference a Year Makes

Before ServiceNow, we were using Planview. Actually one of the reasons I joined CareFusion was because of my knowledge and experience with this product.   While we had grown the deployment with elements such as capacity, demand, project, financial and resource management, we couldn't really advance our project portfolio management approach since our service desk was in another tool.   We had no way to fully review capacity or demand of available resources.  

ServiceNow was already being used by our Service Desk, so when we received a directive that we were moving from Planview to ServiceNow, I was surprised but welcomed the opportunity to finally have a single system of management and record for IT.  

I utilized the Wiki and PPM best practice sessions with ServiceNow to understand available functionality to perform the gap analysis.   An evaluation specifically for PPM was definitely an eye-opener and after a three-day workshop to get immersed, we made the transition — hitting our go-live target in just eleven weeks.  

The Power Begins to Shine

As we went live and began using ServiceNow PPM, it became clear that the capabilities within ServiceNow were going to fuel the effectiveness of not only the PMO but the entire enterprise. But it did take about three months for me to really think, "Wow, this is going to be beautiful!" You've got to approach a major transformation with your eyes open. Now, I see the ability to truly have an end to end solution that's seamless and automated — a first for us.

I think it's very important to focus on effective training and consistent adoption. In the early days, we needed to reinforce that everything was done in ServiceNow because it is so closely tied together.

A year later, these fundamental capabilities have transformed the life of a project manager. Instead of managing all the administrative tasks, our team can now focus on managing projects. Productivity has drastically improved.

Effectively Managing Time and Resources

One of the most compelling benefits — which I think is a must-have — is integrating the time and staffing financials into the PPM application. I'm sure there are some readers who view the management of timecards as unnecessary when a formula may get you close, but this integration within ServiceNow allows us to automate, and easily conduct a financial month end close.  

I did have to make a change to how we process month end.   Because our Resource Managers approve timecards, the Project Managers had no timecard visibility.   Approvals or adjustments that could impact their project cost could not be reviewed or monitored.  

As a result, I moved the entire timecard processing into a scheduled job. Approval flow and adjustments can be made throughout the month cycle. Exchange rates can also be imported. At the end of the month, the scripts run and create the expense lines and expense allocations against the project, portfolio budgets and cost centers automatically.

Putting the Pieces Together

Over the past year, I've enjoyed providing input directly to ServiceNow Product Managers as new capabilities are evaluated and with other users at the ServiceNow demo days, SNUG and at Knowledge. Being able to share ideas and lessons learned with developers and architects has raised my excitement for the power of the platform. I can envision the benefits of ServiceNow automating work across IT and even further into the business beyond what we are doing today.

For me, I now see this transformation as similar to a move away from a Microsoft — it is easy to get comfortable using the features provided out of the box. But it is much more rewarding to put together your own model with the pieces that work the best in your enterprise.  

When I think of Project Portfolio Management, it's more than just an application.   It's a way to conduct the business of IT.  

There are several applications and modules in the ServiceNow platform that makeup an end to end solution for PPM effort and initiatives.   Over the next few blog items, I will be detailing "PPM with Etta" illustrating our end to end solution.  

Let's start with "Submitting an Idea" for a project in the Service Catalog and creating demand using the recently released "Eureka" Demand Management application.  

Come join the party and hopefully the information shared will help you develop your own effective and comprehensive PPM platform —it will be fun!


Comments
Kilo Sage

Hi Etta,



It's nice to see a positive success story in regards to the PPM. The only OOB module I have not been able to get my company on board with is PPM. The argument is that it's not as advanced as MS Project and can't do the "complicated" finance reporting that they currently use Planview for.



I did show case them back on the Berlin release and I know there have been updates in the latest releases so I am quite looking forward to the rest of your posts which, I hope you don't mind, I will be taking ideas from to revisit replacing Planview.



Pete


Mega Sage

Pete,   I have to admit I had to regroup my thinking about what I really needed a PPM application to do because it's not MS Project or Planview.   I used Planview for 8 years and it has amazing financial capabilities but do I really need all that awesomeness if I have SAP.   What I do need is a way to manage schedule, cost and scope. I can manage all of these with PPM and a few supporting applications.   Hopefully by the time I've completed the blog series, you will have enough information to convince your management to join the party.


Giga Contributor

Etta,



I know it has been a while since you wrote this entry, but I still thought it was a very good read, provided a good deal of insight and I appreciate that, and look forward to the next entry.



I am in a similar situation with our Company right now, we've been with Service Now since 2011, and we are using all of the usual applications, and we just recently stood up Configuration & Asset. Our PPM group is slowly coming around and I almost have them convinced to make the move, but as I'm sure you are aware... Change is scary, and when people are comfortable using existing tools, change is even more scary.



I'm really interested to see what Service Now is going to do to bridge the gap between SDLC, Change & Project. To me those three application are all intertwined, and as I continue to change the culture to view Service Now as the sole source of authority for the work we do in our Company, it's important to me to be able to show how all of these different application do intertwine and can be used to efficiently perform the work we all do.



Some of our challenges that we are facing is how to get all of the groups, PPM, IT, and business office to initially work out the roles and responsibilities within the Project applications themselves, there are some shops that the PPMs don't want anyone else in there other than to view the project information, the IT managers wants to be ale to split tasks apart, add new tasks, assign their resources effectively,   the business office wants to be able to look at projects from a finance perspective and see what the total cost of development is. All are valid perspectives, but often it takes a great deal of conversation between all groups and finding the right unbiased parties to facilitate those conversations.
Don't get me wrong, we still haven't gotten this worked out ourselves, but I can see the potential and the benefit the Company will get out of moving the PPM group into Service Now, it's a change, and change takes time.


Mega Sage

Doug,



I believe that once you can show them the value of having all work in a single system of record and how easy it is to use, they will welcome the change.   Your comment regarding bridging the gap between SDLC, Change & Project is spot on. They are definitely intertwined. In Fuji, ServiceNow is starting the path to connect them.   As a project manager, I understand the concerns of the PMs not wanting IT managers in their plans because the plan becomes a long task list and not a place to manage schedule, cost, and scope.   Unfortunately, without having some place to keep the task details so that it ties back to the project, neither the PM or IT manager really has a handle on what's going on.  



What's exciting about Fuji, is it allows the IT manager the ability to define the detail tasks using whatever development methodology (waterfall or agile) and then ties it back into the project.     I kept time card entry at the project task so that people entering time didn't have 100 development tasks on their time cards. The development task schedule rolls into the project task schedule.  



The nice thing about this approach is that it gives the PM direct access to the development tasks so that they can start to proactively manage the project.   It also provides the IT manager a place to define development tasks.   We communicate project actuals and schedule back to the business using the Demand application.   After time cards are processed and the actual cost updated, it feeds that information to the Demand application so that the business can view planned vs. actual cost and schedule.  


Giga Contributor

Etta,



One of the other things that seems to be a concern for our PPM team is the fact that I as an admin default to the advanced view of the project that contains all the additional fields, such as:


Budget Cost, Estimated costs, Net Value, ROI


Sections such as Goals, Risks, Issues




I can't figure out why Service now does not make the advanced view the default view for those with the project_manager role. I have asked our SN representative what the reasoning for this was if there were concerns that those items should not be visible to the PMs. I've never really gotten a good answer for this.



I have given all of our PPMs the following Roles:


project_portfolio_user


project_manager



Is there something I am missing?


Mega Sage

Doug,



We had to do the same thing. Since the project manager is responsible for schedule, cost, and scope, all the fields on the advance view belong to them. Are you a member of the ServiceNow User Group - SIG PPM?   https://community.servicenow.com/groups/ppm


Kilo Sage

You can enforce views on users. Check the global BR "incident functions"


Giga Contributor

Etta,



I am a member of that group, thanks though for the direct!