Safe City integration overview

• LahorePunjab
• RawalpindiPunjab
• FaisalabadPunjab
• MultanPunjab
• GujranwalaPunjab
• SialkotPunjab

• Emergency contact centreRequires authorisation

  Receive permitted incident records and supporting attachments

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Punjab Safe Cities Authority (intended target); (2) the vendor's contact_centre interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Dispatch / resource managementRequires authorisation

  Request a dispatch decision and receive authorised response updates

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Punjab Safe Cities Authority (intended target); (2) the vendor's dispatch interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Event bus / integration gatewayRequires authorisation

  Exchange structured alerts and workflow events

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Punjab Safe Cities Authority (intended target); (2) the vendor's event_bus interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Event bus / integration gatewaySandboxAETNIC simulator

  Exchange structured alerts and workflow events

  Blocking — SIMULATOR — not a live connection. Demonstrates the workflow only. To go live: Requires: (1) a signed data-sharing or interconnection agreement with Punjab Safe Cities Authority (intended target); (2) the vendor's the organisation's interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Evidence managementRequires authorisation

  Transfer approved evidence packages and preserve provenance

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Punjab Safe Cities Authority (intended target); (2) the vendor's evidence_management interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• GISRequires authorisation

  Display approved incident locations, jurisdiction boundaries and operational zones

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Punjab Safe Cities Authority (intended target); (2) the vendor's gis interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Identity providerRequires authorisation

  Federated authentication and role mapping where supported

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Punjab Safe Cities Authority (intended target); (2) the vendor's identity_provider interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Incident management / CADRequires authorisation

  Create approved incidents, receive acknowledgements and synchronise status

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Punjab Safe Cities Authority (intended target); (2) the vendor's incident_cad interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Video management (VMS)Requires authorisation

  Reference authorised cameras and retrieve incident-specific clips

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Punjab Safe Cities Authority (intended target); (2) the vendor's vms interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• KarachiSindh
• HyderabadSindh
• SukkurSindh
• LarkanaSindh

• Emergency contact centreRequires authorisation

  Receive permitted incident records and supporting attachments

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Sindh Safe City programme (intended target); (2) the vendor's contact_centre interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Dispatch / resource managementRequires authorisation

  Request a dispatch decision and receive authorised response updates

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Sindh Safe City programme (intended target); (2) the vendor's dispatch interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Event bus / integration gatewayRequires authorisation

  Exchange structured alerts and workflow events

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Sindh Safe City programme (intended target); (2) the vendor's event_bus interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Event bus / integration gatewaySandboxAETNIC simulator

  Exchange structured alerts and workflow events

  Blocking — SIMULATOR — not a live connection. Demonstrates the workflow only. To go live: Requires: (1) a signed data-sharing or interconnection agreement with Sindh Safe City programme (intended target); (2) the vendor's the organisation's interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Evidence managementRequires authorisation

  Transfer approved evidence packages and preserve provenance

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Sindh Safe City programme (intended target); (2) the vendor's evidence_management interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• GISRequires authorisation

  Display approved incident locations, jurisdiction boundaries and operational zones

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Sindh Safe City programme (intended target); (2) the vendor's gis interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Identity providerRequires authorisation

  Federated authentication and role mapping where supported

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Sindh Safe City programme (intended target); (2) the vendor's identity_provider interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Incident management / CADRequires authorisation

  Create approved incidents, receive acknowledgements and synchronise status

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Sindh Safe City programme (intended target); (2) the vendor's incident_cad interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Video management (VMS)Requires authorisation

  Reference authorised cameras and retrieve incident-specific clips

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Sindh Safe City programme (intended target); (2) the vendor's vms interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• PeshawarKhyber Pakhtunkhwa
• MardanKhyber Pakhtunkhwa
• AbbottabadKhyber Pakhtunkhwa
• Mingora (Swat)Khyber Pakhtunkhwa

• Emergency contact centreRequires authorisation

  Receive permitted incident records and supporting attachments

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Khyber Pakhtunkhwa Safe City programme (intended target); (2) the vendor's contact_centre interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Dispatch / resource managementRequires authorisation

  Request a dispatch decision and receive authorised response updates

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Khyber Pakhtunkhwa Safe City programme (intended target); (2) the vendor's dispatch interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Event bus / integration gatewayRequires authorisation

  Exchange structured alerts and workflow events

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Khyber Pakhtunkhwa Safe City programme (intended target); (2) the vendor's event_bus interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Event bus / integration gatewaySandboxAETNIC simulator

  Exchange structured alerts and workflow events

  Blocking — SIMULATOR — not a live connection. Demonstrates the workflow only. To go live: Requires: (1) a signed data-sharing or interconnection agreement with Khyber Pakhtunkhwa Safe City programme (intended target); (2) the vendor's the organisation's interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Evidence managementRequires authorisation

  Transfer approved evidence packages and preserve provenance

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Khyber Pakhtunkhwa Safe City programme (intended target); (2) the vendor's evidence_management interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• GISRequires authorisation

  Display approved incident locations, jurisdiction boundaries and operational zones

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Khyber Pakhtunkhwa Safe City programme (intended target); (2) the vendor's gis interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Identity providerRequires authorisation

  Federated authentication and role mapping where supported

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Khyber Pakhtunkhwa Safe City programme (intended target); (2) the vendor's identity_provider interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Incident management / CADRequires authorisation

  Create approved incidents, receive acknowledgements and synchronise status

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Khyber Pakhtunkhwa Safe City programme (intended target); (2) the vendor's incident_cad interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Video management (VMS)Requires authorisation

  Reference authorised cameras and retrieve incident-specific clips

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Khyber Pakhtunkhwa Safe City programme (intended target); (2) the vendor's vms interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• QuettaBalochistan
• GwadarBalochistan
• TurbatBalochistan

• Emergency contact centreRequires authorisation

  Receive permitted incident records and supporting attachments

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Balochistan Safe City programme (intended target); (2) the vendor's contact_centre interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Dispatch / resource managementRequires authorisation

  Request a dispatch decision and receive authorised response updates

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Balochistan Safe City programme (intended target); (2) the vendor's dispatch interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Event bus / integration gatewayRequires authorisation

  Exchange structured alerts and workflow events

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Balochistan Safe City programme (intended target); (2) the vendor's event_bus interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Event bus / integration gatewaySandboxAETNIC simulator

  Exchange structured alerts and workflow events

  Blocking — SIMULATOR — not a live connection. Demonstrates the workflow only. To go live: Requires: (1) a signed data-sharing or interconnection agreement with Balochistan Safe City programme (intended target); (2) the vendor's the organisation's interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Evidence managementRequires authorisation

  Transfer approved evidence packages and preserve provenance

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Balochistan Safe City programme (intended target); (2) the vendor's evidence_management interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• GISRequires authorisation

  Display approved incident locations, jurisdiction boundaries and operational zones

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Balochistan Safe City programme (intended target); (2) the vendor's gis interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Identity providerRequires authorisation

  Federated authentication and role mapping where supported

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Balochistan Safe City programme (intended target); (2) the vendor's identity_provider interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Incident management / CADRequires authorisation

  Create approved incidents, receive acknowledgements and synchronise status

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Balochistan Safe City programme (intended target); (2) the vendor's incident_cad interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Video management (VMS)Requires authorisation

  Reference authorised cameras and retrieve incident-specific clips

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Balochistan Safe City programme (intended target); (2) the vendor's vms interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• IslamabadIslamabad Capital Territory

• Emergency contact centreRequires authorisation

  Receive permitted incident records and supporting attachments

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Islamabad Capital Territory Safe City project (intended target); (2) the vendor's contact_centre interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Dispatch / resource managementRequires authorisation

  Request a dispatch decision and receive authorised response updates

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Islamabad Capital Territory Safe City project (intended target); (2) the vendor's dispatch interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Event bus / integration gatewayRequires authorisation

  Exchange structured alerts and workflow events

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Islamabad Capital Territory Safe City project (intended target); (2) the vendor's event_bus interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Event bus / integration gatewaySandboxAETNIC simulator

  Exchange structured alerts and workflow events

  Blocking — SIMULATOR — not a live connection. Demonstrates the workflow only. To go live: Requires: (1) a signed data-sharing or interconnection agreement with Islamabad Capital Territory Safe City project (intended target); (2) the vendor's the organisation's interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Evidence managementRequires authorisation

  Transfer approved evidence packages and preserve provenance

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Islamabad Capital Territory Safe City project (intended target); (2) the vendor's evidence_management interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• GISRequires authorisation

  Display approved incident locations, jurisdiction boundaries and operational zones

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Islamabad Capital Territory Safe City project (intended target); (2) the vendor's gis interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Identity providerRequires authorisation

  Federated authentication and role mapping where supported

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Islamabad Capital Territory Safe City project (intended target); (2) the vendor's identity_provider interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Incident management / CADRequires authorisation

  Create approved incidents, receive acknowledgements and synchronise status

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Islamabad Capital Territory Safe City project (intended target); (2) the vendor's incident_cad interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Video management (VMS)Requires authorisation

  Reference authorised cameras and retrieve incident-specific clips

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Islamabad Capital Territory Safe City project (intended target); (2) the vendor's vms interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

No endpoints recorded.

• Abuse reportingRequires agreement

  Submit reviewed evidence concerning fraud, threats or other defined abuse

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Company Limited (intended target); (2) the vendor's abuse_reporting interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Enterprise connectivityRequires credentials

  View health of the customer's own contracted circuits

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Company Limited (intended target); (2) the vendor's enterprise_connectivity interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Evidence exchangeRequires agreement

  Transfer approved, minimum-necessary case evidence

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Company Limited (intended target); (2) the vendor's evidence_exchange interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Identity federationUnsupported

  Authenticate authorised operator users through supported federation

  Blocking — Pakistan Telecommunication Company Limited (intended target) publishes no federation interface this application can use. Requires an identity-federation arrangement agreed with the organisation as a precondition.

• Incident exchangeRequires agreement

  Create, acknowledge and update operational tickets

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Company Limited (intended target); (2) the vendor's incident_exchange interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Incident exchangeSandboxAETNIC simulator

  Create, acknowledge and update operational tickets

  Blocking — SIMULATOR — not a live connection. Demonstrates the workflow only. To go live: Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Company Limited (intended target); (2) the vendor's the organisation's interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Request trackingRequires agreement

  Track official requests and operator responses without assuming implementation authority

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Company Limited (intended target); (2) the vendor's request_tracking interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Service assuranceRequires credentials

  Receive outages, maintenance notices and restoration updates

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Company Limited (intended target); (2) the vendor's service_assurance interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• SLA reportingManual submission

  Compare observed ticket milestones against configured contractual targets

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Company Limited (intended target); (2) the vendor's sla_reporting interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

No endpoints recorded.

• Abuse reportingRequires agreement

  Submit reviewed evidence concerning fraud, threats or other defined abuse

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Transworld (intended target); (2) the vendor's abuse_reporting interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Enterprise connectivityRequires credentials

  View health of the customer's own contracted circuits

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Transworld (intended target); (2) the vendor's enterprise_connectivity interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Evidence exchangeRequires agreement

  Transfer approved, minimum-necessary case evidence

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Transworld (intended target); (2) the vendor's evidence_exchange interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Identity federationUnsupported

  Authenticate authorised operator users through supported federation

  Blocking — Transworld (intended target) publishes no federation interface this application can use. Requires an identity-federation arrangement agreed with the organisation as a precondition.

• Incident exchangeRequires agreement

  Create, acknowledge and update operational tickets

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Transworld (intended target); (2) the vendor's incident_exchange interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Incident exchangeSandboxAETNIC simulator

  Create, acknowledge and update operational tickets

  Blocking — SIMULATOR — not a live connection. Demonstrates the workflow only. To go live: Requires: (1) a signed data-sharing or interconnection agreement with Transworld (intended target); (2) the vendor's the organisation's interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Request trackingRequires agreement

  Track official requests and operator responses without assuming implementation authority

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Transworld (intended target); (2) the vendor's request_tracking interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Service assuranceRequires credentials

  Receive outages, maintenance notices and restoration updates

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Transworld (intended target); (2) the vendor's service_assurance interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• SLA reportingManual submission

  Compare observed ticket milestones against configured contractual targets

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Transworld (intended target); (2) the vendor's sla_reporting interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

No endpoints recorded.

• Abuse reportingRequires agreement

  Submit reviewed evidence concerning fraud, threats or other defined abuse

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Nayatel (intended target); (2) the vendor's abuse_reporting interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Enterprise connectivityRequires credentials

  View health of the customer's own contracted circuits

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Nayatel (intended target); (2) the vendor's enterprise_connectivity interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Evidence exchangeRequires agreement

  Transfer approved, minimum-necessary case evidence

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Nayatel (intended target); (2) the vendor's evidence_exchange interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Identity federationUnsupported

  Authenticate authorised operator users through supported federation

  Blocking — Nayatel (intended target) publishes no federation interface this application can use. Requires an identity-federation arrangement agreed with the organisation as a precondition.

• Incident exchangeRequires agreement

  Create, acknowledge and update operational tickets

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Nayatel (intended target); (2) the vendor's incident_exchange interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Incident exchangeSandboxAETNIC simulator

  Create, acknowledge and update operational tickets

  Blocking — SIMULATOR — not a live connection. Demonstrates the workflow only. To go live: Requires: (1) a signed data-sharing or interconnection agreement with Nayatel (intended target); (2) the vendor's the organisation's interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Request trackingRequires agreement

  Track official requests and operator responses without assuming implementation authority

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Nayatel (intended target); (2) the vendor's request_tracking interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Service assuranceRequires credentials

  Receive outages, maintenance notices and restoration updates

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Nayatel (intended target); (2) the vendor's service_assurance interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• SLA reportingManual submission

  Compare observed ticket milestones against configured contractual targets

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Nayatel (intended target); (2) the vendor's sla_reporting interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

No endpoints recorded.

• Abuse reportingManual submission

  Submit reviewed evidence concerning fraud, threats or other defined abuse

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Authority (intended target); (2) the vendor's abuse_reporting interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Enterprise connectivityManual submission

  View health of the customer's own contracted circuits

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Authority (intended target); (2) the vendor's enterprise_connectivity interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Evidence exchangeManual submission

  Transfer approved, minimum-necessary case evidence

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Authority (intended target); (2) the vendor's evidence_exchange interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Identity federationManual submission

  Authenticate authorised operator users through supported federation

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Authority (intended target); (2) the vendor's identity_federation interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Incident exchangeManual submission

  Create, acknowledge and update operational tickets

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Authority (intended target); (2) the vendor's incident_exchange interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Incident exchangeSandboxAETNIC simulator

  Create, acknowledge and update operational tickets

  Blocking — SIMULATOR — not a live connection. Demonstrates the workflow only. To go live: Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Authority (intended target); (2) the vendor's the organisation's interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Request trackingManual submission

  Track official requests and operator responses without assuming implementation authority

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Authority (intended target); (2) the vendor's request_tracking interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Service assuranceManual submission

  Receive outages, maintenance notices and restoration updates

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Authority (intended target); (2) the vendor's service_assurance interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• SLA reportingManual submission

  Compare observed ticket milestones against configured contractual targets

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Authority (intended target); (2) the vendor's sla_reporting interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

No endpoints recorded.

• Abuse reportingManual submission

  Submit reviewed evidence concerning fraud, threats or other defined abuse

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with National Cyber Crime Investigation Agency (intended target); (2) the vendor's abuse_reporting interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Enterprise connectivityManual submission

  View health of the customer's own contracted circuits

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with National Cyber Crime Investigation Agency (intended target); (2) the vendor's enterprise_connectivity interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Evidence exchangeManual submission

  Transfer approved, minimum-necessary case evidence

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with National Cyber Crime Investigation Agency (intended target); (2) the vendor's evidence_exchange interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Identity federationManual submission

  Authenticate authorised operator users through supported federation

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with National Cyber Crime Investigation Agency (intended target); (2) the vendor's identity_federation interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Incident exchangeManual submission

  Create, acknowledge and update operational tickets

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with National Cyber Crime Investigation Agency (intended target); (2) the vendor's incident_exchange interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Incident exchangeSandboxAETNIC simulator

  Create, acknowledge and update operational tickets

  Blocking — SIMULATOR — not a live connection. Demonstrates the workflow only. To go live: Requires: (1) a signed data-sharing or interconnection agreement with National Cyber Crime Investigation Agency (intended target); (2) the vendor's the organisation's interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Request trackingManual submission

  Track official requests and operator responses without assuming implementation authority

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with National Cyber Crime Investigation Agency (intended target); (2) the vendor's request_tracking interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Service assuranceManual submission

  Receive outages, maintenance notices and restoration updates

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with National Cyber Crime Investigation Agency (intended target); (2) the vendor's service_assurance interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• SLA reportingManual submission

  Compare observed ticket milestones against configured contractual targets

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with National Cyber Crime Investigation Agency (intended target); (2) the vendor's sla_reporting interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

No endpoints recorded.

• Abuse reportingManual submission

  Submit reviewed evidence concerning fraud, threats or other defined abuse

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Ministry of Interior, Pakistan (intended target); (2) the vendor's abuse_reporting interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Enterprise connectivityManual submission

  View health of the customer's own contracted circuits

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Ministry of Interior, Pakistan (intended target); (2) the vendor's enterprise_connectivity interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Evidence exchangeManual submission

  Transfer approved, minimum-necessary case evidence

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Ministry of Interior, Pakistan (intended target); (2) the vendor's evidence_exchange interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Identity federationManual submission

  Authenticate authorised operator users through supported federation

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Ministry of Interior, Pakistan (intended target); (2) the vendor's identity_federation interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Incident exchangeManual submission

  Create, acknowledge and update operational tickets

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Ministry of Interior, Pakistan (intended target); (2) the vendor's incident_exchange interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Incident exchangeSandboxAETNIC simulator

  Create, acknowledge and update operational tickets

  Blocking — SIMULATOR — not a live connection. Demonstrates the workflow only. To go live: Requires: (1) a signed data-sharing or interconnection agreement with Ministry of Interior, Pakistan (intended target); (2) the vendor's the organisation's interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Request trackingManual submission

  Track official requests and operator responses without assuming implementation authority

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Ministry of Interior, Pakistan (intended target); (2) the vendor's request_tracking interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• Service assuranceManual submission

  Receive outages, maintenance notices and restoration updates

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Ministry of Interior, Pakistan (intended target); (2) the vendor's service_assurance interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

• SLA reportingManual submission

  Compare observed ticket milestones against configured contractual targets

  Blocking — Requires: (1) a signed data-sharing or interconnection agreement with Ministry of Interior, Pakistan (intended target); (2) the vendor's sla_reporting interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.