Haryana Tourism PMIS / Digital Initiatives Copilot

Standalone Tourism workflow site

HubStartup HaryanaPR HaryanaTourism PMIS
OverviewDemoCase detailGovernanceSources

Official sources

Evidence registry

Governance / deployment

Prepared for careful Tourism workflow deployment language

This page describes alignment targets and safe deployment posture without claiming a live PMIS, live dashboard, or production certification.

Source-grounded governance posture

This site is derived from the public Tourism PMU / consultancy RFP and does not claim a live Tourism PMIS, live dashboard, or live destination data feed.

Source-grounded governance posture

Designed to align with GIGW 3.0 guidance on accessibility, usability, content quality, security, and performance.

Source-grounded governance posture

Prepared for deployment within state-controlled hosting environments, including MeghRaj-aligned or NIC/NICSI-style cloud setups.

Source-grounded governance posture

Prepared for security review and VAPT-style assurance workflows that commonly rely on CERT-In empanelled audit capacity.

Security scope

What is safe today, and what must exist before any live Tourism workflow

The prototype remains a TOR-derived PMU review site today. A live departmental workflow would require controlled hosting, identity, logging, and review controls.

Prototype boundary

The current build is a static frontend. The PMIS review pack is simulated from public TOR requirements only. There is no Tourism Department database, no live dashboard feed, and no persistent storage.

Safe production boundary

For a live deployment, keep the workflow inside a state-controlled hosting environment, align UI and lifecycle practices with GIGW 3.0, and place application infrastructure within NIC / MeghRaj-style hosting arrangements.

Controls that should be mandatory

Role-based access, audit logs, encryption in transit and at rest, data retention policy, and security review through a CERT-In-aligned audit process should be non-negotiable before any live workflow data is handled.

What the AI should never do

It should not auto-approve, silently alter official records, pull unrelated departmental data, or send workflow files to external services without explicit government approval and deployment design.