Attachment 3.6 - Phase II - Key eDelivery Functional Requirements Explanation.xlsx
XLSX spreadsheet 89 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 key functional requirements for an eDelivery construction management system solicited by the Federal Highway Administration, Office of Federal Lands Highway. The solicitation seeks a comprehensive web-based and mobile system to fully integrate all aspects of FLH's program construction activities, including engineering cost estimating, electronic bidding, construction management, and construction documentation management. The functional requirements address areas such as module interoperability, metric and customary unit support, specification management, accounting code configuration, schedule and option differentiation, bid history analysis, material and non-material incentive tracking, contracting methods, work activity tracking, document management, and legacy data migration. Bidders are required to explain how their solution will meet each requirement and any flexibility offered.
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
Functional Requirements_Sec. 1 Request for Proposal No. 693JJ321R000013 Attachment 3.6 - Phase II - Key eDelivery Functional Requirements Explanation Evaluation Factor 2 - 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 Will Meet These Requirements
| 1.1.b | Ability for each module to communicate with each other without a manual import/export of data | High |
| 1.4 | Ability to do a project in either US Customary units or metric units. See also Master Pay Item list (Section 6.3) | High |
| 1.5.a | Ability to have multiple, active Specification Books within the system | High |
| 1.6.1.a | Ability to add multiple unique construction accounts to the Project during any project phase. [user input] | High |
| 1.6.1.b | Ability to Split Pay Items into Separate Accounts by exact quantity (throughout the life of the project, i.e. in Design, Acquisition, and Construction) | High |
| 1.6.1.c | Ability to Split Pay Items into Separate Accounts by percentage (throughout the life of the project, i.e. in Design, Acquisition, and Construction) | High |
| 1.6.1.d | Ability to Chain Account Numbers during any project phase (i.e. prioritize accounts) | High |
| 1.6.1.e | Ability to have multiple, separate account chains in a project | High |
| 1.6.1.f | Ability to Override the calculated Current Approved (payment) Amount with a user entered payment amount for each Construction account | High |
&G
&"Calibri,Regular"&K0079C1Your Preferred Source for IT Acquisition Across the DoD | &K003A63www.esi.mil 1 ESICOMPASS081811
Functional Requirements_Sec. 2 Request for Proposal No. 693JJ321R000013
| 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
| 2.2.a | Ability to differentiate between Schedule, Options, and Pay Item Alternate | High |
| 2.4.a | Provide an explanation of the bid history statistical analysis that your system can provide. Explain what statistical information will be available to the designer based on the bid history data available on FLH projects and explain any flexibility provided to develop the unit price. Provide a workflow describing the unit price analysis process that will be utilized by the designer to evaluate historical bid prices in accordance with the requirements below. Identify the information that will be available to the designer and the steps the designer will take to identify the projects for analysis, select appropriate data, and identify the estimated unit price. | High |
| 2.4.b | Provide explanation for how bid history is handled between different Specification Books. | High |
| 2.4.i | Provide a method to Inflate Unit Prices for each pay item based on multiple Construction Cost Indices. See Section 6.4 for additional information/requirements for unit price analysis. | High |
| 2.5.a | Ability to add, edit and show multiple specific pay item material incentives for each milestone estimate’s schedules, options, and pay item alternates. (Pre-defined material incentive type, user defined dollar amount, such as potential total dollar amount of 401 Asphalt Material Quality Incentive). | High |
| 2.5.c | Ability to add, edit and show multiple individual project non-material incentives for each milestone estimate’s schedules, options, and pay item alternate (user defined dollar amount such as pavement roughness, partnering, etc.). | High |
&G
&"Calibri,Regular"&K0079C1Your Preferred Source for IT Acquisition Across the DoD | &K003A63www.esi.mil 1 ESICOMPASS081811
Functional Requirements_Sec. 3 Request for Proposal No. 693JJ321R000013
| 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
| 3.4.d | Ability to ensure confidentially of the contractor’s bid. | High |
| 3.4.m | Ability to control who can bid on a project. | High |
| 3.4.n | Ability to receive bid bonds. | High |
| 3.1 | Provide system flexibility to accommodate the above innovative contracting methods. Describe how your system can accommodate these innovative contracting methods. | High |
&G
&"Calibri,Regular"&K0079C1Your Preferred Source for IT Acquisition Across the DoD | &K003A63www.esi.mil 1 ESICOMPASS081811
Functional Requirements_Sec. 4 Request for Proposal No. 693JJ321R000013
| 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
| 4.2.2.2.a | Ability to enter multiple work activity codes. Each work activity code has the following information associated with it: work activity description, location, associated pay items, labor and equipment. | High |
| 4.2.4.b | Approval Workflow – creation by construction contractor, submission to FHWA, review and comment to contractor, approval to File | High |
| 4.4.1.i | Approval Workflow – creation by construction contractor or FHWA, submission to FHWA, review and comment to contractor, approval to File and contractor | High |
| 4.5.r | Ability to award options that were not initially awarded, as a contract modification and import all option information automatically. The information that would need to be imported would be the same as an individual project including all option pay items, quantities, awarded contractor unit prices, accounting information for those pay items, any incentives related to the option, etc. | High |
| 4.8.3.a | Provide the ability to download project documents such as PDF plan sets, and other Acrobat PDF and Microsoft Office documents (Word, Excel, PowerPoint, etc.) from the Document Management System to the mobile device while connected to the internet, and working within the application. | High |
| 4.8.3.c | Provide the ability to create, edit, and approve contractor daily reports, inspection daily reports (including labor and equipment, project work item), daily diaries, and other information while connected or not connected to the internet, and working within the application – approvals may be synced when back online | High |
| 4.8.3.e | Provide the option to sync the information manually or automatically on the mobile device back to the main project database when the user is able to reconnect back to the internet. The syncing with the main database should only require a few steps to complete, or occur automatically, after the user is reconnected to system. | High |
&G
&"Calibri,Regular"&K0079C1Your Preferred Source for IT Acquisition Across the DoD | &K003A63www.esi.mil 1 ESICOMPASS081811
Functional Requirements_Sec. 7 Request for Proposal No. 693JJ321R000013
| 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
| 7.13 | Provide access to the data for Government database administrators | High |
| 7.14.a | Ability to import legacy data. | High |
| 7.14.b | Upload legacy bid history data and general project information. | High |
| 7.14.c | In order to capture all projects, an upload of legacy data will have to be performed several times during the implementation process. | High |
| 7.14.1 | Import the following Design & Acquisitions Legacy Data - see Attachment 3.1, Section 7.14.1 | High |
| 7.14.2 | Import the following Construction Status Legacy Data - see Attachment 3.1, Section 7.14.2 | 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 .