Not bad.
So Kennith, do you have an engineering skill set are you bring to the table, besides boundless enthusiasm and a gift of communication?
Are you providing the fab shop the prints? Sounds like you are at least familiar with one of the CADDs systems. Which one? How many years?
You know, a Cirriculum Vitae, as it were.
Check your PM thing in a bit.
There is legitimately no reasonable way for me to answer your question in it's entirety here. I'm complicated. My skill-set is whatever it needs to be, and I bring whatever needs to be brought to the table. The longest it takes me to learn a new industry is about a week; but I can shrink it by applying contextually relevant previously assimilated information in real time. I will expand as required, but I've certainly no intent on paying someone that much money if they can't at least replicate an engine (to a serviceable degree) without my help.
I've no intention of pocketing any money or leading their internal project.
So far as my familiarity with the processes, software, and machines, I'm out of date. The last time I touched anything like that I was using MS-DOS on my main computers. I've been demanding others to do that part for me since the day I realized I could get away with looking over someone's shoulder instead of sitting in front of a monitor.
I can brush back up, but I'd rather not. I spend enough time on computers already. I'll do it if I have to, though.
The "alterations" in which I'm personally interested revolve largely around the improved material, radiation and conductivity, dimensional stability, and distribution of mass. That's where I'd prefer to stay, and most of that is a problem that's already solving itself by moving from cast to billet. I'll do what needs to be done, but at this time I don't even know what I'll need to know... As soon as I do, I'll assimilate what's required and make it happen.
Nothing can happen, however, until numerous blocks are observed very carefully for the effects of time and use, as well as model the engine. The same goes for determining how it's got to be made.
There is a limit to what a manufacturer is willing to put up with when it comes to this stuff, and we're also limited by the inability to perform numerous long-term tests, compatibility issues, and the overall engine design; which indeed is a
good design. It just comes from an era in which it was just two more cylinders to make people feel better.
It was a V8 for people who could only afford a V6; little more than a Buick marketing move. It was not intended to be a powerful engine, and I'm sure nobody at Buick thought it would remain in production from late 1961 until what... 2006 or so? When did they stop with the "Coscast" stuff, anyway? I really wanted one of those.
The amount of time required to fully develop the Rover V8 and reclaim 45 years of what amounts to stagnation would cost millions.
Things that will be altered are generally going to be related to the change in production process. Some stuff is easily sorted without a hassle, but other things affect expansion characteristics unevenly, and that's when you'll end up having to test things beyond reasonable capacity. I can't add five pounds of aluminum to one corner and just expect it to be good, as an example; or enlarge certain passages without having to consider what else happens.
It's not my purpose, anyway. I'm not going to pay someone that doesn't already know how to make a V8, and I wouldn't suggest anyone else pay them, either. I'd pay
me if it had to be done, but I don't intend to let anything go that far. If I've got to be the brain in the room, that's when the cash flow reverses or I just go home and watch cartoons.
I grew tired of having to tell people how to do their jobs long ago, unfortunately. I certainly don't intend to do this myself without bringing in some people I already trust to consult alongside me; people who are reliably running trash can lid-sized twin turbo setups on old 3.5 blocks; people who go out and break them, people who are curious enough to have actually paid attention to what's happening in these things, and people who have spent lots of time already improving things quietly.
That starts with looking at newly identified faults and working with them to come up with solutions.
Cheers,
Kennith