I wanted to end the last year with a look back, far back, all the way to the origins of time. Revit time, that is. It ended up taking a bit longer than planned, so here it comes now at the beginning of this year instead.
In December I mentioned the topic of the history and origins of Revit, and promised to see whether I could dig up some more on that. A thread listing the Revit Timeline is available on AUGI, and a short description is given in the history section of the Wikipedia article on Revit.
I asked my colleagues in the Revit team whether they could contribute some titbits on the early times to flesh this out a bit, and reaped a ripe harvest of anecdotes from David Conant, Matt Jezyk, and Richard Taylor on the company and players, and from Emile Kfouri on the Revit API.
Dave: In the beginning, there were two PTC alumni Leonid and Irwin. Each, after spending some time enjoying not working, began thinking independently about where they could next use their experience. Both identified building and construction as a field where the potential benefits of design computing were largely unrealized. When, after talking, they discovered they were both interested in the same issue, they decided to run with it. After about 6 months of working over their concept, they wanted to get feedback from actual architects. Through some serendipitous connections, I presented myself to them thinking this would be an interesting conversation with some people with yet another pipe dream. It soon became obvious to me, that I should abandon my attempts to build various FM connections to AutoCAD as shareware and work with these guys who had the chops to provide something of real substance.
Our office for the spring and summer of '98 was a 5 room space hidden behind and above a Domino's pizza joint on Rt. 9. Its most distinguishing feature was the large collection of 'genuine oil paintings' featuring sad clowns, big eyed puppies, and cliché landscapes all left by the previous tenant. As I was only a consultant at that point, I would drive out there after my day job and engage in hours long discussions on the architecture/building process and on what we could do with a complete building model. I worked with them to document the ideas as planning statements and then as a paper prototype. We took these around to a number of local architecture and engineering firms to get some validation of the ideas. We also brought along venture funders to help build their confidence in our concept in preparation for getting funding. One of the comments that seemed to sum up the response was 'I don't think you can pull this off, but if you could do this, it would be the Holy Grail'.
By the end of the summer, I had quit my day job, talked Leonid into a higher salary so that I could buy a second car, and come on full time. At that point there were 5 people in the office. All funding was still coming out of Leonid and Irwin's pockets, but VC money was just around the corner. By September we were hiring the 7th person and it was time to move. By virtue of a two week sooner availability, we took space on Speen St in Framingham, overlooking the Turnpike toll plaza. In this office we got the first VC money and began serious hiring including a CEO and a number of people still in the organization to this day.
I could go on, but that would go beyond the 'short' history. Some items of interest:
Matt: Oh boy, this could turn into a long thread. Here are some more old-school data points:
Richard: I started in April 2000 just before the release of 1.0 and the big AIA show that Matt refers to. I remember several times at the AIA show being told to quiet down because I had a microphone that seemed to be on full blast directly toward the Autodesk booth.
In Revit 1.0, we had the AccuRender rendering engine, but no way to save the image! You had to run a rendering and then take a screen shot to capture and save the rendering for inclusion in any sheet or drawing. That was just one of many interesting work-arounds.
We launched Revit 2.0 at AEC Systems in England in August or September. My understanding was the VC people wanted to see an expansion into international markets very early on. I was lucky to attend with Dave Lemont (CEO) and the freshly minted 'sales team' from the UK. I remember staying up until 5 in the morning at 'My Hotel' bonding with the CEO and sales team and telling WAY TOO many personal stories.
Emile: Well, Dave, Matt and Richard bring a very interesting perspective because they came in at the ground level. I arrived just before Revit Building 8 was released which was also the first official API release. I was brought in as the Revit API Product Manager but for a few months I also worked as the Revit Structure Product designer.
Originally the API was built specifically to support a single workflow – getting the analytical model out of RST into a structural analysis application and getting the results of any structural member changes back into Revit. There was a single person Giles Gilbert working on the API and it is quite amazing what a single person was able to do given the three realties he had to work with:
All this while trying to figure out what a BIM API should really look like and how it should work. Needless to say, the first API left much room for improvement when looking from the outside in, but was quite an accomplishment when looked at it from the inside out. During the next few releases through Revit 2008 we worked our tails off to build out a larger team, improve our requirements gathering from partners and scale our training, documentation etc. At this point we were still getting features from the feature developers and then figuring out how to build an API around them. A quick-back-of-the-envelope calculation made us realize that if we continued along this path there would need to be as many Revit API developers as there were Revit internal developers just to keep up with feature development and expose existing features.
So starting with the development of Revit 2009 we started our transition to what I call API Centric Development. The idea is that the API is developed and exposed at the same time as the features and by the same developers. We started off slow and had a few successes. For the past couple of development cycles we have been doing almost 100% API centric development.
Beyond API Centric Development the other major shift that moved the Revit API forward was the concept of Asynchronous Development when the Revit team and the rest of Autodesk started to develop applications on top of the Revit API outside of the regular development cycle. The best three examples are probably the Workshare Monitor, the Revit DBLink and the REX based applicators that are still some of our most used applications. REX specifically showed everyone inside and outside Autodesk that Revit could be a viable development platform.
The journey from a single API developer and a few partners to what we have now has had many great memories. In the first few years I used to know every single partner, their business goals, their needs and even their hobbies. Then the Revit community working on the Revit API ballooned to the point that I could not even keep up with whom was developing what. The Revit API developers went from needing to respond to every API related support question to just providing second tier support as ADN has ramped up their skills. We now look at Revit as a development platform and always look to see if and how features can be developed purely on top of the API – eTransmit is a recent example of that.
So what does the future look like for Revit? Well, I continue to see it getting brighter and brighter. It is more often than not that I find partners doing amazing things with the Revit API that impress me or that I did not think possible. Looking at the dedication of the Revit team to the API and the platform and knowing some of the things we plan on delivering in the next few releases I sometimes admit I get a little bit giddy.
Much has changed in the past few years – I handed the Product Manager responsibilities to Anthony who has done an amazing job continuing to push Revit forward. I now hear people all across the organization talking about how to leverage the API. I continue to see external developers who are working on the Revit API being very passionate about Revit and continue to pressure us to make the API even better.
In summary I would say if people have seen our humble beginnings, our accelerated progress in the API for the past few years they may wonder what else we have up our sleeves. The answer is you ain't seen nothing yet!
Adendum by Kirshan Kumar, BIM Manager at SYSTRA India, on Oct 1, 2014:
The History is now the future.
Revit was created in 1997. It is currently in it 33rd release. 2 to 3 releases a year.....
Revit = Revise Instantly
Revit was developed by individuals that came from the company PTC, Parametric Technology Corporation. Revit was developed specifically with Architecture in mind and was purpose built for Architects by Architects. To that point, the majority of the product development teams are architects or come from a design and construction background. The Revit Building application has been developed as a purpose built tool for Architecture and is the only completely parametric Building Information Modeling tool available.
AutoCAD is the de facto standard non-specialized CAD solution and its file formats DXF and DWG are the most common for CAD interchange. Since the late 1990's, the company made a concerted effort to provide a product for every solution in the industry, often purchasing competing companies and technologies.
In 2002, Autodesk purchased a competing software called Revit, from Massachusetts-based Revit Technologies for $133 million. Revit, for the building solutions and infrastructure group and Inventor for the manufacturing group, formed the foundation for future Autodesk products – a strong departure away from their 20-year old AutoCAD software code.
Prior to Public release – Charles River Software
Product released to Public – Revit Technology Corporation
Autodesk Revit
Structural Version of Revit
MEP Version of Revit