Clarify the main workflow, standalone tools, customization, and separately confirmed scope.
Back Specification and Acceptance
Product Scope and Delivery Criteria
The specification aligns product scope, functional boundaries, interfaces, data flow, permissions, licensing, deployment conditions, and acceptance checks.
Online activation, offline authorization, system permissions, and runtime write actions are included.
Confirm screens, tags, scripts, alarms, alarm sound, trends, downloads, documents, and troubleshooting entries.
SRS
Mingxu Software Requirements Specification
Use this specification to align product descriptions, selection, trial preparation, delivery scope, and acceptance criteria. Project contracts, customer-specific customization, and site remediation remain separately confirmed.
Clarify logic, establish order, and keep screens, data, permissions, and site workflows clear and controlled.
Use this page for sales discussion, project selection, trial preparation, delivery-scope confirmation, and acceptance checks. Customer-specific system changes, protocol adapters, or site network remediation should be confirmed by project scope.
This specification states product capabilities, responsibility ownership, required environment conditions, and delivery checks to align project communication. Contracts, quotations, and customer-specific requirement documents remain governed by the formal project documents.
Acceptance should confirm page access, screen-package loading, data integration, permissions and licensing, alarms, alarm sound, trends, script interfaces, deployment services, mobile reading, documentation delivery, and download entries item by item.
Site network remediation, deep customization of third-party systems, unlisted protocol adapters, project-specific script logic, and internal customer policies should be confirmed separately in project scope.
Scope
Product Scope and Boundaries
Confirm which product owns the question before mixing the main workflow with standalone tools.
The main workflow is HQ VISU Designer exporting PowerPoint screen packages, then HQControl receiving and running those screen assets with tags, menus, languages, permissions, alarms, alarm sound, trends, scripts, and licensing.
Use HQ Scan only when a project needs TIA / PLC DB points, symbolic addresses, alarm candidates, or trend candidates. Use HQShare only for LAN file exchange, delivery packages, logs, and field material transfer.
Customer-specific system changes, unconfirmed protocol adapters, third-party system customization, and site network-security remediation should be evaluated and confirmed by project scope.
Functions
Functional Requirements
Describe expected product capabilities so selection, trials, and delivery scope can be confirmed consistently.
The plugin should support authoring industrial pages, templates, popups, scripts, animations, and bindings in PowerPoint, then exporting HTML / SVG / JS screen packages for HQControl.
- Support full-package export and current-page export.
- Support online or offline licensing.
- Check pages, assets, and behavior configuration before export.
HQControl should support screen asset onboarding, runtime entry configuration, devices and tags, menus, i18n, permissions, alarms, alarm sound, trends, scripts, licensing, federation, and redundancy.
- Screen assets and runtime configuration should have clear management entries.
- Device data, alarms, alarm sound, trends, permissions, and licensing should be configured by project scope.
- Production operation should have basic status monitoring and delivery checks.
HQ Scan should prepare normalizable DB points and symbolic addresses from TIA / PLC engineering projects, with scan, review, filtering, and export capabilities.
- Explain supported export content and excluded content clearly.
- Export results should support later import, review, or delivery.
HQShare should provide controlled LAN file sharing through web login and role permissions for download, upload, rename, delete, and user management.
Integration
Interfaces, Data, and Runtime Flow
Explain where data comes from, where it enters, and who maintains each part.
Screen data starts in PowerPoint, is exported by HQ VISU Designer as a screen package, and is then loaded by HQControl. Site device data enters the runtime through HQControl device, tag, IO, and integration capabilities.
Device connections, IO State API, WebSocket, Integration Script, and third-party real-time access should be checked in the HQControl manual first. Protocols or interfaces outside official documentation require project confirmation before they become delivery scope.
HQ Scan exports reviewed point results. Raw TIA projects, full project trees, internal rule state, and structured objects outside normalized point rows are excluded from export results.
Security
Permissions, Licensing, and Security
Public documentation can be read openly, while runtime systems and management actions need clear permission boundaries.
Product pages, manuals, requirements, and troubleshooting pages are readable without login so customers can evaluate and field teams can reference them quickly.
Admin entries, write actions, file operations, and user management in HQControl and HQShare must be controlled by accounts, roles, and permissions. Hidden menus should be treated only as navigation controls, not access control.
Licensing should distinguish trials, production licenses, online activation, and offline activation. Production projects should record license state, machine information, version, and delivery scope.
Delivery
Deployment, Exceptions, and Acceptance
Make delivery checks explicit for field execution and later maintenance.
Before production deployment, confirm platform, software version, ports, service state, database or runtime dependencies, browser access path, license state, and site network boundaries.
When an issue appears, start from the troubleshooting page by symptom, then confirm environment, version, permissions, service state, network reachability, logs, and configuration-change records before changing project configuration.
Acceptance should cover main page access, screen navigation, tag data, alarms, alarm sound, trends, permission login, license state, export results, download entries, mobile reading, and key troubleshooting paths.
Next
Continue to product material
Use this specification to confirm scope, then open product manuals for installation, operation, and troubleshooting.
HQ VISU Designer
Read screen authoring, templates, scripts, tag binding, and export guidance.
HQControl
Read runtime platform, devices and tags, permissions, licensing, deployment, and delivery checks.
Documentation Center
Continue by product, troubleshooting, downloads, and reading paths.