By Terri Hiskey on Jan 15, 2014
Special guest blog by Domain Systems
We are all trying to get the best performance out of everything--out of our people, machinery, vendors...any investment, really. But some of us make the fatal mistake of exhausting our resources until they can no longer produce anything of value. We've all done "burners"--working through the night with no sleep in order to get a project done. At a time when most people are waking up, we are hoping for a third or fourth wind to get us through the next few hours. When we are young, we can do this many times a year with no real side effects. As we get older, these burners start to take a larger toll on our bodies, health and mental capabilities. The body needs sleep, as well as other important items such as food, water, emotional and mental stability. We can put these things off for a while and survive, but if we put them off too long, really bad things can happen.
Your Agile PLM software is no different. Your software and hardware are just like our bodies. They require certain (and quite simple) things for healthy operation, and if those are ignored for long periods of time, your Agile PLM system will shut down. What is really painful to see is that a lot of companies purposely put aside regular maintenance activities in the name of productivity, until it is too late. The cost can sometimes result in millions of dollars of downtime, scrap and high-priced emergency fixes. In order to maintain your Agile PLM implementation, here are four vital activities that will give your Agile PLM implementation a healthy life:
1. Back up every day. This really should go without saying. If you like your data, and your data is important to your business--make a copy and keep that copy secure.
2. Schedule routine maintenance windows. At a minimum, these should be monthly. If you run a lot of transactions, you might want to schedule these twice a month. We know that down time can sometimes mean lost money, and in this day and age of 24/7 availability, it can be difficult to find a convenient time for this. However, this is one of those things that you just need to schedule. If you don't, your system will decide on its own to take down time when it can no longer survive without it, and most likely at the most inconvenient time for you, when it will cost you the most money to get it back up and running. A company who refuses to schedule routine maintenance windows is like having a policy against putting gas in your car until you are on empty. It is just not smart.
3. Run Averify. Averify is a tool that checks for conflicts in data integrity caused by upgrades, user errors and software defects. Typically, this takes less than an hour. Of course, each company and set up is different, so yours could be longer. But less than an hour is what most companies should expect.
4. Check your table spaces for room. When you run out of room is typically when potentially irreversible bad things can happen, like overwritten or corrupted data. When this happens, Agile PLM will crash.
If you follow these four steps, Agile PLM will run better, smoother, with less errors and you are less likely to have a crash that you can't recover from. Don't treat your Agile PLM system like you treated your 19-year old self--treat it like your grandma. Give it the care and attention it deserves, and if you do, you'll get all the PLM cookies you want and more!
Domain Systems is a Certified Oracle Gold Partner, and the only partner to work solely with Agile PLM. Domain Systems provides all services related to Agile PLM including installations, upgrades, data migration, business process consulting and the development of process extensions and adapters. Check out Domain Systems at www.domainsi.com.