Department Name: Human Resources List

¶ … Department Name: Human Resources List Hardware/Software and RTOs and RPOs indicated. If you changed the RTO of the department to a different one in Assignment #1, please use the RTOs for the hardware and software as listed. DO NOT CHANGE THESE.

In response to the organizational assessment for planning of the technology recovery strategy(s) of the CLIENT, a leading edge service provider for E-Commerce Solutions, the foregoing is a list of the RTO and RPOs indicated in the evaluation of the Human Resource department; which keeps the database of employees current in PeopleSoft's HR system. A critical point in the CLIENT's disaster response network, the sustained operations of the company are reliant upon the HR system for notification and supervision if a disruption occurs.

The system contains a complete list of all employees who must be contacted to implement recovery efforts. Attendant functions to the HR system correlate to: Function 1) Payroll; Function 2) Recruitment of New Employees; and Function 4) Organizational Development & Employee Relations. The it system is comprised of the following components: PeopleSoft (20 Sun Fire V880 Midrange Systems); Office (PC and LAN based). RTO of Work Area/Software: 3 days RPO: 1 day Recovery Time Objectives (RTOs) Are: 4 hrs, 8 hrs, 1 Day, 2 Days, 3 Days, 1 Week, 2 Weeks, or 1 Month 4. Choose the technology strategy(ies).

You may choose one strategy or more than one strategy. Recovery Strategy is focused solely on the CLIENT's Headquarters in Lincoln, Nebraska, where Human Resource administration is located. The strategy will ensure that critical company functions in this Department are restored, and that supporting systems are secured within acceptable timeframe post unplanned disruption. Objectives to the Strategy are to provide structured definition and solution to each action item in the Strategy, for implementation of a 'total' recovery mechanism in Table 1.

Table 1 Measures to support all critical business functions and locations RTO and RPO recovery strategies for each identified business function and support services Risk management measures to hedge against fiscal losses to the CLIENT's critical business functions in the shortest time possible according to standard projections (4 hours to 1 month). Rapid facilitation of operational recovery post implementation of the it recovery strategy to the "zero" risk level within the CLIENT's companywide systems critical to all business functions Table 1. CLIENT Recovery Strategy Objectives.

With over $500,000,000 in company revenues attributed to over 29,000 clients globally, dependent upon the CLIENT for planning, execution, and ongoing service to their E-Marketplace integrated solution(s) subscribers, serious interruptions due to disaster pose significant risks to both short-term and long-term performance. The interface also includes extensive internal use of the mainframe and midrange systems, so that where the CLIENT's production systems are concerned, the Lincoln Headquarters is the highest risk node in the network due to the occupation of its North American Value Added Network (VAN) telecommunications hub.

The location also houses the production environment for the PeopleSoft database, the target in this portion of the Strategic Recovery Plan. Where the CLIENT has agreed that the selection of the software application (SAP) PeopleSoft is the priority in RTO and RPO planning, service to the Office PC support terminals via the LAN network, and 20 Sun Fire V880 Midrange Systems is integral to administration and monitoring of the CLIENT's Infrastructure; the facilitator to data required to carry out day-to-day operations.

Dangers to the Wide Area Network or GSCI (WorldCom) Frame Relay networks of the CLIENT may be impacted in emergency, causing delays to the GSCI, and more importantly the LAN. Midrange Hardware components for the PeopleSoft SAP also support other activities (i.e. program source control, R+D testing, Vantive). Unix environment backed takes place on Sun midrange system via Legato; creating a journal relocated off site every six weeks. Finally, consideration.