Attachment 4 - FM System Technical Specifications-Amend 0001.xlsx
XLSX spreadsheet 31 KB Posted
- Attached to
- NIST Facilities Management System (FMS) Solution Licenses and Implementation Support Services Federal contract opportunity
- Solicitation number
- 1333ND21QNB130237
About this file
This solicitation seeks licenses and implementation support services for a Facilities Management System solution. The National Institute of Standards and Technology's Office of Facilities and Property Management requires a software-as-a-service Facilities Management solution providing both Enterprise Asset Management and embedded Enterprise Resource Planning capabilities. The solution must enable planning and managing daily operations, executing project management and preventative maintenance activities, and using one system for Work Management, Labor Management, Inspection Management, Materials Management, Operations Intelligence, Construction Project Management, Asset Management, and Preventative Maintenance. Questions are due by June 15, 2021 with responses provided in an amendment. The North American Industry Classification System code is 541512 for Computer Systems Design Services and the size standard is $30 million set aside for small businesses.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Attachment 2 - Instruction to Offeror_Amend 0001.pdf | ||
| Attachment 7 - Orals Presentation Script_Amend 0001.pdf | ||
| Appendix B - Gov Roles and Responsibilities.pdf | ||
| Attachment 1 - NIST_Facilities_SOW - Amend 0001.pdf | ||
| Attachment 6 - Responses to Questions-FINAL.pdf | ||
| Attachment 1 - Sol-1333ND21QNB130237.pdf | ||
| Attachment 4 - FM System Technical Specifications.xlsx | XLSX spreadsheet | |
| Attachment 7 - Orals Presentation Script.pdf | ||
| Appendix A - NIST OFPM Operations Overview-FINAL.pdf | ||
| Attachment 3 - Evaluation Criteria.pdf | ||
| Attachment 6 - Question and Answer Template.xlsx | XLSX spreadsheet | |
| Attachment 2 - Instruction to Offeror.pdf | ||
| Attachment 5 - Pricing Template.xlsx | XLSX spreadsheet | |
| Attachment 8 - Past Performance Questionnaire.pdf |
Show all 14
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Lists Requirement Metric Requirement Value Years Value Employees Value
| Supported (out of the box) | <5 | <10 |
| Supported via 3rd Party | 5-10 | 10-50 |
| Configuration Required | 10-25 | 50-250 |
| Modification Required | 25+ | 250-500 |
| Future Release | 500-1000 | |
| Not Supported | 1000-5000 | |
| 5000+ | ||
| Yes/No | Yes/No/Both |
| Yes | Yes |
| No | No |
| Both |
Technology
| Leading |
| Mainstream |
| Trailing |
Strategy
| Improve/Enhance |
| Maintain/Stabilize |
| Importance |
| Mandatory |
| Optional |
| Not Required |
Minimum Requirements
| Ref. No | Minimum Requirement | Yes/No | Comments |
| GNG01 | Proposed solution is a Commercial off-the-shelf (COTS) Software-as-a Service (SaaS) system that has one of the following security requirements: |
1) has been through the Government's FedRAMP authorization at the moderate level;
2) has an Assessment and Authorization (A&A) at the moderate level as it relates to the security requirements set forth in FISMA; or
| 3) meets the equivalent to security and privacy controls compliant with security requirements defined by applicable federal laws, regulations, policies, and standards (e.g., the Federal Information Security Management Act (FISMA), OMB Circular A-130, and FIPS Publication 200), and requirements in accordance with the NIST FMS SOW. | If Yes, please specify here which security requirement. | |
| GNG02 | Proposed solution is an EAM application solution that provides an embedded ERP capability with low/no code configuration. | |
| GNG03 | Proposed solution shall provide real-time data flow between the EAM and ERP components. | |
| GNG04 | Proposed solution shall provide mobile capabilities that are designed to function natively on iOS and Android devices in occasionally connected environments, enabling workers in the field to perform all aspects of Work Management including receiving, reviewing, and completing work orders, and all associated (view, consume, and order materials, review manuals, etc.) activities. | |
| GNG05 | Proposed solution shall provide a robust Construction Management component that integrates seamlessly into EAM. |
Functional Specifications
| Attachment 4 - FM System Functional Specifications |
| Please complete the table below indicating how your product(s) support the features and requirements. |
Definitions:
| • | Supported out-of-the-box: The feature is fully supported without any additional changes. | |||
| • | Supported via 3rd Party: This feature is supported but it requires the purchase of a 3rd party product in order to fulfill the requirement. | |||
| • | Configuration Required: The feature is supported but requires configuration to be used. | |||
| • | Modification Required: The product must be customized or altered in order to provide the feature. Customization means that the product requires changes to code within any part of the application architecture (application, database, etc.). | |||
| • | Future feature: This feature is planned to be supported in a future release and may not be immediately available. | |||
| • | Not Supported: The product does not provide the feature or functionality. | |||
| Ref. No. | Feature/Requirement | Product Feature | ||
| FN | Functionality | |||
| FN01.00 | Asset Management | |||
| FN01.01 | Asset Register | |||
| FN01.02 | Linear Assets | |||
| FN01.03 | Asset Hierarchies | |||
| FN01.04 | Locations | |||
| FN01.05 | Geographic Information Systems (GIS) | |||
| FN01.06 | Warranties / Claims | |||
| Specific Requirements | ||||
| FN01.07 | The system must have a library of operations and maintenance manuals and reference data that can be assigned to a specific asset(s) or job. | |||
| FN01.08 | The system must have the ability to track the life cycle for real property, including any projects associated with the real property. | |||
| FN01.09 | The system will allow engineers to edit job plans for assets and associate them with preventive maintenance work orders. | |||
| FN01.10 | The system will allow a user to report downtime on an asset or work order. | |||
| FN01.11 | The system will evaluate failures against expected service life. | |||
| FN01.12 | The solution must allow tagging and scanning of assets for reporting purposes. | |||
| FN01.13 | The solution shall manage assets by geographic location thru a Geographic Information System (GIS). | |||
| FN01.14 | The solution shall provide a warranties/claims component that tracks information to determine if an asset is still under warranty. | |||
| FN01.15 | The solution will provide integration with device monitoring systems to provide realtime device status. Potentially trigger corrective work order. | |||
| FN02.00 | Work Management | |||
| FN02.01 | Emergency Work Order | |||
| FN02.02 | Corrective Work Order | |||
| FN02.03 | Preventative Maintenance | |||
| FN02.04 | Meters | |||
| FN02.05 | Condition Based | |||
| FN02.06 | Bar Coding | |||
| FN02.07 | Project Work (incl. reimbursables) | |||
| Specific Requirements | ||||
| FN02.08 | The system must have an automatic routing process for reviewing and approving preventive maintenance work orders, maintenance slips and work orders. | |||
| FN02.09 | The system must have the ability to keep an electronic work order file, including the ability to upload documents associated with the work order, and provide an audit trail that includes version control and history logs. | |||
| FN02.10 | The system must have the ability to record electronic signatures. | |||
| FN02.11 | The system must maintain roles, permissions and delegation. | |||
| FN02.12 | The system must support handhelds or mobile devices to accommodate preventive maintenance work orders, maintenance slips, and work orders. | |||
| FN02.13 | The system shall be able to support and track alerting based on meters. | |||
| FN02.14 | The system will send email notifications to technicians about new work orders. | |||
| FN02.15 | The system shall track information at the work order level including labor planned, labor actual, materials planned, materials actual, tools planned, tools actually used, contractors/fed, and safety requirements. | |||
| FN02.16 | The system shall allow users to build a job cost estimate for work orders prior to approval. | |||
| FN02.17 | The system shall allow for work orders to be manually or automatically assigned. | |||
| FN02.18 | The system shall provide multiple options for scheduling preventive maintenance, including calendar, meter readings, and real-time operational parameters. | |||
| FN02.19 | The system shall provide written preventive maintenance procedures or a procedure code that references the tasks to be performed. | |||
| FN02.20 | The system shall estimate how many hours a preventive maintenance work order will require based on previously charged labor for that preventive maintenance. | |||
| FN02.21 | The system shall have the ability to display an activity log for a work order and display complete and incomplete tasks. | |||
| FN02.22 | The solution provides robust and rapid search capability to enable searches across all data, including active and archived files | |||
| FN03.00 | Labor Management | |||
| FN03.01 | Resources and Availability | |||
| FN03.02 | Personnel Administration | |||
| FN03.03 | Certifications | |||
| FN03.04 | Graphical Scheduling | |||
| FN03.05 | Automated Scheduling | |||
| FN03.06 | Embedded Training | |||
| FN03.07 | Health and Safety | |||
| Specific Requirements | ||||
| FN03.08 | The system must have the ability to provide labor projections. | |||
| FN03.09 | The system shall link to the personnel system to pull employee data information. | |||
| FN03.10 | The system must have a scheduling component that enables work orders/preventive maintenance work orders to be scheduled in advance, assigned to the appropriate employees. The target is to provide for scheduling projects 12-16 weeks in advance. | |||
| FN03.11 | The system will allow a manager to level workloads, assign set amounts of each work order type, keep records of work order types completed and assigned to personnel in order to balance time between individuals and work order types. | |||
| FN03.12 | The system shall have the ability to track resource dependencies across multiple projects | |||
| FN03.13 | Predict and track critical inter-dependencies and alert or adjust project schedules accordingly | |||
| FN03.14 | The solution must allow configurable labor rates. | |||
| FN03.15 | The solution shall have the ability to track staff certifications, skills, training and safety requirements for assigning appropriate individuals to tasks. | |||
| FN03.16 | The solution shall allow the assignment and scheduling of work orders based on resources availability. | |||
| FN03.17 | The solution shall allow the viewing of work order backlog, work in progress, and completed work orders. | |||
| FN04.00 | Construction Project Management | |||
| FN04.01 | Enterprise resource Planning (ERP) solution for project management | |||
| FN04.02 | Construction Contract Management | |||
| FN04.03 | Construction Project Budget, Schedule Scope, Risk management | |||
| FN04.04 | Construction Program/Portfolio Level Budget, Schedule Scope, Risk management | |||
| FN04.05 | Construction Project Budget, Schedule Scope, Risk reporting | |||
| FN04.06 | Construction Program/Portfolio Level Budget, Schedule Scope, Risk reporting | |||
| FN04.07 | Construction site/project outage | |||
| FN04.08 | Construction site/equipment lock out tag out | |||
| FN04.09 | Cost Estimating | |||
| FN04.10 | Bi-directional Interface to Project Mgmt. System | |||
| FN04.11 | Capital Planning (long-range facilities planning) | |||
| Specific Requirements | ||||
| FN04.12 | Bid management, contract management, Requests For Information, Change orders | |||
| FN04.13 | Budget management, Commitments/Obligations | |||
| FN04.14 | Project Budget, Schedule,Scope, Risk Planning, management, monitoring and reporting | |||
| FN04.15 | Architect Supplement Instruction (minor additional details needed on drawings) | |||
| FN04.16 | Submittals (contractor submits to NIST for review and approval), Transmittals (from NIST to contractor for completion) | |||
| FN04.17 | Project Daily Log, Project Photos, Drawings, Documents (incl req'd Safety documentation) | |||
| FN04.18 | Planning and Coordination Meetings per contract requirements and reports | |||
| FN04.19 | Punch Lists | |||
| FN05.00 | Inspection Management | |||
| FN05.01 | Serial / Lot Control | |||
| FN05.02 | Inspection Loops | |||
| FN05.03 | Calibration | |||
| FN05.04 | Routes | |||
| Specific Requirements | ||||
| FN05.05 | The solution must have the ability to conduct, assign, and track site inspection. | |||
| FN05.06 | The solution shall allow the creation of inspection punch lists and loops to be executed at a specified frequency. | |||
| FN05.07 | The solution shall allow the specification of inspection routes to optimize the completion of inspection activities. | |||
| FN05.08 | The solution shall allow the use of checklists to ensure accountability. | |||
| FN06.00 | Materials Management | |||
| FN06.01 | Storeroom Management | |||
| FN06.02 | Inventory Control | |||
| FN06.03 | Lot / Serial Number Tracking | |||
| FN06.04 | Issuing | |||
| FN06.05 | Receiving | |||
| Specific Requirements | ||||
| FN06.06 | The system must allow multiple UPC's to reference one stock number. | |||
| FN06.07 | The system must contain the functionality to maintain a minimum of two storerooms. The storerooms would be managed independently of each other but tracked within the same system. | |||
| FN06.08 | The system must support the use of scanners for receiving, transfers, and periodic inventory of materials. | |||
| FN06.09 | The system shall allow for material transfers between warehouses. | |||
| FN06.10 | The system shall allow for both automatic and manual requisition when a reorder point is reached. | |||
| FN06.11 | The system shall notify planners which work orders can be fulfilled when a part is received. | |||
| FN06.12 | The system shall allow storeroom items to be viewed and purchased by NIST employees using a web-based interface. | |||
| FN06.13 | The solution must allow storeroom management to track and review parts inventory and create new requisitions and purchase orders. | |||
| FN07.00 | Procurement | |||
| FN07.01 | Purchase Orders | |||
| FN07.02 | Contracts | |||
| FN07.03 | Approval Workflows | |||
| FN07.04 | Quotes | |||
| Specific Requirements | ||||
| FN07.05 | The system must have the ability for users to complete all procurement forms on-line and submit them electronically to the facility management organization. | |||
| FN07.06 | The system must be able to track the procurement status in the Department-level procurement system from start to finish. | |||
| FN07.07 | The system must have an ordering module to generate Requests for Quote (RFQ's), compile results, and generate Purchase Orders (PO's). | |||
| FN08.00 | Financial Integration | |||
| FN08.01 | GL Segments | |||
| FN08.02 | Journal Vouchers | |||
| FN08.03 | Labor Transactions | |||
| FN08.04 | Inventory Transactions | |||
| FN08.05 | Budgeting | |||
| FN08.06 | Material Transactions | |||
| FN08.07 | Billing | |||
| FN08.08 | Capitalized Work in Process (CWIP) | |||
| Specific Requirements | ||||
| FN08.09 | Provides multi-site functionality (ability to track all aspects of assets, work, materials, etc. within the same system but different sites) | |||
| FN08.10 | The system must complete an automatic closeout purchase order reconciliation process with the Department-level financial system. | |||
| FN08.11 | The system must be able to link estimated and actual costs from credit card purchases, purchase orders and storeroom requests, to the appropriate Work Order record. | |||
| FN08.12 | The system must have the ability to assign the appropriate General Ledger Account based on specified criteria to a maintenance slip or reimbursable work order. | |||
| FN10.00 | Operational Intelligence | |||
| FN10.01 | KPI and Dashboard | |||
| FN10.02 | Inbox | |||
| FN10.03 | Ad-Hoc Reporting | |||
| FN10.04 | Operational Perfomance Monitoring | |||
| FN10.05 | Compliance | |||
| FN10.06 | Audit Trail | |||
| FN10.07 | Alerts | |||
| Specific Requirements | ||||
| FN10.08 | The system must provide automatic email notifications. The system must also have the ability for turn on/turn off notifications. | |||
| FN10.09 | The users shall have a dashboard that allows them to quickly organize their work by what is required of them in the system. | |||
| FN10.10 | The system shall automatically be able to generate a list of affected buildings and areas associated with upcoming preventive maintenance work orders. | |||
| FN10.11 | The system shall include a report writer (the ability to create custom reports). | |||
| FN10.12 | The system shall be able to track equipment downtime. | |||
| FN10.13 | The system shall be able to forecast equipment downtime. | |||
| FN10.14 | The system shall provide functionality that allows variance to be measured between baseline and actual project milestone dates and produce a report of overdue activities. | |||
| FN11.00 | Customer Service | |||
| FN11.01 | Service Requests | |||
| FN11.02 | Knowledgebase | |||
| FN11.03 | Customer Portal | |||
| FN11.04 | Billing | |||
| Specific Requirements | ||||
| FN11.05 | The system will allow users to create and track service request tickets. | |||
| FN11.06 | The system shall allow customers to view recent work activity for service request tickets that they submit | |||
| FN11.07 | The system must have the ability to send customer satisfaction surveys when the work has been completed. | |||
| FN12.00 | Architecture | |||
| FN12.01 | Provides standard out-of-the box integration capabilities and any adapters that you have for business systems (financial, time keeping, procurement, other industry applications) | |||
| FN12.02 | The system shall provide native mobile functionality (designed for mobile using HTML5/responsive design or app for Android/iOS) | |||
| FN12.03 | The system shall allow for occasionally connected, offline data capture and synchronization | |||
| FN13.00 | Mobile Capabilities Requirements | |||
| FN13.01 | The solution shall have the ability for employees to perform work using mobile devices including alerts and notifications for the newly assigned work order. | |||
| FN13.02 | The solution supports offline capabilities for devices not connected to a network, with the ability to sync with the application when reconnected. | |||
| FN13.03 | The mobile application shall provide the full complement of services available in the application. |
NOTE: All requirements must be filled in and the box marked "COMPLETE" --> INCOMPLETE
File details come from the government source that posted it. Updated .