SOLICITATION NOTICE
70 -- Alternative Analysis for ASFR-EASE (F&PC Domain)
- Notice Date
- 5/30/2008
- Notice Type
- Presolicitation
- NAICS
- 334113
— Computer Terminal Manufacturing
- Contracting Office
- Department of the Treasury, Internal Revenue Service (IRS), National Office Procurement (OS:A:P), 6009 Oxon Hill Road, Suite 500, Oxon Hill, Maryland, 20745
- ZIP Code
- 20745
- Solicitation Number
- IRS-RFI-ASFR-EASE-PROJECT
- Archive Date
- 7/15/2008
- Point of Contact
- David F Smith III,, Phone: 202-283-1456
- E-Mail Address
-
david.f.smith@irs.gov
- Small Business Set-Aside
- N/A
- Description
- IRS ASFR-EASE Project Request for Information The purpose of the Request for Information (RFI) is for information and planning purposes only and to assist the IRS in considering the use Commercial Off the Shelf (COTS) products for implementation of the modernized version of the Automated Substitute for Return (ASFR) system currently in use today. Your response to this RFI will be used to make a determination on the IRS’ potential use of COTS product as an alternative to custom development. Current System Description: ASFR is a batch system written in the COBOL language. Essentially, this system works with individual taxpayers that have been identified as “non-filers” by other IRS systems. These other systems provide basic account information for a taxpayer based on third-party filings such as W-2s, 1099s, etc. ASFR has several functions, broadly defined as follows: 1. Preparing a substitute return on the taxpayer’s behalf. 2. Generating letter content for letters to taxpayers as defined by federal statute. 3. Tracking calls from the taxpayer regarding the return substitute. 4. Tracking correspondence to and from the taxpayer regarding the return substitute, including undeliverable correspondence. 5. Finalizing the return substitute as an official tax return. 6. Reconciling the return substitute with an actual tax return subsequently filed by the taxpayer. 7. Posting transaction codes to other IRS systems as needed to reflect changes in status of the return substitute and taxpayer’s account. 8. Limited executive reporting. Aspects of a Successful Modernized System: The modernized system being proposed has several key capabilities. The new system will be a complete “rewrite” of the old system, keeping the current business functionality and adding a modest amount of new business capabilities. The ASFR-EASE project is envisioned as a multi-release effort over several years. IRS views elements of a successful ASFR-EASE system as follows: (a) Conforms to the target Enterprise Architecture. (b) Provides the ability to change business rules in a dynamic fashion by non-technical users. (c) Provides a real-time web-based interface. (d) Available to a wider internal IRS audience. (e) Utilizes modern RDBMS databases. (f) Supports Web Services. (g) Utilizes modern reporting tools. (h) Supports IRS single sign-on technology. (i) Shortens or eliminates batch cycles in use today. (j) Is expandable consistent with future release plans. (k) Integrates with other case management solutions. (l) Integrates with IRS document management strategies (Documentum). Application Requirements: Much of the evaluation criteria center around application requirements as documented in this section. These requirements are separated by broad categories in the sections that follow: Enterprise Architecture Requirements (EA): It is beyond the scope of this analysis to list all Enterprise Architecture (EA) requirements. These may be found in the IRS Enterprise Architecture. For evaluation purposes, the evaluation team will look at the following aspects of the proposed solution in terms of the IRS Enterprise Architecture: (1) Solution must operate in one of the approved operating environments. These include either Sun Solaris or Microsoft server environments. (2) Solution must utilize an Oracle database if operating in a Solaris environment or the MS SQL Server database if operating in a Microsoft environment. (3) Data maintained by the system must be able to use Business Objects for reporting. (4) Solution must support Services Oriented Architecture with real-time integration with a WebMethods Integration Broker. (5) Solution must integrate with an IRS Portal architecture, which provides for user authentication and authorization Other Technical Requirements. The Enterprise Architecture only covers a portion of technical requirements for the project. These requirements also apply to ASFR-EASE: (a) Solution must be able to access external Oracle databases for reference information. (b) Solution must be able to access “flat” files for data feeds by utilizing an EA-compliant ETL tool (e.g. Informatica) (c) Solution must be able to reasonably handle 500 concurrent users. There are approximately 1500 users in the universe. (d) Solution must have the ability to recognize duplicate customer records. (e) Solution must have capability of creating a best-of-breed record from multiple source records. Project Requirements This section contains formalized requirements based on the introductory material submitted elsewhere. Respondents are encouraged to make a copy of these tables and respond to each requirement. IDRequirement Interfaces INT1The system shall support interfaces with other IRS systems using Service Oriented Architecture INT1.1The system shall support WebMethods SOA messaging using SOAP XML messages via IBM WebSphere, MQ or HTTPS. INT2The system shall support flat (ASCII) files as input. Availability/Access ACC1Full Services: hours of operation from 6:00AM to 2:00AM local time on weekdays. ACC2The system will be available only to IRS employees. Reporting REP1The system shall generate various reports using Business Objects. General Technical Requirements TECH1The system shall support a database of approximately 1Tb in size. TECH2The system shall be compliant with the IRS Enterprise Architecture. TECH3The system shall support at least 500 concurrent users. TECH4The system shall support export of internal data to support ETL activities. Business Capabilities BUS1ASFR-EASE needs the ability to manage workflow. BUS1.1Ability for certain users to select and assign cases based on definable elements BUS1.2Query ability on specific segment of inventory, and integration of data from separate systems to formulate prioritization and selection of cases to be started. BUS1.3Track specific cases through-out the ASFR process based on definable elements BUS1.4Ability to report on inventory, case status BUS1.5Ability to track workload of each CSR handling cases. BUS1.6Ability to generate robust and ad hoc reporting including generating reports that filter and display selected fields BUS1.7Ability to define or modify business rules and development of parameters that will reduce WRs BUS1.8Provide error notification for attempted workflow actions that violate business rules. BUS2System must support multiple user role based access BUS3System will support a flexible way to change business-rules in a manner that does not require programming support. BUS4ASFR-EASE needs the ability to process current ASFR inventory BUS4.1Ability to calculate proposed tax liability, penalty and interest based on IRP BUS4.2Ability to generate ASFR correspondence: BUS4.5Ability to Correct IRP BUS4.6Ability to Archive Closed Cases Timeframes This project will be implemented in FY10 or FY11. The NAICS code for this requirement will be 334113. NOTE: This notice is for planning purposes only. Responses shall not exceed 10 pages and must include the following: (1) Name and address of firm; (2) Size of business, indicating whether: Large, Small, Small Disadvantaged, 8(a), Women-Owned, HUBZone, Veteran-Owned and/or Service-Disabled-Veteran-Owned Business including: Average annual revenue for past three years and Number of employees; (3) Ownership (including Country of Ownership) and Central Contractor Registration (CCR) information; (4) Number of years in business; (5) Two points of contact, including: name, title, phone, fax, and e-mail address; (6) DUNS Number; (7) Affiliate information: parent corporation, joint venture partners, potential teaming partners, prime contractor (if potential subcontractor) or subcontractors (if potential prime); (8) Product information, including cost, that identifies the vendor’s proposed COTS product and it’s ability to meet the requirements listed above. Responses shall be submitted via e-mail or fax to david.f.smith@irs.gov, fax number (202)283-1290 or by mail to IRS National Office Procurement, 6009 Oxon Hill Road, Suite 500, Oxon Hill, MD 20745, Attn: David F. Smith III, OS:A:P:I:D:B. This information is for research and planning purposes only and is not a commitment by the Government. This is not a solicitation for proposals and no contract will be awarded as a result of the information obtained from this synopsis. No reimbursement will be made for any costs associated with providing information in response to this synopsis, or any follow-up information requests. Respondents will not be notified of the results of the evaluation. All response must be received by 5:00 p.m. EST, Monday, June 30, 2008. The reference number for this request is IRS-RFI-ASFR-EASE-PROJECT.
- Web Link
-
FedBizOpps Complete View
(https://www.fbo.gov/?s=opportunity&mode=form&id=fe91538aab21ae61863747c7ead85458&tab=core&_cview=1)
- Place of Performance
- Address: Internal Revenue Service, 5000 Ellin Road, Lanham, Maryland, 20706, United States
- Zip Code: 20706
- Zip Code: 20706
- Record
- SN01583938-W 20080601/080530220700-fe91538aab21ae61863747c7ead85458 (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |