THANK YOU FOR SUBSCRIBING
Network Infrastructure Mag Weekly Brief
Be first to read the latest tech news, Industry Leader's Insights, and CIO interviews of medium and large infrastructures exclusively from Network Infrastructure Mag
Many enterprises has came across the problem of disjunction from high level architecture design down to operational level support. In many circumstances, the business requirement drove the rapid architecture changes, cloud adoption and SDWAN are the best examples in recent years. Due to the business investment and project timeliness, the integration works could carry out swiftly with overwhelming project activities, which led to multiple enterprise network team couldn’t withstand the rapid changes, miscommunication and arguments between the network towers happens subsequently.
In many large enterprises, the networking space usually has a very clear demarcation. Where architects plan for the technology roadmap, engineering design how's tech should implemented in day zero, delivery team implement the changes in day one, where operations carry out the 24/7 support on day two onwards. However, the new technology evolution urges the architect bring in new tech without details knowledge of existing legacy Infra, engineering team who is focus on integrate the new tech with little concerns of how the support team could understand the new traffic flow. Same time, Operation Support team has limited time to understand the new integrated tech with their little involvement from the project, in the consideration of compliance to mission-critical business 24/7 support policies, the Ops team obligated to accept and support the new Infra upon project completion.
"The Successful and Seamless Integration Stem from an Effective Communication, no matter from a Machine or from a Human-Being"
A few conflicts emerging from such vicious circle.
1. With a little consideration to the low-level setup, the new tech integration following the industry best practices might not fit to certain legacy setup. Which could prolong of parallel infra and increase the business investment.
2. The engineering & delivery could implement the new tech at speed to meet the project timeline. Things could go bad whenever existing Infra could not fit with best practices, a “cowboy” type of re-engineer work could happen.
3. It is challenging to document every little low-level change on the project handover document for operation support. With the limited implementation knowledge from operation team, a lot of troubleshooting could refer back to the team who implemented the new tech. It causes the tech handover stagnant between teams.
Regularly communicating between teams is the key to addressing the above-mentioned. Each teams should have a L3 technical person who well verse on their own domain. And everyone should regularly meet and discuss the new tech integration in project early stage. Many concerns and challenges can be resolved once the teams has concurred with the same direction.
Every teams play equally important role from the whole Networking ecosystem. The successful and seamless integration stem from an effective communication, no matter from a machine or from a human-being. Therefore, let's reconnect back each network teams, more regularly.
Read Also
