TEXAS DEPARTMENT OF TRANSPORTATION …ftp.dot.state.tx.us › pub › txdot-info › gsd › pdf › tss › tss...use by internal and external customers and allows for web-based updates,

TEXAS DEPARTMENT OF TRANSPORTATION

GENERAL SERVICES DIVISION

SPECIFICATION NO. TxDOT 920-56-77 DATED: NOVEMBER 2006

TEXAS PERMIT ROUTING OPTIMIZATION SYSTEM (TxPROS) SOLUTION

PUBLICATION

This specification is a product of the Texas Department of Transportation (TxDOT). It is the practice of TxDOT to support other entities by making this specification available through the National Institute of Governmental Purchasing (NIGP). This specification may not be sold for profit or monetary gain. If this specification is altered in any way, the header, and any and all references to TxDOT must be removed. TxDOT does not assume nor accept any liability when this specification is used in the procurement process by any other entity.

1. SCOPE: This solicitation is a Request for Offer (RFO) to provide services to develop and implement a software solution for use by TxDOT and its customers to automatically generate and evaluate alternate routes for oversize and overweight vehicles and loads being permitted to travel on Texas’ roadways. TxDOT is seeking a solution involving a system integration approach potentially using commercial off-the-shelf (COTS) software customization, or specifically developed software that takes advantage of the current TxDOT technical architecture and available roadway data. TxDOT desires a solution designed to reduce the time it takes to issue oversize/overweight (OS/OW) permits, allow the Motor Carrier Division (MCD) to meet increasing demand for services, increase the safety of the traveling public, improve TxDOT’s tracking of structures that affect OS/OW routing, and provide the ability to track the transport of OS/OW loads on Texas’ roadways. The proposed solution, which may include an optional hosting alternative, shall be web-based and designed to:

1.1. Provide a single, electronic, oversize/overweight mapping source that includes required parameters for OS/OW routing (i.e., vertical clearance, structure height, lane width, load ratings, one-way attributes, access roads, turn restrictions, at-grade railroad crossings, etc.) for use by internal and external customers and allows for web-based updates, due to construction and other restrictions, from designated location(s) in real time and on a daily basis.

1.2. Provide an automated routing system for OS/OW permits that is web-based; self-service; compatible with TxDOT’s base GIS architecture (Ref. Para 3.2.3); offers alternative routing solutions based on origin and destination points; evaluates routes based on obstructions, load parameters and other weighted data including Texas traffic laws and rules found in the Texas Transportation Code (TRC) and the Texas Administrative Code (TAC).

1.3. Integrate with TxDOT’s existing web-based Central Permitting System (CPS).

1.4. Be compatible with bridge/construction/pavement data, systems, and processes in TxDOT’s Bridge (BRG) and Construction (CST) Divisions for locating and tracking structures and roadway data as well as provide for additional data to be imported from non-TxDOT resources as needed for effective mapping and routing.

1.5. Provide a single source for the official permit map to eliminate the numerous changes each permit officer or customer must make to their individual paper maps each day. All permits will be issued using one electronic base map, eliminating the current paper maps (except for manual backup processing capability).

1.6. Enable automatic processing and delivery of qualified Internet permits (based on pre-determined vehicle envelope size) through CPS to replace the current process, which requires a permit officer to analyze or develop a route for each single-trip permit application.

1 - 19


1.7. Provide reporting capabilities for TxDOT divisions and districts to identify routes used to transport OS/OW loads, how often these routes are being used, sizes and weights of permitted vehicles traveling these routes, the effect of permit restrictions on other roadways, types of loads transported over which routes, and other reporting capabilities.

1.8. Provide growth ability that will allow MCD to provide quality customer service while experiencing increased permit demand without incurring significant backlog.

2. DEFINITIONS OF TERMS AND ACRONYMS

2.1. BRG: Bridge Division of TxDOT.

2.2. CCB: Change Control Board (comprised of Project Board members).

2.3. Computer Associates Erwin®: Data modeling tool used in the creation and maintenance of database models

2.4. COTS: Commercial Off-the-Shelf Software.

2.5. CPS: Central Permitting System (currently used by TxDOT).

2.6. CVISN: Commercial Vehicle Information Systems and Networks.

2.7. FHWA: Federal Highway Administration.

2.8. FTE: Full-time equivalent.

2.9. HCRS: Highway Condition Reporting System (currently used by TxDOT).

2.10. ISD: Information Services Division of TxDOT.

2.11. JAD: Joint Application Design (or development).

2.12. MCCS: Motor Carrier Credentialing System (currently used by TxDOT).

2.13. MCD: Motor Carrier Division (TxDOT).

2.14. MCO: Motor Carrier Operations (Section within MCD).

2.15. MCR: Motor Carrier Registration (TxDOT issued moving authority).

2.16. OS/OW: Oversize / Overweight.

2.17. PCR: Purchase Change Request.

2.18. PMP: Project Management Plan.

2.19. RFO: Request for Offer.

2.20. TAC: Texas Administrative Code.

2.21. TRC: Texas Transportation Code (contains Texas traffic laws).

2.22. TXPROS PMP: Texas Permit Routing Optimization System Project Management Plan.

3. APPLICABLE LAWS AND STANDARDS: The vendor shall provide service in accordance with all federal, state and local applicable laws, standards and regulations necessary to perform the services, including, but not limited to:

3.1. Considerations for routing of OS/OW permits shall be in compliance with Texas Transportation Code Chapters 622 to 623 and in accordance with Title 43 Part 1 Chapter 28 of the Texas Administrative Code all of which can be accessed through: www.txdot.gov.

3.2. ARCHITECTURE COMPLIANCE: The proposed solution shall comply with the TxDOT architecture documents which are posted along with this RFO. Proposed variations or exceptions to these documents shall be identified in the RFO response and will be subject to review and approval by ISD.

2 - 19


3.2.1. TxDOT Core Technology Architecture: Version 5.3.1, June 2006.

3.2.2. TxDOT Data Architecture: Version 3.0, February 2006.

3.2.3. TxDOT GIS: Technical Architecture: Version 1, August 2004.

3.2.4. TxDOT Graphic Data Standard: Version 1, August 2004.

3.2.5. TxDOT Configuration Management Standard: Version 1.4, September 2005

4. HISTORY OR BACKGROUND: TRC and TAC identify legal sizes and weights of transportation vehicles and require those that exceed these limitations, and that qualify, to apply for and be issued an OS/OW permit that has the most practical and safest route selected and assigned by MCD to ensure the safety of the traveling public and to protect the integrity of the highways and the bridges. In fiscal year 2004, MCD permit officers manually routed approximately 380,000 permitted loads using manually-updated paper maps. In fiscal year 2005 this number increased to over 410,000 and in fiscal year 2006 exceeded 450,000. This manual mapping and routing process needs to be replaced with an automated solution that is compatible with MCD’s existing CPS, provides the ability to assimilate the forecasted growth based on historical and current trends, and enables MCD to ensure mapping and routing consistency for internal and external customers.

Though several states claim to have automated routing, these systems in general would be better classified as route checking software rather than true automated routing. These systems generally pass or fail a user-selected route, but do not provide alternate routes upon failure of the user-selected route. Frequently, these systems require the permit officer or customer to manually select routes on a trial and error basis, without the benefit of initial or alternative automated route generation. The mapping programs associated with these systems also do not generally provide the level of data necessary to route OS/OW loads to intersections of state-maintained roadways and roads operated by other entities (i.e., city streets). While these systems may provide sufficient functionality to agencies that issue 100,000 or 200,000 permits annually, that type of system is not sufficient to provide for the issuance of over a half-million permits annually on over 80,000 centerline miles of state maintained (on-system) roadways and over 49,000 on and off system bridges, as is currently being done in Texas.

MCD does not currently have a method for tracking or reporting OS/OW permit data for use by other TxDOT divisions and districts. This data includes information about which routes OS/OW loads are using, how often these routes are used, sizes and weights of permitted vehicles traveling these routes, the impact of permit restrictions on surrounding roadways, which types of loads are using which routes, and other reporting capabilities that are yet to be defined.

Automated routing will allow TxDOT to better ensure the safety of the traveling public, protect the integrity of the highways and bridges, provide accurate and timely customer service, obtain data critical to making informed decisions, and more efficiently and effectively meet increasing permitting demands.

5. RESPONDENT QUALIFICATIONS: The respondent shall:

5.1. Be a company engaged in the business of providing information technology solutions with a minimum of three years experience within the last five years. Start-up businesses do not meet the requirements of this solicitation.

5.2. Have a minimum of one year within the last three years experience performing jobs that are similar in size and complexity, specifically utilizing an integrated web-based GIS solution.

5.3. Have a minimum of three years within the last five years experience with transportation industry related technical solutions.

5.4. Have a minimum of one year within the last three years experience working with federal, state or local governments.

3 - 19


5.5. Be in good financial standing, not in any form of bankruptcy, current in payment of all taxes and fees such as state franchise fees. TxDOT will request a copy of the respondent’s audited or un-audited financial statement (Ref. Para. 28.2.3.1).

6. RESPONDENT PERSONNEL QUALIFICATIONS: The staff proposed for this project shall have experience in providing the services requested in this RFO.

6.1. DESIGNATION OF KEY PROJECT PERSONNEL: All respondent key personnel assigned to this project shall be subject to TxDOT’s approval. As part of the negotiation process, TxDOT and the respondent shall agree to designate specific members of the project team considered to be essential to the services to be provided as key personnel. Specific conditions and requirements shall apply to key personnel.

6.2. KEY PERSONNEL – PROJECT MANAGER: The PM shall meet all of the following minimum skills and qualifications required to ensure that the tasks defined in this document can be successfully performed. PM skills and qualifications shall include, but not be limited to, the following:

6.2.1. Have a minimum of three years within the last five years work experience in all of the following:

6.2.1.1. Analyzing and managing large software development or integration projects.

6.2.1.2. Providing project management services.

6.2.1.3. Implementing enterprise level IT solutions.

6.2.1.4. Using industry-accepted software development methodologies and standards.

6.2.1.5. Analyzing business processes and developing specification documents.

6.2.1.6. Leading or managing a team involved in building applications for web-based GIS solutions.

6.2.2. Possess excellent written and oral communication skills with the ability to communicate with people of all technical levels.

6.3. KEY PERSONNEL – TEAM MEMBERS: The respondent shall designate key personnel with a minimum of one year of experience within the last three years in the services referenced in Para. 5 and shall have the knowledge to develop and implement the service requirements in this solicitation.

7. ADDITIONAL PERSONNEL REQUIREMENTS

7.1. The PM’s primary responsibility shall be the day-to-day operation of the service in accordance with the requirements of the purchase order.

7.2. The PM shall be a permanent staff employee and shall serve as a constant primary point of contact for TxDOT.

7.3. The PM shall serve as a member of the TxPROS Project Management Team and the Integrated Change Control Committee (Ref. Attachment A TxPROS Project Organization).

7.4. Key personnel shall have knowledge and experience, including all applicable current licenses, certifications, and permits, necessary to perform assigned duties under the purchase order.

4 - 19

SPECIFICATION NO. TxDOT 920-56-77 DATED: NOVEMBER 2006 8. PERSONNEL CONTINUITY AND REPLACEMENT

8.1. TxDOT recognizes that events beyond the control of the vendor such as the death, physical or mental incapacity, long-term illness, or the voluntary termination of employment of the PM will require that the vendor propose a replacement. In the event that such a replacement is necessary, vendor agrees that no personnel shall begin work on the project without prior written approval from TxDOT.

8.2. The vendor agrees that the PM and other key personnel assigned to the project shall remain available for the entirety of the project throughout the term of the purchase order as long as that individual is employed by the vendor and until the project is complete.

8.3. If TxDOT determines that the PM or other key personnel is unable to perform in accordance with the service requirements or to communicate effectively, the vendor shall immediately remove that person from the project.

8.4. Proposed replacement personnel shall meet minimum qualifications and have experience comparable to the person(s) being replaced. Replacement personnel shall be provided at no additional cost to TxDOT. A profile and references will be requested for the proposed replacement(s). TxDOT may reject any replacement if references or past working performance are questionable or unfavorable. TxDOT will be the sole judge of the qualifications of the proposed replacement personnel.

9. SYSTEM FUNCTIONALITY AND BUSINESS REQUIREMENTS: The proposed system shall meet all system functionality and business requirements in the following areas:

9.1. MAPPING: Ref. Attachment B TxPROS Requirements – Mapping.

9.2. RESTRICTION MANAGEMENT: Ref. Attachment C TxPROS Requirements – Restrictions Management.

9.3. ROUTING: Ref. Attachment D TxPROS Requirements – Routing.

9.4. REPORTING: Ref. Attachment E TxPROS Requirements – Reporting.

10. TECHNICAL REQUIREMENTS: The proposed system shall meet all technical requirements as specified in Attachment F TxPROS Requirements – Technical.

11. DEVELOPMENT APPROACH: The vendor shall manage this project to ensure quality, project success, long-term viability and optimal cost of ownership.

11.1. DEVELOPMENT METHODOLOGY: The vendor’s technical methodology shall relate to the specified business model. As part of the submission, vendor shall identify the methodology proposed and how it is intended to be applied to this project.

11.2. DETAIL DESIGN AND CUSTOMIZATION: Vendor-facilitated joint application design (JAD) sessions shall be included in the proposed approach to develop a detail design document that will require approval by the TxPROS Project Board prior to proceeding with detail development or customization. It is anticipated that these sessions, at various times would, in addition to the vendor, include appropriate project team personnel from MCD as well as from the ISD Work Group, representatives from the Districts’ user community, as well as members of the Customer Work Group.

11.3. DATABASE DESIGN: The vendor shall develop and present (logical or physical data models or both), for ISD approval, a technical database design using a methodology that:

11.3.1. Identifies entities (roles, events, locations, end-user data).

11.3.2. Identifies relationships (associations between entities using a relationship matrix).

11.3.3. Identifies cardinality (number of occurrences of one entity for a single occurrence of the related entity).

5 - 19


11.3.4. Defines primary keys (data attributes that uniquely identify one and only one occurrence of each entity).

11.3.5. Identifies and maps attributes (fields essential to the system development).

11.3.6. Includes a comprehensive data dictionary.

11.3.7. Uses ERWIN® for development of entity relationship diagrams.

11.4. INTERFACE DEVELOPMENT: The vendor shall handle the design, development, testing, and deployment of automated interfaces and file transmissions between the TxPROS Solution, TxDOT’s legacy (Bridge, Pavements, roadbed, etc.) systems, TxDOT Central Permitting System and any COTS products employed in the solution.

12. IMPLEMENTATION APPROACH: The vendor’s solution for implementation shall include, but not be limited to the following:

12.1. INFRASTRUCTURE SETUP: The activities necessary to establish and test the infrastructure required to operate the system. This includes all hardware and software components necessary to address the functional and technical requirements of the project. The vendor shall consider development, testing, and training environments during the infrastructure setup.

12.2. DATA CONVERSION: The vendor shall be responsible for performing any and all required data conversion activities associated with the project, including the confirmation of data conversion requirements and development of a comprehensive data conversion plan. The vendor shall lead the data conversion and loading effort. TxDOT, in conjunction with the vendor, will be responsible for verifying the accuracy of the converted and loaded data.

12.3. DATA CONVERSION PLAN: The vendor’s data conversion plan shall include the following:

12.3.1. All files and tables to be built in the new system.

12.3.2. Data sources for those files and tables.

12.3.3. Expected data volumes.

12.3.4. Identification of those conversions where automated conversion tools or programming can be used to significantly reduce data conversion labor.

12.3.5. Roles, responsibilities, and a schedule for the conversion effort.

12.4. EXECUTION OF DATA CONVERSION: In the execution of the conversion plan outlined above, the vendor shall be responsible for developing and testing automated conversion programs to support the commencement of live operations. This effort shall include, but not be limited to:

12.4.1. Development of programming specifications.

12.4.2. Coding of conversion programs in accordance with program specifications.

12.4.3. Performance of unit and integration testing of the conversion programs.

12.4.4. Performance of data integrity testing, which includes correcting problems associated with past code changes.

12.4.5. Building any crosswalk file structures required to assist TxDOT in developing test scenarios and conducting acceptance testing.

12.4.6. Running the conversion programs and assisting TxDOT with the verification of the converted data in the production environment.

12.5. DOCUMENTATION AND TRAINING: The vendor shall provide documentation and training in an agreed upon timeframe to ensure that all TxDOT end users have the knowledge and capabilities necessary to independently use the TxPROS system. The requirements for this training are contained in Attachment G TxPROS Requirements – Documentation & Training.

6 - 19


12.5.1. Training shall be conducted at agreed upon TxDOT facilities throughout the state.

12.5.2. The vendor shall develop and provide user documentation including manuals, quick reference guides, tutorials, help, and other techniques as appropriate to satisfy the requirements identified in Attachment G TxPROS Requirements – Documentation and Training.

12.5.3. Documentation and training plans shall be developed by the vendor during the early phase of the project and approved by TxDOT.

12.6. TESTING AND ACCEPTANCE CRITERIA: TxDOT will, in its sole discretion, determine whether the system meets the acceptance criteria. To meet the acceptance criteria, the system shall pass all, but not be limited to, stages of testing described below. The system will be accepted when at least the following conditions are met:

12.6.1. All deliverables required by the purchase order have been provided to TxDOT.

12.6.2. The system is fully operational in its installed setting at TxDOT, and all integrated subsystems are functioning as designed.

12.6.3. Vendor has completed the Installation Qualification and provided all associated documentation to TxDOT.

12.6.4. All new application system interfaces with external systems are functioning as designed and without system conflicts.

12.6.5. All system data conforms to expected output, and data integrity is verified.

12.6.6. All user acceptance testing of the system feature/functionality is successfully completed.

12.6.7. Training of TxDOT personnel has been completed.

12.6.8. The system has been in production (“live”) at all TxDOT locations without malfunction and free of defects for a period of 30 days following successful user acceptance testing.

12.7. TESTING AND ACCEPTANCE PLAN: The vendor shall have a Testing and Acceptance Plan that includes, but is not limited to:

12.7.1. Functional testing:

12.7.1.1. Unit testing (functionality) on all individual modules or components prior to integration into a system or subsystem.

12.7.1.2. Component integration testing (subsystem and system) to ensure that appropriate communications, links and data sharing occur properly.

12.7.2. Business logic testing against all documented business rules to include validation of appropriate system response for invalid or unexpected input conditions as well as valid conditions.

12.7.3. Performance testing to ensure integrated system satisfies service level targets under normal workloads.

12.7.4. Stress testing of the application to determine failure point of the system under extreme levels of usage and counter actions effectiveness.

12.7.5. Preliminary (beta) testing by TxPROS’ Customer User Group as external customer acceptance.

12.7.6. Design of testing scenarios (with documented expected results) that address all of the above.

7 - 19


12.7.7. Processes and methodologies for correcting problems based on test results using regression testing techniques to ensure changes made for subsequent tests do not adversely affect those already tested.

12.7.8. Final user acceptance and integration testing.

12.7.9. Provision of a Production “Go Live” Plan.

12.8. TRANSITION PLAN: The vendor shall provide a fully functioning system including transfer of knowledge, technical training, software, hardware, data and processes. TxDOT will approve the Transition Plan which shall include processes and responsibilities for transferring the system to TxDOT. The transition period shall not exceed 90 days.

12.9. POST-TRANSITION SUPPORT: The vendor shall provide post-transition support including the provision of a manager-level employee with significant experience with the contract and access to other technical and operational experts during business hours for a period of at least 30 calendar days following transition of the system to TxDOT.

13. SYSTEM SECURITY REQUIREMENTS: The vendor shall meet all security requirements for each component of the system including:

13.1. Computer software security.

13.2. Data access and storage.

13.3. Client and user security.

13.4. Network security.

13.5. Web-based security.

14. PROJECT MANAGEMENT: Project Management requirements shall include, but not be limited to, the following:

14.1. PROJECT OVERVIEW

14.1.1. Background: History of the approach, business objectives and critical success factors.

14.1.2. Assumptions: Regarding implementing the TxPROS Solution as defined within this RFO.

14.1.3. Scope: Understanding of the scope of the project, including what is considered in and out of scope.

14.1.4. Timeline: A high-level timeline of the proposed approach, listing the major milestones and deliverables in a Gantt chart accessible in Microsoft Project 2000®.

14.2. SCHEDULE AND WORK PLAN: The vendor shall provide a detailed project schedule and work plan for all project tasks for inclusion into the TxPROS PMP (Ref. Attachment H TxPROS Project Management Plan). The PM shall monitor and update the project schedule and work plan, revising as appropriate, with approval from TxDOT. The plan shall be accessible via Microsoft Project 2000® or compatible product approved by TxDOT. The plan shall include, but is not limited to, the following:

14.2.1. An implementation schedule.

14.2.2. A logical sequence of tasks and deliverables included in each project period.

14.2.3. A clear definition of each task and deliverable.

14.2.4. Staff requirements for each task and deliverable.

14.2.5. A specific target completion date for each task and deliverable.

14.2.6. Task and deliverable relationships and dependencies.

8 - 19


14.2.7. Use of a gated approach as defined in Para.14.4.2.

14.3. REPORTS: The vendor shall submit reports as identified in the TxPROS Communication Management Plan (Ref. Attachment I TxPROS Communication Management Plan) and as requested by TxDOT. Reports and format standards will be approved by TxDOT and shall be delivered to the designated TxDOT representative.

14.4. PROJECT MANAGEMENT APPROACH: The vendor shall provide a project management methodology and management approach that complies with the Texas Department of Resources’ (DIR) Texas Project Delivery Framework and is compatible with TxDOT’s TxPROS Project Management Plan (Ref. Attachment H TxPROS Project Management Plan) ensuring completion of the project to specified quality standards.

14.4.1. Project Methodology: The vendor shall establish a plan including written project controls, standards and procedures for all project tasks for which it will be responsible. These documents will be reviewed and approved by TxDOT’s TxPROS Project Management Team and incorporated into the TxPROS PMP. This requirement includes, but is not limited to:

14.4.1.1. Processes for managing project documentation.

14.4.1.2. Software version control.

14.4.1.3. Requirements management.

14.4.1.4. Business process reviews.

14.4.1.5. Naming conventions.

14.4.1.6. Change control.

14.4.1.7. Timekeeping procedures.

14.4.1.8. Submission and approval of deliverables.

14.4.1.9. Submission and approval of the gated phases.

14.4.1.10. Meeting procedures.

14.4.2. Gated Approach: The vendor shall use gates within the project work plan. This approach shall include the following criteria:

14.4.2.1. Gates are decision points that proceed every forthcoming phase. Unless specific prior criteria have been met, as evidenced by certain approved deliverables, the project shall not move forward into the next phase.

14.4.2.2. The gate shall provide an opportunity for TxDOT and the vendor to review the deliverables included in the previous phase and to determine whether the project is on target and the deliverables are accepted. The gate sessions will be attended by the TxPROS Project Management Team, selected stakeholders and the vendor’s management team. Conditional approval of the deliverables will occur as the deliverables are submitted; however, acceptance of the deliverables will occur at the gate sessions. The TxPROS Project Management Team will provide written conditional approval to allow the project to move forward.

14.4.3. Project Organization: The vendor’s Project Manager and the vendor’s team members (Ref. Para. 6) will be incorporated into the TxPROS project organization as identified in Attachment A TxPROS Project Organization. The vendor shall identify the roles and responsibilities of all of its identified key personnel for inclusion into the TxPROS PMP (Ref. Attachment H TxPROS Project Management Plan).

9 - 19


14.4.4. Communication Planning: The vendor’s communication plan shall be in conformance with, and for incorporation into, the TxPROS Communication Management Plan (Ref. Attachment I TxPROS Communication Management Plan) and shall facilitate organizational communication and identify strategies for effective communication throughout the life of the purchase order.

14.4.4.1. The vendor shall administer the work by establishing and maintaining communication through the TxDOT Project Management Team with all groups related to the project. The activities of the vendor project team shall be directed, coordinated and communicated to ensure that the project progresses as outlined in the approved project work plan and is completed on schedule.

14.4.4.2. Meetings shall be scheduled as required by the TxDOT project management team or the vendor. The vendor's Project Manager and personnel shall be available to provide information reports, audits or other special reports as required by TxDOT.

14.4.5. Quality Approach: The vendor shall assure quality results by validating, measuring and documenting the quality of the deliverable. Performance standards and measures will be developed in purchase order negotiations and included in the purchase order and incorporated into the TxPROS PMP.

14.4.6. Risk Management: The vendor shall identify and assess potential risks to the project and identify and manage actions to avoid, mitigate, or manage those risks in accordance with the TxPROS Risk Management Plan (Ref. Attachment J TxPROS Risk Management Plan). This shall include, but not be limited to, the following:

14.4.6.1. Provision of the appropriate methods, tools, and techniques for active identification and assessment of project risks.

14.4.6.2. Development of risk mitigation actions.

14.4.6.3. Risk response planning and management strategies.

14.4.6.4. Monitoring and reporting of risk status throughout the life of the project.

14.4.7. Issue Management: As part of the Issue Management process to be established in accordance with the TxPROS PMP (Ref. Attachment H TxPROS Project Management Plan, Para. 4.2), the vendor’s process shall include:

14.4.7.1. Issue identification and tracking.

14.4.7.2. Time frames for resolution.

14.4.7.3. Responsible parties.

14.4.7.4. Specific steps to be taken on issues or disputes arising during the implementation process, including approval and escalation procedures.

14.4.7.5. Issue Resolution Plan addressing each issue identified.

14.4.8. Change Management: The vendor’s process shall include:

14.4.8.1. Change identification and tracking.

14.4.8.2. Timeframes for resolution, responsible parties, and specific steps to be taken on issues or disputes arising during the implementation process, including approval and escalation procedures in accordance with the TxPROS change control process identified in the TxPROS Configuration Management Plan (Ref. Attachment K TxPROS Configuration Management Plan).

10 - 19


14.4.9. Acceptance Management: The vendor’s proposed process shall be negotiated and approved for inclusion into the TxPROS PMP (Ref. Attachment H TxPROS Project Management Plan ) and shall include but not be limited to:

14.4.9.1. Deliverable identification and tracking.

14.4.9.2. Timeframes for proposed acceptance gate work sessions based on the work plan.

14.4.9.3. Responsible parties.

14.4.9.4. Specific steps to be taken on issues or disputes arising with the deliverables, including approval and escalation procedures.

14.4.9.5. Criteria for acceptance or rejection that is approved by both the vendor and TxDOT within the early phase of the project.

15. HOSTING REQUIREMENTS – (OPTIONAL): Although this RFO primarily seeks to identify a mapping and software solution that takes advantage of the current TxDOT technical environment, an optional vendor hosted solution that satisfies the business and functional requirements will also be considered. A hosted alternative would be subject to additional vendor service requirements that are specified in Attachment L TxPROS Requirements – Optional Hosting.

16. WARRANTIES

16.1. The vendor shall warrant each deliverable (Ref. Schedule 4 – Pricing Schedule) for a period of one year after the system is fully implemented and accepted. During the warranty period, the vendor shall be responsible for correcting any defects causing any portion of the system to be inoperable or any defects resulting in inaccurate results produced by the system, when the system is used in accordance with the product documentation provided by the vendor and without extraordinary actions on the part of TxDOT or its users. Such defects shall be localized and reproducible upon demand and, if found to be contained in the system delivered by the vendor, shall be corrected to the satisfaction of TxDOT at no additional cost to TxDOT.

16.2. The vendor shall not be responsible for correcting defects resulting from system components that have been improperly altered or affected by the actions of TxDOT. Should TxDOT request the vendor to correct a defect that is a result of TxDOT's improper alteration of the system components or affected by the actions of TxDOT, TxDOT agrees to reimburse the vendor on an agreed upon hourly basis for the problem diagnosis and defect correction, if any. During the problem diagnosis, the vendor shall keep TxDOT informed of potential charges.

17. MAINTENANCE AGREEMENT: The vendor’s solution shall provide a planned maintenance, upgrade, and data management strategy. TxDOT will consider a multi-year agreement with volume discount pricing. The proposed maintenance agreement shall include at a minimum:

17.1. Planned software and data upgrades and maintenance schedules.

17.2. Planned maintenance and upgrades shall be scheduled. The vendor shall schedule any required maintenance for the environments covered under the resulting purchase order.

17.3. Software upgrades shall be coordinated with TxDOT to ensure that version incompatibilities are not created.

17.4. The vendor shall have procedures that ensure that all potentially affected users are notified if at any point a system must be halted to provide maintenance.

17.5. Clearly defined roles, responsibilities, and coordination processes.

17.6. Clearly identified roles and responsibilities and ownership during disaster readiness and recovery.

17.7. Clearly defined process for testing recovery services at a minimum of once per year with documentation for each recovery process.

11 - 19

SPECIFICATION NO. TxDOT 920-56-77 DATED: NOVEMBER 2006 18. VENDOR REQUIREMENTS: The vendor shall:

18.1. Adhere to the TxDOT Terms and Conditions identified on the solicitation.

18.2. Provide all labor, materials and equipment necessary to meet requirements of the specified services throughout the term of the purchase order.

18.3. Provide equipment, personnel and resources for on-shore (within the United States) performance of the requirements of the RFO.

18.4. Maintain a Texas office staffed with key project personnel within a 300 mile radius of Austin, Texas for the duration of the purchase order. If not currently established in Texas, the office shall be established within 30 days after purchase order award.

19. TXDOT RESPONSIBILITIES: TxDOT will:

19.1. Provide a contract manager and point-of-contact.

19.2. Provide access to appropriate data systems and information.

19.3. Provide a top-level system overview.

19.4. Require that TxDOT’s TxPROS Project Board and the TxPROS Project Management Team oversee and manage the project.

19.5. Actively participate in the project to assure success of the project.

19.6. Provide resources for oversight, implementation and deployment of the project.

19.7. Provide subject matter experts who will be responsible for working with the vendor to modify the existing business rules (which are based on manual processes) and update the business rules for the automated TxPROS Solution.

19.8. Provide resources to assist the vendor in configuring and testing the workflow. TxDOT will identify the system owner(s) who will be responsible for the TxPROS Solution through the transition period. The transition team will report to the system owner(s) during the transition period. Identification of the system owner(s) will occur during the last phase of the project.

20. SUBCONTRACTING: Subcontracting is allowed under the following circumstances.

20.1. Subcontractors providing service under the purchase order shall meet the same service requirements and provide the same quality of service required of the vendor.

20.2. No subcontract under the purchase order shall relieve the primary vendor of responsibility for the services.

20.3. The vendor shall be the only contact for TxDOT and subcontractor(s).

20.4. The vendor shall maintain all project management, schedules, performance and responsibilities for subcontractors. The vendor shall be held solely responsible and accountable for the completion of all work for which the vendor has subcontracted.

20.5. TxDOT reserves the right to request the removal of vendor’s subcontractor staff deemed unsatisfactory by TxDOT.

20.6. Subcontracting shall be at the vendor’s expense.

20.7. SOLICITATIONS OVER $100,000: TxDOT will make an initial determination of whether subcontracting is probable. It is the respondent’s determination if they choose to subcontract any of the work under this purchase order with a Texas Certified Historically Underutilized Business (HUB) or other businesses.

20.7.1. If TxDOT has determined that subcontracting opportunities are probable, the class and items in which HUBS may be registered will be noted in the solicitation.

12 - 19


20.7.2. The respondent shall identify all proposed subcontractors at the time of response submittal. The required forms with video instructions can be found at the following website: http://www.tbpc.state.tx.us/hub/forms/hubsubcontplan.html

20.8. HSP PRIME CONTRACTOR PROGRESS ASSESSMENT REPORT: After award the vendor shall report all HUB and non-HUB subcontractor information using the HSP Prime Contractor Progress Assessment Report form. One copy of this report shall be submitted monthly to TxDOT’s Business Opportunity Programs Office, and one copy shall be submitted with the invoice. Only actual payments made to subcontractors are to be reported. These reports will be required monthly even during months when no payments to subcontractors have been made. TxDOT may verify the amounts being reported as paid by requesting copies of cancelled checks paid to subcontractors.

20.9. TxDOT retains the right to check subcontractor's background and make a determination to approve or reject the use of submitted subcontractor(s). Any negative responses may result in disqualification of the subcontractor.

21. BUSINESS CONTINUITY AND DISASTER RECOVERY PLAN: The respondent shall submit a business continuity and disaster recovery plan (limit two pages) which shall include the following:

21.1. Business continuity procedures that shall be implemented to fulfill all requirements of the purchase order in case of fire, theft, natural disaster, technical difficulty, workforce problems or other disruption of business.

21.2. A disaster recovery plan for recovery of the data for this service shall be maintained in case of fire, theft, natural disaster, or technical difficulty. The vendor shall be responsible for all cost of the disaster recovery plan. The disaster recovery plan may include the transfer of this service to a subcontractor as approved in writing by TxDOT.

22. SOFTWARE DELIVERY AND INTELLECTUAL PROPERTY RIGHTS

22.1. DELIVERY: The vendor shall:

22.1.1. Deliver all custom and reuse software, if used, as machine readable source files, and linkable or executable modules, and printed source listings, in addition to installed and operating copies of the programs (baseline software or hardware configuration shall not be created such that only vendor could change).

22.1.2. Identify the tools required for the modification and compilation of the custom and reuse software programs.

22.1.3. Deliver source codes for all custom and reuse software programs developed under the purchase order with all needed support resources needed to edit, compile and link these programs on the central processors, including, but not limited to: CASE tools, compilers, editors, and function libraries used in the development of the programs.

22.1.4. Deliver all documentation concerning protocol for reuse and custom software, source code, commented listings, descriptions of software structure, database utilization, and instructions necessary to convert the source code into an operational system.

22.2. SOFTWARE: The vendor shall not:

22.2.1. Create software that only the vendor could modify.

22.2.2. Create or utilize reuse software that is not in the public domain.

22.3. CUSTOMIZED SOFTWARE LICENSE: The vendor shall not place any legend on the custom or reuse software, which restricts TxDOT’s rights in such software unless the restrictions are set forth in a license agreement approved and executed by TxDOT.

13 - 19


22.4. OWNERSHIP

22.4.1. The vendor shall transfer to TxDOT or purchase for TxDOT all licenses to software and data acquired in conjunction with this project, including all original media, documentation, warranties, licenses, applications software, and developmental software used in developing custom applications.

22.4.2. In the event that custom software development is required, TxDOT will own the entire rights (including copyrights, copyright applications, copyright renewals, and copyright extensions), title and interests in and to the custom software development documentation, software, and any other intellectual properties created for custom software and versions thereof, and all works based upon, derived from, or incorporating works thereof, and in and to all income, royalties, damages, claims, and payments now or hereafter due or payable with respect thereto, and in and to all causes of action, either in law or in equity for past, present, or future infringement based on the custom software and copyrights arising there from, and in and to all rights corresponding to the custom software and versions thereof throughout the world. TxDOT shall retain ownership of all production and historical data produced by the proposed system.

22.5. SOFTWARE LICENSING: The vendor shall provide for TxDOT to have escrow account access to, and receive, the source codes and data for any licensed products upon the failure or demise of the vendor’s company.

23. TRAVEL: All travel and per diem shall be included in the unit price.

24. CONFLICT OF INTEREST: The vendor or vendor’s subcontractor(s) covenants that it does not have, nor shall it acquire any interest that would conflict in any manner with the performance of its obligations in regard to services authorized.

25. PERFORMANCE BOND: If the total solicitation for services to be performed under the purchase order exceeds $100,000, the vendor shall submit a performance bond in the total amount of the purchase order.

25.1. Bonds shall be executed in accordance with Article 7.19-1, Vernon’s Texas Insurance Code.

25.2. The cost of the bond(s) shall be included in the pricing submitted. TxDOT will not pay for bond(s) as a separate item.

25.3. Acceptable forms of bonding are cashier’s check, certified check or irrevocable letter of credit issued by a financial institution subject to the laws of Texas; a surety or blanket bond from a company chartered or authorized to do business in Texas and entered on the United States Department of Treasury’s listing of approved sureties or the Texas Department of Insurance listing; United States treasury bond; or certificate of deposit.

25.4. If using bonds, the bond(s) shall be executed on a form provided by TxDOT and returned to TxDOT within 15 calendar days after written notice has been issued to the vendor. A Power of Attorney and a printed document stating the bonding company’s name, address and telephone number and the Texas Department of Insurance telephone number shall accompany the bond(s).

26. AMENDMENTS: TxDOT and the vendor reserve the right to amend the purchase order by mutual written agreement at any time during the term of service, as may be necessary to achieve the highest quality of production by the most efficient and cost-effective means or to include a different element or special feature that was not contemplated or fully developed at the time of solicitation. The amendment process will be accomplished through a Purchase Order Change Notice (POCN).

27. INVOICING INSTRUCTIONS AND PAYMENT REQUIREMENTS: The vendor shall provide a comprehensive and detailed invoice with reference to the basis for each item charged. Original documentation that validates the charges shall be attached. The original and one copy of the invoice shall be mailed to the address shown on the purchase order and shall include the following:

14 - 19


27.1. Purchase order number.

27.2. Vendor EIN.

27.3. Date and time of service.

27.4. Invoices that require correction(s) shall be re-submitted with a new invoice date.

28. RESPONSE SUBMISSION: Failure by the respondent to submit the documentation listed below will disqualify the respondent from further consideration. The response submission shall be submitted in the following format:

28.1. GENERAL FORMAT: The respondent shall submit one signed and dated original (marked Original) and eight copies (marked Copy). The submission shall be in separate loose leaf binders on one sided 8-1/2 X 11-inch paper and shall be tab-indexed corresponding to the sections listed below. Plastic spine-bound or wire bound submittals are highly discouraged. Include only the information specified for each section.

28.2. ORIGINAL RESPONSE: The original response shall include the following:

28.2.1. Section 1 – Request for Offer (RFO): Original signed, dated and completed RFO.

28.2.2. Section 2 – Schedule 1 - Company Profile and History: The respondent shall complete and submit Schedule 1 – Company Profile and History which includes:

28.2.2.1. A brief description of the company, including the company name, address, phone number, legal status (i.e., corporation, partnership, etc.).

28.2.2.2. Name, phone number and email address of the person TxDOT should contact with any questions regarding the response submission.

28.2.2.3. Number of years in business, size and scope of operation.

28.2.2.4. Name and title of person signing the response.

28.2.3. Section 3 – Financial Standing: The respondent shall submit:

28.2.3.1. Submit the most recent three years audited financial statements, or if audited financial statements are unavailable, un-audited financial statements shall be submitted and certified as true, correct and accurate by the chief financial officer or treasurer of the respondent’s company. (Ref. Para. 5.5)

28.2.4. Section 4 – Company Qualifications and Experience: Respondent shall describe their background and experience that qualifies them to undertake the project. The minimum information to be presented should include complete descriptions of projects of similar size and scope. In addition the respondent shall address:

28.2.4.1. Experience providing information technology solutions.

28.2.4.2. Experience performing jobs that are similar in size and complexity, specifically utilizing an integrated web-based GIS solution.

28.2.4.3. Experience with transportation industry related technical solutions.

28.2.4.4. Experience working with federal, state or local governments.

28.2.5. Section 5: Schedule 2 - Project Manager Qualifications and References: The respondent shall submit Schedule 2 documenting the Project Manager’s qualifications (Ref Para. 6.2 and references).

28.2.6. Section 6 - Key Personnel – Team Member Qualifications: The respondent shall complete and submit brief profiles of the team members proposed (Ref. Para.6.3) including any subcontractors, who will be part of the respondent’s personnel providing the service. The profile shall include:

15 - 19


28.2.6.1. Each individual’s name and title.

28.2.6.2. Education.

28.2.6.3. Specific work to be performed and services to be provided.

28.2.6.4. Qualifications and relevant experience that makes the proposed individual suitable for their designated role on this project.

28.2.6.5. Each individual’s percentage of time to be dedicated to this project if the respondent is selected and the number of other projects the individual is currently assigned to.

28.2.6.6. Any additional information that indicates the individual’s ability to successfully perform the services required in this RFO.

28.2.7. Section 7 – System Functionality and Business Requirements: The respondent shall describe their approach and their ability to meet the system functionality and business requirements in the order specified in Para 9 and the related Attachments. The response should be specific and address all requirements related to:

28.2.7.1. Mapping (Ref. Attachment B – TxPROS Requirements – Mapping).

28.2.7.2. Restriction Management (Ref. Attachment C – TxPROS Requirements – Restriction Management).

28.2.7.3. Routing (Ref. Attachment D – TxPROS Requirements – Routing).

28.2.7.4. Reporting (Ref. Attachment E – TxPROS Requirements – Reporting).

28.2.8. Section 8 – Technical Solution: Respondent shall describe their approach and their ability to meet the technical requirements in the order specified in:

28.2.8.1. Technical Requirements (Ref. Para 10 and Attachment F – TxPROS Requirements – Technical).

28.2.8.2. Development Approach (Ref Para. 11): Response shall include a high level design and development plan that reflects the major activities and gates through the development phases.

28.2.8.3. Implementation Approach (Ref. Para. 12).

28.2.8.3.1. Data Conversion Plan (Ref. Para. 12.3).

28.2.8.3.2. Documentation and Training (Ref. Para. 12.5 and Attachment G – TxPROS Requirements – Documentation and Training).

28.2.8.3.3. Testing and Acceptance Plan (Ref Para. 12.7).

28.2.8.3.4. Transition Plan (Ref. Para. 12.8).

28.2.8.4. System Security Requirements (Ref. Para. 13).

28.2.8.5. Maintenance Agreement (Ref. Para. 17).

28.2.9. Section 9 – Project Management: Respondent shall describe their approach to project management and address all requirements in the order presented in Para. 14

28.2.9.1. Include a high level timeline (Ref. Para. 14.1.4).

28.2.9.2. Include a proposed project schedule and work plan (Ref. Para. 14.2).

16 - 19


28.2.10. Section 10 – Business Continuity and Disaster Recovery Plan: Respondent shall submit a contingency and recovery plan detailing how they propose to meet the specifications in the event vendor service is interrupted. The plan shall detail the vendor’s backup and recovery process (Ref. Para. 21).

28.2.11. Section 11 – Schedule 3 – Client References: Respondent shall submit references (for all identical and similar services, which are alike in size and scope) that verify the qualifications and experience requirements for services completed within the past five years). References shall illustrate respondent’s ability to provide the services outlined in the specification. References shall include name, point of contact, telephone number, and dates services were performed. The response will be disqualified if TxDOT is unable to verify qualification and experience requirements from the respondent’s references. The response will be disqualified if TxDOT receives negative responses. TxDOT will be the sole judge of references (Ref. Schedule 3).

28.2.12. Section 12 – Schedule 4 – Pricing Schedule.

28.2.13. Section 13 – HUB Subcontracting Plan.

28.2.14. Optional Section 14 – Hosting: Respondent may describe their approach to meeting the optional hosting requirements in the order presented in Attachment L – TxPROS Requirements – Optional Hosting.

28.3. CD REQUIREMENT: The respondent shall submit Section 1 through Section 11 on a CD with the original signed and dated submittal.

28.4. COPIES: The eight reproduced copies (marked Copy) shall include only the following tab-indexed sections:

28.4.1. Section 2 – Company Profile and History.

28.4.2. Section 4 – Company Qualifications and Experience.

28.4.3. Section 5 – Project Manager Qualifications and References.

28.4.4. Section 6 – Key Personnel - Team Member Qualifications.

28.4.5. Section 7 – System Functionality and Business Requirements.

28.4.6. Section 8 – Technical Solution.

28.4.7. Section 9 – Project Management.

28.4.8. Section 10 – Business Continuity and Disaster Recovery Plan.

29. RESPONSE EVALUATION: Only complete responses with the required submittal documents and meeting minimum qualifications will be considered. Failure to meet the minimum qualifications and submit the required documents will result in a response being declared non-responsive.

29.1. STEP 1 – INITIAL EVALUATION: A TxDOT evaluation committee will evaluate and score each response based on established criteria. Respondents shall not contact members of the evaluation team. Responses will be evaluated according to the respondent’s ability to best satisfy TxDOT requirements.

29.1.1. Respondent qualifications and response submission information will comprise 70 percent of the evaluation total.

29.1.2. Pricing submitted for the solicitation requirements will be 30 percent of the evaluation total.

29.2. STEP 2 – ORAL PRESENTATION AND DISCUSSION: TxDOT may request that selected respondents give a presentation to TxDOT. A TxDOT evaluation committee will evaluate and score each presentation. All responses will be evaluated according to the respondent’s ability to best satisfy TxDOT requirements.

17 - 19


29.2.1. TxDOT may provide an agenda for the presentation.

29.2.2. Respondents should be prepared to address any questions that may be asked by TxDOT evaluators.

29.2.3. Proposed key personnel may be expected to attend and participate in the presentation. TxDOT will notify the respondent with a list of titles or individuals who should attend the presentation. TxDOT will advise each respondent in writing of the location, date and time of their scheduled presentation. Preferably, a minimum of two weeks notice will be given to the respondent(s) selected for the oral presentation phase; however, there may be times when a shorter time frame is required.

29.2.4. After oral presentations, TxDOT reserves the right to continue discussions or negotiations with selected respondent(s).

29.3. STEP 3 – BEST AND FINAL OFFER (BAFO): TxDOT may determine to award the purchase order for the service without requesting a BAFO, if it is in the best interest of TxDOT. TxDOT reserves the right to request a BAFO from selected respondent(s). The respondent(s) shall submit a final price and any added value or incentives. If more than one respondent reaches this level, the negotiated terms, references, BAFO and best value will be the considered in the award, but TxDOT will make the final determination on what is the best value and solution for TxDOT.

30. AWARD: TxDOT reserves the right to award a purchase order to the company that provides the best service and value to TxDOT in performance of this service.

31. BEST VALUE: TxDOT will be the sole judge of best value. Best value criteria may include, but is not limited to a solution that best meets the following objectives:

31.1. Reduces the time it takes to issue OS/OW permits,

31.2. Allows MCD to meet increasing demand for services,

31.3. Increases the safety of the traveling public,

31.4. Improves TxDOT’s tracking of structures and restrictions that affect OS/OW routing,

31.5. Provides the ability to track and report the transport of OS/OW loads on Texas’ roadways.

31.6. Provides the most customer focused solution that will best meet the needs of the OS/OW carriers.

31.7. Experience in successfully providing services in the solicitation.

32. POST AWARD MEETING: Vendor(s) shall attend a post award meeting in Austin, Texas with TxDOT within 30 calendar days after the award of the purchase order. The purpose of the meeting is to discuss the terms and conditions of the purchase order and to provide additional information regarding work plans, which shall be executed by both parties, wherein vendor(s) and TxDOT shall identify specific goals, strategies and activities planned for meeting particular program area objectives.

33. TRANSITION

33.1. BEGINNING PHASE: If the purchase order is awarded to a new vendor, the new vendor shall agree to a transition phase for a period of 60 days. These 60 days shall commence on a date confirmed in writing by TxDOT at the time of award. The new vendor shall be responsible to contact the previous vendor and request the transfer of all publications, documents, property, equipment, other material which TxDOT retains ownership right and any additional material related to work provided under the previous purchase order. TxDOT will provide assistance as needed for the efficient and smooth transfer of all material to the new vendor.

18 - 19


33.2. ENDING PHASE: At the termination date of the purchase order, the current vendor(s) shall cooperate fully, with the subsequent vendor(s), to transfer all publications, documents, property, equipment, and other material in which TxDOT retains ownership rights. This includes any additional material related to work provided under the current purchase order. During this transition period, this purchase order may be extended for an additional 60 or 90 days at the same price and terms and conditions to allow for the transition of all TxDOT data, material and education of purchase order requirements to the new vendor(s) and to allow the current vendor time to complete any project(s) in progress.

34. CONTRACT ADMINISTRATION: Administration of the purchase order is a joint responsibility of the TxDOT Division and TxDOT Purchasing. TxDOT Purchasing staff will be responsible for administering the contractual business relationship with the vendor.

34.1. Any proposed changes to work to be performed, whether initiated by TxDOT or the vendor, must receive final written approval in the form of a Purchase Order Change Notice signed by the authorized TxDOT purchasing agent.

34.2. Upon issuance of purchase order, TxDOT will designate an individual who will serve as the Contract Manager and point-of-contact between the agency and the vendor. The Contract Manager does not have any express or implied authority to vary the terms of the purchase order, amend the purchase order in any way or waive strict performance of the terms or conditions of the purchase order. This individual’s contract management and contract administration responsibilities include, but are not limited to:

34.2.1. Monitoring the vendor’s progress and performance and ensuring services conform to established specification requirements.

34.2.2. Managing the financial aspects of the contract including approval of payments.

34.2.3. Meeting with the vendor as needed to review progress, discuss problems, and consider necessary action.

34.2.4. Identifying a breach of contract by assessing the difference between contract performance and non-performance.

34.2.5. Other areas as identified by the Texas Building and Procurement Commission State of Texas Contract Management Guide, latest edition

19 - 19


SCHEDULE 1

COMPANY PROFILE AND HISTORY

Respondent shall use this schedule or a facsimile to clearly show how they meet the requirements set forth in the response submission, Paragraph 5.

RESPONDENT NAME:

ADDRESSES:

Physical:

Mailing:

PHONE NUMBER:

FAX NUMBER:

LEGAL STATUS: Type of Organization, i.e., corporation, partnership, sole proprietorship.

NAME:

PHONE NUMBER:

EMAIL ADDRESS:

of person to contact with questions regarding the solicitation.

Number of years in business and scope of operation:

Name and title of person signing the response:

DOCUMENTATION OF RESPONDENT HISTORY AND QUALIFICATIONS:

Brief description of three years of experience within the last five years providing information technology solutions; use of integrated web-based GIS solution, experience with transportation industry related technical solutions, experience working with federal, state, or local governments. (Ref. Para 5.)

This form may be modified as needed to comply with the requirement to document company information.

THIS PAGE OR A REASONABLE FACSIMILE SHALL BE RETURNED WITH THE RESPONSE. FAILURE TO RETURN THIS PAGE OR A REASONABLE FACSIMILE WILL RESULT IN THE RESPONSE BEING CONSIDERED NON-RESPONSIVE.

1 - 1


SCHEDULE 2

PROJECT MANAGER QUALIFICATIONS AND REFERENCES

Respondent Name: The respondent shall complete a Project Manager profile not to exceed two pages. TxDOT reserves the right to reject the proposed Project Manager if references or past working performance are questionable or unfavorable. PROJECT MANAGER INFORMATION RESPONSE AREA Full Name: Number of years employed by respondent: PROJECT MANAGER QUALIFICATIONS AND REQUIREMENTS

# YRS EXP.

DESCRIPTION OF EXPERIENCE AND PROJECT

A minimum of three years of experience: 1) Analyzing and managing large software development or integration projects.

2) Project Management experience. 3) Implementing enterprise level IT solutions. 4) Using industry-accepted software development methodologies and standards.

5) Analyzing business processes and developing specification documents.

6) Leading or managing a team involved in building applications for web-based GIS solutions.

7) Specific education, qualifications, training, certifications.

Reference #1

Name of Organization: Business Address: Business City: Business State: Zip Contact Person Name: Contact Person Title: Phone Number: Fax Project Title:

Project Description and dollar amount:

Roles and Responsibilities of the Proposed Staff during this project

Project Start Date: Project End Date Client Comments:

1 - 2


SCHEDULE 2 (CONTINUED)

PROJECT MANAGER QUALIFICATIONS AND REFERENCES

Reference #2

Name of Organization: Business Address: Business City: Business State: Zip: Contact Person Name: Contact Person Title: Phone Number: Fax: Project Title:


Roles and Responsibilities of the Proposed Staff during this project:

Project Start Date: Project End Date: Client Comments:

Reference #3

Name of Organization: Business Address: Business City: Business State: Zip: Contact Person Name: Contact Person Title: Phone Number: Fax: Project Title:


Roles and Responsibilities of the Proposed Staff during this project:

Project Start Date: Project End Date: Client Comments:


2 - 2


SCHEDULE 3

CLIENT REFERENCES

INCLUDE ONLY REFERENCES FOR WHICH PROJECTS WERE COMPLETED WITHIN THE LAST FIVE YEARS. Respondent Name ___________________________________________________________________ Reference #1

Name of Client Organization:

Business Address:

Business City:

Business State: Zip:

Contact Person Name:

Contact Person Title:

Phone Number: Fax:

Project Title:

Project Description:

Project Start Date:

Project End Date:

THIS PAGE OR A REASONABLE FACSIMILE SHALL BE RETURNED WITH THE RESPONSE. FAILURE TO RETURN THIS PAGE OR A REASONABLE FACSIMILE WILL RESULT IN THE RESPONSE BEING CONSIDERED NON-RESPONSIVE. ANY NEGATIVE RESPONSE(S) MAY RESULT IN DISQUALIFICATION OF THE RESPONSE.

1 - 1


SCHEDULE 4

PRICING SCHEDULE

As identified in the solicitation, the TxPROS project will utilize a gated approach for decision points to control the flow and transition from each major phase of the project to the next. Accordingly, payments will be made based upon receipt of approved and accepted deliverables that satisfy the full requirements of the associated gate. Subject to the final solution approach, these phases are anticipated to include: ANTICIPATED DELIVERABLES

PHASE I DESIGN AND PLANNING PHASE (20%)

JAD Summaries Detail Design Documents Database design (data models) Interface design (CPS) Data Acquisition, Conversion & Integration Plan Testing Plan(s) Documentation Plan Training Plan Implementation and Transition Plan Schedule and Work Plan WBS and WBS Dictionary Responsibility Assignment Matrix Implementation Schedule TxPROS PMP updates Communications Plan Project Organization (vendor resources) Risk Management updates Issue Resolution Plan Change Management updates

PHASE II

MAP DATA ACQUISITION AND INTEGRATION (10%) Integrated data base GIS map of on and off system roadways with full attributes Map data maintenance plan

PHASE III DEVELOPMENT AND TESTING (20%) Functional Software and Satisfactory test results for: Mapping Modules Restriction Management Modules Routing Modules Reporting Modules TxPROS PMP Updates

1 - 2


SCHEDULE 4 (CONTINUED)

PRICING SCHEDULE

ANTICIPATED DELIVERABLES

PHASE IV TRAINING AND DOCUMENTATION (20%) TxDOT Training Completion Certifications End-user Training Completion Certifications TxDOT User Documentation Technical Documentation Customer Documentation TxPROS PMP Updates

PHASE V IMPLEMENTATION AND ACCEPTANCE (30%) Completed Transition Plan Parallel success confirmations Acceptance Documents Business Area Acceptance Technical Acceptance TxDOT ISD Technical Acceptance TxDOT MCD Technical Acceptance TxPROS Project Board Acceptance

ADDITIONAL ITEMS PRICE

Cost of data acquired in Phase II $

License fees $

TOTAL OFFERED PRICE OF PROJECT

$______________________

If optional hosting is offered, respondent shall provide a detailed breakdown of a pricing structure:

Optional Hosting

$______________________


2 - 2