Re: Factory engine testing?
Don't ask me how I know about this...I vowed NEVER again to set foot in the Flint Engine plant!
But, in the mid-70's the hot engine test stand system was automated using mini computers to control/run/accept-reject the individual hot engine test stands. An intermediate 'scheduling' mini computer battery was used to interface with the plant's production main frame, and control over-head 'picker' equipment to grab completed engines off the assy line coveyer and move them to/from the individual test stands.
The computer portion of the project (lion's share) consisted of suppling the hardware, writing & debuggng the factory automation control code and doing turn-key installation as a sub-contractor to the prime contractor who supplied the mating material handling system.
Different engines (configuration based) had different run times on the hot engine test stands against GM defined performance tables for run time, run profile and accept/reject criteria. When completed, the system was JOY to behold!
But, let's NOT revisit the PAINFUL ordeal of defining the overall system's performance specification and who was going to eat what cost(s) associated with the lack of definition prior to open bidding and contract award!
Don't ask me how I know about this...I vowed NEVER again to set foot in the Flint Engine plant!
But, in the mid-70's the hot engine test stand system was automated using mini computers to control/run/accept-reject the individual hot engine test stands. An intermediate 'scheduling' mini computer battery was used to interface with the plant's production main frame, and control over-head 'picker' equipment to grab completed engines off the assy line coveyer and move them to/from the individual test stands.
The computer portion of the project (lion's share) consisted of suppling the hardware, writing & debuggng the factory automation control code and doing turn-key installation as a sub-contractor to the prime contractor who supplied the mating material handling system.
Different engines (configuration based) had different run times on the hot engine test stands against GM defined performance tables for run time, run profile and accept/reject criteria. When completed, the system was JOY to behold!
But, let's NOT revisit the PAINFUL ordeal of defining the overall system's performance specification and who was going to eat what cost(s) associated with the lack of definition prior to open bidding and contract award!
Comment