The document discusses system design and acquisition for an HRIS, including separating the data view from the process view as the data will remain the same but processes may change. It also discusses moving the logical model and requirements to the physical design phase, including hardware, software, and networking considerations. The purpose of a request for proposal is to work with internal IT staff and software vendors to develop an RFP that includes functionality, architecture, integration, price, and vendor viability to evaluate potential HRIS solutions.
The document discusses system design and acquisition for an HRIS, including separating the data view from the process view as the data will remain the same but processes may change. It also discusses moving the logical model and requirements to the physical design phase, including hardware, software, and networking considerations. The purpose of a request for proposal is to work with internal IT staff and software vendors to develop an RFP that includes functionality, architecture, integration, price, and vendor viability to evaluate potential HRIS solutions.
The document discusses system design and acquisition for an HRIS, including separating the data view from the process view as the data will remain the same but processes may change. It also discusses moving the logical model and requirements to the physical design phase, including hardware, software, and networking considerations. The purpose of a request for proposal is to work with internal IT staff and software vendors to develop an RFP that includes functionality, architecture, integration, price, and vendor viability to evaluate potential HRIS solutions.
What is data view? What data the organisation captures and uses and on the definitions and relationships of data What is process view?
Business processes and
activities in which the organisation engages and how data flows through the HRIS Why do they have to be separate?
Data will probably remain the same
Process might be changed in the future
Data flow diagram (DFD) Data flow diagram (DFD) Level 0 of DFD Level 0 of DFD Level 1 of DFD Level 2 of DFD Futher…. Futher…. Moving the logical model Physical and requirements to design phase physical design including hardware, software, and networking Physical design phase The purpose of a 1. Requirement HR and manager new hire/rehire Code Comments
request for a proposal? checklist ability, by position, with check-
off ability as tasks are completed (for example, offer letter has been sent and received). • Work with internal IT staff and software 2. Provides ability to automatically notify other areas of organization of new hire vendors (security, payroll, etc.) • Develop a request for proposal 3. Provides ability to automatically notify new hire of activities they need to • RFP includes: complete and remind them if they don’t do them in a timely manner. 4. Manager is prompted to assign correct property to the employee. 5. Ability to enter new hire before start date (effective dating) and new person will not appear on org charts until effective start date. Criteria Functionality used to IT architecture and IT integration evaluate Price vendor Vendor longegvity and viability proposals Evaluating potential solution Explaining how to reply to an RFP document 1. Introduce your company and its mission. 2. Describe your proposed terms and timeline in detail. 3. Include pricing information. 4. Summarize the benefits of partnering with you from the customer's perspective 5. Include your authorized signature and contact information.