Agency | R&H | Primary R&H Business Objectives | External Business System Integrations | 3rd Party Tools to Extend R&H Functionality | Agency Developed Custom Software (related to LRS/RI) | Other Comments | Centerline Mileage | LRS Editors | Event Editors | Total Editors | Status Updated | ||||||||||||||||||||||||||||||||||||||||||||||||||
General Status | Version | Maintain LRS Network | Number of LRM | Maintain State Only, or State & Local | Maintain Events | Number of Events Being Maintained (ex - NHS, roadway width, shoulder, etc.) | Number of Unique Event Editor Applications | Top 3 Benefits to Business | Top 3 Performance Impacts Business | Bridges | Pavement | Maintenance | Capital Projects | Financial System | Traffic Monitoring | Collector Integration | Vendor 1 | Software | Purpose | Performance Status | Vendor 2 | Software | Purpose | Performance Status | Vendor 3 | Software | Purpose | Performance Status | Name | Purpose | Technology | Performance Status | Willing To Share (provide contact info / location) | ||||||||||||||||||||||||||||
System (version x) | Integration Type | Performance Status | Additional Needs | System (version x) | Integration Type | Performance Status | Additional Needs | System (version x) | Integration Type | Performance Status | Additional Needs | System (version x) | Integration Type | Performance Status | Additional Needs | System (version x) | Integration Type | Performance Status | Additional Needs | System (version x) | Integration Type | Performance Status | Additional Needs | Assets in Collector | Integration Type | Performance Status | Additional Needs | ||||||||||||||||||||||||||||||||||
Ohio DOT | Production | 10.5.1 | Yes - R&H Desktop Extension | 1 | State & Local | Yes - R&H | 83 | 1 | 1. Potential integration functionality 2. Potential workflow management 3. Potential replacement for labor intensive BTRS process | 1. Issues with core R&H product result in significant productivity losses (ex - ALRS inconsistencies & related event behavior performance) 2. API limitations (lack of interaction with LRS_EDIT_LOG) 3. Inconsistent workflows / use of tools across ArcMap tools and R&H tools | Benteley InspecTech | Manual | Automatic Integration Needed | Deighton dTIMS | Manual | undecided | Agile Assets 6.9 | None | Not exploring | Custom In-House | Manual | Works, labor intensive | Automatic Integration Needed | Custom In-House | Manual | Works, labor intensive | Automatic Integration Needed | MS2 | Manual 2-way integration | In development | TBD | ESRI Collector | Manual 1 - way custom python script / REST | Acceptable | Automatic Integration Needed | Transcend Spatial Solutions | Validation Assistant | data quality checks | enables data validations | BTRS | distributes LRS & RI data to enterprise | Mainframe, Java, DB processes, scripting | Labor intensive | Currently having system configuration & workflow issues resulting in significant data quality issues | 121,759 | 9 | 9 | 9 | 4/26/2018 | ||||||||||||
WVDOT | Production | 10.5.1 | Yes - R&H Desktop Extension | 2 | State & Local | No | 0 | 0 | 1. One authoritative LRS 2. Seamless integration w/ other ESRI ArcGIS applications 3. Flexibility to manage events | 1. Async of LRS due to business rules 2. Challenging integration 3. Lack of accuracy from GIS | Benteley InspecTech | Manual | Integration Needed | Deighton dTIMS | Manual | Integration Needed | Agile Assets 6.9 | 1 way (under development) | Integration Needed | Custom In-House | Manual | Works, labor intensive | Integration Needed | Custom In-House | Manual | Works, labor intensive | Integration Needed | Transmetric | Manual 1-way integration | Integration Needed | ESRI Collector | Manual | Integration Needed | None | Implementing Event Editor for managing roadway characteristics; implementing a workflow to publish LRS | 38,000 | 5 | 5 | 4/26/2018 | ||||||||||||||||||||||
MnDOT | Production | 10.5.1 | Yes - R&H Desktop Extension | 1 | State & Local | Yes - R&H | 40 | 4 | 1. Authoritative Source 2. Manage events effectively 3. Utilizing the LRS .API | 1. Constant issues with core R&H product 2. Complexity of training new people for R&H 3. Challenging integrations | SIMS | undecided - dependent of carto-realignment fixes | undecided | n/a | Agile Assets 6x | 1 way | working | Custom In-House | Semi-Automatic | works | FMIS | Automatic via ETL | Works | Jackalope (High Desert Traffic) | None | In development | Carto-graphic realignment issues caused Traffic to not integrate | ESRI Collector | Manual | Integration Needed | Our Desktop editors also perform event edits. | 138,794 | 5 | 10 | 10 | 4/23/2018 | |||||||||||||||||||||||||
Kansas DOT | Testing | 10.6.1 | Yes - R&H Desktop Extension | 2 | State & Local | not yet, performing network cleanup ops | 100 | 0 | 1. combine separate LRS systems to one system 2. Implement REST interfaces to LRS based busines systems 3. utilize partnerships with NG911 and GIS offices | 1. implementation 2. Centerline/Network attribute and measure validation 3. Temporality | AASHTOWARE BRM | test | develop | test | Internal, Custom | custom | development | test | custom | custom | develop | test | custom In-House | custom | develop | test | custom In-House and FMIS | custom | develop | test | Jackalope | develop | develop | test | Signs, Rail crossings, sidewalks, lights, bells, parking lanes, turn lanes, high water marks, WiFi access points... | manual | portions in production, other portions vailable but not implemented | documentation, educational materials, communications | Transcend Spatial Solutions | implementing | 1spatial | 1spatial 1integrate | data validation and enhancement, conflation, change detection, correction processing | interface between RH centerline and source NG911 centerline geometry | 143,000 | 5/9/2018 | |||||||||||||||
Indiana DOT | Production | 10.5.1 | Yes - R&H Desktop Extension | 2 production +1 development | State & Local | yes - R&H | 98 | 9 | 1. Single source of truth 2. Integrates with other systems 3. Is accessible | 1. ALRS System administration skills pool depth 2. Mission and redundancy planning 3. Stakeholder involvement in the network edit process | Bentley InspecTtech | Internally developed 2 way integration | Phase 1 Acceptable Phase 2 in development | Deighton dTIMS | System, on demand | development | test | Agileassets 7.0 SP6 | 1 way | development | test | Custom In-House | custom | production | method made redundant by dTims integration and scoping workflows | Custom financial app integration with Event Editor for FMIS | Auto notifications with manual project locations entry | Effective but Event Editor is labor intensive | method made redundant by dTims integration and scoping workflows | MS2 | 2 Way integration | development | test | ADA, Retaining Walls, Cores, Slides, Luminaries, dTIMS Recommendations, Small Culverts, Patching Rx, Random Notes and Stuff, Special Markings and many more | None planned with the exception of a new Maintenance planning playbook. | Small Culverts (largest inventory) -performance is terrible. Others are OK. | further testing of our collector / ALRS integration scripts/process | Transcend Spatial Solutions | Productivity tools suite, Road Analyzer | Intersection manager and strip map | IM - process is in development RA is in production | HNTB | python scripting | Integrate Collector with Federal Rail Administration to maintain crossing data that the INDOT Rail division is responsible for | Operational May 2018. | Many internally developed systems interface with the ALRS for authoritative inventory and attributes. | C#, python | production | Not really stand alone or realistically distributable, N/A | Adding Rail network to R&H, May be adding trail networks to R&H | 109,000 | 2 | 100+ | 100+ | 6/12/2018 | ||||||
New York DOT | Production | 10.5.1 | Yes - R&H Desktop Extension | 1 | State & Local | yes - limited asset events in Event Editor. Roadway Inventory to be established in R&H in 2018 using custom interface. | 4 | 2 | AgileAsset 7.0 | COTS R&H / Agile | Agile system in production; integration pending Agile upgrade to 7.3 | linear bridge event locations are currently being verified in Event Editor | AgileAsset 7.0 | COTS R&H / Agile | Agile system in production; integration pending Agile upgrade to 7.3 | Current custom New system wil be AgileAssets 7.3; expected 2019 |
Is there a way states can update their information?
Like: who is currently running 10.6.1 R&H/ArcGIS AND 7.3 Agile Assets/TAMS? Are you in production, or testing? And how is that going?
Hi Nicole, I added you and some others as editors of this document.
Hi Kyle, I'd like to request access to edit this document on behalf of the Michigan Department of Transportation. Thanks!
-Meredith
more editors added - I think we have at least one from each state on the list, plus Arizona and Oklahoma now.