STATE OF ALASKA RFP NUMBER 2516H009 AMENDMENT NUMBER ONE (1)

Transcription

1 STATE OF ALASKA RFP NUMBER 2516H009 AMENDMENT NUMBER ONE (1) AMENDMENT ISSUING OFFICE: Department of Transportation & Public Facilities Statewide Contracting & Procurement P.O. Box (3132 Channel Drive, Room 350) Juneau, Alaska THIS IS NOT AN ORDER DATE AMENDMENT ISSUED: June 20, 2016 RFP DUE DATE AND TIME: July 6, 2:00 PM Alaska Time The following change is required: RFP TITLE: Highway Performance Monitoring Integration System (HPMS) 1. The Procurement Officer of Record is reassigned to: Becky Gattung becky.gattung@alaska.gov Phone: (907) The RFP due date and time is extended until July 11, 2016 at 2:00 PM Alaska Time. 3. The number of proposals required in RFP Section 1.01 is amended to: Offerors must submit one (1) original with three (3) copies and one electronic device (CD-ROM or Flash Drive) of their proposal, in writing, to the procurement officer in a sealed package. Submit only one Cost Proposal clearly identified in a separate, sealed envelope. No portion of the cost proposal shall be included within the body of the proposal. Submissions must be addressed as follows: Department of Transportation Statewide Contracting and Procurement Attention: Becky Gattung Request for Proposal (RFP) Number: 2516H009 Project Name: Highway Performance Monitoring Integration System (HPMS) 4. RFP Section 1.02, Contract Term and Work Schedule is amended to: The length of the contract will be from date of award through December 31, 2017 with five (5) one year optional renewals. Renewals may be exercised solely by the State at its discretion.

2 Page 2 of 4 RFP 2516H009 - Amendment 1 5. RFP Section 1.03, Purpose of the RFP is amended by removing the following: The State will only consider proposals from financially responsible firms currently engaged in the business of telecommunications services. Each Offeror must provide the required documents, in the required format, as outlined in this RFP, in order to be considered RESPONSIVE. 6. RFP Section 3.02, Contract Price Adjustments is amended to: Hourly Rates for the performance of Optional Tasks 4.0 through 8.0 will remain firm through December 31, The Contractor may request a price adjustment, in writing to the Procurement Officer, 30 days prior to the contract renewal date. If the Contractor fails to request a CPI price adjustment 30 days prior to the renewal date, the adjustment will be effective 30 days after the State receives their written request. Price adjustments for Hourly Rates will be made in accordance with the percentage change in the U.S. Department of Labor Consumer Price Index (CPI-U) for All Urban Consumers - All Items - Anchorage Area. The price adjustment rate will be determined by comparing the percentage difference between the CPI in effect for the base year six-month average of January through June 2017 and each January through June six-month average thereafter. The percentage difference between those two CPI indexes will be the price adjustment rate. No retroactive contract price adjustments will be allowed. 7. RFP Section 5.03, Task 2: Training is amended. The Contractor will perform one (1) initial training session and one (1) follow-up training session on-site at the DOT&PF facility in Juneau, Alaska for up to eight (8) DOT&PF staff. The initial training session will familiarizes users with the features necessary to operate the system, adding data, making changes to data sets, queries reports etc. Once DOT&PF s 2016 data is available in the system, the follow-up training session will be conducted by the Contractor. The follow-up session will provide necessary training to ensure a successful HPMS submittal to FHWA using the new system. Proposals should describe the proposed training and length of each training session. Travel expenses incurred by the Contractor under Task 2 must be included in their cost proposal. 8. RFP Section 5.03, Task 3: HPMS Integration Software Operations, Technical Support and Software Maintenance is amended to add the following: The Contractor will provide technical support to DOT&PF staff utilizing the system. The Contractor shall provide technical support via and direct telephone during Alaska hours, 8:00 AM to 4:30 PM, Monday thru Friday (preferably). If unable to provide this support, the Contractor shall provide hours as close to the preferred times as possible. The Contractor will provide DOT&PF with a Service Level Agreement (SLA) identifying at a minimum: procedures for initiating requests for service; procedures for escalating service requests; Contractors approach to supporting requests for technical assistance and reports of system outages or functional issues with the system.

3 Page 3 of 4 RFP 2516H009 - Amendment 1 9. RFP Section 5.04, Task 7: Additional Training and On-Site Technical Support is amended to remove on-site technical support as follows: Task 7: Additional Training Additional training may be requested by the DOT&PF Project Manager. The Contractor may perform training via webinar, a walk-through by telephone or on-site at the DOT&PF facilities in Juneau, Alaska. Deliverable 7.1: Conduct as-needed training. The following is in response to questions posed by a potential offeror: 10. Question: RFP Section 6.08 Cost Proposal states. Offerors must complete and submit the Cost Proposal Summary provided in the RFP. No changes or alterations to this Cost Proposal Summary are permitted. In Section 2 of the Cost Proposal Summary, it states, If the Offeror s job classifications differ from those provided, the Offeror must furnish a job description, the title, and hourly billing rate for that like-position classification. The first table included in Section 2 provides the names of several different Job Classes and associated estimated number of hours for each one. If we wish to change this table to add a Job Class (e.g., Database Administrator), may we do so? If so, how should we assign hours to the proposed new Job Class? 11. Answer: Offerors may not add job classes to the existing classes noted in the first table in Section 2. If your job class is not a like position, (for example, a like job class would be Office Manager, versus Administrative Support) then the job class offered must be identified in the second table of Section Question: Is it possible to adjust the estimated number of hours in the table to better reflect what we anticipate would be needed to support the State s requirements, for example, reducing the Project Manager/Principal in Charge from 200 to 150 hours and increasing the Senior Programmer from 100 to 150 hours? Answer: No. The estimated number of hours in the hourly rate table may not be changed. The number of hours is a mechanism used for evaluation purposes only. The hourly rate, job class and employee(s) assigned to each job class become the billing rates in the resultant contract. Per RFP Section 3.11 Contract Personnel, changes to personnel must be preapproved and will be assigned the contractual hourly rates based on their job class. 13. Question: In that table, there is a row for Associate. Can you describe the type of role that is supposed to be, e.g., clerical or something more high-level like a Subject Matter Expert. Answer: This is a typographical error. The correct position is Training Associate as it relates to the Contractor s performance in Task 7. The Cost Proposal Summary is amended.

4 Page 4 of 4 RFP 2516H009 - Amendment Question: The timeline in Section 1.02 Contract Term and Work Schedule on page 5 of the RFP indicates that full implementation of the HPMS solution is expected by November 1, What is driving that implementation date? Would it be possible to extend that date for 30 days or so? Answer: The implementation date is based on data delivery for the 2017 HPMS submittal to FHWA. It may be possible to push that date slightly depending on the circumstances. 15. Question: The timeline included on page 22 of Attachment 1 HPMS Integration Software Concept of Operations that includes 2015 dates and appears to contradict some of the dates in Section 1.02 of the RFP. Can you clarify? Answer: 4.2 Timeline on Page 22 of Attachment 1 is updated. 16. Question: In the Map to ConOps column of Table 1 Requirements Related to the Manual User Interface, MMUI-14, MUI-14-1, MUI-14-2, MUI , MUI , MUI-15, MUI-15-1, MUI-16, MUI 19, MUI-19-1, MUI-19-2, MUI-19-3, and MUI-19-4 are shown to map to through of Attachment 1 HPMS Integration Software Concept of Operations. We cannot find reference to through in the ConOps document. Can you clarify? Answer: These are typographical errors. Attachment 2 is amended. This is a mandatory return Amendment. Your proposal may be considered non-responsive and rejected if this signed amendment is not received [in addition to your proposal] by the date and time proposals are due. Becky Gattung Procurement Officer PHONE: (907) FAX: (907) NAME OF COMPANY DATE SIGNATURE PRINTED NAME

5 ATTACHMENT 1 HPMS Integration Software Concept of Operations (HPMS ConOps) 4.2 Timeline HPMS Integration Software Implementation Timeline Action / Activity Target Date(s) Project Initiation June 15, 2015 Project Planning (Concept of Operations, Systems July, June, 2016 Requirements, RFP Language) Procurement June, 2016 July, 2016 Contract Award August, 2016 System Implementation August, 2016 November, 2016 Production Deployment Achieved (Activity #1 & Estimated November 2016 Activity #2) HPMS Submittal Period April 2017 Software maintenance and support from vendor Ongoing (Activity #4) Hardware hosting & support from ISSD (Activity 5) Ongoing: Start date November 2016 Vendor support of transition to ESRI Roads & TBD Highways (Activity 3) Page 22

6 ATTACHMENT 2 HPMS Integration Software System Requirements Version 1.0 This document describes the functional requirements documented by the DOT&PF HPMS Project Team and is a required document to be submitted with your Technical Proposal. Offerors: You must complete the far right column. We ask that provide a text response for each requirement (each row) and describe whether your proposed system is able to meet or exceed the requirement. You may also use the narrative to describe an alternate functionality that your proposed system offers that will satisfy some or all of the requirement.

7

8 Table -1 Concepts , , SI-1 Requirements Related to System Interfaces SI-1-1 SI-1-2 SI-1-3 SI-2 The System shall acquire HPMS feature data from the DOT&PF Roadway Data System (RDS). Note: The DOT&PF GIS/Mapping Section is currently operating an Environment Systems Research Inc. (ESRI) Spatial Database Engine/Oracle Geodatabase to store and manage a linear reference based centerline network and associated roadway features and attributes. The System shall maintain a connection to the DOT&PF RDS and automatically interface with the RDS to pull data without the need for users to manually transfer data. The trigger for when the System executes a pull of data from RDS, and what data to pull shall be users initiating the request in the user interface. The System shall integrate with DOT&PF s ESRI products to acquire the RDS data elements selected by the authorized user and store the data within the HPMS Integration Software. The System shall include the ability to acquire data from the RDS ESRI Roads & Highways interface when implemented SI-3 The System shall integrate with the Transmetric TrafficServer Traffic data system (AK TS) operated by DOT&PF in order to pull traffic data when needed. SI-3-1 The System shall maintain a connection to AK TS and automatically interface with AK TS to pull data without the need for users to manually transfer data. 3

9 Concepts SI-3-2 SI-3-3 The trigger for when the System executes a pull of data from AK TS, and what data to pull shall be users initiating the request in the user interface. The System shall connect to the AK TS and acquire the data elements, summary data, or summary reports selected by the authorized user and store the data within the HPMS Integration Software SI-4 The System shall acquire traffic data from the DOT&PF Manual Field Check Tool. SI-4-1 SI-4-2 The System shall acquire data from the DOT&PF Manual Field Check Tool when initiated by an authorized user. The System shall connect to the DOT&PF Manual Field Check Tool Database (Access Database) and acquire the data elements selected by the authorized user and store the data within the HPMS Integration Software , , , SI-5 SI-6 The System shall have demonstrated capability to interface to additional databases or systems in order to support future uses identified by DOT&PF. The System shall automatically connect to the appropriate external system, maintain a connection, and execute a data pull when initiated by an authorized user through the user interface. 4

10 Concepts , , , SI-6-1 SI-6-2 The data pulled shall include the data described by the data elements time period identified by users through the user interface. The System shall track status of the process of connecting to external systems and pulling data in order to present updates to the users through the user interface SI-7 The System shall allow DOT&PF staff to perform minor configuration changes to the data acquisition process. Configuration changes may include: - Identifying new IP addresses or external systems; - Identifying new database tables or naming conventions SI-8 The System shall enable the vendor of the system to modify the configurations to external systems without the need for software changes. 5

11 Table -2 Map to ConOps , Requirements related to the Manual User Interface MUI-1 MUI-1-1 MUI-1-2 The System shall provide a mechanism for authorized users to access the user interface from any Internet SOA Intranet accessible location, using common Internet browsers. The System shall only allow authorized users to access the HPMS Integration Software. LDAP/VPN access is used with other systems; should be an administrative interface to allow user access and establish user accounts MUI-2 The System shall have an administrative interface, allowing authorized individuals to create and update accounts granting users permissions MUI-2-1 DOT&PF shall have a mechanism to assign privileges to user accounts. As a minimum, the following privileges shall be determined by DOT&PF when creating a user account: - Administrator with authority to create/edit users and assign privileges; - View & Edit with authority to upload/edit and view data, and generate reports (all authority except create/edit users); - View Only with authority to view data, generate reports, but not edit data. 6

12 Map to ConOps MUI-3 The System shall include a help feature to assist users through the user interface. Viewing Data and Information MUI-4 The System shall include a Dashboard Summary display function that displays a summary of the HPMS process MUI-4-1 The Dashboard Summary shall include details about activities need to be performed as part of the FHWA HPMS process MUI-4-2 The Dashboard Summary shall provide a mechanism for users to view the current status of the Alaska HPMS process, including such things as: - What data has been acquired and translated; - What summary data and/or calculations have been generated - Number of Validation errors - Missing data - Validations performed MUI-5 The System shall provide a mechanism for authorized users to request to view data. MUI-5-1 When requesting to view data, users shall be able to select from all data that has been acquired from external systems or entered in to the HPMS Integration Software, regardless of who created or acquired the data. 7

13 Map to ConOps MUI-5-2 The System shall provide a mechanism for users to view a summary of data that is stored in the HPMS Integration Software, and select the data to view MUI-5-3 The System shall include a map interface to enable users to select locations for which they wish to view data. MUI MUI The map display shall enable users to pan and zoom the map in order to orientate the map display to allow users to select locations. The System shall use the DOT&PF Roadway Data System (RDS) Geodatabase as the centerline road network when presenting Users with maps to select locations for data display MUI The map display shall provide a mechanism for users to select one or multiple locations, either solely through the map display or through the map display and complementary tools such as drop-down displays. Loading Data from External Systems , , MUI-6 MUI-6-1 MUI-6-2 The System s user interface shall enable users to select the external system they wish to pull data from. The System s user interface shall enable users to select from available external systems that have been configured within the HPMS Integration Software to support data acquisitions. The System s user interface shall enable users to select the data type for the HPMS Integration Software to acquire from each external system selected. 8

14 Map to ConOps , , , , , MUI MUI MUI-7 MUI-7-1 MUI-8 MUI-8-1 Users shall be able to select multiple data types at one time. Users shall be able to select the date range of data to acquire from external systems. The System shall provide a display of the status of data pulls to the user. The System shall display the results of the data pull, and identify when a data pull was not successful. The System shall display the results of format checks performed on the data when acquiring data from external systems and translating it into HPMS compatible formats. When data translations are not executed successfully, the System shall display a notice to users that the data translation was not successful, and display the errors that occurred MUI-8-2 The System shall provide any supporting data possible to describe why the data acquired was not translated properly during the acquisition process. Entering / Editing Data , , MUI-9 MUI-9-1 MUI-9-2 The System shall provide a mechanism for users to select data elements to be overwritten for the current year. The System shall provide a mechanism for users to select one or multiple data elements to be overwritten. The System shall enable the users to enter notes describing the reasons why the data is being overwritten this year, and shall retain notes. 9

15 Map to ConOps 3.9, 6.7 MUI-9-3 The System shall provide a mechanism for users to select the approach for overriding current data, and shall execute the calculations necessary to implement the selected approach , , , , , , MUI MUI MUI MUI-9-4 MUI MUI-10 MUI-10-1 MUI-10-2 The System shall enable users to select Interpolation as an approach for completing overwritten data. The System shall enable users to select to substitute data from previous years as the approach to filling in data overwritten for the current year. When selecting to substitute data from previous years, users shall have the option of selecting the year(s) to choose from. Substituting overwritten data (and the calculations needed) shall be controlled by a set of business rules. Business rules for calculating and substituting overwritten data shall be set by the vendor, based on established calculations and accepted practices of substituting data. The System shall provide a mechanism for authorized users to manually enter data into the HPMS Integration Software. The System shall provide a mechanism for users to manually type data values into the user interface. The System shall provide a mechanism for users to select the location that the data value is associated with. MUI When selecting locations for data entered manually, users shall be able to select an intersection. 10

16 Map to ConOps MUI When selecting locations for data entered manually, users shall be able to select a segment of highway by designating the start / end points. MUI When selecting locations for data entered manually, users shall be able to select a sample segment. MUI When selecting locations for data entered manually, users shall be able to select traffic recording station MUI-11 The System shall provide a mechanism for users to load data previously collected and stored as.csv or.xls files , MUI-11-1 MUI-11-2 MUI-11-3 When loading data stored to.csv or.xls files, the location, data type, and data values will be included in the formatting of the.csv or.xls files. The System requirements for the formatting of.csv or.xls files shall be available to DOT&PF users. The System shall provide feedback to users loading files into the HPMS Integration Software if the data was loaded correctly or if errors were encountered MUI-12 The System shall provide a mechanism for users with edit privileges to select any data element and edit the data value. MUI-12-1 MUI-12-2 When edits to data are performed, the System shall track the user who edited the data, and the date of the edit. There is no requirement for storing the original value(s) of data before editing, or interval data values. Each time a user edits data, the new value shall be stored as the value for the data element. 11

17 Map to ConOps MUI-13 The System shall provide a mechanism for users to request that summary data be generated. Validating data MUI-13-1 MUI-13-2 MUI-14 MUI-14-1 MUI-14-2 The System shall provide a mechanism for users to select the data set to use to create the summary. The system shall provide feedback to users if summary data were generated correctly or if errors were encountered. The System shall provide a mechanism for users to select data to be validated. Users shall have a mechanism to select multiple types of data that are required to perform validation checks. When internal processes perform validation checks, the System user interface shall display the results of the validation to the user. MUI Validation results shall be displayed to include information describing the errors that were encountered, and specifically what data sets the errors were found. MUI Validation results shall be displayed to users and users shall have a mechanism to share validation results with others. MUI-15 MUI-15-1 The System shall provide a mechanism for users to request that Summary data be calculated during the validation process. When internal processes calculate summary data, the results shall be displayed as part of the validation display. 12

18 Map to ConOps MUI-16 MUI-16-1 MUI-17 Generating Reports , MUI-17-1 The System shall generate a table that will serve as the estimates catalog. The System shall provide a mechanism for users to populate the (estimates catalog) table through an operator driven process. The System shall identify when missing data elements are encountered during the validation process, and generate flags to the user when estimates are needed for the data element(s). The System shall provide a mechanism for users to populate missing data elements with estimates, and shall execute the calculations necessary to implement the selected approach. MUI The System shall enable users to select Interpolation as an approach for inserting estimated data where data elements are missing. MUI The System shall enable users to select to substitute data from previous years as an approach for inserting estimated data where data elements are missing. MUI The System shall enable users to manually enter data element values as an approach for inserting estimated data where data elements are missing. MUI-18 The System shall provide a mechanism for users to request reports. 13

19 Map to ConOps MUI-18-1 MUI-18-2 Users shall be able to request any of the reports that are required for the annual HPMS reporting to FHWA. When requested by a user, the System needs to generate the data reports. MUI Users shall be able to save reports in formats compatible with the needs to upload reports to the FHWA HPMS website. MUI The processes for generating HPMS reports shall be controlled by a set of business rules. MUI Business rules for generating HPMS reports shall be set by the vendor, based on FHWA HPMS reporting requirements. MUI Business rules for generating HPMS reports shall be configurable to enable the vendor to edit/adjust the business rules in the future if FHWA HPMS reporting requirements change MUI-18-3 The System shall enable users to specify that partial reports be generated, and users shall not have to have all data in place to generate partial reports. TOPS MUI-19 MUI-19-1 The System shall enable users to request an HPMS Table of Potential Samples (TOPS). When requested, the System shall generate the TOPS Note: the generation of TOPS is covered by requirements in the Internal Processes section. 14

20 Map to ConOps MUI-19-2 MUI-19-3 MUI-19-4 The System user interface shall display the TOPS to users when calculated. The System shall provide a mechanism for users to select one or multiple segments displayed in the TOPS and load current samples into the segment(s). The System shall enable users to adjust the samples by breaking existing samples into multiple samples, or other adjustments. 15

21 Table -3 Requirements Related to Internal Calculations Map to ConOps Data Translation and Format Checks When Pulling Data , , , IC-1 IC-1-1 IC IC IC-2 When pulling data from external systems, the System needs to translate data into the format needed for HPMS reporting. Data translation shall be controlled by a set of business rules. Business rules for data translations shall be set by the vendor, based on FHWA HPMS reporting requirements. Business rules shall be configurable to enable the vendor to edit/adjust the business rules in the future if FHWA HPMS reporting requirements change. The System shall calculate Predominance Values when translating data for items that require reporting by predominance over the length of a section IC-3 The System shall calculate Weighted Averages when translating data for items that require reporting by weighted average over the length of a section IC-4 The System shall determine any coded values that result from the actual data, for items that require reporting by coded value IC-5 Each time the System pulls data from an external system, the System shall perform format checks on the data during the pull process to determine if the data is formatted properly. 16

22 Map to ConOps IC-5-1 IC-5-2 The System shall provide users with access to the results of format checks. If format checks are not successful, the System shall present users with information about the errors encountered during the format check IC-5-3 Format checks performed on the data shall be controlled by a set of business rules. IC IC Validation of Data Business rules for format checks shall be set by the vendor, based on FHWA HPMS reporting requirements. Business rules for format checks shall be configurable to enable the vendor to edit/adjust the business rules in the future if FHWA HPMS reporting requirements change IC-6 The System shall perform validation checks on data when requested by users. IC-6-1 IC-6-2 IC IC Validation tests shall be conducted on a data set, as selected by users from the user interface. Validation tests performed on the data shall be controlled by a set of business rules. Business rules for validation tests shall be set by the vendor, based on FHWA HPMS reporting requirements. Business rules for validation tests shall be configurable to enable the vendor to edit/adjust the business rules in the future if FHWA HPMS reporting requirements change. 17

23 Map to ConOps IC-6-3 The System shall display results of validation tests through the user interface IC Users shall have the option of printing or saving the results of validation tests IC-6-4 The System shall calculate Summary Data during the Validation process to be displayed to the users when requested. IC IC IC IC Summary Data shall be stored in the HPMS Integration Software for display and use in report generation. Summary data calculations shall be controlled by the metadata describing the data and on a set of business rules. Business rules for Summary Data calculations shall be set by the vendor, based on FHWA HPMS reporting requirements. Business rules for Summary Data calculations shall be configurable to enable the vendor to edit/adjust the business rules in the future if FHWA HPMS reporting requirements change IC-7 The System shall identify missing data elements while performing data validation, and flag the missing data elements for users to generate Estimate Values. 18

24 Map to ConOps IC-7-1 IC-7-2 IC-7-3 TOPS Creation and Support The System shall perform calculations to support the selected approach for generating Estimated Values for the missing data elements, as selected by users through the user interface. Options for generating the Estimated Values shall include: - Interpolation; - Using data values from previous years; and - Manual entry of estimated values. Once created, Estimated Values shall be used in calculations and report generation in the same way that actual values are used. Estimated values shall be flagged as estimated value, in order to enable users to view which data elements were estimates at times in the future IC-8 The System shall determine segments that are potential samples by assessing each segment against the five TOPS elements defined by FHWA (AADT, urban code, functional system, facility type, and thru lanes) IC-8-1 When determining TOPS, the System shall process the five elements against all roadways included in the system. IC-8-2 The System shall use the DOT&PF Roadway Data System (RDS) Geodatabase as the centerline road network when assessing the five data elements to determine TOPS samples, as pulled from the RDS. 19

25 Map to ConOps IC-8-3 The System shall provide a mechanism for users to request that segments be broken into smaller segments to provide additional TOPS segments IC-8-4 As TOPS are identified by the System and users select the samples, the System shall populate the tables with values from data stored in the System. 20

26 Table -4 Requirements Related to Hosting & Operations Concepts ID System Requirement Hosting, Operations 8.1 Oper-1 The System shall operate on a DOT&PF operated hosting environment. 8.1 Oper-1-1 The System shall be compatible with all DOT&PF software and database hosting standards and requirements. Offeror s Response to Requirement (e.g. Understand and Agree to Deliver Requirement ; Understand and Suggest an Alternative Requirement ; Cannot deliver Requirement ) 8.3 Oper-2 The System shall provide a mechanism for the vendor to perform needed administrative functions by accessing the system remotely. 21

27 HPMS Integration System AMENDMENT 1 COST PROPOSAL SUMMARY Offeror: Offerors must complete and submit all portions of this Cost Proposal Summary. Offerors must take into consideration the costs necessary to provide the State with successful implementation of the HPMS Integration Software (including software, maintenance, and technical support) for all years of the contract. In addition to completion of the summary, Offerors must also provide a separate itemized list of all costs per task deliverable supporting their Cost Proposal Summary. Failure of the Offeror to submit the Cost Proposal Summary with a separate itemized list of cost by task deliverable may cause the proposal to be considered non-responsive and rejected. SECTION 1 Firm Fixed Pricing for Tasks 1-3: Offerors must provide their Firm Fixed pricing as it relates to providing all services and deliverables to complete each task listed below. Task 1: HPMS Software Delivery, Configuration, Testing and Launch Description HPMS System Install/Implement/Configure and Successful Launch $ Firm Fixed Cost Task 2: Training Description Qty. Unit Unit Cost Total Extended Cost Initial Training Sessions 1 ea. $ $ Follow-up Training Sessions 1 ea. $ $ Training Manual 2 ea. $ $ User Manual 2 ea. $ $ Total Extended Cost: $ 1 P age

28 HPMS Integration System AMENDMENT 1 COST PROPOSAL SUMMARY (Cont.) Task 3: Technical Support and Software Maintenance Offerors must identify annual costs for Support & Maintenance. If License fees are applicable, the Offeror must also identify that cost or otherwise note $0. Contract Year Annual Service Annual Cost Year 1 Support & Maintenance $ License Fee (if applicable) $ Subtotal: $ Year 2 Support & Maintenance $ License Fee (if applicable) $ Subtotal: $ Year 3 Support & Maintenance $ License Fee (if applicable) $ Subtotal: $ Year 4 Support & Maintenance $ License Fee (if applicable) $ Subtotal: $ Year 5 Support & Maintenance $ License Fee (if applicable) $ Subtotal: $ Total Cost (5 years): $ 2 P age

29 HPMS Integration System AMENDMENT 1 COST PROPOSAL SUMMARY (Cont.) SECTION 2 Hourly Rates for Optional Tasks 4-8: The purpose of this cost formula is to provide a mechanism for Offerors to submit fully loaded hourly in a manner that DOT&PF can evaluate and score per Section Each job class, employee assigned and rate identified will establish billing rates for the resultant contract. RFP Section 3.11 allows for change of personnel at the established contract rate. Established hourly rates are only subject to adjustment per the conditions set forth in Section In the chart below, the State identifies the likely job classes used by a Contractor in their performance of Tasks/Deliverables 4-8 described in RFP Section Offerors must identify the employee and the fully hourly rate for each applicable job class. If the Offeror s job classifications differ from those provided, the Offeror must furnish a job description, the title, and hourly billing rate for that likeposition classification. If the Offeror has multiple levels of the job classes provided, the Offeror must submit each job class proposed with a job description, identify each employee, their title, and hourly rate. The total number of estimated hours must equal the State s estimated number of hours for that job class. Job Class Employee Name Est. No. of Hrs. Project Manager or Principal in Charge Senior Programmer Junior Programmer Application Integration Analyst Database Administrator Hourly Rate 300 $ $ 100 $ $ 100 $ $ 100 $ $ 100 $ $ Testing Analyst 100 $ $ Extended Cost (Est. Hrs. x Hourly Rate) Technical Support 100 $ $ 3 P age

30 HPMS Integration System AMENDMENT 1 Job Class Employee Name Est. No. of Hrs. FHWA Reporting Analyst Administrative Support Hourly Rate 50 $ $ 75 $ $ Extended Cost (Est. Hrs. x Hourly Rate) Training Associate 40 $ $ Section 2- Total Extended Cost for Hourly Rates: $ Identifying Other Job Classes If applicable, Offerors must identify any additional job classes and personnel with their fully loaded hourly rate. In order to be included into the resultant contract, these billable rates must be identified below: Job Class Employee Name Fully Loaded Hourly Rate $ $ $ $ $ $ $ $ $ 4 P age

31 HPMS Integration System AMENDMENT 1 COST PROPOSAL SUMMARY (Cont.) TOTAL COST SUMMARY: Description Total Cost by Section SECTION 1: HPMS Primary Tasks 1 thru 3: $ SECTION 2: HPMS Optional Tasks 4 thru 8: $ Total Cost for All Sections: $ (This will be evaluated for cost per Section 6.08) 5 P age