Bsa 375 - Riordan Manufacturing Case Study

Riordan

Stanley Pietrzak

BSA / 375

February 1, 2015

Michael James

Riordan

Riordan Manufacturing is a global plastics manufacturer employing 550 people with projected annual earnings of $46 million dollars.  The company is wholly owned by Riordan Industries, a Fortune 1000 enterprise with revenues in excess of 1 billion.  Riordan Manufacturing consists of plants in Albany, Georgia, Pontiac Michigan, facilities in Hangzhou, China with corporate headquarters in San Jose California.  The chief customers of Riordan Manufacturing are automotive parts manufacturers, aircraft manufacturers, the Department of Defense, beverage makers and bottlers, and appliance manufacturers. (Apollo Group)

        Riordan Manufacturing desires to implement a state-of-the-art informational system that integrates the existing variety of Human Resources tools into a single integrated application and is the scope of this project.  The expected result of Service Request SR-RM-022 has several objectives.  The first objective is to define the business requirements for the development of an HR system that supports the objectives of this service request.  The second objective is to create a detailed system design and project implementation plan to complete this project.  The third objective is to have this project completed within six months to meet the expectations of implementing this new system in the second quarter of the next year.

Methodology

        To meet these objectives a complete and thorough investigation will be conducted to fully evaluate the current processes being implemented at Riordan Manufacturing.  Key stakeholders will be identified, interviews conducted with key members of the staff at the various levels of those involved in the Human Resources workflow, observations of current methodologies and workflow environment as well as documentation review of the current system and procedures.  The success of this project will depend heavily on key stakeholders of the company and must play an active role in the various steps of this process.  These stakeholders for this project are to include the following individuals. (Apollo Group)

• Dr. Michael Riordan – President and CEO - As with any project having the complete buy-in and support of the upper most reaches of management helps to ensure that project implementation will be of utmost importance.  
• Hugh McCauley – COO – As Chief Financial Officer of the company his role is to ensure that programs are administered and completed to meet company’s goals and objectives and is the creator of the originating Service Request.
• Yvonne McMillan – Director of Human Resources – As Director of Human Resources it is imperative that Yvonne takes a very active role in providing feed back at all stages of this project as it directly impacts her department.
• Dale Edgel – CFO – As Chief Financial Officer Dale has direct over-site of the Human Resources Department and will provide additional insight into any and all financial concerns and reporting that must be considered in this project.
• Maria Trinh – CIO – As Chief Information Officer Maria plays an integral role in ensuring that technologies implemented with this project are compatible with current systems and make recommendations on any new or enhancements that may result during this project.
• Lowell Bradford – CLC – As Chief Legal Counsel, Lowell will be able to advice on any and all legal issues that may arise as a result of this project.

The need to amend this list of key stakeholders may arise and could include key personal identified during the initial phases of this project.  

        The development of a plan will begin with the gathering of deliverables for requirement determination known as information gathering.  This phase will include but not be limited to employee interviews, workflow observations, review of existing documents and files and results from any joint application design (JAD) sessions, computer aided software engineering (CASE) repository contents, reports of existing system displays and reports from any system prototypes. (Joseph S Valacich, 2012)  Through this information gathering the likeliness of redundancies and discrepancies within the process should be eliminated and allow for a clearer understanding of current strengths and weaknesses to be addressed in the new system.