I was able to use the software VPN today to connect to the new ERP System. After several attempts of logging in, and eventually locking myself out, I finally contacted the Lead Consultant. He reset my account, and let me know that I was not authorized to log into the 'Test Database'. He had only set me up to connect to the 'Production Database'. He reset my login account, and I was able to finally connect to the new system and poke around for a bit. Have you ever noticed how much more intuitive a software package looks when someone else is using it?
Our hardware device came in today to set up the VPN between our building and HQ. HQ's tech guy was onsite at our place today to install and configure it. After 4 hours of attempting to set it up, he let me know he had to leave for a meeting. He emailed me at the end of the day to let me know he believed he had everything configured, but needed a change to our firewall to allow connection. I will make the requested changes in the morning and see if it allows traffic to flow through.
I spoke to the lead consultant just before receiving the email from the HQ Tech Guy. He wanted to walk back through the BOM import program I thought was completed over the weekend. It appeared he was doing some final testing on his side, and wanted to make sure his assumptions were correct. There were some required changes do to the structure of our engineering design release process. He assured me he would have this critical piece completed by the time he comes back in ---Friday (today is Tuesday).
I received an email from our Project Manager with another update to the training schedule today. Department training was moved around to allow me to have a few hours of administrative training Friday morning. We will begin setting up users and roles (permissions) on Friday.
I received a bit of a comic relief at the end of the day. As I was leaving the office, I was giving an update to the plant manager. I let her know that I talked to one of the key guys at our remote facility #1 and he didn't know we were implementing the new software - or they were expected to go live with the new system on May 1. I suggested to the plant manager that the 'key guy' be invited to connect to our training sessions via the web next week to get some exposure to the software (he can't be here in person due to personal obligations). She let me know that the plant manager and engineering manager of remote #1 were invited to be onsite the week of 3/9 (go live week) to see the software in action. I rolled my eyes a bit and asked if she really thought that was a good idea (well planned go live days are hectic enough). She almost jumped out of her chair saying how excited she was to have them here to see the new software going live on 3/9.
Note---My apologies to all for the delay in posting the last week. I am trying to balance having some sort of life, with the extra work imposed on me and find time to be as objective as possible in this blog.
I do want to reiterate my position during this implementation. I am there to support the implementation in any way I can, without affecting the outcome of the implementation. I am not the project manager, I am not responsible for the success or failure of going live on 3/9. I will be Johnny on the Spot if someone needs something from me: data exports, admin, hardware, documentation, troubleshooting...I am trying to be objective and not interfere with planning, timelines or methodology. I am trying to learn as much as I can about the software, different approaches to implementation and process improvement and generally support the plan as best as possible. I am honestly concerned at the short and long term implications of a poor project plan and implementation timeline. That in no way affects what I do or how quickly I do it. I will do everything within my power to support making the go live date. My biases are based on my experience. I don't think I am being pessimistic, I believe I am realistic in my approach. Feel free to reread my post on 2/13 to better understand my real concerns for the longevity of the company.
No comments:
Post a Comment