Laserfiche WebLink
<br />IRM Corporate Applications <br />This group, in collaboration with the eSRs and other customers, develops and supports <br />Westemwide cOr]lorate information resource management applications. <br /> <br />Comments opposed shifting any data communications responsibility out of ADPIIRM. Enough <br />evidence was raised to persuade senior management that the final "Will Be" needed to be neutral <br />on this issue. To resolve this issue, a collaborative process involving interested/expert stafffrom <br />the CAO and the ehiefProgram Office will be initiated. Other comments suggested that long- <br />term cost savings could be accomplished by avoiding the expense ofleased circuits in favor of <br />microwave upgrades to support communications. This issue will also be addressed through a <br />collaborative process. <br /> <br />Staffing for operations was a subject of comment. Due to the HQ responsibility for several <br />Westemwide applications, including the need to staffmultiple shifts, it was suggested that a CSO <br />staff of three was too small and an increase to three operations staff in each eSR may be too <br />large. This comment appears to have some validity, and needs to be addressed through a <br />collaborative process within the IRM community. Staffing levels may be adjusted depending on <br />the outcome of this collaboration. <br /> <br />The proposed "Will Be" called for a proposed 70130 split between the Federal workforce and <br />contractor support. In recognition of the competitive IRMjob market, and the need to assure <br />that Western has the right balance between workforce continuity and up-to-date skills, this <br />balance has been changed to a 50/50 split for aD IRM offices Westernwide. Ifnecess~'Y, <br />adjustments to this split may be made by IRM managers based upon such factors as local job <br />market COnditioDS. <br /> <br />Final staffing level: 12 FfE, 12 contractor <br /> <br />IRM CSO Support <br />The IRM CSO Support group supports the computer and infonnation management needs of <br />people who work in the CSO. <br /> <br />Several comments suggested that the IRM function should be centralized, and that a Corporate <br />Information Office be established that reports directly to the Administrator, in recognition of its <br />importance. It was further suggested that the eso and corporate applications groups could be <br />combined and report to the same IRM manager. <br /> <br />In considering this comment, senior managers determined they need more focus on Western's <br />corporate IRM strategy in the future. Rather than establishing another direct report to the <br />Administrator, the senior managers recognize that they need to be involved in and provide future <br />direction for Western's IRM functions. The final 'Will Be" does not centralize IRM, relying <br />instead on the model of decentralization and collaboration to meet the needs oflRM customers. <br />The CSO and corporate applications groups will not be merged, to assure focus on their <br />respective respoUSlbilities and to avoid the risk ofCSO support becoming a secondary priority. <br /> <br />Final staffing level: 9.5 FfE, 9.5 contractor <br /> <br />10 <br />