CONNECTING CRUISE VISITORS WITH THE CITY.

The Harbor visitor interface currently demonstrates the intended experience. It is explicitly presented as a Concept Demo, not as proof of a live commercial network.

NTM already has relevant experience with hardware, local networking, captive interaction, edge systems and operational software. The complete multi-location Harbor architecture still has to be validated.

Harbor does not claim that a fixed number of Nodes automatically guarantees city-wide WiFi coverage.

Coverage depends on placement, buildings, street geometry, interference, local internet, radio conditions and client-device behaviour.

Real-world deployment therefore requires: plan → deploy → measure → adjust → measure again.

Harbor should not depend on one access mechanism. Captive behaviour can differ between devices and operating systems.

The intended model therefore includes multiple paths to the same visitor environment:

• Harbor WiFi
• QR access
• Direct web access
• Normal mobile internet

A distributed Harbor deployment must assume that individual components will fail.

Nodes may lose power, internet connectivity, backend access or require maintenance. Monitoring and fault isolation are therefore part of the architecture.

Harbor Lab will deliberately introduce failures to test detection, isolation and recovery behaviour.

Free local connectivity can provide a strong reason to enter the Harbor environment, but connectivity alone is not intended to be the product.

Harbor aims to combine destination context, local discovery, routes, businesses, offers and return-to-ship awareness in one local experience.

Whether visitors actually value and use that experience is a commercial validation question, not an assumption NTM currently presents as proven.

Harbor is designed to create more than advertising exposure. Participating businesses can become part of discovery, routes and visitor decision flows.

Potential value can include business views, route starts, offer interactions and physical visits.

The final commercial model and pricing should be based on demonstrated business value, not assumptions made before field testing.

The final Harbor data model has not yet been fixed. That design must follow the principle of collecting only what is necessary for legitimate operational and measurement purposes.

Privacy, retention, consent, analytics and access control must be defined before public commercial deployment.

Harbor Lab is also intended to clarify which technical telemetry is actually necessary.

No.

Harbor is a new NTM application. Kuşadası is currently presented as a proposed future commercial deployment, not as an existing Harbor customer or live Harbor network.

NTM's confidence comes from accumulated engineering experience in location technology, hardware, networking, captive interaction and real-world systems — not from claiming a Harbor deployment that does not exist.

Harbor is not currently presented as having a commercial agreement with Ege Port, a cruise line or a cruise-terminal operator.

Future cruise-industry participation could significantly strengthen Harbor by introducing the service directly to passengers, but Harbor must first demonstrate technical and visitor value independently.

Harbor should not continue in its current architecture simply because time and money have already been invested.

A fundamental inability to achieve reliable operation, acceptable visitor usability, responsible data handling or meaningful commercial value could require major redesign or termination of the deployment model.

The purpose of validation is to discover those problems before scale makes them expensive.