Spatial mismatch
Survey coordinates, mapped routes and execution records can disagree.
01 / 14
Login
Built for Project Implementation Agencies
Everything in one platform.
Connect field work, network records and operational decisions across your BharatNet project.
3 packagesPlatform implemented with project data
Package 4GIS server deployed
10-year maintenanceA continuing role for field records
14 slides · Read at your pace
02 / 14
The challenge
One network. Too many versions.
When survey, GIS, execution and operations work from separate copies, every handover becomes a reconciliation exercise.
Detached evidence
Photos, videos and supporting files become difficult to match to the right location or revision.
File conversion cycles
KML/KMZ conversions, exports and imports create repeated checking and manual rework.
Stale operational records
Field changes can reach reporting teams and SNOC at different times.
The leadership questionWhen the records disagree, which version should your team act on?
03 / 14
An everyday O&M scenario
The cable was restored. Was the network record?
A repair can change cable length, slack distribution or splice position. Closing the ticket alone does not bring the network record up to date.
Illustrative field scenario
OTDR measures distance along the fibre. GIS places that distance on the ground.
01
Service is restored.The field team uses spare loop cable to repair a cut.
02
The record can fall behind.Changed slack, splice position or cable length remains unrecorded.
03
The next fault is harder to locate.A distance reading interpreted against old records can point to the wrong ground location.
Using a loop does not necessarily change total fibre length. The risk depends on what changed and whether the spatial and optical records were updated.
The workflow to verifyCapture the repair → validate the change → update the network record → inform operations.
04 / 14
The Xentric platform
Four solutions. One project lifecycle.
Manage the network, survey the field, deliver construction and coordinate operations within one platform.
The connectionField evidence and project records remain useful across delivery and maintenance.
05 / 14
01 / GIS Server Solution
A network record operations can use.
Bring spatial data management, map tools and SNOC visibility together to support network monitoring and fault rectification.
Deployed · Package 4
GIS for the operational network.
A GIS server solution with map tools, spatial data management and live monitoring for the SNOC environment.
NETWORK / FIELD / SNOC
Manage spatial information
Work with network geography and map tools in the project context.
Support fault rectification
Give operations geographic context for investigation and field response.
Reduce reconciliation work
Keep spatial management within the project workflow instead of relying on repeated file handovers.
06 / 14
02 / Survey Solution
Start with the field. Build a trusted record.
Monitor POP and route-kilometre surveys with geo-tagged field capture and supporting evidence.
POP, RKM and HOTO records
Monitor field surveys and collect geo-tagged supporting proofs. Preserve the initial POP and handover/takeover (HOTO) records for later maintenance use.
POP surveyRKM surveyGeo-tagged proofsHOTO baseline
From capture to approved GIS data
- MIS correction
- Approval
- GIS server publication
Extend the field record into a reviewed, approved source for GIS and operations.
Long-term valueThe survey investment becomes the starting reference for the maintenance team.
07 / 14
03 / Execution Solution
See the progress. Follow the evidence.
Connect construction activity, geographic context and supporting records so progress reviews can reach the work behind the numbers.
Progress with context
Review construction activity by package, block and job, with geographic visibility.
Evidence behind the work
Inspect geo-tagged photos, videos and work records behind reported completion.
Records that carry forward
Retain execution knowledge for handover, fault investigation and maintenance.
Field activity→Work record→Evidence & review→O&M reference
The management questionWhat has been completed—and can we inspect the record behind it?
08 / 14
04 / WFMS Solution
Know who is deployed. See what gets done.
Bring field teams, ITSM ticketing, FRT and patrol activity into the same operational review as SLA and restoration performance.
Who is deployed?
Field teams, manpower and vendor visibility.
What work is happening?
FRT, patrol activity, field tracking and ticket response.
Where does service need attention?
SLA, mean time to repair (MTTR) and root-cause analytics.
What supports the field team?
Personnel, assets, vehicles and material records.
Vendor accountabilityReview deployment, recorded activity and service performance together.
09 / 14
Continuity across the lifecycle
One field investment. Ten years of reference.
Put the investment in survey, HOTO and execution records to work throughout the 10-year maintenance period, with field changes keeping the baseline current.
10years
The maintenance horizon
Survey & HOTO
Initial POP condition, route survey and geo-tagged proofs.
Construction & execution
Work records, photographs, videos and supporting files.
Maintenance & restoration
Reference the original evidence and record subsequent field changes.
Preserve the investmentManaged files + location context + current records = continuing operational value.
The original survey and HOTO baseline stays useful when maintenance changes are recorded against it.
10 / 14
PIA · IE · BSNL
Shared visibility. Clear responsibility.
Give authorised stakeholders direct access to relevant project information through their logins, reducing repeated report preparation and circulation.
Project leadership
Review progress, deployment, vendors and operational performance.
Independent Engineer
View relevant project information and supporting evidence through an authorised login.
Project stakeholders
Access relevant records directly for visibility and review.
Direct accessSpend the review discussing the work, with relevant records available to the people reviewing it.
Operational records are accessed through authorised accounts. This public overview does not grant access to project data.
11 / 14
Everything in one platform
The work. The people. The resources behind both.
Support the four core solutions with the workforce, commercial and resource-management capabilities a PIA needs.
Build & understand
- Planning & Survey
- Construction
- Analytics + GIS
Operate & respond
- ITSM / Ticketing
- FRT + Patrol
- SLA & MTTR
People & partners
- WFMS + HRMS
- Labour Compliance
- Vendor Management
Resources & finance
- Finance
- Warehouse & Assets
- Vehicle Management
For the PIAUnderstand delivery alongside the people, partners and resources supporting it.
12 / 14
Built for BharatNet · Used in the field
Purpose-built. Already in operation.
Developed from the ground up for this project and implemented across three packages with actual project data.
Actual project data and field use.
Package 4
GIS capability deployed for the SNOC environment with live monitoring.
Developed for this project.
Survey, execution and operational workflows shaped around BharatNet requirements.
Evidence-led evaluationAsk to see the deployed workflow and the records that demonstrate it.
Deployment scope is specific to each package. The planned survey approval-to-GIS workflow is identified separately in this overview.
13 / 14
Your evaluation
Follow one workflow. Verify the connection.
Use a focused walkthrough to assess how the platform fits your package, teams and existing SNOC environment.
Trace one field record
Follow a survey or execution record through its location, evidence and use in maintenance.
Inspect operational control
Review team deployment, a ticket lifecycle and the service-performance measures behind it.
Confirm your package scope
Agree stakeholder access, existing data, SNOC interfaces and the rollout sequence.
Optional detail · opens a separate presentation page
14 / 14
The next conversation
Bring your project. See the workflow.
Arrange a 30-minute walkthrough with your project, GIS/SNOC and operations leads. Start with the workflow that matters most to your PIA.
Nagarajan Sampathkumar / Xentric
Arrange a walkthrough ↗nagarajan8585@gmail.com+91 86676 52156A focused 30-minute review
- 01Your priority workflow and current data challenges.
- 02A demonstration using existing project records.
- 03Fit, interfaces and the next evaluation step.
Include your package and priority solution in the email so the session can focus on your requirements.
GIS Server · Survey · Execution · WFMSEverything in one platform.
Preparing your overview · / 14 slides