Attachment 3.5 - Phase I - High-Level eDelivery System Requirements Explanation.xlsx
XLSX spreadsheet 75 KB Posted
- Attached to
- Federal Highway Administration, Office of Federal Lands Highway’s eDelivery Construction Management System
- Solicitation number
- 693JJ321R000013
About this file
This document outlines requirements for an eDelivery construction management system. The Federal Highway Administration seeks a comprehensive web-based and mobile system to integrate all aspects of its construction program activities, including engineering cost estimating, electronic bidding, construction management, and documentation management. Key capabilities include developing cost estimates, creating bid schedules and amendments, providing a secure electronic bidding portal at no cost to bidders, tracking construction progress payments and accounting, and generating reports. The system must allow communication between modules without manual data imports/exports, include both US customary and metric units, support multiple active specification books, and track costs by customizable accounts. It is to be hosted on a FedRAMP approved cloud and provide both production and test environments with separate databases.
View the file
Other files
Show all 14
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
Phase I_eDelivery Requirements Request for Proposal No. 693JJ321R000013 Attachment 3.5 - Phase I - High-Level eDelivery System Requirements Explanation Evaluation Factor 1 - High-Level eDelivery System Requirements
| Attachment 3.1 Requirements Reference | System Requirements | Importance | |
| (High, Medium, Low) | Out-of-the-Box |
Availability?
(Yes/No) Offeror's Explanation of How their Solution Meets these Requirements
| 1. Overall System Requirements | ||
| 1.0.a | Ability for each module to communicate with each other without a manual import/export of data | High |
| 1.0.b | Ability to do a project in either US Customary units or metric units | High |
| 1.0.c | Ability to have multiple, active Specification Books within the system. | High |
| 1.0.d | Provide the ability throughout the life of a project (in Design, Acquisitions, and Construction modules) to track the required cost account information by multiple unique accounts | High |
| 2. Design Module | ||
| 2.0.a | Develop Independent Government Estimates (Engineer’s Estimates) for Construction Projects | High |
| 2.0.b | Ability to use Bid History Data to develop Unit Prices | High |
| 2.0.c | Ability to Create, Edit and Delete Multiple Schedules, Options, and Pay Item Alternates in a Project. | High |
| 2.0.d | Provide the ability to add a Supplemental Description to the project pay items. | High |
| 2.0.e | Ability to track engineer’s estimate cost by accounts. (Pay Items are split into separate accounts by quantity or percent) | High |
| 2.0.f | Ability to develop required design reports (including report data exports) | High |
| 3. Acquisition Module | ||
| 3.0.a | Ability to create bid schedules | High |
| 3.0.b | Ability to create bid Amendments | High |
| 3.0.c | Provide a usable, secure eBidding submodule | High |
| 3.0.d | Ability to transfer a project from the Acquisition Module to the Construction Module | High |
| 3.5.e | No cost for a company to submit a bid for a FHWA project | High |
| 4. Construction Module | ||
| 4.0.a | Ability for the Construction Contractors to access projects | High |
| 4.0.b | Ability to track progress payment through the construction project | High |
| 4.0.c | Ability to track and manage accounting information | High |
| 4.0.d | Ability to create construction reports | High |
| 4.0.e | Ability access the project on a mobile device | High |
| 4.0.f | Ability to work offline | High |
| 5. System Administration & Reporting | ||
| 6.a | Provide User and Role Management including the abilities for the administrative users to create and customize the roles | High |
| 6.b | The system must support a master pay item list of items from the Federal Specification book | High |
| 6.c | The system must be able to support pay item list from multiple Specification books (i.e. FP14, FP22, etc.) | High |
| 6.d | Provide the ability for the users to create and save standard and ad-hoc queries | High |
| 6. System IT Requirements | ||
| 7.a | Provide details on two-factor authentication that will be used on the web-based part of the system for non-Government users | High |
| 7.b | The system work with at least the web browsers from Google, Microsoft, Apple, and Firefox | High |
| 7.c | The system provides a mobile offline option that works on at least Apple iOS | High |
| 7.d | Provide both a Production and Test/Sandbox instance of the system (two separate instances with two separate databases) | High |
| 7.e | The system is hosted in a FedRAMP approved cloud | High |
| 7.f | Ability to import legacy data | High |
&G
&"Calibri,Regular"&K0079C1Your Preferred Source for IT Acquisition Across the DoD | &K003A63www.esi.mil 1 ESICOMPASS081811 image1.jpeg
File details come from the government source that posted it. Updated .