Integrated Production Model (IPM)
Purpose of the System:
The Integrated Production Model (IPM) will provide various types of data to a number of compliance systems in the IRS. The data will include data from sources including the Master files (e.g. individual master file or IMF, Business Master file or BMF), the Return Transaction Files or RTFs, Transaction Data, third party data including information from SSA, HHS and Address information from Choicepoint, Employee Plans Information, Information Returns data, case information, large dollar cash transaction data, North American Industry Classification Code System (NAICS) data from the National Institute for Standards and Technology (NIST), State workforce agency data, demographics data and Census data. The data will be made available to compliance projects and programs to increase the efficiency of those programs. Efficiencies will be realized in two ways. The first is that client projects and programs will be able utilize the data that has been gathered on the IPM without having to create another data store saving considerable development and maintenance costs. The second is that the development time from concept to implementation will be shortened.
- Describe the information (data elements and fields) available in the system in the following categories:
- Taxpayer
- Source: BMF-DB2 & BMF
- Data Elements: BMF Entities; Tax Modules; Entity Transactions; Tax Return Transactions; Tax Return Statuses
- Source: BRTF
- Data Elements: Transcribed sections of Business Tax Returns: Forms 941 & 943
- Source: CAWR
- Data Elements: Wage Related Documents from SSA<.li>
- Source: DM-1
- Data Elements: Name Control; Date of Death; Birth Data; Citizenship Indicator
- Source: EPMF-DB2
- Data Elements: Employee Plan Master File Entities and Tax Modules
- Source: IRMF & PMF
- Data Elements: Information Return Documents; and Payer Documents
- Sources: IRMF & PMF
- Data Elements: Information Return Documents and Payer Documents
- Employee
- There is no Employee data stored on the system for Release 1.1.
- Audit Trail Information (including employee log-in info)
- Audit trails will be created using Oracle 10g auditing features. There are no individual End Users, however Audit Trails for Client Application access to IPM will be added to the PIA at future Milestones, as developed.
- Other (Describe)
- There is no Other data stored on the system for Release 1.1.
- Describe/identify which data elements are obtained from files, databases, individuals, or any other sources.
- IRS
IPM Release 1.1 will include data from the following Sources:
- Business Master File Database (BMF-DB2) – IRS Database
- Business Master File (BMF) – IRS Tier 1 Repository
- Business Return Transaction File (BRTF) – IRS Tier 1 Repository
- Combined Annual Wage Reporting (CAWR) – IRS Tier 1 Repository of wage related documents from SSA
- Data Master – 1 (DM-1) – IRS Tier 1 Repository
- Employee Plan Master File (EPMF-DB2) – IRS Database
- Information Returns Master File (IRMF) – IRS Tier 1 Repository
- Payer Master File (PMF) – IRS Tier 1 Repository
- Taxpayer
No data is received directly from Taxpayers, as all taxpayer information from is secured from an IRS source as listed in A. above.
- Employee
No data is received directly from Employees, as there is no direct employee access to the system
- Other Federal Agencies (List agency)
No data is received directly from other federal agencies.
- State and Local Agencies (List agency)
No data is received directly from State and Local Agencies.
- Other third party sources (Describe)
No data is received directly from other third party sources.
- Is each data item required for the business purpose of the system? Explain.
Yes. The system is designed to serve as a common data repository for a number of client projects and system. All of the information identified as being required for IPM was derived by reviewing the client applications needs.
- How will each data item be verified for accuracy, timeliness, and completeness?
Data contained in IPM comes from IRS authoritative sources which IPM relies on for accuracy. Data record element fields which are input to the Data Preparation component have already been extensively validated by their respective components. For example, delinquency data obtained from Business Master File has already been validated by that system.
Run-to-run balancing controls will be maintained by all programs which extract data for the IPM. The Log Accounting Reporting System (LARS) will be utilized to maintain control totals.
All Data Loads will employ the following Data Validation Rules:
- BMF and EPMF data is loaded as is from the master files on DB2. The exception to this is that any data that is acceptable on Tier I (DB2), but not acceptable on Tier II (Oracle), will be nulled.
For all other sources:
- When a value that is to be loaded into a DATE formatted attribute is found to be invalid, the value of the attribute is set to “null”. The SSA_DM1_REF table is an exception. Dates from SSA are loaded as received since some are know to be invalid.
- When a value that is to be loaded into a NUMERICAL formatted attribute is found to be invalid, the value of the attribute is set to “null”.
- When a new attribute is added to a table, the value of that attribute will be null in any rows that were already on the database.
- Right Trim (RTRIM) is used on all Name and Address attributes as well as the Condition Code Field and City attributes to conserve space on these variable length fields. Spaces to the right of the last significant character in these attributes are set to null.
- Money fields are represented as taken from the master files, dollars only or dollars and cents depending on the legacy field definition.
- Is there another source for the data? Explain how that source is or is not used.
IPM extracts data from various internal authoritative sources into a centralized location. These authoritative sources, as listed in Question 2, are the original sources of the data contained in IPM, however, there is no other source that centralizes this data into one database.
- Generally, how will data be retrieved by the user?
Individual users will not have access to the IPM to retrieve data. The system’s design is that it will be a data repository that will be accessed by client applications through a direct link. All IPM DB using applications will connect to IPM via an application to DB connection. There is no direct IPM User Interface. The design of the using application to IPM DB interface is the responsibility of the using application.
- Is the data retrievable by a personal identifier such as name, SSN, or other unique identifier?
Yes, data is retrievable by TIN: SSN; EIN. The client projects will build queries that will be run against IPM to retrieve data that fits the queries. These queries can contain personal identifiers.
Access to the Data
- Who will have access to the data in the system (Users, Managers, System Administrators, Developers, Others)?
System and Database Administrators will have access to maintain the system. Developers will have access to the development system and read access to the production domain to check tables. Testers will have access to the test development system.
Database Administrators, System Administrators, Developers and Project Account Managers will be granted access via OL5081 process. As is stated above, the primary access to the system will be approved client applications. Users will gain access to the IPM data by way of these client applications designed to grant access.
- How is access to the data by a user determined and by whom?
IPM will have no individual end users with access to the data. Individual user data access will be determined at the client application level, with access controlled by the user’s manager via the OL5081.
- Do other IRS systems provide, receive, or share data in the system? If YES, list the system(s) and describe which data is shared. If NO, continue to Question 12.
The IPM will receive data from a number of systems. For release 1.1, the data sources will be BMF, BRTF, PMF, IRMF, EPMF, CAWR, and DM-1. Each of these items is detailed in Question 2 above.
The IPM is designed to be a data repository. IPM will serve Multiple client projects. For Release 1.1, IPM will serve BMF CCNIP.
Future client connections to IPM will be submitted as a change request (CR). The client CR will then be reviewed for approval and security impact by the IPM Configuration Control Board (CCB), which will also include members from Cybersecurity, ITSAE, and Systems Architecture and Engineering. Access to the IPM system can not occur until IPM is in production.
- Have the IRS systems described in Item 10 received an approved Security Certification and Privacy Impact Assessment?
At Release 1.1 BMF CCNIP is expected to have achieved security certification and have access to the IPM. The remaining client applications are in development and have not achieved security certification.
No client applications will be allowed access to the IPM without an approved Security Certification and Accreditation.>br />
- Will other agencies provide, receive, or share data in any form with this system?
IPM will receive data from wage related documents from SSA, as listed in 1A. above, however, the source of this data for IPM CAWR which is internal IRS System.
Administrative Controls of Data
- What are the procedures for eliminating the data at the end of the retention period?
IPM does not contain original documents or data and is not the authoritative source for data. The data loaded into IPM from the various data sources listed in this questionnaire will be updated with current information from weekly, monthly or annual loads.
W–4 paper case files and National Computer Center (NCC) magnetic tape records are destroyed two years after the cases have been inactive. Records associated with the examination of returns are disposed of in accordance with the established Retention Schedule 1(15)59.22, Records Control Schedule. Records not associated with the examination of returns will be destroyed at the completion of the program or project, or in accordance with Records Disposition Handbooks, IRM 1.15.2.1 through IRM 1.15.2.31.
- Will this system use technology in a new way? If "YES" describe. If "NO" go to Question 15.
No. The IPM will used IRS Enterprise Architecture approved systems and software to store data compliance related data in a format that is easily accessed by the client applications
- Will this system be used to identify or locate individuals or groups? If so, describe the business purpose for this capability.
Yes. The client applications will access data from the IPM that will be matched against their business rules that will include case selection. The business purpose for this capability is to ensure that taxpayers are compliant in their tax obligations. The system will be used to address tax gap issues.
- Will this system provide the capability to monitor individuals or groups? If yes, describe the business purpose for this capability and the controls established to prevent unauthorized monitoring.
The IPM will be designed to allow compliance functions to identify non compliant taxpayers. The system is not designed to monitor individuals or groups except for those taxpayers or groups of taxpayers who are non compliant.
- Can use of the system allow IRS to treat taxpayers, employees, or others, differently? Explain.
The IPM will be designed to allow compliance functions to identify non compliant taxpayers. The system is not designed to nor will it contain information on Race, Gender, Sexual Preference, or any other issue not related to tax compliance.
- Does the system ensure "due process" by allowing affected parties to respond to any negative determination, prior to final action?
The system does not make determinations negative or otherwise. These actions are in the purview of the client applications and ensuring “due process” is the responsibility of these client applications.
- If the system is web-based, does it use persistent cookies or other tracking devices to identify web visitors?
The system is not web based.
|