these are the slides about a talk that i gave at DevOps Meetup Bern about industrial DevOps, and how manufacturing industries deal with the mindset and practises of DevOps and how it matches "our" software DevOps practises.
and visualized quickly • We have one source of truth • Process cadences are synchronized among teams • People can innovate and see immediate effects or consequences • Changes are reflected over the whole value chain • People should receive, integrate and learn feedback (provided by users or data)
ground to innovate on • They need to see how a part of the system does behave integrated into a complete system rather than isolated • As this can be expensive there are tools such as simulators, digital twins and practices such as 3D printing and fast protoyping to gain insights before the whole product fails.
innovate the value streams need a common ground, or model • This is usually done with digital twins • These look and often behave like their real-world counterparts, enabling us to test things out in real world • This does often not just cover aspects of the thing to be built, but can also be extended to its manufacturing process
and industrial systems failures become very costly and dangerous quite fast • Hence a lot of those processes and standards are regulated or at least internally constrained • It is good practise to apply here quality gates and security tests for infrastructure and software / firmware wherever applicable (e.g. Open Policy Agent) • You can also enforce and assess policies on CAD files and even “ integration test” CNC files to ensure compliance
manufacturing line should be monitored like a software system • By analyzing real time data and analytically feed them back to the digital twin model, both the real-world item and its digital twin can learn and improve • This starts the DevOps cycle again
janmoser
csswizardry
lara
eitanlees
panda_program
sergeychernyshev
notwaldorf
brettharned
smashingmag
bluesmoon
tanoku
mraible
