Getting a new system? Be prepared! There are quite a few factors involved in a successful implementation.
Project Management: Knowledge of the project itself is critical. Do you know the steps, timeline, risks and costs? How about the skillset and size of the project team? Who are the stakeholders? The decision makers? We know!
Functional Knowledge: Tax laws, labor laws, healthcare reform... It's tough to keep up! Add in the countless vendors, systems and versions... It's nearly impossible! Unless, of course, it is your job to know all of these things. This is our job!
Technical Knowledge: Let's face it, unless your title contains the letters "IT," the technical part of any project can be overwhelming. Having an understanding of system requirements, interfaces, systems of record and databases is essential. We understand all of this!
Testing: Is extensive testing really necessary? YES!!! Unity testing, acceptance testing, system testing integration testing, regression testing - all phases of testing are absolutely necessary. It may seem tedious, but testing now means you won't have to fix it later. The most important part of testing? The test scripts! They must encompass all features and functions being implemented. Do you have the expertise to manage this? We are testing experts!
Training: While vendors offer generic training classes on their systems, they rarely understand the uniqueness of each client. Wouldn't it be nice if someone could tailor the training to your needs? We can teach you!
Doesn't it seem like just as you are feeling comfortable with your system, it is time for an upgrade? No matter how small the changes may be, an upgrade is not to be taken lightly. Something is changing! A few things to consider at the very least are:
Guess who has managed dozens of upgrades of all sizes, from under 50 to over 100,000 employees... We have!
The best way to describe this type of project is trying to fit a square peg into a round hole. Nothing is simple. First you must decide which system to keep. Will history be converted? How long will the former system be accessible? Then you need to standardize codes across all companies. Are there any conflicts? Be careful if you are converting history! Then you have to determine which policies are changing. Don't grandfather too many! Next, the employees must be considered. Which employees will be converted? Have they ever worked for the company whose system was selected? In other words, do they already exist in the database? How will transfers be handled? Other items to address are reports, interfaces, benefits, benefit accruals, calculations, qualifiers and general ledger to name a few. This may be the most challenging project, and it is easy to overlook some tasks. Unless, of course, you've done this many times before, like we have.
Are you in the market for a new system but don't know where to begin? A good place to start is understanding all of your requirements, no matter how small. Can these requirements be satisfied? Make sure you ask all of the right questions. The one you leave out will come back to haunt you. Trust me!
Once you know what to ask, do you know who to ask? There are many vendors out there that would love your business. Why spend weeks researching solutions when we have already done it for you? Use our years of experience to find the right fit for you!
A successful interface is the result of the perfect mix of technical and functional knowledge. The vendor requesting the interface will provide detailed specifications - which fields to include, acceptable field and file formats, transmission methods, scheduling, etc. However, the developer must also understand how data are related and how changes in the system may affect the outcome - the functional stuff. Have you ever thought an interface was correct only to find months later that it isn't working as expected? That's usually the result of data being mapped incorrectly! Also, if you are working with multiple systems, you probably have multiple interfaces. They may not be directly related, but I can guarantee that they impact one another. Do you have a resource that understands both the technical and functional aspects of your system? We do!
Reports, like interfaces, require both technical and functional knowledge. The reporting tools that come delivered with your HCM solution simplify the process to an extent, removing some of the technical requirements. However, the end user must still have a good understanding of the database and from where data must be pulled. Is this a point-in-time report, or must history be included? Will it ever have to be run for dates in the past? In addition, the report writer must also ask the right questions to uncover the true purpose of the report. Who needs it and why? Don't you wish someone could just write this report for you? We can make your wish come true!
Have you ever sat through a training class and thought, "None of this applies to me!" Classes are designed to teach the basics of the system to all clients; they are not tailored to your needs. As a result, you may learn things you will never use and may not learn much of what you do. Wouldn't it be nice if someone could understand how you use the system and design a class just for you? We're nice like that, and we've done this many times!