Views on submitting native files
Views on submitting native files
(OP)
I wondering what other's policy on releasing native analysis files (structural files like STAAD or RISA or pipe stress like Caesar II) to clients for review is. Historically, at companies I've worked at we typically don't do it. I have had a few cases where we are working closely with a client that is an engineering firm and we have released structural analysis input files that they can run themselves at their request.
I used to have a boss that claimed if someone reviewed calcs at that level then they were taking on responsibility for the design. I don't know if this is just something he said to get people to back off or if there is actually some validity to that legally.
I'm not crazy about handing out native files for a couple of reasons. For one, a less than scrupulous company might take your file and just change some dimensions and use it to create their own design. Perhaps a bit far fetched but I suppose it could happen, though I don't lay awake at night worrying about that. Another reason is that I've found when you give someone that much data they tend to question a lot of things. Heck, I'm guilty of that. If I get a STAAD (structural analysis) file from somebody I'll invariably find things that I would have done different. Maybe their judgment was that offsets were insignificant and didn't include them. I might not be convinced and think they should have modeled them. Now we're in a pissin' contest to see who will prevail.
I used to have a boss that claimed if someone reviewed calcs at that level then they were taking on responsibility for the design. I don't know if this is just something he said to get people to back off or if there is actually some validity to that legally.
I'm not crazy about handing out native files for a couple of reasons. For one, a less than scrupulous company might take your file and just change some dimensions and use it to create their own design. Perhaps a bit far fetched but I suppose it could happen, though I don't lay awake at night worrying about that. Another reason is that I've found when you give someone that much data they tend to question a lot of things. Heck, I'm guilty of that. If I get a STAAD (structural analysis) file from somebody I'll invariably find things that I would have done different. Maybe their judgment was that offsets were insignificant and didn't include them. I might not be convinced and think they should have modeled them. Now we're in a pissin' contest to see who will prevail.





RE: Views on submitting native files
RE: Views on submitting native files
TTFN (ta ta for now)
I can do absolutely anything. I'm an expert! https://www.youtube.com/watch?v=BKorP55Aqvg
FAQ731-376: Eng-Tips.com Forum Policies forum1529: Translation Assistance for Engineers
RE: Views on submitting native files
Obvious exception is if you're actually being paid (i.e. in the contract) to deliver native format.
What is Engineering anyway: FAQ1088-1484: In layman terms, what is "engineering"?
RE: Views on submitting native files
RE: Views on submitting native files
RE: Views on submitting native files
Cheers
Greg Locock
New here? Try reading these, they might help FAQ731-376: Eng-Tips.com Forum Policies http://eng-tips.com/market.cfm?
RE: Views on submitting native files
http://www.nceng.com.au/
"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."
RE: Views on submitting native files
RE: Views on submitting native files
I have on several occasions now, done safety calculations by hand using Microsoft Word. I have submitted these to the customer or to the customer's consulting engineer. I am not a professional engineer, so I am not authorized to stamp and seal stuff. This fact is clearly noted on my calculations. Under the circumstances, I have to submit the calculations.
The engineers who review my stuff have come back and asked what the heck I am doing. This has been a useful exercise. My calculations do not show the opto-electronics that make our systems actually work, so IP is not an issue. I archive my emails, so I can verify what I sent out. In my world, I don't see why the customer or his consultant would modify or copy my stuff. Your world sounds very different.
I have attached FEA output to my notes. I explained what I was working out, and I explained my FEA model. I believe I provided enough information that an engineer could reproduce my analysis on their software.
How useful is your FEA model if your customer is not running the same software you are?
--
JHG
RE: Views on submitting native files
$50/hr mechanic work
$100/hr if you watch
$150/hr if you help
Seems like it might apply here.
RE: Views on submitting native files
Whether receive the files or not, we are in fact responsible for the consequences of errors. If a dam fails and kills dozens of people, is a utility insulated from liability if a consultant makes a mistake? Not likely. The NTSB report on the Rt. 35 bridge collapse in Minneapolis made this clear when they placed some of the liability on the owner for the design error.
RE: Views on submitting native files
From a strictly academic standpoint, I actually like getting feedback from other engineers and discussing technical issues. Unfortunately, I live in the real world and the people who pay me want me to design something and move on.
The reason I brought up the question is because I'm aware of a situation where an engineering firm is asking for native files from a vendor (not us) so they can do a more in depth review. The vendor is pushing back with a vengeance, making me wonder if they are hiding something. I was just wondering what other people's policy/experience is and if there is a good reason not to hand out native files.
As I mentioned, I don't submit them as a matter of course but if a client ask I'll give it to them.
Oh, someone asked suppose you're not using the same software. Well, then, of course, it doesn't really make a lot of sense to share an input file with them. In my case, our major client has most of the same software that we have.
RE: Views on submitting native files
What is Engineering anyway: FAQ1088-1484: In layman terms, what is "engineering"?
RE: Views on submitting native files
I would like to understand more about IRstuff's suggestion about using a digital hash signature to ensure that the original file is still intact so you don't have to rely on he said, she said.
RE: Views on submitting native files
But that takes someones time to do that, and if they can't come to an agreement quickly can drag out and lead to issues with accusations over who changed the file and when etc..
I'm not without sympathy for the party not wanting to share the data if it wasn't contractually required, in which case it should have been baked into the cost and relevant configuration control provisions taken as several people allude to above.
What is Engineering anyway: FAQ1088-1484: In layman terms, what is "engineering"?
RE: Views on submitting native files
Even if you aren't submitting files, hash generators can also be used to detect file corruption, assuming you hashed the file beforehand...
TTFN (ta ta for now)
I can do absolutely anything. I'm an expert! https://www.youtube.com/watch?v=BKorP55Aqvg
FAQ731-376: Eng-Tips.com Forum Policies forum1529: Translation Assistance for Engineers
RE: Views on submitting native files
The way I look at it, as an engineer, how do you get more work from the client? You solve its problems and make it easy for them to do work. I assure you, I will come back to time and time again if you make the process of doing work easy for me.
RE: Views on submitting native files
If you hash the files at handover, and keep copies of the generated hashes, then it should be relatively easy to prove that the native (source) files have been changed. Time and date stamps are tricky as they're often file system dependent, and the same file may end up with a separate time / date stamp depending on whose system its stored on. Other things like metadata can also throw the timestamp, thus I'd not recommend using it as a verification of file integrity.
I believe, although I've not confirmed, that CollabNet's SVN versioning tool uses hashing to detect file changes for the purpose of file versioning.
RE: Views on submitting native files
Are we a profession or a commodity?
thread507-89434: Calculations: Personal Tool or Public Record
Check out Eng-Tips Forum's Policies here:
FAQ731-376: Eng-Tips.com Forum Policies
RE: Views on submitting native files
In any case, I don't think it's a question of commodity or not; I'm not even sure how one gets to that conclusion. As you described in that thread, there was a time that transparency was a novelty, but in these times, transparency is mandatory. One reason is that the complexity of the designs being built today is substantially higher than before, and design margins are slimmer.
The notion of a permanent record that can be trusted to be a true reflection of the original submittal works both ways; by the same token where we might worry about customers altering drawings or calculations, we might likewise worry that an engineer alters the calculations, for whatever reason, or that the engineer either retires or dies, and the records are no longer recoverable. As these calculations pertain to the very heart of the PE license, public safety, it's all the more necessary that such calculations are retained for the duration of the structure's existence. If the structure fails or is modified, then those calculations would be the basis by which the design is evaluated. Trying to figure out someone else's design without such records is otherwise guesswork, at best.
TTFN (ta ta for now)
I can do absolutely anything. I'm an expert! https://www.youtube.com/watch?v=BKorP55Aqvg
FAQ731-376: Eng-Tips.com Forum Policies forum1529: Translation Assistance for Engineers
RE: Views on submitting native files
Many, many times I've been tasked to design/calculate in parallel with hired engineering work and then work with the consultant to identify and resolve differences as a means of peer review. Sharing of native files is very beneficial in these cases.
RE: Views on submitting native files
RE: Views on submitting native files
RE: Views on submitting native files
Ron - I realize that this is the intent of a lot of US states in mandating digital signatures, but in this day and age of photoshop, etc. it seems to me that ANYTHING can be altered....am I right?
The digital signature, embedded in an electronic document, will certainly "turn off" if the document is changed....but the graphic used by the digital signature, usually some kind of check mark vs. an exclamation point, can be faked in on a pdf where a potential user down the line wouldn't know that anything had changed....with today's snipping and screen shot tools you can essentially do anything graphically.
This doesn't mean that authorities, investigating a problem/collapse, couldn't determine that the EOR didn't supply a particular detail by investigating the source file....it seems to me it would just would allow others to fake in my seal/signature and digital signature if they really wanted to.
Check out Eng-Tips Forum's Policies here:
FAQ731-376: Eng-Tips.com Forum Policies
RE: Views on submitting native files
RE: Views on submitting native files
RE: Views on submitting native files
RE: Views on submitting native files
I believe there is a difference between submitting a file and providing the file to a client. I use AutoCAD files as an example, the client will need the native to allow it to update in the future (I am basing my comments on OnG industry, but it could be applicable to structural drawings as well)
Tickle