1 / 25

2005 Trns•port User Group Meeting November 6, 2005 Roger Bierbaum

2005 Trns•port User Group Meeting November 6, 2005 Roger Bierbaum. CRLMS Civil Rights and Labor Management System. Why a Civil Rights Labor Management System?. Need for software to record, track and report Civil Rights and Labor Compliance requirements

davis-wiggins
Download Presentation

2005 Trns•port User Group Meeting November 6, 2005 Roger Bierbaum

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 2005 Trns•port User Group MeetingNovember 6, 2005Roger Bierbaum CRLMS Civil Rights and Labor Management System

  2. Why a Civil Rights Labor Management System? • Need for software to record, track and report Civil Rights and Labor Compliance requirements • Required documentation is costly and time consuming for contractors, local, state and federal agencies • Current software available doesn’t meet the needs, too expensive or has other issues • BizTrack, DivTrack, Champ, Outreach Manager, EBO, TRS, TransBot • Many of the functions in Trns•port, but compatible with current Civil Rights requirements

  3. 2004 TUG Discussion • Breakout meeting was held during 2004 TUG in Mobile to determine interest • Enough interest was expressed to generate further discussions

  4. April 2005 JAD • Hosted in St. Paul, MN by MnDOT • 31 participants • 13 states • 2 states via video conference • Draft requirements prepared by MnDOT • 100+ Use Cases • System Requirements

  5. April 2005 JAD • Confirmed need for common software product owned by AASTHO • Software to include both: • Civil Rights • Labor Management

  6. April 2005 JAD • Software should be integrated into Trns•port software • Common database • Trns•port look and feel • Able to operate with as an independent product • Import/export functions to state’s legacy systems

  7. Contract-related Information • DBE Goal Setting on Contracts • Bidders Data • DBE Commitments • Subcontract and Supplier Quotes • Approved Subcontract Data • Prompt Payments • Completed Contract Data

  8. Vendor-related Information • Vendor Data • Addresses • Officers / Staff • Work Classes • Financial Data • DBE Certifications

  9. Employee-related Data • Payroll Data and Tracking • Wage Decision Information • On-the-Job Training Program(s) • Trainees

  10. Reports / Analyses • Semi-annual and Annual Reports on DBE Commitments and Subcontracting • Program DBE Goal Setting • Market Availability • Market Utilization • FHWA Form 1391 • FHWA Form 1392

  11. AASHTO Joint Development Process • States share development costs • Eliminates duplicated development work • Ensures compliance with federal requirements • Licensing structure consistent with other TRNS•PORT modules

  12. AASHTOJoint Development Process

  13. Joint Development Process • Built in currently supported by TRNS•PORT technology (.NET, Agile, Unified Data Model) • Independent of other TRNS•PORT modules (a state would not be required to license other modules to use the system) • Must interface with TRNS•PORT modules, if a state has them • Meet Federal and common state requirements for Civil Rights and Labor Compliance

  14. Joint Development Process • AASHTO - solicit states to participate in the development of a system to track Civil Rights and Labor Compliance • Trns•port Task Force (TTF) - will manage CRLMS due to its relationship to Trns•port products and data • Technical Review Team (TRT) - would be formed to oversee AASHTO Contractor development efforts in conjunction with the TTF

  15. Issues Surrounding Joint Development • Keeping the Software Generic • Satisfying all the Agencies’ Needs • State specific reporting, letters and analysis

  16. Meeting the needs of our Customers • Civil Rights Staff • Responsible for the civil rights programs • Contract letting Staff • Responsible for getting requirements on the contracts with our contractors • Contract administration Staff • Responsible for collecting construction data and data from contractors • IT Staff • Involved in automating processes

  17. Benefits to FHWA • Consistent Federal Reporting requirements • Timely responses from agencies to FHWA

  18. Our efforts to involve • FHWA • Subcommittee on Civil Rights • Subcommittee on Construction • Contractor Associations???

  19. Highway Contractor Involvement • Information would come directly from the contractor: • through a electronic transfer of payroll information • be entered manually through a electronic interface by small contractors • Cost to the contractor should not be an undue burden

  20. CRLMSWhat is the status?

  21. What has happened recently? • AASHTO held meeting with FHWA Office of Civil Rights to determine their interest, and support, of an AASHTO CRLMS module • Subgroup of states has prepared a list of “Must Haves” • ITI has prepared “low cost, likely cost, and high cost” to complete the Must Haves

  22. What is next • Get a commitment from FHWA on which federal funds a state could use to fund CRLMS • Solicitation planned for late this calendar year

  23. Development Schedule • Preview showing – August 2006 • AASTHO Subcommittee on Civil Rights • Initial Release Fall, 2006? • End of Phase 1 Release – 2007?

  24. CRMLS Technical Review Team • Todd Bergland, MnDOT • TTF Representative • TRT Chair • Other members appointed by TTF • Based on states contributing funds • Expertise on Civil Rights and Labor Management

  25. Questions

More Related