<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://communities.bentley.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>MXROAD V8i (SELECTseries 4) - Discontinued Support and use of Input files</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/176147/mxroad-v8i-selectseries-4---discontinued-support-and-use-of-input-files</link><description>We recently received an email with respect to an update to the Bentley Support Policy. Many people in the office took this as a discontinuation of MXRoad but it is unclear if this is the case. However, we do note that MXROAD V8i (SELECTseries 4) will</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: MXROAD V8i (SELECTseries 4) - Discontinued Support and use of Input files</title><link>https://communities.bentley.com/thread/617720?ContentTypeID=1</link><pubDate>Mon, 02 Nov 2020 11:51:16 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:32f84259-db0d-4b9c-be9e-54b3de0659f6</guid><dc:creator>Paul Xiao</dc:creator><description>&lt;p&gt;Don&amp;#39;t be frustrated man.&lt;/p&gt;
&lt;p&gt;&lt;span&gt;With using the template, you could not only easily design a road widening to match existing, also you could control the overlay / inlay / milling depth / analyse and optimize existing crossfall etc, anything you could image in a corridor style model.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;And&amp;nbsp;you could&amp;nbsp;still rub12D on the ground with ORD even in QLD.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;And the 12D&amp;nbsp;users will never have the chance to say &amp;quot;we could do trimesh while MX is a line string model&amp;quot; to you anymore.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Trust me if you don&amp;#39;t you could trust Mark. &lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MXROAD V8i (SELECTseries 4) - Discontinued Support and use of Input files</title><link>https://communities.bentley.com/thread/617704?ContentTypeID=1</link><pubDate>Mon, 02 Nov 2020 10:11:42 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:f15b7830-be4f-4ff1-904a-8eb996b43c80</guid><dc:creator>Yavuz Ozkan</dc:creator><description>&lt;p&gt;Agree with you.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MXROAD V8i (SELECTseries 4) - Discontinued Support and use of Input files</title><link>https://communities.bentley.com/thread/596516?ContentTypeID=1</link><pubDate>Mon, 06 Jul 2020 12:51:04 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:92c8ca4f-290b-4581-9a26-9f9cb21c93fd</guid><dc:creator>Mark Shamoun</dc:creator><description>&lt;p&gt;The drawing production side of things is completely different. ORD has a new drawing production engine so you dont &amp;quot;export to native&amp;quot; anymore and use MX, Inroads, etc. to create your drawings. The new engine is based on dynamic sectioning of your 3d model that can be considered overcomplicated, but I can see where they&amp;#39;re heading with it.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;There&amp;#39;s some pretty good info here about it:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://learn.bentley.com/app/VideoPlayer/LinkToIndividualCourse?LearningPathID=113449&amp;amp;CourseId=129681&amp;amp;MediaID=5015000"&gt;https://learn.bentley.com/app/VideoPlayer/LinkToIndividualCourse?LearningPathID=113449&amp;amp;CourseId=129681&amp;amp;MediaID=5015000&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I know there&amp;#39;s some work happening to add some automation to the process so some potential here, but we are still missing the concept of a nest input file process that would punch out dozens of sets of sections over lunch..&lt;/p&gt;
&lt;p&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MXROAD V8i (SELECTseries 4) - Discontinued Support and use of Input files</title><link>https://communities.bentley.com/thread/596509?ContentTypeID=1</link><pubDate>Mon, 06 Jul 2020 12:36:50 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:bbfb578f-a923-487f-87bd-aa7b6e96a723</guid><dc:creator>Adrian McBain</dc:creator><description>&lt;p&gt;Cheers Mark,&lt;/p&gt;
&lt;p&gt;I&amp;#39;ll bear that in mind.&lt;/p&gt;
&lt;p&gt;I am going to give ORD another try in my own time, based on one of my schemes I&amp;#39;m working on. I need to bottom this out, I don&amp;#39;t want to be pursuing Civil3D if its not going to perform as expected.&lt;/p&gt;
&lt;p&gt;What is the cross section output like nowadays? You will probably remember when OR wasn&amp;#39;t very friendly when selecting which features to display. Every time it processed, the &amp;#39;features&amp;#39; never retained the same name, so was requiring manipulation every time to produce cross sections. Has this been corrected? Is it now a straightforward process?&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Adrian.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MXROAD V8i (SELECTseries 4) - Discontinued Support and use of Input files</title><link>https://communities.bentley.com/thread/596503?ContentTypeID=1</link><pubDate>Mon, 06 Jul 2020 12:25:01 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:df813b4e-2b0f-4aa3-8bad-7c6ee8796fa3</guid><dc:creator>Adrian McBain</dc:creator><description>&lt;p&gt;Hi Chris, hope you&amp;#39;re well.&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve got more excel converters for MX than you can imagine to help automate one thing or another  &lt;/p&gt;
&lt;p&gt;You can&amp;#39;t import whole designs though and all the intricate details you created with code. You&amp;#39;re probably ok in that a lot of your designs are from scratch and thus simple to replicate. Some of our designs have intricacies along the whole scheme and tweaked as such to meet tight constraints. Being able to transfer alignment input files isn&amp;#39;t good enough. We don&amp;#39;t have the time or budgets to be converting past &amp;#39;on-hold&amp;#39; designs or even ongoing designs which will be on site after the withdrawal of mx licences. Any design software should be forwards compatible without redesign.&lt;/p&gt;
&lt;p&gt;I&amp;#39;ll be interested to see why we are being given Civil3D/MX as preferred design tools, when you&amp;nbsp;are using OR. I think I need to get to the bottom of this, because I don&amp;#39;t want to pursue one route, only to be told to switch down the line.&lt;/p&gt;
&lt;p&gt;Cheers.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MXROAD V8i (SELECTseries 4) - Discontinued Support and use of Input files</title><link>https://communities.bentley.com/thread/596502?ContentTypeID=1</link><pubDate>Mon, 06 Jul 2020 12:23:25 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:9ef0d993-b41b-477f-acce-7a65d30fe18e</guid><dc:creator>Mark Shamoun</dc:creator><description>&lt;p&gt;definitely true...&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;We are now limiting our corridors and the design files more for the practicalities for multiple users working on a project vs. processing as we used to with the v8i OR version. Usually 2.5km performs pretty snappy.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;We did a 30km Pacific Highway project in OR SS4 (in the MX environment), but started getting out of memory errors with too much processing and corridor lengths (but still delivered the project thankfully). This issue is now redundant due to the 64-bit nature of the new standalone ORD version and many of the legacy issues, like the one you mentioned, no longer exist since the software was rebuilt in the new standalone version. There are still some minor bugs that are annoying, but nothing close to what we had in the original versions...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MXROAD V8i (SELECTseries 4) - Discontinued Support and use of Input files</title><link>https://communities.bentley.com/thread/596493?ContentTypeID=1</link><pubDate>Mon, 06 Jul 2020 12:07:15 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:93c5d714-50a6-41ca-913d-481fd76e2ce8</guid><dc:creator>Adrian McBain</dc:creator><description>&lt;p&gt;I think peoples perceptions of the software are down to past experiences. OR didn&amp;#39;t perform for that job I worked on but Civil3D was used to complete it. On the other hand you used Civil3D successfully for council work, but not major highway work.&lt;/p&gt;
&lt;p&gt;How are you finding OR with schemes of considerable length? What length are you dividing your schemes in to? References were a problem and took an age to load, and still attempting to load after they had been removed and the drawing purged. This was a major source of crashes. I&amp;#39;d be interested to know if this issue has been resolved.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MXROAD V8i (SELECTseries 4) - Discontinued Support and use of Input files</title><link>https://communities.bentley.com/thread/596490?ContentTypeID=1</link><pubDate>Mon, 06 Jul 2020 11:57:56 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:4f7de38e-d08a-4c7f-8b39-858682a0a313</guid><dc:creator>Adrian McBain</dc:creator><description>&lt;p&gt;I&amp;#39;m quite open-minded to any software and I embraced using OpenRoads when we adopted it for the scheme in Sydney. I think at the time, we were working with a product that wasn&amp;#39;t polished. I much prefer the interface of ORD to Civil3D, but it was frustrating at the time attempting to design something with tools which were not working. There were endless crashes when creating vertical alignments, applying levels tools, and problems producing cross sections. Not to mention the problems with reference files. I&amp;#39;m sure these will have all been addressed in some way by now.&lt;/p&gt;
&lt;p&gt;Having said that, Paul Cusack and Alan Benger in Sydney were excellent in trying to get these problems ironed out at the time.&lt;/p&gt;
&lt;p&gt;My former colleague in Sydney today says he hasn&amp;#39;t used MX much for about a year, they use &amp;#39;12d and Civil3D in their office, saying &amp;#39;maybe openroads down the track when it is better&amp;#39;, but didn&amp;#39;t rate civil3D at all.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I will revisit ORD and see how it performs compared with how it used to.&lt;/p&gt;
&lt;p&gt;I also have a concern where schemes have been put on the back burner because of budget constraints, only to be resurrected a few years later, which does happen in public schemes as funding gets reallocated. What is going to happen with these schemes? If licencing is removed, these will have to be redesigned. You may be able to pull some reference string information, but all the intricacies will be lost. If a software is going to be abandoned, it should at least be forward compatible with the software replacing it.&lt;/p&gt;
&lt;p&gt;We have schemes now which won&amp;#39;t even have started construction by the time these licences are withdrawn? What does Bentley expect us to do with those?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MXROAD V8i (SELECTseries 4) - Discontinued Support and use of Input files</title><link>https://communities.bentley.com/thread/596438?ContentTypeID=1</link><pubDate>Mon, 06 Jul 2020 07:43:57 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:1a9e7050-ddf2-4940-8ad6-ea8f57320c98</guid><dc:creator>jpln</dc:creator><description>&lt;p&gt;HI Guys, Very interesting conversation showing that it is so hard to satisfy all of our users. Not a surprise at all. I started with MOSS in 1991 and have been supported it (technical/Sales) until 2008. I agree the MX command language is superior to any other product. Detailed cross sections are not that easy to produce except by an expert.&lt;/p&gt;
&lt;p&gt;However, I don&amp;#39;t believe Bentley is pleased to abandon any product and does it with no regard to the users.&lt;br /&gt;Even during the glorious era of MOSS it was not easy. Looked as too difficult, for programmers, ...&lt;br /&gt;It evolved to bring more interactivity. Less and less users were looking at linemode. And many input files were there just to automate the design because there were no intelligence in the models. What is very good and we should find a way to bring this in OpenRoads, is that if you read your input file 30 years after, you can still understand what is being done especially if you comment it.&lt;/p&gt;
&lt;p&gt;The market was/is looking for something else even existing users were (and are) still pleased with MX.&lt;br /&gt;No choice for Bentley.&lt;br /&gt;The concept of BIM has not been invented by software vendors. Users are asking for it.&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;However, most of what is being done in MX can be done in OpenRoads including string modelling (and extension of crossfall).&lt;br /&gt;Many things that MX was unable to do is possible in OpenRoads.&lt;br /&gt;New workflows to be found.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MXROAD V8i (SELECTseries 4) - Discontinued Support and use of Input files</title><link>https://communities.bentley.com/thread/596359?ContentTypeID=1</link><pubDate>Sun, 05 Jul 2020 23:05:04 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:5b1896dd-b7cf-42b4-8593-81c15b31fd47</guid><dc:creator>John Keating</dc:creator><description>&lt;p&gt;Hi Mate, unfortunately they don&amp;#39;t get it and never will as they have never actually built a job. MX gave me a competitive edge over all the 12D lemmings out there. In business you need to to differentiate from your competitors not follow them.&amp;nbsp;You can&amp;#39;t beat first principles when it comes to any application.&amp;nbsp;My last 20 years has been major projects, LCT, M2 widening, Pac Hwy various and now Westconnex. All these jobs are road reconstruction. Try and design a road widening to match existing using a template.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Bentley is not interested, they&amp;#39;re running a global business and we MX users are simply not plentiful enough to have a say. That&amp;#39;s why its all about BIM, they&amp;#39;re trying to create demand for new product sales. Back to VBA and LISP for us, although I am sure the gurus in the big design houses will come up with something clever to get us through to retirement.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MXROAD V8i (SELECTseries 4) - Discontinued Support and use of Input files</title><link>https://communities.bentley.com/thread/596306?ContentTypeID=1</link><pubDate>Sat, 04 Jul 2020 10:11:30 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:eea10504-79e8-4868-bb58-8d251fb0ae5d</guid><dc:creator>Chris Andrew</dc:creator><description>&lt;p&gt;Adrian.&lt;/p&gt;
&lt;p&gt;Give OpenRoads Designer one last try before jumping to C3D. Its completely different to the OpenRoads Technology add-on you used before. Yes it&amp;#39;s had it&amp;#39;s issues and there are still some.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Interestingly, enough you can still import alignment input files into OpenRoads Designer and you can use Parametric Constraints in Corridors and Linear Templates as a text input to replicate MX Design Inputs. And these controls are far superior to C3D.&lt;/p&gt;
&lt;p&gt;We&amp;#39;ve developed Excel formulas to convert MX input files for design offsets into parameters for ORD.&lt;/p&gt;
&lt;p&gt;To sum up. Not perfect, not as good as MX but better than C3D IMO&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MXROAD V8i (SELECTseries 4) - Discontinued Support and use of Input files</title><link>https://communities.bentley.com/thread/596288?ContentTypeID=1</link><pubDate>Fri, 03 Jul 2020 22:19:01 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:545ee7f2-b97a-4ab6-8aa7-1096b9c04f5d</guid><dc:creator>Mark Shamoun</dc:creator><description>&lt;p&gt;Hi Adrian, each to their own.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;An interesting fact about the Sydney environment is that OpenRoads Designer is the platform that our road authority and some of the larger consultancies are moving towards from MX. A few like us dabbled with c3d but abandoned it after finding it&amp;#39;s shortfalls (I did spend 2 years at a council using it successfully, but it has limitations in scale so inevitably it fails on highway jobs). NWR was back in the SS3 days when OpenRoads was an &amp;quot;add in&amp;quot;. It&amp;#39;s now it&amp;#39;s own 64-bit software package, so a lot has changed, to the point that we are delivering tender and detail designs of some of the largest road and tunnel projects in NSW in it right now.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Definitely not perfect and it has it&amp;#39;s flaws, but something to be aware of.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MXROAD V8i (SELECTseries 4) - Discontinued Support and use of Input files</title><link>https://communities.bentley.com/thread/596265?ContentTypeID=1</link><pubDate>Fri, 03 Jul 2020 14:21:19 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:6897b8ff-cdd8-4d25-9142-37c2e350bc2e</guid><dc:creator>Adrian McBain</dc:creator><description>&lt;p&gt;Mark,&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve tried all three and 12D, but my experience with OpenRoads hasn&amp;#39;t been a good one, although I&amp;#39;m sure it&amp;#39;s improved since I used it. Some of the functions didn&amp;#39;t even perform correctly, extension of crossfall for example, didn&amp;#39;t work at all. Interesting to see that you are in Sydney, it was the NWRL that I had used it on.&lt;/p&gt;
&lt;p&gt;Likewise Civil3D and 12D have their quirks. They both have their own strengths and weaknesses, but I cannot dictate to a client/organisation which design software to use. I will adapt to whatever is required. If they want MX or Civil3D and there is no MX, then I go Civil3D, as simple as that.&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Adrian.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MXROAD V8i (SELECTseries 4) - Discontinued Support and use of Input files</title><link>https://communities.bentley.com/thread/596231?ContentTypeID=1</link><pubDate>Fri, 03 Jul 2020 10:42:02 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:8e5910ad-eb0f-4d09-b7ea-3e3c4492fe95</guid><dc:creator>Mark Shamoun</dc:creator><description>&lt;p&gt;Hi Adrian, you obviously haven&amp;#39;t used Civil 3d before...MX is in a class of its own for string-based modeling and anyone who has ever used it knows c3d takes exponentially more time to do things vs. MX.&lt;/p&gt;
&lt;p&gt;OpenRoads is far superior to Civil 3d (IMO) for Template-based 3d modeling. I suggest you try them all before making any judgements.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MXROAD V8i (SELECTseries 4) - Discontinued Support and use of Input files</title><link>https://communities.bentley.com/thread/596188?ContentTypeID=1</link><pubDate>Fri, 03 Jul 2020 07:41:33 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:4e2d9d97-fb9c-4a77-86af-cbbf651f8fc9</guid><dc:creator>Adrian McBain</dc:creator><description>&lt;p&gt;Agree with John Keating wholly! Used MX for nearly 30 years and is a proven tool for providing designs quickly. I am currently using it for all designs on one of the UK&amp;#39;s maintenance contracts. For our work output, we have two options, either MX or Civil3D. I&amp;#39;ve use OpenRoads before and was too cumbersome, and at that time so full of faults that I understand it was abandoned in favour of Civil3D after I had left. By the looks of it, I will finally have to jump ship and go down the Autodesk route of products!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MXROAD V8i (SELECTseries 4) - Discontinued Support and use of Input files</title><link>https://communities.bentley.com/thread/556768?ContentTypeID=1</link><pubDate>Wed, 27 Nov 2019 04:30:49 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:f825085b-0be6-4a78-b394-c30baddfc8b2</guid><dc:creator>John Keating</dc:creator><description>&lt;p&gt;Unfortunately Simon Open Roads doesn&amp;#39;t cut it for our work. Neither does Civil3Dud. It was Linemode that made MX unique, is highly efficient and differentiated it from the competition. We work string to string and we build to strings. Templates, objects and meshes are great for demos, selling BIM and selling cool-aid to sales staff, but in the real world on the ground it has proven to be of little value. The standard joke around here is BIM is only good for the BIN. If the MX market is too small for Bentley to maintain then they should have kept their greedy hands off it in the first place.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MXROAD V8i (SELECTseries 4) - Discontinued Support and use of Input files</title><link>https://communities.bentley.com/thread/509475?ContentTypeID=1</link><pubDate>Wed, 06 Mar 2019 10:34:50 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:8e78100c-80c7-4a37-b4e0-e3faca48c071</guid><dc:creator>Simon Pegg</dc:creator><description>&lt;p&gt;Hi Richard,&lt;/p&gt;
&lt;p&gt;OpenRoads Designer is a completely new product. There is no linemode option within it. It does not use MX Commands.&lt;/p&gt;
&lt;p&gt;You will still be able to use&amp;nbsp;MX in the future, but it won&amp;#39;t be developed any more, and we will still be providing support for the foreseeable future.&lt;/p&gt;
&lt;p&gt;The intention is to transition users to ORD.&lt;/p&gt;
&lt;p&gt;I&amp;#39;d be happy to discuss specific requirements, if you want to drop me an email. &lt;a href="mailto:simon.pegg@bentley.com"&gt;simon.pegg@bentley.com&lt;/a&gt; I&amp;#39;d be happy to discuss with you.&lt;/p&gt;
&lt;p&gt;Simon Pegg&lt;/p&gt;
&lt;p&gt;Bentley Civil Support&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>