AASHTOWare Project Data Analytics Software€¦ · AASHTOWare Project Data Analytics™ PAGE 2...

AASHTOWare Project

Data Analytics™ Software

Proposal for the Development of

AASHTOWare Project Data Analytics™

Prepared by: AASHTOWare Project™ Task Force

Approved by the AASHTO Special Committee on AASHTOWare®

July 2018

© Copyright 2018 by the American Association of State Highway and Transportation Officials, Inc. All rights reserved. This document or parts thereof may not be reproduced in any form without written permission of the publisher. Printed in the United States of America.


PAGE ii

Table of Contents

EXECUTIVE SUMMARY .......................................................................................................................................... 1

THE NEED FOR AASHTOWARE PROJECT DATA ANALYTICS ............................................................................... 3 AASHTOWARE PROJECT DATA ANALYTICS DESCRIPTION ................................................................................. 3 AASHTOWARE PROJECT DATA ANALYTICS BENEFITS ........................................................................................ 3 THE INVESTMENT ...................................................................................................................................................... 4 SCHEDULE .................................................................................................................................................................. 4 RETURN ON AGENCY INVESTMENT AND KEY DELIVERABLES ............................................................................... 5

AASHTOWARE PROJECT DATA ANALYTICS – PROJECT PROPOSAL ..................................................... 6

BACKGROUND ............................................................................................................................................................ 6 AASHTOWARE PROJECT DATA ANALYTICS OBJECTIVES ................................................................................... 6 INVITATION TO PARTICIPATE ................................................................................................................................. 10 DEVELOPMENT METHODOLOGY ............................................................................................................................ 10 AASHTOWARE PROJECT DATA ANALYTICS DELIVERABLES ............................................................................ 11 AASHTO PROJECT ADMINISTRATION .................................................................................................................. 11 DEVELOPMENT COST .............................................................................................................................................. 12

Consultant Contract .............................................................................................................................................. 12 Administrative Costs ............................................................................................................................................. 12

SUMMARY OF COSTS ................................................................................................................................................. 13 PROJECT FUNDING .................................................................................................................................................. 13

AASHTOWare Project Task Force License Fee Revenue .................................................................................. 13 Participant Funding ............................................................................................................................................. 13 Additional Funding .............................................................................................................................................. 14

QUESTIONS AND INQUIRIES ............................................................................................................................... 14


PAGE 1

Executive Summary

The American Association of State Highway and Transportation Officials (AASHTO) is proposing, on behalf of its member agencies, a project to develop the AASHTOWare Project Data Analytics™ software. The software will be delivered as both web-based and Software-as-a-Service (SaaS) platforms, providing decision support and analysis functionality, including two construction dashboard components. Considering the mission critical nature of the AASHTOWare Project™ software, it is imperative that the product set be kept current with evolving technology and business requirements. This proposed software development effort, set for incremental releases (every two to four weeks) to participating agencies of a supported production environment over a 48-month period, involves developing features that will enable agencies to analyze AASHTOWare Project data to find patterns, draw conclusions, and make better data-driven decisions. AASHTOWare Project Data Analytics will leverage the existing web-based AASHTOWare Project unified database, providing additional value to the collection of the AASHTOWare Project data. This software will provide agencies the ability to perform interactive data analytics using feature sets and dashboards that are tailored specifically to the highway construction field. This software development effort will considerably enhance each functional area and integrate data from all AASHTOWare Project modules for a more streamlined data review with decision-making capabilities. To date, the following work has been accomplished in preparation of the AASHTOWare Project Data Analytics full development project. A pilot project was completed in 2017 to test the SaaS development and deployment of analysis functionality. The pilot validated an approach where the historical repository for all agency data remains with the agency’s web-based AASHTOWare Project installation, and agency users can securely run analysis functions through the SaaS. A Decision Support Summit was held in December 2017. This summit brought subject matter experts from 22 agencies together to discuss data analytics, decision support and the features required in the software. An interim six-month development project, which began in February 2018, will deliver initial core SaaS production functionality for Line Item Profiles and Bid Evaluation Analysis by August 2018. Portions of these modules have been deployed and are used by member agencies. The production delivery of the full AASHTOWare Project Data Analytics software will utilize results from the 2017 SaaS pilot and the Decision Support Summit. The results from the Summit were used to prioritize the functionality that is represented in Appendix A of this work plan. The Summit participants and the AASHTOWare Project Task Force also identified six new analysis features to be included in the software that are also included in Appendix A of this work plan.


PAGE 2

AASHTOWare Project Data Analytics will be integrated with the AASHTOWare Project software and built to maximize the potential of the AASHTOWare Project unified database. The software will aid in breakings down departmental silos by using and analyzing all data from the estimate, letting, bids, construction, materials, civil rights and labor. This will provide more accurate, current results and the ability to respond more quickly and accurately to citizen, legislative, and vendor requests. The software will utilize user-friendly interactive analysis tools, and dashboards, built specifically for agency construction management business needs. Minimal user training will be required, with a low-complexity product and simple navigation. The use of the SaaS platform keeps the product at the latest production version and the technology remains current. Agencies will no longer be required to license the SAS statistical analytical tool in order to do their analysis and queries. With SaaS in a hosted environment, the rapid delivery model will allow new features to go live more quickly without the need for agency deployment and with minimal IT support. We invite you to review the enclosed information, and ask that you respond to this solicitation no later than September 28, 2018.


PAGE 3

The Need for AASHTOWare Project Data Analytics

The AASHTOWare Project Task Force recognizes the need to greatly enhance the AASHTOWare Project software by building upon the architecture and infrastructure now in place, and to provide the ability to analyze the vast array of data within the AASHTOWare Project unified database to easily provide answers to questions. Considering the mission critical nature of the software, it is imperative that the product set provide agencies the ability to easily perform interactive data analytics and decision support queries on their AASHTOWare Project data. This proposed software development effort, set for incremental production environment releases to participating agencies (every two to four weeks) over a 48-month period, with the final features being delivered in October 2022, will considerably enhance each functional area and integrate all modules for a more streamlined data review and decision-making capabilities.

AASHTOWare Project Data Analytics Description

AASHTOWare Project software provides a powerful suite of tools to collect a vast array of valuable data across an agency’s entire construction program, from cost estimates, proposals, contractor bids/analysis, and contracts to daily work reports, contractor payments, change orders, claims, payrolls, material samples and tests, producer/suppliers, and more! With all this valuable data in one place and accessible anytime, anywhere, agencies need user-friendly analysis tools to aid in future planning and to help make better data-driven decisions. The AASHTOWare Project Data Analytics software will provide a revolutionary tool for agencies to analyze their AASHTOWare Project data - finding patterns and drawing conclusions. All of this will be presented in a user-friendly, easy-to-understand format. A primary objective for this work plan is to provide participating agencies with key production ready functionality as soon as possible without having to wait until the end of project delivery. SaaS AASHTOWare Project Data Analytics functionality will be available to participating agencies for production use on a continuous basis, with new features added every two to four weeks, throughout the project as approved by the AASHTOWare Project Task Force.

AASHTOWare Project Data Analytics Benefits

The development of AASHTOWare Project Data Analytics will result in major benefits to the entire community of users.

Major Benefits of AASHTOWare Project Data Analytics: • Allows an agency to adjust Key Performance Indicators (KPIs) based on historical analysis • The ability to quickly analyze bid irregularities, identifying vendor bidding patterns, market

shares and market areas to potentially reduce overall costs of construction contracts in subject areas

• Map areas with key information such as dollars awarded, vendor activity, and price changes over time to help monitor and control costs

• Dashboard display of construction portfolios, allowing key information to be provided earlier in the project which helps ensure cost efficient results


PAGE 4

• Integrated with the AASHTOWare Project software and built to maximize the potential of the AASHTOWare Project unified database

• Breaks down departmental silos by using and analyzing all data from the estimate, letting, bids, construction, materials, civil rights and labor

• Accessible from anywhere, mobile-friendly • Interactive analysis tools, including construction dashboards, built specifically for agency

construction management business needs • Ability to respond more quickly and accurately to citizen, legislative, and vendor requests

with user-friendly tools accessing current data • Improved future planning based on current, broader sets of information that are more

accurate • Use of industry-standard third-party tools for additional analysis, visualization, and

reporting • Minimal user training, with a low-complexity product and simple navigation • A SaaS platform that keeps the product at the latest production version and the technology

current • Licensing of the SAS statistical analytical tool is no longer required • A rapid delivery model allowing new features to go live quicker • No agency deployment needed as the SaaS is in a hosted environment

The Investment

AASHTO is seeking 12 AASHTO member agencies to make a commitment of $750,000 each to provide the necessary funding for the development of the AASHTOWare Project Data Analytics software. This commitment may be divided into as many as four fiscal year installments. Agencies may allocate funding between fiscal years 2019, 2020, 2021 and 2022. Agencies wishing to propose a different funding breakdown should contact the AASHTO Project Manager, Brian Korschgen, at [email protected] or 202-624-8566. In addition, agencies may elect to use newly purchased or existing AASHTOWare Project Service Units to fund participation in this project. AASHTO has coordinated with the Federal Highway Administration to allow project participants to use 100% of State Planning and Research (SP&R) funds for participating in this project. A copy of the letter authorizing the use of these funds including a waiver of the non-Federal funding match requirement is included in this proposal.

Schedule

The development of the AASHTOWare Project Data Analytics software will be a multi-year effort with a 48-month software development and testing cycle. Production ready software will be delivered incrementally to participating agencies (new features every two to four weeks) with the completion and delivery of the final release expected by September 2022.

mailto:[email protected]


PAGE 5

Return on Agency Investment and Key Deliverables

The objective of the AASHTOWare Cooperative Software Development Program is to provide a cost-efficient means for member agencies to voluntarily pool their resources to produce mutually acceptable computer software products. By working with participants to share the total cost of development, the AASHTOWare Cooperative Software Development Program provides member agencies the opportunity to realize significant financial benefits through the delivery of quality software specifically designed and continually updated by experts from state transportation agencies across the nation. Some of the benefits include:

• Development of a complex and innovative software application that would be uneconomical on an individual member agency basis

• Nomination of subject matter experts by funding agencies to serve on the Technical Review Teams so agency needs/practices are voiced and considered throughout the development cycle including future enhancement releases

• Efficient use of agency resources through the promotion of best practices identified by the pooling of knowledge across member agencies

• Delivery of production ready state-of-the-art software capable of meeting evolving technology

• Delivery of software that can be maintained, supported, and enhanced over its lifecycle through the established method of pooling of agency resources lowering total ownership costs requirements.

Agencies participating in the project will be provided the following:

• Access to an AASHTOWare Project Data Analytics agency specific evaluation site • A seat on the AASHTOWare Project Data Analytics Technical Review Team (TRT) • Access to all development related materials as approved by the AASHTOWare Project Data

Analytics Technical Review Team and the AASHTOWare Project Task Force • AASHTOWare Project Data Analytics manuals, including the System, Installation and Users

manuals • Production ready software delivered incrementally every two to four weeks over the 48-

month development period • The first twelve (12) agencies providing target level funding ($750,000) will receive a 25%

reduction in license fee for the AASHTOWare Project Data Analytics software for a period of 3 years after the conclusion of the project


PAGE 6

AASHTOWare Project Data Analytics – Project Proposal

Background

The September 2017 release of the AASHTOWare Project 4.0 software provided AASHTO member agencies with the latest functionality to support daily construction management activities (e.g., estimation, preconstruction, civil rights, labor, construction, and materials). The software represents the effort by AASHTO and its member agencies to migrate client/server AASHTOWare Project module functionality to the web-based platform and supplement it with new features and functionality. Now that the four web-based AASHTOWare Project modules (AASHTOWare Project Preconstruction, AASHTOWare Project Civil Rights & Labor, AASHTOWare Project Construction & Materials, and AASHTOWare Project Estimation) are part of the unified database it is time to introduce software that will take full advantage of this combined and easily accessible data. The final step in this evolution is the migration of the decision support and analysis functionality features currently found in AASHTOWare Project BAMS/DSS™. AASHTOWare Project Data Analytics will provide the opportunity to focus on increasing the functionality and efficient data reporting across all the software modules. The AASHTOWare Project Data Analytics software will be developed in a way that maximizes the advantage of the existing web-based platform and for the first time enable delivery functionality in a SaaS platform, providing participating agencies with key production ready functionality every two to four weeks throughout the life of the project. A Technical Review Team will be appointed to work together with the software development contractor to refine the new and existing requirements and test the software as it is developed. The AASHTOWare Project Data Analytics software is proposed to enhance and further unite the current modules on the existing web-based AASHTOWare Project infrastructure using its unified code base and database structure. The major benefits of cooperative software development afford each agency that participates in the project the opportunity to guide and provide input on the functionality and capability of the application.

AASHTOWare Project Data Analytics Objectives

The scope of the AASHTOWare Project Data Analytics development effort has been defined by the following high-level goals:

1. Deliver identified web-based features functionality 2. Deliver identified SaaS features functionality 3. Deliver two construction dashboards 4. Deliver applicable product documentation 5. Additional enhancements as approved by the AASHTOWare Project Task Force

The guiding principle that will drive all decisions in pursuit of these goals is to provide high-quality functioning software that delivers the maximum product value for the budget and time


PAGE 7

allocated. The ultimate scope addressed in this effort has been determined collaboratively and iteratively based on the work of the AASHTOWare Project Task Force, the Decision Support Summit members and the contractor, Info Tech, Inc. The proposed themes are listed below in alphabetical order. See Appendix A for the initial theme priorities. Theme: Bid/Estimate Review The Bid/Estimate Review analysis provides a method to compare item prices on a contract or set of contracts to historical, regression generated item average prices and standard deviations.

Theme: Bid Evaluation Analysis The Bid Evaluation Analysis model identifies contracts and items that require further review due to excessive deviation of item bid prices from the engineer's estimate. The deviation of the low/winning bidder's item bids from the engineer's estimates are compared to historically observed bid deviations for each item. Those items with deviations that are large in light of historical data are identified and displayed. Theme: Bridge Costs The Bridge Costs analysis produces reports useful for comparing bridge costs. Theme: Contract Profile The Contract Analysis models provide summary information, called contract profiles, about contracts. Contract profiles list general information about the contract, including its contract, project, and federal identification numbers, the vendors who bid on the contract, vendors who purchased plans for the contract, location of the contract, important dates associated with the contract, and vendors who received subcontracts. Theme: Historical Statistics The Historical Statistics models produce graphic and tabular displays that provide summary information about volume of work, location of work, and vendor activity over a specified period. This analysis report can be produced with or without the Engineer's Estimate information. Theme: Item Price Analysis The Item Price Analysis model provides summary statistics for historical item bid prices. Theme: Item Rank Analysis The Item Rank Analysis model identifies the items that have the greatest dollar impact on the total awarded contract dollars in a specified period and market. Theme: Item Statistics Map The Item Statistics Maps model provides a method to evaluate and compare item usage in different geographic areas.


PAGE 8

Theme: Line Item Profiles The Line Item Profile analysis identifies the bid items most responsible for vendors' bidding deviations on a specified contract. The identified bid items can then be studied to determine the cause(s) of the deviations (for example, unbalanced bidding, front-end loading, complementary bidding, or an inaccurate estimate). Since these key items usually determine the outcome (that is, the winner) of the contract, Line Item Profiles highlight the key items on each contract. Theme: Quantity Variance - Letting The Quantity Variance - Letting compares the results of the bidder’s rank when using an alternate value for the quantity of an item based on actual item bid vs as built quantity differences. Theme: Award Maps The Award Map analysis allows the analyst to produce maps defined by either the number of awarded contracts, the number of awarded projects, or the amount of awarded dollars. Theme: Cost Variance Profiles The Cost Variance Profile models compare the actual item costs and the Engineer's Estimate item costs to the amount originally bid by the vendor. These models are meant to be used on selected completed (or nearly completed) contracts to evaluate how well actual costs tracked the original estimated costs. Theme: Market Area Definition The automatic market area definition analysis provides the analyst with a phased method of grouping counties into meaningful analysis markets based on shared vendor activity. Theme: Market Shares The Market Shares models calculate the percentage of the business in a market that is controlled by each vendor. These reports are useful for determining the number of active vendors and measuring the level of competition in the market. There are three different models

- Market Shares Dollars (uses the contract dollars and subcontract dollars if selected), Market Shares items (using item dollars), and Market Shares Quantity (using item quantity).

Theme: Quantity Variance The Quantity Variance Profile models compare the actual item quantities to the original quantities (estimated quantities) bid by the vendors. This model is meant to be used on selected completed (or nearly completed) contracts to evaluate how well actual quantities tracked the original estimated quantities.


PAGE 9

Theme: Vendor Activity Map The Vendor Activity Map model provides the analyst with a method to graphically display the bidding, winning, and subcontract activity of a single selected vendor. If desired, the vendor's facilities (plants) may also be mapped. Theme: Vendor Competition Analysis The Vendor Competition analysis is useful for investigating the bidding relationships between two or more vendors. The bidding behaviors of the vendors are summarized, to assist in determining whether each vendor's wins versus losses ratio appears reasonable in head to head competition with specific opponents. Theme: Vendor Grouping The Vendor Grouping model provides the analyst with a method to evaluate the activity of affiliated vendors as though they were one vendor. Affiliated vendors are vendors with common ownership, common officers, or other aspects that might prevent them from being true competitors. Theme: Vendor Profile The Vendor Profile model provides the analyst with summary information on selected vendors' bidding, award, and subcontract activities during a specified time. Activities are summarized for contracts that were both let and awarded during the specified time. This model also summarizes the vendor's facility (plant) information during the specified time, if the information is contained in the analysis data. Theme: Work Location Map The Work Location Map model provides a graphical display of the work locations and facilities (plants) of contract winners for specified periods, specified geographic areas, and specific vendors. This model is useful for comparing the location of awarded contracts to the locations of particular vendor's plants. The model is intended to work only with awarded contracts. Additional Themes: Requirements for six new themes are planned as part of this project:

- Compare Contracts - Compare Prices of Similar Items Within Letting and Recent History - Trends of Unbalanced Items - Unbalanced Bidding Analysis - Construction Time Dashboard - Construction Budget Dashboard

Upon approval of the new themes by the Project Task Force, Info Tech will prepare a change order outlining any resided estimate and/or scheduled modification.


PAGE 10

Invitation to Participate

AASHTO invites your agency to join with other member agencies to develop the AASHTOWare Project Data Analytics software. Participation in the Joint Software Development Program requires submission of the enclosed commitment form. The email response with the completed Commitment Form is an indication of intent to provide the requested funding. As with all AASHTOWare efforts, participation is voluntary. We invite you to review the enclosed information and ask that you respond to this solicitation no later than September 28, 2018.

If you have any questions, please feel free to contact Brian Korschgen, AASHTO Project Manager, at [email protected] or 202-624-8566.

Development Methodology

The scope items for AASHTOWare Project Data Analytics, defined in Appendix A of the attached work plan, are in various stages of the requirements gathering phase. The majority of the requirements have been approved for inclusion in the software by the AASHTOWare Project Task Force. There are six features, analysis and dashboards, that will be fleshed out through requirements gathering as part of this project. The AASHTOWare Project Data Analytics development contractor, Info Tech Inc., will work with the Technical Review Team and the Task Force to complete the requirements gathering phase creating user stories for these features. These user stories will capture the expectations of the user in common business language without regard to the technical aspects of the system. Members of the Technical Review Team will then review and approve the user stories. The guiding principle that will drive all decisions in pursuit of the final project deliverables is to provide high-quality functioning software that delivers the maximum product value for the budget and time allocated. The ultimate scope addressed in this effort has been and will continue to be determined collaboratively and iteratively through the discovery process along with these goals and guiding principles. The attached work plan addresses the methodology and approach that the software development contractor, Info Tech, Inc., will employ to develop the AASHTOWare Project Data Analytics software. A high level of user collaboration with the Technical Review Team, coupled with pervasive manual and automated testing, will mitigate stakeholder risks throughout the development lifecycle while ensuring high quality AASHTO standard deliverables. The overall AASHTOWare Project Data Analytics team will consist of the AASHTO Project Manager, the AASHTOWare Project Data Analytics Technical Review Team, chaired by an AASHTOWare Project Task Force member, and the Info Tech Development Team. The team will review the results of each major deliverable, project test plan and materials, etc.



PAGE 11

Development of the AASHTOWare Project Data Analytics software, as with all AASHTOWare offerings, will be guided by and adhere to the AASHTOWare® Standards and Guidelines Notebook. The current version of the notebook can be found at: https://www.aashtoware.org/about/standards-and-guidelines/. All deliverables and artifacts developed in relation to this project will conform to the guidelines set out in the AASHTOWare® Standards and Guidelines Notebook. AASHTOWare Project Data Analytics Deliverables

Participation in AASHTO’s Joint Software Development Program provides significant financial benefits as well as high quality software designed by users for users. The AASHTOWare Project Data Analytics software will significantly improve the efficiency and effectiveness of current operations at a fraction of the cost of development by each agency. Agencies participating in the project will be provided the following:

• Access to an AASHTOWare Project Data Analytics agency specific evaluation site • A seat on the AASHTOWare Project Data Analytics Technical Review Team (TRT) • Access to all development related materials as approved by the AASHTOWare Project Data

Analytics Technical Review Team and the AASHTOWare Project Task Force • AASHTOWare Project Data Analytics manuals, including the System, Installation and Users

manuals • Production ready software delivered incrementally every two to four weeks over the 48-

month development period • The first twelve (12) agencies providing target level funding ($750,000) will receive a 25%

reduction in license fee for the AASHTOWare Project Data Analytics software for a period of 3 years after the conclusion of the project

AASHTO Project Administration

AASHTO will administer the AASHTOWare Project Data Analytics software development contract under the AASHTOWare Cooperative Software Development Program. Technical management will be performed by the AASHTOWare Project Data Analytics Technical Review Team appointed by the AASHTOWare Project Task Force which in turn reports to the AASHTO Special Committee on AASHTOWare (SCOA). Participating agencies will be able to nominate candidates to serve on the AASHTOWare Project Data Analytics Technical Review Team. The Technical Review Teams will guide the development project through their review and recommendation of approval of project deliverables to the AASHTOWare Project Task Force.

https://www.aashtoware.org/about/standards-and-guidelines/


PAGE 12

The project organization is depicted in the following chart:

AASHTOWare Project Data Analytics Organizational Chart

Development Cost

Total cost of the AASHTOWare Project Data Analytics Project is estimated at $10,929,825 over a 48-month period. The general breakdown of the project budget is as follows: Consultant Contract

If the project solicitation is successful and sufficient commitments for funding are received, the proposed total contract amount is $9,852,825. Administrative Costs

Administrative costs, estimated at $1,077,000 are composed of the following: Project Related Travel

Technical Review Team Member, AASHTO Staff and Special Committee on AASHTOWare travel is projected at $77,000 for the AASHTOWare Project Data Analytics Technical Review Team including onsite testing during development. Travel costs will be reimbursed by AASHTO according to governing policy. AASHTO Program Development Pool

Contribution into the AASHTOWare Program Development Pool is estimated at $250,000. The policy governing all AASHTOWare activities, as described in the AASHTOWare Cooperative Software Policies, Guidelines and Procedures document requires that 5% of all new revenue be set aside in a capitalization fund. This fund is held in reserve by AASHTO and is not used in the development activities.

AASHTO Board of Directors and Executive Committee

AASHTO Special Committee on AASHTOWare (SCOA)

AASHTOWare Project Task Force (9 Member Agency Representatives)

AASHTO Project Manager

AASHTOWare Project Data Analytics Technical Review Team

Technical and Application Architecture Task Force

(T&AA)

Info Tech, Inc. Contractor


PAGE 13

Contingency Fund

Due to the size of this development effort, a contingency fund of $750,000 has been added to the projected costs. The purpose of this fund is to cover unforeseen expenses such as additional functionality deemed necessary to meet member agency needs by the AASHTOWare Project Data Analytics Technical Review Team during the development process. If these funds are not utilized in the development of the first production release of AASHTOWare Project Data Analytics, then they will be applied as functional enhancements in the next production release of the software.

Summary of Costs

AASHTOWare Project Data Analytics Project Costs

AASHTO Program Development Pool ................................................ $250,000 Project Related Travel ........................................................................... $77,000 Contractor ........................................................................................ $9,852,825 Contingency Fund ............................................................................... $750,000 Total Estimated Cost to Participants - ....................................... $10,929,825

Project Funding

The following two sources of funding are proposed for the development of the AASHTOWare Project Data Analytics software.

AASHTOWare Project Task Force License Fee Revenue

Over the length of the 48-month development project, the AASHTOWare Project Task Force is proposing to commit $2,000,000 in current license fee revenue to support the AASHTOWare Project Data Analytics software development effort. Participant Funding

To allow the AASHTOWare Project Data Analytics project to proceed, a total of twelve (12) member agency participants, each contributing $750,000 for a combined funding total of $9,000,000 are being sought through this solicitation process. The Federal Highway Administration has approved project participants to use 100% of State Planning and Research (SP&R) funds for participating in this project. If more than 12 agencies agree to participate at the target funding level, project participants will have the option of reducing the participant funding commitment required, or choose to accomplish additional work that may be desired beyond the currently envisioned scope. If less than the required amount is committed, the


PAGE 14

AASHTOWare Project Task Force will work with the funding agencies to adjust the project scope and/or schedule, if needed. Note: Agencies may utilize AASHTOWare Project Service Units to fund this project. This includes both service units previously purchased by an agency or newly purchased service units.

Additional Funding

Info Tech, Inc. is contributing resources, up to $1,000,000, to the project, to provide additional value to the work plan. This contribution will allow for the inclusion of the two construction dashboards into the software without increasing the cost of the overall project.

Questions and Inquiries

Any questions about this project solicitation, the proposed system, or the AASHTOWare Cooperative Software Development Program should be directed to Brian Korschgen, Project Manager. Phone: (202) 624-8566, email: [email protected]


Commitment Form

AASHTOWare Project Data Analytics ™ Cooperative Software Development Project As described in the letter from AASHTO, dated July 9, 2018, and the associated project proposal to develop the AASHTOWare Project Data Analytics software: [ ] We agree to participate in this project, and hereby commit to fund the project, as follows:

[ ] Target funding level $750,000 Funding Allocation*: FY 2019: $__________________ FY 2020: $__________________ FY 2021: $__________________ FY 2022: $__________________ [ ] Other Commitment Amount $___________________

*Funding Allocations may be split between FY 2019, FY2020, FY2021 and FY 2022. [ ] We do not wish to participate in the proposed AASHTOWare Project Data Analytics project. Authorized by: (Requires signature by an individual authorized to commit required funding level). Signature: __________________________________________________________________

Name/Title: _________________________________________________________________

Agency: ____________________________________________________________________

Address: ___________________________________________________________________

___________________________________________________________________

Telephone: __________________________ FAX: ________________________________

Email: _____________________________________________________________________ NOTE: If you have elected to participate, please provide the name of the primary agency contact for this

project in the space provided below, (PLEASE PRINT OR TYPE) Please submit nomination letter(s) and resumes for candidates to serve on the AASHTOWare Project Data Analytics Technical Review Team as separate attachments.

Name/Title: __________________________________________________________________

Address: ____________________________________________________________________

Telephone: __________________________ FAX: _________________________________

Email: ______________________________________________________________________ Please return as soon as possible, but not later than September 28, 2018 to: AASHTO Attn.: Brian Korschgen, Project Manager, 444 N. Capitol St., NW, Suite 249, Washington, DC 20001 Email: [email protected], Phone: 202-624-8566


m% DEPARTMENT OFTRANSPORTATION

May 11,2018

Dear AASHTO Member Agencies:

Subject: AASHTOWare Project Data Analytics Software Solicitation

AAS 1-ITO Ware Project Data Analytics software is a continuation of the cooperative development ofAASHTOWare Project. This software will become part of the unified database of AASHTOWare Project,eliminating interfaces and module based systems. In order to fully fund the development of this software,AASHTO is issuing a project solicitation.

AASHTOWare has been an integral part of the Minnesota Department of Transportation (MNDOT) process formany years and allows the opportunity to collaborate with other state transportation agencies to collectivelycombine their strengths and best business practices to create a viable software product of superior quality, farmore powerful and effective than an individual agency could develop and deliver on their own.

The Minnesota Department of Transportation (MNDOT) is very committed to AASHTOWare and fillysupports the development and positive impact this software and web-based technology will bring to our agency.Web-based systems offer numerous, widely recognized, business and technical advantages that can dramaticallylower costs due to reduced support and maintenance, lower requirements on the end user system and simplifiedarchitecture.

MNDOT is very excited about the ability to perform interactive data analytics using feature sets and dashboards thatare tailored specifically to the highway construction field. In addition, MNDOT participated in a data Summitsurrounding the AASHTOWare Project Data Analytics software development effort. MNDOT was made aware thatthe AASHTOWare Project Data Analytics software will considerably enhance each functional area and integrate datafrom all AASHTOWare Project modules for a more streamlined data review with decision-making capabilities. Thesoftware will be delivered as both web-based and Software-as-a-Service (SaaS) platforms.

We ask that all member agencies strongly consider financial support to the AASHTOWare Project DataAnalytics software solicitation. The software resulting from your investment will allow all of us to put more ofour transportation dollars into preserving our roads and less into administrative overhead, which is atremendous benefit to member agencies and gives taxpayers more value for their money.

Todd R. BerglandApplication Portfolio Manager MN.IT@DOT395 John Ireland Blvd.St. Paul, MN. 55311

Sincerely,

Nancy Sannes, P.E.State Estimates Engineer MNDOT395 John Ireland Blvd.St. Paul, MN. 55311

Data Analytics Endorsement

The Ohio Department of Transportation is enthusiastically awaiting the AASHTOWare Project Data Analytics

Project coming this spring. Our Bid Analysis and Review Team has been in place and active for more than 15

years utilizing the BAMS/DSS software for market analyses and the AASHTOWare data for providing useful

information to the Department.

All agencies are recognizing the needs and benefits of accessing projects and program data. The approach

being taken to bring the AASHTOWare Project market analysis models up-to-date and to incorporate data

analytic capabilities from its rich unified database makes perfect sense, especially when we recognize this joint

development effort will bring forward the best ideas from all the project participants.

Ohio has been very successful utilizing the BAMS/DSS software in a settlement for alleged price fixing in a

roadway salt case, creating quarterly highway construction indices and semi-annual construction cost

forecasts, analysis of bid prices to award contracts, and analyzing the relationships between as-bid and as-built

prices, just to name a few. We see the value of examining how our project data is inter-related and what we

can extract from it to better perform our work.

We are looking forward to working with other project participants in this solicitation to bring the new Data

Analytics Project to a reality.

-Jeff Hisem

Administrator, Office of Estimating

Division of Construction

Ohio Department of Transportation

http://www.rightsignature.com/documents/XPR56WIBY5MWRP867B3PTM

XPR56WIBY5MWRP867B3PTM

Jeff HisemParty ID: LW6FSEIU4IZ25BFSTHMETMIP Address: 73.87.188.223

VERIFIED EMAIL: [email protected]

Multi-FactorDigital Fingerprint Checksum 16a68c8038ad6c2d4a64219a86e94e610bfea037

Timestamp Audit2018-05-16 10:19:42 -0700 All parties have signed document. Signed copies sent to: Jeff Hisem and

Lindsey M Pflum.

2018-05-16 10:19:40 -0700 Document signed by Jeff Hisem ([email protected]) with drawn signature.

- 73.87.188.223

2018-05-16 10:19:38 -0700 Jeff Hisem ([email protected]) has viewed Consumer Disclosure and

affirmatively consented. - 73.87.188.223

2018-05-16 10:18:10 -0700 Document viewed by Jeff Hisem ([email protected]). - 73.87.188.223

2018-05-16 10:17:41 -0700 Document created by Lindsey M Pflum ([email protected]). -

156.63.133.8

Page 1 of 1

Prepared by

AASHTOWare Project Data Analytics™ Development and Production Releases Work Plan

April 19, 2018 Document Version 3.0

AASHTOWare is a registered trademark and service mark of AASHTO.

The AASHTOWare logo, Trns•port Estimator, the Trns•port Estimator logo, Trns•port Expedite, the Trns•port

Expedite logo, AASHTO Trns•port, the AASHTO Trns•port logo, CES, the Trns•port CES logo, CAS, the Trns•port

CAS logo, PES, the Trns•port PES logo, LAS, the Trns•port LAS logo, BAMS/DSS, the Trns•port BAMS/DSS

logo, Trns•port SiteManager, the Trns•port SiteManager logo, SiteManager, Trns•port SiteXchange, the Trns•port

SiteXchange logo, Trns•port FieldManager, the Trns•port FieldManager logo, Trns•port FieldBook, the Trns•port

FieldBook logo, Trns•port FieldBuilder, the Trns•port FieldBuilder logo, Trns•port Preconstruction, the Trns•port

Preconstruction logo, Trns•port CRLMS, the Trns•port CRLMS logo, AASHTOWare Project logo and

AASHTOWare Project BAMS/DSS logo are registered trademarks of AASHTO.

AASHTOWare Project Bids, AASHTOWare Project Bids logo, AASHTOWare Project Civil Rights & Labor,

AASHTOWare Project Civil Rights & Labor logo, AASHTOWare Project Construction Administration,

AASHTOWare Project Construction Administration logo, AASHTOWare Project Construction & Materials,

AASHTOWare Project Construction & Materials logo, AASHTOWare Project Data Analytics, AASHTOWare

Project Data Analytics logo, AASHTOWare Project Decision Support, AASHTOWare Project Decision Support

logo, AASHTOWare Project Payroll XML Resource Kit, AASHTOWare Project Payroll Spreadsheet and

Conversion Utility, AASHTOWare Project Estimation, AASHTOWare Project Estimation logo, AASHTOWare

Project Estimator, AASHTOWare Project Estimator logo, AASHTOWare Project Expedite, AASHTOWare Project

Expedite logo, AASHTOWare Project FieldBook, AASHTOWare Project FieldBook logo, AASHTOWare Project

FieldBuilder, AASHTOWare Project FieldBuilder logo, AASHTOWare Project FieldManager, AASHTOWare

Project FieldManager logo, AASHTOWare Project FieldNet, AASHTOWare Project FieldNet logo, AASHTOWare

Project, AASHTOWare Project logo, AASHTOWare Project Preconstruction, AASHTOWare Project

Preconstruction logo, AASHTOWare Project Worksheet, AASHTOWare Project Worksheet logo, AASHTOWare

Project SiteManager, AASHTOWare Project SiteManager logo, AASHTOWare Project SiteXchange,

AASHTOWare Project SiteXchange logo, AASHTOWare Project TRACER, and AASHTOWare Project TRACER

logo are trademarks of AASHTO.

AASHTO Trns•port, Trns•port CES, Trns•port PES, Trns•port Expedite, Trns•port LAS, Trns•port CAS, Trns•port

SiteManager, Trns•port BAMS/DSS, Trns•port SiteXchange, Trns•port Preconstruction, Trns•port CRLMS,

AASHTOWare Project BAMS/DSS, AASHTOWare, AASHTOWare Project Bids, AASHTOWare Project Civil

Rights & Labor, AASHTOWare Project Construction Administration, AASHTOWare Project Construction &

Materials, AASHTOWare Project Cost Estimation, AASHTOWare Project Data Analytics, AASHTOWare Project

Data Analytics logo, AASHTOWare Project Decision Support, AASHTOWare Project Estimation, AASHTOWare

Project Expedite, AASHTOWare Project Preconstruction, AASHTOWare Project, AASHTOWare Project

SiteManager, AASHTOWare Project Worksheet, AASHTOWare Project Payroll Spreadsheet & Conversion Utility,

AASHTOWare Project Payroll XML Resource Kit, and AASHTOWare Project SiteXchange are proprietary

software products of AASHTO.

FieldManager represents a registered trademark and proprietary product jointly owned by Info Tech, Inc., and the

State of Michigan.

FieldBook and FieldBuilder represent trademarks and proprietary products jointly owned by Info Tech, Inc., and the

State of Michigan.

Estimator, FieldNet, Field Interviewer, and SYNC are trademarks and proprietary products of Info Tech, Inc.

Mobile Inspector is a registered trademark and a proprietary product of Info Tech, Inc.

Other product names are trademarks or registered trademarks of their respective owners.

© Copyright 2018 by the American Association of State Highway and Transportation Officials, Inc. All rights

reserved. This document or parts thereof may not be reproduced in any form without written permission of the

publisher. Printed in the United States of America.

iii

Contents

1. Project Overview ....................................................................................................... 1-1

1.1 Purpose ............................................................................................................. 1-1

1.1.1 Background ........................................................................................... 1-1 1.2 Goals and Objectives ........................................................................................ 1-3 1.3 Scope ................................................................................................................ 1-4

1.4 Assumptions ..................................................................................................... 1-6 1.5 Constraints ........................................................................................................ 1-7

2. User Requirements and Specifications.................................................................... 2-1

3. Work Activities.......................................................................................................... 3-1

3.1 Project Management/Support Activities ........................................................... 3-2 3.1.1 Management and Administration .......................................................... 3-2

3.1.2 Project Startup/Mobilization ................................................................. 3-2 3.1.3 TRT and Agency On-sites ..................................................................... 3-2 3.1.4 TRT Review Meetings .......................................................................... 3-2

3.2 Requirements, Analysis, and Design ................................................................ 3-3

3.3 Construction ..................................................................................................... 3-3 3.4 Testing .............................................................................................................. 3-3

3.4.1 Accessibility Testing ............................................................................. 3-4 3.5 Product Delivery and Project Closeout ............................................................ 3-4 3.6 SaaS Operation, Maintenance, and Support Services ..................................... 3-4

3.7 Warranty (SaaS) .............................................................................................. 3-4

4. Schedule, Milestones, and Price ............................................................................... 4-1

4.1 High-Level Schedule ........................................................................................ 4-1 4.2 Milestones, Review Gates, and Deliverables ................................................... 4-2

4.2.1 SaaS-Specific Invoicing ........................................................................ 4-3 4.3 Price .................................................................................................................. 4-3

4.3.1 Total Price ............................................................................................. 4-3

iv

4.3.2 Price Breakdown ................................................................................... 4-5 4.4 Estimation Methods and Estimates .................................................................. 4-6

4.4.1 Estimation Methods .............................................................................. 4-6 4.4.2 Estimates ............................................................................................... 4-6

5. Organization and Staffing ........................................................................................ 5-1

5.1 Organizational Structure ................................................................................... 5-1 5.2 Roles and Responsibilities ................................................................................ 5-2

5.3 Contractor Staffing ........................................................................................... 5-4

6. Technical Process and Technologies ....................................................................... 6-1

6.1 Methods and Standards ..................................................................................... 6-1 6.1.1 URS/SRS/FDS and RTM Creation ....................................................... 6-1 6.1.2 Project Documentation .......................................................................... 6-2

6.1.3 AASHTOWare Project Product Documentation (Web-based AASHTOWare

Project) ................................................................................................ 6-3

6.1.4 AASHTOWare Project Product Documentation (SaaS AASHTOWare

Project) ................................................................................................ 6-4

6.2 Project Lifecycle ............................................................................................... 6-4 6.2.1 Web-Based AASHTOWare Project Software ...................................... 6-4 6.2.2 SaaS AASHTOWare Project Software ................................................. 6-5

6.3 Tools and Technologies .................................................................................... 6-5 6.4 Exceptions to AASHTOWare Standards .......................................................... 6-5

7. Monitoring and Control ........................................................................................... 7-1

7.1 Issue Management ............................................................................................ 7-1

7.2 Change Management ........................................................................................ 7-1 7.2.1 Examples of Change ............................................................................. 7-2

7.2.2 Change Control Process ........................................................................ 7-2 7.3 Status Reporting ................................................................................................ 7-3

8. Quality Management ................................................................................................ 8-1

8.1 Quality Assurance ............................................................................................ 8-1 8.2 Quality Control ................................................................................................. 8-1

8.2.1 Review Gate Approval Procedure ......................................................... 8-1

8.2.2 Major Deliverable Approval Procedure ................................................ 8-1 8.2.3 Reviews and Assessments ..................................................................... 8-2

8.3 Test Plan ........................................................................................................... 8-2

9. Communication Management.................................................................................. 9-1

10. Configuration Management and Repository ...................................................... 10-1

10.1 Configuration Management .......................................................................... 10-1 10.2 Repository ..................................................................................................... 10-1

11. Risk Management ................................................................................................. 11-1

12. Backup and Disaster Recovery ............................................................................ 12-1

12.1 Backup Plan .................................................................................................. 12-1

12.2 Disaster Recovery Plan ................................................................................. 12-1

v

13. Revision History .................................................................................................... 13-1

Appendix A. AASHTOWare Project Data Analytics Development and Production

Releases Work Plan Scope ................................................................................... A-1

Appendix B. Contractor Personnel .............................................................................B-1

B.1 Info Tech Key Personnel Biographies .............................................................B-1 Haval Aloussi: Technical Lead/Developer .....................................................B-1

Ian Baldwin: Business Manager......................................................................B-1 Kateryna Bondareva: Test Coordinator ..........................................................B-2 Dan Hay: Technical Lead/Developer ..............................................................B-2 Randy Lawton: Business Manager..................................................................B-2 Elizabeth Rodgers: Project Manager ...............................................................B-3

B.2 Info Tech Supporting Personnel Biographies ..................................................B-4 Jim McClave: Co-CEO ...................................................................................B-4

Tom Rothrock: Co-CEO .................................................................................B-4 Russell W. Barron: Director ............................................................................B-5

Jeff Lee Derrer: Subject Matter Expert ...........................................................B-5 Jim Ferguson: Director ....................................................................................B-6 Paul Guidry, Jr.: Director/Scrum Master ........................................................B-7

Roy Johnstone: Subject Matter Expert ............................................................B-7 Lora Labonte: Test Coordinator ......................................................................B-8

April Cantrell: Subject Matter Expert .............................................................B-8

vi

This page intentionally left blank.

AASHTOWare Project Data Analytics Development and Production Releases Work Plan 1-1

1. Project Overview

1.1 Purpose

This work plan describes the development and production release activities planned by Info

Tech, Inc. (Info Tech) to provide the AASHTOWare Project Data Analytics (formerly

AASHTOWare Project Decision Support) software. This includes software delivered for both

the web-based and Software-as-a-Service (SaaS) platforms for the AASHTOWare Project

software. A primary objective for this work plan is to provide agencies with key production-

ready functionality as soon as possible without having to wait until the end of the project. SaaS

AASHTOWare Project Data Analytics functionality will be available to licensing agencies for

production use on a continuous basis throughout the project (e.g., bi-weekly or monthly) as

approved by the AASHTOWare Project Task Force (PTF). Refer to Appendix A for a

prioritized list of the functionality and production delivery timeline.

1.1.1 Background

Current Functionality

The September 2017 release of the AASHTOWare Project 4.0 software provided AASHTO

member agencies with the latest functionality to support daily construction management

activities (e.g., estimation, preconstruction, civil rights, labor, construction, and materials). The

software represents the ongoing effort by AASHTO and its member agencies to migrate

client/server AASHTOWare Project module functionality to the web-based platform and

supplement it with new features and functionality.

There remains one area of client/server AASHTOWare Project module functionality to migrate:

AASHTOWare Project BAMS/DSS, which provides decision support and analysis

functionality. The AASHTOWare Project 4.0 software introduced initial AASHTOWare Project

Data Analytics functionality to: “Utilize web-based AASHTOWare Project as the historical

pricing source”, Ticketed Modification Request (TMR) APR-14907. The AASHTOWare

1-2 Project Overview

Project 4.0 software also included the AASHTOWare Project Data Analytics license key, and the

AASHTOWare Project 4.1 software will include “Authentication for AASHTOWare Project

Data Analytics to Support SaaS” (TMR APR-17638), which allows already authenticated

AASHTOWare Project users to access the SaaS functionality without needing to log in twice.

Software-as-a-Service (SaaS)

As the AASHTOWare Project software has progressed, so has technology. SaaS is now a

mature technology platform that provides AASHTO and its member agencies with capabilities to

develop and utilize software in the cloud as opposed to agency-specific installations. AASHTO,

Info Tech, and three agencies were involved in a pilot project in 2017 to test the development

and deployment of analysis functionality as SaaS. The pilot validated an approach where the

historical repository for all agency data remains with the agency’s web-based AASHTOWare

Project installation, and agency users can securely run analysis functions through the SaaS. A

service running on an agency’s application server securely copies the necessary data from the

agency’s web-based AASHTOWare Project database to the SaaS. The results of the analysis are

available via a user interface in the SaaS. The following diagram illustrates the planned

architecture.

Figure 1-1. AASHTOWare Project Data Analytics SaaS Architecture

Recent Work

The PTF approved an interim six-month development project that began in February 2018. The

project will deliver initial core SaaS production functionality for Line Item Profiles and Bid

Evaluation Analysis by August 2018 based on PTF approval. The production delivery will

utilize results from the 2017 SaaS pilot and the AASHTOWare Project Decision Support

Functionality Review Summit that was held in December 2017. The Summit was well-attended,

with 46 participants representing 22 agencies. The results from the Summit were also used to

prioritize the functionality that is represented in Appendix A of this work plan. The Summit

participants also identified four new analysis features, which are included in Appendix A:

▪ Compare prices of similar items (using existing item classifications) within letting

and recent history

Results

AASHTOWare Project Unified

Database Analysis

AASHTOWare Project

Data Analytics™ SaaS

Web Browser

Data Subsets


▪ Unbalanced bidding analysis

▪ Compare contracts

▪ Trends of unbalanced items

The PTF also approved the inclusion of two dashboard themes (see Appendix A).

Data Migration and Ad Hoc Reporting

Throughout the client/server AASHTOWare Project software migration, migration tools have

been developed for agencies to migrate their client/server data to the web-based platform. The

PTF has outlined migration services (information available through Cloverleaf) related to the

migration of agency data. These services are based on survey results gathered from the user

community (AASHTOWare Project BAMS/DSS Models that Use Construction Data and

AASHTOWare Project BAMS/DSS D-Tables Requiring Migration).

The web-based AASHTOWare Project software comes with a built-in run-time ad hoc reporting

tool called ActiveReports, and agencies can use their own industry-standard reporting tools, such

as SAS and Crystal Reports (Business Objects), for ad hoc reporting. Agencies can also access

the data in the unified database using the Open Data Protocol (OData) standard.

The SaaS will provide the ability for analysis data to be exported and downloaded to an agency’s

preferred tool (e.g., Microsoft Excel, Tableau) for further manipulation and analysis.

What’s Next

This work plan addresses the activities required to continue the development of the

AASHTOWare Project BAMS/DSS features, along with new functionality not found in the

legacy system, in the web‐based and SaaS platforms. The work plan also addresses frequent

production releases throughout the life of the project as opposed to the end.

1.2 Goals and Objectives

Info Tech will deliver fully functioning, tested software and applicable product documentation

representing the agreed upon functionality (see Appendix A) by following the artifact and

deliverable creation and approval processes described in this work plan. Info Tech will deliver

the software and documentation according to the schedule defined in Chapter 4. Schedule,

Milestones, and Price.

Based on the positive results from the SaaS pilot, AASHTO intends to offer the functionality

listed in Appendix A via the web-based and SaaS platforms. AASHTO will be able to leverage

the SaaS work products created during the previous projects. The web-based platform will

provide back-end data and customizable reporting-related functionality, and the SaaS platform

https://www.cloverleaf.net/index.php?option=com_docman&task=doc_download&gid=1728


will provide front-end analysis functionality. The web-based functionality will be delivered for

production use in one scheduled web-based AASHTOWare Project release early in the project.

The SaaS functionality will be delivered continuously for production use throughout the

project. The goal is to release new SaaS functionality every two weeks to an evaluation

environment and promote those releases to a production environment as soon as possible based

on approval. The SaaS releases will be in a supported production environment for each licensing

agency, and the agency will have access to a copy of its production data from its AASHTOWare

Project unified database. The functionality listed in Appendix A will not be a duplicate of the

current AASHTOWare Project BAMS/DSS models, but rather a redesign of the key features

taking advantage of SaaS capabilities where applicable. Agencies will not be required to license

the SAS analytical tool or any other third-party software to use the AASHTOWare Project Data

Analytics software.

The web-based and SaaS Appendix A features are independent. Coordinating the web-based

AASHTOWare Project software release with the SaaS releases will not be necessary. Refer to

Appendix A for further details regarding the work plan scope and Chapter 4. Schedule,

Milestones, and Price for the project schedule.

The following sections describe the scope, approach, artifacts/deliverables, schedule, and

price. The overall assumption is that this work will leverage the current web-based and SaaS

AASHTOWare Project code bases, documentation, architecture, methodology, tools, techniques,

processes, etc. as much as possible. This work plan will be incorporated into an agreement

between Info Tech and AASHTO upon acceptance.

1.3 Scope

Info Tech will perform the following. Refer to Chapter 3. Work Activities for a detailed

description of the work activities.

Project Includes

User Requirements Specifications (URS), System Requirements Specifications (SRS), detailed Functional Design Specifications (FDS), and Requirements Traceability Matrix (RTM) created for the web-based Appendix A functionality. URS and RTM for the new SaaS Appendix A functionality (compare prices of similar items within letting and recent history, unbalanced bidding analysis, compare contracts, trends of unbalanced items, two dashboard themes). A schedule and estimate placeholder for the new SaaS Appendix A functionality. Upon URS/RTM approval, Info Tech will work with the PTF to create a change order based on the approved scope. Two four-day on-site Technical Review Team (TRT) meetings will be held during the project with up to twenty total participants (includes agency, PTF, and AASHTO participants) for each on-site visit. The objectives (e.g., requirements, testing, etc.) for the on-sites will be approved by the PTF and TRT. The on-site meetings will occur in Gainesville, Florida at Info Tech headquarters, and Info Tech will work with the PTF and TRT to schedule these on-site visits.


Project Includes

Eight two-day Info Tech agency on-site visits will be held during the project. The objectives for these on-site visits include assessing current and planned agency decision support analysis practices, assessing agency technology infrastructure, and obtaining agency feedback on the AASHTOWare Project Data Analytics software. The agency on-site visits provide the opportunity for the Info Tech development team to meet with several agency users and discuss their agency-specific practices and business needs. Develop, test, and package software for the Appendix A functionality. Regular evaluation and production releases of the SaaS AASHTOWare Project software. Twenty hosted agency evaluation instances and twenty hosted production instances for the SaaS AASHTOWare Project software. Project documentation (see section 6.1.2). Product documentation (see sections 6.1.3 and 6.1.4). Production source code will be available upon request to participating agencies as approved by AASHTO. Note that the delivered source code may contain SaaS, hosting (e.g., Amazon Web Services), and third-party tool code. Agencies must abide by AASHTO’s source code agreement, which includes complying with third-party software license agreements as contained in the third-party tools and notices section of the applicable AASHTOWare Project installation.

Table 1-1. Project Includes

Project Excludes

Backup and Disaster Recovery Plan. This is covered under the then-current AASHTOWare Project Maintenance, Support, and Enhancement Work Plan (MSE). Release costs (e.g., packaging, release project management, etc.) for the web-based Appendix A functionality will be handled under the then-current MSE project associated with the web-based AASHTOWare Project release. Support for the hosted TRT Preview site for the web-based software will be covered under the then-current AASHTOWare Project MSE. Operational, maintenance, and support services and direct costs for the production SaaS will be covered under the then-current AASHTOWare Project MSE. The operational terms for the SaaS will be included in the contract for the then-current MSE. No data migration services are included. No activities are planned to support a third-party testing entity, as it is assumed this work will be handled outside of the work plan at the discretion of AASHTO and the PTF. Product-related documentation that needs to be updated on Cloverleaf (e.g., Frequently Asked Questions, Technical Architecture Overview, brochures, etc.) will be handled under the then-current MSE. No SaaS product/user documentation (e.g., Training and User Guides) are included in the work plan. Requests for product/user documentation may come up during the project, but it is too early to assess what the user requirements may be and what may be the best media for delivery. If requirements do arise during the project, Info Tech will provide a proposal and estimate to the PTF and this work will be funded by the then-current MSE based on PTF approval. No new performance tests are anticipated for the web-based Appendix A functionality.


Table 1-2. Project Excludes

1.4 Assumptions

Assumptions

1 The current AASHTOWare Project Data Analytics SharePoint workspace will be used to store the Technical Review Team (TRT) artifacts, deliverables, and work products.

2 One TRT will be appointed by the PTF for the project, the AASHTOWare Project Data Analytics TRT. Info Tech will work with AASHTO, the PTF, and the current TRT members to provide orientation to new members that join during the course of the project. Feature Package Groups (FPGs) will be created as needed from TRT members for the web-based Appendix A functionality.

3 The project will continue to follow the user interface material design guidelines for the SaaS Appendix A functionality.

4 Info Tech will engage the PTF for any questions or direction that involves the user interface (UI) and report layout standards.

5 Info Tech will work with the PTF and TRT to define performance criteria for the SaaS Appendix A functionality.

6 No AASHTOWare Project BAMS/DSS enhancements are anticipated based on the Appendix A functionality.

7 The AASHTOWare Project Data Analytics software will not require agencies to license the SAS analytical tool or any other third-party software.

8 Review gates and standards associated with the web-based AASHTOWare Project Appendix A functionality will be handled under the then-current MSE project associated with the web-based AASHTOWare Project release.

9 Agency data used in this project will follow the Agency Grant License Data Agreement Template data usage policy and dispositioned at the end of the project according to the agency’s response in the data agreement.

10 Info Tech will use the approved URS/RTM for the applicable SaaS Appendix A functionality. This work was done under a previous project outside of this work plan (AASHTOWare Project Decision Support December 2017 Functionality Review Summit).

11 Info Tech will conduct an annual security assessment on the AASHTOWare Project Data Analytics service. Info Tech’s obligation to oversee the performance of the security assessment is governed by the then-current MSE.

12 This work plan and price are valid through June 30, 2019.

Table 1-3. Assumptions

https://material.io/guidelines/


1.5 Constraints

Constraints

1 Info Tech will use existing web-based and SaaS AASHTOWare Project standards, functionality, documentation, and infrastructure as much as possible. Requirements that significantly impact existing standards, infrastructure, documentation, and functionality will be documented as change controls and reviewed with the PTF for direction.

2 The TRT members will be the primary points of contact for their agencies. The TRT members will consolidate any requested agency feedback for web-based artifacts and deliverables prior to submittal to Info Tech. This includes documents provided in Microsoft Word. Info Tech will receive one consolidated document per agency for web-based feedback. Feedback for the SaaS AASHTOWare Project software will be submitted by users from within the SaaS, during review meetings, etc..

3 Info Tech will comply with the applicable standards contained in the September 1, 2017 AASHTOWare® Standards and Guidelines Notebook (as amended October 12, 2017) to perform the work with exceptions noted in Section 6.4. If new standards become available during the course of the project, Info Tech will work with AASHTO and the PTF to identify any potential impacts and address any changes through the standard change control process.

4 Info Tech will perform the Voluntary Product Accessibility Template (VPAT) 508/Web Content Accessibility Guidelines (WCAG) assessment on the SaaS Appendix A functionality in conjunction with the web-based AASHTOWare Project software releases. If the assessment indicates areas of non-compliance based on changing standards since the last assessment, Info Tech will provide recommendations to the PTF.

5 The TRT members will use existing web-based AASHTOWare Project test data on the TRT Preview site and manually populate any new data as needed to test the web-based Appendix A functionality. No activity for Info Tech to populate the TRT Preview site, whether manually or with migrated agency data, is included in this work plan. All new data needs to conform to the existing TRT Preview site data (e.g. reference data, code tables, security).

6 TRT members wishing to test the SaaS Appendix A functionality must have a valid AASHTOWare Project BAMS/DSS or AASHTOWare Project Data Analytics license or approval from AASHTO. Agencies will log in using Cloverleaf credentials if they are not using the AASHTOWare Project 4.1 software.

7 Report format/layouts for the web-based Appendix A report functionality may differ from the original AASHTOWare Project BAMS/DSS reports based on the Report Layout Standards.

8 The SaaS evaluation and production areas will be available for use according to the availability times posted on Cloverleaf. Support for the sites will be according to the availability times posted on Cloverleaf. Info Tech reserves the right to take down the sites and Cloverleaf for maintenance as needed.

9 The SaaS software will be accessible by AASHTO and can be downloaded at any time. An Archive Package will be delivered annually to AASHTO in conjunction with the web-based AASHTOWare Project releases and at the end of the project. The archive package will contain the project and product documentation only (e.g., status reports, deliverables, meeting minutes, etc.).

Table 1-4. Constraints


2. User Requirements and Specifications

Please refer to Appendix A. AASHTOWare Project Data Analytics Development and

Production Releases Work Plan Scope for the functionality that Info Tech will deliver through

the activities in this work plan. As stated in Table 1-1, Info Tech will deliver URS, SRS, FDS,

and RTM artifacts and deliverables for the web-based Appendix A functionality. Info Tech will

deliver URS and RTM artifacts and deliverables for the new SaaS Appendix A functionality

(compare prices of similar items within letting and recent history, unbalanced bidding analysis,

compare contracts, trends of unbalanced items, two dashboards).

2-2 User Requirements and Specifications



3. Work Activities

This work plan has the following activities, which are described in further detail below:

▪ Management and Administration

▪ Start-Up/Mobilization

▪ TRT On-sites

▪ Info Tech Agency On-sites

▪ TRT Review Meetings

▪ Requirements, Analysis, and Design

▪ Construction

▪ Testing

▪ Product Delivery and Project Closeout

▪ SaaS Operation, Maintenance, and Support Services

▪ Warranty

3-2 Work Activities

This work plan will follow the Standard Project Lifecycle as described in Section 1.2.1.1 of the

September 1, 2017 AASHTOWare Standards and Guidelines Notebook (as amended October 12,

2017) with some exceptions (see Section 6.4 Exceptions to AASHTOWare Standards).

The following diagram depicts the lifecycle that will be followed for the SaaS development. The

web-based development will follow the lifecycle of the then-current MSE project associated with

the web-based AASHTOWare Project release.

Figure 3-1. SaaS AASHTOWare Project Development Lifecycle

3.1 Project Management/Support Activities

The following activities will occur to support the overall work plan objectives. These activities

will occur throughout the project.

3.1.1 Management and Administration

This involves several tasks, including project management and oversight, status reporting, TRT

coordination, cross-TRT coordination, record keeping, meeting support (agendas, minutes,

workspace postings, etc.) for TRT and PTF meetings, and daily communications with team

members and stakeholders on status.

3.1.2 Project Startup/Mobilization

This involves tasks necessary to mobilize the project, including repository and collaboration

space setup, project kickoff (remote) meeting, team member ramp up, and repository creation.

3.1.3 TRT and Agency On-sites

This includes the tasks necessary to prepare, facilitate, attend, support, and provide follow-up for

the on-site meetings as described in Table 1-1.

3.1.4 TRT Review Meetings

This activity includes tasks necessary for business managers, subject matter experts,

administrative staff and others to prepare, facilitate, attend, support, and provide follow-up for

Construction & Testing

TRT Evaluation

Production Release

Warranty

Performed for each SaaS release


the TRT meetings. These TRT meetings include regularly scheduled meetings and meetings that

may come up during the project to discuss specific topics of interest (e.g., Feature Package

Group meetings).

3.2 Requirements, Analysis, and Design

Info Tech will complete the URS/SRS/FDS for the web-based Appendix A functionality and

deliver them as feature packages following the approach used in the then-current MSE project

associated with the web-based AASHTOWare Project release.

Info Tech will complete the URS for the new SaaS Appendix A functionality (compare prices of

similar items within letting and recent history, unbalanced bidding analysis, compare contracts,

trends of unbalanced items, two dashboards) using the same approach as the AASHTOWare

Project Decision Support December 2017 Functionality Review Summit.

3.3 Construction

Info Tech will utilize the approved requirements, analysis, and design artifacts and deliverables

for the Appendix A functionality and continue with a test-driven development (TDD) approach

used in past projects to develop code, automated tests, and documentation that meets the stated

requirements.

Info Tech will complete the development using the latest web-based and SaaS AASHTOWare

Project code bases, automated tests, and documentation using the same tools, infrastructure, and

processes augmented where needed.

The web-based Appendix A functionality will follow the development lifecycle of then-current

MSE project associated with the web-based AASHTOWare Project release.

Developed SaaS Appendix A functionality will follow the development lifecycle described in

Figure 3-1 above. Once Info Tech has completed development and testing of features associated

with a release, they will be delivered to the TRT evaluation instance for testing.

3.4 Testing

The web-based Appendix A functionality will follow the testing lifecycle of then-current MSE

project associated with the web-based AASHTOWare Project release.

Info Tech will post a SaaS software release to the TRT evaluation instance every two weeks for

TRT agency testing. TRT members will test the software based on the “What’s New” notice.

When the TRT has completed their testing, Info Tech will request PTF approval to release the

software to production based on TRT recommendation.

3-4 Work Activities

3.4.1 Accessibility Testing

Info Tech will conduct accessibility compliance testing on the web-based and SaaS Appendix A

functionality annually in conjunction with the web-based AASHTOWare Project software

releases. Info Tech will review the software against the latest 508/WCAG accessibility standards

(VPAT 2.0) and update the VPAT as needed. Info Tech will make any recommendations to the

PTF based on changes in the standard if applicable. See Section 1.5 Constraints.

3.5 Product Delivery and Project Closeout

The web-based Appendix A functionality will be delivered for production use as part of the then-

current MSE project associated with the web-based AASHTOWare Project release.

Info Tech will post SaaS updates to the production instance based on PTF approval. AASHTO

has access to the hosted instance and can archive the contents at any time. A Project Closeout

Review Gate will be submitted to the PTF at the end of the project.

3.6 SaaS Operation, Maintenance, and Support Services

Info Tech will provide one Full Time Equivalent (FTE) resource comprised of a combination of

personnel maintaining the operation of the service (e.g., business lead who has responsibility for

the overall service, IT/technology expert who checks logs and keeps the service running, a

support person for internal and external customers, etc.). The personnel will also apply

appropriate procedures to ensure agency data is secure and properly managed inside the service.

These pricing and terms for these services will be covered under the then-current MSE.

3.7 Warranty (SaaS)

The web-based AASHTOWare Project software will follow the same warranty policy as

established under the annual MSE contract. The purpose of this section is to establish a warranty

policy for the SaaS AASHTOWare Project software. The SaaS AASHTOWare Project software

includes the base code, documentation, and packaging. Platform-specific errors resulting from

third-party tools or hosted services software are not part of the warranty obligation. Service-

level warranty terms for the operation of the SaaS AASHTOWare Project software are excluded

from this section and are covered under the then-current AASHTOWare Project MSE.

The SaaS AASHTOWare Project software is subject to the following warranty:

▪ The Contractor shall warrant its work to correct any issue reported in production code

that does not function according to the approved URS.

▪ The Contractor shall warrant its work for acts of negligence where the Contractor

failed to take steps that a reasonable software developer would have taken.


▪ The Contractor shall warrant its work for instances where the software code produces

clearly unintended results. An example is where the intention of a function in the

code was to display data for a vendor selected by the user, but data for a different

vendor is displayed.

Warranty Period

Info Tech will warrant production-delivered SaaS features during the work plan's performance

period and for two years after the work plan final release.

Issues reported against the production SaaS AASHTOWare Project software delivered after this

work plan will be covered under the warranty terms stated in the then-current MSE.

Verification and Resolution of Warranty Errors

If an agency reports an error within the warranty period, the Contractor shall validate the

function for which the error was reported.

If the function is determined not to be functioning as approved, the reported error is classified as

a warranty error. Warranty errors are resolved in the next scheduled release or sooner based on

criticality.

If the reported error is determined to be a change to the approved URS, it is classified as a

modification request to the scope of intended software and is not a warranty item.

Resolution of Non-Warranty Errors

A reported error that does not meet the above definition of a warranty error is considered a

modification in the requirements for the software. Discovered issues that are not categorized as

warranty errors are addressed according to AASHTO funding and approval.

3-6 Work Activities



4. Schedule, Milestones, and Price

This section contains the schedule, milestones, deliverables, review gates, price, and estimation

methods for the project for the web-based and SaaS AASHTOWare Project software releases.

As stated in the Assumptions and Constraints section, Info Tech has included an estimate and

schedule placeholder for the six new themes listed in Appendix A. Upon PTF approval of the

URS/RTM, Info Tech will submit a change order to the PTF detailing the revised estimate and

any schedule variance.

Info Tech will utilize the SaaS themes, features and priorities established as part of the

AASHTOWare Project Decision Support December 2017 Functionality Review Summit to help

define the order of theme and associated feature production delivery for the work plan. The

themes and their features are listed in Appendix A in priority order from the Summit. Info Tech

has outlined the initial production delivery for the themes in a Gantt chart provided in Appendix

A. Info Tech will work with the TRT/PTF to revise the theme delivery order as needed

throughout the project.

The following Gantt chart depicts the high-level project schedule based on a desired start date of

August 1, 2018. A detailed schedule will be provided to the PTF in the monthly status report

updated throughout the project as needed. Note that the web release schedule will be

administered through the then-current MSE.

4.1 High-Level Schedule

Calendar Year 2018 2019 2020 2021 2022

Activity Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4

Mobilization X X

Project Management X X X X X X X X X X X X X X X X X

SaaS Releases

Development X X X X X X X X X X X X X X X X X

TRT Evaluation X X X X X X X X X X X X X X X X X

Production Release X X X X X X X X X X X X X X X X X

4-2 Schedule, Milestones, and Price

Calendar Year 2018 2019 2020 2021 2022

Web Release

Design X X

Development X X

Testing X X X X

Production Release X

Table 4-1. High-Level Project Schedule

4.2 Milestones, Review Gates, and Deliverables

Info Tech will submit the following review gates and milestones/deliverables for this project as

stated in Section 1.2.2 of the September 1, 2017 AASHTOWare Standards and Guidelines

Notebook (as amended October 12, 2017) and Chapter 3. Work Activities. Refer to exceptions

noted in Section 6.4 Exceptions to AASHTOWare Standards.

As stated in Table 1-3, review gates associated with the web-based AASHTOWare Project

Appendix A functionality will be handled under the then-current MSE project associated with

the web-based AASHTOWare Project release.

For each milestone/deliverable listed in Table 4-2 below, the TRT/PTF will have ten business

days to conduct their first review. Info Tech will have five business days to respond with

revisions. The TRT/PTF will have five business days to provide final approval.

Milestone/ Deliverable/ Review Gate

Content Type When Delivered and to Whom

(URS/SRS/FDS) Requirements, Scenarios/Test Procedures, Glossary

Web As needed to Feature Package Groups

RTM RTM Web Delivered under the then-current MSE project associated with the web-based AASHTOWare Project release

URS Features SaaS As needed to the TRT RTM RTM SaaS With Closeout Review Gate to PTF Test Plan Approach, roles and

responsibilities, etc. for testing the SaaS Appendix A functionality

SaaS Beginning of project to PTF and updated throughout project as needed

Product Documentation (web)

See section 6.1.3 Web As needed in conjunction with the applicable web-based AASHTOWare Project release


Milestone/ Deliverable/ Review Gate

Content Type When Delivered and to Whom

Product Documentation (SaaS)

See section 6.1.4 SaaS Available for download at any time from within the SaaS AASHTOWare Project software

Closeout Review Gate

RTM and Archive Package

SaaS End of the project to the PTF. The VPAT, Technical Design Specifications (TDS), User Interface/Report Layout Standards, and Application Infrastructure Component List (AICL) will be updated annually where applicable in conjunction with the web-based AASHTOWare Project releases.

Table 4-2. Review Gates and Milestones/Deliverables

4.2.1 SaaS-Specific Invoicing

Info Tech will include the monthly payment amount (see Table 4-3) in the monthly AASHTO

invoicing, and the final Project Closeout payment amount in the AASHTO invoice following

Project Closeout review gate approval.

4.3 Price

The firm fixed-price for tasks, activities, milestones, and deliverables for the project are defined

in the table below.

4.3.1 Total Price

Deliverable/Payment Delivery Price % of Total

Web-Based Functionality (70%) Web Release Development Review Gate $1,665,300.00 16.90% Web-Based Functionality (30%) Web Release Beta Test Acceptance

Review Gate $713,700.00 7.26%

SaaS Payment #1 Aug 2018 Invoice $155,704.70 1.58% SaaS Payment #2 Sep 2018 Invoice $155,704.70 1.58% SaaS Payment #3 Oct 2018 Invoice $155,704.70 1.58% SaaS Payment #4 Nov 2018 Invoice $155,704.70 1.58% SaaS Payment #5 Dec 2018 Invoice $155,704.70 1.58% SaaS Payment #6 Jan 2019 Invoice $155,704.70 1.58% SaaS Payment #7 Feb 2019 Invoice $155,704.70 1.58% SaaS Payment #8 Mar 2019 Invoice $155,704.70 1.58% SaaS Payment #9 Apr 2019 Invoice $155,704.70 1.58%



SaaS Payment #10 May 2019 Invoice $155,704.70 1.58% SaaS Payment #11 Jun 2019 Invoice $155,704.70 1.58% SaaS Payment #12 July 2019 Invoice $155,704.70 1.58% SaaS Payment #13 Aug 2019 Invoice $155,704.70 1.58% SaaS Payment #14 Sep 2019 Invoice $155,704.70 1.58% SaaS Payment #15 Oct 2019 Invoice $155,704.70 1.58% SaaS Payment #16 Nov 2019 Invoice $155,704.70 1.58% SaaS Payment #17 Dec 2019 Invoice $155,704.70 1.58% SaaS Payment #18 Jan 2020 Invoice $155,704.70 1.58% SaaS Payment #19 Feb 2020 Invoice $155,704.70 1.58% SaaS Payment #20 Mar 2020 Invoice $155,704.70 1.58% SaaS Payment #21 Apr 2020 Invoice $155,704.70 1.58% SaaS Payment #22 May 2020 Invoice $155,704.70 1.58% SaaS Payment #23 Jun 2020 Invoice $155,704.70 1.58% SaaS Payment #24 July 2020 Invoice $155,704.70 1.58% SaaS Payment #25 Aug 2020 Invoice $155,704.70 1.58% SaaS Payment #26 Sep 2020 Invoice $155,704.70 1.58% SaaS Payment #27 Oct 2020 Invoice $155,704.70 1.58% SaaS Payment #28 Nov 2020 Invoice $155,704.70 1.58% SaaS Payment #29 Dec 2020 Invoice $155,704.70 1.58% SaaS Payment #30 Jan 2021 Invoice $155,704.70 1.58% SaaS Payment #31 Feb 2021 Invoice $155,704.70 1.58% SaaS Payment #32 Mar 2021 Invoice $155,704.70 1.58% SaaS Payment #33 Apr 2021 Invoice $155,704.70 1.58% SaaS Payment #34 May 2021 Invoice $155,704.70 1.58% SaaS Payment #35 Jun 2021 Invoice $155,704.70 1.58% SaaS Payment #36 July 2021 Invoice $155,704.70 1.58% SaaS Payment #37 Aug 2021 Invoice $155,704.70 1.58% SaaS Payment #38 Sep 2021 Invoice $155,704.70 1.58% SaaS Payment #39 Oct 2021 Invoice $155,704.70 1.58% SaaS Payment #40 Nov 2021 Invoice $155,704.70 1.58% SaaS Payment #41 Dec 2021 Invoice $155,704.70 1.58% SaaS Payment #42 Jan 2022 Invoice $155,704.70 1.58% SaaS Payment #43 Feb 2022 Invoice $155,704.70 1.58% SaaS Payment #44 Mar 2022 Invoice $155,704.70 1.58% SaaS Payment #45 Apr 2022 Invoice $155,704.70 1.58% SaaS Payment #46 May 2022 Invoice $155,704.70 1.58% SaaS Payment #47 Jun 2022 Invoice $155,704.70 1.58%



Project Closeout Review Gate (SaaS Payment #48)

July 2022 Invoice $155,704.10 1.58%

Total $9,852,825.00 100.00%

Table 4-3. Total Price

4.3.2 Price Breakdown

Task Group Name Price

Web-based AASHTOWare Project

Management, administration & TRT/FPG meetings $285,055

Design, unit/acceptance tests, online help, documentation updates, and development $1,766,214

Alpha testing (2 rounds + fixes) $327,731

Total Web-based AASHTOWare Project $2,379,000

SaaS-based AASHTOWare Project

Management and administration $537,067

SaaS development, testing, and delivery $5,484,220

TRT on-sites (2) $17,354

Project and product documentation $72,704

6 new themes requirements gathering $28,468

6 new themes estimate placeholder $1,110,592

Total SaaS-based AASHTOWare Project $7,250,405

Work plan preparation $65,000

Contract preparation $2,500

Directs • SaaS Dev/Eval AWS: $72,000 • TRT on-sites: $1,600 • Info Tech agency on-sites (8): $82,320 $155,920

Grand Total $9,852,825

Table 4-4. Price Breakdown


4.4 Estimation Methods and Estimates

4.4.1 Estimation Methods

Info Tech maintains several constantly-refined estimation approaches and models, based on the

type of work, to ensure consistency. After accounting for the scope of work effort, types of

resources, and the required deliverables, Info Tech uses a variety of methodologies, as

appropriate, to estimate price, effort, and schedule:

▪ Capacity-Based Estimate: Info Tech assesses work based on utilization of known

resources. Based on anticipated capacity levels for known resources and resource bill

rates, Info Tech can determine the output and estimate based on past production.

▪ Direct Estimate: Info Tech directly estimates work based on requirements,

assumptions, and constraints where possible. Direct estimation is typically used for

factors that are largely known. For example, approved labor rates, testing schedules,

and other factors can be used to estimate the effort for product testing.

▪ Parametric Estimate: Info Tech can assess work based on probability of unknown

factors using key cost drivers. Parametric estimation is typically used for factors that

involve a high amount of uncertainty. For example, complex tasks such as data

migration might be estimated using parametric formulae.

▪ Historically-Based Estimate: Info Tech refers to similar work effort when estimating

the effort, labor, work distribution, and other factors of an upcoming project when

relevant historical data is available. This data can be derived from project

management software. Historic data is typically used as a basis for direct or

parametric estimation or for validating those estimates.

Estimate data is typically recorded and calculated in Microsoft Excel spreadsheets. Estimates

progress through multiple rounds of internal review to ensure accuracy in the calculation and

methodology.

4.4.2 Estimates

The following provides estimates of effort, schedule, and any other estimate that was used to

determine the total price.

Estimates

Total effort estimate in person-hours 64,562

Schedule estimate in calendar months 48

Table 4-5. Estimates


5. Organization and Staffing

5.1 Organizational Structure

The following diagram depicts Info Tech’s organizational structure for the work plan in relation

to external stakeholders. Info Tech assumes one TRT for the project. Info Tech will engage the

PTF, other TRTs, and FPGs as needed throughout the project as approved by the PTF.

Figure 5-1. Organization

5-2 Organization and Staffing

5.2 Roles and Responsibilities

The following table summarizes roles and responsibilities for the organizational entities depicted

above.

Role Responsibility Organization

Sr. Executive Stakeholders

Contract oversight. Review and approval of contract modifications.

Special Committee on AASHTOWare (SCOA)

Executive Stakeholders

Project oversight. Review and approval of major deliverables/milestones and review gates. Review and approval of change orders. Work with the AASHTO Project Manager to monitor the budget and allocate funds as necessary. Responsible for overall product vision. Responsible for managing the TRT and ensuring the TRT members understand their roles and the product vision.

PTF

Project Manager

Responsible for the work plan and related agreement between AASHTO and the Contractor (Info Tech). Coordinates and collaborates with the PTF and TRT. Enforces project management requirements and AASHTOWare standards. Ensures action items and issues are addressed in a timely manner. Monitors the monthly status, budget, risk, and schedule reports, advising the PTF, and Info Tech on issue resolution. Manages change control process and contract modification requests. Participates in regular project meetings.

AASHTO

Stakeholders Participate in development, review, and approval of artifacts and software testing. Collaborate with the members in their own agency to clarify requirements as needed. Participate in regular project meetings and software testing. Work to collaborate on issues that are in the best interest of the product for all member agencies.

TRT

Beta Testers Provide data and resources to participate in the web-based AASHTOWare Project beta testing activity. Participate in regular beta meetings. Provide data to the Contractor in advance of the beta testing activity. Administer, support, and test throughout the beta period. This activity will be coordinated under the then-current MSE project associated with the web-based AASHTOWare Project release.

Selected Agencies

VP and Directors

Oversight, monitoring and support to the Info Tech project team. Review of key deliverables and milestones for conformance to the work plan and AASHTOWare Standards and Guidelines. Escalation of issues to the PTF as needed. Review of change orders and contract modifications.

Info Tech Management



Project Manager

Responsible for development and delivery of written and verbal administrative communications pertaining to the work plan activities. In collaboration with team leads, act as the manager, coach, and representative to management for the team. In collaboration with Business Managers and team leads, define agenda for and notes the creation and follow-up of action items for PTF and TRT meetings. Manage overall communication and follow-up regarding general issues and status reporting. Consolidates deliverables and communications as needed for TRT/PTF review. Coordinate, define agenda for, and note the creation and follow-up of action items for planning/review, retrospective, and daily meetings. Facilitate resolution to impediments identified by team. Manage Info Tech record keeping and time tracking requirements. Facilitate change management in collaboration with Business Managers and team leads. Work with AASHTO PM and PTF to ensure project and product vision are understood by all team members and any issues are dealt with according to the best interests of the project and product. Monitor budget and reporting processes and prepare project status report.

Info Tech

Business Managers

Lead the TRT and Info Tech team through the artifact and deliverable creation throughout the project. Ensure artifact creation is according to applicable Appendix A requirements and aligned with applicable standards. Provide lead business area expertise to the team. Facilitate the TRT and/or FPG meetings. Work with the Info Tech Project Manager to ensure goals and objectives are accomplished.

Info Tech

Subject Matter Experts

Draft artifacts for internal and external review. Participate in internal and TRT meetings as needed. Work with developers and Business Managers to create artifacts for respective areas of expertise. Provide business analysis and application knowledge to the team. Provide application testing as needed.

Info Tech

Scrum Master Lead the team of developers. Responsible for daily development status and reporting status out to Info Tech Project Manager. Manage team burndown progress. Responsible for managing developers to resolve technical issues and maintain product technical health.

Info Tech

Developers Work with Subject Matter Experts, Business Managers, and TRT to create artifacts. Resolve technical issues and recommend technical options that will maintain and improve the technical health of the product. Develop, maintain, and assess technical upgrades for product code. Support, maintain, and upgrade technical environments as needed.

Info Tech

Test Coordinator

Plan, execute, and manage Info Tech test activities. Work with the Info Tech Project Manager and team members throughout this process. Prepare and manage test environments and report on testing status.

Info Tech

Testers Execute assigned tests and report on testing status for individual items. Prepare test data as needed.

Info Tech

5-4 Organization and Staffing


Beta Coordinator

Plan, execute, and manage the overall beta test activity. Work with the Info Tech Project Manager, team members, the TRT and beta agencies throughout this process. This activity will be handled under the then-current MSE project associated with the web-based AASHTOWare Project release.

Info Tech

Technical Writers

Work with developers and Subject Matter Experts to create online help and project documentation. Create, update, and review project deliverables and artifacts as needed according to applicable standards.

Info Tech

Project Administration

Provide day-to-day support for the team. Handle meeting logistics, minute taking, document posting, etc.

Info Tech

Table 5-1. Roles and Responsibilities

5.3 Contractor Staffing

The following key Info Tech personnel will be assigned to this effort, and their biographies are

provided in Appendix B. Info Tech will have additional staff allocated based on the work being

performed at that time and the expertise required. Representative biographies for additional staff

have been included in Appendix B.

Info Tech agrees that the continuity of key personnel is critical and agrees to the continuity of

key personnel. Subject to the exceptions below, any staff substitution for the key personnel

listed in Table 5-2 will have the prior approval of AASHTO. Without AASHTO’s prior written

approval, Info Tech shall not remove or reassign any of the key personnel until such time as the

key personnel have completed all of their planned and assigned responsibilities in connection

with performance of Info Tech’s obligations during the course of the project. This prohibition

against removal or reassignment shall not apply where key personnel must be replaced for

reasons beyond reasonable control of Info Tech, including but not limited to illness, disability,

and resignation of the key personnel’s employment; nor shall it apply to limit in any way Info

Tech’s discretionary right to terminate an employee as an “at will” employer under Florida law.

Contractor Key Personnel Role Name % Time on Project

Project Manager Elizabeth Rodgers 8%

Data Analytics Business Manager Randy Lawton 50%

Data Analytics Business Manager Ian Baldwin 50%

Technical Lead Developer Haval Aloussi 100%

Technical Lead Developer Dan Hay 100%

Test Coordinator Kateryna Bondareva 90%

Table 5-2. Contractor Key Personnel Staffing

.


6. Technical Process and Technologies

6.1 Methods and Standards

This section describes the approach for producing the deliverables and artifacts according to the

applicable standards in the September 1, 2017 AASHTOWare Standards and Guidelines

Notebook (as amended October 12, 2017), work activities described in Chapter 3. Work

Activities, and Section 6.4 Exceptions to AASHTOWare Standards.

6.1.1 URS/SRS/FDS and RTM Creation

The URS/SRS/FDS and RTM artifacts/deliverables document the requirements for the Appendix

A functionality.

Info Tech will complete the URS/SRS/FDS for the web-based Appendix A functionality and

deliver them as feature packages following the approach used in the then-current MSE project

associated with the web-based AASHTOWare Project release.

Info Tech will complete the URS for the new SaaS Appendix A functionality (compare prices of

similar items within letting and recent history, unbalanced bidding analysis, compare contracts,

trends of unbalanced items, two dashboards) using a similar approach as the AASHTOWare

Project Decision Support December 2017 Functionality Review Summit.

The above will be delivered to the TRT Feature Package Groups (FPGs) for review and

approval.

Info Tech will provide an overview of the artifacts/deliverables and the FPG processes to the

TRT at the beginning of the project.

6-2 Technical Process and Technologies

6.1.2 Project Documentation

Test Plan

The Test Plan describes several testing aspects in accordance with the September 1, 2017

AASHTOWare Standards and Guidelines Notebook (as amended October 12, 2017) including:

testing strategy, environments, schedule, and procedures. The Test Plan is specific to testing the

SaaS Appendix A functionality. Testing for the web-based Appendix A functionality will be

handled under the then-current MSE project associated with the web-based AASHTOWare

Project release.

Info Tech will deliver the Test Plan to the PTF early in the project and update it periodically

throughout the project as needed.

Updated User Interface/Report Layout Standards

The AASHTOWare Project User Interface Standards document provides a description of the

design and functionality aspects of the web-based AASHTOWare Project software that are

visible to the user.

The SaaS AASHTOWare Project software will follow the Material Design standards for the User

Interface. These standards will be referenced in the User Interface Standards document.

Info Tech will update the AASHTOWare Project User Interface Standards document, as

applicable, annually for approval by the PTF for delivery with the web-based AASHTOWare

Project releases as needed.

Updated Voluntary Product Assessment Template (VPAT)

The VPAT template artifact documents the software’s status towards the published standards for

the applicable 508/Web Content Accessibility Guidelines (WCAG) accessibility compliant

areas. Info Tech will review the applicable web-based and SaaS Appendix A functionality

against the latest standards (VPAT 2.0) annually and update the VPAT applicable content for

delivery with the web-based AASHTOWare Project releases as needed. Info Tech will make

any recommendations to the PTF as needed based on changes in the standards.

Technical Design Specifications (TDS)

As per Section 5.8.2 of the Software Development & Maintenance Process Standard in the


2017), the TDS consists of the following:

▪ Physical File and Database Structures (Data Model)

▪ Data Dictionary

▪ Technical Architecture

https://material.io/guidelines/


As the Appendix A functionality will not impact the AASHTOWare Project Data Model and

Data Dictionary, Info Tech will only update the Technical Architecture. Info Tech will start with

the latest approved version of this document and update applicable content annually for delivery

with the web-based AASHTOWare Project releases as needed.

Updated Application Infrastructure Component List (AICL)

Info Tech will start with the latest approved document and update it annually in conjunction with

the annual web-based AASHTOWare Project releases as needed.

6.1.3 AASHTOWare Project Product Documentation (Web-based AASHTOWare Project)

Updated Installation Instructions

The AASHTOWare Project Installation Instructions document provides instructions for the

installation and configuration of the web-based AASHTOWare Project software. Info Tech will

start with the latest approved document and update applicable content annually for delivery with

the web-based AASHTOWare Project releases as needed.

Updated Online Help

Info Tech will update the web-based AASHTOWare Project online help with any new/changed

information that may be needed based on requirements introduced with the AASHTOWare

Project Data Analytics software. Info Tech will start with the latest approved online help and

update applicable content annually for delivery with the web-based AASHTOWare Project

releases as needed.

Updated Bid-Based Estimation Methodology Document

Info Tech will update this document with any new/changed information that may be needed

based on requirements introduced with the AASHTOWare Project Data Analytics software. Info

Tech will start with the latest approved document and update applicable content annually for

delivery with the web-based AASHTOWare Project releases as needed.

Updated Implementation Planning Guide Package

Info Tech will update the guide package with any new/changed (e.g., SaaS) information that may

be needed based on requirements introduced with the AASHTOWare Project Data Analytics

software. Info Tech will start with the latest guide package and update applicable content

annually for delivery with the web-based AASHTOWare Project releases as needed.


6.1.4 AASHTOWare Project Product Documentation (SaaS AASHTOWare Project)

Data Elements Information

Access to this information was created during the interim six-month project and is incorporated

into the SaaS software. The information lists the data (fields) collected by the “Scribe” which is

a service running on an agency’s application server that securely copies the necessary data from

the agency’s web-based AASHTOWare Project database to the SaaS. Users will be able to

download the data elements information at any time from within the SaaS AASHTOWare

Project software. Contents of the information will be based on completed functionality to date.

6.2 Project Lifecycle

Info Tech will follow the Standard Project Lifecycle as described in Section 1.2.1.1 of the


2017) as previously described in Chapter 3. Work Activities.

Meetings will be held with the TRT at the beginning of the project to provide an orientation to

the work plan approach, TRT structure, and methodology. Info Tech will work with the PTF in

drafting the materials for these sessions.

The collaboration, review, and approval process with the TRT members and the PTF will be

accomplished through virtual meetings (conference call/webinar), e-mail, and a collaboration

workspace. The meeting schedules will be established during mobilization and adjusted as

needed. TRT on-site and Info Tech agency on-site meetings are planned to occur during the

course of the project (see Assumptions). Info Tech will work with the PTF and TRT to confirm

the objectives and timing for these meetings.

6.2.1 Web-Based AASHTOWare Project Software

TRT members will sign up to provide input on web-based Appendix A functionality at the

beginning of the project. Info Tech will draft each URS/SRS/FDS feature package and work

with the assigned TRT members (Feature Package Groups) to review the feature package. Once

the Feature Package Groups (FPGs) are satisfied with the contents of the initial feature package,

it will be posted to the TRT for review.

The TRT will have a set number of business days (see section 4.2) to review the feature package

and provide feedback. If revisions are required, Info Tech will revise the feature package in

accordance with the identified revisions. After the revisions have been completed, the feature

package will be re-submitted to the TRT for revision review. After TRT review, the FPGs will

provide final approval of the feature package. Info Tech will document the status of each feature

package in a package tracker that is maintained under the then-current MSE project associated

with the web-based AASHTOWare Project release.

The approved feature packages will then be brought into the construction phase under the then-

current MSE project associated with the web-based AASHTOWare Project release.


Info Tech will test the developed software, after which it will be made available to the TRT

Preview site, and the TRT will conduct their testing according to the Test Plan under the then-

current MSE project associated with the web-based AASHTOWare Project release. The final

software will be released in conjunction with the then-current MSE project associated with the

web-based AASHTOWare Project release.

6.2.2 SaaS AASHTOWare Project Software

Info Tech will develop the SaaS AASHTOWare Project software based on previously approved

URS feature packages. As the features are developed and tested, Info Tech will post the

software to the evaluation instance on a bi-weekly basis, and the TRT will begin its agency

testing. Upon PTF approval, Info Tech will post the software to the production instance.

6.3 Tools and Technologies

Info Tech will use the same tools and technologies as used on the latest web-based and SaaS

AASHTOWare Project development projects and will augment as needed based on PTF approval

where applicable.

6.4 Exceptions to AASHTOWare Standards

Info Tech will submit a formal request for an exception(s) to a standard if a requirement of the

standard cannot be complied with during the course of the project. The request will be sent to

the PTF early in the project. The request will include all proposed changes and/or exclusions to

one or more standards, along with the documentation that describes or justifies the reasons for

the exception (s) and any additional documentation for PTF consideration. If the work plan is

approved, the work plan revision history, date, and version will be updated, and the revised work

plan will be saved as a new document.

The following exceptions apply at this time:

1. The Functional Design, Alpha Test Acceptance, and Beta Test Acceptance review gates

will not be provided for the project. The web-based Appendix A functionality will be

addressed through the review gate process under the then-current MSE project associated

with the web-based AASHTOWare Project release. The SaaS Appendix A functionality

will follow the SaaS rapid delivery model established during the SaaS pilot and interim

six-month development projects. The SaaS AASHTOWare Project software releases

have less scope and are delivered through a hosted service, which reduces the delivery

and review timeframes. The development, testing, and delivery lifecycle is continuous

and does not function as a typical project. The software will be tested by representatives

from every agency participating in the project that wishes to perform the testing and with


their data. TRT and PTF review meetings will be used in lieu of review gate approvals

for the SaaS AASHTOWare Project software releases. Meeting minutes will be

documented for these meetings.

2. Info Tech will not provide a Development and Maintenance document. Pertinent

information contained in this document is provided in other deliverables (Technical

Design Specifications [TDS], Installation Instructions) and through other program-level

activities performed under the then-current MSE (e.g. Backup and Disaster Recovery

Plan).

3. The Archive Package will not contain the SaaS AASHTOWare Project software. The

SaaS software is accessible by AASHTO and can be downloaded at any time. The

Archive Package will be delivered annually to AASHTO in conjunction with the web-

based AASHTOWare Project releases and at the end of the project. The archive package

will contain the project and product documentation only (e.g., status reports, deliverables,

meeting minutes, etc.).

4. Info Tech will not provide a Backup and Disaster Recovery Plan, as this requirement will

be covered under the then-current MSE.


7. Monitoring and Control

7.1 Issue Management

Info Tech will follow similar processes and reporting for issue management as used on previous

web-based AASHTOWare Project development projects. Issues will be logged and reported out

in the monthly status report (see Section 7.3 Status Reporting below). The Info Tech Project

Manager maintains a log to track all reported issues. This is a decision tracking log that

identifies how key issues are addressed, so as to provide transparency with stakeholders. This

log is updated throughout the project, as new issues arise and existing issues are addressed. Any

stakeholder can report an issue to the Info Tech Project Manager, who ensures that it is

documented in the log. The Info Tech Project Manager distributes the log to the appropriate

stakeholders as part of the monthly status report. When the log is updated, the most recent

version is distributed with the next monthly status report.

7.2 Change Management

Info Tech will describe change management for fixed-price development in separate project

work plans.

For time and materials services, change management allows all necessary changes to be made to

the scope, schedule, budget, and previously approved deliverables and services described in this

work plan, while ensuring that change impacts are clearly explained to the PTF and all necessary

stakeholders and external resources. Change management involves evaluating, controlling, and

approving changes made during the project.

The change control process below outlines the steps for creating, submitting, and approving

changes. Actions can result from this process, such as creating a contract modification and

entering the change in a log system, and detailed documentation is created for each change. This

7-2 Monitoring and Control

type of documentation will depend on what within the project is being changed (for example,

planned scope vs. functional specifications).

7.2.1 Examples of Change

Many scenarios can trigger the change control process. One scenario is triggered by changes in

work plan scope at any time during the fiscal year, such as the need for additional status

reporting or the replacement of approved TMRs.

In the case of submitted deliverables, feedback from the approving group is an expected part of

the approval process, although it might not happen in all cases. When feedback is given, Info

Tech will evaluate that feedback and determine if it is within the scope of this work plan. Info

Tech will treat any feedback that it considers outside work plan scope as a change request,

subject to the reviews and approvals outlined below. It will address the in-scope issues and

resubmit the deliverable. If the approving group provides additional feedback, Info Tech will

repeat the cycle, including scope determination, a maximum of one additional time unless the

original revisions are incorrectly applied. It is critical to the success of the work plan schedule

that all change control efforts be expedited to minimize impacts.

7.2.2 Change Control Process

Changes are processed via change controls, change orders, and contract modifications. A change

order describes the work product in question, the proposed change controls, and related impact to

scope, schedule, or budget. Note that Info Tech will perform no out-of-scope work without

approval. The following process is designed to streamline the review and approval process and

to expedite the completion of work that is determined to be in-scope.

The following steps are to be followed in managing a change request:

1. Info Tech will document any identified change in the applicable project management and

issue tracking tools. Some examples:

A) A change can come within the context of feedback from a deliverable or service.

B) A change can come from subject matter experts who identify a new requirement.

C) A change can come from a customer who experiences an issue with a deliverable

or service.

2. Info Tech will have leads responsible for reviewing the submitted change request and

determining if it is a change within the scope of the work plan or outside the scope of the

work plan. If it is a scope change, Info Tech will notify the PTF and request further

direction.

3. If it is determined that the scope change has an impact to budget and/or schedule, Info

Tech will perform an impact assessment and provide a change order for revision to the

work plan scope, budget, and/or schedule for PTF review and direction.


4. If the change order is approved, Info Tech will re-baseline the project with the agreed

upon changes and submit a contract modification. Note that multiple approved change

orders may be combined into one contract modification.

Figure 7-1. Change Control Process

7.3 Status Reporting

The Info Tech Project Manager will generate a monthly status report which includes:

• High Level Summary with Key Items Supporting Health Status

• Schedule Details

• Key Accomplishments, Summary Tasks, and Milestones this reporting period

• Key Summary Tasks and Milestones in the next period

• Principal Issues and Risks

7-4 Monitoring and Control

• Change Controls

• Design Tracker

• Development Tracker

The content and layout of this report will be similar to the monthly status report generated for

previous web-based AASHTOWare Project development projects. Info Tech will review and

discuss progress with the PTF during their weekly meetings as needed throughout the project.


8. Quality Management

8.1 Quality Assurance

Info Tech will perform quality assurance for the project throughout the day-to-day tasks required to

complete the approved work plan services and deliverables as described in Chapter 3. Work

Activities. This includes internal and external review processes.

8.2 Quality Control

Info Tech will perform quality control for the project throughout the day-to-day tasks required to

complete the approved work plan services and deliverables as described in Chapter 3. Work

Activities. This includes requirements traceability, adherence to standards, checklists, and the

rigors enforced by automated tools.

8.2.1 Review Gate Approval Procedure

Info Tech will submit review gate approval requests as defined in section 4.2 to the PTF for

approval per the Software Development & Maintenance Process Standard in the September 1,

2017 AASHTOWare Standards and Guidelines Notebook (as amended October 12, 2017). Info

Tech will use the applicable Review Gate Approval Request form included in the standard. Info

Tech will meet the review gate requirements defined in the Software Development &

Maintenance Process Standard except for where exceptions are requested (see Section 6.4

Exceptions to AASHTOWare Standards).

8.2.2 Major Deliverable Approval Procedure

As Info Tech completes major deliverables (see Table 4-2), Info Tech will post them to the

Contractor (Info Tech) SharePoint workspace and notify the PTF via e-mail. Info Tech will

request PTF approval or other direction within a set number of business days (see Chapter 4.

8-2 Quality Management

Schedule, Milestones, and Price). After each major deliverable is reviewed, the PTF will be

asked to either identify required revisions or accept it. Info Tech will revise the deliverable in

accordance with the revision process in place for the deliverable (e.g., change control process if

revisions are required). After the revisions have been completed, the deliverable will be re-

submitted to the PTF for acceptance, and the review timeline will restart for a maximum of one

additional review unless the original revisions are incorrectly applied. Review gate

documentation will reference any artifacts/deliverables that have already been approved.

8.2.3 Reviews and Assessments

Info Tech will participate and provide artifacts and deliverables for periodic Quality Assurance

annual meetings that may occur during the course of the project. These activities will be

performed outside of the work plan under the then-current MSE work plan.

8.3 Test Plan

One of the first major deliverables for this effort is a test plan, which Info Tech will deliver to the

PTF as per Table 4-2. See Section 6.1.2 Project Documentation for further details. The test plan

will encompass all SaaS software releases and will be updated throughout the project as needed.


9. Communication Management

Info Tech will follow similar processes and reporting for communication management as used on

previous web-based AASHTOWare Project development projects. Info Tech will develop a

Communication Plan early in the project and present it to the PTF for review and approval. The

focal point of the Communication Plan is the Communication Matrix, which is a table of

information that details the following: what information will be communicated, to whom, how

frequently (as needed, weekly, monthly, etc.), and by what means (formal report, e-mail

notification, etc.). Note that the identified lines of communication do not preclude

communication from occurring between any stakeholders where required.

Deliverables are included as part of the matrix, as they are a key point of communication. As the

needs of this effort change throughout the project, the matrix is updated. When the

Communication Plan is updated, the most recent version is distributed with the next monthly

status report.

9-2 Communication Management



10. Configuration Management and Repository

10.1 Configuration Management

The September 1, 2017 AASHTOWare Standards and Guidelines Notebook (as amended October

12, 2017) states that the purpose of Configuration Management is “to establish and maintain the

integrity of work products using configuration identification, configuration control, configuration

status accounting, and configuration audits.” For the project, configuration management will be

applied to the artifacts, deliverables, and work products (e.g. status reports).

Artifacts, deliverables, and work products delivered to the TRT/PTF for the Appendix A

functionality will be stored, managed, and controlled within a configuration management/version

control tool (Subversion). Similar numbering and naming conventions established for previous

web-based AASHTOWare Project development projects will be applied.

Amazon Web Services (AWS) CodeCommit is being used along with a Git-style repository for

storing and managing the SaaS code. The SaaS source code will not be delivered via CD. Direct

secure access is available through authorized read-only credentials to the entire code base.

10.2 Repository

Info Tech will store all artifacts, deliverables, and work products that require TRT review and

approval in the AASHTO-designated SharePoint workspace. This includes meeting agendas,

minutes, deliverables, change controls, status reports, and any other reference documents

necessary during the course of the project. In some cases, artifacts may also be posted in another

SharePoint workspace for review (e.g., Contractor (Info Tech)).

10-2 Configuration Management and Repository



11. Risk Management

Info Tech will follow similar processes and reporting for risk management as used on previous

web-based AASHTOWare Project development projects. Info Tech will develop a risk register

and update it on a regular basis as part of the monthly status reporting process. When the Risk

Register is updated, the most recent version is distributed with the next monthly status report.

11-2 Risk Management



12. Backup and Disaster Recovery

12.1 Backup Plan

The artifacts, deliverables, and work products created for the project will be administered by the

Backup Plan documented in the then-current MSE.

12.2 Disaster Recovery Plan

The artifacts, deliverables, and work products created for the project will be administered by the

Disaster Recovery Plan documented in the then-current MSE.

12-2 Backup and Disaster Recovery



13. Revision History

The following table provides a revision history for this work plan.

Version Date Name Description

1.0 Document Version 1.0 First version provided to the PTF.

2.0 Document Version 2.0 Second version provided to the PTF. Changes from the 4/4/2018 PTF weekly meeting.

3.0 Document Version 3.0 Third version provided to the PTF. Added 2 new Dashboard themes.

4.0 5.0

Table 13-1. Revision History

13-2 Revision History


AASHTOWare Project Data Analytics Development and Production Releases Work Plan A-1

Appendix A. AASHTOWare Project Data Analytics Development and Production Releases Work Plan Scope

The following tables list the SaaS and web-based themes and features established as part of the

AASHTOWare Project Decision Support December 2017 Functionality Review Summit. The

themes and their features are listed in priority order from the Summit.

SaaS Theme SaaS Feature

New Theme: Construction Dashboard #1 TBD

New Theme: Construction Dashboard #2 TBD

Line Item Profiles To see reference prices in addition to estimate and bidder's prices so that I can see how the bid prices differ from a reference price

Line Item Profiles The quantity change amount that would result in a different low bidder so that I can determine if the deviation on the item warrants additional investigation

Line Item Profiles

To specify the deviation type be the unweighted unit price percentage difference so that I can find out which items to focus my analysis on independent of their impact on the specific proposal

Line Item Profiles Items that are historical outliers highlighted so that I can find out which items to focus on based on if the deviation is not common for the item

Line Item Profiles

A comparison of each vendor's bids at the proposal section level so that I can find out what the results would be grouped specific to the organization of the proposal

A-2 Appendix A. AASHTOWare Project Data Analytics Development and Production Releases Work Plan Scope


Line Item Profiles To specify a user defined deviation so that I can find out which items to focus my analysis on based on a different calculation

Bid Evaluation Analysis

To specify the deviation type be the unweighted unit price deviation so that I can find out how the difference varies relative to the item rather than the proposal


To specify not to collapse item information across spec years so that items that differ between spec years are not compared together


To interactively obtain additional key information so that I can find out more contextual information to assist in data analysis


The Generated Price, Lower Bound, Upper Bound, and Bid History Rating from the Bid/Estimate Review model so that I can find out the reasonable price and range

Bid Estimate Review

To compare the low bidder's and estimated prices on a proposal to bids on a historical generated price so that I can find out if the low bid and estimated prices are outside of the norm established by the historical bid prices

Bid Estimate Review

To compare a vendor's bid prices to a historical generated price from just their bids so that I can find out if their price is outside of the norm established by their historical bid prices

Bid Estimate Review

To compare all bidder's and estimated prices on a proposal to a historical generated bid price so that I can find out if the bid and estimated prices are outside of the norm established by the historical bid prices

Bid Estimate Review

To select which historical data and regression settings to use so that I can find out if the bid and estimated prices are outside of the norm established by the historical bid prices

Bid Estimate Review

To compare the estimated prices on a proposal to a historical generated price based on the estimate so that I can find out if the estimated price is outside of the norm established by the historical estimated price

Bid Estimate Review To see the proposal items and generated prices with confidence ranges for all bidders so that I can find out how each proposal item ranged historically

Bid Estimate Review

To compare the estimated prices on a proposal to a historical generated price based on the winning bidder so that I can find out if the estimated price is outside of the norm established by the historical award price

Bid Estimate Review The bidder's total compared to the estimate so that I can find out how much they differ

Bid Estimate Review The item’s generated prices with confidence ranges for low bidder and estimate so that I can find out how the bid and estimate fit with the historical range

Bid Estimate Review A summary of bidder's price comparison to the generated price for the proposal so that I can find out the magnitude of the differences overall



Bid Estimate Review To review the bidders and how they ranked so that I can find out who was potentially trying to get the award and how close they were

Bid Estimate Review

The items with the awarded range and set of generated prices with confidence ranges for a single bidder so that I can find out what their historical range was and how their award range compared

Bid Estimate Review

The out of range proposal prices compared to the generated price with confidence ranges so that I can find out the magnitude of the differences for the out of range items

Bid Estimate Review To see just the key items so that I can focus my review on the most important items

Bid Estimate Review Basic descriptive information about the proposal so that I can find out what the proposal is for

Bid Estimate Review Basic location information about the proposal so that I can find out where the proposal is

Quantity Variance - Letting

To find out if the low bidder changes when a historically based percent quantity change is applied so that I can determine if the proposal quantity needs more scrutiny.

Quantity Variance - Letting

To specify an alternate quantity for a bid item so that I can see if the low bidder changes and determine if the proposal quantity needs more scrutiny.

Item Price Analysis The results to be based on the top items by total dollars so that I can find out about items that make up the most of the dollars spent

Item Price Analysis The results to be based on the top items by quantity so that I can find out about the items with the most amount used

Item Price Analysis The results to be based on the top items by frequency so that I can find out about the items with the most occurrences

Item Price Analysis To specify the area definition to use so that I can find out how the information is split/grouped by the area set I am using for analysis

Item Price Analysis The price of the item vs quantity by area so that I can find out how the price changes with quantity across areas

Item Price Analysis The price of the item vs quantity so that I can find out how the price changes with quantity

Item Price Analysis The price of the item vs date by area so that I can find out how price changes over time across areas

Item Price Analysis The price of the item vs date so that I can find out how price changes over time

Item Price Analysis The distribution of the occurrences across price levels by area so that I can find out what price levels occur more/less often across areas



Item Price Analysis The distribution of the occurrences across price levels so that I can find out what price levels occur more/less often

Item Price Analysis Univariate results about the item's average price by area so that I can find out about the statistics behind the average price across areas

Item Price Analysis Univariate results about the item's average price so that I can find out about the statistics behind the average price

Item Price Analysis To view the results by specified time period by area so that I can find out how the results changed across years and across areas

Item Price Analysis To view the results by specified time period so that I can find out how the results changed across time

Item Price Analysis The item's awarded value and next two bidders on each contract so that I can find out if the awarded bidder’s price is in line with the next two low bidders.

Item Price Analysis To specify not to collapse items information across spec year to have more history available for ranking

Item Price Analysis To exclude statistical outliers for the analysis so that I can find out the information about the items better representing the overall trends

Item Price Analysis To combine similar items together using common units for analysis so that I can get results based on a larger set of data

Item Price Analysis To limit the number of bidders used for analysis by bid rank so that I get results based on the bidders with the best overall total bid amount

Item Price Analysis To specify the level for the token bids (ex: penny bids) that occur with the item so that they are removed from the statistical calculations

Item Price Analysis To interactively obtain additional key information so that I can find out more contextual information to assist in data analysis

New Theme: Compare Prices of Similar Items Within Letting and Recent History TBD

Item Statistics Map To specify the area definition to use so that I can find out how the information is split/grouped by the area set I am using for analysis

Item Statistics Map The set of items to be included based on total dollars so that I can find out about items that make up the most of the dollars spent

Item Statistics Map The set of items to be included based on total quantity so that I can find out information about the items with the most amount used

Item Statistics Map The set of items to be included based on frequency so that I can find out information about the items with the most occurrences



Item Statistics Map The item by total dollars by area so that I can find out how the dollars awarded compares between areas

Item Statistics Map The item quantity by area so that I can find out how the quantity used compare between areas

Item Statistics Map The item frequency by area so that I can find out how the frequency compares between areas

Item Statistics Map To view the results by time period so that I can find out how the price changes over time

Item Statistics Map To display the results in a standard mapping format so that I can see the results geographically

Item Statistics Map The item average price by area so that I can find out how the price compares between areas

Item Statistics Map The item's awarded value on each contract so that I can find out information about attributes that could impact the price

Item Statistics Map To interactively display and drill down additional information and parameters so that I can find out additional underlying detail information

Item Statistics Map To specify not to collapse items information across spec year to have more history available for ranking

Market Area Definition

To control the factors that cause areas to be grouped so that I can explore the impact of weighting different factors with the formation of the areas


To review the grouping results as the areas are formed so that I can see the results of the grouping analysis at each phase


To review the new areas as the areas are formed so that I can see the results along the way and have a chance to change the inputs based on what I see


The final results so that I can verify that the grouping is what I want to use for analysis


To review the vendor activity of each area as the areas are being evaluated for grouping so that I can assist the grouping based on vendor activity


Use another boundary type instead of county/district so that I can have more flexibility in defining the market


A recommendation of the optimal grouping to use based on the data provided so that I can more quickly determine the market area to use


The overall vendor activity by county so that I can get a general idea of the activity before grouping starts




To control how much areas grow so that I can manage how fast the areas grow and are re-evaluated based on the newly grouped area's activity

Market Shares To specify the area definition to use so that I can find out how the information is split/grouped by the area set I am using for analysis

Market Shares To specify the vendor group definition to use so that I can find out results that are reflective of overall ownership

Market Shares

The amount subcontracted from the prime transferred to the subcontractor for the purposes of determining market share so that I can find out results based on who the work really goes to

Market Shares The vendors’ dynamic market percent over time by market area so that I can find out how much of the market they had at each point in time for each area

Market Shares The vendors’ dynamic market percent over time so that I can find out how much of the market they had at each point in time

Market Shares The as built quantities used instead of bid quantities so that I can find out a more accurate reflection of the market share

Market Shares The vendors’ total market share and contracts worked by market area so that I can find out how much of each area they have in terms of value and number

Market Shares The vendors’ total market share and contracts worked so that I can find out how much statewide they have in terms of value and number

Market Shares To specify the set of vendors so that I can find out the results by the selected vendors

Market Shares

The vendors’ total contract work and adjustments based on suppliers so that I can find out how much they had overall and the impact of supplier work on that total

Market Shares The Herfindahl-Hirschman Index for the vendors so that I can find out the measure of market concentration

Vendor Competition Analysis

A competition matrix with total bids and total wins head-to-head for each vendor so that I can find out how successful a set of vendors are when bidding against each other


The results to be based on the top bid winners so that I can find out about the vendors that win the most bids


The results to be based on the most active bidders so that I can find out about the vendors that are the most active bidders


The results to be based on the top dollar winners so that I can find out about the vendors that win the most money

Vendor Competition Analysis To specify the set of bidders so that I can compare specific vendors




To interactively obtain additional information including locations so that I can find out more contextual information


The high individual vendor win percentages highlighted so that I can find out the key vendors easier


The high head-to-head win percentages highlighted so that I can find out the key matchups easier

Vendor Activity Map The locations where the vendors bid and won so that I can find out where their awarded contracts are

Vendor Activity Map The locations where the vendors bid and lost so that I can find out where their losses are

Vendor Activity Map The locations where the vendors were subcontractors after losing the bid so that I can find out where they bid first, and then do subcontract work

Vendor Activity Map The locations where the vendors were just a subcontractor so that I can find out where they do their subcontract work

Vendor Activity Map The locations of their facilities so that I can find out where their plants are relative to their activity

Vendor Activity Map The vendor's location by address so that I can find out where they are located relative to their activity

Vendor Activity Map The results displayed in a standard mapping format so that I can see the results geographically

Vendor Activity Map The locations that could not be plotted due to inconsistent coordinates so that I can find out what data needs to be corrected

Vendor Activity Map To change which layers show on the map so that I can find out where the activity is relative to the elements of the layer(s)

Vendor Activity Map To identify which boundaries to show on the map so that I can find out where the activity is relative to the boundary

Vendor Activity Map To interactively obtain additional key information so that I can find out more contextual information

Vendor Activity Map The types of sources/facilities distinguished so that I can find out more detail information about source/facilities

Vendor Activity Map Activity from other vendors so that I can find out how similar/complementary the activity patterns are between the vendors

Vendor Activity Map Facilities from other vendors so that I can find out where their plants are relative to each vendor's activity



Vendor Activity Map The display of facilities limited to within a specified radius from the vendor's activity so that I can find out which facilities are relative to the vendor's activity

Vendor Activity Map The sources/facilities of specified types to be displayed so that I can find out about just the facilities that are relevant

Vendor Activity Map Activity to be shown for the controlling project instead of all projects so that I can focus just on the proposal activity

Work Location Map To identify which boundaries to show on the map so that I can find out where the activity is relative to the boundary

Work Location Map Activity to be shown for the controlling project instead of all projects so that I can focus just on the proposal activity

Work Location Map The display of facilities limited to within a specified radius from the vendor's activity so that I can find out where facilities are relative to each vendor's activity

Work Location Map To view entire state or just area of activity so that I can focus on specific results

Work Location Map To change which layers show on the map so that I can find out where the activity is relative to the elements of the layer(s)

Work Location Map The locations where vendors bid and won so that I can find out where their awarded contracts are

Work Location Map The locations of vendors’ facilities so that I can find out where their plants are relative to their activity

Work Location Map The locations that could not be plotted due to inconsistent coordinates so that I can find out what data needs to be corrected

Work Location Map To limit which types of facilities are displayed so that I can find out about just the facilities that are relevant

New Theme: Unbalanced Bidding Analysis TBD

Award Maps To specify the area definition to use so that I can find out how the information is split/grouped by the area set I am using for analysis

Award Maps Maps by letting so that I can find out what was done for each letting

Award Maps To view the results by time period so that I can find out how the awarded amount changes over time

Award Maps To view entire state or just area of activity so that I can focus on specific results

Award Maps The map with totals grouped into ranges so that I can find out what the difference is between areas easier since there will be fewer values



Award Maps The dollars of awarded contracts in each area so that I can find out how much money went to each area

Award Maps The number of awarded contracts in each area so that I can find out how many contracts went to each area

Award Maps The number of awarded projects in each area so that I can find out how many projects went to each area

Award Maps To interactively obtain additional key information so that I can find out more contextual information to assist in data analysis

Award Maps The project dollars of awarded proposals in each area so that I can find out how much money went to each area

Award Maps To display the results in a standard mapping format so that I can see the results geographically

Cost Variance Profiles

To integrate the cost variance with the quantity variance analysis so that I can better understand the differences from as bid vs as built


The total cost over/under so that I can find out the impact of the differences on the contract


The differences by contract for each item so that I can find out which contracts and items to focus on for further analysis


To specify the deviation level that identifies the key items so that I can find out which items to focus my analysis on


The results summarized by area so that I can find out how the cost differences differed across areas


The results summarized by vendor so that I can find out how the cost differences differed across vendors


The differences by contract for each item including the estimate so that I can find out which contracts and items to focus on for further analysis taking the estimate into consideration


To compare the actual costs vs each bidder's bid so that I can find out if there would have been a different low bidder


The results summarized by proposal work type so that I can find out which types of work are impacted most


The results based on the top items by frequency so that I can find out about the items with the most occurrences


The results based on the top items by total variance so that I can find out about the items with the most variance




The results based on the top items by total dollars so that I can find out about items that make up the most of the dollars spent


The results based on the top items by quantity so that I can find out about the items with the most amount used


Descriptive and location information about each contract so that I can find out attributes of the contract that may have contributed to the significances of the quantity differences


The results summarized by staff so that I can find out how the cost differences differed across staff

Quantity Variance An overall summary of the results on a contract so that I can find out what the net impact would have been

Quantity Variance The differences by quantity so that I can find out how significant the differences were as quantity changes

Quantity Variance To specify the deviation level that identifies the key items so that I can find out which items to focus my analysis on

Quantity Variance The results summarized by area so that I can find out how the quantity differences differed across areas

Quantity Variance The results summarized by vendor so that I can find out how the quantity differences differed across vendors

Quantity Variance The differences by contract for each item so that I can find out how each contract was impacted

Quantity Variance The results summarized by proposal work type so that I can find out which types of work are impacted most

Quantity Variance The results based on the top items by frequency so that I can find out about the items with the most occurrences

Quantity Variance The results based on the top items by total variance so that I can find out about the items with the most variance

Quantity Variance The results based on the top items by total dollars so that I can find out about items that make up the most of the dollars spent

Quantity Variance The results based on the top items by quantity so that I can find out about items that make up the most of the dollars spent

Quantity Variance

To provide descriptive and location information about each contract so that I can find out attributes of the contract that may have contributed to the significances of the quantity differences

Quantity Variance The results summarized by staff so that I can find out how the quantity differences differed across staff



Historical Statistics To specify the area definition to use so that I can find out how the information is split/grouped by the area set I am using for analysis

Historical Statistics To specify date range for the contracts so that I can find out information for the specific time period I'm interested in

Historical Statistics To specify the number of major vendors to include so that I can find out information about just the top vendors

Historical Statistics To specify the number of major contract work types to include so that I can find out information about just the top work types

Historical Statistics To specify the number of major subcontract types to include so that I can find out information about just the top subcontract types

Historical Statistics The award totals by area, work type, and vendor so that I can find out the level work across areas, top work types, and top vendors

Historical Statistics

The subcontractor totals by area, work type, and vendor so that I can find out the level of subcontract work across areas, top subcontract types, and top subcontractors


The supplier totals work type and vendor so that I can find out the level of supplier participation across areas, top subcontract types, and top subcontractors

Historical Statistics The total bids by vendor so that I can find out the overall level of activity of top bidders

Historical Statistics The number of bids received by area so that I can find out how each area compares with respect to the number of bidders

Historical Statistics The overall totals by area so that I can find out the level of work in the area


The vendor's bids vs how many other bids received on contracts where they bid by area so that I can find out the level of a bidder's bidding activity vs number of other bidders in the area

Historical Statistics The vendor subcontracts and subcontract dollars by area so that I can find out the level of a subcontractor's work in the area relative to its total

Historical Statistics The vendor supplier and supplier dollars by area so that I can find out the level of a supplier's participation in the area relative to its total

Historical Statistics The vendor awarded contracts and awarded dollars by area so that I can find out the level of a vendor's work in the area relative to its total


The vendor's total bids by area and how much of the area's total contracts they bid so that I can find out the level of a bidder's bidding activity in the area relative to its total



Historical Statistics The percent of awards within range of the estimate by area so that I can find out how awards vs estimates compare across areas

Historical Statistics To interactively display and drill down additional information on summaries so that I can find out additional underlying detail information

Historical Statistics The percent of a vendor's awards within range of the estimate by area so that I can find out how a vendor awards vs estimates compares across areas

Historical Statistics The percent of a vendor's awarded dollars within range of the estimate by area so that I can find out how a vendor awards vs estimates compares across areas

Historical Statistics The overall totals by area so that I can find out the overall level of work


The percent of dollars awarded within range of the estimate by area so that I can find out how much is awarded within range of the estimate compares across areas

New Theme: Compare Contracts TBD

New Theme: Trends of Unbalanced Items TBD

Bridge Costs To specify the date range for the proposals so that I can find out the results for the time period I'm interested in

Bridge Costs

The bridge cost per square foot within work classifications so that I can find out the average cost per square foot for the different types of bridge work along with the how the projects differed in costs

Table A-1. Work Plan SaaS Scope and Priority

Web-Based Theme Web-Based Feature

Vendor Group Definition

The results to be based on multiple criteria (vendor affiliations, vendor officers) so that I can find out how the vendors group when combining grouping methods


The results to be based on other vendor attributes so that I can find out how the vendors group when using other attributes of the vendors


A set of grouped vendors so that I can use the set in other analyses to find out how the vendor patterns are impacted


To start with an existing vendor grouping so that I can find out how the groups change with new information




To manually reassign vendors and vendor groups so that I can find out how that impacts the analyses

Bid History Profile To select a group of items and/or contracts that I would run my bid history profile over

Pricing Profile To select a group of items and/or contracts that I would run my pricing profile over

Proposal Filter/Selection

To select a set of proposals so that I can run different analyses against the same set of proposals


The proposals that are selected so I can see validate my selection criteria resulted in the expected set of proposals


The projects that are selected so I can see which projects were included based on the proposals selected


How many proposals were selected by area so I can see how the number compared across area


How many proposals were selected by date so I can see how the number compared across time


How many proposals by vendor involvement as a planholder, bidder, or subcontractor so that I can see vendor activity across the set of proposals

Item Rank Analysis The results based on the top items by frequency so that I can find out about the items with the most occurrences

Item Rank Analysis The results based on the top items by total dollars so that I can find out about items that make up the most of the dollars spent

Item Rank Analysis The results based on the top items by quantity so that I can find out about the items with the most amount used

Item Rank Analysis

The ranking of items within item groups by total dollars so that I can find out which are the most important items in the group and which groups are the most important by dollars spent

Item Rank Analysis The ranking of item classifications by total dollars so that I can find out which are the most important item classifications by item dollars spent

Item Rank Analysis To specify not to collapse items information across spec year to have more history available for ranking



Item Rank Analysis To specify the type of item reference attribute to group by so that I can control how the items are grouped

Item Rank Analysis An average historical price to be stored with the item reference information so that I can use it with other analysis

Item Rank Analysis To specify a threshold (dollars,quantity, frequency) for which items are included so that I can focus just on the top items

Item Rank Analysis The items that have not been used so that I do not spend time on items that are not important for further analysis

Cost Data Book Bridge Cost Per Square Foot/Meter

Vendor Profile Report To specify the vendor so that I can find out information for that vendor

Vendor Profile Report

To specify the date range so that I can find out information for the time period I am interested in

Vendor Profile Report The dollars they were awarded so that I can find out how big they are


The vendors they subcontracted work to so that I can find out who their subs are


The vendors they subcontracted work from so that I can find out who they are subs for


The number of contracts they were awarded so that I can find out how successful they are as a bidder


To filter contracts by contract attributes so that I can find out information about a specific subset of contracts


The number of contracts they bid so that I can find out how active they are as bidder


The number of bids they quoted so that I can find out how active and successful they are as a subcontract quoter


The results by vendor work codes (CRL) so that I can find out validate the information against other tracked information


The number of contracts where they bid, lost, and then received a subcontract on so that I can find out the level of subcontract work on contracts they bid




The number of subcontracts they had where they did not bid so that I can find out the level of subcontract work not bid on


To interactively obtain additional information so that I can find out more contextual information to assist in data analysis


Information about vendors facilities so that I can find out what facilities they have available


The types of work they were awarded so that I can find out what type of work they do


The areas where they had awarded contracts so that I can find out what areas they work in


A map for any vendor activity so that I can find out the geographic areas where the vendor is active (feature will be satisfied through Vendor Activity Map)


The awarded work type within each area so that I can find out a breakdown of awarded work type within each area


The awarded areas within each work type so that I can find out what areas they do each type of work

Contract Profile Report

To interactively obtain additional information so that I can find out more contextual information to assist in data analysis (this feature will be satisfied through the other analysis features involving contract information in the SaaS analysis service)


Proposal descriptive and location information so that I can find out general information about the proposal


Project descriptive and location information so that I can find out general information about the project

Contract Profile Report The key proposal/contract dates so that I can find out key date information


The estimate and vendor bid totals and status so that I can find out bid result summary information


Non-bidding planholders so that I can find out general information about nonbidding planholders


Subcontract and supplier information so that I can find out general information about subcontractors and suppliers




DBE commitment information so that I can find out general information about DBE commitments


Payroll summary information so that I can find out general information about the payroll

Contract Profile Report Change order summary so that I can find out general change order information


Non-construction cost information so that I can find out general information about non-construction costs


Current and final construction costs so that I can find out general information about construction costs


Estimates of cost so that I can find out general information about estimated costs


A summary of material usage, exceptions, and facilities so that I can find out general information about materials

Contract Profile Report Generate information for all proposals in a proposal selection list

Table A-2. Work Plan Web-Based Scope and Priority


Info Tech has outlined the initial production delivery for the above themes in the following Gantt

chart. Info Tech will work with the TRT/PTF to revise the theme delivery order as needed

throughout the project.

Table A-3. Initial Production Delivery Timeline

AASHTOWare Project Data Analytics Development and Production Releases Work Plan B-1

Appendix B. Contractor Personnel

The following provides biographies for Info Tech personnel referenced in Chapter 5.

Organization and Staffing. Key personnel biographies are provided for the staff listed in Table

5-2 and sample biographies are provided for the supporting roles described in Table 5-1.

B.1 Info Tech Key Personnel Biographies

Haval Aloussi: Technical Lead/Developer

Haval Aloussi is a Senior Lead Software Developer and has worked at Info Tech for over fifteen

years. Mr. Aloussi joined the AASHTOWare Project development team in 2005, and he now

works on the AASHTOWare Project Data Analytics projects.

Haval has been fortunate to work in multiple departments at Info Tech. He began his Info Tech

career by providing customer support for estimation-related products, including the

AASHTOWare Project BAMS/DSS software. Later, he moved to services, where he assisted

with on-site installations and training for the AASHTOWare Project BAMS/DSS software.

Working in these various areas prior to moving to development provided Haval with a unique

perspective and experience that he utilizes on a daily basis.

Mr. Aloussi holds a bachelor's degree in Computer Science from the University of Central

Florida.

Ian Baldwin: Business Manager

Mr. Baldwin has worked for Info Tech for over fifteen years in various roles and is currently a

Sr. Manager on the AASHTOWare Project development team. Initially, he worked for several

years on the FieldSuite team in the development, project management, and implementation of

various products, mainly AASHTOWare Project FieldManager™. For the past several years, he

has spent working with the web-based AASHTOWare Project development team as a Business

Manager. In this capacity, he has worked extensively with the application and various user

B-2 Appendix B: Contractor Personnel

groups and the PTF, playing an active role in requirements management, analysis, design,

testing, and development methodologies and processes. Most recently he continues his role of

Business Manager specifically on AASHTOWare Project Data Analytics as well as global

aspects with focus on the user interface and application documentation.

Mr. Baldwin holds a Civil Engineering degree from Vanderbilt University. He is certified as a

Project Management Professional (PMP) by the Project Management Institute and has a master's

certificate in Project Management from The George Washington University School of Business

in Washington, D.C.

Kateryna Bondareva: Test Coordinator

Kateryna Bondareva serves as a Senior Business Analyst on Info Tech’s AASHTO Web

Development team.

Prior to joining Info Tech, Ms. Bondareva worked for the Aurora Financial Systems Holdings,

where she served in capacity of Quality Assurance Engineer/Business Analyst. There, she

performed business system analysis, system testing, and quality assurance, working closely with

development team through the software development life cycle. She has expertise in designing

test cases, performing integration and regression testing, and gathering requirements.

Ms. Bondareva holds a Ph.D. in Computer Science from the Donetsk National Technical

University. Her scientific area of interest is parallel modeling and simulation of complex

dynamic systems.

Dan Hay: Technical Lead/Developer

Daniel Hay is a Lead Software Developer and has worked with Info Tech for over twenty-three

years in various programming and development roles. At different times, he has been

responsible for requirements analysis, systems analysis and design, development, and unit and

acceptance testing. Mr. Hay has done extensive work with the various incarnations of the

AASHTOWare Project software over the years, beginning with the creation of the client/server

versions of PES, LAS, AASHTOWare Project Construction Administration (CAS), and

AASHTOWare Project Cost Estimation (CES), and continuing with the development of the web-

based suite. As a member of that team for over eight years, Mr. Hay contributed to the

development of the business and report layers, as well as to team leadership and infrastructure

development. Mr. Hay has also spent several years working on mobile applications and cloud-

based services, and he is most recently contributing to the AASHTOWare Project Data Analytics

projects.

Mr. Hay holds a Master of Engineering degree in Computer Engineering from the University of

Florida.

Randy Lawton: Business Manager

Randy Lawton is a Senior Manager on Info Tech’s AASHTOWare Project development

team. He has significant software development and business expertise on most AASHTOWare


Project products. He has worked on the web-based AASHTOWare Project software since 2004.

His primary areas of business expertise are data analytics, preconstruction, and estimation. He

also has significant experience in web user interface design.

Mr. Lawton handles a variety of tasks, including business process analysis, data analytics design,

and user interface analysis and design. Mr. Lawton works closely with user and engineering

teams throughout the software lifecycle to help bring together and balance solutions that work

best for all.

Mr. Lawton began work at Info Tech in 1989 to help customize and test agency-specific versions

of the mainframe BAMS/DSS software. He has been involved in all phases of the various

system rewrites and upgrades of the data analytics and estimation software. Mr. Lawton’s

primary analytical development experience has been with SAS. He has also worked with several

supporting databases and languages for the mainframe, client/server, and web-based platforms.

Prior to joining Info Tech, Mr. Lawton worked for the Center for Instructional Research and

Computing Activities at the University of Florida as a laboratory supervisor.

He holds a bachelor’s degree in Computer Science from the University of Florida.

Elizabeth Rodgers: Project Manager

Elizabeth Rodgers has been a PMP certified Project Manager since 2005 and has been working

as a Senior Project Manager with Info Tech Client Services for the last seven years. In this

capacity, Ms. Rodgers leads Info Tech’s efforts supporting transportation agency work plan

deliverables and services related to the analysis and implementation of the AASHTOWare

Project suite of products. Ms. Rodgers manages schedules, scope, budgets, issue resolution plans,

risk mitigation plans, and customer satisfaction. She coordinates communication between

customers, subject matter experts, technical resources, and project stakeholders. Ms. Rodgers

works closely with customer Project Managers and resources to ensure clear communication,

timely completion of tasks, and removal/resolution of project roadblocks.

Ms. Rodgers worked on various analysis, implementation, and support projects for the

transportation agencies in Connecticut, Georgia, Indiana, Kentucky, Louisiana, Maryland,

Minnesota, New York, Nevada, North Carolina, Nova Scotia, Oklahoma, Oregon, Virginia,

Washington D.C., and Wisconsin, as well as Federal Lands Highway and the Philippines

Department of Public Works and Highways. Her roles within these projects varied from

working as a Senior Project Manager, Senior Systems Analyst, and Programmer/Analyst. Ms.

Rodgers performed analysis of business processes, data flows in automated and non-automated

environments, data conversions, data mapping, reports analysis, hardware and system software

analysis, training analysis and implementation project planning and management. She wrote

interfaces for state agencies to facilitate data flow between the AASHTOWare Project

environment and external systems. These projects required the ability to interview clients, and

have a thorough understanding of government regulations, civil rights and all aspects of

automated systems, including networks, hardware, client/server, internet, computer training and

operating systems.


Ms. Rodgers worked for Sum Total Systems as a Senior Project Manager where she managed a

portfolio of twenty clients ranging from ASP BPO (full service business process offering),

Premise (behind customer firewall), and hosted SaaS customers. She successfully developed and

deployed virtual team networks which incorporated resources from customer support, client

services, and development to provide key customer satisfaction. This virtual team model was

adopted company wide. Ms. Rodgers successfully fast-tracked two implementations as rapid

deployment of TotalPerformance modules and completed the implementations in seven and

twelve weeks respectively.

She holds a Bachelor of Science degree in Agriculture, and a Master of Science in Decision and

Information Sciences with a focus on statistical analysis from University of Florida.

B.2 Info Tech Supporting Personnel Biographies

Jim McClave: Co-CEO

James T. McClave, Ph.D. serves as the Co-Chief Executive Officer of Info Tech, Inc. After

earning his Doctorate in Statistics at the University of Florida in 1971, Dr. McClave founded

Info Tech in 1977 with the primary mission of applying statistical principles to real-world issues

and problems.

He worked on a U.S. Department of Justice grant as a consultant to the Florida Attorney General,

investigating the use of statistical methods for detecting illegal collusion. Dr. McClave began his

academic career at the University of Florida, where he spent 20 years, serving as an Assistant

and Associate Professor of Statistics and as an Associate Professor of Business and Economic

Statistics. He has authored numerous research articles and six leading textbooks in statistics. Dr.

McClave completed undergraduate training at Bucknell University in physics and post-graduate

work at the State University of New York at Buffalo.

Under Dr. McClave’s direction, Info Tech’s Consulting Division has continued to provide sound

statistical analyses to a wide diversity of applications and clients, including work for the

Environmental Protection Agency and the Medicare and Medicaid programs. Over his career,

Dr. McClave has consulted on hundreds of matters before both state and federal courts. He and

his Info Tech staff have applied sound statistical and econometric principles in cases ranging

from antitrust to employment discrimination, from calculation of business damages to

establishing pollution standards, and from business valuations to risk analyses.

Tom Rothrock: Co-CEO

Thomas Rothrock, Ph.D. is Info Tech's Co-CEO. For eleven years before joining Info Tech, Dr.

Rothrock was an economics professor at the Universities of Missouri, Wisconsin, and

Florida. Tom earned an undergraduate degree in Mathematics from the University of Missouri,

after which wrote computer programs while working as an engineering assistant for McDonnell

Aircraft in St. Louis, Missouri. He returned to the University of Missouri to earn a Ph.D. in

Economics, and there he pioneered research on computerized methods for market


analysis. Specializing in econometrics and mathematical economics, Dr. Rothrock joined Info

Tech in 1981 to work with Dr. Jim McClave on computerized bid monitoring.

From the beginning of the BAMS (Bid Analysis and Monitoring System) software in 1982, Tom

has been instrumental in its development. The American Association of State Highway and

Transportation Officials (AASHTO) went on to purchase the BAMS software in the mid-1980s,

and it is now known as the AASHTOWare Project software, having expanded to cover the entire

contract and construction cycle, from cost estimation to proposal preparation, letting bids,

construction and material management and data collection. Info Tech continues to work as

AASHTO's contractor for the software, and Tom and Info Tech have worked closely with the

states and AASHTO to oversee its evolution. He served as Senior Vice President of Info Tech's

System Division and as President of the company before moving into a Co-CEO role.

Russell W. Barron: Director

Russell Barron serves as the Director for all AASHTOWare Project Program and Project

Management at Info Tech. In this capacity, he has oversight for all AASHTOWare projects. Mr.

Barron is a subject matter expert in the construction management software development field and

a seasoned project manager, based on his years of large-scale implementations of AASHTOWare

Project applications with various state transportation agencies. Mr. Barron led the multi-year

implementation of several major construction management applications at the New York State

Department of Transportation. As an on-site project manager, he coordinated Info Tech and

agency resources to ensure a successful implementation. Mr. Barron then transitioned to Info

Tech’s AASHTO Web Development team and managed the beta testing for the AASHTOWare

Project Civil Rights & Labor (formerly Trns•port CRLMS) project. Mr. Barron also managed

the requirements gathering (URS) and system analysis (SRS/FDS) phases for the AASHTOWare

Project Construction & Materials and AASHTOWare Project Estimation development

efforts. Throughout his tenure, he has been a leader in the advancement of project management

and team facilitation skills at Info Tech.

Prior to joining Info Tech in 2002, Mr. Barron was the Applications Technology Coordinator for

the Missouri Department of Transportation. During his tenure, he managed a team that

implemented and developed software applications for the agency, including AASHTOWare

Project SiteManager. He also served as a Programmer Analyst, Automation Liaison Analyst,

Final Plans Reviewer, and Construction Inspector at the Missouri Department of Transportation.

Mr. Barron is certified as a Project Management Professional (PMP) by the Project Management

Institute and as a Certified ScrumMaster (CSM) by the Scrum Alliance. He holds a bachelor’s

degree in biology from the University of Missouri and a master's certificate in Project

Management from The George Washington University School of Business in Washington, D.C.

Jeff Lee Derrer: Subject Matter Expert

Jeff Lee Derrer has been with Info Tech since 2001 in various roles and is currently a Project

Manager/Senior Consultant. Prior to coming to Info Tech, Mr. Derrer worked at two state

agencies (North Carolina Department of Transportation 1991 – 2001, and Virginia Department


of Transportation 1987 – 1991). At both agencies, Mr. Derrer supervised a section that used the

AASHTOWare Project BAMS/DSS software to analyze and monitor bids on the highway

construction projects. During Mr. Derrer’s time at Info Tech, he has performed many

competition data analysis studies for U. S. highway agencies using the AASHTOWare Project

BAMS/DSS analysis tools.

Mr. Derrer’s additional qualifications include: Member of the AASHTO Trns•port User Group

Contract Monitoring Technical Adversary Group 1989 – 2001. Coordinator of this TAG 1992 –

1996. Member of the AASHTO BAMS Technical Review Team for the DSS 3 project 1992 –

1993. Member of the AASHTO BAMS TAG Coordinator Task Force during 1992. BAMS

User Group Chair during 1994 – 1995. Member of the AASHTO Trns•port Task Force from

December 1995 to September 2001. Chair of this task force 1999 – 2001. Chair of the

AASHTO Trns•port Technical Review Team for the Client/Server project 1997 –

2000. Participated as an instructor at Info Tech’s annual Collusion Detection Seminars since

1996.

Mr. Derrer holds a Civil Engineering degree from Virginia Polytechnic Institute and State

University. He is certified as a Project Management Professional (PMP) by the Project

Management Institute and has a master's certificate in Information Technology Project

Management from The George Washington University School of Business in Washington,

D.C. Mr. Derrer is also a licensed Professional Engineer and a Certified Public Manager.

Jim Ferguson: Director

Jim Ferguson serves as the Director for all AASHTOWare Project analysis and customer support

at Info Tech. In this capacity, he leads a team of business and customer support subject matter

experts performing support, business system analysis, implementations, system testing, and

quality assurance for all AASHTOWare Project product areas.

Prior to joining Info Tech, Mr. Ferguson served in several capacities at the Nebraska Department

of Roads (NDOR) over a span of 25 years. He started with engineering duties in the field,

transitioning to systems analysis and management duties. He most recently served as the

supervising Systems Administrator for all AASHTOWare Project applications licensed by

NDOR and other related applications, including Bid Express. Mr. Ferguson worked directly

with AASHTOWare software and users throughout the stages of agency implementation. He

has significant experience with AASHTOWare Project Civil Rights & Labor, AASHTOWare

Project SiteManager, AASHTOWare Project Preconstruction, PES, LAS, AASHTOWare

Project Expedite, and AASHTOWare Project SiteXchange software, with additional

experience using the AASHTOWare Project BAMS/DSS and AASHTOWare Project Cost

Estimation software. For more than 12 years, he represented NDOR as a member of the Project

Users Group (PUG, formerly the Trns•port Users Group, or TUG). Mr. Ferguson served on the

TUG board, becoming TUG chair in 2005. For three years, he served as AASHTOWare Project

Technical Advisory Group (TAG) coordinator for the Civil Rights & Labor Management

TAG. Mr. Ferguson represented NDOR on the Civil Rights & Labor and Construction &

Materials TRTs and related subgroups, collaborating with other agencies to define user

requirements for the web-based AASHTOWare Project software.


Mr. Ferguson helped align the business practices and technical architecture that surround the

estimation, bid letting, and construction processes of a highway contract at NDOR. He has

managed various projects and teams in key areas such as business analysis, implementation

planning, process improvement, end user training/support, system administration, and joint

application design.

Mr. Ferguson has a Bachelor of Science degree in Agronomy from the University of Nebraska –

Lincoln.

Paul Guidry, Jr.: Director/Scrum Master

Paul Guidry serves as the Director of AASHTOWare Project development and technical services

at Info Tech. He also serves as the Scrum Master on the web-based AASHTOWare Project

development team at Info Tech. Mr. Guidry manages and leads the day-to-day activities of the

development team and coordinates with program, project, and business managers to ensure the

development team is aligned with project delivery schedules. Mr. Guidry has been involved in

the development of AASHTO’s web-based AASHTOWare Project suite since 2007. During this

time, he has also served as the Project Manager/Scrum Master for the AASHTOWare Project

Preconstruction and AASHTOWare Project Civil Rights & Labor projects.

Prior to joining Info Tech in 2006, Mr. Guidry served in several roles at Intel Corporation over a

span of 17 years. He most recently served as an Applications Security Development Manager.

In that role, he led the worldwide development team through the design, construction,

deployment, and support of Intel’s enterprise access management system and Intel’s provisioning

system. He also served as a Program Manager for Intel’s home products group, where he

coordinated efforts across many internal teams to drive requirements, design, development, and

validation for software releases. Prior to that, as the Logistics Project Manager, he led design,

development, and worldwide deployment of Intel’s warehouse management system, shipping

system, and warehouse labeling system.

Mr. Guidry has successfully implemented systems using .Net, C#, C++ and SQL Server.

Mr. Guidry holds a Bachelor of Science degree in Computer Science from the University of

Florida, and a master’s degree in Manufacturing Engineering from North Carolina State

University.

Roy Johnstone: Subject Matter Expert

Roy Johnstone is a Senior Lead Analyst on Info Tech’s web-based AASHTOWare Project

development team. His focus is on the estimation, preconstruction, and contract monitoring

areas. He was the lead subject matter expert on the AASHTOWare Project Estimation

URS/SRS/FDS project, and he has been the lead estimation subject matter expert on subsequent

AASHTOWare Project development projects since AASHTOWare Project 3.0.

He performs a variety of tasks, including requirements analysis, systems analysis, design, testing,

data analysis, and documentation. Other tasks include QA/QC testing of new releases for


AASHTOWare Preconstruction and AASHTOWare Civil Rights & Labor software and assisting

in platform certification testing.

Mr. Johnstone has more than 20 years of experience in systems analysis and software

development and has been with Info Tech since 1985. He has been involved in numerous

AASHTOWare Project software development and implementation projects in the areas of

estimation, preconstruction, and contract monitoring.

He holds a master’s degree in Mathematical Science and a master’s degree in Business

Administration.

Lora Labonte: Test Coordinator

Lora Labonte serves as Quality Support Manager on Info Tech’s web-based AASHTOWare

Project development team. In this capacity, she coordinates the user acceptance-related (e.g.,

alpha, QA/QC) software testing for the web-based AASHTOWare Project development

projects. This includes creating test plans and coordinating resources and tools needed for the

testing. Ms. Labonte communicates with resource managers and project managers on a regular

basis to ensure testing is carried out in the most effective way possible.

Prior to joining the development team, Ms. Labonte worked in Info Tech’s accounting

department as an Accounting Specialist II for five years. There, Ms. Labonte developed a good

working knowledge of the company, which was a great benefit when she transitioned to

development.

Ms. Labonte holds a Bachelor of Science in Business Administration from the Warrington

College of Business at The University of Florida with a specialization in Decision and

Information Sciences.

April Cantrell: Subject Matter Expert

April Cantrell is a Lead Analyst on the AASHTOWare Project Support team with a primary

focus on AASHTOWare Project BAMS/DSS and AASHTOWare Project Cost Estimation

(CES). She has been with Info Tech for 20 years and had the opportunity to work with agencies

in multiple roles.

As a system analyst on the Client Services team, she provided services related to the analysis and

implementation of AASHTOWare Project BAMS/DSS and other AASHTOWare Project

software including installation, training, and development of agency-specific solutions and

reports. She also participated in market analysis activities and training.

As manager of the AASHTOWare Project Support team, she worked closely with the team and

agencies to resolve reported issues for all AASHTOWare Project products and identify

opportunities to improve the users’ experience with the software.

Ms. Cantrell holds a Bachelor of Science in Accounting from the University of Florida. Prior to

joining Info Tech, she worked for the Center for Instructional Research and Computing

Activities at the University of Florida designing and implementing an issue tracking system

Dear AASHTO Member Agencies: Subject: AASHTOWare Project Data Analytics Solicitation AASHTOWare Project Data Analytics™ software is a continuation of the cooperative development of web applications. This software will become part of the unified database of AASHTOWare Project™, eliminating interfaces and module based systems. In order to fully fund the development of this software, AASHTO is issuing a project solicitation. AASHTOWare has been an integral part of the Wisconsin Department of Transportation (WisDOT) process for many years and allows the opportunity to collaborate with other transportation agencies. This allows agencies to collectively combine their strengths and best business practices to create a viable software product of superior quality, far more powerful and effective than an individual agency could develop and deliver on their own. As a participant in the pilot for AASHTOWare Project Data Analytics, WisDOT worked first hand with other agencies to help set the base for the future, fully developed product. Already from the pilot we can see several benefits from this product:

The web-based application does not require the user to install a separate application. Data Analytics is user-friendly and intuitive. Bid analysis data is quick easy to retrieve. Additional data is obtained through the click of button rather than generating new analysis models

and reports. Product development staff are responsive to the agency needs.

WisDOT is very committed to AASHTO and fully supports the development and positive impact this software and web-based technology will bring to our agency. Web-based systems offer numerous, widely recognized, business and technical advantages that can dramatically lower costs due to reduced support and maintenance, lower requirements on the end user system and simplified architecture over client/server-based systems. I ask that all member agencies strongly consider financial support to the AASHTOWare Project Data Analytics software solicitation. The software resulting from your investment will allow all of us to put more of our transportation dollars into preserving our roads and less into administrative overhead. This is a tremendous benefit to member agencies and gives taxpayers more value for their money. Sincerely,

Scott J. Lawry, P.E. Bureau of Technical Services Director

David C. Castleberg, P.E. Design and Construction Technologies Supervisor

Division of Transportation System Development Bureau of Project Development Design and Construction Technologies Section 4822 Madison Yards Way, 4th Floor South P.O. Box 7916 Madison, WI 53705

Scott Walker, Governor Dave Ross, P.E., Secretary

wisconsindot.gov Telephone: 608-266-1631

FAX 608-266-8459 Email: [email protected]

May 29, 2018

AASHTOWare Project Data Analytics Software€¦ · AASHTOWare Project Data Analytics™ PAGE 2...

Documents

Transcript of AASHTOWare Project Data Analytics Software€¦ · AASHTOWare Project Data Analytics™ PAGE 2...