P 73
GIS Experience
On reporting at Bombay,Don felt comfortable with Reliance management set-up and the whole team
looked him with high respect. That paid rich dividend.
To start with he advised my team to carry out ultimate service departments' interactive exchanges to list down their want list from GIS. He prepared a set of questions and issued to them to answer and then attend meetings to deliberate. He identified various segment of communication service departments and had interaction meeting with each dedicated team. From their want list, he made sure that our GIS team to note down the requisite attribute data for each service. That came out as the listing of various data attribute requirement.. Then with our Network Engineering team , he drafted the data matrix. That was the time he took classes for the GIS/NE team regarding the database management and how the identification of layers have to be arrived in GIS domain.
As we did not have the overall idea of data sets and listing of cities where Reliance plan to launch the communication services at that juncture, to start with we did a make shift server sourced from Sun Systems . Don ensured that the team transported the map data and corresponding attribute listing in that server using Arch Info software. Then came the specific requirement of Network Engineering software ! As my core team members were from instrument fraternity, they had the vision and dream of instrumentation loops that too OSBL-extended to cross country. When those ideas were exchanged, Don came out with the suggestion of having services of NE from Atlanta! Then we got in touch with that management through Don and they were happy to join the game, as they were regular partners for network engineering for ESRI. They deployed Michael Crawford as the core member for NE development,Rest is history.
As members from Reliance were from project execution, they looked for complete cross country cabling and intra city hook-ups data in system. That paved the way for identifying the requisite attributes. Don, Michael and Milind with Jaydip,Harshad Acharya listed the requisite network attributes viz: trench, duct, fibre, slicing etc. As they were all project engineering members, they furnished the detailed specification listing for each item.For the trench- the elevation, trapezium dimensions, length, breadth along with lat/long coordinates to be picked up field survey team. When man hole and hand hole come in back bone, its location co-ordinate along with as built dimensions were picked. During execution, it was decided to have varied number of ducts in the back bone trench depending on the route popularity with potential business traffic.In cities, depending upon city ranking in hierarchy, number of ducts of intra city varied. When it came to cabling, not only the number of fibres data were picked but also the make/test certificates and detailed fibre characteristics data were picked and entered in data base. Then splicing details were picked. We did not realize that the GIS team was issuing the IFC drawings to field construction team and were expecting the construction to issue the as built data. But the network planning team realized that well in advance and they were doing basic engineering(equivalent to P&I D in process plant) and gave requirements to GIS team. The whole process were stream lined and data issue and as built reporting worked like a clock work. As said earlier, we ended working for 36000 run kms back bone and 10+48+212 intra city data capture. At one stage the data volume was as high as 6 terra bytes which called for a super computer with large memory! As things were on high, everything what we wanted were sanctioned by management and we built.
Contd....
Key Aspects :- Communication, Critical challenge, Incident analysis, Initiative, Multi discipline exposure, Reputation, Technical issue,Team building
GIS Experience
On reporting at Bombay,Don felt comfortable with Reliance management set-up and the whole team
looked him with high respect. That paid rich dividend.
To start with he advised my team to carry out ultimate service departments' interactive exchanges to list down their want list from GIS. He prepared a set of questions and issued to them to answer and then attend meetings to deliberate. He identified various segment of communication service departments and had interaction meeting with each dedicated team. From their want list, he made sure that our GIS team to note down the requisite attribute data for each service. That came out as the listing of various data attribute requirement.. Then with our Network Engineering team , he drafted the data matrix. That was the time he took classes for the GIS/NE team regarding the database management and how the identification of layers have to be arrived in GIS domain.
As we did not have the overall idea of data sets and listing of cities where Reliance plan to launch the communication services at that juncture, to start with we did a make shift server sourced from Sun Systems . Don ensured that the team transported the map data and corresponding attribute listing in that server using Arch Info software. Then came the specific requirement of Network Engineering software ! As my core team members were from instrument fraternity, they had the vision and dream of instrumentation loops that too OSBL-extended to cross country. When those ideas were exchanged, Don came out with the suggestion of having services of NE from Atlanta! Then we got in touch with that management through Don and they were happy to join the game, as they were regular partners for network engineering for ESRI. They deployed Michael Crawford as the core member for NE development,Rest is history.
As members from Reliance were from project execution, they looked for complete cross country cabling and intra city hook-ups data in system. That paved the way for identifying the requisite attributes. Don, Michael and Milind with Jaydip,Harshad Acharya listed the requisite network attributes viz: trench, duct, fibre, slicing etc. As they were all project engineering members, they furnished the detailed specification listing for each item.For the trench- the elevation, trapezium dimensions, length, breadth along with lat/long coordinates to be picked up field survey team. When man hole and hand hole come in back bone, its location co-ordinate along with as built dimensions were picked. During execution, it was decided to have varied number of ducts in the back bone trench depending on the route popularity with potential business traffic.In cities, depending upon city ranking in hierarchy, number of ducts of intra city varied. When it came to cabling, not only the number of fibres data were picked but also the make/test certificates and detailed fibre characteristics data were picked and entered in data base. Then splicing details were picked. We did not realize that the GIS team was issuing the IFC drawings to field construction team and were expecting the construction to issue the as built data. But the network planning team realized that well in advance and they were doing basic engineering(equivalent to P&I D in process plant) and gave requirements to GIS team. The whole process were stream lined and data issue and as built reporting worked like a clock work. As said earlier, we ended working for 36000 run kms back bone and 10+48+212 intra city data capture. At one stage the data volume was as high as 6 terra bytes which called for a super computer with large memory! As things were on high, everything what we wanted were sanctioned by management and we built.
Contd....
Key Aspects :- Communication, Critical challenge, Incident analysis, Initiative, Multi discipline exposure, Reputation, Technical issue,Team building
