MODIFICATION
D -- Replace Loan Accounting System for Housing for the Elderly (LASHE)
- Notice Date
- 10/27/2004
- Notice Type
- Modification
- NAICS
- 541519
— Other Computer Related Services
- Contracting Office
- Department of Housing and Urban Development, Denver Field Contracting Operations, Denver Contracting Operations, 1670 Broadway 23rd Floor, Denver, CO, 80202-4801
- ZIP Code
- 80202-4801
- Solicitation Number
- R-DEN-01965
- Response Due
- 11/5/2004
- Archive Date
- 11/20/2004
- Point of Contact
- Nancy Royce, Contract Specialist (Team Leader), Phone 303-672-5281 x1812, Fax 303-672-5062, - Tony Karpowicz, Supvy Contract Spec. (Branch Chief), Phone 303-672-5281 x1818, Fax 303-672-5062,
- E-Mail Address
-
Nancy_J._Royce@hud.gov, Tony_M._Karpowicz@hud.gov
- Description
- This amendment is issued to provide all offerors with the questions submitted by offerors, and the answers to those questions: Question 1. JFMIP requirements envision retaining information about collateral condition/value data. Since collateral data is resident in REMS, will the new loan accounting system also require the data be maintained internal to it? As another example, would program-related correspondence to borrowers about debt repayment be retained by the new loan accounting system as well? Answer: No, the OCFO loan accounting system will not maintain collateral data. No, the OCFO loan accounting system will not maintain debt repayment information. That requirement will stay with Housing. Question 2. JFMIP requirements indicate the system should be capable of automatically capitalizing interest in accordance with established policies. While the loan accounting system must be able to establish a modifed mortgage, including capitalizing delinquent interest, for example, does this feature need to be automatic or automatically generate a new amortization schedule based on the recast mortgage? Answer: The functional requirements document currently calls for the generation of a new amortization schedule. However, if the proposed COTS package includes an automatic feature to handle recast mortgages that meets the requirements, it will be considered. Question 3. Is the Claims Collection Litigation Report used for the Section 202 program? Answer: This is not a requirement for the OCFO loan accounting system. Question 4. HUD indicates that it wishes to have scanned memos and other documents available in the system. What kind of scanning technology and infrastructure does HUD envision? Answer: HUD expects the proposed COTS technology to include scanning technology that is compatible with HUD's hardware/software infrastructure. Question 5. In several places, the PWS states that the COTS must be web-based. Does web-based imply a browser user interface, or does it mean that the application must operate using the internet rather than a dedicated communication line[s]? Answer: Web-based is intended to mean a browser user interface via the internet and Intranet Question 6. On pages 12 and 14 of the PWS, the document refers to "Testing of the COTS software in MS 2000 or successor operating systems on the server and client". Is operating on MS2000 a requirement? Answer: Microsoft Windows 2000 Operating System is the HUD standard. Question 7. The System Security and Privacy Plan, page 2.1, discusses the availability requirements for the LAS system. The document states: "The intended up time for web access is expected to be 24 hours since there is no direct access to the LAS database." Does this mean that the web system is a separate system? Does the web-based system access the LAS database as its data source, or is it a separate system that contains data extracted from the LAS system? Answer: The web-based front-end system is the new LAS system; there is no separate system or database after implementation of the new LAS system. There should be a real time interface for web access to the LAS database. Question 8. In the PWS on page 2, the document states "successful completion of all scenarios required" during Product demonstration. Where are the scenarios documented? Answer: Product demonstration scenarios were provided in Amendment 3 of the solicitation Question 9. Does HUD expect to acquire source code for the vendor's product? Should the price bid for CLIN001A reflect the cost for source code to the commercial product? Answer: HUD expects to purchase a COTS package. If the vendor develops source code to customize the COTS, HUD expects to own the customized source code. Question 10. In the PWS section 9.1.5.G, use of CA Endeavor and PVCS are required. Allfusion Endeavor is a mainframe software configuration management tool. Why does HUD specify software configuration management tools when purchasing a COTS? COTS licenses do not include source code, and any modifications to the licensed product would be made by the vendor. Please explain. Answer: Interface logic to Hitachi and Unisys based systems must still use either CA Endeavor or PVCS. Question 11. Standard COTS software purchases include an initial license fee followed by yearly maintenance and support fees. The Solicitation Description in the PWS does not include an annual software license fee line item for the first, second, third and fourth option period. In addition, Tasks 1, 9, and 10 of the PWS, which are the tasks that apply in those option periods, make no mention of software license and maintenance fees to the vendor. Task 2 specifies annual licenses, and the Schedule of Contractor Deliverables specifies licenses must be provided annually. Please comment. Answer: The vendor is responsible for purchasing all required license and software fees. These fees should be built in to the price for the base period and option years. Separate line items will not be provided for the license and software fees. Question 12. Page 11, Task 2, states the following requirement: "Includes technical training for three HUD developers and five HUD super-users." Why is training for HUD developers required if the vendor is responsible for maintenance? Answer: The developer training noted in the SOW is required to enable HUD staff to have a better understanding of the software and it's capabilities. HUD staff receiving the developer training would not undertake a true developer role. Question 13. There are several COTS loan servicing solutions offered as an ASP model, some of which are compliant with FFMIA JFMIP, USSGL, etc. If a vendor were willing to offer a solution that fulfilled the LASHE functional requirements and offered a cost-effective alternative to customized COTS, would this solution be considered? Answer: No. At this time HUD OCFO is pursuing purchase of a COTS system to support loan servicing. Question 14. Implementing the functionality required in the extensive Functional Requirements Document plus developing the required interfaces will likely constitute more than minimal modifications to a COTS product. After these enhancements are made, it is quite likely that future vendor releases and patches will not be compatible with the HUD product. How will HUD address the cost and product knowledge required to maintain its product, which will no longer be COTS? Answer: HUD expects to purchase a COTS package that has already been implemented at another federal agency. In addition, we are ready to tailor our business processes as needed to accommodate better loan servicing while still maintaining our business regulations. HUD expects minimum to no customization and does not expect this to be an issue. Question 15. Does HUD still have a requirement that the LAS software be compatible with Windows 95? Answer: No. Windows XP is currently the HUD standard. Question 16. In order to address all requirements, particularly the Special Standards for COTS software highlighted in Amendment #1, which specifies that, "HUD must have the ability to work directly with the person or entity that has the legal authority to repair, alter, etc. the software without the involvement of a third party", we plan to proposes a GSA Team Arrangement (http://www.gsa.gov/Portal/gsa/ep/contentView.do?faq=yes&pageTypeId=8199&contentId=8124&contentType=GSA_OVERVIEW). Please clarify whether HUD has any objections to GSA Teaming Arrangements for this solicitation. Answer: HUD is still researching the answer to this question. The answer will be provided in an upcoming amendment. As a result of this amendment, the date set for receipt of proposals is hereby extended to noon on Friday, November 5, 2004. Offers may be submitted by email to Nancy_J._Royce@hud.gov (NOTE: Offerors are advised that there is a 5 megabyte limit per email), or hand delivered to the following address: Nancy Royce Contract Specialist US Dept. of Housing & Urban Development 1670 Broadway, 23rd Floor Denver, CO 80202-4801 Ms. Royce can be reached at 303-672-5281, ext 1812. The addendum to this notice may be accessed at the following website: http://www.hud.gov/offices/cpo/contract/den01965.cfm Point of Contact Nancy Royce, Contract Specialist, Phone 303-672-5281, fax 303-672-5062, Email Nancy_J._Royce@hud.gov Place of Performance: Washington, DC
- Place of Performance
- Address: Washington, DC
- Zip Code: 20410
- Country: USA
- Zip Code: 20410
- Record
- SN00699615-W 20041029/041027211703 (fbodaily.com)
- Source
-
FedBizOpps.gov Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |