What to Prepare for Private Deployment of a Data Dashboard

Summary: Private deployment is not complete when files are copied to a server. Before a data dashboard goes live, confirm the server environment, access method, database permissions, API network, security policy, backups, acceptance criteria, and responsibility for ongoing operations.

When is private deployment needed?

Projects involving business performance, production equipment, park energy, customer records, government or enterprise intranets, or command-center duty often consider private or intranet deployment. This can reduce exposure to external access and simplify integration with existing systems, databases, and equipment platforms.

Pre-deployment checklist

Item	What to prepare	Purpose
Server environment	OS version, CPU, memory, disk, network, and ports.	Confirm operating requirements and performance boundaries.
Access method	Intranet IP, domain, HTTPS certificate, and access allowlist.	Define how users will open the dashboard.
Database permissions	Database name, account, read-only access, schema, and field definitions.	Keep data access stable and permissions controlled.
API network	API URLs, authentication, sample responses, and call frequency.	Support integration and error handling.
Security requirements	Accounts, password policy, logs, backups, and internal/external network boundary.	Reduce data and access risks after launch.
Acceptance criteria	Page count, data accuracy, refresh frequency, and performance requirements.	Avoid disagreement just before launch.

How do we work together if data cannot leave the intranet?

If data must stay on the company network, explain the network conditions to Hongshan Technology first, then agree on deployment and data connection. Full offline operation also depends on whether maps, fonts, video, identity services, software licenses, and other dependencies support the target environment. Check each one.

Illustration separating intranet runtime and external dependency checks — Intranet deployment also requires checking maps, fonts, authentication, licenses, and other dependencies. The illustration separates the internal runtime boundary from dependency checks so “the server is inside the network” is not mistaken for “every feature works offline.”

Common customer questions	What to confirm together	Materials to prepare
Which resources need internet access?	How each dependency is used, its licensing conditions, and intranet alternatives	Inventory of existing software, maps, video, and authentication services
Who provides the environment?	Owners of servers, OS, database, domain certificate, and network access	Environment versions and network requirements; do not send account passwords during initial discussions
How will existing systems connect?	API authorization, test data, field definitions, and an integration window	System contacts, API documents, and de-identified sample responses
How will upgrades work after launch?	Who delivers updates, approves installation, backs up data, and rolls back changes?	Internal maintenance process, acceptable change window, and takeover staff
Can our own team maintain it?	Scope of source code or deployment packages, build and run instructions, configuration, and dependencies	Work to be taken over and the skills of current technical staff

If you already use ERP or Excel, see data integration and intranet project preparation (Chinese); for handover, compare the source code, deployment, and account handover checklist (Chinese).

Common private deployment risks

Required server ports were not opened in time, so APIs or pages cannot be reached.
Database permissions are insufficient: the development setup works but production cannot read data.
HTTPS certificates, domains, or intranet DNS are not ready, disrupting access.
API response fields differ from the documentation and prolong integration.
No owner has been assigned for server, database, API changes, or backups.

What should acceptance cover?

Acceptance is not just a visual review. Check data accuracy, stable refresh, clear error states and permissions, adequate speed on the target displays, and complete deployment and maintenance documentation.

Recommended handover materials

Deployment files and operating instructions
API field definitions and metric definitions
Account permissions and access addresses
Launch checklist and acceptance checklist
Maintenance boundaries and change process

Frequently asked questions

Can an intranet dashboard always run without internet access?

That depends on the project's dependencies. Maps, fonts, video, login services, licenses, or APIs may use external services. Check for lawful intranet alternatives and test under the agreed network conditions before confirming offline scope.

Can Hongshan support deployment if remote access to the intranet is prohibited?

Discuss the permitted delivery and installation process first. Agree which steps the customer's technical staff will perform, whether on-site support is needed, and the scope of installation, integration, upgrades, and maintenance. Specific arrangements and costs depend on the target environment and each party's responsibilities.

Do we need to send database credentials during initial assessment?

An environment description, field documents, and de-identified samples are enough for initial assessment. If integration needs access, agree on authorization, method, and permission scope, then exchange credentials through the agreed channel. Do not attach production passwords to ordinary inquiry materials.