In Part 1, I wrote about how implementing shorter deployment cycle is imperative for companies like AutoX (i.e. companies like Ford, Toyota's and Airbus) and for PLM vendors (i.e. companies like Dassault Systèmes and Siemens PLM). And implementing DevOps practices is the way to achieve these shorter cycles.
In Part 2, I wrote about how to achieve the seemingly impossible dream of dream of major version upgrade PLM version in a Auto company in one month and minor version upgrades in a week. What features PLM vendors should add to support this kind fast deployment cycles ?
In this part, I plan to write what changes PLM Customers like AutoX (i.e. companies like Ford, Toyota, Airbus, etc) have to do in their way of working to achieve fast PLM updates.
DevOps for PLM is imperative for AutoX to reduce the maintenance, upgrade and enhancement costs of PLM at the same time taking maximum advantage of new PLM features in day-to-day work.
I am assuming you (Reader) are the AutoX company.
Point 1 : Understand that you are a 'software company' now. (whether you like it or not)
For you it is actually more complex situation than traditional software company because you have to 'integrate' software into your own workflow. So think about how you will manage source code of your software (configuration management), compiled executables/binaries, release cycles, code integration, feature/bug life cycles, version management, deployment management etc.
Even though you are a software company, you are not probably developing your own software product and you are not a company doing projects for others. You are somewhat like a 'systems integrator'. You have your own unique set of challenges. Unfortunately software literature is usually focused on 'products' or 'projects'. There are very few references available.
Point 2 :You will have to customize the PLM and other Enterprise software for your own needs. Out of The Box (OOTB) will not give you competitive advantage that you need.
- These customization will be done by your own team, PLM vendor, or some third party development company.
- You have to integrate code from multiple sources. These code-bases may be delivered at different intervals, with different technology stacks.
- These code bases will have complex dependencies (sometimes circular dependencies).
- Compiling these code-bases and deploying them in production is a complex task.
- Tracking the deployment metrics and production performance is required.
It is possible to apply the 'assembly line' concepts from manufacturing application (coming from Kanban, Toyoto Production System, Theory of Constraints etc etc) to this software assembly line and thereby improve the efficiency of this assembly line
Please share your feedback.
- Think about dependencies. Identify and break circular dependencies.
- Treat whole program as 'system' and apply 'systems engineer' concepts to streamline workflows
- Apply concepts like controlling WIP, reducing batch sizes etc. The features not yet delivered to end user is 'inventory'. Features underdevelopment is 'Work In Progress' inventory. Time Boxed Sprints of SCRUM is essentially controlling WIP and reducing batch size.
So where to start ?
- Define configuration management tools and practices.
- Which configuration management tool will be used in-house. Which tools will be used by your vendors
- Add every customization in configuration management. (including build scripts, database schema migration scripts, deployment scripts etc etc)
- Define how the code-base delivered by vendor, will be merged in your configuration management tool
- Define configuration management practices in such a way that you can identify what is changed between version easily.
- Mandate that the vendor has to deliver 'automated test scripts' along with source code (and not just test results).
- Major bottle neck in DevOps implementations is lack of automated testing scripts.
- If you need to test manually all new features/bug fixes, then the deployment cycle (i.e. your batch size of features increase a lot)
- Overall not having 'automated tests' reduces efficiency of DevOps implementation
- Define Integration Pipeline
- How the code will be merged ?
- How it will be compiled and executable created ?
- How it will be 'staged' on a test environment ?
- How automated tests will run ?
- How automatic deployment will happen ?
- Every single step in integration pipeline will be 'managed' in your configuration management system.
- Once code delivered by vendor (or released by your in-house team), entire integration process should take less than 1 week.
- Define Integration and release cadence.
- Make sure integration and release cycles are as short as possible.
- Make sure that 'deployment downtime' should be as less as possible. Use newer cloud deployment tools like creating on demand Virtual machines, using Docker containers etc.
- Define a 'sane' agile change management process.
- Make sure 'change management' is part of Integration pipeline.
- When projects/companies move from Water Fall to Agile (especially with code developed by vendor), biggest confusion is about managing 'change requests'.
- Measure everything in production
- Use tools like 'fluentd', 'TICK stack', ELK stack to collect metrics from production deployments.
- Create dashboards which show this production metrics to your team.
- Share the dashboards with your development team. Let them see how the applications they developed are performing in production.
- To facilitate this data collection in production, define design/coding practices which will push the data to these systems.
- In case of mixed deployment (part desktop, part server) define and implement how 'automatic' deployment/upgrade of desktop parts will be done along with server parts
- PLM systems require integration with CAD/CAM/CAE applications and customization of those applications.
- DevOps implementation will require pushing changes in production for these applications as well. An automatic update mechanism will be of tremendous help.
- Building metrics and bug/crash reporting inside these customization will increase the efficiency even more.
Please share your feedback.
Thanks Nitin. Interesting all 3 parts. I dont think it will change in near future considering the amount of specific customization which gets done for some AutoX. But it is a good future.
Post a Comment