DiscussWorldIssues - Socio-Economic Religion and Political Uncensored Debate - View Single Post

**h0ldem** · 12-09-2008, 11:51 PM

I've worked on a few of these in the past, the largest being the material control on a $4billion capital project.

The model on that occasion was for the key contractor to protect their application and have a 2nd slave system controlling the transfer of information from sub contractors, suppliers, fabricators and main contractors. In this instance, no IP was shared apart from basic interface linking.

I doubt that this is the case in this instance.

What I would assume is that a few Boeing developers working in conjunction
with Renault engineers will create a branch development. What basically happens is that 99% of the standard code is used. However, when code needs altering, it's checked out, altered and checked back in. What this means is that you have two parallel editions of the code with exactly the same backbone but different version numbers. These can be developed as 2 different products but at any time, the branched versions can be deleted or incorporated into the master code to maintain a single enhanced version.

The advantages are that any changes do not effect existing customers codes when upgrading live versions, any enhancements can benefit the core product when fully tested and Renault can have a very cost effective tailored version adapted to their needs and no IP leaves Boeing's systems.

I understand your view of it, but I don't see it like that.

According to the quotes from the above article, the code is being improved to make it efficient for Renault's use and this will be also used by Boeing as it gives them a much better performance than the previous version.
As I see it, the new version can do everything the older could and more and also faster.

As for intellectual property implications, I bet they found a way to agree about the use of the said code.

12-09-2008, 11:51 PM	#36
h0ldem Join Date Nov 2005 Posts 645 Senior Member	I've worked on a few of these in the past, the largest being the material control on a $4billion capital project. The model on that occasion was for the key contractor to protect their application and have a 2nd slave system controlling the transfer of information from sub contractors, suppliers, fabricators and main contractors. In this instance, no IP was shared apart from basic interface linking. I doubt that this is the case in this instance. What I would assume is that a few Boeing developers working in conjunction with Renault engineers will create a branch development. What basically happens is that 99% of the standard code is used. However, when code needs altering, it's checked out, altered and checked back in. What this means is that you have two parallel editions of the code with exactly the same backbone but different version numbers. These can be developed as 2 different products but at any time, the branched versions can be deleted or incorporated into the master code to maintain a single enhanced version. The advantages are that any changes do not effect existing customers codes when upgrading live versions, any enhancements can benefit the core product when fully tested and Renault can have a very cost effective tailored version adapted to their needs and no IP leaves Boeing's systems. I understand your view of it, but I don't see it like that. According to the quotes from the above article, the code is being improved to make it efficient for Renault's use and this will be also used by Boeing as it gives them a much better performance than the previous version. As I see it, the new version can do everything the older could and more and also faster. As for intellectual property implications, I bet they found a way to agree about the use of the said code.
	Quote