1.15.17  Records Control Schedule for Information Technology

1.15.17.1  (02-23-2009)
Description and Authorities

  1. The records covered by this schedule are created and accumulated by Information Technology (IT) activities and functions Servicewide. However, records created by the Detroit and Martinsburg Computing Centers are covered by separate records control schedules published as IRM 1.15.18 and IRM 1.15.19; certain files created and maintained in the operation and management of IT and related services are covered in IRM 1.15.61 (refer to the IRM for examples of the types of records); and electronic systems used in tax administration activities are covered in IRM 1.15.35.

  2. The Information Technology organization, headed by the Chief Information Officer, is responsible for:

    • strategic technology planning,

    • planning and designing multi-functional information systems,

    • data administration,

    • coordinating and integrating functional systems into the overall systems architecture,

    • acquiring, testing, developing, and maintaining computer equipment, and software,

    • providing data security, and

    • providing telecommunications services.

  3. This schedule consists of two major groups of records:

    • administrative records, and

    • technical records.

  4. The records disposition authorizations in this schedule are based on administrative determinations of the Internal Revenue Service and disposal authorities dated March 13,1975, June 12,1975, March 10,1977, and February 9,1998, granted by the Archivist of the United States.

  5. See Exhibit 1.15.17–1 for the Records Control Schedule.

  6. See Exhibit 1.15.17-2 for an Alphabetical Listing for the Records Control Schedule.

  7. See Exhibit 1.15.17-3 for a Forms Listing for the Records Control Schedule.

Exhibit 1.15.17-1  (02-23-2009)
Records Control Schedule for Information Technology

Item
No.
Description of RecordsAuthorized Disposition
  Administrative Records
1. Correspondence Files.
Routine correspondence covering day-to-day operations, transmittals, facsimiles, and requisitions that relate to administrative housekeeping and facilitative roles of the organization and not procedural in nature. (Job No. NC–58–75–1, Item 2)
Destroy when 2 years old.
2. Annual Business Review Reports. Record copies of program review evaluations and associated correspondence operations and activities of IRS regional offices, service centers, and field offices. (Job No. N1-58-93-5, Item 3) Retire to Records Center when 5 years old.
Destroy when 10 years old.
3. Treasury Inspector General for Tax Administration (TIGTA) Audit Reports. Reports, work papers, and correspondence, including correspondence, reports on surveys, special studies, and investigations conducted jointly with other organizations. (Job No. NC1-58-77-3, Item 1)  
  (1) Record Copy. Cut off annually.
Retire to Records Center when 3 years old.
Destroy 10 years after issuance of report.
  (2) All other copies. Destroy when 3 years old or when no longer needed for current operations, whichever is sooner.
4. GAO Reports.
(1) Record copy of IS responses and copy of reports relating to tax systems modernization issues.
(Job No. N1–58–97–4, Item 4)

PERMANENT.
Cut off annually.
Retire to Records Center when 5 years old.
Transfer to NARA when 20 years old.
  (2) All other copies of reports, correspondence generated in response to report, and related background information.
(Job No. N1–58–97–4, Item 4)
Cut off annually.
Destroy when 3 years old.
5. Forms and Form Letter Files.
pertaining to the development of internal and external use forms and form letters, revisions, instructions for preparation and distribution, justifications and coordinations. Form is placed in inactive file when rescinded, superseded, or rendered obsolete. (Note: Historical copies are maintained by Publishing Services in W&I).
(Job No. NC–58–75–1, Item 5)
Retire to Records Center when 2 years old.
Destroy when 10 years old.
6. Substitute Form Files.
Correspondence with practitioners, firms, and individuals relating to substitute forms for IRS official forms. Includes approval and disapprovals.
(Job No. NC–58–75–1, Item 13)
Destroy when 2 years old.
7. Information Systems Management Careers Program.
(1) Case files documenting the selection of incumbents for positions in the program. Files consist of evaluations and board members evaluation and criteria used in the selection. (Job No. NC–58–75–1, Item 15(1))
Destroy 2 years after selection.
  (2) Case files of individual applicants for positions in the program. Files consist of current application, evaluations and other pertinent documents as required.
(Job No. NC–58–75–1, Item 15(2))
Destroy 2 years after the latest update.
8. Administrative Management and Organization Records.
(1) These records include studies, analyses, or correspondence which establish policies, practices, and programs for the management of the Information Systems organization. Included are organizational changes in the field and National Office structure, functional realignments and responsibilities, long and short term planning documents. (Job No. NC–58–75–1, Item 1(1))
Cut off correspondence annually; studies and case files, upon completion of study or at an appropriate phase.
Retire to Records Center when 5 years old.
Destroy when 25 years old.
  (2) Record copies which document the history of the Information Systems Organization. These records include correspondence and case files of this type with analyses, coordinations, approvals and disapprovals, recommendations, plans and implementing instructions for the plans, and any background materials which contribute to an understanding of or provide an explanation for complete documents. (Job No. NC–58–75–1, Item 1(2)) PERMANENT.
Cut off annually or upon completion of a study.
Retire to Records Center when 5 years old or when no longer needed.
Transfer to NARA when 10 years old.
  (3) Reference copies of records listed in Items (1) and (2) above.
(Job No. NC–58–75–1, Item 1(3))
Destroy when 2 years old.
9. Study Group or Task Force Files.
(1) Records created as a result of studies initiated or sponsored by IS on issues or problems that have surfaced and resulted in national, regional, or local impact on the IRS or taxpayers. Examples are issues relating to tax processing operations; the filing season; major ADP procurement strategies; privacy and security of taxpayer data, telecommunications, and hardware architecture. (Job No. N1–58–97–4, Item 9)
 
  (a) Record copy of final reports, recommendations, implementation plans, briefing papers, presentation materials, publications, and related correspondence. PERMANENT.
Cut off
annually.
Retire to Records Center when 5 years old.
Transfer to NARA when 20 years old.
  (b) Working papers, background information produced by the study group or task force. Cut off annually.
Destroy when 3 years old.
  (2) Records produced by other study groups or task forces dealing with routine operations, automation, or administrative issues. Cut off annually.
Destroy when 5 years old.
10. Committee, Meeting, and Conference Records.
(1) These records are created or maintained by committees, boards, groups, or during meetings, conferences sponsored by the Chief Information Officer (CIO) or attended by the CIO with other IS and senior-level IRS executives, Department of Treasury or other government officials, and contractor personnel, as well as speeches delivered by the CIO. These records document significant decisions or discussions on policy; development/direction of tax systems modernization projects; budget; strategic planning; standards; tax processing operations; technology affecting information systems development and operations; and issues relating to systems architecture, integration, transition, security and privacy.
(Job No. N1–58–97–4, Item 10)
 
 
(a) Record copy of agendas, briefing papers, presentation materials, minutes, speeches, final reports or recommendations, and related correspondence.
PERMANENT.
Cut off
annually.
Retire to Records Center when 5 years old.
Transfer to NARA when 20 years old.
  (b) Logistical documentation created in preparation for each conference or meeting, i.e., notification packages, routine correspondence to participants, printing requests, and related records. Cut off annually.
Destroy when 2 years old or when no longer needed, whichever is sooner.
  (2) Records created or maintained by other committees or during other conferences and meetings dealing with routine operations or administrative issues. Cut off annually.
Destroy when 3 years old or when no longer needed, whichever is
sooner.
11. Congressional Testimony
Records.

Copies of testimony delivered by the Chief Information Officer to Congressional committees dealing with the status of Information Systems programs, projects or budget issues. Also included are working drafts, internal correspondence and background information gathered in preparation of each hearing. (Job No. N1–58–97–4, Item 11)
Note: Record copies of all congressional testimony are maintained by Legislative Affairs.
Cut off annually.
Destroy when no longer needed for operational purposes.
12. Reading Files.
(1) Copies of correspondence signed by the Chief Information Officer or the Deputy Chief Information Officer.
(Job No. N1–58–97–4, Item 12)
PERMANENT.
Cut off
annually.
Retire to Records Center when 2 years old.
Transfer to NARA when 20 years old.
  (2) All other reading files. Cut off annually.
Destroy when 2 years old or when no longer needed, whichever is sooner.
  Technical Records
13. Program Requirement Packages
(PRP).
Records consist of input and output data specifications and related processing formula involved in each procedure of an information system which are required and prepared for the development of computer programs for service centers, computing centers, regional and field offices.
 
  (1) IMF and BMF PRP’s—includes many sections, each of which pertains to a particular project in the data processing system. (Job No. NC–58–75–1, Item 31 (1)) Retire to Records Center 1 year after new PRP is received.
Destroy when 9 years old.
  (2) Functional Specification Package (FSP) contains many sections each of which deal with a subject area of the Service Center data processing system. (NOTE: Superseded FSP is placed in inactive file when complete). (Job No. NC–58–75–1, Item 31(2)) Retire to RecordsCenter 1 year after revision or supersession.
Destroy after 9 years old.
  (3) Special Project PRP’s (IMF and BMF related) --these are of a continuing nature and are updated periodically with a complete rewrite. (NOTE: Superseded FSP is placed in inactive file when complete). (Job. No. NC–58–75–1, Item 31(3)) Retire to RecordsCenter 1 year after revision or supersession.
Destroy when 9 years old.
  (4) Working and reference copies of PRP’s. (Job No. NC–58–75–1, Item 31(4)) Destroy when no longer needed for current operations.
14. Computer Program Books (CPB) for the IMF, BMF, and the Master File and service center, Data Center, regional or district offices related programs. Requirements as contained in the PRP’s. (Original, camera copy is maintained for updating).  
  (1) CPB 1 including run description and schematic diagrams (narrative and picture of flow of data through the programs in the system). (Job No. NC–58–75–1, Item 32(1)) Destroy 6 months after the last program in CPB is discontinued.
  (2) CPB 3 including Core Record Layouts. (Hard copy picture of the tape or card record). (Job No. NC–58–75–1, Item 32(2)) Destroy 3 months after the last program in CPB is discontinued.
  (3) CPB 5, detailed instructions for console operators running the computer programs. Includes operating instructions for I/O units, Set-up Switches, Halt List, and Message List. (Job No. NC–58–75–1, Item 32(4)) Destroy 3 months after the last program in the CPB is discontinued.
  (4) File search records. (Job No. NC–58–75–1, Item 32(19)) Destroy when inactive or when 6 months old, whichever is earlier.
  (5) Log of file search requests. (Job No. NC–58–75–1, Item 32(20)) Destroy when 6 years old.
  (6) Control Log Problem Definitions and Problem Evaluations (PEs) and copies of PEs generated in the field. (Job No. N1–058–97–4, Item 14(6)) Destroy when 2 years old.
15. Information Systems Equipment and System Requirements
Analyses and Evaluations
. Case files include procurement requests for authorities to lease or purchase equipment, and specifications for procurement and maintenance of equipment. (Job No. NC–58–75–1, Item 36).
Cut off annually or upon completion of the project.
Retire to Records Center after 5 years old.
Destroy when 15 years old.
16. Case Files of Information
Systems Equipment
Acceptability Testing
. Contain procedures and guidelines for testing, testing forms, interim and final reports of the test, and related correspondence. (Job No. NC–58–75–1, Item 37)
Cut off when test is completed or contractual requirements of the acceptance test have been met.
Retire to Records Center when 3 years old.
Destroy when 6 years old.
17. System Acceptability Test Documentation (SAT). Includes project folders, system test plans, predetermined results, test data, Problem Definitions, copies of supporting documentation, i.e., PRPs, Unified Work Requests, Computer Operator's Handbook, FSPs, Core Record Layouts, and End of Test Status Reports. (Job No. NC-58-75-1, Item 38.) Destroy 1 year after completion of test.
  A. Routine SAT Records  
  1. Paper copies.
(Job No. NC-58-75-1)
Destroy 1 year after completion of test.
  2. Electronic Source Records (e-mail or word processing) used to create/produce the recordkeeping copy.
(Job No. N1-58-99-2)
Destroy/Delete or Overwrite when recordkeeping copy is produced.
  B. Year 2000 SAT Records  
  1. Paper copies. Destroy 1 year after obtaining year 2000 certification.
  2. Electronic Source Records (e-mail or word processing) used to create/produce the recordkeeping copy.
(Job No. N1-58-99-2)
Destroy/Delete or Overwrite after recordkeeping copy has been produced.
  C. Year 2000 Reports  
  Weekly, monthly, quarterly, and yearly progress reports, plans, and documentation which provide Year 2000 conversion century date change activities, contingency procedures, expenditure of funds, and other reports documenting Year 2000 conversion activities, [including, but not limited to, Treasury Reports, Projects Management Plan Reports, etc.]
(Job No. N1-58-99-2)
 
  1. Paper copies. Cut off files annually.
Retire
to Records Center when 1 year old.
Destroy when 5 years old.
  2. Electronic Source Records (e-mail or word processing) used to create/produce the record keeping copy. Destroy/Delete or Overwrite when recordkeeping copy is produced.
18. Quality Review Feedback Sheet
(Report 30(242)0–2).
A feedback sheet is prepared for each discrepancy. The discrepancy will be concisely documented and categorized by Scheduling, Tape Library, and Operations. Each feedback sheet will be assigned a Quality Review Control Number, which will be used to track, control, and file the sheets. The sheets will be used as a turn-around document for Information Systems management to provide corrective action to quality review function. Media: Paper; Location: Service Center. (Job No. N1–58–93–5, Item 14)
Destroy when 5 years old.
19. Tax Processing Systems
Software and Database Design
Programming Documentation Records.

developed and maintained for service center mainframe operating/security systems, telecommunications, transaction processing, and program transmittal software. All programs support National and field operations. Records include instructions or guidelines establishing program objective, programming requirements, documentation, design specifications, data dictionaries and related records. (Job No. N1–58–97–4, Item 19)
Destroy when no longer needed for current operations.
20. Tax Processing Systems and
Administrative Systems Project
Files.
Each system initiated by the IRS evolves in the three phases of the systems life cycle, i.e., the initiation phase, design or development phase, and implementation phase. These files contain records which have been created, updated, or finalized by IRS or contractor personnel who are developing new systems or making enhancements to existing systems. All of the documents described below may not be created for every system. (Job No. N1–58–97–4, Item 20)
 
  (1) Initiation Phase Documentation. These records are created and maintained during the initiation phase of a system. Examples include, but are not limited to, the following: Project Initiation Document, Charter, Approved Project Master Plan, Resource Agreements, Requirements Analysis, Business Case Analysis, Cost Benefit/Economic Analysis, Request for Human Resources Service, Agency Procurement Request, Delegation of Procurement Authority, Feasibility Study, other contractor deliverables, and all related correspondence. A. PERMANENT.Documentation for administrative systems appraised as permanent.
Transfer
to NARA with the system.
B. Documentation for tax processing and administrative systems appraised as temporary.
Cut off files annually.
Retire to Records Center when 5 years old.
Destroy when 10 years old.
  (2) Design/Development Phase Documentation. These records are created and maintained during the design and development phase of a system. Examples include, but are not limited to, the following: Analysis Specification Package, Functional Specification Package, Work Breakdown Structure, Source Code, Program Listings, Database Specifications, Version Description Documents, Configuration Management Policy, Plan, and Baseline Documents, Critical Design Review Documents, Contract Change Requests/Modifications, System Architecture Documents, Training Manuals/User Handbooks, System Administrator Guide, Technical Reference Manuals, System Test Plan, Prototyping Candidate Evaluation, Prototyping Plan, Statement of Work, Acquisition Plan, Performance and Capability Validation Plan, Risk Analysis/Contingency Plan, System Security Certification, Security Evaluation Report, Investment Evaluation Review Report, Capacity Management Plan, Telecommunications Plan, Site Preparation Requirements/Plan, other contractor deliverables, status reports, and all related correspondence. A. PERMANENT. Documentation for administrative systems appraised as permanent. Transfer to NARA with system.

B. Documentation for tax processing and administrative systems appraised as temporary.
Cut off files annually.
Retire to Records Center when 5 years old.
Destroy when 10 years old.
  (3) Implementation/Operation Phase Documentation.
These records are created and maintained prior to the implementation of a system. Examples include, but are not limited to, the following: Decision to Implement, Implementation plan/schedule, Hardware Installation Guide, Hardware Acceptance Test Checklist, System Implementation & Testing Documents, Test Contingency Plan and Post-Implementation Review Reports, other contractor deliverables, status reports, and related correspondence.
A. PERMANENT. Documentation for administrative systems appraised as permanent. Transfer to NARA with the system.

B. Documentation for tax processing and administrative systems appraised as temporary.
Cut off files annually.
Retire to Records Center when 5 years old.
Destroy when 10 years old.
21. Unified Work Requests.
Memoranda from organizational components requesting programming changes to current and planned computer systems. Requests set forth system requirements and is used by IS as the basis for planning, estimating, performing and tracking a project's software activity, as well as the overall management of IS plans and resources. (Job No. N1-58-97-4, Item 21)
 
  (1) Original requests and related correspondence. Cut off files at completion of project.
Retire to Records Center when 3 years old.
Destroy when 6 years old.
  (2) All other copies and related correspondence. Cut off at the end of the fiscal year.
Destroy when no longer needed, not to exceed 3 years.
22. Electronic Return File
Specifications and Record
Layouts for Individual Tax
Returns (Publication 1346).

Publication 1346 outlines the communications procedures, transmission formats, character sets, validation criteria, and reject codes for filing individual tax returns electronically via telephone lines to participating Internal Revenue service centers. (Job No. N1–58 –97–4, Item 22)
 
  (1) Copies of IMF forms, schedules, and instructions used to update Publication 1346. Destroy when 2 years old or when no longer needed, whichever is sooner.
  (2) All other copies, including working drafts, background information. Destroy when 2 years old or when no longer needed, whichever is sooner.
23. Information Technology Assets Management System (ITAMS). This system provides an integrated solution to inventory management of all IRS ADP hardware and software, network configuration management and IS problem management at Computing/Service Centers. All data is entered through interactive, real time, screen displays. An additional inventory interface exists through the use of a hand-held barcode scanner that reads labels for the purpose of performing inventory certification. Inventory records are recorded from the time of purchase to the time of disposal. (Job No. N1–58–97–4, Item 23) The database contains the following components:  
  (1) Operator/User Profile
Database. The database contains records concerning the user’s name, ID, password, location, phone number, organization, security level, and query time limits.
Delete record from database immediately upon notification that access to the system is no longer required.
  (a) Input Records. These records include source documents used to collect information on adding and deleting system users, i.e., name, location, phone number, organization. Destroy when 1 year old or when no longer needed for operational purposes, whichever is sooner.
  (b) Output Records. These records include management information reports and audit trail or equivalent documentation. Destroy/Delete from database when 1 year old or when no longer needed for operational purposes, whichever is sooner.
  (2) Inventory Management
Database. The database contains information describing hardware and software in the inventory by barcode numbers, serial numbers, manufacturer’s name, model numbers, device type, location, disposal codes and date, procurement, maintenance, and depreciation information.
Delete 2 fiscal years after disposal date.
  (a) Input Records. These records include source documents used to collect information describing the hardware/software and location information, as well as the final disposition documents. Note: Baseline data resulted from conversion of data from previous inventory system. Destroy when 1 year old or when no longer needed for operational purposes, whichever is sooner.
  (b) Output Records. These records include management information reports, program-related reports, ad hoc queries, and audit trail or equivalent documentation in electronic or hard copy formats. Delete/Destroy from database when 1 year old or when no longer needed for operational purposes, whichever is sooner.
  (3) Network Configuration
Management Database. The database contains records describing the physical and logical connections through parent/child linking of ADP equipment via a Local Area Network (LAN) or a Wide Area Network (WAN), i.e., bridge/routers, circuits, front end processor, cable interface, software, switches, and workstations.
Delete 2 fiscal years after the disposal date.
  (a) Input Records. These records include source documents used to collect information describing the hardware/software and location information, as well as final disposition documents. Destroy when 1 year old or when no longer needed for operational purposes, whichever is sooner.
  Note: Baseline data resulted from conversion of data from previous inventory system.  
  (b) Output Records. These records include management information reports, program-related reports, ad hoc queries, and audit trail or equivalent documentation in electronic or hard copy formats. Delete/Destroy when 1 year old or when no longer needed for operational purposes, whichever is sooner.
  (4) Problem Management
Database. The database contains records on Computing/Service Center problems by ticket number (generated by the system), name, phone and location of person reporting problem, priority code, description of problem, actions taken to resolve and date resolved, identification of the piece of equipment, software, or other appropriate identifier related to the problem occurring.
Delete 3 years after date of problem resolution.
  (a) Input Records. This data is input directly to the system and documents the date and time the problem was reported, name and location of reporting party, date and time problem occurred, system or application affected, description of the problem. Delete 3 years after date of problem resolution.
  (b) Output Records. These records include information reports, program-related reports, ad hoc queries, and audit trail or equivalent documentation in electronic or hard copy formats. Delete/Destroy when 1 year old or when no longer needed for administrative, legal, audit or other operational purposes.
  (5) System Documentation Records. These records include Inventory Management Overview Guide, User Reference Guide, Data Dictionary, File Layouts, Training Manual, procedural guides, and System Design and Analysis Manual. Destroy/Delete when superseded or obsolete.
24. Quarterly Century Date Change Joint Appropriations Committee Report. This report to Congress provides project progress status, overall strategy progress, and expenditure of funds and full time equivalents. (Job No. N1-58-00-2)  
  (a) Paper. Cut off annually.
Retire to Records Center 5 years after cutoff.
Destroy
20 years after cut off.
  (b) Electronic Source Records (email or word processing) used to create/produce the recordkeeping copy. Destroy/Delete, or Overwrite when recordkeeping copy is produced.
25. IRS.gov Website. The website is available to the public and contains tax information for individuals, business, pension plans, Government entities, tax professionals, and non-profits. It has tax statistics, forms and publications, and a way for taxpayers to find out about their refunds. (Job No. N1-58-06-1)  
  (1) Web Management and Operations Records. Include records such as help desk reports and contact logs; meeting minutes, status reports, change requests and other artifacts of the Requirements Traceability Matrix (RTM). Destroy/Delete 6 years after processing year or when superseded, obsolete or no longer needed for the conduct of Agency business, whichever is later.
  (2) Web content records and records that can be used as evidence of content.  
  (a) HTML-Encoded Pages, PDF files and code changes; Site "snapshots" and comprehensive URL listings; CMA guidelines, style guides, Interim guidance, web applications such as Installment Agreement Calculator and Excise Tax including their requirements and design documents. Destroy/Delete 20 years after processing year or when superseded, obsolete or no longer needed for the conduct of Agency business, whichever is later.
  (b) Copyrighted web content and agreements; Web Design documents and application development records; Web metrics data including web trends and other web traffic reports. Destroy/Delete 6 after processing year or when superseded, obsolete or no longer needed for the conduct of Agency business, whichever is later.

Exhibit 1.15.17-2  (02-23-2009)
Alphabetical Listing for Information Technology

  Description of Item Item No.
  Acceptability Tests 16,17
  Administrative Housekeeping Records 1
  Administrative Organization Records 8
  Administrative and Tax Processing Systems Project Files 20
  Annual Business Review 2
  Audit Reports 3
  Committee, Meeting, and Conference Records 10
  Computer Program Books (CPB) 14
  Congressional Testimony Records 11
  Correspondence Files 1-4,6,8-12,16,20,21
  Database and Software Design 19
  Electronic Return File Specifications and Record Layouts for Individual Tax Returns 22
  Equipment Acceptability Testing 16
  Equipment and System Requirements Analyses and Evaluations 15
  Forms and Form Letters 5,6
  Functional Specification Package (FSP) 13(2),17
  GAO Reports 4
  Individual Tax Returns (Specifications and Record Layouts) 22
  Information Technology Assets Management System (ITAMS) 23
  Management Careers Program 7
  Meeting Records 10
  Program Requirement Packages (PRP) 13,17
  Programming Documentation (Software and Database Design) 19
  Project Files (Tax Processing Systems and Administrative Systems) 20
  Quality Review Feedback Sheet 18
  Quarterly Century Date Change Joint Appropriations Committee Report 24
  Reading Files 12
  Record Layouts and Specifications (for Individual Tax Returns) 22
  Reports 2-4,9,10,16-18,20,23-25
  Software and Database Design 19
  Study Group or Task Force Files 9
  Substitute Form Files 6
  System Acceptability Test (SAT) Documentation 17
  Task Force or Study Group Files 9
  Tax Processing and Administrative Systems Project Files 20
  Tax Processing Systems Software and Database Design Programming Documentation 19
  Treasury Inspector General for Tax Administration (TIGTA) Audit Reports 3
  Unified Work Requests 17,21
  Website (IRS.gov) 25

Exhibit 1.15.17-3  (02-23-2009)
Forms Listing for Information Technology

Form No. Title Item No.
5715 Systems Production Evaluation Report 21
9216 Program Warranty Procedures (PWP) Checklist 16
9218 Efficiency Test Report 17A
9224 Generic Code Inspection Checklist 18
9225 Structured COBOL Code Inspection Checklist 13(3)
9796 FSP/PRP Registration, Update and System Identification 13(3)
10068 Project Change Request 13(3)
10524 Security Accreditation for New System 20(3)
10888 Request for ADP Assistance 13(3)
13089 Hardware – Software Configuration 14
Obsolete Forms:
4537 Roster of Eligibles for Promotion and Promotion Certificate 7
9556 System Change Request (SCR) Input Record 14(6)
9557 System Change Request (SCR) Comment Input Record 14(6)

More Internal Revenue Manual