1. CRLMS Civil Rights and Labor Management System Wednesday, October 10, 2007 St. Louis, Missouri

2. Before CRLMS

6. CRLMS The Beginning –Need for an AASHTO software “product” that would address all federal reporting requirements of Civil Rights and Labor Management –April 27 th -28 th, 2005 thirty-one (31) individuals representing 13 agencies came together in St. Paul, Minnesota to discuss the need for an AASHTO software “product” to track Civil Rights and Labor Compliance issues. –As a result of the Joint Application Development (JAD) session the Civil Rights and Labor Management System (CRLMS) was born to meet the common needs of the AASHTO member agencies.

7. AASHTOWare ® Benefits

8. States lack resources to develop their own system All states have same federal requirements to meet Cost for each participating state is less than the cost of a state creating their own system Minimize cost to highway contractors

9. AASHTOWare ® Benefits State overhead costs for data collection and storage would be minimized The software is being built on the same next generation Trnsport platform with the unified database CRLMS being developed to integrate with 1) AASHTO Trnsport modules or 2) As a Standalone module

10. CRLMS Benefits AASHTO owns and licenses to state agencies AASHTOWare ® provides long term support and maintenance of CRLMS AASHTOWare ® allows for staying current with ever changing Federal Regulations

11. AASHTOWare ® Technical Review Teams (TRTs) Appointed by TTF –Assist TTF in working with contractor in development of new product/enhancement Chaired by TTF member CRLMS TRT consists of: –Users familiar with product/functions nominated from agencies contributing funding

12. AASHTOWare ® Technical Review Teams (TRTs) CRLMS started with 10 TRT Members –Missouri added –Continue to receive interest from other agencies Business conducted by: – e-mail – conference calls – face-to-face meetings Travel associated with TRT meetings are covered by AASHTO in the development costs

13. AASHTOWare ® Technical Review Teams (TRTs) Each individual on the TRT has to be committed and available to the project Review software prototypes as software is developed Provide contractor guidance on user needs Review and recommend acceptance of results of the software testing Review and prioritize Product Backlog

14. AASHTOWare ® Technical Review Teams (TRTs) –Tony Bianchi – AASHTO Project Manager –Todd Bergland – TRT Chair / TTF / Minnesota

15. AASHTOWare ® Technical Review Teams (TRTs) Members of the TRT –Roger Bierbaum – Special Committee on Joint Development (SCOJD) / Iowa –Rhonda Ringer – Technical & Application Architecture Task Force –Jim Ferguson – Nebraska –Patricia Flowers – Georgia –Patricia Collins – Michigan –Shay Hope – Virginia

16. AASHTOWare ® Technical Review Teams (TRTs) Members of the TRT (cont.) –Joe Weber – New Jersey –Denis Glascock – TTF / Missouri –Charles Groshens – Minnesota –Art Wright – Florida –Andy Penney – Oklahoma –Leslie Wootan-Hartung – Chair Civil Rights Technical Advisory Group (TAG) / Montana

17. CRLMS TRT Team

18. AASHTOWare ® Technical Review Teams (TRTs) TRT meeting – May 2007 TRT meeting – August 2007 TRT meeting – November 2007

19. System Overview and Preliminary Requirements

20. CRLMS is intended to ultimately address the following functions: –Equal Employment Opportunity and Affirmative Action monitoring –Payroll – wage and labor monitoring –DBE/MBE/WBE program monitoring –Civil Rights, labor, on-the job training, and DBE/MBE/WBE federal reporting

21. System Overview and Preliminary Requirements –Integration with, yet capability to operate independently of Trnsport –Access to and use of the system by external parties (for example, contractors, subcontractors, FHWA, cities, and counties) –Data migration from existing relevant Trnsport client / server modules –Provide the base data for DBE/MBE/WBE data analysis (Disparity Study)

22. External Connectivity Desired process for CRLMS – currently awaiting TTF approval

31. Development Process

32. Agile Development –Agile Development – The scope is defined as the work is being performed –Agile Development promotes involvement and interaction of the entire user community –Agile Development delivers working software frequently

33. Development Process Product Backlog –Prioritized list of requirements –Prioritized by TRT 1 month “sprints” build highest priority items Produce potentially-releasable product increments Hands-on evaluation by TRT every iteration Highly-disciplined process Produces standard artifacts but in a different way Measure productivity with burn down charts

34. Development Process Dedicated team of developers and analysts Collective ownership by team Co-location with everyone participating in interpreting requirements, defining backlog items and estimating them Backlog items estimated relative to each other Sprint plan and estimates reassessed daily based on team progress and knowledge gained Retrospective at end of every iteration to identify and leverage lessons learned

37. Priority Use Case DescriptionGroupPriority Appendix A Estimates 12043Maintain Vendor DataDBE1 7 23013Maintain Wage Decisions HeaderLabor2 20 33005Associate Wage Decisions to a ContractLabor3 45 43027Enter/Edit DBE CommitmentsDBE4 20 53028Review/Approve Contractor DBE CommitmentDBE5 7 XX3011Maintain Field Interview DataLabor14 112109Enter Sub Contractor Sublet DataDBE8 45 XX2113Enter Bidders ListDBE10 XX3002Create Modify Electronic SignatureLaborNP XX3012View Edit Contractor Labor Compliance HistoryDBENP 122110Enter/Maintain Month End Trucking DataDBE13 45 133029Review/Approve Contractor SubletDBE10 7 143022Import Payments to Prime ContractorDBE16 45 202107View Basic Contractor InformationContract9 2 44 Alternate Screen CreationITI 85 45 Recommend DB TailoringITI 7 463007Export Contract Certified PayrollLabor 20

38. 82024Maintain Contract Employee and Employment DataLabor11 20 82031Maintain Contractor Employee DataLabor11 7 82082Import Payroll FileLabor16 2 83001Maintain Certified PayrollLabor11 85 83014Import Contractor Employee DataLabor16 20 83021View Certified Payroll ApprovalsLabor15 20 93009Maintain Certified Payroll RulesLabor11 85 103004Check Certified PayrollLabor12 45

39. 62014Maintain Contract Award DataContract7 7 72042Maintain Contract DataContract6 20 143023 Import Contract Amendment (Change Order, Modifications) Data Contract16 20 143024Import Sub-Contractor DataContract16 20 14 Interface from SM to CRLMSTechnical16 45 14 Interface from FM to CRLMSTechnical16 45 14 Inferface from CAS to CRLMSTechnical16 45

40. 152037Enter Payment Data by ContractorDBE18 20 163025Verify PaymentDBE18 20 172026 Maintain Sub Contractor Payment Data DBE17 45 182032Maintain OJT Trainee DataLabor19 45 192050Report OJT Employment InformationLabor20 7

41. R 01 1024 Create Federal 1392 Report 20 R 02 1023 Create US DOT Quarterly and Semi-Annual DBE Award Commitments Report 85 R 03 1029 Create Contract Clearance DBE Participation Report 20 R 04 1097 Create DBE Availability Report 20 R 05 2054 Create Report On the Job Training by Contract and Trade Category 20 R 06 2056 Create Report Showing Payments Made on a Contract 7 R 07 2057 Create Report Showing Progress Toward Transp Agency Goals 7 R 08 2095 Report Contractor/Subcontractor Data 1 R 09 3010 View Month End Truck Report 7 R 10 3019 Create Verify Contractor Data Report 20 R 11 3041 Create Contract Payroll Activity Report 45 R 12 2034 Report Contract Employment Data (total hours, minority and women hours) 7 R 13 2019 Report Contract DBE Subs From Start to Finish 20

42. Involvement Sources for Involvement wT/CRLMS Message Board Preview Site Acceptance Tests Civil Rights TAG

43. CRLMS Civil Rights and Labor Management System User involvement is vital to this process and, therefore, participation by agencies is welcome. If you would like more information, please contact Tony Bianchi, the AASHTO project manager, at tbianchi@aashto.org or Todd Bergland of the Trnsport Task Force at TTF@cloverleaf.net. For more information on web Trnsport, please go to www.cloverleaf.net.tbianchi@aashto.org TTF@cloverleaf.net

44. Questions?