Recently, I come across one situation. During consultancy regarding automation for HR department.
Approach 1: Modular approach where modules like Leave Management System, Feedback System etc would be developed on SharePoint Online with Integration with other applications for Salary Processing etc.
Approach 2: Go for the full HRMS software like SAP, BAAN, Oracle etc. but let me tell you the requirements are very few may be 5% of the SuccessFactor would be used.
Please give suggestions Saving Changes...
Sort By:
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
I'd recommend starting with identifying constraints such as must have requirements, appetite to spend, and enterprise technology standards. That should help to reduce the set of options available. As far as develop in house vs. buy a single COTS vs. buy individual best-of-breed solutions and integrate, there are pros & cons for each so there's no single "right" answer.
The modular approach can be cost effective and tailored to your needs, but managing the interfaces can be very difficult, for one reason among many in that you don't control any of the software, and the vendors are prone to change. Maintaining the software and interface management can be a significant expense over time and a constant opportunity for errors.
Fully integrated software solutions can avoid this, but can be significantly more expensive when you only use a small portion of the functionality, and you can be held hostage by a single vendor. Saving Changes...
Deepesh RammoorthyICT Project Manager ( PMP®AgilePM®Certified ScrumMaster® (CSM®))| Australian Red Cross Blood ServiceTarneit, Vic, Australia
I have seen two types of approaches when looking for a solution to business problems. And Both for Commercial Off The Shelf Products.
Gathering an exhaustive set of requirements and then going out to the market to find solutions that meet those requirements OR
Starting with a set of Basic Mandatory requirements that the solution MUST have , then getting a solution from the Market , Which would be the Minimum Viable Product.
In both cases, you can evaluate the products based on Technical Features and Total Cost of Ownership and make an informed decision.
Like our colleagues have stated earlier , There are pros and cons of purchasing integrated and discrete systems.
Perhaps looking at buying an integrated product to fulfill an initial set of Business processes but looking at the company's long future road-map to evaluate if they may require to enable other features in the product would not be a bad idea. Saving Changes...
