ABP Replacement RFI 47HAA024N0003.pdf
PDF 749 KB Posted
- Attached to
- Asset Business Plan (ABP) Replacement
- Solicitation number
- 47HAA024N0003
- Issued by
-
GSA Office of Administrative Services
About this file
This Request for Information (RFI) from the U.S. General Services Administration (GSA) seeks information on asset management systems and platforms to develop, track, and store long-term asset strategies for managing and optimizing the GSA Public Buildings Service (PBS) real property portfolio. Responses are due by December 18, 2023 and should not exceed 25 pages, describing the vendor's proposed solution and capabilities to integrate with GSA's existing data systems, while addressing functional and technical requirements including 508 compliance, SAML authentication, and FedRAMP moderate security controls for cloud-based solutions. Vendors should also provide responses to questions in Appendix 2 regarding building performance analysis, tenant occupancy data, stacking and blocking visualizations, and report customization. A cost estimate is requested for years one through five for developing, configuring, and maintaining the proposed solution. An industry day will be held on December 12, 2023 for vendors to submit questions in advance.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFI 47HAA024N0003- Questions and Answers-12-7-2023.pdf | ||
| Attachment 1 - Question Template.xlsx | XLSX spreadsheet |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
General Services Administration (GSA)
Office of Administrative Services (OAS)
Office of Internal Acquisition (OIA)
Request for Information (RFI) 47HAA024N0003
Asset Business Plan (ABP) Replacement in support of
GSA IT - Office of Public Buildings Information Technology Services and
PBS - Office of Portfolio Management & Customer Engagement
NAICS code 541519
November 16, 2023
Disclaimer
1. Introduction
2. Background
3. Description of Need
3.1. Functional Requirements
3.2. Technical Requirements
3.3. Additional Security Requirements
4. RFI Response Requirements
5. Generic Cost Estimate
6. RFI Submission Instructions
7. Final Comments
Public Records and Request for Confidentiality Copyrights Content of Responses Cost to Vendors No Obligation to Issue Request for Quote
Appendix 1: System Definitions (as referenced in Figure 2) Appendix 2: Vendor Questionnaire
1.0 General (Question-Based Requirements)
2.0 Stacking and Blocking (System Capability Questions)
3.0 Other Capabilities
Disclaimer This Request for Information (RFI) is for planning purposes only and is not a Request for Quotes (RFQ), Request for Proposals (RFP), Invitation for Bids (IFB) or an obligation on the part of the Government to acquire any services.
Responses to this RFI are not offers and cannot/will not be accepted by the Government to form a binding contract. The Government reserves the right to determine how it should proceed as a result of this notice. Furthermore, those who respond to this RFI should not anticipate feedback with regard to their submission. However, the government may engage vendors that respond to this notice by seeking further information about capabilities or even a direct award. The Government will not pay any cost incurred in response to this RFI. All costs associated with responding to this RFI will be solely at the responding party’s expense. The information provided in this RFI is subject to change and is not binding on the Government.
1. Introduction The U.S. General Services Administration (GSA) is engaging our industry partners in the formative stages of our requirements for contractual support. The Office of GSA Information Technology (GSA IT) - Public Buildings Information Technology Services (PB-ITS) and the PBS Office of Portfolio Management and Customer Engagement (PT) are looking for ways to better meet the challenges inherent to the growing variety of interfaces, increasing IT capabilities, demanding security needs, and rising expectations of customers. We invite the industry to suggest ideas in technology and business practices that will help us move to the next level of service.
The purpose of this RFI is to gather information on asset management systems and platforms available in the marketplace to develop, track, and store long-term asset strategies used for managing and optimizing the performance of the Public Buildings Service (PBS) real property inventory. The solution shall be able to assemble a detailed snapshot of each asset in the portfolio, including its financial performance, budget data, physical condition, liabilities, short-and long-range plans, and customer and market information.
To assist the Government in its market research, the responses shall provide a detailed description of the vendor’s proposed solution to address the questions and technical requirements below. The solution can comprise multiple applications and systems, but it shall provide an integrated user experience. Figure 2 provides a high-level view of systems that provide different functionality and all available data, except license-restricted data.
The solution can utilize functionality provided by GSA systems and/or introduce new applications and systems, but the solution shall be seamless for the user (i.e., provide an integrated user experience). Available GSA systems include IBM Tririga, IBM Maximo, Kahua, and ESRI ArcGIS. Platforms such as Appian and ServiceNOW are available, but the government’s preference is to utilize their out-of-the-box features and templates over fully custom-built solutions. GSA’s current reporting and dashboard solutions include Oracle Analytics Server, Tableau, and MicroStrategy.
Responses shall address how the solution will answer the business questions listed in the Vendor Questionnaire in Appendix II. In addition to describing your technical approach, responses must include estimated costs to develop and maintain the solution, assumptions that aid these estimates, and a timeframe to develop, configure, and implement the solution.
Responders shall state whether their solution is FedRAMP certified or if it can be run on premise. If the solution is not FedRAMP certified or cannot be run on premise, then the responder shall be willing to comply with stringent IT Security requirements, which includes implementing controls specified under the Federal Risk and Authorization Management Program (FedRAMP) for cloud service offerings for a moderate system.
2. Background The U.S. General Services Administration (GSA) provides workplaces by constructing, managing, and preserving government buildings and by leasing and managing commercial real estate. The Public Buildings Service (PBS) under GSA is the landlord for the civilian Federal Government.
PBS manages over 370 million rentable square feet of workspace for federal employees, owns 1,600 plus assets totaling over 180 million rentable square feet, and manages 7,000 plus leased assets totaling over 180 million rentable square feet.
The Office of Portfolio Management and Customer Engagement (PT) under PBS manages the real estate portfolio to meet customers’ workplace needs. They serve as the taxpayer’s trustee by developing innovative real estate solutions that maximize the taxpayer's dollars while delivering excellent customer service to tenant agencies. While optimizing the portfolio, PT must balance customer needs, social and economic priorities, and financial return, so that the portfolio provides the best overall value to the taxpayers.
GSA IT delivers secure and exceptional technology solutions and experiences to GSA. PB-ITS under GSA IT provides enterprise solutions for GSA’s real estate mission and buildings portfolio.
PB-ITS focuses on the delivery of innovative workspace IT programs, services, and solutions.
https://www.fedramp.gov/assets/resources/documents/FedRAMP_Security_Controls_Baseline.xlsx
Information technology and project management experts in PB-ITS understand the PBS real estate business requirements and their federal customers’ unique workspace needs, and advises PBS business lines on IT tools to support and enhance the government’s business processes for workspaces leveraging innovative technology solutions.
3. Description of Need The PBS Office of Portfolio Management and Customer Engagement (PT) requires a comprehensive asset business planning solution that has the ability to quickly analyze multiple owned and leased assets across a market, region, and the nation in order to maximize value and savings for the American taxpayer. The vision for this solution is a “central nervous system” that contains the data and artifacts required to make strategic portfolio decisions and support several business processes that are utilized to execute those decisions. Figure 1 illustrates this concept.
Figure 1: Asset Business Plan (ABP) Vision
The solution shall contain dynamic building profiles, which are essential and feed the asset and portfolio planning processes, including scenario planning and strategic project prioritization.
Given various scenarios, the solution shall identify what business case makes the most sense to provide the best overall value to GSA customers and the American taxpayer. These building profiles and planning efforts are guided by Federal government sourced financial data and projections for each building and scenario, and assist with prioritizing projects and related funding needs. Information from these components shall be visible via dashboards. These dashboards help understand the overall portfolio of owned and leased buildings at a national, regional, state, and metropolitan area level. The system shall assist asset managers, planning managers, and program managers in their various roles by providing a complete picture with key data points required to make sound asset business plans that meet regional and national needs.
3.1. Functional Requirements
In addition to what is briefly described above, the solution shall provide answers to the questions stated in Appendix 2. For the purposes of this document, buildings and assets are used interchangeably. Please provide responses to the questions in Appendix II. The responses will count towards the maximum page count.
3.2. Technical Requirements
● Seamless integration with existing PBS systems and applications via APIs (preferred when available), or ETLs from our 19c Oracle Data Warehouse, or possibly directly from PBS systems, which are a mix of custom built and SaaS solutions such as IBM Tririga, Kahua, and IBM Maximo. See Figure 2 and Appendix 1 for system information.
● Although the system is mainly an “aggregation” of data, it shall allow users to input and store specific data that is key for asset planning.
● The proposed solution must be Section 508 compliant.
● Authentication mechanism should use SAML 2.0.
● Hosting Options: If proposing a SaaS solution, FedRAMP certification is preferred or the system must be able to run on premise. FedRAMP moderate controls must be adhered to for cloud based solutions.
● The system shall adhere to security requirements listed in NIST 800-53 to receive an authority to operate (ATO).
● User Interface and User Experience Requirements:
○ The vendor shall provide expert guidance and direction on user experience (UX) strategy, research, and design.
○ The vendor shall create designs that use the U.S. Web Design System and, when applicable, align with GSA’s design system.
○ The vendor shall conduct usability and user acceptance testing on new designs, features, content, navigational elements, etc. to ensure a quality end-user experience.
○ The solution shall incorporate robust accessibility principles into design, and testing for all products to deliver high-quality digital experiences to users of assistive devices.
https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final
Figure 2: High-Level View of PBS Systems
3.3. Additional Security Requirements
● Reference 1 CIO 21001M GSA Information Technology (IT) Security Policy
● Reference 2 IT General Rules of Behavior CIO 2104.1B CHGE 2
● Reference 3 Continuous Monitoring (ISCM) Strategy OA Program [CIO IT Security 12-66
Rev 3]
● Reference 4 CIO IL-20-91 Enterprise Identity, Credential, and Access Management
(ICAM) Policy
● Reference 5 CIO 2200.1 Privacy Act Program
● Reference 6 - IT Security Procedural Guide: Security and Privacy Requirements for IT
Acquisition Efforts (CIO-IT Security-09-48)
4. RFI Response Requirements All interested parties shall furnish the following information:
● Name of Company
● POC, Telephone Number(s), Address, Website and Email Address
● Applicable Contract Vehicles (e.g., GSA Schedule, GWAC, BPAS, etc.)
https://www.gsa.gov/system/files/CIO%2021001N%20GSA%20Information%20Technology%20Security%20Policy%2009-21-2022.pdf https://www.gsa.gov/system/files/CIO%2021001N%20GSA%20Information%20Technology%20Security%20Policy%2009-21-2022.pdf https://www.gsa.gov/directives-library/gsa-information-technology-it-general-rules-of-behavior-4 https://www.gsa.gov/system/files/CIO%2021001N%20GSA%20Information%20Technology%20Security%20Policy%2009-21-2022.pdf https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-137.pdf https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-137.pdf https://www.gsa.gov/system/files/CIO%2021001N%20GSA%20Information%20Technology%20Security%20Policy%2009-21-2022.pdf https://www.gsa.gov/directives-library/enterprise-identity-credential-and-access-management-icam-policy-1 https://www.gsa.gov/directives-library/enterprise-identity-credential-and-access-management-icam-policy-1 https://www.gsa.gov/system/files/CIO%2021001N%20GSA%20Information%20Technology%20Security%20Policy%2009-21-2022.pdf https://www.gsa.gov/directives/files?file=2023-07/CIO%202200.1%20GSA%20Privacy%20Act%20Program%20(5-12-2020).pdf https://www.gsa.gov/system/files/CIO%2021001N%20GSA%20Information%20Technology%20Security%20Policy%2009-21-2022.pdf https://www.gsa.gov/system/files?file=Security-and-Privacy-Requirements-for-IT-Acquisition-Efforts-%5BCIO-IT-Security-09-48-Rev7%5D-07-25-2023.pdf https://www.gsa.gov/system/files?file=Security-and-Privacy-Requirements-for-IT-Acquisition-Efforts-%5BCIO-IT-Security-09-48-Rev7%5D-07-25-2023.pdf
● Unique Entity Identifier (UEI) Number1
● Business Size
● High level description of client base for similar services
○ Do you have one current client of similar services and size?
○ Do you have one former client of similar services and size?
● Number of customers
○ Geographic distribution of customers
○ Who is your largest customer?
○ Potentials for conflict of interest in the customer base.
● Length of experience
● If proposing a solution with multiple applications and systems, provide detailed experience and success as a system integrator
● A detailed narrative (vendor capability statement) addressing the Government’s stated need and how your company can fulfill the requirements through your proposed solution(s). Generic responses are not acceptable.
○ Response shall include the solution’s capabilities to integrate with GSA’s existing data
■ Preferred method(s) of integration
■ Examples of your experience with integrating multi-platform and on-premise federal data
■ Approach for addressing both ingress and egress of data
○ Response shall provide data integration capabilities of SaaS, COTS, GOTS product, for example:
■ The solution can read and display APIs in real time, display it and use it along with transactional data without performance issues.
■ The solution can store and accept input data only through nightly loads and needs to store data locally and only then display it.
■ The solution is flexible and it can do both.
■ The solution can only read from sources but cannot store data.
○ Include assumptions or exceptions
● A response to each of the questions in the Vendor Questionnaire (Appendix 2). Please number your response to reference the question being answered (e.g., 1.0 #1).
● A high-level schedule for the deployment of the solution/system including security approvals. (Important: FedRAMP moderate controls must be adhered to for cloud based solutions, and is the responsibility of the vendor.)
1 If you are already registered in SAM.gov and have a DUNS number, most likely you have automatically been assigned a UEI number.
5. Generic Cost Estimate Provide a Rough Order of Magnitude (ROM) estimate to develop, configure, and maintain the proposed solution based on GSA’s requirements. What are the anticipated “best guess” annual maintenance and other costs/fees? List any assumptions made based on the requirements listed in this document. Please provide for years one through five.
The estimate shall include all products/services. Also provide your cost structure for different integration methods supported by levels of complexity (small, medium, large), along with assumptions on how levels of complexity were defined. If there are any licensing costs, please include the cost model and licensing information.
6. RFI Submission Instructions Vendors shall submit responses to the RFI via email, no later than 9:00 AM, EST, Monday, December 18, 2023. Responses shall be submitted to the Contracting Officer, Erica Pelham at erica.pelham@gsa.gov and Jerome Martin, jerome.martin@gsa.gov. Responses shall not exceed 25 pages. All responses shall be typewritten and presented in MS Word or PDF format (minimum of 12 point, Times New Roman or Arial font). Vendors may provide additional materials relevant to the RFI (e.g., screenshots, etc.) as attachments outside of the 25 pages, for a maximum of 10 additional pages. If applicable, title your screenshot according to the question/statement being referenced (e.g., 1.0. #1).
The government (GSA) plans to hold an Industry Day on December 12, 2023. Vendors shall register for the Industry Day and submit their questions no later than 9:00 AM Friday, December 1, 2023 using Attachment 1-Questions Template. Vendors are permitted to have a maximum number of two attendees. Questions and feedback shall be limited to 1 page. The government reserves the right to not respond to vendor questions during the Industry Day.
To register for Industry Day submit the following form.
This is not a marketing opportunity, it is an opportunity for good corporate citizenship and to show your best interest in a more effective and efficient government. Any submission that resembles a "sales pitch” will be considered non-responsive.
mailto:erica.pelham@gsa.gov mailto:jerome.martin@gsa.gov https://docs.google.com/forms/d/e/1FAIpQLSeu_hxNb2nj22-tG-zPD-P0UBVOWWVrb-jm7hOCU_OgMBfgMg/viewform?usp=sf_link
7. Final Comments Public Records and Request for Confidentiality Any document submitted that contains confidential information must be watermarked as containing confidential information, and each page upon which confidential information appears must be marked as containing confidential information. The confidential information must be clearly identifiable to the reader wherever it appears.
Copyrights By submitting a response, the vendor agrees that the government may copy the response for purposes of facilitation of review or to respond to requests for public records. The vendor certifies that such copying will not violate any copyrights in the materials submitted.
Content of Responses Responses should be based on the material contained in this RFI and any other relevant information the vendor thinks is appropriate. Responses will not be returned.
Cost to Vendors The government is not responsible for any costs incurred by a vendor in relation to the preparation of a response to this RFI.
No Obligation to Issue Request for Quote The issuance of this RFI does not obligate the government in any way to issue an RFQ for the services described.
Appendix 1: System Definitions (as referenced in Figure 2) Reimbursable Work Requests & Tracking - data available includes external customer agency and internal GSA work requests, Reimbursable Work Authorizations, and RWA cost estimates.
Summary and detailed information such as obligations, commitments, costs, financial information, and audit trail of key transactions is available. It is on-premise and a custom built .NET based application running on Oracle 19c database.
Acquisition Data - available data includes procurement requests, award information, and obligations. It is on premise, built on Appian 21.3, and is custom code running on an Oracle 19c database.
Building Operations and Maintenance Data - available data includes detailed building operations (facility equipment) and maintenance data including planning and tracking information. It is built on IBM Maximo, a cloud based SaaS system.
Building Inventory and Profile Data - available data includes key attributes on leased (7,088) and owned buildings (2,157) that spans 369 million square feet of space as well as lease processing and lessor payment information on 8,087 active leases. It is on-premise, custom built on Java, and runs on an Oracle 19c database.
Estimated Rent data - available data includes estimated future rent charges for occupancies, changes in space and calculating their associated impact on rent within the PBS inventory. It is on-premise and custom built based on Java and Oracle 19c.
Cost Estimate Data - available data includes national parameter-based planning and early-design phase cost estimates for new construction, R&A, land ports of entry, and modernization projects for GSA PBS owned and leased assets. Cost estimates are for design cost, construction costs, and building maintenance / repair costs. A breakdown of estimated costs for a specific project are provided. It is cloud based and built on Salesforce.
Tenant Satisfaction Data - available data includes tenant satisfaction survey results from federal employees regarding the building in which they work and documented maintenance tasks created by building managers as they relate to information obtained from the survey. It is cloud based and built on Salesforce.
Competitive Utility Data - available data includes competitive gas and electric accounts such as utility contract and service data, customer account data, and building information. It is on-premise, custom built on Angular JS, and PostgreSQL 14.4.
Occupancy Agreement Billing Data - data available includes rental invoice information. It is on-premise and custom built on Java and Oracle 19c.
Asset Disposal Data available data includes Federal property disposal from initial service request to final disposal or appraisal results for a property or group of properties. It is cloud based and built on Salesforce.
Asset Appraisal Data - available data includes fair market rental appraisal information. It is on-premise, custom built .NET and runs on Oracle 19c.
Energy & Water Usage Data - available data includes both energy and water usage history annually, compound annual change usage, usage relative to R5 average, environmental impact data, technology: renewable energy systems in the building. It is on-premise and custom built on Java and Oracle 19c.
Work Items - data available includes work items and their estimated costs for a building. It is on-premise and custom built on Angular JS and PostgreSQL 14.4.
Financial Data - Transactional data from GSA’s financial systems available through an Oracle database.
Construction Project Management data - available data includes enterprise-wide construction and project management information for PBS projects above and below the prospectus threshold in both owned and leased space. It is built on Kahua, a cloud based SaaS system.
Project Prioritization, Liability, and Safety data - available data includes prioritization of asset repairs, building assessment surveys data, asset liabilities, costs for newly discovered repairs and alterations, and fire, life and safety liabilities of assets. It is on-premise and custom built on Angular JS and PostgreSQL 14.4.
Occupancy Agreement Management, Building & Space Inventory - data available includes occupancy agreements and space assignment information such as: space and parking used by the client agency, space costs, rental rates, and other related information in a rental agreement. It is built on IBM Tririga, a cloud based SaaS system.
Lease Acquisition Management and Documents data available includes leased project data -when a tenant will be moved into another building (acquisition and expiration of leases used for schedules and investment planning. It is on-premise and built on Appian 21.2 with custom code and runs on MySQL 5.7.
Sustainable Building Data (Guiding Principles and LEED) - data available includes: sustainable designation and building certification information. It is on-premise and custom built on NestJS and MS SQL 2019.
Building Automation System and Utility Metering data Data available includes building system performance data that is used for fault detection and diagnostics (FDD) to monitor and track operating guidelines and to notify facility managers of potentially costly irregularities for investigation and correction when necessary. It is on-premise and built on COTS and a Skyspark proprietary DB.
Appendix 2: Vendor Questionnaire Please provide your responses to the questions below as part of your RFI response. The responses to these questions are part of the maximum page count.
1.0 General (Question-Based Requirements)
1. How is a specific building performing? How will it perform in the future? The answers to these questions should be derived by utilizing current/known measures, by generating forecasts based on changes to the building and other scenarios, and using pro forma data which includes effective gross income, vacancy loss, potential gross income, capital expenditures, operating expenses, and G&A expenses.
2. Can a selected building’s infrastructure (utilities) support moving selected tenant(s) into a specified building?
3. Where are all the buildings that house a specific tenant? This shall be viewable nationally, by state, regionally, or by metropolitan area. Regions should be configurable to align with GSA’s 11 regions.
4. What occupancies, buildings, and/or markets are under-performing or at risk? The solution shall allow users in a specified role to set thresholds for data elements and change those thresholds without requiring a developer. Occupancy data, reinvestment needs, and local portfolio statistics must be utilized to answer these questions.
5. What is the condition of a building(s)? What are its reinvestment needs and corresponding reinvestment plan, and does it make sense to reinvest in the asset or should it be disposed of?
6. What buildings are within a specified proximity of a selected building?
7. What/Where are all the buildings with selected attribute(s) such as building type (e.g., courthouses, historical courthouses, etc.)?
8. What is the current and projected customer agency space demand in a market, and the current and projected supply of PBS-controlled real estate within a market? When answering these questions, the solution shall account for the surrounding real estate market conditions.
9. What are the costs and benefits of proposed projects and housing scenario alternatives?
How do they compare? The solution shall allow end users to save and share this information, and the solution shall also allow users to prioritize investments and housing strategies within an asset and market(s).
10. Why did we make this decision? What didn’t happen that we expected? One of the major goals with this solution is being able to go back and understand why previous decisions were made, what assumptions were in place, which assumptions were incorrect or correct.
11. What building(s) can I move specified tenants into, or where can I move all tenants in a building to, and what is the projected financial impact of that decision? The answer shall take into account the type of space needed, location of space, and other attributes. This shall be achieved with a visual stacking and blocking capability along with robust scenario planning.
12. How does moving tenants into a specific building or buildings compare with moving them into other buildings or a new building (not in the current portfolio)? The system shall allow the user to compare and save scenarios. If a comparison is not possible, scenario data must be exportable, so that financial analysis can be completed outside of the system.
2.0 Stacking and Blocking (System Capability Questions)
1. What building(s) can I move specified tenants into, or where can I move all tenants in a building to, and what is the projected financial impact of that decision? The answer shall take into account the type of space needed, location of space, and other attributes. This shall be achieved with a visual stacking and blocking capability along with robust scenario planning.
2. How does moving tenants into a specific building or buildings compare with moving them into other buildings or a new building (not in the current portfolio)? The system shall allow the user to compare and save scenarios. If a comparison is not possible, scenario data must be exportable, so that financial analysis can be completed outside of the system.
3. What are the solution’s stacking and blocking capabilities? Does the solution allow a user to filter and generate reports based on specific criteria such as: region, building, report type, space type, space category, agency code, agency bureau code, and ANSI/BOMA code? The solution’s Stacking and Blocking capability shall provide detailed insights into space allocation, grouping spaces by various criteria, and calculating key metrics like Utilization Rate, Maximum Occupancy Capacity.
4. In regards to stacking and blocking, does the solution provide clarity and visual distinction by assigning colors for space type, space category, and agency/AB code? If yes, can the colors be customized to meet predefined rules for criteria like space type, space category and agency/AB code? The solution shall label essential attributes, such as agency bureau code, ASA number (for specific space categories), and sq.ft., all rounded to two decimal places. The solution should ensure visual distinction for ANSI
BOMA codes. For example, BOMA’s published standards recognize that, in an office building that is leased entirely to a single occupant (as in build-to-suit development and sale-leaseback transactions), it is common to utilize exterior gross area instead of rentable area as the basis for leasing. This structured approach streamlines data interpretation and aids in effective decision-making within the context of asset management and optimization.
5. In regards to stacking and blocking, can the solution provide exported files in the dwg format that can be edited within AutoCAD?
6. How are stacking and blocking drawings rendered to the user? More specifically:
a. Does the system automatically adjust block sizes to accommodate the number of floors within a building?
b. Will buildings with fewer floors appear with larger block heights and buildings with more floors adjust block heights to fit the frame while maintaining a minimum height to display all labels?
c. Can users view reports with a fixed block height, regardless of the building's height?
7. In regards to stacking and blocking, how can a user see occupancy based on agency bureau codes? Can occupancies be displayed separately based on user-defined criteria?
8. How can a user see where a space block fits? Can they move space blocks to another floor or into another building? Once a space block(s) has been moved, what does the overall stacking plan look like for this scenario? The solution shall allow users to seamlessly move space blocks between floors without altering actual assignment data or space geometry within the live or scenario module. The solution needs to be flexible while adhering to established stacking plan rules while accommodating unique functional constraints.
9. What space does a specific tenant or tenants occupy in a stack plan? The solution shall provide the flexibility to filter stacking plans by tenants or other pertinent data elements selected by the user. For multi-tenant buildings, tenants should be presented in a single comprehensive view.
10. What happens if a user tries to move tenants into 1) unoccupied space, 2) the attempted move results in floor expansion, or 3) if the space is occupied? Does the system alert the user and can the user proceed or dismiss their action?
3.0 Other Capabilities
1. Serve as a centralized repository where users can view, edit, upload and store asset plan data and information to include images, files, attachments, data, metrics, financial statements, and tenant housing plans.
2. Calculate figures, allow users to modify formulas, allow users to enter data and act as the system of record for designated data fields.
3. Provide visualization of data sets to include graphs, charts, maps, etc. and allow users to filter results based on selected criteria.
4. Capture user provided strategies and associated action/project plans with defined high level schedule milestones, accountable parties, and estimated costs.
5. Reports should be exportable (Excel and PDF) enhancing accessibility and usability.
6. Reports and dashboards should be at the occupancy, asset, market, regional, and national levels which capture, aggregate and summarize critical asset information, including financial performance, budget data, physical condition, liabilities, tenant details, market insights, and planned strategies.
7. Provide a photograph of an asset within the building profile.
8. If applicable, please provide any URL to a demo of your product.
| Disclaimer |
| 1. Introduction |
| 2. Background |
| 3. Description of Need |
| 3.1. Functional Requirements |
| 3.2. Technical Requirements |
| 3.3. Additional Security Requirements |
| 4. RFI Response Requirements |
| 5. Generic Cost Estimate |
| 6. RFI Submission Instructions |
| 7. Final Comments |
| Public Records and Request for Confidentiality |
| Copyrights |
| Content of Responses |
| Cost to Vendors |
| No Obligation to Issue Request for Quote |
| Appendix 1: System Definitions (as referenced in Figure 2) |
| Appendix 2: Vendor Questionnaire |
| 1.0 General (Question-Based Requirements) |
| 2.0 Stacking and Blocking (System Capability Questions) |
| 3.0 Other Capabilities |
File details come from the government source that posted it. Updated .