For whom the chaos calls
Alex Bruskin
Bespoke Generative AI for Engineering & Manufacturing (PLM, MES, ERP) | Cloud Native | Air Gapped | System Integration | Concepts, Technologies, Execution
One common theme from both history and technology is a perpetual struggle between simplicity and complexity. Simplicity is about energy efficiency and reducing the chance of errors, all at the risk of being trapped in a niche habitat. Complexity is about being clever, having more options to adapt and expand, all at the expense of bleeding energy and increasing the chance of errors.
Nature tends to balance simplicity and complexity by trimming excessive manifestations of either, though humans have become quite proficient at increasing complexity while delaying (or even avoiding) the inevitable exhaustion.
Proper constraints define structural rigidity and expansion boundaries within a given environment, so that simplicity and complexity can safely coexist. Well-defined constraints empower, while poorly defined constrains cause suffocation or runaway complexity. The former stifles innovation; the latter can lead to a vicious cycle culminating in a full systemic collapse .
As usual, Hollywood is helping us to comprehend the relationship between simplicity, complexity and constraints.
The engineering and manufacturing means of production represent a super-complex and rather fragile function of Newton 's, Moore 's, Conway 's, Parkinson 's, Murphy 's, and other laws. They are spurred by in-house innovation and competition, restrained by corporate limbo, strangled by government regulations, and torn apart by growing supply chain troubles, cyber threats, and societal chasms.
The modern engineering and manufacturing environment is simultaneously split by explicit functional constraints into design , purchasing , manufacturing , assembly, MRO , etc., and it is leaking and tearing at the seams. This is particularly evident when design complexities spill into production and distribution. Far too often, massive variations in PLM /CAD are 'thrown over the fence' to the production organizations, causing complications and delays, with each upgrade creating more bumps on the road.
There seems to be no present industry-standard expectation for PLM to be easily deliverable for downstream consumption. While PLMs must often handle multiple CAD formats like CATIA and NX , procurement, build, and inspection should not care. Their input must always be as simple as possible: for example, JT for 3D viewing, PDF for 2D documents, and something consistent for the structures. Perhaps the next paradigm shift will be the PLM creating a standard CAD-agnostic output. That would sever the umbilical cord and install a safety constraint between competitively unique design sophistication and desired production and distribution simplicity.
PDF is (obviously) a universal standard for document exchange between teams, business, and the government: it doesn't matter what the authoring tool was; anyone can read the result as long as it can be sent via PDF. Sadly, there is no PDF-like medium that simultaneously meets ISO precision and popular adoption for CAD.
While 3DXML and PLMXML offer some downstream viewing options, they are not ISO, and as such are relatively unpredictable. And then, there is a long-term data archiving dream: LOTAR 's ISO?14721 model already provides such interoperability infrastructure. The LOTAR model already covers critical 3D CAD information, composites, harnesses, etc. Perhaps the right path for PLM systems is to align their entire downstream output with LOTAR?
Interestingly, one of the big remaining hurdles for LOTAR is Semantic PMI . While it has been adopted by ISO, CAD vendors and the industry in general are still lagging behind. For example, from what we know about experiments converting CATIA to JT, the presentation of PMI is consistent, but the Semantic values are not. The industry needs time to untangle the various Semantic terminologies across multiple platforms.
Speaking of the bigger picture, the Western industry still owns highly sophisticated intellectual property, hardware, software and energy systems, yet its long-term survival depends on unrestricted access to offshore materials and on-shore availability of a motivated and competent workforce . These are no longer guaranteed with the present turmoil in the world and within Western societies - even if things do not get worse.
The solution for manufacturing may come from extreme automation. Complex-inside and simple-outside AI engines will handle swift alternative material and design ideas, and should even compensate for the reduction in workforce engineering expertise. The remaining loyal and competent humans will be assigned to higher-level decision-making and control.
By the way, Bourbon-driven software development practices offer a successful and safe paradigm for navigating the storm of simplicity, complexity and constraints on a grand scale: very small changes deployed daily or even more frequently, using hardened containers , and along the lines of zero-trust security .
We at Senticore apply our hearts and minds to the wise inquiry of all things simple and complex, and have a keen eye for the right balance. Talk to us about mapping the simplicity, complexity, and constraints of your engineering and manufacturing environment, so they can all evolve in harmony towards successful outcomes.
Originally published at Senticore blog .
Owner of TECH-NET.
2 个月What is a PLM Guru? Most of these guys are Infotech Specialist with data management experience only, others have Mechanical Engineering Degrees but have not spent any time as Mechanical engineers. These are BSME, MSME and even PHD’s in engineering. I chuckle as I read many of the profiles of BSME and MSME working in PLM! I wonder what their dream was for a career in engineering? I am sure it was not "Data Management". The document control system of the past was managed by admin people. Engineers were not even involved in the documentation. The draftsman were "The Keepers of the Engineering Documentation Keys" Let’s take a look at some of their qualifications. These are the top PLM posters. ·???PHD Civil Engineering – Never even did any “Civil” engineering, software development only ·???BSME - not one day of engineering – Started at PTC ·???BS Aerospace – 4 years engineering – 13 years PLM! Nope, none in Aerospace! ·???Engineer’s Degree in Information Technology?? What does that even mean? ·???PHD Mechanical Engineering – Development of software only? Engineering Documentation ?A Primer for the PLM Guru! https://tecnetinc.com/Engineering%20Documentation%20Defined%20for%20the%20PLM%20Guru.html
Owner of TECH-NET.
2 个月Today, engineering is shackled by PLM, MBE, MBD, VR, Digital Transformation, Digital Twin and so much more. All under the control of the InfoTech Gurus. “Equipped only with drafting tables and slide rules they nonetheless produced a prototype that made its first flight on April 10, 1959. By March 17, 1961, the T-38 officially entered service with the Air Force – less than two years after its first flight.” T-7A Delays Compound Pilot Shortage, "Expose Digital Engineering Pitfalls" https://www.thedrive.com/the-war-zone/t-7a-delays-compound-pilot-shortage-expose-digital-engineering-pitfalls
Owner of TECH-NET.
2 个月This was the recommendation to the prior CEO. The new CEO will do no better. They were removed from a functional engineering system at the turn of the century. Engineering and manufacturing is driven by documentation. This was solved a century ago. Sadly, the brilliant Infotechs today have never looked to the past for solutions for today's problems. Recommendations to the New Boeing CEO https://tecnetinc.com/Recommendations%20to%20the%20New%20CEO%20of%20Boeing.htmlof another “Chaos is always the result of trying to reinvent the wheel in a place where the wheel is very well defined.” Most of Boeing problems are caused by poor computer implementation in engineering and manufacturing. The computer’s basic tenet is to cut costs. The operations were put into the hands of the CIO, who probably had no experience in engineering or manufacturing. There are very few short cuts in building airplanes. They threw out decades of proven systems and standards and eliminated the backbone of engineering, the drafting group. One thing all C-Suite, managers, engineers and draftsmen should know: "Murphy is always sitting on your shoulder"
Bespoke Generative AI for Engineering & Manufacturing (PLM, MES, ERP) | Cloud Native | Air Gapped | System Integration | Concepts, Technologies, Execution
2 个月Ros Poplar Sara O'Neil-Manion certain part here connects to some of your regular concerns.