SRCSGT | R | This Request for Information (RFI) provides information about the Physical Assessment Sub-System and the maintenance/development work which will be required under a planned contract that will begin in May 2009.

FBO DAILY ISSUE OF NOVEMBER 23, 2008 FBO #2554
SOURCES SOUGHT

R -- This Request for Information (RFI) provides information about the Physical Assessment Sub-System and the maintenance/development work which will be required under a planned contract that will begin in May 2009.

Notice Date: 11/21/2008
Notice Type: Sources Sought
NAICS: 541511 — Custom Computer Programming Services
Contracting Office: Department of Housing and Urban Development, OCPO, Office of Support Operations, Office of Support Operations, NO, 451 7th Street S.W., Washington, District of Columbia, 20410, United States
ZIP Code: 20410
Solicitation Number: R-OPC-23400
Archive Date: 12/20/2008
Point of Contact: Timiko D Wilkins ,, Phone: 202-402-7145, Pamela C. Kelly,, Phone: 202-402-3113
E-Mail Address: Timiko.D.Wilkins@hud.gov, Pamela.C.Kelly@hud.gov
Small Business Set-Aside: 8a Competitive
Description: U.S. Department of Housing and Urban Development Office of the Chief Procurement Officer Information Technology and Financial Support Division 451 7th Street, SW, Washington, D.C. 20410 Request for Information for Physical Assessment Sub-System Services (PASS) RFI # R-OPC-23400 NAICS CODE: 541511 This is a Request for Information (RFI) only. It is not a Request for Proposals (RFP). Not responding to this RFI by December 1, 2008 will result in your company not being qualified to receive a Request for Quote (RFQ). Responding to this RFI, including acceptable answers to the questions, will make your company qualified to receive an RFQ for future work. This RFI is restricted to companies who are currently listed on the General Services Administration’s 8(a) program list of contractors. TABLE OF CONTENTS 1.NATURE OF THE RFI3 2.INTRODUCTION TO PIH AND PASS3 3.SCOPE OF SERVICES4 4.DEVELOPMENT REQUIREMENTS6 5.MAINTENANCE REQUIREMENTS8 6.CONFIGURATION MANAGEMENT REQUIREMENTS11 7.REPORTING OR OTHER PROGRESS/COMPLIANCE REQUIREMENTS11 8.DELIVERY SCHEDULE13 9.PERFORMANCE EVALUATION13 10. PLACE OF PERFORMANCE14 11. REQUIREMENTS FOR RESPONDING TO RFI14 1.NATURE OF THE RFI This Request for Information (RFI) provides information about the Physical Assessment Sub-System and the maintenance/development work which will be required under a planned contract that will begin in May 2009. The following points highlight the nature and requirements of this Request for Information: •This is an RFI only. It is not a Request for Proposals (RFP). The information supplied will be used to determine which contractors have interest in receiving the planned Request for Quote and which ones satisfy the requirements. •Section 11 of this RFI contains a list of questions which each respondent must answer. Not answering the questions will make the submission considered to be non-responsive, resulting in the contractor being ineligible to receive the RFQ. •Contractors who respond to this RFI, including acceptable answers to all its questions in Section 11, will be eligible to receive an RFQ. •There are three specific requirements needed to become eligible to receive an RFQ for this work: (1) contractor must be listed in the GSA 8(a) program contract list; (2) contractor must be certified as CMMI Level 2; (3) the contractor must conduct business according to the non-manufacturer rule as defined in FAR 19.001. •A highly condensed and simplified representation of the current, Scope of Services is contained in this RFI entitled “Scope of Services”. The RFI is only meant to give the contractor a sense of the type and magnitude of the work that is involved. The requirements may change at any time and in any manner prior to the request for proposals. •It is anticipated that this RFI will lead to an RFQ and a competitively bid contract for the project. •Clarifications to this RFI may be requested no later than three (3) calendar days prior to the deadline for a response. Answers to requested clarifications will be emailed regularly to all contractors in the GSA 8(a) program list. •The deadline for responding to this RFI is December 5, 2008, 10:00 a.m. EST. No RFIs will be accepted after date. Clarifications may be requested no later than December 2, 2008, 10:00 a.m. EST. •Responses to the RFI and clarifications should be directed to either of the following persons: Timiko Wilkins, Contracting Officer, 202-402-7145, Timiko.D.Wilkins@hud.gov Pamela Kelly, Secondary Contact Contracting Officer, 202- 402-3113, Pamela.C.Kelly@hud.gov 2.INTRODUCTION TO PIH AND PASS The Department of Housing and Urban (HUD), Office of Public and Indian Housing (PIH), is seeking a contractor to provide development, maintenance and operational support services for its Physical Assessment Sub-System (PASS). The Department of Housing and Urban (HUD), Office of Public and Indian Housing (PIH), oversees the Real Estate Assessment Center (REAC), which is responsible for capturing, standardizing, improving and evaluating data arising from the portfolio of properties for which HUD has a financial interest or statutory obligation to monitor. PIH-REAC assesses the physical and financial condition, resident satisfaction, management operations, quality assurance, and other information originating from the following major components of HUD’s program participant base: •Public Housing Agencies (PHAs) •Multi-Family (MF) Housing properties The PIH-REAC is responsible for capturing, standardizing, improving, and evaluating data from the portfolio of properties for which HUD has a financial interest or statutory obligation to monitor. The REAC assesses the following areas: 1) physical condition, 2) financial condition, 3) management capability, and 4) tenant satisfaction surveys Public Housing and Housing Multifamily properties. The Physical Assessment Sub-system provides the means to assess the physical condition of properties in the HUD portfolio. PASS is the cornerstone of the PIH-REAC suite of products and is the largest most complex subsystem in the inventory. The key business functions supported by PASS include: (1) the collection of profile data for all public housing and multifamily properties for which HUD has a statutory obligation or a financial interest, and (2) the inspection of these properties which provides the capability to assess their physical condition. The need for these business functions surfaced to assist in improving the quality of property conditions and achieve HUD’s mandate The Physical Assessment Subsystem (PASS) collects data and reports the actual state of repair and habitability of the real property. The inspection observations are recorded on a hand-held computer using HUD developed and HUD owned software and sent electronically to PIH-REAC for scoring, analysis, and processing. 3.SCOPE OF SERVICES Contractor shall perform work for all phases as defined in HUD’s Systems Development Methodology (SDM). See http://www.hud.gov/offices/cio/sdm/index.cfm. The contractor shall include security considerations in every stage of system development and maintenance. Documentation produced is to include not only documentation required by the SDM but also documentation required to meet applicable NIST series 800 requirements http://csrc.nist.gov/publications/nistpubs/index.html, FIPS security standards http://csrc.nist.gov/publications/fips/index.html and optional NIST documents that are required by CIO contained in HUD Handbook 2400.25 “HUD Security Policy.” ¬Planning/Initiate Phase. The purpose of the planning phase is to define the need for the next phase of system activity. Strategic Planning: The Contractor shall prepare, revise, and maintain information strategy plans that are an extension of business requirements and priorities developed by the program office. Information Technology (IT) Planning: The Contractor shall conduct research, develop cost/benefit analysis, risk assessment, and feasibility studies in support of the IT planning function. Business Process Reengineering Support: The Contractor shall provide technical advice to the GTM and the IPT concerning technical issues technical feasibility and the applicability of emerging technologies in addressing issues arising during business planning that is the outgrowth of Business Process Reengineering (BPR) and Joint Requirements Planning (JRP). Documentation should include recommendations for transitioning to new procedures in support of technical and business processes. Models will include both data and process models. Requirements/Define Phase. The purpose of the requirements phase is to develop detailed functional and data requirements that trace to business requirements and which can be used as the reference in designing the system. Development of System Requirements: The Contractor shall support the GTM in working with the program office to obtain detailed business requirements. The contractor shall review plans and business requirements from the PIH offices and coordinate with the business staff in formulating system functional requirements that implement the business requirements efficiently and effectively. The contractor will provide estimates of the cost, time requirements and technical issues that will arise in implementing business requirements. Design Phase. The purpose of the design phase is to take the detailed system requirements formulated in the define phase and implement them in details for system modules including how the system modules will interrelate, the types of reports, the format of reports and screens, the logical progression within modules, the utilities that will be required to manage the system, the user roles, the actions that they will take and how the access and scope of actions is to be stratified. Development of System Design Documentation: Design document details are to be sufficiently detailed so as to make the fundamental choices before programming starts, leaving the options to the programmer of choosing between programming tools and coding techniques. Assessment of legacy and Commercial-off-the-Shelf (COTS) Software: Design tasks may include, as directed by the GTM, assessment of the possible usefulness of COTS and legacy software. Build Phase: The purpose of the build phase is for developers to implement the design in code and to test the result to refine it until all components of the system interface and function correctly. Development/Programming of Application: Contractor shall program and test system modules, creating new modules or revising existing modules and test the modules so that they function as designed and work quickly and reliably in the application environment. Development may include modification of COTS software and adaptation of legacy software to help meet requirements. Test/Evaluate Phase: The purpose of the test phase is to assess how well the system will perform in satisfying requirements and that it will not interfere with other applications in the production environment. Acceptance Testing: Contractor shall assist the GTM in demonstrating to Stakeholders that the application addresses all business requirements and implements the agreed-upon design in a workable manner. Stress and Performance Testing: The contractor shall test and report results to the GTM that detail how tests were conducted and how the test results validate that the application meets HUD and PIH performance requirements under test conditions that mirror or simulate those in production. Integration Testing: The contractor shall participate in testing of the compiled code for each new PASS system release for testing along with the existing implementation or new releases of other PIH systems that share the same production infrastructure. Testing will include end-to-end testing of application processes and all system operations. Assistance to Testers: The contractor shall assist the GTM facilitating testing by HUD users as well as volunteers from the HUD business partner community. This includes configuring test IDs, explaining test scripts, assisting users who encounter problems and compiling and verifying tester results. Test results and planned corrections are reported to the GTM during each weekly test cycle. Deployment/Operate Phase: The purpose of the deployment phase is to put a system release that is considered by the GTM to have passed testing into production. Installation and Conversion Instructions: Contractor develops installation and conversion instructions that are developed, tested and refined during the Test Phase and which are implemented by the CIO staff. Contractor answers questions by CIO staff and helps trouble-shoot any issues that may arise. ¬Assistance to Trainers: Although the contractor is not required to perform training, contractor develops materials for and provides technical assistance to those who do perform training in the use of the system and in its use in the business context. 4.DEVELOPMENT REQUIREMENTS 4.1Established Development Workload PASS is currently being re-engineered from the current Cold Fusion environment to leverage Java 2 Platform, Enterprise Edition (J2EE). J2EE defines the standard for developing multi-tier enterprise applications. The J2EE platform makes enterprise applications development easier by establishing them on standardized, modular components, by providing a complete set of services to those components, and by handling many details of application activities automatically. The J2EE platform leverages many features of the Java 2 Platform, Standard Edition (J2SE), such as "Write Once, Run Anywhere" portability, JDBC API for database access, technology for interaction with existing enterprise resources, and a security model that protects data even in internet applications. Building on this base, the Java 2 Platform, Enterprise Edition adds full support for Enterprise JavaBeans components, Java Servlets API, JavaServer Pages and XML technology. The Physical Assessment Sub-System does not currently have a dynamic interface with other Major Application systems, but is reliant on batch data transfers from other systems such as NASS, REMS and other REAC systems, as well as furnishing batch data to other HUD systems. End users can access the PASS Information Center through the Internet or by using HUD’s Intranet. Access to The Physical Assessment Sub-System is secured and requires a user ID and password, which are granted on an as needed basis by the security administrator. If permission is granted, security administrators will provide the end users with very specific access only to relevant sub-modules within the system. 4.2Future Development Workload For future development work the offeror must experience providing design and development services for complex and large-scale information technology systems in a Java 2 Platform, Enterprise Edition (J2EE) supporting Enterprise JavaBeans components, Java Servlets API, Java Server Pages and XML technology on a Oracle environment. Future work will include but is not limited to the following PASS business modules. BusinessAdditional Details 1Complete revisions on the 4.0 Inspection Software and the server side processing systemsResolve all open items recorded in Quality Center and Implement requirements (functional and technical) that were carried forward from the past three releases. 2.Exigent Health and Safety ModuleCreate a EH&S work engine that incorporates all business requirements to include, Query EHS Deficiencies, Results Report, PHA/User mitigation of EHS Deficiencies, HUD Approve/Disapprove, Dashboard notifications/warnings 3.Inspection OversightCreate/Edit Inspect Auction Information; Data Transfer between Auction Vender and PASS; Generate/Update Reports 4.Software 4.0 Public and Training VersionsModify the 4.0 Inspection Software for a Public and Training Version of the 4.0 Inspection Software incorporating all Business Requirements 5.Send 4.0 Correspondence (PH & MF) Data Interface with REMS/REAC Data Warehouse. Provide inspection reports to REMS/NASS. 6.Scheduler for 4.0 Inspections Design this module to serve as the workflow management component for all PASS-related scheduling activities and geographic mapping of regular inspections, quality assurance inspections, and exigent health and safety follow-up reviews. The module will track all activities through their lifecycle, from initial order to acceptance of a possible appeal. 7.Inspection Training Create a Web based 4.0 Training engine incorporating all business rules to include login, training ID generation, multiple test inspections, auto grading and interface with IA/QA System, and interact with Inspection Admin module and Scheduler. 8.Inspector Administration Design the Inspector Administration decision-making engine to integrate with all components of the PASS system. This component, among other activities, will allow tracking of inspectors’ performance and identify at-risk inspectors based on established business rules. The following module list is currently planned for future efforts. 1. PASS Inspection Ordering Module (Public Housing/Multi-Family/Servicing Mortgagee/QA) 2. PASS Financial Management/Inspection Oversight Module 3. PASS Reverse Auction Module 4. PASS Inspection Software 4.0 Module (Inspection, Public, Training Versions) 5. PASS Inspection Review Module (Process/Scoring/Timestamp/Reports/Technical Reviews) 6. PASS Exigent Health and Safety Module 7. PASS Scheduler Module 8. PASS Management/Ad-hoc Reports Module 9. PASS Inspector Administration/QA Module 10. PASS Inspector Training Module 5.MAINTENANCE REQUIREMENTS The Offeror must be able to maintain large systems with diverse code including, but not limited to, ColdFusion, ASP, COM, Java, VB, C++, XSL and XML. Database support shall include expertise in MS SQL, Sybase and Oracle. The Offeror shall include information on support for batch data transfers and ability to code online interactive applications for wide-scale use across the Housing industry. The Contractor shall perform operational support, corrective maintenance, and adaptive maintenance activities. a.Operational Support: The Contractor shall provide operational support to include: a.Analyzing production and on-line batch processes each day to determine/verify task completion status and to obtain metrics for space allocations and performance tuning. b.Initiating steps for periodically archiving data. c.Coordinating and reviewing problems reported by the HUD IT Production Support staff, responding to user/help-desk inquiries, providing ad hoc reports and extracts regarding operational throughput, and providing background information regarding data characteristics. d.The REAC-TAC (Technical Assistance Center) supports Public Housing users by answering questions whose answers have been recorded in their knowledge base. The Contractor shall provide support when the help desk cannot resolve technical issues. e.Developing ad hoc reports in response to one of the program offices, GAO reports, and the HUD Office of Inspector General as well as Freedom of Information Act (FOIA) requests, etc. f.The Contractor shall perform post-implementation system reviews to document lessons learned; identify reusable components; best practices and make recommendations for future implementations. b.Corrective Maintenance: The Contractor shall modify PASS and its associated documentation to fix problems caused by design, logic, or coding errors. The Contractor shall perform software definition, design and build activities associated with the change. The Contractor shall also prepare or update test plans and test scenarios for user acceptance testing. Once coded, tested and documented, fixes are brought before the Change Control Board (CCB) and may only be implemented when and as approved. High-priority fixes that cannot wait for inclusion in the next release may become cause for an unscheduled or emergency release. c.Adaptive Maintenance: The Contractor shall modify PASS and its associated documentation to incorporate changes that are a result of new or changed laws, regulations, agency directives, OMB directives or audit findings. The Contractor shall perform software definition, design and build activities associated with the change. The Contractor shall also prepare or update test plans and test scenarios for user acceptance testing. Changes for adaptive maintenance are subject to the same CCB processes and requirements as those for corrective maintenance. The table below represents the typical maintenance tasks and their frequency, the number of batch procedures the system executes, the lines of code in the system and the number of COM objects in the system. This reference is subject to change as the system is maintained or modified. System Complexity TableOccurrence I. Work Level 2 technical assistance/user support - # of escalations100 Annual code Maintenance: Number of annual Problem Reports (SCRs)100 Production support: Number of batch procedures - Daily9 Number of batch procedures - Weekly3 Number of batch procedures - Monthly0 Number of batch procedures - Quarterly0 Number of batch procedures - Annually0 Number of Automated correspondence (letter/email)19 Active Production server operation (contract staff)Lockheed/EDS # Data requests - audits, correspondence, FOIAs, etc.30 II. Metrics Total number of application screens84 Number of update screens74 Number of inquiry screens10 Number of output reports5 Number of ASP/COM/Java/XSL/XML Files1276 Lines of VB/C++/JAVA /XSL/XML/163,040 Number of stored database procedures899 Lines of SQL Code184,937 Lines of CF Code90,951 Total Users32760 Number of potential internal users (HUD employees)7,000 Number of potential external users (Business partners)25,000 Annual Distinct Log-ins 3276 concurrent Number of external system interfaces5 Number of scoring areas 5 Number of scoring sub-areas600 Number of complex formulas/calculationsVery Complex >1000 Annual volume of Inspections12,000-32,000 Submissions:Approximately 21,000 inspections. 20,972 inspections performed in 2006 Public Housing Inspection Uploads7,217 in 2006; 9,527 thus far in 2007 Multi Family Inspection Uploads13,755 in 2006; 10,646 thus far in 2007 EH&S Mitigation Total 52,469; 20,153 in 2006; 20,048 in 2007 * Fluctuation due to complexity of each release. 6.CONFIGURATION MANAGEMENT REQUIREMENTS The Contractor shall perform all development and maintenance activities in accordance with PIH-REAC’s Configuration Management Plan. The plan, which may be found at http://hudatwork.hud.gov/po/reac/products/DCG/docs_guide.cfm, addresses several topics including the following: Configuration Management: Configuration management is a set of processes to identify configuration items, baseline configuration items and control changes to that configuration baseline. Change Management: Change management identifies and defines steps for initiating a Software Change Request (SCR) that may alter the existing Software Configuration Items (SCI). Change Requests (CR) and Problem Reports (PR): Primary mechanism to initiate a change to the existing requirements or report a problem occurring in the system. Release Management: Release management consists of specific processes that manage the risks associated with each of the four PIH release categories: major releases, feature releases, defect releases and emergency releases. Problem Tracking: SCRs, CRs and PRs are submitted to the CCB for evaluation and approval. Upon CCB approval, the subsystem that submitted the SCR, CR or PR provides an assessment package for the appropriate release. 7.REPORTING OR OTHER PROGRESS/COMPLIANCE REQUIREMENTS The project has various reporting requirements including weekly status reports, monthly status reports, and the reporting of all problems, flaws and deficiencies. The contractor is responsible for submitting various plans including a Project Management Plan (PMP), Transition Plan, Risk Management Plan, Quality Assurance/Quality Control Plan, and System Security Plan. The contractor is also required to comply with the Earned Value Management processes. The PMP consists of 4 parts: •Project Plan; •Transition Plan; •Risk Management Plan; and •Quality Assurance/Quality Control Plan. The Project Plan shall include a narrative that: a.Describes the staffing resources allocated to each task; and b.Provides the rationale for the project organization, staff utilization and other resources allocated to each task or activity. Contractor shall use Work Breakdown Structure (WBS) categories that breakdown work packages into activities of 80 to 100 hours of effort. Each activity will result in a milestone associated with a particular deliverable. The Risk Management Plan shall: a.Describe each individual risk to include the source of the risk and the trigger (or symptom) of the risk; b.Determine the impact of the risk in terms of cost and schedule; c.Document procedures to manage the risk; and d.Assign responsibility for risk monitoring and contingency plan implementation to those identified at the PMR or Risk Management planning session. The Quality Control Plan shall: a.Identify the Contractors’ standards that are applicable to this effort; b.Include procedures for complying with those standards; c.Identify techniques and metrics for measuring compliance; and d.Include an approach for eliminating the causes of unsatisfactory/unacceptable performance. With each major release, the system security plan (SSP) should be enhanced and updated to reflect security issues arising out of the new release or that have been identified since the plan was last updated. The purpose of the SSP is to document all of the security controls that are in place, whether built into the system or managed by personnel who operate the system or use its output. The SSP must meet the standards set by NIST Special Security Publication 800-18. Contractor is required to adhere to the Earned Value Analysis management and reporting procedures as stated in the ANSI 748 Standard. Monthly reporting shall cover five of the six guidelines found in the Analysis and Management Reports Category (sections 2.4 a, b, c, d, and f) to the level of detail illustrated in the HUD Earned Value Reporting Template. 8.DELIVERY SCHEDULE Deliverables Due Date Project Management5 days after award; updated monthly by the 10th day of the month Project Plan - final Monthly Reports against plan5 days after award; updated monthly by the 10th day of the month Transition PlanGTM’s discretion, 90 days before base/any option period expiration Risk Management Plan update5 days after award; updated monthly by the 10th day of the month Quality Control Plan5 days after award; updated monthly by the 10th day of the month Earned Value ReportsMonthly – by 10th of the month Project Plan RebaseliningUpon request within two weeks of request by GTM Status ReportsWeekly for scheduled meeting Progress ReportsWeekly for scheduled meeting Tasks DescriptionsWith project plan, project plan updates and re-baselining actions Strategic PlanningAs necessary Information Technology (IT) PlanningAs necessary Business Process Reengineering SupportAs necessary Planning RequirementsPer DCG Schedule Initiate ProjectPer DCG Schedule Define systemPer DCG Schedule Development RequirementsPer DCG Schedule Design SystemPer DCG Schedule Build SystemPer DCG Schedule Evaluate SystemPer DCG Schedule Implement SystemPer DCG Schedule 9.PERFORMANCE EVALUATION Using HUD’s System Development Methodology as the standard, the government will evaluate the Contractor’s performance. When quality assurance reviews by HUD indicate defective performance, the GTR/GTM will request the Contractors’ response to the substandard performance in writing within five business days of receipt. A quality assurance plan will be included in the Statement of Work. The plan will state for each deliverable and measurable activity (e.g. Project Management, Strategic Planning, Requirements/Define Phase), a task requirement, the standard for evaluation, and method of measurement. For example, the entry for Project Management is the following: TaskPerformance RequirementPerformance StandardPerformance Measurement PROJECT MANAGEMENTContractor shall successfully complete a baseline plan, quality control plan and progress report. The Project Plan shall be subject to an Integrated Baseline Review (IBR) and may be revised in light of the input from the IBR. Progress on all authorized work is reported and compared with the project baselines. All authorized work is identified and defined to the work package level in WBS; tasks relationships are depicted graphically and scheduled; project team members and organizational units are identified along with their roles and responsibilities.The contractor’s baseline plan shall be through and include all aspects of the work/tasks needed to provide all deliverables within the time frames authorized by the contract. The quality control plan shall be realistic and pragmatic with an emphasis on assuring high quality deliverables. Progress reports shall convey a realistic picture of current progress, identifies any potential roadblocks or problems, and defines a strategy to mitigate the impact of any such roadblocks. The Progress Reports conform to standards for content and format, delivered in accordance with delivery schedule, and reflect acceptable progress.The GTR/GTM shall review the quality of all deliverables to determine if the plans and reports clearly indicates a thorough understanding of the objectives of this project. These plans and reports shall clearly identify all significant concerns/ risk/ weakness/ deficiencies in accomplishing its goals. Reports/plans are well defined, realistic, clear, concise, and useful. 10.PLACE OF PERFORMANCE The work shall be performed at HUD and the contractor’s facility. HUD shall provide workstations for 10 contract staff. 11.REQUIREMENTS FOR RESPONDING TO RFI Each contractor who responds to this RFI must provide the following information: a.State which Capability Maturity Model Institute certification level your firm has achieved or will achieve within 4 months of the contract award date (CMMI Level 2). b.State whether your firm is a participant in the GSA 8(a) program contract schedule, (Inclusion in 8(a) program is a requirement). c.State whether your firm will abide by the non-manufacturer rule as defined in FAR 19.001 (This is a requirement). d.Indicate whether your firm would like to receive the Request for Quote (Affirmative answer is required.) e.Indicate the number of web-based applications (Java-based J2EE compliant) in a federal government environment they have individually or teaming with other contractors had responsibility for developing and maintaining in the last three years. f.State whether your firm has worked on a system of the size and complexity like the PASS in the past three years. g.Based upon your current understanding of the system and the required work, whether in your best judgment your firm individually or in partnership can meet the requirements of this project.
Web Link: FedBizOpps Complete View
(https://www.fbo.gov/?s=opportunity&mode=form&id=317841b5b498f9df5b838e16d5cc5f66&tab=core&_cview=1)
Place of Performance: Address: US DEPT OF HUD, 451 7th Street, SW, Washington, District of Columbia, 20410, United States; Zip Code: 20410
Record: SN01708646-W 20081123/081121215224-317841b5b498f9df5b838e16d5cc5f66 (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 |

Loren Data's SAM Daily™

R -- This Request for Information (RFI) provides information about the Physical Assessment Sub-System and the maintenance/development work which will be required under a planned contract that will begin in May 2009.