- 25.8.1.1 OFP Code Overview
- 25.8.1.2 Revisions
- 25.8.1.3 Approval Authority for Reorganization
- 25.8.1.4 OFP Consistency File
- 25.8.1.5 Required Security and Ethics Statements
- 25.8.1.6 Organization Codes
- 25.8.1.7 Function Codes
- 25.8.1.8 Program Codes
- Exhibit 25.8.1-1 Index to Organization Codes
- Exhibit 25.8.1-2 Index Function Codes
- Exhibit 25.8.1-3 Index of Programs Codes
- Exhibit 25.8.1-4 Special and Reimbursement Project Codes
- Exhibit 25.8.1-5 Reimbursable Projects
- Exhibit 25.8.1-6 Data Processing Support for Compliance Operation and Criminal Investigation Local Projects
-
The codes listed in this IRM are for use with Integrated Management Planning Information System (IMPIS) as is outlined in IRM 25.14, Integrated Management Planning Information System. Work Planning & Control (WP&C) Organization, Function and Program (OFP) codes are recorded on Forms 3081 Employee Time Report to identify work that Internal Revenue Service employees perform daily. This IRM provides a list of valid organizations, functions and programs.
-
Work Planning & Control System OFP codes are used in preparation of the Business Operating Divisions Work Plans/Work Schedules. This data shows historic staff-hour and volume usage. Because of the many uses for this data it is imperative that reporting be as accurate, consistent and error free as possible. Other uses for OFP data are:
-
Source data for numerous Management Information Systems
-
Employee Performance Evaluations
-
Balanced Measures
-
IRM 3.30.10 Cost Estimate Reference
-
Reports to Congress
-
Resource & Inventory Monitoring
-
Agency Wide Shared Services & Strategic Human Resources Measures System
-
-
IRM 1.1.4 Organization and Staffing - Organizational Planning describes detailed approval authority. IRM 1.1.4 must be referred to when a change to an existing or creation of a new organization is proposed. No revision will be made to this IRM or 5995A database, valid OFP combinations, located via the OFP Home Page web link http://ofp.web.irs.gov, that conflicts with IRM 1.1.4, Organization and Staffing - Organizational Planning.
-
Revisions to this IRM will be issued once each year. The 5995A database that contains detailed exhibits of the valid OFP combinations is continuously updated. No revision to this IRM or the OFP coding structure will be made without first having been approved by the owners of the OFP and WP&C systems.
-
Business Operating Division program analysts/areas are responsible for originating requests for new OFPs and providing input to this IRM and 5995A database in the proper format via the OFP Home Page web link: http://ofp.web.irs.gov . All OFP related questions should be directed to the OFP/WP&C administrators at Joint Operations Center. However, specific program related questions should be directed to the appropriate program area analyst at the Business Operating Division. Campus personnel requesting codes that are not valid are responsible for initiating and maintaining contact with relevant Business Operating Division program areas.
-
Program areas are responsible for providing documentation to the Joint Operations Center OFP administrator. All necessary input to revisions or changes to Exhibits should be requested through and provided to the Joint Operations Center OFP administrator by the Business Operating Division program areas.
-
Types of requests from field offices that must be directed to the Business Operating Division program analyst/area include, but are not limited to:
-
Editing or changing Exhibit information
-
Requesting a new program code
-
Requesting an existing function-program code combination be made valid for reporting in a different Operation/Campus
-
-
Each field office/campus has one or more OFP Coordinators that are responsible for all general OFP related issues for that site. Any OFP requests should be coordinated with the OFP Coordinator at the appropriate campus. A list of campus OFP Coordinators and their numbers may be obtained from the Joint Operations Center OFP administrator.
-
Requests for changing the existing Work Planning and Control System (WP&C) organization code structure, or proposals at the Operation level and above for the assignment of new organization codes, including, but not limited to, eliminating, adding or redistributing the functions or duties of an organization for field offices/campuses or Agency Wide Shared Services must be submitted in writing simultaneously to Strategic Planning Division, the CFO, and the OFP administrator as outlined in IRM 1.1.4.
-
The field offices/campuses are not authorized and do not have the capability to establish, change or edit parent organization, function and program codes on their OFP Consistency File. All changes of this nature must be submitted to the Joint Operations Center OFP administrator via http://ofp.web.irs.gov/5948.asp , OFP Consistency File Input form.
-
Detailed procedures for preparing Form 5948 are outlined in IRM 3.30.50, Performance Evaluation Reporting System (PERS) see IRM 3.30.50.3.3 . Each field must be completed. This form is available in every field office/campus and usually prepared by the Reports Unit or the OFP Coordinator. Incomplete forms will not be processed.
-
Codes that are not authorized by this manual and 5995A database http://ofp.web.irs.gov/5995a.asp are not to be used in IMPIS and will not be added to the OFP Consistency File.
-
Field offices/campuses are authorized and have the capability at their option, to assign third, fourth and fifth digits of the organization codes, third digits of the function codes and fifth digits of the program codes. These third, fourth and fifth digit codes must have a valid parent combination. These can be added to their OFP Consistency File at the campus.
Exception:
There are exceptions to this rule in cases where the Business Operating Division program area has mandated specific use of third and fifth digits (e.g., for use within SETR).
-
Procedures to request individual codes:
-
To add or change an individual Organization Code, follow IRM 1.1.4 reorganization guidelines. Once a reorganization request is approved by the appropriate approving official, request(s) can be submitted to the Joint Operations Center OFP administrator for assignment of, or changes to, organization codes.
-
To add an individual function code, or an individual permanent program code, submit Form 13242, Organization Function and Program List via http://ofp.web.irs.gov/app/13242request.asp . Justification for each proposed new code must be given which will include (1) an explanation of why the tasks of the new code cannot be reported under an already existing code (2) an explanation of how the results will be used (3) estimate of the expected yearly volume and staff hour usage, (4) beginning and ending (if temporary) dates, and (5) source of funding when applicable. Codes will not be issued if fewer than 2000 staff hours per year are anticipated Nationwide.
-
Each Form 13242 request will include the proposed implementation date, point of contact, as well as the organizations in which the work will be performed and the field offices/campuses that are to perform the work.
Note:
Prior coordination with work plans and work schedule teams at Business Operating Division is critical and must be completed before an OFP Code assignment will be made.
-
-
The Joint Operations Center OFP Administrator will initiate an E-mail of approval upon receipt of a specific program code request (see procedures above). The Business Operating Division's program areas, in turn, must be responsible for notifying the field of the new code combination(s) approved by the OFP administrator.
-
To add a non-reimbursable Special Project Program Code (80000 series), proceed as in 25.8.1.4.1(1) b and c above. In addition, if the code is needed for a test project, documentation of proper authorization and background must be included in request.
-
To add a reimbursable project Special Program Code, proceed as in 25.8.1.4.1(1) b and c above. Include a copy of the signed Form 5181, Agreement Covering Reimbursable Services, or Memo of Understanding (MOU). Include duration, point of contact and type of special or reimbursable program code. The special and reimbursable program code are listed in Exhibits 25.8.1.4 and 25.8.1.5.
-
Field office/campus directors, must direct their OFP request to the appropriate Business Operating Division program area responsible for preparing a request on their behalf to the Joint Operations Center OFP Administrator.
-
To delete any of the codes mentioned above from this IRM and 5995A database, update Form 13242/13242A, Organization Function and Program Code, via the OFP Home Page web link: http://ofp.web.irs.gov. Include the proposed deletion date. If work is being reassigned to another program, specify program. Inform the impacted Business Operating Division or Field Office/Campus and work plan/work schedule teams.
-
To add an OFP submit Form 13242, http://ofp.web.irs.gov/app/13242request.asp or Form 13242A. http://ofp.web.irs.gov/app/13242arequest.asp via the web link to the 5995A database, See IRM 25.8.1.4.1 above. To authorize reporting to an existing function/program code combination in a different organization submit an updated Form 13242 or 13242A via the OFP Home Page web link. New and revised Form 13242 and 13242A will be published to the 5995A database immediately upon approval by Joint Operations Center.
-
To edit, change, or delete an OFP page Form 13242 or Form 13242A, submit an updated Form 13242 or 13242A via the OFP Home Page web link with the proposed action along with the expected implementation and/or deletion date.
-
In the event that an OFP is obsolete or a task is removed from an OFP, resulting in work being transferred to another OFP, an audit trail of such transfer will be included in the justification of the Form 13242 or Form 13242A request. If the proposed change appears significant, obtain comments regarding field impact from the Campus Directors. Include these statements with the request. Send a copy of this information to impacted field offices for their information.
-
Once an OFP Code becomes obsolete, removal of the corresponding page in the exhibit by the responsible Business Operating Division program area must be initiated immediately. Simultaneous notification should be given to the impacted Business Operating Division program areas so that the field offices/campuses will no longer use the code.
-
Business Operating Division program analysts are responsible for providing all of the above mentioned information in the proper format to the Joint Operations Center OFP Program Administrator via the OFP Home Page web link: http://ofp.web.irs.gov .
-
Form 13242 is required for general codes with the above specified justification memorandum. Form 13242A is required for Special Project Codes in the 8XXXX and 9700099990 series with the above specified justification memorandum.
-
In the event that a task is moved to or removed from an OFP, OFP pages to which this work is transferred or deleted must be updated accordingly.
-
Such general terms as documents, forms, returns, etc., are to be avoided. Instead indicate, by listing if necessary, precisely which items are involved.
-
In the event that a task is removed from an OFP, either because that OFP is discontinued or for other reasons, the OFP page to which this work is transferred must be updated accordingly.
-
Organization Titles, Function Titles and Program Titles must conform exactly to their counterparts in Exhibits 25.8.11, 25.8.12 and 25.8.13. Organization Codes will no longer be referenced as 3X000 as in past revisions. The Organization Code should contain specific numerics, (e.g. 35000) and titles.
-
The point of count is that step in the process at which the work is counted released (or completed or resolved, etc.). This entry must be clearly stated to preclude duplicate counts or conflicts with "What is Counted" , "How Counted" , or "Where Counted" .
-
The work unit is the type of form, document, case, etc., that is being worked upon.
-
What is counted is that document, module, transcript, etc., that is to be counted as one. This entry must be definitive to avoid inconsistent reporting among the campuses.
-
This entry relates to the method and/or sources to be used in performing the count (from cards, registers, actual item/document count, etc.).
-
Where counted involves the location at which the count is to be performed. This entry is not to state when the count is performed.
-
Insert the number of the Handbook, IRM, etc., of publications that relate to (or authorize) the task.
-
This section must contain a thorough description of all major operations that are to be performed. If the program area wants sites to use the fifth digit of the program code to describe a certain aspect of the parent code consistently, prescribe the breakdown in this section.
-
Tasks performed, as shown in the "Major Operations" portion of an exhibit page, must be charged only to the function/program code combination shown at the top portion of that page and to the specific organization code shown at the bottom portion of that page. This requirement is necessary in order to promote uniform reporting.
-
Deviations from this rule are permissible in special cases (such as differences in facilities, equipment, etc.) Requests for such deviations must be made in writing by memorandum to the National Director, Joint Operations Center and coordinated with the appropriate Business Operating Division program area(s). They will be considered on a case by case basis and approval (or disapproval) will be transmitted in writing.
-
Service officials and managers must communicate security standards contained in IRM 1.4.6, Managers Security Handbook, to subordinate employees and establish methods to enforce them. Employees are responsible for taking required precautions in providing security for the documents, information, and property which they handle in performing official duties.
-
Employees who have access to and work with returns processing information and data in connection with this IRM must not alter the data, disclose information to persons without a need to know such information, use data for unauthorized purposes, or make unauthorized access to the data.
-
The organization codes listed in IRM 25.8.14 represent the valid organization codes to be used by sites. Each code has an abbreviated title and a title displayed. The abbreviation is used as the literal on the OFP Consistency File. The Functional Area (FA) identifies a financial and functional category for the Services programs. FAs are primarily used for internal management purposes and also during the Financial Plan formulation and execution.
-
An organization code is a five digit code and is used to describe where the work is being performed, e.g., Document Perfection, Accounts Management, etc. In Submission Processing and Compliance, the first and second digit identifies the Operation, the third digit identifies the Department, the fourth and fifth digit identifies the Team. In Accounts Management, first and second digit identifies the Operation and Department, the third and fourth digit identifies the Team.
-
The function codes listed in Exhibit 25.8.12 represent valid function codes to be used by sites. Each code has an abbreviated title and a title displayed. The abbreviation is used as the literal on the OFP Consistency File. The codes are for use in combination with valid organization and program codes. A function code is a three digit code that is used to describe "what" is being done, e.g., ISRP, Code & Edit, Batching, etc. or who is working that related program, e.g., Revenue Agent, TCO, etc. The third digit of the function code is sometimes used as a sub-function at the sites discretion to describe different aspects of the parent function. Sub-functions that are mandatory are described in Exhibit 25.8.12.
-
The program codes listed in Exhibit 25.8.13 represent valid program codes to be used by sites. Each code has an abbreviated title and a title displayed. The abbreviation is used as the literal on the OFP Consistency File. The codes are for use in combination with valid organization and function codes. A program code is a five digit code that is used to describe the "program" being worked, e.g., IMF, BMF, 1040, etc. The fifth digit of the program code is sometimes used as a sub-program at the sites discretion to identify different aspects of the parent program. The use of the fifth digit can be mandated by Business Operating Division program areas when necessary, e.g., SETR codes, Customer Service programs, etc. All program related OFP code questions should be directed to the program area at the Business Operating Division.
| Org. Code | Title | Abbrev. | FA | Site |
|---|---|---|---|---|
| 11000 | National Distribution Center | NDC | 1W | KCSC |
| 12000 | Statistics of Income Operation | SOI OP | 4Q | CSC |
| 12000 | Statistics of Income Operation | SOI OP | 4Q | OSC |
| 13000 | Taxpayer Advocate Service | ADVOCATE | 1M | KCSC |
| 16000 | Chief Financial Officer | CFO | 4A | ANSC |
| 16000 | Chief Financial Officer | CFO | 4A | BSC |
| 16000 | Chief Financial Officer | CFO | 4A | AUSC |
| 16000 | Chief Financial Officer | CFO | 4A | KCSC |
| 16000 | Chief Financial Officer | CFO | 4A | PSC |
| 17000 | Learning & Education | L&E | 1A | AUSC |
| 1A000 | Correspondence Production Services | CPS | 1D | OSC |
| 1B000 | Electronic Tax Administration | ETA | 2F | MSC |
| 1C000 | Electronic Products & Services Support (East) | EPSS E | 2A | ANSC |
| 1C000 | Electronic Products & Services Support (West) | EPSS W | 2A | AUSC |
| 1D000 | Fraud Detection Center/Criminal Investigation | FRADETCN | 5H | ANSC |
| 1D000 | Fraud Detection Center/Criminal Investigation | FRADETCN | 5H | ATSC |
| 1D000 | Fraud Detection Center/Criminal Investigation | FRADETCN | 5H | AUSC |
| 1D000 | Fraud Detection Center/Criminal Investigation | FRADETCN | 5H | BSC |
| 1D000 | Fraud Detection Center/Criminal Investigation | FRADETCN | 5H | CSC |
| 1D000 | Fraud Detection Center/Criminal Investigation | FRADETCN | 5H | FSC |
| 1D000 | Fraud Detection Center/Criminal Investigation | FRADETCN | 5H | KCSC |
| 1D000 | Fraud Detection Center/Criminal Investigation | FRADETCN | 5H | MSC |
| 1D000 | Fraud Detection Center/Criminal Investigation | FRADETCN | 5H | OSC |
| 1D000 | Fraud Detection Center/Criminal Investigation | FRADETCN | 5H | PSC |
| 20000 | Director Submission Processing | SPDRCTR | 2B* | ANSC |
| 20000 | Director Submission Processing | SPDRCTR | 2B* | ATSC |
| 20000 | Director Submission Processing | SPDRCTR | 2B* | AUSC |
| 20000 | Director Submission Processing | SPDRCTR | 2B* | FSC |
| 20000 | Director Submission Processing | SPDRCTR | 2B* | KCSC |
| 20000 | Director Submission Processing | SPDRCTR | 2B* | CSC |
| 20000 | Director Submission Processing | SPDRCTR | 2B* | OSC |
| 23000 | Planning & Analysis Staff | PASTAFF | 2B* | ANSC |
| 23000 | Planning & Analysis Staff | PASTAFF | 2B* | ATSC |
| 23000 | Planning & Analysis Staff | PASTAFF | 2B* | AUSC |
| 23000 | Planning & Analysis Staff | PASTAFF | 2B* | FSC |
| 23000 | Planning & Analysis Staff | PASTAFF | 2B* | KCSC |
| 23000 | Planning & Analysis Staff | PASTAFF | 2B* | CSC |
| 23000 | Planning & Analysis Staff | PASTAFF | 2B* | OSC |
| 24000 | Site Coordinator Staff | COORDNTR | 2B* | ANSC |
| 24000 | Site Coordinator Staff | COORDNTR | 2B* | ATSC |
| 24000 | Site Coordinator Staff | COORDNTR | 2B* | AUSC |
| 24000 | Site Coordinator Staff | COORDNTR | 2B* | FSC |
| 24000 | Site Coordinator Staff | COORDNTR | 2B* | KCSC |
| 24000 | Site Coordinator Staff | COORDNTR | 2B* | CSC |
| 24000 | Site Coordinator Staff | COORDNTR | 2B* | OSC |
| 31000 | Receipt and Control Operation | RECCONOP | 2B* | ANSC |
| 31000 | Receipt and Control Operation | RECCONOP | 2B* | ATSC |
| 31000 | Receipt and Control Operation | RECCONOP | 2B* | AUSC |
| 31000 | Receipt and Control Operation | RECCONOP | 2B* | FSC |
| 31000 | Receipt and Control Operation | RECCONOP | 2B* | KCSC |
| 31000 | Receipt and Control Operation | RECCONOP | 2B* | CSC |
| 31000 | Receipt and Control Operation | RECCONOP | 2B* | OSC |
| 32000 | ITIN Operation | ITINOP | 2B* | AUSC |
| 34000 | Document Perfection Operation | DOCPRFOP | 2B* | ANSC |
| 34000 | Document Perfection Operation | DOCPRFOP | 2B* | ATSC |
| 34000 | Document Perfection Operation | DOCPRFOP | 2B* | AUSC |
| 34000 | Document Perfection Operation | DOCPRFOP | 2B* | FSC |
| 34000 | Document Perfection Operation | DOCPRFOP | 2B* | KCSC |
| 34000 | Document Perfection Operation | DOCPRFOP | 2B* | CSC |
| 34000 | Document Perfection Operation | DOCPRFOP | 2B* | OSC |
| 35000 | Data Conversion Operation | DATCONOP | 2B* | ANSC |
| 35000 | Data Conversion Operation | DATCONOP | 2B* | ATSC |
| 35000 | Data Conversion Operation | DATCONOP | 2B* | AUSC |
| 35000 | Data Conversion Operation | DATCONOP | 2B* | FSC |
| 35000 | Data Conversion Operation | DATCONOP | 2B* | KCSC |
| 35000 | Data Conversion Operation | DATCONOP | 2B* | CSC |
| 35000 | Data Conversion Operation | DATCONOP | 2B* | OSC |
| 36000 | Input Correction Operation | INPCOROP | 2B* | ANSC |
| 36000 | Input Correction Operation | INPCOROP | 2B* | ATSC |
| 36000 | Input Correction Operation | INPCOROP | 2B* | AUSC |
| 36000 | Input Correction Operation | INPCOROP | 2B* | FSC |
| 36000 | Input Correction Operation | INPCOROP | 2B* | KCSC |
| 36000 | Input Correction Operation | INPCOROP | 2B* | CSC |
| 36000 | Input Correction Operation |







