Maritime GNSS Jamming & Spoofing, Backup Navigation Readiness, Voyage Delay & Retrofit ROI Tool
Maritime GNSS Jamming & Spoofing, Backup Navigation Readiness, Voyage Delay & Retrofit ROI Tool
Convert exposure to GNSS interference into a transparent voyage-delay business case. Compare backup-navigation retrofit tenders, audit independent navigation readiness and calculate ten-year expected commercial benefits without treating projected savings as a safety guarantee.
How the scenario works
Simple: exposed passages × incident probability = expected events per year. Each modeled event costs delay hours × vessel daily time cost ÷ 24, plus entered additional cash expense. Efficacy reduces this modeled cost only by the entered percentage. Installation off-hire is treated as an incremental day cost when specified.
Advanced: per-vessel passages are distributed across risk regions using their share-of-passages fields. Risk-region shares must total no more than 100%. Confirmed project costs, retrofits and expected operating losses are projected over the selected horizon. Benefits are not automatically inferred from a readiness score.
15-term glossary & methodology
GNSS: satellite-derived positioning/navigation/timing. Jamming: disruption of reception. Spoofing: apparently plausible but false PNT data. Independent fix: non-GNSS method used to verify position. DR: dead reckoning. EP: estimated position. ECDIS: electronic chart display and information system. AIS: automatic identification system; may share compromised positioning data. PNT: positioning, navigation and timing. Material incident: exposure producing a consequential commercial delay in the assumed scenario. Expected events: exposed passages × modeled material-incident probability. Consequence-hours: expected delay per incident, not hours of interference. NPV: discounted benefit minus discounted costs. IRR: discount rate yielding zero NPV where a solution exists. Payback: undiscounted recovery period.
Two different costs must not be counted twice: time value for schedule impact and incremental incident cash charges. Fatalities, collisions, pollution, legal exposure and other safety consequences are not priced by this model.
Calculation self-checks
Set incident chance to 0: expected incidents and avoided loss should become zero. Set avoided impact to 0: savings should be zero before support. Higher CAPEX reduces NPV, other factors equal. A higher avoidable-loss percentage raises NPV but never creates a safety assurance. In Advanced mode, Included route shares above 100% block calculation. Pending project expense rows are excluded from the base case; open critical acceptance gates prevent an approval-ready designation. Switching a bid or stress cell does not write Tool Data; only Calculate does.