Accessibility Skip to Top Navigation Skip to Main Content Home  |  Change Text Size  |  Contact IRS  |  About IRS  |  Site Map  |  Español  |  Help  

11.53.3  Policy and Strategic Planning

11.53.3.1  (09-23-2008)
Communications, Liaison and Disclosure's (CLD) Policy and Strategic Planning (PSP)

  1. The mission of Policy and Strategic Planning (PSP) is to:

    1. Serve as the operational link between all SB/SE Communications, Liaison and Disclosure (CLD) components.

    2. Establish and maintain strategic plans, policies and standard procedures for CLD functions.

      Example:

      The IMRS program.

    3. Provide support to members of the CLD Director's staff while they conduct operational reviews.

    4. Identify and resolve issues that impact SB/SE stakeholders.

    5. Provide coordinated and complete SB/SE responses to GAO and TIGTA reports; track legislative implementation efforts.

    6. Provide critical support to the goals and priorities of CLD.

    7. Coordinate all CLD cross functional initiatives.

      Example:

      Tax Gap.

  2. PSP's responsibilities include:

    1. Developing and implementing guidelines for all CLD functions and programs ensuring processes are supported with required CLD technologies.

    2. Establishing overall CLD policy and strategic objectives in coordination with SB/SE compliance priorities.

    3. Providing centralized oversight and program coordination.

      Example:

      Establishing standard SETR programs for specific program time reporting.

    4. Preparing reports that gauge adherence to the organizational priorities.

    5. Submitting information concerning organizational performance to members of the CLD Director's staff for consideration as they conduct operational reviews.

    6. Coordinating the identification and resolution of issues that impact SB/SE stakeholders and directing activities of the Project Manager and staff charged with oversight of the Issue Management Resolution System (IMRS).

    7. Coordinating SB/SE's responses to GAO and TIGTA reports, tracking legislative initiatives, and developing appropriate implementation plans.

    8. Providing guidance and monitoring CLD's SB/SE Request for Organizational Change (S-ROC) process.

    9. Preparing appropriate Work Request Tracking System (WRTS) items.

    10. Developing and updating the CLD IRMs.

    11. Identifying, developing, and representing CLD Information Technology (IT) needs for consideration and discussion with Business Systems Planning (BSP).

    12. Creating agendas and capturing minutes for the Executive Steering Committee (ESC), Governance Board, and Management Advisory Council.

    13. Overseeing CLD's Strategic Planning.

    14. Monitoring various inventory management statistics relating to statutory requirements, including Governmental Liaison and Disclosure (GLD) Measures, GAO/TIGTA procedures/timeliness, and Disaster activity for CLD.

    15. Ensuring timelines for TRAS/SETR system submissions are followed.

    16. Overseeing SB/SE legislative proposals that are sent through SB/SE Commissioner and Legislative Affairs for consideration in the Treasury Reports from the Legislative Implementation Tracking System (LITS) and the Joint Audit Management Enterprise System (JAMES).

    17. Implementing Financial Management Controls (FMC).

11.53.3.1.1  (10-01-2006)
Key Interdependencies of Policy and Strategic Planning

  1. The Director, PSP reports to the Director, CLD.

  2. Director PSP serves as the operational link between all SB/SE CLD components.

  3. Director PSP coordinates programs with all Business Operating Divisions (BOD).

  4. The following managers report to the Director PSP:

    • Chief, Planning and Review

    • Chief, Operations Support

    • Chief, TIGTA/GAO/ Legislative Implementation

    • Project Manager - Issue Management Resolution System (IMRS)

  5. The Web site for Policy and Strategic Planning is accessed at: http://mysbse.web.irs.gov/CLD/PSP/default.aspx.

  6. PSP staff contact information is found on the IRS intranet at the following web address: http://mysbse.web.irs.gov/CLD/PSP/PSPcontact/default.aspx.

11.53.3.1.2  (09-23-2008)
Issue Management and Resolution System (IMRS)

  1. The mission and purpose of issue management is to:

    1. Provide stakeholders and practitioners with a method of surfacing concerns about IRS policies, practices, procedures, and offering suggestions.

    2. Resolve identified issues relating to IRS policies, practices, and procedures in a timely manner.

    3. Share issue resolutions with internal and external stakeholders (nationally and locally) and ask that they share these with other members of their organizations.

    4. Identify trends in filing and payment of taxes that may require educational programs, seminars, symposia, etc., for stakeholders and practitioners to provide guidance on updates to IRS policies, practices, procedures, and tax law changes as appropriate.

    5. Provide opportunities for exchange of information with representatives of stakeholder and practitioner organizations and the appropriate representatives of the IRS.

    6. Refer issues identified by stakeholders, which require explanation, evaluation or changes pertaining to other IRS programs, to the responsible office within the IRS, i.e., Taxpayer Burden Reduction, Abusive Schemes, Forms and Pubs, Office of Legislative Affairs, and Governmental Liaison (GL) Business Template.

11.53.3.1.2.1  (09-23-2008)
Roles and Responsibilities

  1. The Issue Management Resolution System Project Team includes the IMRS Project Manager, and HQ Analysts.

  2. The role of the IMRS Project Manager is to:

    1. Provide oversight of the Issue Management program for CLD.

    2. Monitor IMRS, together with the IMRS HQ Analysts, to ensure timely resolution and responsiveness to stakeholders.

    3. Facilitate IMRS Working Group (WG) efforts to enhance the program, support liaison relations, and identify Compliance trends.

    4. Provide guidance and support to Area Managers and the IMRS Working Group members, including the development and delivery of IMRS Training.

  3. The role of the IMRS HQ Analyst is to:

    1. Coordinate elevated issues with the appropriate Headquarters officials.

    2. Coordinate with CLD Communications for development of communication products for local and national issues.

    3. Together with the IMRS Project manager, monitor IMRS to ensure timely resolution and responsiveness to stakeholders.

    4. Identify trends appropriate for key messages and communications to stakeholders through liaison activities.

    5. Facilitate the delivery of information/educational materials to internal and external stakeholders.

    6. Identify issue patterns and opportunities for burden reduction.

    7. Develop a comprehensive strategy for using the IMRS and IMRS Question & Answers (Q&A) databases to identify and deliver outreach and enhance content on IRS.gov.

  4. The Issue Management Resolution System Project Team partners with Stakeholder Liaisons (SL) or Governmental Liaisons (GL), Area Managers, and the IMRS Working Group to coordinate the IMRS program.

  5. The role of the Stakeholder Liaison, SL HQ Tax Analysts, or Governmental Liaison in regard to the IMRS program is to:

    1. Act as the primary contact point (liaison) for stakeholder, practitioner, and industry organizations.

    2. Maintain regular continuing contacts and open lines of communications with stakeholders to ensure early identification of issues and concerns and potential issues for IMRS Q&A database. IMRS Q&A explained in 11.53.3.1.2.6(3), Glossary of IMRS Terms.

    3. Review minutes of the meetings with industry stakeholders and practitioners to identify issues for IMRS and/or IMRS Q&A.

    4. Use the Issue Management Decision Tree (found on the IMRS home page at: http://sbse.web.irs.gov/cl2/sl/IMRS/index_login.asp) to develop and determine the scope of the issue.

    5. Elevate stakeholder issues to the manager for concurrence. Fully developed issues are added to IMRS, based on established guidelines.

    6. Monitor identified issues and take appropriate actions to resolve the issues.

    7. Work with CLD staff on delivery of key messages and/or issue resolutions for internal and external audiences.

  6. The role of the Area and SL HQ Managers are to:

    1. Review issues elevated by employees and determine if appropriate for IMRS. If issues do not meet IMRS criteria, determine appropriate actions needed to resolve the issues.

    2. Ensure employees enter appropriate issues into IMRS and take timely action toward resolution.

    3. Elevate issues that cannot/should not be resolved at the local level, (i.e., issues with national or international impact).

    4. Use the local Stakeholder Relationship Management Council to stay informed of developments of interest to IRS functions, practitioners and industry stakeholders, and elevate appropriate issues through IMRS in accordance with established guidelines.

    5. Ensure key messages and/or communication products, developed by SL Headquarters regarding issue resolution, are delivered to internal and external stakeholders.

    6. Close resolved IMRS issues in the database.

    7. Coordinate the use of the IMRS Local Issues Database. (See IRM 11.53.5, Stakeholder Liaison Activities, for procedures on the IMRS Local Issues Database).


    While consistency of Program management activities across the Areas is recognized as constructive and necessary for its success nationwide, nothing in this section is construed prohibitive. Each individual Area Manager’s need to provide his/her own managerial approach, initiatives, oversight, and/or authority, to the extent that they generally impact on the IMRS program.

  7. The role of the IMRS Working Group is to:

    1. Increase the dialogue across SL HQ Managers and the Field Areas on stakeholder issues and Q&As, promoting engagement and involvement in issue resolution.

    2. Build and maintain a clear, consistent, communication channel between Headquarters and the Field on stakeholder issues.

    3. Understand fully and explain to others within their respective Areas the uses, capabilities, related guides, procedures for using the National IMRS Issues database, the National IMRS Q&A database, and each respective Area’s Local IMRS Issues database.

    4. Serve as mentors within their Areas to provide help and guidance with IMRS issue and Q&A identification, and development.

    5. Work with the Area Manager to ensure communication about the IMRS program is ongoing Area-wide.

    6. Review and analyze Area issues and Q&As to ensure they are appropriate, properly developed, complete, and resolved in a timely manner.

    7. Participate in regularly scheduled WG calls to share research tips and techniques and discuss emerging issues, Q&As, outreach requests, IMRS sub-team projects, and various other IMRS concerns. On an ongoing basis, the Working Group members should use the IMRS SharePoint site as a group communication tool.

    8. Fulfill the duties and responsibilities of the IMRS WG members as they relate to Communications and communications products, as described in 11.53.3.1.2.1(8).

  8. Any need for outreach materials or efforts are entered into the National IMRS Issues database. The WG will vet each issue posted, and help determine the issue’s impact and actions needed. In addition, the duties and responsibilities of the IMRS WG members as they relate to Communications and communication products are:

    1. Take the lead in briefing SL employees within their respective Areas regarding changes to the CLD intranet, approved communication products in the Outreach Initiatives Database, and related activities surrounding the entire communication process.

    2. Identify the need for communication products within their respective Areas based on stakeholder requests.

    3. Research existing materials to determine whether appropriate products currently exist.

    4. Where necessary and practical, combine existing materials to meet stakeholder needs.

    5. Requests for new materials are elevated through the management chain and timely placed on the Issue Management Resolution System (IMRS).

  9. Specifically, WG members should ensure that SL Field employees within their Areas understand that:

    1. They should share only material approved for external communication with external stakeholders.

    2. They should coordinate requests for new topics or materials through the IMRS and Communications process.

    3. News releases and material published in IRS.gov content, while approved for distribution, should not be altered prior to distribution if that information is shared across geographic areas, unless prior IMRS HQ approval is obtained.

11.53.3.1.2.2  (09-23-2008)
IMRS SharePoint

  1. The IMRS SharePoint provides a single workspace for the IMRS Project Manager, IMRS Program Analysts, and IMRS Working Group to coordinate schedules, organize documents, and participate in discussions within the organization and over the intranet.

  2. Authorized users can access documents and information through IMRS SharePoint under "Document Libraries" where sections may include:

    • Meeting Minutes (prepared from the WG meetings)

    • Shared Documents (significant or archived Hot Issues shared with the team)

  3. The IMRS SharePoint also includes:

    • Announcements (significant or important messages posted on the IMRS Home Page)

    • Links (related Web sites)

  4. The IMRS SharePoint "Discussion Boards" feature is used to regularly communicate about potential issues, Q&As, and requested Outreach Material.

  5. Access to the IMRS SharePoint is provided to the IMRS WG Members, SL Area Managers, and other employees, upon request. Requests for access are directed to the National IMRS Project Manager.

11.53.3.1.2.3  (09-23-2008)
Significance of Issue Management Resolution System

  1. Issue management is an important tool in our efforts with stakeholders and practitioners to effectively influence tax compliant behavior. CLD has primary responsibility to ensure issues raised by SB/SE stakeholders are addressed and, when possible, resolved.

  2. Issue management and IMRS provide a framework of support for relationship managers who ensure proper tracking and response to stakeholder issues.

  3. Issue management is tracked and monitored through the IMRS Database, the IMRS Local Issues Database, and the IMRS Q&A Database.

  4. The IMRS Database, a web-based application, facilitates tracking and monitoring of National, International, and significant local issues.

    1. The IMRS Database allows SB/SE to pro-actively gather data on issues, detect trends, monitor, resolve issues, and plan and distribute communications with greater efficiency.

    2. The initial screen has three main links: Submitter, Approver, and Issue Search. The user must select one of these links to gain access to the application.

  5. The IMRS Local Issues Database captures issues that are raised in each Stakeholder Liaison Area.

    1. Local issues are entered into the database and may be resolved locally, elevated to IMRS, or referred to other functions such as Forms and Publications, Taxpayer Burden Reduction, etc. Legislative proposals are forwarded to Policy & Strategic Planning’s GAO/TIGTA/Legislative Issues function. The system is designed to allow each Area to easily capture issues and maintain historical data as needed.

    2. The SL HQ and Area Managers determines who will input issues into the system, either designating individuals or giving access to all group members. However, it is the responsibility of the IMRS Area Lead to monitor the system and provide guidance for the resolution of the issue.

  6. IMRS Q&A Database is designed to parallel and augment the current IMRS database.

    1. The purpose of the IMRS Q&A database is to catalog and house FAQs for continuing reference, to eliminate duplicated research efforts. The system is designed to function as an additional source of information available to the IMRS user.

    2. The IMRS Q&A database was designed to enhance the IMRS program by creating new user features, such as the ability to search by using keyword topic, which simultaneously searches the IMRS Q&A and the IMRS databases.

11.53.3.1.2.4  (09-23-2008)
Reports and Records

  1. The IMRS Project Manager produces a monthly report that provides a brief synopsis of some of the issues that were received and/or closed during the past month. These reports assist the Area Manager in discussing current issues with their stakeholders. The relationship manager also shares resolved issues with liaison partners in advance of meetings, enabling partners to share information with their membership and provide feedback. Feedback assists in determining the scope of many issues and identifying other concerns. The IMRS Monthly Overview is available on the Tax Professionals page on IRS.gov. and past issues are archived.

  2. The IMRS Project Manager generates input for the Director's PSP Monthly Report, Business Performance Review, Operational Review, and ad hoc reports.

  3. General Information on IMRS is available on the IMRS Home page: http://sbse.web.irs.gov/cl2/sl/IMRS/index_login.asp.

  4. The annual IMRS Report is a compilation of the significant national and international IMRS issues closed during the calendar year. The report is available early the following year alongside the IMRS Monthly Overview.

  5. The "Hot Issues" Report is also available on the IMRS Home page: http://sbse.web.irs.gov/cl2/sl/IMRS/index_login.asp.The current version of "Hot Issues" is also posted on IRS.gov. Archived issues are maintained on the SL Bulletin Board SharePoint and the IMRS SharePoint.

11.53.3.1.2.5  (09-23-2008)
System Procedures

  1. A guide to system procedures is available on the IMRS Home Page.

  2. Access to the System:

    1. All employees have "research and input" access to IMRS and "read only" access to the IMRS Q&A Databases.

    2. Individuals with a need for a higher level of access (Approver or Administrator) should contact the project manager.

11.53.3.1.2.6  (09-23-2008)
IMRS Key Information

  1. Users may access IMRS through the IMRS Home page at: http://sbse.web.irs.gov/CL2/sl/IMRS/index_login.asp.

  2. IMRS Monthly Updates are found on irs.gov at: http://www.irs.gov/businesses/small/article/0,,id=158507,00.html.

  3. A research tool kit with tips and useful links is available on the IMRS home page at: http://mysbse.web.irs.gov/CLD/SL/IssueManagementResolutionSystemIMRS/IMRSArticles/2660.aspx.

11.53.3.1.2.7  (09-23-2008)
Glossary of IMRS Terms

  1. Issue Management Resolution System (IMRS) - A web-based application that permits tracking and monitoring of local, national, and international issues identified by Stakeholder Liaison and Governmental Liaison partners and stakeholders. The system provides management officials with trend analysis that determines how widespread the issues are and captures them in a centralized electronic format.

  2. Local Issues Database – A database developed for the purpose of capturing all issues that are raised in each Stakeholder Liaison Area.

  3. IMRS Q&A – The IMRS Q&A is an electronic database, designed to catalog and house FAQs so others can use them without reinventing and/or re-researching a response. The system is designed to function as an additional source of information available to the IMRS user. The link to the database is: http://sbse.web.irs.gov/cl2/sl/IMRS_QA/default.asp.

  4. IMRS Decision Tree – A checklist to help ensure issues are fully developed in scope, impact, and understanding. Employees should use the decision tree as a guide for gathering information before submitting an issue to IMRS.

  5. IMRS User Guide – The IMRS User Guide is an on line guide that describes how to use the IMRS System and provides detailed screen shots of system applications.

  6. IMRS Research Toolkit – The IMRS toolkit provides electronic links to help employees, Working Group members, and Area Managers fully develop the issues.

  7. Issue – A policy, practice or procedural issue identified by internal and external partners and stakeholders.

11.53.3.2  (09-23-2008)
PSP's Planning and Review

  1. Planning and Review (P&R) provides critical support to Policy and Strategic Planning (PSP) in alignment with the goals and priorities of the IRS and SB/SE Communications, Liaison and Disclosure (CLD).

11.53.3.2.1  (09-23-2008)
Mission and Responsibilities of Planning and Review

  1. The mission of Planning and Review (P&R) is to establish and maintain critical support to all CLD. P&R develops programs, policies, reviews internal procedures/processes, and provides technical assistance. The assistance includes conducting internal workshops and preparing written resource materials for the development and implementation of local procedures. P&R coordinates with other internal partners who have responsibilities related to the functionality of SB/SE CLD. In addition P&R:

    1. Develops and implements SB/SE and CLD wide policies.

      Example:

      Annual performance reports and measures.

    2. Collects and reviews processes to ensure adherence by all CLD components.

    3. Provides leadership and direction to the CLD strategic planning effort.

    4. Provides support to CLD Director's staff.

  2. Planning and Review provides overall governance, strategic planning, policy, oversight of policy implementation, and general processes in CLD by:

    1. Developing quantitative indicators to evaluate progress made in implementing policies within the established time frames.

    2. Monitoring the implementation and effectiveness of products and services.

    3. Ensuring BPR statistical data is recorded and monitored.

    4. Reviewing documentation and statistics to ensure that key business objectives are met and that continuous improvement is made to verify the effectiveness of our systems.

    5. Identifying and communicating key responsibilities and practices to achieve business results.

    6. Contributing to CLD business goals by achieving target deliverables.

    7. Supporting the planning and management of business unit processes and practices to ensure that programs are aligned with business goals and objectives.

    8. Acting as the advocate and Point of Contact (POC) to all CLD components.

    9. Monitoring work processes routinely to ensure they are operating as determined by process requirements.

    10. Monitoring and assessing data to ensure that work is performed accurately and resource allocations are tracked appropriately.

    11. Documenting and tracking actions.

    12. Identifying hindrances to the achievement of performance objectives and measures.

    13. Participating in cross-functional processes to develop and implement program and assessment activities.

11.53.3.2.2  (10-01-2006)
Key Interdependencies of Planning and Review

  1. The Chief, P&R reports to the Director, PSP.

  2. The P&R staff partners with interagency counterparts within SB/SE, Wage and Investment (W&I), Large and Mid-Size Business (LMSB), and Tax Exempt and Government Entities (TE/GE) to develop processes and report on the SB/SE Business Performance Review (BPR), IRS Strategic Planning Process, and Tax Gap.

  3. Work with Modernization and Information Technology Services (MITS) to develop and implement monitoring and tracking systems.

11.53.3.2.3  (09-23-2008)
Roles and Responsibilities of Planning and Review Analysts

  1. Establish and maintain processes and coordinate development of CLD Strategic Plan, including the development of strategic assessments and performance measures.

  2. Collect performance data from all CLD components to include in the Business Performance Review (BPR), Monthly Report, and Operational Review (OR) for senior management.

  3. Act as Point of Contact (POC) for CLD operating functions and SB/SE Research activities.

  4. Provide support and guidance to CLD management and project teams to improve the quality of business processes and meet the needs of customers.

  5. Act as administrative support for various key program initiatives.

11.53.3.2.4  (09-23-2008)
Business Performance Reviews (BPR)

  1. The Business Performance Review is a performance management document that is prepared quarterly and presented to the Deputy Commissioner, Services and Enforcement.

  2. Chief, P&R is responsible for coordinating the CLD input to the BPR.

  3. Copies of the SB/SE BPR reports are on the Strategy and Finance internet site: http://sbse.web.irs.gov/SF/PPM/OPR/BPR/BPR.htm.

11.53.3.2.5  (09-23-2008)
Operational Reviews

  1. The Operational Review (OR), conducted by the SB/SE Commissioner and Deputy Commissioner, is generally held bi-monthly. During the OR the Director, CLD reports on:

    • CLD Performance Measures

    • Significant accomplishments and Issues/concerns

    • Employee Engagement Activities

    • Functional Updates

    • Financial Plan Issues

  2. P&R is responsible for preparing the documents for the OR by consolidating the input from all CLD Functions.

11.53.3.2.6  (09-23-2008)
Communication Liaison and Disclosure Strategic Planning Process

  1. The Strategy & Finance Office, SB/SE (S&F) facilitates development of the SB/SE Strategic Plan. They provide a process to senior leadership on strategic direction and priorities that SB/SE should pursue to meet agency goals while effectively using limited resources. The SB/SE Strategic Plan (the SB/SE Plan) is usually a multi-year outline of strategies and priorities that identifies SB/SE program goals. The SB/SE Plan is written every fiscal year.

  2. P&R represents CLD and works closely with S&F in developing the SB/SE Plan and the CLD Strategic Plan.

    1. P&R is responsible for ensuring CLD involvement and timely response to S&F requests for input to the SB/SE Plan.

  3. P&R develops the CLD Strategic Plan, outlining activities supporting the SB/SE Plan.

    1. The CLD Strategic Plan is also written every fiscal year.

    2. P&R ensures all CLD functions, involvement in developing the plan, and their input adequately supports the SB/SE plan.

    3. P&R ensures timely response to S&F requests concerning the CLD Plan.

  4. P&R develops the annual Program Letter. Generally the Program Letter transmits the current year(s) strategic plan to employees; it is signed by the Director, CLD.

11.53.3.2.6.1  (09-23-2008)
Measures

  1. CLD's Strategic Plan contains measures developed for use in setting and achieving organizational performance outcomes.

  2. P&R monitors the measures developed by the other CLD functions and uses them in appropriate reports on behalf of PSP.

11.53.3.2.7  (09-23-2008)
Requesting Research Projects Overview

  1. CLD's P&R established procedures for submitting research projects that supplement the SB/SE Research Procedures. The procedures are available on the CLD Web site at: http://mysbse.web.irs.gov/CLD/PSP/MgrAlerts/1486.aspx.

  2. P&R is responsible for coordinating, controlling, and monitoring all CLD research requests.

  3. P&R serves as the liaison between CLD and SB/SE Research and assists with formulating, expediting, requesting, and processing all research requests.

  4. Each CLD functional office is responsible for generating and developing its own research projects or ideas and for submitting its research requests to P&R.

11.53.3.2.7.1  (09-23-2008)
Steps in Requesting a Research Project

  1. The CLD procedures for requesting a research project are as follows:


    Step 1. CLD functional office(s) determine if research is necessary to facilitate a project by considering the following:

    1. What kind of information is needed, e.g., counts, percentages, estimates, analyses, models, testing, profiling, etc.

    2. Why is the information needed, e.g., what value would it add to the project or assignment?

    3. Who uses the research results? e.g. projects requiring support of resources from other functions are in the research request planning process.


    Step 2. CLD employees discuss their research ideas with their managers and secure approval for their research requests.
    Step 3. CLD employees complete the SB/SE Research Request Form available through the Research Web site at: http://sbse.web.irs.gov/Research/, using the link "How to Request SB/SE Research" . The request initiator and their Director must sign the form and send it, via e-mail, to the CLD Research Team.
    Step 4. P&R reviews the research request and logs it into the research request database.
    Step 5. P&R reviews the SB/SE Research Reports Database summary to determine if similar research projects exist and direct the initiator to any relevant reports.
    Step 6. P&R contacts the initiator to discuss resource needs and projected time frames. Initiators must recognize that time frames should be flexible since SB/SE Research may not be able to accommodate the initiator's projected time frames.
    Step 7. P&R submits the signed Research Request Form to SB/SE Research for approval by the SB/SE Director, Research.
    Step 8. SB/SE Research schedules an Initial Customer Meeting within 45 days of receiving the approved research request to address project needs. During this meeting, they will address project purpose, scope of proposed project, whether resources are available, projected time frames including anticipated completion dates, and whether the project warrants a streamlined or traditional report.

    Note:

    Streamlined projects get completed in a short time frame if it does not involve complex statistical techniques, tests, and can be completed by supplying data tables with standard calculations, etc. Traditional projects typically involve statistical methodologies and are closed with a formal written report to the customer. Traditional projects usually take 9-12 months (or longer) to complete.


    Step 9. SB/SE Research develops a project prospectus (within 45 days of the Initial Customer Meeting) that summarizes the Initial Customer Meeting. The prospectus documents the project’s objectives, purpose, methods, activity schedule, and costs. It serves as a contract between SB/SE Research and the CLD requesting office.
    Step 10. SB/SE Research completes all agreed upon work in the prospectus and provides the report within the agreed upon time frames. If agreed upon time frames cannot be met, Research contacts the initiator to revise the project scope or milestones, as needed.

11.53.3.2.8  (10-01-2006)
Internal Management Document Coordination

  1. The Internal Management Document (IMD) Coordinator(s) for CLD are located in P&R and have responsibility to oversee the development and delivery of:

    • New CLD IRM procedures

    • Updates to the IRMs

    • Delegation Orders owned by CLD

    • Policy Statements owned by CLD

    • Interim Guidance Memos for CLD

  2. P&R's IMD Analysts are also responsible for coordinating the review and concurrence of cross-functional IRMs, Interim Guidance Memorandum, Delegation Orders, Policy Statements, and Memorandum of Understanding owned or requested by other operations. The Analysts ensure Form 2061, Document Clearance Record, is forwarded to the appropriate CLD group(s) performing the review and monitors due dates, comments, and concurrences.

11.53.3.2.8.1  (09-23-2008)
Internal Revenue Manual (IRM) Coordination

  1. P&R has the responsibility of coordinating all CLD IRM's.

  2. Requests for reviews and comments/concurrences of other SB/SE IRMs get directed through P&R.

  3. Each CLD component identified a liaison who works with the assigned P&R IRM Coordinator(s).

  4. Annually, all CLD IRMs get reviewed to identify procedures requiring updates. Updates are performed through the year but publishing my be delayed if released during the time the filing season/processing IRMs are worked on by Publishing Services or if they experience a conflict in their workload priorities.

  5. When IRM updates are completed, Form 2061, Document Clearance Record, is used to gather simultaneous clearance requests. After all requested changes are recorded (or discussed to the submitters satisfaction), Form 2061-A, IMD Coordinator Checklist, Form 1767, Publishing Services Requisition, and the final EPIC SGML file is submitted to the National IRM Coordinator in the Servicewide Policy Directives and Electronic Research (SPDER) staff using electronic upload.

  6. Before the IRM(s) are published, the functions must decide the media for the distribution (paper, electronic or both). This information is recorded on the Form 1767, Publishing Services Requisition.

  7. Sample documents are available in a desk guide located on the PSP SharePoint site.

11.53.3.2.8.2  (09-23-2008)
Interim Guidance Memorandum Coordination

  1. Interim guidance is issued when there is a need for an immediate procedure change and the IRM is not yet due for revision and/or updating. The effected CLD function is responsible for developing the interim guidance document and coordinates the approval. Numbering and posting to the internet and intranet is coordinated by the P&R IMD coordinator(s).

  2. Interim Guidance Memorandum (IG) are assigned an expiration date, not to exceed 1 year. Within that year, the function who initiated the guidance memorandum must update the IRM to include the revised procedures.

  3. The SB/SE and CLD P&R IRM Coordinator(s) review the published interim guidance memorandum monthly to ensure that memos close to expiration are in the process of being incorporated into the IRM. IRM Coordinator(s) initiate follow-up contacts with the initiating guidance author(s) to stress the importance of timely revising the IRM procedures. If IRM update delays are expected beyond the interim guidance memorandum's expiration date, an extension of the procedures in the memorandum is need until the IRM revision is completed; but SB/SE discourages extension requests.

  4. Expired memos are also removed regularly from the Electronic Reading Room.

  5. Finalized interim guidance memorandum are accessed on the intranet at: http://sbse.web.irs.gov/MS/IGMemos/.

  6. Samples are additional information is available in the desk guide on the PSP SharePoint site.

11.53.3.2.8.3  (09-23-2008)
Delegation Order Coordination

  1. The Internal Management Document (IMD) Coordinator(s) for CLD are located in P&R and have responsibility of ensuring the Delegation Orders assigned to CLD are reviewed and updated, if necessary, each year. Complete procedures for the Delegation Order process is in IRM 1.2.1, Servicewide Policies and Authorities. The procedures are further defined in Chapter 2 of IRM 1.2.2, Delegations of Authority. Additional background information on the process is found in IRM 1.11.1, Internal Management Documents System.

  2. Delegations of Authority are organized within IRM 1.2 by specific function responsibility. CLD's are in IRM Chapter 1.2.49.

  3. Samples are available in the desk guide on the PSP SharePoint site.

11.53.3.2.9  (10-01-2006)
Stakeholder Liaison and PSP Time Reporting System

  1. Stakeholder Liaison (SL) HQ, SL Field, and PSP report and record hours by Organization Function and Program (OFP) in the Single Entry Time Reports (SETR) system.

  2. SETR input, for the above functions, interfaces with the WP&C system.

  3. Weekly validation of SETR is required as follows:

    1. Close of business each Friday, all timekeepers must validate their SETR entries.

    2. Each Monday, prior to 10:00 AM EST, a validation report is generated in SETR to confirm SL & PSP organization numbers are all validated.

    3. If the weekly validation is not completed, telephone or e-mail contacts are made with the appropriate timekeeper/management official.

    4. If validation does not occur timely, Time and Attendance (T&A) adjustments and Individual Performance Report (IPR) changes are required. The IPR adjustments are prepared manually using hard copy forms.

    5. Guidance on making IPR adjustments/changes are contained in IRM 3.30.28.4.5.2,Work Planning and Control - Individual Review, or through Servicewide Electronic Research Program (SERP).

  4. SETR/WP&C is designed to use specific OFP codes to track time charged. Weekly WP&C reports are used to show how time was applied by the organizations.

  5. Valid OFP's are found at the PSP Web site: http://mysbse.web.irs.gov/CLD/PSP/Time+Monitoring/default.aspx.

11.53.3.2.10  (09-23-2008)
Stakeholder Liaison Resource Tracking Process

  1. In August 2007, PSP, P&R, SL Field, and SL Headquarters reached an agreement that a formal work plan and work schedule would not be developed or loaded into the automated systems (STRAWS) for their organizations.

  2. P&R performs quarterly monitoring to identify resource usage anomalies in the administrative time reporting by SLs using the actual hour data recorded in the Work Planning & Control (WP&C) system at the following web address: http://eosco.enterprise.irs.gov/managers/index.htm.

11.53.3.2.11  (09-23-2008)
Section 1204 Quarterly Managerial Certification

  1. The Consolidated CLD Managers Certification Listing is updated and submitted quarterly to the SB/SE Section 1204 Coordinator.

  2. The report is usually due about 3 1/2 weeks after the quarter ends.

  3. TIGTA requires that the functions maintain a current list that contains the name, work title, seid, and POD for each of the managers, by quarter, indicating their Section 1204 classification status. Due to the current nature of CLD work, the managers are not required to quarterly submit individual self-certification forms and are classified "Non-Section 1204" .

  4. P&R is responsible for gathering the updates from all the CLD functions and for providing a consolidated response to the SB/SE Section 1204 Coordinator. Managers, acting managers or employees detailed into management positions, on the last day of a quarter, must be shown on the listing.

  5. Samples are available in a desk guide located on the PSP SharePoint site.

11.53.3.2.12  (09-23-2008)
Social Security Administration (SSA) Trust Fund Quarterly FTE Chargeback Report

  1. The CLD Consolidated SSA report captures the Stakeholder Liaison (SL) Field FTE count for the portion of their work connected to the Federal Insurance Contributions Act (FICA) Administration. A pre-determined percentage of certain program work is reported for chargeback to the SSA Trust Fund Account. The labor (direct program hours) and non-labor (overhead: managerial and clerical) costs for each quarter are provided.

  2. These costs must be provided within 10 business days into the new quarter.

  3. A P&R Analyst gathers and submits a consolidated response to the SB/SE Strategy and Finance Budget Analyst who performs an analysis to compare estimated costs and documents significant variances.

  4. Background
    Social Security and Medicare taxes pay for benefits to workers and their families under FICA. Social Security taxes pay for benefits under the Old Age, Survivors, and Disability Insurance part of FICA. Medicare taxes pay for hospital benefits. Each public sector employee contributes to these taxes and the employer pays a matching amount. Self-employed taxpayers must also pay Social Security and Medicare taxes in the form of self-employment taxes. These taxes are deposited to the OASDI and HI Trust Funds.
    The Secretary of the Treasury is directed by the Social Security Act to pay to the Treasury General Fund from the OASDI and HI Trust Funds, the amount estimated as expended by the Department of the Treasury, including the IRS, for this service. The IRS’ expenses make up a significant portion of the charges to the OASDI and HI Trust Funds. On a quarterly and annual basis, IRS is required to provide certain reports to the Bureau of Public Debt (BPD) on administrative costs incurred in gaining taxpayer compliance, and providing customer service around these taxes.

    Behind this requirement, a reasonable, supportable, and repeatable methodology was developed for reporting these costs using guidelines provided by SB/SE Strategy and Finance. Their Budget Office is responsible to gather statistics on work performed in the functions that contribute to the collection of FICA taxes.

  5. Responsibilities
    SB/SE is responsible for determining the labor and non-labor costs expended by each organization within SB/SE that provides services to the OASDI and HI Trust Funds. These costs are provided to the Beckley Finance Center (BFC), by the Budget Office on a quarterly basis. In addition, each year SB/SE must provide relevant information to the BFC for preparation of a forecast of OASDI and HI Trust Funds expenses to be incurred the next fiscal year.

    CLD is required to report the cost of education and outreach efforts to employers and self-employed taxpayers. A file is maintained that includes source reports (WP&C extracts & Calculation Template) to support quarterly costs and the fiscal year assumption document used to calculate the data.

  6. Samples are available in a desk guide located on the PSP SharePoint site.

11.53.3.3  (10-01-2006)
PSP's Operations Support

  1. Operations Support (OS) provides critical operational and administrative support to Policy and Strategic Planning (PSP) in concert with the goals and priorities of Communication, Liaison and Disclosure (CLD).

11.53.3.3.1  (09-23-2008)
Mission and Responsibilities of Operations Support

  1. The primary mission of OS is to provide operational and administrative support to all functions within the CLD organization enabling SL Field, SL Headquarters, Governmental Liaison & Disclosure, Safeguards, and Communications to achieve their respective goals and objectives.

  2. To assist CLD in accomplishing their mission, the Chief, OS provides leadership and direction in the following program areas:

    1. Develops and issues consistent CLD operational guidelines to ensure procedures are standardized throughout the organization.

      Example:

      CLD Employee Suggestion Program (ESP)and CLD IDRS Security.

    2. Develops and coordinates hiring and staffing activities within the CLD organization including overseeing SB/SE Requests for Organization Changes (S-ROC).

    3. Collaborates with directors to develop CLD's training plans.

    4. Ensures Mandatory Briefing certifications are completed timely.

    5. Provides oversight of Employee Engagement efforts and survey administration.

    6. Coordinates with National Labor Relations and SB/SE SMART Human Capital Office regarding all National Treasury Employees Union (NTEU) related issues.

    7. Provides oversight and coordination of activities such as office space, equipment (ITT) and COTR requirements.

    8. Ensures Office of Government Ethics (OGE 450), Confidential Financial Disclosure Reports are prepared and processed timely.

    9. Ensures the Business Resumption Plan is updated as needed.

    10. Coordinates the Work Request Tracking System (WRTS) process.

    11. Works various special projects as assigned by the Director, Policy & Strategic Planning.

    12. Serves as the Unit Security Representative (USR) and coordinates all CLD employees’ USR and IDRS terminal security activities.

11.53.3.3.2  (10-01-2006)
Key Interdependences of Operations Support

  1. The Chief, Operations Support reports to the Director, Policy and Strategic Planning (PSP).

  2. The Operations Support staff interacts at the Headquarters and Field levels with all functions within CLD as well as functions within SB/SE, W&I, LMSB, and TE/GE.

  3. Operations Support staff coordinates all NTEU issues with SB/SE SMART Human Capital Office or Labor Relations.

  4. Operations Support collaborates with MITS equipment and WRTS issues.

11.53.3.3.3  (09-23-2008)
Roles and Responsibilities of Operations Support Analysts

  1. Operations Support Analysts have responsibilities to ensure:

    1. Operational guidance is communicated via CLD Managers’ Alert or other vehicles.

    2. Staffing and hiring goals of CLD are met in a timely manner using resources to maximize candidates for potential positions.

    3. CLD training plans address critical training needs, identifies opportunities for alternative delivery methods, and provides staff with "just-in-time" procedures to meet the current rollout of operational priorities. The Training Analyst should also provide all training opportunities available and ensure slots are available for CLD employees.

    4. Mandatory training of employees is conducted on a yearly basis.

    5. Work space and appropriate equipment is available to employees within the CLD organization.

    6. Employee engagement efforts are communicated to all CLD employees.

    7. WRTS information is input and coordinated throughout the process.

    8. IDRS security issues are handled appropriately.

    9. SB/SE Request for Organizational Change (S-ROC) is timely prepared.

    10. Employee Suggestions are managed and closed timely.

11.53.3.3.4  (10-01-2006)
Employee Suggestion Program (ESP)

  1. The Employee Suggestion Program (ESP) is a vehicle for submitting ideas for improving the organization. Employees are encouraged to submit acceptable ideas and management agrees to consider granting an appropriate award for those adopted. Refer to IRM 1.55.5,Wage and Investment - Employee Suggestion Program, Exhibit 1 (1.55.5-1) for additional guidance.

  2. All suggestions are submitted via the Employee Suggestion database. The website for this database is: http://esp.web.irs.gov.

  3. Suggestions that impact CLD operations are reviewed and assigned to CLD Subject Matter Experts (SMEs).

  4. Operations Support responsibilities are to:

    1. Serve as the local/site coordinator for suggestions coming into the CLD organization.

    2. Review Form 13380, I Suggest, for completeness and meeting appropriate program criteria.

    3. Review Form 13245, I Suggest Transmittal Form, for completeness and appropriately complete the bottom of the form.

    4. Assign a number to the suggestion if the employee is unable to submit the suggestion on the AWSS electronic website. See IRM 1.55.5.7,Wage and Investment - Employee Suggestion Program.

    5. Send an acknowledgement letter to the submitter within seven days of receipt of the suggestion by the coordinator.

    6. Assign the suggestion to Site Evaluator or SME.

    7. Handle all completed suggestion evaluations from Site Evaluator. See IRM 1.55.5.8.

    8. Complete actions for adopted or non-adopted suggestions. See IRM 1.55.5.9.

    9. Perform other actions necessary to monitor the process and close the suggestions.

  5. CLD Suggestion Reviewer is responsible for the following:

    1. Complete their evaluation within 60 days from the date they receive the suggestion case package.

    2. Prepare Form 2665, Suggestion Evaluation.

    3. Review and perfect the cost-benefit analysis.

    4. Contact submitter to clarify the suggestion.

    5. Prepare decision for approving officials signature if the suggestion is rejected or adopted at the local level.

    6. Obtain Approving Official’s signature Form 2665.

    7. Return completed case to CLD ESP Coordinator.

    8. Refer to IRM 1.55.5.5.4 for additional duties.

  6. To accomplish the program responsibilities, OS receives guidance and support from SB/SE SMART Human Capital Office Information Management on the Employee Suggestion Program:

    • Administration

    • Policy

    • Marketing strategies

    • Assignments

  7. The ESP process is owned by the SB/SE SMART Human Capital Office - Information Management. Both OS and SB/SE SMART Human Capital Office - Information Management coordinate efforts to meet both organizations’ employee suggestion program needs.

  8. For additional information on ESP refer to:

    • Automated Employee Suggestion Program http://esp.web.irs.gov or

    • Employee Suggestion Program (Employee Resource Center) http://ansc.irs.gov/suggestions/s-intro.htm

11.53.3.3.5  (09-23-2008)
Unit Security Representative (USR)

  1. The Integrated Data Retrieval System (IDRS) Security Program within CLD is managed in Policy and Strategic Planning, Operations Support. Operations Support will serve as the Unit Security Representative and coordinate all CLD employees’ USR and IDRS terminal security activities.

  2. Operations Support has responsibility to:

    1. Explain all security procedures and instructions that relate to IDRS security prior to adding new users to IDRS.

    2. Perform periodic security awareness training (at least annually) for each IDRS user.

    3. Ensure management has reviewed the security rules with IDRS users and each IDRS user has recertified to the security rules via Form 5081, Information System User Registration.

    4. Prepare and submit on line Form 5081, Information System User Registration.

    5. Process change requests, to add a user, update a present user or any action that requires a Form 5081.

    6. Add and delete command codes to/from employee profiles.

    7. Perform SINOF checks.

    8. Delete the profile of employees who do not require access to IDRS.

    9. Lock and unlock user profiles.

    10. Unlock IDRS terminals.

    11. Initiate the transaction to transfer employee profiles.

    12. Monitor sensitive command code usage.

    13. Review and certify Security Reports.

  3. USR & Group Managers Responsibilities:

    1. The USR and group managers are responsible for reviewing IDRS online Reports Services (IORS) reports on a weekly basis to determine if IDRS users are accessing IDRS for valid work requirements.

    2. The USR is responsible for certifying all IORS reports.

  4. All IORS Reports are certified by the USR. USR Report Certification Requirements:

    • Weekly Security Violations Report

    • Weekly Sensitive Access Report

    • Monthly IDRS Security Profiles Report

    • Quarterly IDRS Security Profiles Report

  5. Manager Responsibilities in the Report Certification Process:

    1. Managers are not required to certify IORS reports but must review weekly, monthly, and quarterly reports per LEM 10.8.34.2.1.10(6)b, Information Technology (IT) Security - Integrated Data Retrieval System (IDRS) Security Handbook and input comments onto the IORS system.

    2. Managers are responsible for reviewing all sensitive access(s) and inputting comments onto the IORS report system.

    3. Managers are responsible for reviewing all violation access(s) and inputting comments onto the IORS report system if patterns of potential misuse are identified.

  6. For additional guidance and briefing documents refer to:

    1. MITS Cybersecurity web site: http://mass.web.irs.gov/IDRS/iors.asp.

    2. LEM 10.8.34.2.1.10, Information Technology (IT) Security - Integrated Data Retrieval System (IDRS) Security Handbook.

  7. Employees’ Responsibility For Reporting Inadvertent Access(s):

    1. Taxpayer Data Access ( Form 11377-E.

    2. Refer to IRM 5.1.1.11.6,General Collecting Procedures - Miscellaneous Guidelines for additional guidance.

11.53.3.3.6  (09-23-2008)
Hiring and Staffing

  1. Operations Support (OS), in coordination with the CLD Director Staff, i.e. the Budget Analyst, develops and coordinates all hiring and staffing activities within the CLD organization.

  2. OS has responsibility to:

    1. Develop the CLD staffing guidelines for hiring, temporary promotions, and details.

    2. Develop, consolidate, and revise monthly staffing charts.

    3. Monitor on-board and authorized staffing patterns.

    4. Implement SB/SE request for organizational changes that impact staffing.

    5. Serve as point of contact for Employment Branch on all personnel related issues.

    6. Maintain vacancy report.

    7. Monitor weekly Career Opportunities Listings.

    8. Coordinate Hardship Transfer requests.

    9. Coordinate request for exception to Hiring Freeze.

    10. Collaborate with SB/SE SMART Human Capital Office to resolve unique staffing issues.

    11. Approve request for Recruit, Temporarily Promote, and Detail.

    12. Develop and revise CLD organizational charts.

    13. Coordinate and assist with the development of new positions descriptions (PD).

    14. Develop guidance for various issues such as no-cost moves/change in post-of-duty.

    15. Develop knowledge, skills and abilities (KSA), and crediting plans for positions.

11.53.3.3.6.1  (10-01-2006)
Hiring and Staffing Reports

  1. OS develops a number of reports and charts to maintain an accurate account of staffing.

    Example:

    Staffing charts, vacancy reports, and organization charts.

  2. CLD Staffing Charts include:

    1. Authorized staffing

    2. On rolls

    3. Division

    4. Positions/title/series grade

    5. Office locations

    6. Post of duty

    7. Bargaining Unit (BU) status

    8. Projected gains/losses

  3. CLD Vacancy Reports include:

    1. Historical information on new hires and promotions

    2. Vacancy status

  4. CLD Organization Charts:

    1. Identifies authorized staffing

    2. Tracks employees on-board and monthly organizational changes

  5. Each division has responsibility to:

    1. Timely submit personnel actions for all approved personnel changes

      Example:

      Recruit, change in post of duty.

    2. Provide monthly staffing changes

  6. To accomplish these, OS receives guidance and support from SB/SE SMART Human Capital Office.

  7. For additional information on the SB/SE Hiring and Staffing Guidelines refer to the following Web site: http://sbse.web.irs.gov/SF/, for Strategy and Finance.

11.53.3.3.7  (09-23-2008)
SB/SE Request for Organization Changes (S-ROC)

  1. The SB/SE Request for Organizational Change (S-ROC) is the method SB/SE uses to review and approve proposed organizational changes. The Director, SB/SE SMART Human Capitol Office, is responsible for monitoring and coordinating organizational change proposals.

  2. S-ROC is the first step taken when seeking approval of organizational design changes. The S-ROC process is not intended as a replacement for routine processes, already in place, to secure funding of additional positions, upgrades, etc. The S-ROC approves the organizational design only. Once the S-ROC is approved, implementation of the new design (e.g., filling positions) is completed in accordance with current Finance and Human Resource guidelines.

  3. Operations Support has responsibility to:

    1. Coordinate all S-ROC changes for Communications, Liaison and Disclosure (CLD).

    2. Coordinate the review and approval of requested organizational changes with SB/SE SMART Human Capital Office.

    3. Determine the organizational change category type.

    4. Provide required attachments.

    5. Prepare required current and proposed organizational charts.

    6. Secure written approval from SB/SE Finance if the change results in a change in salary dollars.

    7. Assist CLD management with the development of the business case for proposed changes.

    8. Coordinate the establishment of TIMIS code changes when applicable.

    9. Implement approved changes.

    10. Maintain historical files on approved S-ROC.

  4. CLD functional offices are responsible for:

    1. Submitting written requests for S-ROC changes to Chief, OS.

    2. Preparing the business case for requests for organizational changes.

    3. Developing new position descriptions when applicable.

    4. Initiating personnel actions to implement approved changes.

11.53.3.3.7.1  (09-23-2008)
S-ROC Categories

  1. All proposed changes are assigned to one of three categories. The category depends on the nature, scope, cost, and expected impact of recommended organizational changes. The three categories, the purposes, and review/approval authority are:

    Category Purpose Review/Approval
    A Proposals that affect very limited components of the overall organization such as:
    1. Eliminating vacant positions that are no longer needed.

    2. Collapsing or combining the existing groups/territories.

    Director, CLD
    B Proposals that involve or affect other operating units, add positions not previously funded, incur additional costs, or involve changes in type of position, grade or series such as:
    1. Increase grade 14 and 15 positions.

    2. Increase management levels and/or narrow the span of control of first line managers.

    Approved by the Director, CLD, Information Management, Business Systems Planning, Human Resources, Finance & Management and Support
    C Major organizational change proposals whose scope and impact directly affect other Business Operating Divisions such as:
    1. Create/abolish/merge Director level organizations within divisions, functional or support unit.

    2. Create, abolish, promote to ES-5 level position and above.

    All levels above, SB/SE Commissioner and IRS Commissioner

  2. To accomplish these responsibilities, Operations Support receives guidance and support from SB/SE SMART Human Capitol Office - Information Management.

  3. For additional information on the SB/SE S-ROC program refer to: IRM 1.53.1, Managing Organizational Change.

  4. ) For additional information on the SB/SE S-ROC procedures refer to: http://mysbse.web.irs.gov/SBSENews/6619.aspx.

11.53.3.3.8  (09-23-2008)
Training

  1. OS is responsible for developing, coordinating, and monitoring the CLD Training Plan.

  2. CLD’s Training Program ensures "just-in-time" training needs are met by the employees of the CLD Organization.

  3. The Director, Planning and Strategic Planning (PSP) has responsibility for oversight, development, and delivery of the CLD Training Program along with the Director of Learning and Education.

  4. The Director PSP :

    1. Works in partnership with Learning and Education.

    2. Provides oversight and involvement with Learning & Education in development and delivery of CLD Training to ensure employees have the skills and knowledge so they are effective in their positions.

    3. Provides recommendations to the Director, CLD and CLD functional directors for needed training activities.

    4. Communicates with other CLD Executives to ensure information is shared and received in a timely manner.

  5. Servicewide Learning and Education:

    1. Works in partnership with the CLD PSP Director and the OS Training Analyst.

    2. Provides recommendations to ensure "just-in-time" training is delivered in the most effective and efficient manner.

    3. Formulates the budget for CLD Training development and delivery.

  6. Two major segments share the mission and values of Servicewide Learning and Education:

    • Embedded SB/SE Learning and Education

    • Corporate SB/SE SMART Human Capital Office Leadership, Education & Delivery Services (LEADS)

  7. SB/SE Learning and Education has primary responsibility to:

    1. Design courses and develop program instructional materials.

    2. Measure the educational effectiveness of programs.

    3. Formulates, monitors, and approves training plans, training related expenditures, and training budgets.

  8. SB/SE SMART Human Capital Office Leadership, Education & Delivery Services (LEADS) has primary responsibility to:

    1. Conduct national training programs when needed

    2. Provide CLD leadership information on best methods of training delivery.

    3. Coordinate all aspects of technical, cross functional and leadership training delivery.

    4. Evaluate instructor effectiveness and supports embedded L&E to evaluate overall program effectiveness.

    5. Provide training administrative support and manage Enterprise Learning Management System (ELMS).

  9. The Operations Support Training Analyst :

    1. Coordinates and oversees the development of the CLD training plan.

    2. Monitors the approved training plan.

    3. Serves as a conduit for problems.

    4. Provides a comprehensive list of available training classes that match the skill needs of all CLD positions.

11.53.3.3.8.1  (10-01-2006)
Out-Service Training

  1. The CLD Training Program includes requests for out-service training classes and sessions. If out-service training is needed, the request must meet the criteria below:

    1. Submit the request for out-service training to the CLD Training Analyst at least 30 days prior to the start of the class or session.

    2. The CLD Training Analyst is the point of contact for the out-service training request process.

    3. All management levels must approve the request prior to submission for consideration.

11.53.3.3.8.2  (09-23-2008)
Out-Service Approval Process – Completing the SF 182

  1. Standard Form SF 182, Request, Authorization, Agreement and Certification of Training is used to start the out-service training request/approval process. Provide specific information when completing the four sections on the form. Additional guidance in completing these sections is provided below.

    Note:

    Do not register for class until the SF 182 and RTS Request is approved.

  2. A copy of the SF 182 is available at: http://publish.no.irs.gov/othergov/pdf/10411L79.PDF.

    • Heading Box B (OFFICE USE ONLY) -The RTS number is inserted by the Secretary/Management Assistant preparing the RTS request

  3. Section A – Trainee Information:

    • Employee completes training information section

      Note:

      The SEID is used in lieu of the Social Security Number.

  4. Section B – Training course Information

    • Line 15a - Enter name and address of training vendor

    • Line 16 - Enter course title and training objectives

    • Line 17 - Enter the appropriate catalog/course number


    Catalog/Course Number for CLD Functional Areas:

    Course Number For CLD Functional Area
    5699a Directors Staff
    5699c Communications
    5699s Safeguards
    5699x Policy and Strategic Planning
    5699y Stakeholder Liaison HQ and Field
    2799g Governmental Liaison and Disclosure

    • Line 18a and b - Enter start and completion date of training

    • Line 19a and b - Enter number of course hours

  5. Section C - Estimated Costs – Enter the cost projections for the Out Service Training.

    • Line 21a and d.- Enter the Tuition amount for the Out Service training

    • Line 22a and d.- Enter the projected Travel costs related to the training

  6. Section D - Approvals

    • Line 26a.- Enter Name, title and phone number of the employees manager

    • Line 26b - Employees manager signs approving training. Next level manager initials next to immediate managers signature

    • Line 27a.- Enter Name and Title, "Director PSP"

    • Line 28a.- Enter Name and Title, "Director, Learning and Education HQ"

  7. Section E - Approval/Concurrence

    • Line 29a.- Enter Name and Title "Finance, Plan Manager"

  8. Approval - Other

    • Secretary/Management Assistant initiates the request with the approval path (see Section D above) and forwards to the CLD Training Analyst electronically or via fax

    • The CLD Training Analyst reviews and validates the request for training

    • The Director PSP approves and signs the SF 182 and RTS (Line 27a)

    • CLD Training Analyst sends the SF 182 to Learning and Education (L&E) point of contact for approval

    • L&E point of contact checks the training plan to validate request for training

    • L&E point of contact approves SF 182 and RTS, and forwards the request to Finance, for final approval

    • L&E returns approved SF 182 to CLD Training Analyst

    • CLD Training Analyst returns approved SF 182 to originator

    • Employee may then register for class

  9. Section F - Certification of Training Completion

    • Line 30a and b - After training is completed, employees manager signs to certify training completion

    • Certified SF 182 is forwarded electronically or via fax to the CLD Training Analyst

11.53.3.3.8.3  (09-23-2008)
Guidance for completing the RTS Request

  1. All SF 182s must have an RTS request initiated. The following is Guidance for completing the RTS Request and must contain the following:

    • OCN Field - Use the IRS catalog/course numbers for the CLD functional Areas. See SF 182 Section B See IRM 11.53.3.3.8.2. (4), Policy and Strategic Planning

    • Action Type - MISCF Miscellaneous Funds Will Not Go To Procurement

    • Date Needed - Indicate the last day of the out service training session

    • Requested Amount - Only the amount of the tuition is listed. Do not include travel estimates on the RTS Request

    • ITEMS Section - List the employees name, course title, dates, and justification for training

    • Approval Path - Use the following approval path on the RTS Request:
      1. Originator’s Name
      2. Employee’s Manager
      3. Director PSP
      4. L&E Finance Point of Contact
      5. Finance Plan Manager

11.53.3.3.9  (10-01-2006)
Employee Engagement

  1. Operations Support has responsibility to

    1. Develop and lead the implementation of the CLD Employee Engagement program.

    2. Coordinate Employee Engagement issues for the CLD organization.

    3. Review and analyze survey results at the CLD organizational level.

    4. Serve as CLD survey coordinator/representative to SB/SE engagement effort.

    5. Assist in the administration for the Employee Engagement process within SB/SE.

    6. Use the Engagement Strategy (ES) tracker database to monitor and track issues raised during employee engagement efforts.

    7. Perform other duties necessary to administer the program.

  2. To accomplish these responsibilities, Operations Support receives guidance and support from SB/SE SMART Human Capital Office on the following:

    • Organizational Verification

    • Survey Administration

    • Survey Analysis

    • Communications

  3. Both Operations Support and SB/SE SMART Human Capital Office coordinate efforts to meet the employee engagement needs of the CLD organization. For additional information on the employee satisfaction program, refer to the CLD and SB/SE websites.

11.53.3.3.10  (09-23-2008)
Space

  1. Operations Support has responsibility to:

    • Monitor space availability

    • Ensure all CLD employees have appropriate workstations

    • Ensure the work environment is safe and promotes productivity

    • Coordinate with Agency Wide Shared Services (AWSS), Management & Support for expansion needs

  2. To accomplish these responsibilities, Operations Support receives guidance from SB/SE SMART Human Capital Office, Work Space Management (WSM) and AWSS on the following:

    • Space standards

    • Customer Funded Project request

    • Rent Containment initiatives

    • Build-out and re-stacking

    • Locations for hiring

    • Authorize space allocations

  3. For additional information, refer to the AWSS - Real Estate and Facilities Management website for guidelines on space management at: http://awss.web.irs.gov/Facilities/RealEstate/Real-Prop-Mgmt.html.

11.53.3.3.11  (09-23-2008)
Risk Management Group and SB/SE Governance Reporting Procedures for CLD Information Technology (IT) Projects

  1. The Risk Management Group (RMG) and the SB/SE Governance Reporting Procedures provide guidelines for the establishment and operation of all SB/SE Information Technology Projects (IT) and Operational Improvement Workstreams (OIW). It sets forth the objectives, scope, organization, responsibilities, and general methods of operation. OS coordinates this process for CLD.

  2. The objectives of CLD's reporting procedures are as follows:

    1. The primary objective of the CLD’s reporting procedures are to comply with the two standardized methods of first level governance which were established for the SB/SE organization. The first method is the Business Systems Planning (BSP) Project Management Discipline/Risk Management Group (PMD/RMG), and the second method is the Internal Operating Unit (OU) Governance process.

    2. Either the BSP PMD/RMG or the Internal OU Governance process constitutes the first level of a two-tiered SB/SE Project Management infrastructure. CLD’s IT Projects are not currently sponsored by the BSP PMD/RMG, therefore, the second level of the infrastructure method is used to report the monthly status updates of each CLD IT project to the SB/SE Project Management Dash Board.

  3. The scope of CLD’s reporting procedures for the Internal OU Governance process are to:

    1. Foster and engage the necessary involvement of the OU representative, project managers, senior managers, and executives in strategic projects.

    2. Monitor progress of projects within Communications & Liaison and provide recommendations for continued improvement.

    3. Resolve issues which cross functional lines (i.e. MITS, AWSS, NTEU, etc.).

    4. Provide oversight and policy guidance to assure project success.

    5. Ensure accurate project status reporting via the monthly BSP dashboard report.

    6. Provide the CLD Director with monthly status reports for all CLD IT Projects.

  4. Presently, all CLD’s projects and other major efforts are governed under the Internal OU Governance structure. The general guidelines for assigning a project to this method of governance is as follows:

    • Smaller projects

    • Lower visibility efforts

    • Re-engineering projects in the design phase

      Note:

      Other key projects are governed under the Internal OU Governance process.

  5. When CLD has a need to consult with BSP to ascertain the required support for new project(s), the OU Representatives and the BSP staff will work jointly to determine which projects/efforts go to which process. Projects under the BSP PMD/RMG:

    • All Tier B projects

    • Re-engineering projects in the implementation phase

    • Selected improvement projects

    • Other high profile/high risk projects

  6. Responsibilities of the CLD Project Management Coordinator:

    1. Provides the OU Director with information on the status of CLD’s IT Projects during a monthly "one-on-one" discussion.

    2. Provides the OU Director with a high level "White Paper" update status regarding all IT Projects when an in person meeting is not held.

    3. Provides a forum for projects under internal OU governance to raise their risks/issues.

    4. Provides guidance and direction to Project Managers who need Business decisions supported to keep their projects moving.

    5. Works with the OU Director to establish process improvement for the Internal Process.

  7. For additional information and details, visit: http://sbse.web.irs.gov/BSP/BSPProjectManagement.htm.

11.53.3.3.12  (09-23-2008)
Information Technology (IT) and Equipment

  1. Operations Support is responsible to:

    • Monitor and update the CLD IT & Office Equipment Portfolio

    • Ensure all CLD employees are provided with authorized IT & Office Equipment

    • Ensure all IT software components are provided to CLD employees

    • Coordinate with MITS & SB/SE BSP for expansion of equipment needs, when justifications are necessary

  2. To accomplish these responsibilities, Operations Support receives guidance from the MITS Organization, SB/SE BSP Operating Unit, and SB/SE Workplace Management (WPM) on the following:

    • IT & Office Equipment Replacements

    • Customer funded project requests

    • Office equipment

    • Computer security requirements

    • Computer software upgrade requirements

    • Get-It Ticket procedures and authorizations

11.53.3.3.13  (09-23-2008)
Work Request Tracking System (WRTS)

  1. The WRTS is an on-line tracking system, which requires the use of a Work Request (WR) to submit requests for services from Demand Management and the Technical Supplier functions of the MITS organization.

  2. There are certain requirements which are mandated by Demand Management, which require all users to complete a Form 5081 and complete certain training modules before they are given access to the WRTS.

  3. Form 5081 submission - Before all users take the training, they must submit, an on-line, Form 5081 request for permission to access the application. Select the Work Request Tracking System (WRTS) component from the "System Menu’s" when initiating the Form 5081 request. Once the request is approved by the user’s manager, Demand Management, will add the employee name and BOD to the WRTS’s Database. The employee can then begin the training

  4. Training Requirements -

    1. 1st Module - ELMS Based Training, login to ELMS and select the course number listed below:
      • UWR Process Overview (ELMS Course # 19036)
      • Mandatory for all WRTS users - must complete prior to having access to WRTS

      Note:

      Go to the WRTS Homepage at:
      http://wrts.web.irs.gov/ and Click on "Training" .

    2. 2nd Module - Web Based Tutorial (WBT) Training:
      • WRTS 1.0 Overview Module
      • WRTS 1.0 General Functionality Module
      • WRTS 1.0 Work Request Submission
      • WRTS 1.0 Work Request Response

      Note:

      No classroom training is required. All WBT will have ELMS Course Numbers. The user must complete all training requirements before being granted access to the system. Once the user has completed the training, the system will generate a message: "You have Completed the training" and prompt the user to log on to the WRTS to create or change their WRTS passwords.

  5. Simplified WR Process Illustration Flow Chart

    CUSTOMER INITIATION OF WORK REQUEST
    Initiate unlogged Work Request
    I
    Coordinate request with MITS supplier and other stakeholders (other impacted areas)
    I
    Complete internal (requestor's) doc clearance process
    I
    Approval by Primary Requestor's approving official
    (The UWR is considered logged at this point)
  6. Service-type WR for a major procurement, minor system change, or major system redesign and programming should include a general description of the overall system concept. The WR description should:

    • Identify the concept of what is being requested

    • Identify the host supplier who will provide the services requested

    • Identify primary system and secondary system sources

    • Identify response times

    • Identify the timetable for implementation

    • Describe Input/Output formats

    • Define record layouts - for reports, etc.

    • Define requirement for internal IT support (IRS) or external IT support (Contractor)

    • Provide the functionality desired for processing capabilities

    • Provide general information in accordance with the requirements of the on-line WR input

  7. Responsibilities of the WR Originator, WR Reviewer, and WR Coordinator

    1. WR Originator : The individual who creates the un-logged WR in WRTS on behalf of the Primary Requestor Contact. Individual may also be the Primary Requestor Contact.

    2. WR Reviewer : Any individual or organization asked to comment or concur with a WR during the Coordination or Approval phases of the WR Submission process.

    3. CLD WR Coordinator : The CLD WR Coordinator serves in the same capacity as the coordinator listed above. All Work Request are routed to the WR Coordinator for approval after all coordination, reviews, and concurrence is completed by the CLD Work Requestor, CLD management, and the MITS Technical suppliers. In some instances, the WR Coordinator will act as the Proxy.

  8. In essence, the WRTS is a centralized system which requires the on-line working of the Work Request (WR) submissions, through collaboration and coordination between the Requestor (the CLD organization), and (the Supplier/Programmers, MITS).

  9. Visit the WRTS website for addition additional information and guidance at: http://wrts.web.irs.gov/.

11.53.3.3.14  (10-01-2006)
Office of Government Ethics - OGE 450, Confidential Financial Disclosure Report

  1. The Office of Government Ethics (OGE) Program is a safeguard for employees as well as the government. It provides a mechanism for determining actual or potential conflicts between the employees’ public responsibilities and their private interests and activities. This allows the employee and the agency to fashion appropriate protections against such conflicts.

  2. Operations Support is responsible to:

    • Serve as the OGE coordinator for Communications, Liaison and Disclosure

    • Identify positions required to file OGE 450, Confidential Financial Disclosure Report

    • Prepare monthly activity reports

      Note:

      These reports include:
      1 - New Filers Report
      2 - Deletion Report
      3.- Change Report
      4 - No Change Report

    • Prepare the Annual Master Filer Listing

    • Inform employees of their requirement to file

    • Ensure filers complete the annual Ethics training

    • Provide guidance on completing required documents

  3. Communications, Liaison and Disclosure positions required to file OGE Form 450:

    • Director, Communications

    • Chief, Web Services

    • Web Master under Chief, Web Services

    • Director, Governmental Liaison and Disclosure

    • Chief, Data Services

    • Director, Policy and Strategic Planning

    • Director, Stakeholder Liaison Headquarters

    • Director, Stakeholder Liaison Field

  4. To accomplish these responsibilities, Operations Support receives guidance and support from SB/SE SMART Human Capitol Office. For additional information on the OGE 450 Program, please refer to the Ethics Web site at: http://counsel.web.irs.gov/ethicsLink/.

11.53.3.3.15  (09-23-2008)
Publishing Services Request (PSR) Instructions for CLD Disclosure Offices Requesting Bulk Copying Contracts

  1. OS provides support to the CLD functions when making requests for establishing copying contracts or for copying services that are submitted to Publishing Services, W&I, by using the electronic Publishing Services Request (PSR) application.

  2. Permissions and a password are required to access the PSR application at: http://publish.no.irs.gov/servc.html by clicking on the PSR link (2nd paragraph). The automated PSR form is an automated form, which is used to obtain the funding approvals, and route the request to Publishing for processing.

  3. Requirements:

    1. A designated Disclosure Manager/Management representative is selected to act as the Point of Contact (POC) for the contract.

    2. The designated POC is required to complete and submit the attached automated PSR Form listed above.

  4. Publishing Service Request Instructions:

    1. At PSR Main Screen: Select NEW

    2. At Operating Division: Select SB/SE

    3. At Product Type: Select OTHER

    4. At Product Title: Select "Copying Contract for Disclosure FOIA Copying Services"

    5. At Product Description: Enter the coordinators name, i.e. "for Rose Wong" , to establish a GPO contract for copying services to fulfill FOIA requests, and list the POD(s) with contact names and phone numbers for each POD

    6. At Requested Delivery Date: Select the date needed (allow at least two to three months turnaround)

    7. At Approving Official: Select the approving official for your business unit or organization *

    8. At Funding Approval: Select Gwendolyn Taylor (current approver)

    9. Click "CREATE" to submit the request

  5. Requestor

    1. Upon receipt of the PSR request, the PSR Analysts will prepare and submit the necessary paperwork to the Government Printing Office (GPO) for establishing the copying contract.

    2. GPO will contract and solicit for vendors.

    3. The requesting office is required to conduct a pre-award on-site safeguard & security review of the prospective vendor's facility and staff (Ref: IRM 1.16.3, Physical Security Standards - Safeguard Reviews).,

      Note:

      According to IRM 1.23.2, Contractor Investigations, background investigations of prospective vendor's employees may also be required in addition to the pre-award on-site safeguard/security review.

    4. The cost of the investigation is paid by the requesting office.

    5. IRM 1.16.3, Safeguard Review and IRM 1.23.2, Contractor Investigations contain additional information.


    * An authorized approving official must sign Form 1767. If you cannot locate an approving official for your Area, the Publishing Services Requisition Authorized Signatures link is at: http://publish.no.irs.gov/authsig.html. Instructions on adding, deleting, or changing authorized officials are listed under the section titled Delegation of Authority.

11.53.3.4  (10-01-2006)
GAO, TIGTA, Legislative Implementation (SB/SE)

  1. Although this office is part of Policy and Strategic Planning (PSP) and the Chief, GAO/TIGTA/Legislative Implementation reports to the Director, Policy and Strategic Planning, the procedures used by this office are contained in IRM 11.53.4,Small Business/ Self-Employed - GAO/TIGTA/Legislative Implementation.


More Internal Revenue Manual