SOURCES SOUGHT
70 -- Correspondence Tracking Application
- Notice Date
- 7/11/2011
- Notice Type
- Sources Sought
- NAICS
- 541511
— Custom Computer Programming Services
- Contracting Office
- Securities and Exchange Commission, Office of Acquisitions, Operations Center, 6432 General Green Way, MS 0-20, Alexandria, Virginia, 22312-2413, United States
- ZIP Code
- 22312-2413
- Solicitation Number
- SECHQ1-2011-OITSB
- Archive Date
- 8/2/2011
- Point of Contact
- Reginald Barnes,
- E-Mail Address
-
barnesr@sec.gov
(barnesr@sec.gov)
- Small Business Set-Aside
- N/A
- Description
- INTRODUCTION The U.S. Securities and Exchange Commission (SEC) is seeking information on a solution for a correspondence tracking application that will support the work of the agency in efficiently and effectively in responding to written correspondences. BACKGROUND The U.S. Securities and Exchange Commission (the commission) currently uses several different applications to track incoming correspondence and outgoing responses. However these applications have limited interconnectivity between the systems. The combination of systems currently being used includes in-house developed correspondence tracking systems, commercially available SharePoint technology and a Sales Force application to track incoming and outgoing correspondences. SCOPE OF REQUEST FOR INFORMATION The Commission seeks information regarding an integrated solution with key features to include correspondence tracking, document management and workflow management to replace the current correspondence tracking system. The upgraded application should possess several important functionalities, as outlined below: • The application must be able to track the incoming correspondence from initial receipt to the final response; • The application should facilitate the routing of the correspondence to the appropriate office or division with subject matter expertise within the Commission. From there, the draft response should be routed for approval or edit to other offices or divisions with roles in the response as appropriate; • At any point during the process staff should be able to determine the location of the response and the office/individual with possession/edit authority of the response; • The application must be able to store and catalog all incoming correspondence and the associated responses, including archiving the response as sent; • The application should facilitate collation by correspondent and/or constituent, date received, deadline to respond, current location, originating office within the Commission, final disposition, issue and subject; • The application should allow for staff to track changes on the response through the approval process with an internal content management function or with connectivity to existing Commission content management systems; • The administrator of the application must be able to compartmentalize the information seen or accessed by the various users, so that access can be restricted to only offices/divisions and their staff with a need to view or edit responses at any particular stage of the process; • Upon initial receipt, fields should be provided to note the name and address of the correspondent, the associated Office, the subject and issue identified, the date received and the recommended action; • The system should generate a unique identifier for this information and any associated documents that would assist in the tracking process; • The application should have the ability to use fields to standardize entry of information into the database; • Staff should be able to readily search the application by any fields with exact or partial keywords; • The application should be able to provide a report that shows the status, background information and location of the pending or finalized responses; • The application should have the ability to generate due dates and a production timeline by identifying the level or code of the response. The application should then be capable of producing Due Date alerts; • The application should have the ability to download emails to the correspondence database for processing; • The application should have the ability to integrate with MS Office and other specialized applications such as WorkShare Professional; • Ability to save scanned documents in the correspondence database or to connect to other site of stored data on the network; and • Ability to produce automated reports. Your response to this RFI should include the technology solution requirements. This may include: • Information about the platforms, networking capabilities, databases, implementation processes, configuration options, and hardware requirements; • The ability for the SEC to securely use proprietary data within your solution; • Available end user and technical training and support services; and • Ongoing maintenance fees, support and licensing if applicable. The Commission welcomes responses about products that partially fulfill the functionality described so long as they are available, operational and well-tested. Commercial off-the-shelf (COTS) systems are not required but are preferable to custom-built solutions. This RFI reflects the minimum functionality we seek. Respondents are encouraged to provide information on alternative and innovative solutions, functions, and designs, particularly if a respondent thinks it would produce superior results. RFI respondents must respond in the form of a Capability Statement that addresses: 1) the product's ability to fulfill the above functionality, 2) your company's profile and capability in providing these types of solutions, if any, and 3) any other relevant information that would enhance the staff's understanding of the information submitted. If all or any portion of the required capabilities can be provided via commercial off the shelf software, please so indicate in your response. If you are interested in providing information, please send to Reginald Barnes at BarnesR@sec.gov. The SEC will consider all responses to this RFI as information only, not offers. All information must be sent via email to BarnesR@sec.gov by no later than the response deadline.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/SEC/OAPM/PCB/SECHQ1-2011-OITSB/listing.html)
- Place of Performance
- Address: 6432 General Green Way, MS 0-20, Alexandria, Virginia, 22312, United States
- Zip Code: 22312
- Zip Code: 22312
- Record
- SN02495367-W 20110713/110711235115-e3f45bb9eda3b7a2adf3d3231b1ad232 (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 |