While I can't sing as well as Basia, it is a new day for me.
Today, I sent out the "last day" email to my fellow and former colleagues at Jacobs Engineering. I have been on Company Convenience Leave for the past 40+ days (which is basically an unpaid furlough in which the company hopes to bring you back), and just couldn't wait anymore to determine whether or not it was going to happen for me.
For those who didn't know, I worked in the Global Buildings portion of Jacobs... a business division of the giant Jacobs, but for all practical purposes, an A/E firm within a giant EPC firm. I did many things, but mostly around BIM (Building Information Modeling), Multi Office and Multi Discpline project execution, and other Operations things.
It was a good gig, and I got to meet a lot of great people and work on a bunch of cool projects. But life goes on, and I was put on "CCL". There was no guarantee they would bring me back, so I decided upon a new route.
So, as of Monday, I will be working at...Black and Veatch! I'll be working in the Energy Division of B&V right here in the Kansas City area (a 15-20 minute commute for me from my home in Olathe to Overland Park.)
It's a lot of different things, but basically, they've been doing what I would call BIM or "Intelligent 3D Design" for years, and I'm going to come help out and do what I do (project delivery, mentoring) across all disciplines, not just buildings.
I hope to keep doing what I am doing with many of the friends and business colleagues I've met and worked with over the past few years...and of course I'll be on Twitter.
I do want to thank all of those who supported me in my quest to find a new situation, those who went out on a limb to get me on board with their firm, those who gave ideas, and all of those who provided encouragement.
It's a new day for me...
Thursday, September 20, 2012
Monday, September 17, 2012
USACE BIM Requirements update
In 2006, I had the opportunity to be a founding member of the USACE BIM Advisory committee...a group of like-minded individuals working with the United States Army Corps of Engineers (USACE) to put together a set of BIM Deliverable requirements.
This group, with folks with various capabilities and differing softwares used in a BIM process put together a progressive set of requirements and Contract Language commonly known as : Attachment F. AttF was one of the first public versions of a tight set of contract requirements and deliverables.
One major item was that the requirements were in a Narrative format...that is, the Corps said "model walls (or doors, or AHU, or equipment, or utilities...or..or...or...) with the necessary intelligence to do..." well, whatever you need to do...produce documentation, provide visualization, get ready for O&M,
And all was well....until....it got into use and human nature intervened. While most did their best, and many did what was intended, many folks tried to get around the requirements, or not deliver in the software format required, or argued the requirements, or said they weren't specific enough, or what defined "necessary intelligence", or..or..or..or..
Well, times, they are a'changing...
As the group continued to evolve, as the private sector's capabilities evolve, and the needs of the Corps and their clients evolve, it was time to update the requirements...and make it less 'narrative'....tie it down better so the Corps gets useful information above and beyond the 3% of design time and 4% of construction time in an asset's life cycle.
So here it is: The Minimum Modeling Matrix - Otherwise known as the "M3"
The M3 is a tool in spreadsheet format that Project Teams can use to understand what the Corps wants in a Model deliverable, no matter the format. The idea is that you match your scope against this PRE-FILLED sheet. I say "Pre-Filled" in Caps because you don't have to fill it out...the Corps is LAYING OUT what it wants and how it wants it.
Oh, and it's organized according to standard Classification systems, such as OmniClass, UniFormat, and MasterFormat...so everyone along the life cycle (the designer, the contractor, and the owner) can play in the pool.
https://cadbim.usace.army.mil/ is the link to the headline
https://cadbim.usace.army.mil/MyFiles/3/0/8/USACEBIMM3.pdf is the direct link to the announcement.
https://cadbim.usace.army.mil/USACEBIMMinimumModelingMatrix is a link to the M3 itself.
First, read ALL the instructions. Yes, there are instructions. There is information there about Level of Development AND Element Grade. AND an FAQ.
Second, understand while there are other efforts going on in the industry to do something like this, this effort was for the Corps, by the Corps, with Corps specific needs in mind...
Thirdly, it's not meant to be a "template" that you can use on any project anywhere.... It's meant for you to follow on USACE projects, and for you to use and make a deliverable...AND as a communication tool on your project team...AND..AND..AND.
Is it authoritative? Is it "militaristic?" Sure it is...it's the Army! They know what they want, so do it.
Anyway, check it out (use the PDF link first, read the stuff behind the why)...and we go from there.
Cheers!
This group, with folks with various capabilities and differing softwares used in a BIM process put together a progressive set of requirements and Contract Language commonly known as : Attachment F. AttF was one of the first public versions of a tight set of contract requirements and deliverables.
One major item was that the requirements were in a Narrative format...that is, the Corps said "model walls (or doors, or AHU, or equipment, or utilities...or..or...or...) with the necessary intelligence to do..." well, whatever you need to do...produce documentation, provide visualization, get ready for O&M,
 |
| A Section of the Attachment F with the old Narrative Requirements in Section 4 |
And all was well....until....it got into use and human nature intervened. While most did their best, and many did what was intended, many folks tried to get around the requirements, or not deliver in the software format required, or argued the requirements, or said they weren't specific enough, or what defined "necessary intelligence", or..or..or..or..
Well, times, they are a'changing...
As the group continued to evolve, as the private sector's capabilities evolve, and the needs of the Corps and their clients evolve, it was time to update the requirements...and make it less 'narrative'....tie it down better so the Corps gets useful information above and beyond the 3% of design time and 4% of construction time in an asset's life cycle.
So here it is: The Minimum Modeling Matrix - Otherwise known as the "M3"
The M3 is a tool in spreadsheet format that Project Teams can use to understand what the Corps wants in a Model deliverable, no matter the format. The idea is that you match your scope against this PRE-FILLED sheet. I say "Pre-Filled" in Caps because you don't have to fill it out...the Corps is LAYING OUT what it wants and how it wants it.
Oh, and it's organized according to standard Classification systems, such as OmniClass, UniFormat, and MasterFormat...so everyone along the life cycle (the designer, the contractor, and the owner) can play in the pool.
 |
| A snip from the Instructions that lays out what the Matrix looks like and how to use |
https://cadbim.usace.army.mil/ is the link to the headline
https://cadbim.usace.army.mil/MyFiles/3/0/8/USACEBIMM3.pdf is the direct link to the announcement.
https://cadbim.usace.army.mil/USACEBIMMinimumModelingMatrix is a link to the M3 itself.
First, read ALL the instructions. Yes, there are instructions. There is information there about Level of Development AND Element Grade. AND an FAQ.
Second, understand while there are other efforts going on in the industry to do something like this, this effort was for the Corps, by the Corps, with Corps specific needs in mind...
Thirdly, it's not meant to be a "template" that you can use on any project anywhere.... It's meant for you to follow on USACE projects, and for you to use and make a deliverable...AND as a communication tool on your project team...AND..AND..AND.
Is it authoritative? Is it "militaristic?" Sure it is...it's the Army! They know what they want, so do it.
Anyway, check it out (use the PDF link first, read the stuff behind the why)...and we go from there.
Cheers!
Friday, September 14, 2012
Whoops...I have a blog!
So...here I am. I totally forgot I had a blog.
I am starting a new position, and have resigned from my old position at my old company. As I was cleaning up some "digital footprint" stuff, I found this: an old Google account with my old company address...and connected to it was : TADA! This blog.
So, now that I have a blog, I may begin to use it like I use my Twitter account.
So here's the stats:
My Twitter account: kcflatlander
LinkedIn: http://www.linkedin.com/in/shawnmfoster
I am starting a new position, and have resigned from my old position at my old company. As I was cleaning up some "digital footprint" stuff, I found this: an old Google account with my old company address...and connected to it was : TADA! This blog.
So, now that I have a blog, I may begin to use it like I use my Twitter account.
So here's the stats:
My Twitter account: kcflatlander
LinkedIn: http://www.linkedin.com/in/shawnmfoster
Vizify: http://www.vizify.com/shawn-foster (this is cool, you'll like it)
----
I will be blogging about various subjects, but mostly around:
BIM and Intelligent 3D design
Kansas City
BBQ
NFL Football
College Football
And whatever else comes to mind
Watch out....here I come.
Subscribe to:
Posts (Atom)