1 Organizational Realignment for Enterprise Operations (EOPS) Presented by- Diane Camilleri September 4, 2009 Briefing for National Treasury Employees Union
Today’s Meeting… Purpose: A briefing to describe the realignment activities within the EOPS organization. Agenda: Introductions Review the Specifics: Purpose of Realignment? The Specifics: What Will Change? What Will Not Change? Next Steps & When will it change? Questions & Concerns…
Purpose of the EOPS Realignment… In the past four years, the EOPS organization has grown from approximately 1,000 to nearly 1,700 employees today. The increase of 700 employees is a result of business decisions made by the CIO to realign servers and employees associated with that work into EOPS. As a result, many organizations within EOPS became unbalanced in span of control and scope of work. In addition, a review was conducted to assure employee PD’s accurately reflected the duties being performed. The intent of this realignment is to clean up these “housekeeping” type of issues. There will be no change to employee duties as a result of this realignment.
Let’s Begin… What Changes? The Operations Support Office is the centralized administrative office for EOPS. As the technical staff has grown, the administrative staff has also expanded. The major change in this group is that the Program Coordination Staff is being split into two sections – HR and Communications Services and Training and Support Services. Four bargaining unit employees will be realigned following their work into the Training and Support Services group. No changes in PDs.
Let’s Begin… (Cont’d) What Changes (cont’d) The Operational Security Program Management Office has had several realignments of personnel from Cybersecurity. As a result of additional employees and increasing demands dictated by GAO and TIGTA, the structure was expanded to include a new Security Management and Requirements Office. Employees currently doing this work will be realigned into this office which will require a first and second level management change for nine employees. One BU employee had a PD number change to more accurately reflect the work he has been doing.
Let’s Begin… (Cont’d) What Changes (cont’d) The Customer Relationship and Integration (CR&I) Division will incorporate the ESM Branch from the ITI Division. This will affect 42 BU employees in second line manager only. Two sections in CRI will be realigned from the existing Infrastructure and Acquisitions Management Branch to the Strategic Planning Branch. This will affect 25 BU employees in second line manager only.
Let’s Begin… (Cont’d) What Changes (cont’d) The Enterprise Computing Center changes were primarily to shift employees and their work to appropriate sections/branches. In the Service Center Operations Command Center, 5 Data Base Analysts will be realigned into the Data Management Branch. Six Systems Administrators will move to the Mainframe Operation Branch. No PD changes, just first level managers will change. In the Systems Integration Branch, 6 BU employees are changing PD’s to accurately reflect the work they have been doing. In the Tier 2 Operations Branch, 5 employees are being realigned to follow their work and will have a new first line manager.
Let’s Begin… (Cont’d) What Changes (cont’d) The ITI Infrastructure Division will split into two separate divisions – Large Systems and Storage Infrastructure Division and the Server Middleware and Test Infrastructure Division. The split of the division will impact 156 BU employees as follows: 62 BU employees will change second level managers 67 BU employees will change first level managers 35 employees will be assigned to PDs that accurately reflect the work they are currently doing. (8 of these employees also have first/second level management changes).
What Won’t Change? Customers POD Grade Duties Performed Critical Job Elements (CJE’s) Shift Tour of Duty
Next Steps… 7114 Meeting week of September 14, Implementation date September 27, 2009.
Your Concerns and Questions…