Attachment A - Form B Technical Response.xlsx
XLSX spreadsheet 62 KB Posted
- Attached to
- RFP 252F-24 Bridge Management System
- Solicitation number
- BD-24-1206-40000-40000-111953
- Issued by
- Suffolk County, Massachusetts
About this file
This is a technical response form (Form B) from the Massachusetts Bay Transportation Authority (MBTA) seeking a Digital File Preservation System. The form details extensive functional, technical, and system requirements for a comprehensive asset management solution capable of handling inventory data for 650 bridges, 50 track miles of tunnel, 1,500 culvert and drainage structures, 43,000 linear feet of earth retaining structures, and 2 dams. The system must support bridge inspection data management, load rating calculations, regulatory compliance reporting, and integration with existing MBTA systems including 4D and Trapeze. The implementation timeline is specified as 6 months, with requirements for data migration, customization, training, and 24/7 support services.
The technical requirements specify that the solution must be cloud-based, ISO certified, comply with NIST 800-53-R5 standards, and provide comprehensive data security features. The system must support at least 100 simultaneous users and be accessible via both desktop and mobile devices. Key functionality includes automated workflows, digital signatures, GIS integration, and analytical capabilities for maintenance, repair, and replacement (MRR) planning. The form requires bidders to indicate whether capabilities are available in their standard system or require add-ons, with detailed explanations for implementation approaches, training plans, and support services.
View the file
Other files
Show all 23
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
Form B General Instructions
| RFP 16-24 - Digital File Preservation System |
| Form B - Technical Response Sheet |
| The Bid shall enable the MBTA to assess and evaluate the technical components of the Bid. The following requested information is a mandatory of the Request for Proposal (RFP). Failure to complete this form may be cause for the bid to be deemed as non-responsive and may result in disqualification. Wherever possible, responses should be representative in context to the Scope of Work. *Please do not reformat the cells or columns. Save file with the company name in the file name. |
| Section: Requested Information | Instructions |
| B1: Bidder Experience, Capabilities, and Qualifications | Respond free text in the Reponse column. |
| B2: Technical Capabilities of Proposed Product | Indicate standard and add-on features. Bidders are encouraged to elaborate on features in the Comments section. |
| B3: Implementation Plan | Respond free text in the Reponse column. |
| B4: Training and Support Services | Respond free text in the Reponse column. |
| B5: Software Accessibility | Respond free text in the Reponse column. |
| B6: Supplier Diversity | Respond free text in the Reponse column. |
B1 | Instruction
| TECHNICAL REQUIREMENTS INSTRUCTIONS |
| INSTRUCTIONS: |
| Bidders shall provide two-phase response to B2 Technical Requirements. |
For Phase 1 response, bidders shall fully complete the attached Form B2, in accordance with the below instruction.
For the Phase 2 response, bidders shall provide free text response to the technical and functional requirements under section 2.5-2.7.27 of the RFP,.
| Instruction for the Phase 1 Response |
| 1. Bidders shall complete questions under Tab 2 (Functional Requirements); Tab 3(Technical Requirements) and Tab 4 (Data & Security Requirements) of the attached Form B2 |
| 2. Respond to each and every capability (even ones that appear redundant). |
| 3. In column D ("Bidders Response"), indicate whether the proposed Solution provides the capability referenced in column C. |
| 4. A response of "No" in column G requires no additional response for that requirement. Supplier may provide relevant comments, however; comments will not be scored. |
5, Bidders should answer all questions, even if they appear to be similar or redundant.
6. A response of "Yes" in column F indicates that the solution does not meets the specified technical or functional requirements in its standard Off-the-Shelf format. However it may do so with modification. The level of effort involved in such modification must be qualified according to the below schedule, and must be included in the required explanation.
Add-Ons Schedule Level 1 - No cost or schedule impact to the standard solution whatsoever.
Level 2 - No cost but minor schedule impact to the standard solution Level 3 - Some cost and schedule impact to the standard solution Level 4 - Major cost and schedule impact to the standard solution
| Instruction for the Phase 2 Response |
| 1. Bidders shall review the entire scope of work under Section 2.0 of the RFP. |
| 2. In the context of the scope of work, bidder shall a free text narrative expaining in detail how the proposed system addresses the Technical and Functional requirements listed in Section 2.6.2 - 2.7.18 of the RFP. Bidders should feel free to add any pertinent information. The page limit for this narative is 40 pages. |
| Notes: |
| 1. Bidders shall subbmit the phase 1 spreadsheet and phase 2 narrative document as a single volume. |
| 2. Both Phase 1 and Phase 2 shall be assessed and scored by the MBTA. The scores for both phases shall be combined as determine by the MBTA. |
B1 | Functional Requirements
| Requirements | Bidder Response | MBTA REVIEW | ||||
| ID | Category | Capability | Is this capabilty available in your system? Yes / No | Add-On Required (Yes/No) | Explanation / Comments | |
| B2-FUNC-01 | Functional | Capacity to hold inventory data that includes 650 bridges and bridge like structures, approximately 50 track miles of tunnel, approximately 1500 culvert and drainage structures, approximately 43,000 linear feet of earth retaining structures and 2 dams. | ||||
| B2-FUNC-02 | Functional | Capacity to accept bridge inventory and inspection data, including bridge elements condition values, NBI/SNBI data, bridge inspection reports and associated data, and report recommendations. This should also apply to bridge-like overhead structures. | ||||
| B2-FUNC-03 | Functional | Capacity to accept bridge load rating data, including highway, railroad and transit load capacity data, information on load rating vehicles, load rating recommendations reports and recommendations. This should also apply to bridge-like overhead structures. | ||||
| B2-FUNC-04 | Functional | Capacity to accept tunnel inventory and inspection data, including tunnel element condition values, TIN data, tunnel inspection reports and associated data, and report recommendations. | ||||
| B2-FUNC-05 | Functional | Capacity to accept tunnel load rating data, including highway, railroad and transit load capacity data, information on load rating vehicles, load rating recommendations reports and recommendations. | ||||
| B2-FUNC-06 | Functional | Capacity to accept inventory and inspection data for culverts and drainage structures, including element condition data, channel chacteristics information and load rating data. This should also apply to drainage pipes. | ||||
| B2-FUNC-07 | Functional | Capacity to accept inventory and inspection condition data for Earth Retaing Structures (ERS) of all construction and material types. including inspection and load rating reports and associated recommendations. | ||||
| B2-FUNC-08 | Functional | Ability to accept dam inventory, condition and safety inspection reports and recommendations, and associated haydaulic and hyrology data. | ||||
| B2-FUNC-09 | Functional | Capacity to analyse and agregate inspection and load rating recommendations across user selectable parameters including number or group of bridges, type of identified repairs etc. This functionality should apply to all asset types. | ||||
| B2-FUNC-10 | Functional | Simplified user interface and be capable of both portal and mobile (field) data entry and the associated digitized data collection during bridge inspection. Off-site online access to historical bridge inspection reports during in-field inspections. This applies to tunnels, culverts and ERSs. | ||||
| B2-FUNC-11 | Functional | Regulatory Compliance: Reporting compliance with FTA, FHWA and FRA Regulations. For FHWA, compliance with the new NBIS and SNBI is required. The Federal Transit Authority (FTA) also established the Transit Asset Management (TAM) under 49 CFR 625 and National Transit Database (NTD) under 49 CFR 630, which applies to the tunnel assets. For the FRA, compliasnce with Bridge Safety Standard is required. The proposed solution should be capable of providing the regulatory reports that are mandated by the regulations. | ||||
| B2-FUNC-12 | Functional | Electronic Storage and retrival of historical, current and future inspection and load rating reports, related construction and repair plans, contract documents, legal agreements and similar documents that may be identfied by MBTA from time to time. This applies to all class of assets, including bridges, tunnels, culverts and ERSs. | ||||
| B2-FUNC-13 | Functional | Collect and intergrate data across multiple MBTA approved devices and generate inspection report document, in a format consistent with current MBTA Bridge Safety Inspection Reports. Inspection report documents must incorporate photos, drawings, and clearance and channel documentation, as well as written text and custom sketches. This also applies to other asset types. | ||||
| B2-FUNC-14 | Functional | Electronic routing of inspection report for review, correction approval and signatures, with trackable workflow from start to finish | ||||
| B2-FUNC-15 | Functional | The capability for two-way integration with existing and future software systems such as the updated 4D system and the MBTA enterprise system Trapeze. System should be capable of direct output to these software systems | ||||
| B2-FUNC-16 | Functional | Capacity to produce and distribute predefined data reports automatically, and to produce ad-hoc reports on demand. | ||||
| B2-FUNC-17 | Functional | Automated, trackable reporting of Inspection Critical Finding and Safety Concerns; distribution to predefined stakeholders for notification, review, action and documenting resolution. | ||||
| B2-FUNC-18 | Functional | Periodic management reporting on conditions across all asset types, | ||||
| B2-FUNC-19 | Functional | Capacity for special member inspection which provides for monitoring of the structural members at a specified frequency. Capacity for scheduling, workflow and monitoring associated with such structures, and be able to generate required statutory reports, if the bridge structure falls under the purview of the Federal Highway Administration (FHWA). | ||||
| B2-FUNC-20 | Functional | Bridge level maintenance support for selection of individual and appropriate actions for a specific bridge under consideration. | ||||
| B2-FUNC-21 | Functional | The proposed solution should be capable of reporting and generating a wide variety of technical and administrative reports and summaries of bridge conditions, bridge program budgets, and bridge maintenance, repair and replacement (MRR) programs. | ||||
| B2-FUNC-22 | Functional | Capacity for a fully integrated GIS functionality that supports geospatial data. The full graphical display of all bridges, tunnels, culverts and retaining walls with the asset datapoint integrated with its attributes, reports and other information. The GIS should be capable of 3-dimensional viewing of the asset and be scalable. Individual asset level queries should produce fully integrated result that includes graphics, associated condition and load rating data, and multimedia features etc. | ||||
| B2-FUNC-23 | Functional | Capability to accept contract information and cost data. Inspection and load rating cost data reported at individual bridge or tunnel TIN levels. The system should be capable of tracking inspection/load rating cost data with a view to create cost database to support future assignments. The same applies to all other assets. | ||||
| B2-FUNC-24 | Functional | Inspection reports are also submitted with recommendations and associated cost data. The system should be capable of accepting this information and providing an aggregated report and recommendations. | ||||
| B2-FUNC-25 | Functional | Configurable, automated generation of inspection schedules and past-due reports. This includes assigning responsibility to users such as MBTA staff and consultants, as well as workflow tracking of completed and pending inspections. | ||||
| B2-FUNC-26 | Functional | Storage and viewing of previous inspection report documents from a mobile device in the field. | ||||
| B2-FUNC-27 | Functional | Provide secure digital signature capability for final inspection report approval, | ||||
| B2-FUNC-28 | Functional | Ability to manually generate sketches while in the field, develop and select from predefined standard sketches, and insert such sketches into automatically generated report documents. | ||||
| B2-FUNC-29 | Functional | Ability to collect and visually represent the cross-section of any waterway and embankment along the fascia of the structure, in a format consistent with standard practice. | ||||
| B2-FUNC-30 | Functional | Ability to collect and visually represent vertical and horizontal clearance data in a format consistent with standard practice. | ||||
| B2-FUNC-31 | Functional | A configurable solution for documenting detailed estimates and actual final costs for bridge inspection and reporting activities associated with each bridge inspection record | ||||
| B2-FUNC-32 | Functional | The ability to produce exception reports when data conflicts exist, and the ability to generate reports and route those reports to the appropriate manager when certain data elements are changed, regardless of reason. | ||||
| B2-FUNC-33 | Functional | Integration of historical inspection data. Specifically, data from previous inspections that currently exists in MassDOT 4D environment, MBTA electronic records and paper based format will be migrated into the system. | ||||
| B2-FUNC-34 | Functional | Ability to operate without network connectivity, with effective synchronization once wireless connectivity is restored | ||||
| B2-FUNC-35 | Functional | Enable multiple users and mobile devices to simultaneously work on the same inspection report, with the ability for a single lead user to merge record changes from all users and to review, accept and reject changes made by all other users. | ||||
| B2-FUNC-36 | Functional | Minimum of 100 users must be able to access the server simultaneously without degradation of performance to any individual user | ||||
| B2-FUNC-37 | Functional | Integrated QA/QC and data validation functionality, for both inspection data and schedules. Specifically, the solution must include functionality that validates the correctness of data format and values entered into a single field, and, in some cases, verify the validity of the data in one field using logical checks against other data fields. At a minimum, this validation functionality must account for the potential errors identified in the FHWA National Bridge Inspection Data Checks as identified in the Bidders’ Library. | ||||
| B2-FUNC-38 | Functional | Customizable functionality to store relevant inspection cost data, including detailed estimate and invoice records | ||||
| B2-FUNC-39 | Functional | Customizable form creation, distribution, workflow, tracking, and storage | ||||
| B2-FUNC-40 | Functional | Mobile access from IOS or Android devices | ||||
| B2-FUNC-41 | Functional | Automated generation of inspection schedules and past-due reports | ||||
| B2-FUNC-42 | Functional | Ability to assign responsibility for individual and batch inspections to inspectors and consultants | ||||
| B2-FUNC-43 | Functional | Automated workflow of inspection assignments to inspectors and consultants | ||||
| B2-FUNC-44 | Functional | Workflow tracking of completed and pending inspections | ||||
| B2-FUNC-45 | Functional | Ability to store and view previous inspection reports from a mobile device in the field | ||||
| B2-FUNC-46 | Functional | Workflow tracking for inspection report development, review, and completion | ||||
| B2-FUNC-47 | Functional | Provide secure digital signature capability for final inspection report approval | ||||
| B2-FUNC-48 | Functional | Ability to manually generate sketches while in the field, develop and select from predefined standard sketches, and insert such sketches into automatically generated reports while in a field environment. | ||||
| B2-FUNC-49 | Functional | A configurable solution for documenting detailed estimates and actual final costs for bridge inspection and reporting activities associated with each bridge inspection record | ||||
| B2-FUNC-50 | Functional | Provide the ability to download developed software onto a device through conventional avenues such as Google for android, windows, and iOS systems and any other COV approved device | ||||
| B2-FUNC-51 | Functional | Ability to automatically generate and/or view inspection schedules based on user defined criteria using historical bridge inspection data. Basic scheduling functionality shall be pre-defined within the solution, based on publicly available federal requirements (NBIS, etc) and VDOT policies (IIM’s). Inspection schedules includes both structures due for future inspection, as well as identification of structures potentially past-due for inspection. | ||||
| B2-FUNC-52 | Functional | Ability to filter structures due for inspection based on geography (city, county, etc. data fields), structure attributes, inspection requirements, or other user defined attributes . | ||||
| B2-FUNC-53 | Functional | Ability to individually or batch select structures due for inspection, and assign such inspections to a user. | ||||
| B2-FUNC-54 | Functional | Ability to identify and track inspections that have been assigned to a user as distinct from inspections not yet assigned | ||||
| B2-FUNC-55 | Functional | Does the solution have the capability to capture the hierarchy of approvals with date and time stamp for each inspection report? Please explain. | ||||
| B2-FUNC-56 | Functional | Does the solution have the capability to integrate electronic approval and digital signature? Please explain? | ||||
| B2-FUNC-57 | Functional | Does the solution have the capability to provide an electronic review, correction and approval workflow for inspection record data and inspection report documents? Please explain. | ||||
| B2-FUNC-58 | Functional | Does the solution have the capability to provide an auto generated view of structures that are past due for inspection? Please explain. | ||||
| B2-FUNC-59 | Functional | Does the solution have the capability to auto set a reoccurring inspection schedule based on the month completed? Please explain. | ||||
| B2-FUNC-60 | Functional | Does the solution have the capability to auto alert within a predefined timeframe when a nonscheduled inspection is due (i.e., inspection due in 5 days)? Please explain. | ||||
| B2-FUNC-61 | Functional | Does the solution have the capability to auto assign inspections to a single user? Please explain. | ||||
| B2-FUNC-62 | Functional | Does the solution have the capability for MBTA users to select structures due for inspection and assign such inspections to other authorized users (inspectors)? Please explain. | ||||
| B2-FUNC-63 | Functional | Does the solution have the capability to build inspection reviews and/or approvals via processes into the inspection workflow (3-5 process based approvals required)? Please explain. | ||||
| B2-FUNC-64 | Functional | Does the solution have the capability to manage the review and approval of external user changes in the workflow via auto alerts? Please explain. | ||||
| B2-FUNC-65 | Functional | Does the solution have the capability to differentiate between internal MBTA users and external users? Please explain. | ||||
| B2-FUNC-66 | Functional | Does the solution have the capability to provide customizable inspection form creation, distribution, tracking, and storage? Please explain. | ||||
| B2-FUNC-67 | Functional | Does the solution have the capability to classify inspection types in the workflow (i.e., critical, routine, preventive/long-term recommendations)? Please explain. | ||||
| B2-FUNC-68 | Functional | Does the solution have the capability to provide a configurable alerting schedule? Please explain. | ||||
| B2-FUNC-69 | Functional | Does the solution have the capability to alert on bridge inspections that are incomplete (i.e., inspections that have started, but are not completed)? Please explain. | ||||
| B2-FUNC-70 | Functional | Does the solution have the capability to provide a dashboard that allows drill-down on pending inspections, completed inspections, and group assignments? Please explain. | ||||
| B2-FUNC-71 | Functional | Does the solution have the capability to provide a dashboard that allows drill-down on other scheduling-related data attributes (i.e., other than pending, completed or group assigned)? Please explain. | ||||
| B2-FUNC-72 | Functional | Does the solution have the capability to provide a schedule based on pre-defined criteria from the 2022 National Bridge Inspection Standards (NBIS) and Specification for National Bridge Inventory (SNBI)? Please explain. | ||||
| B2-FUNC-73 | Functional | Does the solution have the capability to filter all bridges into categories based on structure attributes? Please explain. | ||||
| B2-FUNC-74 | Functional | Does the solution have the capability to filter all bridges into categories based on inspection requirements? Please explain. | ||||
| B2-FUNC-75 | Functional | Does the solution provide georeferencing (i.e., relating a map or aerial photo image to a geographic coordinate)? Please explain. | ||||
| B2-FUNC-76 | Functional | Does the solution provide mobile mapping (i.e., collecting geospatial data from a mobile vehicle). Please explain. | ||||
| B2-FUNC-77 | Functional | Does the solution provide any functionality not covered in the above capabilities that may be beneficial to MBTA? If so, please explain. |
B1 | Technical Requirements
| Requirements | Bidder Response | MBTA REVIEW | |||||
| ID | Category | Category | Capability | Is this capabilty available in your system? Yes / No | Add-On Required (Yes/No) | Explanation / Comments | |
| B2-TECH-01 | Functional | Technical | Ability to identify and track inspections that have been started, partially completed, completed, or not yet started . Ability to define the display of inspection status in a dashboard module included with the solution. | ||||
| B2-TECH-02 | Technical | Technical | Automated notification of inspection and load rating actionable recommendations including but not limited to downgrade in condition rating, load restrictions, speed restrictions, height restrictions and bridge approach signage issues. Notification to be generated and transmitted to predifined stakeholders of the need to take an action consistent with addressing the identified issues. Such automated notification should filter through approval process to ensure an adequate review. | ||||
| B2-TECH-03 | Technical | Technical | Capacity for analytical functions. Using deterioration modeling and solution optimization, the system should assist decision-makers to select optimum cost-effective alternatives needed to achieve desired levels of service within the allocated funds and to identify future funding requirements. The data input to support such decision-making process should clearly be identified by the solution provider and associated supports services included in the delivery under this procurement. | ||||
| B2-TECH-04 | Technical | Technical | Be capable of network level analysis for MRR action that is based upon condition, load capacity and critically ranking and life cycle cost analysis optimization. | ||||
| B2-TECH-05 | Technical | Technical | The ability to designate certain data elements in either the proposed solution, the 4D and Trapeze to maintain primacy for that data element and, in some cases, link meta-data so that the most current data is recorded in all the systems. The proposed solution must provide for continuous and/or periodic (daily) synchronization of all data that is contained in all three databases. | ||||
| B2-TECH-06 | Technical | Technical | The proposed software solution shall be capable of being implemented within a period of 6 months. Anticipated services will include the customization, data migration, training, trouble-shooting and 24/7 user support services. | ||||
| B2-TECH-07 | Technical | Technical | Secured cloud storage of assets inspection data consistent with MBTA’s security requirements. (requires MBTA Security Management approval. | ||||
| B2-TECH-08 | Technical | Technical | All software development, customization, and configuration performed under this contract shall be the Intellectual Property of MBTA | ||||
| B2-TECH-09 | Technical | Technical | Development, customization and configuration progress shall be thoroughly documented through the use of inline documentation processes and by the production and delivery of a Software Design Document (SDD). | ||||
| B2-TECH-10 | Technical | Technical | All software, including source code and aforementioned documentation, shall be provided to the MBTA at regular intervals or as requested throughout the project | ||||
| B2-TECH-11 | Technical | Technical | All software, including source code and aforementioned documentation, shall be provided to MBTA if work is suspended or terminated for any reason, by either MBTA or the Vendor | ||||
| B2-TECH-12 | Technical | Technical | The winning bidder shall establish a professional relationship with the 4D hosting organization (MassDOT) and the Trapeze hosting organization will negotiate appropriate non-disclosure agreements (NDA) to protect the interest of both parties. This includes agreeing API connections. | ||||
| B2-TECH-13 | Technical | Technical | Access and full utilization of the developed system which is device agnostic | ||||
| B2-TECH-14 | Technical | Technical | Create a “sandbox” to model current and future developmental solutions. | ||||
| B2-TECH-15 | Technical | Technical | The application must function with MBTA computers and tablets running on Windows operating systems or iOS |
B1|Data & Security Requirements
| Requirements | Bidder Response | MBTA REVIEW | ||||
| ID | Category | Capability | Is this capabilty available in your system? Yes / No | Add-On Required (Yes/No) | Explanation / Comments | |
| B2-SYSD-01 | System Design | Is your product ISO 14721:2012 OAIS Reference Model compliant? | ||||
| B2-SYSD-02 | System Design | Is your product ISO 9001:2015 Quality Management compliant? | ||||
| B2-SYSD-03 | System Design | Is your product capable of Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH)? | ||||
| B2-SYSD-04 | System Design | Is your product compliant to Digital Preservation Level 4 as defined by the National Digital Stewardship Alliance (NDSA)? | ||||
| B2-SYSD-05 | System Design | Can your solution be deployed in cloud environments (e.g., AWS or Azure)? | ||||
| B2-SYSD-06 | System Design | Is your product compatible with Chrome, Edge, IE, Firefox, and Safari? Please describe what mobile operating systems your product is compatible with. | ||||
| B2-SYSD-07 | System Design | Does your system integrate with Microsoft365 products including Exchange and Office365? | ||||
| B2-SYSD-08 | System Design | Do you provide your clients a clearly documented application programming interface (API) upon request? | ||||
| B2-SYSD-09 | System Design | Will your system be able to integrate with existing specialized systems used at the MBTA like Trapeze EAM, eBuilder, ServiceNow, and Origami? Describe how your solution handles integrations of this nature. | ||||
| B2-SYSD-10 | System Design | Does your product provide the same complete functionality on mobile devices as the desktop application? If not, please explain the differences in functionality. | ||||
| B2-SYSM-01 | System Management | Do you provide access to a test environment with an exact copy of production data to your clients? If so, please describe how often the test data is refreshed. | ||||
| B2-SYSM-02 | System Management | Do you provide access to your data structures including data schemas, data tables, and data definitions to your clients? | ||||
| B2-SYSM-03 | System Management | Does your product allow configuration options (field renaming, field visibility, field validation, user dashboards, etc.)? If so, please describe. | ||||
| B2-SYSM-04 | System Management | Do you provide a secure FTP, cloud, or other transmission method for transferring files at implementation? If not, describe your preferred transmission method. | ||||
| B2-SYSM-05 | System Management | Does your product allow either for the batch correction of inaccurate or incomplete metadata using a Find/Replace function or something similar? | ||||
| B2-SYSM-06 | System Management | Does your product allow administrators to place legal holds on files, locking them from editing and deletion? | ||||
| B2-SYSM-07 | System Management | Does your product allow administrators to redact information from digital files while maintaining the integrity of the original file? If so, please explain how this is achieved. | ||||
| B2-SYSM-08 | System Management | Do you provide access to full data extracts to your clients upon request? If so, what is the turnaround time? | ||||
| B2-SYSM-09 | System Management | Does your product allow for a customizable user interface using MBTA branding? | ||||
| B2-USEM-01 | User Management | Does your product integrate with SSO / Active Directory Federation Services (ADFS)? | ||||
| B2-USEM-02 | User Management | Does your product allow non-MBTA employees user access? | ||||
| B2-USEM-03 | User Management | Does your product revoke user access based on status in active directory? | ||||
| B2-USEM-04 | User Management | Does your product allow for granular permissions for access based on role, group, and individual status? | ||||
| B2-PASS-01 | Password Management | Does your product provide the ability to reset passwords for users accounts and unlock accounts using desktop? | ||||
| B2-PASS-02 | Password Management | Does your product provide the ability to allow the user to register his challenge Q&As and allow the user to reset/change the password on its expiration by using security questions? | ||||
| B2-PASS-03 | Password Management | Does your product provide the ability to create strong password policy that enforces application-specific standards such as minimum/maximum password length and history? | ||||
| B2-PASS-04 | Password Management | Does your product provide the ability to delegated password management that allows management and administrators to change or reset passwords as needed? | ||||
| B2-PASS-05 | Password Management | Does your product provide the ability to lock an account after a configurable number of unsuccessful login attempts? | ||||
| B2-PASS-06 | Password Management | Does your product provide the ability to support cross domain password change and synchronization and even in case of IAM server components in different domain? | ||||
| B2-ING-01 | Ingest | Does your product allow for both ad-hoc and bulk ingest of files? | ||||
| B2-ING-02 | Ingest | Does your product conduct fixity checking of files at ingest? | ||||
| B2-ING-03 | Ingest | Does your product conduct virus scanning at ingest? | ||||
| B2-ING-04 | Ingest | Does your product quarantine and prevent ingest of files infected with a virus? | ||||
| B2-ING-05 | Ingest | Does your product perform file validation against PRONOM or another file registry at ingest? | ||||
| B2-ING-06 | Ingest | Does your product detect Personally Identifiable Information (PII) at ingest? | ||||
| B2-ING-07 | Ingest | Does your product perform Optical Character Recognition (OCR) on files at ingest? If so, please decribe performance, correction capabilities, etc. in the Comments. | ||||
| B2-ING-08 | Ingest | Does your product perform file deduplication and/or collision detection at ingest? | ||||
| B2-ING-09 | Ingest | Does your product offer automatic or manual file renaming options for duplicate files at ingest? | ||||
| B2-ING-10 | Ingest | Does your product provide ingest error notifications and an audit trail of ingest activitites? | ||||
| B2-ING-11 | Ingest | Does your product automatically assign a unique ID/primary key to files at ingest? | ||||
| B2-PROC-01 | Processing | Does your product have the ability for automatic metadata creation? | ||||
| B2-PROC-02 | Processing | Does your product have the ability for automatic metadata harvesting? | ||||
| B2-PROC-03 | Processing | Does your producat allow for manual metadata entry? | ||||
| B2-PROC-04 | Processing | Is your product compatible with standard descriptive metadata standards such as Encoded Archival Description (EAD), Dublin Core, PBCore, METS, MODS, XML? | ||||
| B2-PROC-05 | Processing | Does your product come with or have the ability to link to established thesauri, taxonomies, folksonomies, or ontologies? | ||||
| B2-PROC-06 | Processing | Is your product compatible with the PREMIS (Preservation Metadata: Implementation Strategies) data dictionary? | ||||
| B2-PROC-07 | Processing | Does your product allow for rights management? | ||||
| B2-PROC-08 | Processing | Does your product allow for package metadata? | ||||
| B2-PROC-09 | Processing | Does your product allow for automatic SIP (Submission Information Package) creation? | ||||
| B2-ACC-01 | Access | Does your product allow for a public interface? | ||||
| B2-ACC-02 | Access | |||||
| B2-ACC-03 | Access | Does your product allow users to create collections, packages, or starred files for future use? | ||||
| B2-ACC-04 | Access | Does your product allow users to preview files or see thumbnails? | ||||
| B2-ACC-05 | Access | Does your product provide users different views based on sorting information or layout styles (e.g. list, detail, grid, thumbnail)? | ||||
| B2-ACC-06 | Access | Does your product allow users to manipulate previews with the ability to zoom, pan, and rotate documents in 90° increments? | ||||
| B2-ACC-07 | Access | Does your product allow ad-hoc and batch printing and exporting of files to their native format or to PDF? | ||||
| B2-ACC-08 | Access | Does your product allow for automatic DIP (Dissemination Information Package) creation? | ||||
| B2-STOR-01 | Storage | Does your product allow for automatic AIP (Archival Information Package) creation? | ||||
| B2-STOR-02 | Storage | Are preservation and derivitive files stored on separate servers? | ||||
| B2-STOR-03 | Storage | Does your product provide a geographically dispersed data storage model? | ||||
| B2-STOR-04 | Storage | Do you have an exit strategy for your data should the MBTA need to port to another system? Please describe in the Comments section. | ||||
| B2-PRES-01 | Preservation | Does your product provide reliable, long-term bit preservation? | ||||
| B2-PRES-02 | Preservation | Does your product provide file redundancy? | ||||
| B2-PRES-03 | Preservation | Does your product provide automated integrity and validity checking? | ||||
| B2-PRES-04 | Preservation | Does your product provide automated re-characterization? | ||||
| B2-PRES-05 | Preservation | Does your product provide automated forward format migration? | ||||
| B2-PRES-06 | Preservation | Does your product provide maintenance of both preservation and derivitave files? | ||||
| B2-PRES-07 | Preservation | Does your product provide bulk file format migration? | ||||
| B2-SEAR-01 | Searching | Does your product provide simple searching? | ||||
| B2-SEAR-02 | Searching | Does your product provide advanced searching? | ||||
| B2-SEAR-03 | Searching | Does your product provide filters to narrow search results, sort search results by multiple criteria, and save searches? | ||||
| B2-SEAR-04 | Searching | Does your product allow users to search using browsable file trees? | ||||
| B2-SEAR-05 | Searching | Does your product provide truncation and wildcards functionality with searching? | ||||
| B2-SEAR-06 | Searching | Does your product allow for full-text searching of file contents? | ||||
| B2-SEAR-07 | Searching | Does your product allow for printing and exporting of search results? | ||||
| B2-RPRT-01 | Reporting | Does your product come with standard reports? Please describe the standard reports in the Comments section. | ||||
| B2-RPRT-02 | Reporting | Does your product provide the ability to create ad-hoc reports? Please explain the process in the Comments section. | ||||
| B2-RPRT-03 | Reporting | Does your product provide the ability to export reports in multiple file formats (.csv, .xlsx, .pdf, etc.)? Please list the file formats available. | ||||
| B2-RPRT-04 | Reporting | Does your product provide users the ability to schedule reports to run and save at specific intervals? Please describe in the Comments section. | ||||
| B2-RPRT-05 | Reporting | Does your product allow for reports to be governed by the same role and group-based security as the rest of the application? This means that based on a user's permissions, they can only report on data they have access to. | ||||
| B2-RPRT-06 | Reporting | Does your product use third-party reporting software? If so, provide details of the software in the Comments section. | ||||
| B2-SCRY-01 | Security | Is your product ISO 27001 certified? | ||||
| B2-SCRY-02 | Security | Is your product SOC 2 Type 2 accredited? | ||||
| B2-SCRY-03 | Security | Is your product GDPR compliant? | ||||
| B2-SCRY-04 | Security | Is your product aligned with NIST 800-53-R5? Please describe in the Comments section. | ||||
| B2-SCRY-05 | Security | Does your product log users out after a period of inactivity and/or when a browser is closed? | ||||
| B2-SCRY-06 | Security | Does your product have any processes for security updates to keep current with threats to the software? Please describe in the Comments section. | ||||
| B2-INTG-01 | Data Integrity | Do you have a documented Disaster Recovery Plan that you make available to your clients? | ||||
| B2-INTG-02 | Data Integrity | Does your product have regular backup retention schedules (daily, weekly, monthly)? Please describe the cadence in Comments section. | ||||
| B2-INTG-03 | Data Integrity | Does your product have the ability to restore full data from a backup without user intervention or disruption to the system? Please describe in Comments section. | ||||
| B2-INTG-04 | Data Integrity | Does your product provide full audit trail capabilities (series of records about an operating system, an application, or user activities)? Please explain. | ||||
| B2-DABU--1 | Data Access & Back Up | Does the solution have the capability to provide MBTA permissions: Create, Read, Update, Delete? Please explain. | ||||
| B2-DABU--2 | Data Access & Back Up | Does the solution have the capability to provide External permissions: Read, Update? Please explain. | ||||
| B2-DABU--3 | Data Access & Back Up | Does the solution manage access and provide a secure system for public or corporate use? Please explain. | ||||
| B2-DABU--4 | Data Access & Back Up | Does the solution maintain data and sufficient backups such that there is no possibility of data loss? Please explain. | ||||
| B2-DABU--5 | Data Access & Back Up | Does the solution have the capability to provide data backups no less than daily? Please explain. | ||||
| B2-DABU--6 | Data Access & Back Up | Does the solution restore data no less than 24 hours after any loss? Please explain. | ||||
| B2-DABU--7 | Data Access & Back Up | Does the solution provide security for data at rest, data in motion and data in use? Please explain. | ||||
| B2-DABU--8 | Data Access & Back Up | Does the solution have acceptable levels of encryption, particularly for PII/SII/CII and financial information, consistent with industry standards and COV requirements for CII and public-facing system? Please explain. | ||||
| B2-DABU--9 | Data Access & Back Up | Does the solution have the ability to ensure data security is not compromised because of general consumer access to services provided? Please explain. | ||||
| B2-DABU--10 | Data Access & Back Up | Does the solution meet COV security standards that require full encryption of device storage? Please explain. | ||||
| B2-DABU--11 | Data Access & Back Up | Does the solution support and include full database encryption of stored data (e.g. data at rest)? Please explain. | ||||
| B2-DABU--12 | Data Access & Back Up | Does the solution have currently or can adopt secure coding practices that prevent web application exploits (such as SQL injection and cross-site scripting)? Please explain. | ||||
| B2-DABU--13 | Data Access & Back Up | Does the solution have a procedure to inform MBTA (i.e., no more than two (2) hours) after a security-related issue has been discovered? Please explain and provide timeframe of notice. | ||||
| B2-DABU--14 | Data Access & Back Up | Does the solution have back-office security systems that protect data from existing and future threats that violate security or PII/SII to include (but not limited to)( malware, viruses, spyware, hackers, phishing, any other security threats presented by individuals, systems, countries, or any other entity not authorized to access the system? Please explain. |
B2 | Instruction
| Table B3 - Implementation Plan Instructions |
| 1. Bidders shall provide free text narrative response to the items listed in table B3 - Implementation Plan. In order to be considered complete response, all the questions should be addressed. |
| 2. Where the Table B3 element calls out a section of the RFP, bidders shall review that section and premise their response based upon the specific requirements |
| 3. When scheduel is called for, a simple fully annotated Gantt Chart with the key milestones identified will be acceptable. |
| 4. The knowledge of existing MBTA IT architecture in not assumed, therefore response to this prompt should be general in nature as applicable to typical large organization. |
| 5. Bidders should feel free to add any additional material that may help MBTA in determining the adequacy of the bidder's response. |
| 6. The maximum number of pages for the response is 20 pages. |
B2 | Implementation Plan
| B3: Implementation Plan | |
| Requirements | |
| ID | Question |
| B3-IMPL-01 | Please provide an overview of your implementation plan. |
| B3-IMPL-02 | What would be your anticipated implementation schedule with key milestones? |
| B3-IMPL-03 | What is your management approach |
| B3-IMPL-04 | How many employees would be allocated to the Project implementation? See Section 2.7.22 |
| B3-IMPL-05 | What is your test cycle approach? |
| B3-IMPL-06 | What is your plan for customization, if required? |
| B3-IMPL-07 | What is your plan for migration of existing data into the proposed system? |
| B3-IMPL-08 | What is your approach to data integration with other systems, specfocally, 4D and Trapeze? |
| B3-IMPL-09 | What Computer Hardware will be required for implementation? |
| B3-IMPL-10 | What is the approach to System with existing MBTA IT architecture? |
| B3-IMPL-11 | What is the training schedule to support the implementation? |
| B3-IMPL-12 | Software and Hardware Maintenance Requirements |
| B3-IMPL-13 | Please outline your Submittal Schedule. See Section 2.7.27 for additional information. |
| B3-IMPL-14 | Please ouline your Transition Plan. See Section 2.7.23 for additional information. |
B3 | Instruction
| Table B1 - Bidders Experience, Capabilities and Qualifications |
| 1. Bidders shall provide free text narrative response to the items listed in Table B4 - Bidders Experience, Capabilities & Qualifications. In order to be considered complete response, all the questions should be addressed. |
| 2. Where the Table B4 element calls out a section of the RFP, bidders shall review that section and premise their response based upon the specific requirements |
| 3. When scheduel is called for, a simple fully annotated Gantt Chart with the key milestones identified will be acceptable. |
| 4. The knowledge of existing MBTA IT architecture in not assumed, therefore response to this prompt should be general in nature as applicable to typical large organization. |
| 5. Bidders should feel free to add any additional material that may help MBTA in determining the adequacy of the bidder's response. |
| 6. The maximum number of pages for the response is 20 pages (exluding attachments) |
B3|Bidder Experience
| B1: Bidder Experience, Capabilities, and Qualifications | |
| Requirements | |
| ID | Question |
| B1-INFO-01 | State full company name. |
| B1-INFO-02 | Describe the ownership and/or strategic partnerships of your company. |
| B1-INFO-03 | State the total number of your company's employees. |
| B1-INFO-04 | When was your company established? Provide a brief description of your organization's core businesses. |
| B1-INFO-05 | What is your business continuity plan? What is the process and timeline for notifying your clients of significant organizational changes? |
| B1-INFO-06 | When was your proposed solution first brought to market? |
| B1-INFO-07 | Do you have experience with customers in the public sector? Provide short description with customer name, scope, and timeline. |
| B1-INFO-08 | Describe how many customer organizations (greater than 1,000 identities) are currently using your solution in a production capacity. |
| B1-INFO-09 | Is there pending litigation against your company or specific to your proposed solution to this RFP? |
| B1-INFO-10 | Terminations: Describe any situation over the past five (5) years in which a customer has terminated an agreement with your company for cause relating to the types of services and/or technology solution being requested in this RFP prior to the end of term of the agreement. |
| B1-INFO-11 | Please provide three references and contact information for each of the contracts listed above, as well as for any contracts Bidder has with the Commonwealth of Massachusetts. Include the name, title, organization, phone number and e-mail address of the reference. |
| B1-INFO-12 | Is your solution available through software resellers? If yes, indicate which reseller(s). |
| B1-TEAM-01 | Please provide details of the proposed project team, including prime and subcontractor. For each individual, please provide firm name, address and role in this contract. |
| B1-TEAM-02 | For eah individual named in preceeding paragraph, please provide full resume with information on education, professional registration and publications. Please include information on relevant project experience, role in cited projects, brief description of projects, role, location, year of project and contact person details. Please provide information as separate attachment. |
| B1-SAMP-01 | Provide an examples of relevant project completed by the prime or significant subcontractor including brief description of the project, value, staffing, year of project, ownership information, contact for reference and relevance to this contract. Please provide information as separate attachment. |
| B1-EXPR-01 | Please provide information on firm including profile of firms experience, average revenue for the last 5 years and number of employee by discipline. |
B4 | Instruction
| Table B4 - Training & Support Services Plan |
| 1. Bidders shall provide free text narrative response to the items listed in Table B4 - Training & Support Plan. In order to be considered complete response, all the questions should be addressed. |
| 2. Where the Table B4 element calls out a section of the RFP, bidders shall review that section and premise their response based upon the specific requirements |
| 3. When schedule is called for, a simple fully annotated Gantt Chart with the key milestones identified will be acceptable. |
| 4. Bidders should feel free to add any additional material that may help MBTA in determining the adequacy of the bidder's response. |
| 5. The maximum number of pages for the response is 20 pages. |
B4 | Training & Support
| Table B4 - Training & Support Services Plan | |
| Requirements | |
| ID | Question |
| B4-TRSP-01 | Provide full description of your training plan in support of the implementation of the solution. This should include training during the Initial Implelemtation Phase and during the Operational Phase. Please see Section 2.7.21 for additional information. |
| B4-TRSP-02 | Describe your company's approach to service management, including trouble shooting and technical support? |
| B4-TRSP-03 | Describe how users log incidents, errors, or bugs in your product. |
| B4-TRSP-04 | Do you make changes in software releases based on feedback from clients experiences? |
| B4-TRSP-05 | Do you provide a user community space either online or as a listserv for sharing ideas or asking questions? |
B5 | Instruction
| Table B5 - Software Accessibility Instructions |
| 1. Bidders shall provide free text narrative response to the items listed in Table B5 - Software Accessibility. In order to be considered complete response, all the questions should be addressed. |
| 2. Response to each prompt should be entered directly in Table 5. No separate attachment or document will be accepted. |
B5 | Software Accessibility
| Table B5: Software Accessibility | ||
| Requirements | ||
| ID | Question | Bidder Response |
| B5-SACC-01 | Is a completed VPAT available for your solution? If yes, please provide a copy with your response. If no, please indicate what plans, if any, you have to conduct a VPAT. |
| B5-SACC-02 | Is your solution and included documentation compliant with the following: Web Content Accessibility Guildelines (WCAG) version 2.1, levels A and AA? If not, in what areas is the solution noncompliant? |
| B5-SACC-03 | Can you commit to meet all the requirements of RFP Exhibit A - MBTA Accessibility Requirements? If not, please describe in detail any requirement(s) you are unable to meet. |
File details come from the government source that posted it. Updated .