RFI Number: 5000186136 Project Title / Short Description: Brand name Notice Delivery System’s (NDS) PSC: DA01 NAICS Code: 541511 Release Date: 08/31/2024. Response Date: 09/04/2024 Primary Point of Contact: Lincoln Capstick email
[email protected] Secondary Point of Contact: Greg Lombardozzi email
[email protected] Introduction: This is a Request for Information (RFI). This is NOT a solicitation for proposals, proposal abstracts, request for bids or quotations, or a promise to issue a solicitation in the future. Description: Internal Revenue Service (IRS) Correspondence Production Services (CPS) organization operates the Notice Delivery System’s (NDS) which is a business-owned application for the management of IRS’s system generated taxpayer mail production. NDS provides control over all tax notice print and distribution currently processes at the two CPS sites in Detroit, Michigan and Ogden, Utah, soon to have the third site started in Bloomington, Illinois. Production includes file receipts and management, piece level control, printing, inserting, and mailing, as well as integration control with future alternative delivery solutions such as electronic (e-mail) and fax delivery. The system has been in place since 2001 and has received many enhancements. The most recent enhancement was Taxpayer Correspondence Delivery Tracking (TCDT). It encoded Intelligent Mail Barcodes (IMBs) to store outgoing data on first-class mail, receive data from the United States Postal Services (USPS), store and match the data then forward selective elements to other IRS systems. Do any vendors supply NDS? Requested Information: In accordance with FAR 16.505, for brand name items, the Government must determine whether other companies’ similar products meet, or can be modified to meet, the agency’s needs. Interested parties are requested to submit statements on the capability of software maintenance products for NDS, that can meet the Government’s requirement within 3 business days (by COB Wednesday September 4, 2024). Note: NDS software resellers are requested to respond to this RFI. The capability statement shall include: Name of vendor Name of software maintenance manufacturer/publisher Name of software maintenance suite List of line items with descriptions, part numbers, and price Features/Spec Sheet License agreement Product availability Any other information demonstrating software capability. Terms and Conditions regarding this RFI: This RFI does not obligate the Government to award a contract or otherwise pay for the information provided in response. All costs associated with responding to this RFI are solely at the responding party's expense. Any organization responding to this RFI for software brands similar to NDS should ensure that its response is complete and sufficiently detailed to allow the Government to determine software maintenance capability relative the Government’s requirement. No proprietary, classified, confidential, or sensitive information should be included in responses to this RFI for commercially available software. NDS Requirements Job hold and release capability . The contractor shall provide functionality to hold and release jobs, both manually and automatically. Review actions . The contractor shall provide multiple configurable actions, “review and hold” or “sample and release”. PDF file generation . The contractor shall provide an overlay text or image on the PDF indicating that it should not be mailed. Centralized hold job manager . The contractor shall provide a central held job manager that lists all jobs currently held. Hold job management . The contractor shall implement hold job management functionality that is in the NDS GUI being general in nature and not necessarily specific to review or sampling. SLA adjustment . The contractor shall provide the functionality adjust any job’s SLA. Reports . The contractor shall provide the ability to produce specific reports for job hold and review activity. The contractor shall establish a new table in NDS to manage notice type attributes, similar to how class type and job type attributes are managed. The contractor shall create a single notice type attribute named NoticeType.SecureDestruction.Enabled specific to enabling secure destruction for notice types. The contractor shall create a new tab in Data Manager named "Secure Destruction" with a new panel to support setting the NoticeType.SecureDestruction.Enabled attribute for notice types. The contractor shall provide this new panel is specific to managing secure destruction as opposed to a general attribute management panel, such as class types and job types use. This is done for usability reasons, so notice types can be multi-selected and enabled/disabled in bulk. The contractor shall provide a panel that lists all notice types defined to the system, with the current secure destruction enablement state, along with the usual audit information. Buttons are provided to enable or disable secure destruction for one or more selected notice types. The contractor shall annotate that this panel does not have the ability to add or remove notice types, this is intentional. Notice types are added elsewhere, specifically in the existing “Notice Types” tab, when notice type recognition is manual, and by the Index step when it is automatic. Notices types automatically show up in the new panel when added with secure destruction initially disabled. Capability Staments should be sent by email to the Contracts Specialist Lincoln Capstick at
[email protected]