- 25.14.1.1 IMPIS Overview
- 25.14.1.2 Work Planning and Control (WP&C)
- 25.14.1.3 Validation of Data
- 25.14.1.4 Tape and Report Shipments
- 25.14.1.5 Service Center Production Control
-
The following organizations utilize the Integrated Management Planning and Information System (IMPIS) for workload and resource reporting:
-
Wage & Investment Division (W&I) Customer Account Services (CAS) Campuses (Andover Campus (ANSC), Atlanta Campus (ATSC), Austin Campus (AUSC), Brookhaven Campus (BSC), Cincinnati Campus (CSC), Fresno Campus (FSC), Kansas City Campus (KCSC), Memphis Campus (MSC), Ogden Campus (OSC), Philadelphia Campus (PSC))
-
W&I Field Compliance Services Campuses (ANSC, ATSC, AUSC, FSC, KCSC)
-
Small Business/Self Employed (SB/SE) Field Compliance Services Campuses (BSC, CSC, MSC, OSC, PSC)
-
Chief Financial Office (CFO)
-
Taxpayer Advocate Service (TAS)
-
Human Capital Office (HCO)
-
Currency Transaction Reporting Operation
-
Payroll/Personnel Systems
-
Agency Wide Shared Services (AWSS) / Strategic Human Resources
-
Fraud Detection Centers
-
W&I Customer Assistance, Relationships & Education (CARE), Stakeholder Partnerships, Education and Communication (SPEC)
-
SB/SE Taxpayer Education and Communications Operation (TEC)
-
Learning & Education (L&E)
-
Correspondence Production Service (CPS)
-
Electronic Tax Administration and Refundable Credits (ETARC)
-
Electronic Products & Services Support (EPSS)
-
Modernization & Information Technology Services (MITS)
-
Stakeholder Liaison
-
National Distribution Center (NDC)
-
Statistics of Income Operation (SOI)
-
-
IMPIS provides methods and management tools for evaluation of the workload and resources for:
-
Planning
-
Scheduling
-
Controlling
-
Measuring
-
-
IMPIS allows management to view information for the organizations that utilize IMPIS in a common framework and simplifies the tasks of:
-
Developing and evaluating work plans,
-
Developing budgets,
-
Allocating staff-power
-
Determining status of workload and resources, and
-
Appraising performance.
-
-
The system encompasses separate component systems named:
-
Project Literal for Service Center Production Control (PCC)
-
Project Literal for Service Center Workload Scheduling (PCB)
-
Project Literal for Production and Control Accounting (PCA) / Performance Evaluation Reporting System (PERS)
-
Project Literal for Control Data Analysis (PCD)
-
Project Literal for Individual Review (PCE)
-
-
Each of these component systems are separate and have a different primary objective. However, there are certain elements of data in one system that directly relates to the other systems; therefore, the same information is used to satisfy the needs of all systems. This is done when it is practical and there is no danger of defeating the primary objective of each system.
-
Staff-hours reported for Individual Performance are used in Performance and Cost Reports.
-
Volumes used for certain Production Reports are also used for Performance and Cost Reports.
-
-
The following IRMs contain specific requirements and instructions for each of the component systems mentioned above:
-
IRM 3.30.28, Individual Review,
-
IRM 3.30.50, Performance Evaluation Reporting System,
-
IRM 3.30.126, Control Data Analysis,
-
IRM 3.30.127, Workload Scheduling, and
-
IRM 25.8.1, Organization, Function, Program (OFP) Codes Overview.
-
-
Below is a list of abbreviations and acronyms that will be referenced throughout the rest of this section:
Abbreviation / Acronym Definition ADP Automatic Data Processing Adj. Adjustment ANSC Andover Campus ATSC Atlanta Campus AUSC Austin Campus AWSS Agency Wide Shared Services BBTS Batch/Block Tracking System BMF Business Master File BMFOL Business Master File On-Line BOB Block Out of Balance BOD Business Operating Division BPC Batch and Production Control BPR Batch Profile Report BSC Brookhaven Campus CARE Customer Assistance, Relationship & Education CAS Customer Account Services CFO Chief Financial Office CPS Correspondence Production Service CSC Cincinnati Campus Cum Cumulative DCC Detroit Computing Center DLN Document Locator Number DPR Daily Production Report ECC Enterprise Computing Center EFF Efficiency Emp Employee EONS Electronic Output Network System EPSS Electronic Products & Services Support ETARC Electronic Tax Administration and Refundable Credits FSC Fresno Campus Func Function FY Fiscal Year GMF Generalized Mainline Framework HCO Human Capital Office Hrs Hours IDRS Integrated Data Retrieval System IFS Integrated Financial Systems IMF Individual Master File IMPIS Integrated Management and Planning Information System IP Individual Performance IPS Incentive Pay System ISRP Integrated Submission and Remittance Processing IRM Internal Revenue Manual KCSC Kansas City Campus KV Key Verification L&E Learning & Education MEM Memphis MF Master File MIS Management Information Systems MITS Modernization & Information Technology Services MSC Memphis Campus MTB Martinsburg NDC National Distribution Center NMF Non Master File NO National Office OE Original Entry OF Organization Function OFP Organization Function Program Org Organization OSC Ogden Campus O/T Overtime OTF/T {C/C} Other than Full/Time {Career/Conditional} P&C Performance and Cost PCA Project Literal for Production and Control Accounting, Project Literal for Performance Evaluation Reporting System (PERS), Project PCA (551) PCB Project Literal for Service Center Workload Scheduling, Project PCB (562) PCC Project Literal for Service Center Production Control and Performance Reporting, Project PCC (563) PCD Project Literal for Control Data Analysis, Project PCD (565) PCE Project Literal for Individual Review Per Period PERF Performance Perm Permanent PERS Performance Evaluation Reporting System PIMS Pipeline Inventory Monitoring System POF Program Organization Function PSC Philadelphia Campus Qtr Quarter Reg Regular SB/SE Small Business/Self-Employed S/H Staff Hour SC Service Center SCHED Scheduled SCRIPS Service Center Recognition/Image Processing System SCRS Service Center Replacement System SETR Single Entry Time Reporting SOI Statistics of Income Operation SPEC Stakeholder Partnerships, Education and Communication STAND Standard STRAWS Suite of Tools for the Review and Creation of Automated Workplans and Schedules TAS Taxpayer Advocate Service TEC Taxpayer Education and Communications Operation Temp Temporary TEPS Total Evaluation Performance System UPC Unit Production Record VAR Variance VOL Volume W&I Wage & Investment Division WAE When Actually Employed WP&C Work Planning and Control
-
The system is designed to relate workload to staff-power. It is organized to provide management tools for the various management levels. These tools provide the means for:
-
Determining staff-power needs,
-
Preparing of plans to justify staff-power needs,
-
Distributing workload and staff-power within the time span limitations of deadlines and target dates,
-
Appraising performance,
-
Determining status of actual workload accomplished and staff-hours expended related to the plan.
-
-
The system will detect and highlight problem areas for management and provide some basic analyses with regard to current and future conditions. It is designed to assist management.
-
Staff-hour data provided by the management tools of this system (Work Plans, Work Schedules, and Performance and Cost Reports) are to be directly related to the operating Financial Plan. The data will be used as the basis for projections in the Financial Plan, and a comparison will be made of budgeted staff-hours with actual expenditures to reflect true financial conditions.
-
WP&C is one of the major component systems contained within IMPIS. It is not designed for daily production control or individual performance evaluation.
-
Business Operating Divisions require long range estimates or forecasts of workload and staff-power to obtain financial support, short range refinement of these forecasts to distribute resources allocated, and quantitative measurement of work accomplished. The WP&C system provides the following management tools to satisfy these needs:
-
Work Plans — to indicate what work will be done, to determine the resources required to accomplish the work, and provide a basis for the Financial Plan.
-
Work Schedules — to indicate when work projected in the Work Plan will be accomplished, to provide a basis for accession of employees by skills, and provide a basis for periodically analyzing the actual status of work compared to that which has been scheduled.
-
Performance Reports — to reflect actual workload accomplished and resources expended in relation to the schedule.
-
-
The Business Operating Divisions use the various Performance and Cost Reports to budget, monitor and evaluate campus operations. The information provided in these reports serves as a base in:
-
Planning future resource requirements,
-
Analyzing workload scheduling,
-
Extrapolating major program costs,
-
Tracking resource expenditures against planned funding.
-
-
The management tools outlined in IRM 25.14.1.2.1 above, are comprised of the following elements:
-
A uniform OFP list showing where the work is done, the work actions necessary to the performance of the work and the work program requiring the actions.
-
Work Units that reflect work accomplished in relation to the staff-hours expended.
-
Standards of production that establish each measured project, how much output (in terms of work units) can reasonably be expended.
-
Input records that record work accomplished and effort expended.
-
-
The WP&C provides a method for coordinating the combined expertise of the site specific staff and the Business Operating Division (BOD) into a plan of action based on past performance and governed by factors that will influence the course of the individual campus in a specific fiscal year.
-
The plan of action provided by this system is known as the Work Plan. The Plan originates with computer generated performance data which is updated by the Wage & Investment, Customer Account Services, Submission Processing, Program Management/Process Assurance, Resource Section (SE:W:CAS:SP:PMPA:R) and is forwarded to the campuses and BOD for review. All changes made to the Work Plan, as well as the supporting narrative statements, are maintained in Suite of Tools for the Review and Creation of Automated Work Plans and Schedules (STRAWS).
-
The campus and BOD offices review the work plans to ensure their adequacy. This review will be facilitated by the use of computer produced comparison listings. The comparison basis will be the prior calendar year’s performance data.
-
Personnel at individual campuses enter proposed changes into the Suite of Tools for the Review and Creation of Automated Work Plans and Schedules (STRAWS). Each OFP combination adjusted includes a narrative statement containing the reason(s) for decreases/increases. Narratives should be clear and concise, explaining the reason(s) for the proposed adjustment. If the proposal is to move volume and/or staff hours from one OFP to another, both the "from" and the "to" OFP should identify the offset.
-
The automated system provides an audit trail for each OFP from the start of the Work Plan process to the "Final" Work Plan phase. During and after the Work Plan process, all users can review the changes made to an OFP, as well as the narratives that support these changes.
-
Work Plans form the basis for Financial Plans. The staff hour requirements developed in the Work Plan represent the labor or staff year portion of the Financial Plan.
-
Headquarter's Submission Processing, Program Management/Process Assurance, Resource Section personnel are responsible for the oversight of STRAWS, each Business Operation Division is responsible for the processing of Work Plan data. Each Functional user or Business Unit is responsible for:
-
Meeting the timeliness established by Submission Processing,
-
coordinating the review of their functional or Business Unit Work Plans,
-
Analysis of all proposed adjustments,
-
Issuing counter proposals to their field personnel or Business Unit entities, and
-
Conducting joint conferences with their functional or Business Unit entities to reach an "Agreed" or "Final" Work Plan.
-
-
These figures are entered into the database once an agreement is made. Any open issues are finalized by an administrative decision made at the BOD level. The final Work Plan staff hour information is furnished to personnel who translate the staff hours/years into labor costs. Therefore, all parties involved in the Work Plan process are responsible for ensuring the availability of staffing and dollar costs needed to operate programs.
-
Each Functional user or Business Unit at the National level issues Work Plan approval memorandums for their offices (usually in Late-August). These documents provide the approved Work Plan staff years as well as the approved Financial Plan availability for a specific fiscal year by budget allocation office/entity. If the approved Work Plan figures differ from the Financial Plan figure, the memorandum includes instructions or recommendations on what adjustment(s) should be made in scheduling and/or execution. The memorandum may also include high level program guidance on key programs.
-
Situations which require adjustments to the operating Financial Plan, e.g., subsequent Congressional actions, are relayed to the field with appropriate instructions by BOD.
-
Work Schedules provided by this system will be generated by computer programs. These programs and the procedures for preparation of the necessary input documents are provided in IRM 3.30.127, Workload Scheduling.
-
Campuses will schedule work three times per year which will result in three final outputs:
-
Schedule Analysis Tape (PCB 9011) to be used in scheduling review; transmitted to DCC for related operations; and to generate an input cartridge for Project PCC (Service Center Production Control and Performance Reporting).
-
PCB 9013 is input to PCB 93 which creates Disk file PCC 0101.
-
A cumulative Workload and Staff-hour file to be used by Business Operating Divisions.
-
-
The scheduling system will be used to generate scheduling outputs for:
-
The first quarter of the Fiscal Year (October – December),
-
The Individual Master File (IMF) filing period (January – June),
-
The last quarter of the Fiscal Year (July – September).
-
-
Approximate due dates for receipt of scheduling outputs are maintained by the BOD. See Exhibit 25.14.1-3 and See Exhibit 25.14.1-4 for copies of the PCB 0440 and PCB 0540 workload and staff-hour schedules.
-
Work schedules indicate when work projected in the Work Plan will be accomplished. The schedules are a more comprehensive representation of approved Work Plans. After Work Plans have been prepared, reviewed, and agreed to, they may be adjusted by program cuts of efficiency/productivity assessments. These adjusted work plans will be the basis for the recommended Financial Plan. The Business Operating Divisions will base their schedules on the approved Work Plan.
-
The computer programs for producing the schedules call for a master tape (Project PCB, Run 90) that will subsequently be related to the Performance and Cost Reports. On a quarterly basis, management should ensure that the scheduled hours fit within the framework of the Operating Financial Plan. This enables management to determine their position in relation to the funded Work Plan and to make necessary decisions in the event of variances.
-
When all Work Schedule data has been transmitted to the Detroit Computing Center (DCC), they are used in a series of computer programs which compare work schedule data to the most recent comparable quarter or half-year performance data. The listings are produced to coincide with, and as a tool in, the Work Schedule review process.
-
All files produced on File PCB 9011 representing the original work schedules, and the final revised Work Schedules will be transmitted to DCC. (See IRM 3.30.123, Processing Timeliness: Cycles, Criteria, and Critical Dates).
-
Labels and transmittals will identify the DCC project designation (ZNV–PCB 9011) and the appropriate "DCC Data Cycle" from IRM 3.30.123, Processing Timeliness: Cycles, Criteria, and Critical Dates.
-
The BOD will continue to receive copies of all Performance and Cost Reports, as described in IRM 25.14.1.2.5.
-
The weekly Performance and Cost data out of PCC 70 (Files PCC 7003 and 7004), will be transmitted by the Computing Centers (ECC-MEM/ECC-MTB) to DCC. In addition to the usual label information on the retention period and cycle of production, the legend "Week Ending," and the report date of data, must be recorded.
-
The transmission of WP&C data for the periods ending June 30, September 30 and December 31 should reflect all adjustments to receipt volumes required to produce final report figures for the Quarterly or Semi-Annual Period. If the period ending date does not fall on a Friday, Saturday or Sunday, a special period ending run for that complete period must be created and transmitted. The final label for January-June, July-September, and October-December will contain the legend "Quarter Ending," and the report date. The labels and transmittals are to identify the DCC project designation ("ZNK" ) and the appropriate DCC Data Cycle from IRM 3.30.123, Processing Timeliness: Cycles, Criteria, and Critical Dates.
-
The purpose of weekly transmissions to DCC is to produce edited input to the data base system maintained by the BOD. This will reduce transmission of monthly data from campuses to the BOD.
-
In addition to its use as a base, performance data provides the base file for print outs known collectively as the "Blue Book." This series of computer output includes three levels of Staff-hour analysis (campus, operation, department), three levels of overhead program analysis, a function-total listing, an organization detail listing, and a program detail listing. Blue Books are produced for both the fiscal and calendar year and the IMF filing period (January — June).
-
Also, quarterly data is used to create calendar year and fiscal year OFP Analysis Reports, equivalent to the weekly OFP reports. These reports contain volumes, hours, and rates for the entire year in OFP sequence for each campus and a National total. For specific instructions, contact organization SE:W:CAS:SP:PMPA:R (Resource Section).
-
Guidelines for the Performance and Cost data transmission to DCC and the Enterprise Computing Centers are specified in IRM 3.30.123, Processing Timeliness: Cycles, Criteria, and Critical Dates),
-
These computer generated reports enable management to evaluate performance in relation to the schedule for the campus site as a whole, for each operation and for any program within a function. Information as to future needs is projected in relation to current actual production.
-
Time reporting procedures are found in IRM 3.30.50, Performance Evaluation Reporting System.
-
Four weekly WP&C Reports are produced by the system. Two of these, the Managers Report and the Program Analysis Report, use weekly schedule data from the workload scheduling system, performance data from the PERS, and production data from the Daymast File as inputs. Since the Daymast is updated daily and these reports are often not produced until the next week, users should be careful to use the proper Daymast file for these reports. The other two reports, the Abstract Report and the Employee Detail Summary, provide fiscal information on employees by organization. Data for these reports comes from PERS.
-
The Managers Report (PCC 6040) is a weekly report designed to provide site managers with an evaluative tool to manage their operations. The report compares scheduled or projected data with actual production. The report is also used in the work planning/scheduling process. See Exhibit 25.14.1-5 for a sample and description of the Managers Report.
-
This report is also used by BOD managers and analysts to monitor various operations and/or programs within their purview.
-
This report consists of two major sections, Performance and Evaluation. The Performance part of the report is generated from the approved Work Schedule, various volume reports (including Unit Production Records), and actual staff hours taken from the Employee Time Report, Form 3081. The Evaluation part of the report provides analysis of the performance data in the first part of the report. It pinpoints and analyzes the differences and gives an indication of what the results will be if current conditions prevail.
-
The report is printed in OFP sequence. It shows the first two positions of the five digit Organization code (XX000), the first two positions of the three digit Function Code (NN0), and the five digit Program Code (NNNNN) — the first four positions are specified in Document 5995A via link located on the OFP Code Web Site at http://etd.ds.irsnet.gov/etd/ofp and the fifth digit is designated by local management.
-
Each OFP combination that has hours scheduled and/or reported during the covered period is shown on the report. Cumulative data covers the six month period January-June, and the three month report periods July-September and October-December.
-
This report generally covers a one week period, running from Sunday through Saturday. When the periods ending June 30, September 30 and December 31 fall on any day other than Friday, Saturday or Sunday two reports will be produced for that week — one from Sunday through the quarter ending date, the second from the next day through Saturday.
-
The Enterprise Computing Center will ensure that the report is electronically available by Wednesday of the week following the close of the reporting period. In addition, Enterprise Computing Centers will transmit a copy of each campus’ report to the Management Information System (MIS) Data Warehouse and Joint Operations Center (JOC) Planning & Analysis NOEL server. If for any reason reports are not transmitted by the designated date, the appropriate Enterprise Computing Center (ECC-MTB/ECC-MEM) should contact the Chief, Data Management Reports Section in the JOC (SE:W:CAS:JOC:PA:DMR) immediately and give a status of the problem.
-
Control D, MIS Data Warehouse, and JOC EONS provides to the Business Operating Divisions access to WP&C/Managers, Program Analysis, Abstract, Employee Detail, and OFP Analysis Reports via personal computers. Electronic transmission of these reports have eliminated the administrative burden of printing and mailing paper copies.
-
Six reports are transmitted weekly including the Managers Report (PCC 6040) the Program Analysis Report (PCC 6240) the Abstract Report (PCC 4640), and campus extracts (PCC 46), (PCA 07), and (PCC 60W/Q).
-
The performance section is generated from the approved work schedule, various volume reports, and the actual staff hours taken from Form 3081, Employee Time Report.
-
The evaluation section provides analysis of the performance data in the first part of the report. This section pinpoints and analyzes the differences between the scheduled rate and hours, and the actual rate and hours. It also gives an indication of what the results will be if current conditions continue. The analysis of this information may be used to determine whether to alter existing conditions in order to change future results.
-
An asterisk (*) printed next to a cumulative figure indicates that the figure has been adjusted for the week.
-
The report is printed in OFP sequence. Reporting begins with the first two positions of Organization Code (e.g., 34000), the first two positions of Function Code and all five positions of Program Code. Summaries of overhead programs, Operation and Department totals are provided in a special section at the end of the report.
-
An OFP must have actual hours or scheduled hours reported before it will print on the Managers Report. Production volumes reported in the WP&C system without actual or scheduled hours are excluded in the Managers Report. See Exhibit 25.14.1-5.
-
Program number 00000 can be used as a Function Summary for all volumes reported to OFPs in the function which do not have hours reported (i.e., 31000–110–00000 or 31000–180–00000). See IRM 25.14.1.2.6.7.2(1) - (5) for more information on creating summary records using Performance and Cost Control Record (PCC 6081).
-
Hours from programs in 598XX series are excluded from operation and campus totals.
-
The Program Analysis Report (PCC 6240) is a weekly report which provides managers with an evaluative tool to manage their operations. It contains basically the same data elements as the Managers Report but differs in that it is printed in POF sequence. See Exhibit 25.14.1-5 for a sample of the Program Analysis Report.
-
The report reflects all volume and staff-hour data that is reported in IMPIS. Volumes that are reported for production control purposes but suppressed in other Performance and Cost Reports will be reflected in the Program Analysis Report. For certain Program Codes a volume count may be shown without the corresponding staff-hours. In these cases the staff-hours and volume counts were reported at a higher summary level.
-
Quarterly and semi-annual reports will include data through the last day of the quarter or semi-annual period. These quarter or semi-annual reports will end on September 30, December 31, and June 30. When these dates fall on any day other than Friday, Saturday or Sunday, two reports will be produced for that quarter — one running from Sunday through the last day of the planning period and one running from the next day through the last day of the next planning period.
-
Distribution of the Program Analysis Report is identical to that for the Managers Report. ( See IRM 25.14.1.2.6.2(8) and See IRM 25.14.1.2.6.2(9))
-
Columns and calculations for the Program Analysis Report are the same as for the Managers Report. An asterisk (*) printed next to a cumulative figure indicates that the figure has been adjusted for the week.
-
Summaries are provided by the four high order digits of program code. Program summaries of scheduled and actual production, standards and rates include the numbers taken from the function designated as the point of count. The summaries for all other columns include all the details for the program. If no function has been designated as the point of count, the volume field will be left blank. A one line Service Center Total appears at the end of the report.
-
OFPs with volume reported but no actual or scheduled hours are included in the Program Analysis report.
-
At the end of each program is a campus summary (20000/3Z000, A0000/FZ000) as well as the total campus’ program summary (10000–FZ000). All summaries are by program code.
-
The Abstract Report (PCC 4640) is a weekly report used to track hours and costs by fiscal activity and employment category. It is also used in preparing the Reconciliation of Payroll and Performance Cost Report, Form 5462. See Exhibit 25.14.1-5 for a sample and description of the Abstract Report.
-
A separate page is printed for each employment category, within each operation with summary pages by funding code and a total organization summary. Period and cumulative information is provided by operation for each week of the quarter.
-
Four reports are printed for each operation:
-
Permanent Employment Category — Hours and cost for all permanent employees within a program activity.
-
OTF/T {C/C} Employment Category — Hours and cost of all seasonal employees within a program activity.
-
Program Activity Summary — Total of the Permanent and OTF/T {C/C} Employment Category hours within a program activity. For example, in Exhibit 25.14.1–5 for the week ending 04-04, the permanent hours of 849 added to the OTF/T {C/C} hours of 6,282 equals the total hours of 7,131 for Program Activity 2B.
-
Branch Summary — Total hours in the operation/department. This includes all program activities within an operation/department.
-
Other pages may be included at the campus' option by using the Temporary Category Code. This code can be used to obtain a more detailed breakdown of the above categories. For example, the Temporary Career/Career-Conditional Category could be separated by new and returning WAE/Seasonal employees.
-
-
Each Employment Category is printed on a separate page with summary pages by Funding Code and a Total Organization Summary.
-
Each page includes from 1 to 14 weeks data (week by week). Cumulative data is kept for the quarter, except for April–June when cumulative figures also include the January–March figures.
-
The total line for period data equals the total of all period lines. This may be different from the cumulative total because adjustments will only correct cumulative data. The period total line for April to June includes the January–March data. This line does not print if only one week’s data is present.
-
Memorandum items (Compensatory Leave, Night Differential, Sunday Premium, and SC Details In) are not added in the totals.
-
Distribution of the Abstract Report is identical to that for the Managers and Program Analysis Reports. ( See IRM 25.14.1.2.6.2(8) and See IRM 25.14.1.2.6.2(9))
-
The Employee Category Record (PCC 4680) is used to put titles for employment categories (Funding Code and Temporary Category Code) on the Abstract Report.
-
Key the Employee Category Record as follows:
Record Position Input 1 Funding Code (0, 1, or 2) 2 Temporary Category Code (0-9 or blank) 4–16 Employment Category Title -
The Funding Codes are:
-
0 = Permanent,
-
1 = Other than Full-Time Permanent (Career/Career Conditional), and
-
2 = Other than Full-Time Permanent (Non Career/Career Conditional).
-
-
The Temporary Category code can be used for further breakdown of the Funding Code. Codes 1 through 9 define further breakdowns; codes 0 or blank indicate no further breakdown.
-
Performance adjustments can be annotated on Form 4464, Daily Performance Adjustments Log or Form 8069, SCRS Managers Performance Adjustments Log, and then input via BBTS using the corresponding adjustment screen.
-
Performance Adjustment Records are used to adjust hour and cost data on the Abstract and Managers Reports. A managers performance adjustment with a program activity code will adjust the total basic hours and/or basic cost fields on the Abstract Report. If the program activity code is not present, the Abstract Report will not be adjusted.
-
Two records are used to adjust data on the Abstract Report. These records are independent, the presence of one does not require the presence of the other.
-
Fields on the first Abstract Performance Adjustment Record used to adjust Night Differential Hours/Costs, Sunday Premium Hours/Costs and Basic Hours/Costs (Control Code = 1) include:
Record Position Description 1 Record Code — Always "2" 2 Adjustment Code (2, 3, 4, or 9) — See IRM 25.14.1.5.9.3(4) 3–4 Employee Type Code — leave blank unless a detail from outside the campus. 5 Control Code = "1" 6 Funding Code (0, 1, or 2) — See IRM 25.14.1.2.6.4.1(3) 7 Temporary Category code (0-9) — See IRM 25.14.1.2.6.4.1(4) 8–12 Organization Worked — Required 13 Overhead Indicator (9 or blank) 21–26 Week Ended — Required (MMDDYYYY) 27–28 Program Activity Worked — Required 29–30 Assigned Program Activity. Input if different from Program Activity Worked — Otherwise leave blank 34–38 Night Differential Hours — Whole Numbers 39–44 Night Differential Costs — Whole Dollars 45–49 Sunday Premium Hours — Whole Numbers 50–55 Sunday Premium Costs — Whole Dollars 62–69 Basic Hours — Whole Numbers 70–80 Basic Costs — Whole Dollars All positions not specified are left blank. NOTE:Form 4464, Daily Performance Adjustments Log — Adjust Abstract Report Only. -
Fields on the second Abstract Performance Adjustment Record used to adjust Compensatory Leave Hours/Costs, Paid Overtime Hours/Costs and Unpaid Overtime Hours/Costs (Control code = 2) include:
Record Position Description 1 Record Code — Always "2" 2 Adjustment Code (2, 3, 4, or 9) — See IRM 25.14.1.5.9.3(4) 3–4 Employee Type Code — leave blank unless a detail from outside the center 5 Control Code = "2" 6 Funding Code (0, 1, or 2) — See IRM 25.14.1.2.6.4.1(3) 7 Temporary Category Code (0–9) — See IRM 25.14.1.2.6.4.1(4) 8–12 Organization Worked — Required 13 Overhead Indicator (9 or blank) 21–24 Week Ended — Required (MMDD) 25–26 Program Activity Worked — Required 27–28 Assigned Program Activity. Enter if different from Program Activity worked — Otherwise leave blank 34–38 Compensatory Leave Hours — Whole Numbers 39–44 Compensatory Leave Costs — Whole Dollars 45–49 Paid Overtime Hours — Whole Numbers 50–55 Paid Overtime Costs — Whole Dollars 62–69 Unpaid Overtime Hours — Whole Numbers 70–80 Unpaid Overtime Costs — Whole Dollars All positions not specified are left blank. Note:Form 4464, Daily Performance Adjustments Log—Adjust Abstract Report Only. -
Fields on the Managers Performance Adjustment record used to adjust Total Hours and Total Costs (Control Code = 0) include:
Record Position Description 1 Record Code — Always "2" 2 Adjustment Code (2, 3, 4 or 9) — See IRM 25.14.1.5.9.3(4) 5 Control Code — Always zero 6 Funding Code (0, 1, or 2) — See IRM 25.14.1.2.6.4.1(3) 7 Temporary Category Code (0 or 9) — See IRM 25.14.1.2.6.4.1(4) 8–12 Organization Code — Required 13–15 Function Code — Required 16–20 Program Code — Required 21–24 Week Code — Required (MMDD) 25–26 Program Activity Worked — Optional but required to post to Abstract Report 27–28 Assigned Program Activity. Enter if different from Program Activity Worked — Otherwise, leave blank 62–69 Total Hours — Whole Numbers 70–80 Total Cost — Whole Dollars All positions not specified are left blank. Note:Form 8069, SCRS Managers Performance Adjustments Log — Adjusts Managers and Abstract Reports -
Either the Total Hours or Total Cost field must be present; except for a delete.
-
A Managers Performance Adjustment with a Program Activity Code and Funding Code will adjust Total basic hours and basic costs on the Abstract Report. These are basic hours. If these codes are not included, the Managers Report will be adjusted but the Abstract Report will remain unchanged.
-
Required fields for deleting data from the Abstract Report are the Record Code, Adjustment Code (9), Control Code, Employment Category, Organization Worked, Program Activity Worked, and Week Ended. The Week Ended should be the last week on the file. The delete action will change the last week’s cumulative data to zero. This record will remain on the file for two weeks. If no further adjustments are made, the whole record will be deleted from the file. This two week delay allows the correction of an erroneous delete action before the record is purged from the file.
-
Required fields for deleting data from the Managers Report include the Record Code, Adjustment Code (4 or 9), Control Code, Organization, Function, and Program. A delete adjustment to the Managers Report will not affect Abstract Report data.
-
Performance adjustments adjust cumulative data only. Period data will not be changed.
-
The Overhead Indicator on abstract adjustments is used to put the hours adjusted in the Overhead column for use in calculating the Overhead to Direct and Overhead to Total Percentages. A "9" indicates an adjustment to Overhead Hours; a "blank" adjusts Direct Hours.
-
The Employee Detail Summary Report (PCC 4240) is a weekly report which provides managers with data for tracking detailed employees between operations/departments and fiscal activities. See Exhibit 25.14.1-10 for a sample of the Employee Detail Summary Report.
-
The report is printed in organization sequence. A page is generated for period and cumulative data, as well as pages for campus summaries. Each page lists the hours and costs (regular and overtime) for employees (permanent and temporary) detailed "To" and "From" an organization by operation/department and Program Activity Code. This report is used to track hours and costs when employees charge hours (detail their time) either to a different operation/department or to OFPs with a different Program Activity Code than their home organization and home PAC. There is a period data page and a cumulative data page. The Employee Detail Summary reflects the number of hours used and the cost of permanent, temporary, and overtime hours. It also identifies the program activity to which the hours are charged.
-
The left side of the report (Detail To) describes details from the organization listed in the heading to the organizations and fiscal activities listed on the side of the report. The right side of the report (Detail From) describes details from the organizations and fiscal activities listed on the side of the report to the organization listed in the heading.
-
The total hours detailed out "To " equal the permanent regular and overtime hours plus the temporary regular and overtime hours.
-
The total hours detailed in "From " equal the permanent regular and overtime hours plus the temporary regular and overtime hours.
-
When an employee is on detail to another area, the hours are not charged to the Assigned Organization, but the salary (cost) is still paid by the Assigned Organization. Only when the employee is on a temporary promotion, are the hours and costs charged to the Receiving Organization.
-
All zero organizations or management activities will not print on the report.
-
Information included in the Employee Detail Summary may be balanced to the "Inter-Activity Service Center Details-In and/or SC Det In" column on the Abstract Report.
-
Employee Detail Adjustments are prepared whenever erroneous data (e.g., erroneous organizations or Form 3081, Employee Time Report prepared incorrectly) posts to an Employee Detail Job Record.
-
Employee Detail Adjustments can be annotated on Form 8209, Employee Detail Adjustments Log, and then input via BBTS using the corresponding adjustment screen.
-
Fields on the Employee Detail Adjustment Log include:
Record Position Description 1 Record Code — Always 4 2 Adjustment Code (2, 3, or 9) — See IRM 25.14.1.5.9.3(4) 6 Funding Code (0, 1, or 2) 8–12 Organization Worked — Required 25–26 Program Activity Worked — Required 27–28 Assigned Program Activity — Required 29–33 Assigned Organization — Required 45–49 Overtime Hours — Whole Numbers 50–55 Overtime Costs — Whole Dollars 62–69 Regular Hours — Whole Numbers 70–80 Regular Costs — Whole Dollars All positions not specified are left blank. -
At least one of the data fields, Regular Hours or Costs, Overtime Hours or Costs must contain data; except for a delete.
-
Adjustment Code 2 must be used if adding hours to a record that did not previously exist, for example; if a Detail "From" Organization 31000 to 34000 (same program activity code) was incorrectly entered as a Detail " To" Organization 43000 and no other hours had been reported from Organization 31000 to 34000, then:
-
Add the hours and costs to Organization 31000 to 34000 using Adjustment Code 2.
-
Subtract the hours and costs from Organization 31000 to 43000 using Adjustment Code 3.
Note:
A record will be deleted using Adjustment Code 9 therefore, caution must be exercised when using this code. Before deleting a record entirely, determine if the record should be corrected using Adjustment Code 2 or Adjustment Code 3, if adding to or subtracting from a record.
Note:
The same Adjustment Codes used for adjusting the DPR, with the exception of Adjustment Code 4 will be used for Employee Detail Adjustments.
-
-
Valid production, performance, and Employee Detail Adjustments are printed on the Production and Performance Adjustments Listing (PCC 1041). PCC 1041 lists the valid Performance Adjustments Records, Production Adjustments Records and Employee Detail Adjustments for the day. It combines all like OFPs and totals for the day. This listing is for audit trail purposes and to be used as a reference if any of the output is not as expected.
-
All negative adjustments are indicated by an alpha character in the last position of the volume. Close attention should be made to the alpha and numeric "0" on the PCC 1502 Listing. PCC 1502 lists the VALID records from PCC 1089, exception being that the summarized adjustment records generated by BBTS and PCD are listed individually. Codes are annotated as follows:
Alpha and Numeric Code J = 1 K = 2 L = 3 M = 4 N = 5 O = 6 P = 7 Q = 8 R = 9 Blank = 0 or a special character
-
Volume figures without actual or scheduled hours are dropped from the Managers Report unless a Performance and Cost Control Record (PCC 6081) is input for that function, except as described immediately below.
-
Some functions such as Batching and Numbering, require reporting of volume data to individual returns programs for document control in the BPR and DPR, but because of the similarity of work, do not require reporting of hours to that detail. In these functions, volumes are generally reported to Program Code 00000 and hours are reported to the individual returns program. The Performance and Cost Control Record is used to summarize these volume figures under Program Code 00000 for the Managers Report.
-
Under the roll up procedure, all programs with volume data and no actual or scheduled hours will be summarized to Program Code 00000. Programs with actual or scheduled hours charted will not roll up to the 00000 program but will be shown separately.
-
These records are input as follows:
Record Position Input 1–2 First 2 digits of the first Org Code 3–5 Function Code (First) 6–7 First 2 digits of the next Org Code 8–10 Function Code (Second) Continue keying organizations and functions as needed through position 75. Organizations and functions must be entered in ascending OF sequence, e.g. 31–110, 31–180, 34–190, 43–610. Key a "1" in position 78 if more than one P&C Control Record is used. Key a "K" in position 80. -
Campus Work Plan Schedulers should coordinate with the local Reports Staff, Headquarters Joint Operations Center PCC Analyst, and the Computing Centers (ECC-MEM/ECC-MTB) to initiate set-up or changes to this record.
-
The Selected Master Data File Fast Print Control Records are used to obtain a fast print PCC 2640, Selected Master Record List (Project 563) for WP&C Master File of specified records on the Master Data File to determine what data is present for Master file clean-up and maintenance.
-
Each record consists of the Program Code, Organization Code, and Function Code, in that order, in positions 1–13 and an "L" in position 80.
-
Separate records are required for each POF requested.
-
The Reports Staff for each campus should order a complete listing of the PCC 2640, Selected Master Record List, review and perform maintenance clean-up at least twice per year, once during the January – June period and once during July – December.
-
Contact the Joint Operations Center, PCC Analyst prior to input of any final 3,9 Adjustments.
-
Batch and Production Control Records, Unit Production Records, and Performance and Production Adjustments are matched against the OFP Consistency File, Project PCA (551). Invalid records are printed on the Preliminary or Correction Error Registers.
-
Program Activity Codes are carried on the OFP Consistency File indicating the Program Activity relating to each OFP. These are compared against Program Activity Codes carried on the Employee Master File to determine the extent of inter-activity details for the Abstract Report and the Employee Detail Summary.
-
It is possible that some OFPs are used in the Performance and Cost system that were not used in PERS, Project PCA (551) and are thus not on the PERS OFP Consistency File. For example, PERS reporting for a program might include all 3 digits of function code (e.g. 231 and 232) but not include the more general code (230) as reported on the Daymast. These additional OFPs must be added to the OFP Consistency File.
-
All OFPs that are used on Batch and Production Control Records or Unit Production Records must be entered on the OFP Consistency File. This includes individual return programs for Functions 180, 190, and 610 which were reported under the 00000 program code in PERS (34000–190–11110 etc.).
-
The campuses no longer have the capability to establish, change or edit parent Organization, Function and Program code combinations on their OFP Consistency File. All changes of this nature must be submitted using the 5948 link via the OFP web site http://etd.ds.irsnet.gov/etd/ofp . See Exhibit 25.8.1–1 in IRM 25.8.1, OFP Codes Overview for a sample of Form 5948. Detailed procedures for preparing Form 5948 are outlined in IRM 3.30.50, Performance Evaluation Reporting System (PERS).
-
The OFP Coordinator for each Campus Directorship is responsible for coordinating updates to their OFP Consistency File.
-
The OFP Coordinator for each Campus Directorship should notify the Reports Staff of all updates to the OFP Consistency File for both parent and child level OFP combinations.
-
Each Campus Reports Staff will review all PCA02 updates and on a weekly basis review all PCA02 output reports.
-
Hour and cost data for the Managers, Abstract, and Program Analysis Reports and the Employee Detail Summary are obtained from the Performance Evaluation Reporting System (PERS), Project PCA (551).
-
PERS provides weekly hour and cost figures by OFP and employee. These figures are subdivided into Overtime, Compensatory Time, Night Differential, Sunday Differential, and Compensatory Leave taken. In addition, PERS provides information on type of employee (Permanent, Temporary, etc.) and on the type of Program Activity (e.g. 2B = Returns Processing) that the employee is paid under.
-
See IRM 3.30.50, Performance Evaluation Reporting System for information on entering Program Activity Codes and Funding Codes on the Employee Master File.
-
The Daymast File will be copied at the end of each week. One file will be used for daily updates beginning the next week and the other will be used for the weekly WP&C reports.
-
Work Schedule data from the Service Center Workload Scheduling System, Project PCB (562) is input to the Production Control and Performance Reporting system for use in the Daily Production, Managers and Abstract Reports. The Daily Master File must be updated weekly from the work schedule master files using Run PCC 01. During a reporting period, if a revised work schedule is produced for use in this system, the BOD must be notified in writing. The narrative should identify the changes made to the schedule and a summary of staff-hour changes (by operation/department) is required for any significant changes.
-
The work plans and schedules described in IRM 3.30.127, Workload Scheduling are an integral part of the budget process. The approximate dates of the work steps are issued by the BOD.
-
See IRM 25.14.1.2.7 for requirements for work schedule input and for procedures for Quarterly and Annual cut overs.
-
Prior to the quarterly or semi-annual report period the Reports Staff will request that all operational areas take a physical inventory of all documents or returns on hand that are not under the Batch/Block Tracking System (BBTS) Batch Control. The documents or returns requiring physical inventory are those that have receipts, production and inventory reported on WP&C reports via Unit Production Records (UPC’s). Operations will submit in writing the inventory count via E-mail/fax to the Reports Staff. The Reports Staff will review these inventories, and prepare Production Adjustment Records to update the Master Data File and verify that all adjustment records have posted. Negative UPC inventories will be reconciled and brought to zero or greater.
Each campus Reports Staff is responsible for verifying the physical inventory counts and inputting adjustment(s) for any organization reporting data on the sites WP&C. This includes Accounts Management, Compliance, Taxpayer Advocate, TE/GE, SPEC/TEC, etc. The Reports Staff is asked to coordinate this project to ensure the process is completed smoothly and that all adjustments post successfully prior to the end of the WP&C reporting period. -
On the last processing day of the cut-over period, all daily PCC processes will be completed this includes the DPR and BPR.
-
The Joint Operations Center will provide an End of Quarter/End of Year Processing Schedule for production of the Quarterly Performance and Cost Reports.
-
Planning and Analysis Staffs will ensure that the Master Schedule Tape is complete and available to update the Master File.
-
PCC 0140 will be run to produce the Service Center Master Data File POF List. ( See IRM 25.14.1.2.7.3)
-
If the quarter ends on other than a Friday, Saturday, or Sunday, it is necessary to produce a quarterly Performance and Cost Report as of the end of the quarter. It is not necessary to produce a quarterly P&C Report on March 31. Use the following procedures to produce the quarterly report:
-
Process Forms 3081, the necessary Quality Review forms and production records for the short week. Produce PERS run PCA–03 for the quarter using a "Q" in the PERS Date Record.
-
Complete Daily Processing for the last day of the quarter.
-
Run the Quarterly Schedule Update Run (Run PCC–01Q). This run will:
-
Copy the Daymast, Abstract and Employee Detail Files. One set of files can be used for end of quarter processing while the other set of files will be used for daily updates for the next quarter.
-
Zero out quarterly elements on the files. Certain fields such as receipts and production for the DPR, will only be zeroed on Dec. 31.
-
Replace the schedule data on the Daymast.
-
Produce the SC Master Data File POF List.
Note: Records with all zeros in the data fields (Scheduled Volume and Hours, Actual Volume and Hours, and Inventory) will be deleted only if the Adjustment Code is "9" .
-
-
Run the End of Quarter Processing (Run PCC 40Q) using the copied files.
-
Run PCC 01W — this must still be the first run of the next daily processing run.
-
-
The closing inventories for each POF on the Master File as of the last day of the processing period will automatically be rolled over as the opening inventory for the first day of the new processing period. The other fields will be zeroed out automatically.
-
In order to balance the DPR, adjustments must be made to include the inventories in each function as receipts. In the pipeline area, these inventories must show as processed work in each prior function.
-
Special BBTS programming, the BBTS Beginning of Year file, provides new receipts and production figures for each OFP based on the batches of work remaining in the pipeline. This file creates all Production Adjustment Records needed to populate the Daily Production Report (DPR) as 3,2 Production Adjustment Records.
-
Receipts in Functions 910 through 950 will be the same as opening inventories in Functions 910–950.
-
Receipts in Function 610 will be the total of Function 610 production plus Function 610 inventory.
-
Production in Function 230 will be the same as receipts in Function 610.
-
Receipts in Function 230 will be the total of Function 230 production plus Function 230 inventory.
-
Receipts and production for Functions prior to 230 are computed by BBTS’s "Beginning of Year" run according to the workflow established for each program. The receipts in each function must agree with the production from preceding functions.
-
Cum Receipts and Production in Function 110 will equal the cum Receipts in Function 180 plus Function 170 minus the cum Receipts in Function 970 (Re-inputs), plus the inventory in all functions prior to Function 180.
-
-
The BBTS Beginning of Year file will also create 3,2 Production Adjustment Records needed to set the inventory for Organization 43000 Functions 910 through 970 to zero for each program number (and sub-program number) that appears on the DLN Reference File for a campus that has a valid OFP for that campus.
-
After the cumulative data is determined, Reports Staffs will prepare Form 4465, Daily Production Adjustments Log for input of the production adjustments where needed. See IRM 25.14.1.5.9.3 for more information on Form 4465.
-
Once the inventory calculations have been completed, Reports Staffs will total all inventories for Functions 910 to 940 and add them to cumulative receipts and production beginning with Function 610. Include the calculated inventories in all previous functions in the routing pattern for the specific Program Code continuing through Function 110. PCC 2240 Daily Production Report (DPR) totals will differ from Pipeline Inventory Monitoring System (PIMS) totals by these calculations. Production Monitors should be notified of the adjustment amounts for monitoring purposes. See Exhibit 25.14.1-8 for a sample of the PCC 2240.
-
For each OFP, post the cumulative receipts volume to "Cumulative Receipts Since January 1," positions 34–41 and the cumulative production volume to "Cumulative Production to End of Year," positions 57–64.
-
Do not enter production in any other production or receipts field on the Form 4465, Daily Production Adjustments Log. To do so will cause it to appear on the Performance and Cost Report for the new year.
-
-
Unit Production Adjustments — Receipts for Unit Production reporting will be the same as the opening inventory on the Organization Sequence DPR (PCC 2440) for the first day of the new processing year. Reports Staffs will enter the information in "Cum Receipts Since January 1" , positions 34 – 41 for each OFP as applicable.
-
The Service Center Master File POF List (PCC 0140) is produced as an aid for Reports Staff in their year end processing. This listing contains every POF combination that is on the Master File at the completion of processing and its closing inventory.
-
The Last Action Date shows the year and Julian Date of the last posting to the POF. This tells whether all the transactions have posted or not.
-
Schedule on File, Old and New. An "X" in one of these columns indicates that there was or is schedule information on the Master File.
-
Hours or Cost. An "X" indicates that there are hours posted on the old Master File.
-
Closing Inventory Forward. The closing inventory as of the last day of the year.
-
The input production records go through a series of validity checks that identify any error code, duplicate and invalid records; consistency checks for valid OFP combinations; and checks for attempts to delete and post to the same OFP.
-
The Preliminary Error Register (PCC 1040) lists invalid conditions detected in Batch Control Records, Performance Adjustment Records and Production Adjustment Records. An 80 character image of the invalid records is printed followed by the appropriate error codes. During re-input processing the error register is retitled as the Correction Error Register.
-
Performance Adjustment (Record Code 2) errors:
Error Code Element Name Error Condition A Record Code Other than 2 B OFP Invalid (OFP) is not on OFP Consistency File or Delete Adjustment that doesn’t match a record on the file. D Adjustment Code Other than 2, 3, or 9. Adj. Code 4 is valid for Control Code 0 only. E Control Code Not equal to 0, 1, or 2. F Change Data Fields Data in these fields must be all numeric and right justified. If Adjustment Code = 2, or 3, one of these fields must contain data. If Adjustment Code = 4 or 9, these fields must be blank. G Change Data Fields Adj. Code = 2 and at least one data field contains a negative amount. H Total Hours or Costs A managers performance adjustment (Control Code 0) without data in either of these fields or not all numeric. I Employment Category Organization Worked Program Activity Worked Week Ended An Abstract Adjustment (Control Code 1 or 2) with other than all numerics in these fields. J All An Abstract Adjustment with no matching record on the file (Employment Category Organization Worked, Program Activity Worked, Week Ending Date). L Employee Type Code Invalid (Not equal to bb, 00, 02, 10, 11, 20, 21, 30, or 31). Overhead Indicator Invalid Overhead Indicator R All Attempt to update a deleted record. Z All Duplicate input record. -
Production Adjustment (Record Code 3) errors:
Error Code Element Name Error Condition A Record Code Other than 3 B OFP Invalid or Delete Adjustment that doesn’t match a record on the file. D Adjustment Code Other than 2, 3, 4, or 9. F Change Data Fields Data in these fields must be all numeric and right justified. If Adjustment Code = 2, or 3, one of these fields must contain data. If Adjustment Code = 4 or 9, these fields must be blank. G Change Data Fields The Adjustment Code = 2 and at least one data field contains a negative amount. R All Attempt to update a deleted record. Z All Duplicate input record. -
Batch Control Record errors:
Error Code Element Name Error Condition A Record Code Other than 7 B From OFP Invalid C To OFP Invalid (or From OFP = To OFP) D Type Code Other than 1, 3, or 5. E From Org From Function Type 1 only. Must be prior to 31000 (Org.) and 180 (Function). K Program Title Type 3 only. Must be present. N Batch Sequence No. Type 3 only. Must be all numeric. O Estimated Volume Type 3 only. The estimated volume must be present and all numeric if the From Function equals 180 or 210 and the To Function equals 190 or 210. P Actual Volume Type 3 only. Must be present and all numeric when From Function equals 190, or 230 or the To Function equals 230. Q Unit Production Type 5 only. Must be present and all numeric. R From OFP A delete adjustment (Adj. Code 9) is present for the same From OFP. S To OFP A delete adjustment (Adj. Code 9) is present for the same To OFP. T DIS Code Other than blank or D. U Adjustment Code Other than blank, 1, 2 or 3. V To Function To Function must be less than or equal to 210 (Type 1). W Receipts Types 1 and 5 only. Must be present and all numeric. X Release Date Release Cycle Earliest Rec'd Date Other than 001–366
Not equal to 01–53
Other than 001–366Y Adjustment Type Code A field is present but is inconsistent with the type code. Z All Duplicate Record. -
Special error codes for Batch Control Record, Batch Profile Adjustment errors (Record Code 7, Adjustment Code 2, Type Code 3) include:
Error Code Element Name Error Condition B Program Code Invalid. C Function Code From Function equals To Function. F Change Data Fields All of the data fields are blank. N Batch Sequence No. Not equal to 0001–9999. P Actual Volume Not all numeric or all blank. X Release Date Cycle Earliest Received Date Not all numeric or all blank. -
Special error codes for ISRP Batch Profile Adjustments (Record Code 7, Adjustment Code 3, Type Code 3) include:
Error Code Element Name Error Condition B Program Code Invalid. M Function Code Not equal to Function 230. N Batch Sequence No. No matching batch in the function. P Actual Volume Not all zeros. Y Data Fields Data appears in unnecessary fields. -
Employee Detail Adjustment errors (Record Code 4) include:
Error Code Element Name Error Condition A Record Code Other than 4. B Org. Worked / Org. Assigned Invalid. C Organization Program Activity The Assigned Organization and Program Activity is equal to the Organization and Program Activity Worked. D Adjustment Code Not equal to 2, 3, or 9. G Negative Data Field Adjustment Code equals 2 and at least one data field contains a negative amount. H Overtime Hours/Costs or Regular Hours/Costs No data in any of these fields or not all numeric. I Program Activity Funding Code Not all numeric. Not equal to 0, 1, or 2. J Organization Program Activity No matching data to adjust. (Adj. Codes 3 or 9). R Organization Program Activity A delete adjustment (Adj. Code 9) is present for the same Organization and Program Activity combination. X Overtime Hours/Costs or Regular Hours/Costs Data in Hours but not Costs or vice versa or no data in Hours (Adj. Code 2). Z All fields Duplicate input data.
-
The Daily Adjustment Error Listing (PCC 2040) lists adjustments that did not post to the master file. The listing consists of an image of the adjustment that did not post and a message explaining the reason why.
-
These errors were previously checked in the Preliminary or Correction Error Registers. Errors could be the result of computer read fails or changes to files after the original error pass. Non-posted adjustments could lead to Cum figures for the current week that differ from expected figures.
-
See Exhibit 25.14.1-11 for Error Messages.
-
The weekly and quarterly Performance and Cost Tapes are transmitted to the Detroit Computing Center for input to Project 540, N.O. Preparation of Service Center Work Plans, the "Blue Book," and several comparative analyses. See IRM 25.14.1.2.5(2) & See IRM 25.14.1.2.5(3) for shipping instructions.
-
Weekly and quarterly Performance and Cost data is transmitted to the JOC’s NOEL server and to the server for the MIS Data Warehouse.
-
The production control portion of the system is designed to provide:
-
a uniform and effective day-to-day control and routing of service center workloads in both pipeline and non-pipeline operations, and
-
production reporting for such operations, which will provide managers with the means of ensuring that production processing is meeting or will meet the required cycle or desired completion date.
-
-
It is not designed to establish controls or procedures normally associated with systemic or procedural controls such as Data Control, Media Transport and Control, or Accounting Controls.
-
The production control portion of the system relates only to those programs, functions and organization elements of the campus that are required to report on work volumes. Workload volume counts used in production control will be the basis for all actual production counts required for the Performance and Cost Reports.
-
The following procedures provide for arranging work into convenient groups of work, identifying these groups, and reporting on their progress. This section also provides detailed procedures for maintaining the Campus Production Control.
-
These procedures deal with the campus processing only. They do not deal with processing of output tapes or reports at the Computing Centers or the Business Operating Division.
-
All programs do not have the same significance. Therefore, information is not needed for all programs at the same frequency. The computer programs developed to produce production reports required in this system are designed to accept and process information daily which is the maximum frequency. Three computer generated reports are produced by this system:
-
The PCC 3240, Batch Profile Report ( See Exhibit 25.14.1-6),
-
The PCC 2440, Daily Production Report by Organization ( See Exhibit 25.14.1-7), and
-
The PCC 2240, Daily Production Report by Program ( See Exhibit 25.14.1-8.
-
-
The frequency of the reports is not controlled by the computer programs but by the frequency of information input. Daily input will produce daily reports and inputting data only one day a week will produce a weekly report.
-
Two records are used in the system to input volumes of work units. The Production Control Record which is used for pipeline programs and the Unit Production Record ( See Exhibit 25.14.1-13) which is used for non-pipeline programs. Pipeline programs are those programs which have a consistent pattern of functions through which the work must flow. Non-pipeline programs are those generally common to one function. Production Control Records are used as input to all three output reports provided in this system while Unit Production Records are usually used as input to the two daily production reports.
-
These three reports are sent to the Submission Processing web site and the MIS Data Warehouse.
-
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, use data for unauthorized purposes, or make unauthorized access to the data.
-
All campuses currently use a National Standard Application Inventory System known as the Batch/Block Tracking System (BBTS). BBTS generates a disk file which is transmitted to the Enterprise Computing Centers (ECC-MEM & ECC-MTB) for the production of the BPR and the DPR. BBTS is used for input of managerial information for Project PCC (563). However, the following alternative methods can be used as back-up mechanisms when needed.
-
For Project PCC (563), the following files can be input via ISRP along with a Form 813, Document Register or Form 1332, Block and Selection Record to control each block of work.
-
Performance Adj. Records; File #s 10–82–001,002,& 003
-
Production Adj. Records; File # 10–83
-
Type 5 BPC Records; File # 10–85–003
-
Employee Detail Adj. Records; File # 10–84.
-
-
The following files will be input via a terminal utilizing a user friendly front-end processor.
-
DPR POF Control Records; File # 10–81
-
Date Records; File #s 01–80, 10–80
-
DPR OFP Control Records; File # 24–80
-
Select MF Print Control Records; File # 26–80
-
Employee Category Records; File # 46–80
-
PC Control Records; File # 60–81
-
-
Refer to local user manuals for ISRP instructions.
-
Batch and Production Control Records are used to report volumes of individual batches of work and track these batches as they are processed through the pipeline. These records are attached to the batches and are input to the system each time a particular operation (function) is completed on that batch. Two types of volumes are reported on Batch and Production Control Records; estimated and actual. See Exhibit 25.14.1-12, Batch & Production Control Record Layout and See Exhibit 25.14.1-13, Unit Production Record Layout.
-
Estimated receipt volumes are input to Type 1 control records for those functions prior to batching and numbering of documents. The elements of a pipeline receipts record are:
Record Position Title Description 1 Record Code Always "7" 4 Type code Always "1" 8–12 From Organization Always 31000 13–15 From Function Must be a valid function code less than Function 180 16–20 Program Code Must be a valid Program Code 25–29 To Organization Must be a valid Organization Code 30–32 To Function Must be a valid Function Code less than or equal to function 210 33–40 Program Title The use is optional 41–48 Receipts Right justified, all numeric and zero filled 62–64 Earliest Received Date Julian Date (001–366) All positions not specified are left blank. See Exhibit 25.14.1-12 for Batch & Production Control Record Layout. -
Valid Organization, Function, and Program (OFP) Code combinations are prescribed in Document 5995A, via link to the OFP Web Site, http://etd.ds.irsnet.gov/etd/ofp .
-
Actual Volumes are input to Type 3 Batch and Production Control Records from pipeline functions from the time the actual counts are determined in Numbering (Function 190) until the batches have cleared ISRP or SCRIPS. Estimated volumes are reported for batched documents before the actual counts are known. The elements of a pipeline production record are:
Record Position Title Description 1 Record Code Always "7" 4 Type Code Always "3" 8–12 From Organization Valid organization code 13–15 From Function Valid function code 16–20 Program Code Valid program code 21–24 Batch Sequence Number 0001 through 9999 25–29 To Organization Valid organization code 30–32 To Function Valid function code 33–40 Program Title Input program title; do not leave blank 57–59 Release Date Julian date (001–366) 60-61 Release Cycle Input 01 through 53 62–64 Earliest Received Date Julian date (001-366) 65–68 Estimated Volume Input if the actual volume is not known. Must be present if From Function is 190 or 150. 69–72 Actual Volume Input if known, right justified and zero filled. Must be present if estimated volume is blank or From Function is 190 or 150. 73–79 Identification Optional field for service center use 80 ISRP Code Input a "D" when the Function Code is 230 or 450 All positions not specified are left blank. See Exhibit 25.14.1-12 for Batch & Production Control Record Layout. -
Production in Function 230 or 450 is carried as a partial volume until the batch has cleared ISRP or SCRIPS as follows:
-
The cleared ISRP volume is posted as production to ISRP.
-
The cleared ISRP volume is posted as receipts to 43000–610 automatically.
-
At the next posting, the cleared ISRP volume is credited as production for 43000–610.
-
-
No input record is required for Function 610. Batches will automatically be credited to Function 610 after they have cleared ISRP.







