Product Scope and Delivery Criteria

The main workflow is Mingcedar Studio exporting PowerPoint screen packages, then Mingcedar receiving and running those screen assets with tags, menus, languages, permissions, alarms, alarm sound, trends, scripts, and licensing.

Mingcedar Scan is a free, standalone tool for standard-layout DB points in TIA projects. Its Excel, CSV, and JSON can be transformed for later systems, but third-party compatibility must be verified against their official specifications. Mingcedar Share handles document previews, 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.

Author industrial screens, templates, popups, page-scoped scripts, behaviors, charts, video settings, and data bindings in PowerPoint, then export HTML / SVG / JS screen packages for Mingcedar.

• The plugin runs in Microsoft PowerPoint 2016 or later for Windows desktop, including Microsoft 365 desktop PowerPoint. PowerPoint for Mac, the web, and mobile devices are outside the installation scope.
• The plugin installs for the current Windows user and supports 32-bit (x86) and 64-bit (x64) PowerPoint. Bitness refers to the PowerPoint application. After installation, confirm that the ribbon, Behavior Browser, and editors open correctly.
• Configure industrial animation in the plugin behavior editors. Native PowerPoint animations and slide transitions are outside the current screen-package export scope.
• Distinguish PLC Tags, calculated Tags, runtime variables, and template parameters. Read calculated Tags by name with ReadCalculatedTag, without a PLC prefix; calculated results are read-only.
• Supports full-package and current-page export, plus online and offline licensing. Deploy video files separately and configure camera access through the required media channels.
• Check data bindings, interactions, media access, and permissions in the target Mingcedar environment. A supported installation version does not guarantee export of every presentation feature.

Mingcedar runs Web/App, IO, Alarm, Trend, and Script as independent services, with devices, screens and media, alarms and trends, Python, configuration releases, and directional federation.

• Screen assets and runtime configuration should have clear management entries.
• Custom pages and external integrations should use controlled interfaces.
• Devices, permissions, alarms, and trends are runtime foundations with status monitoring and delivery checks.
• Trends support realtime viewing and historical queries. Historical comparison lets you select Tags and time ranges separately for each side, switch between charts and data tables, and export CSV / PNG.

Mingcedar Scan is a free, standalone offline tool for scalar points in standard-layout DBs, with review of symbolic paths, absolute addresses and verification status, rule filtering, and reusable data export.

• Runs on Windows x64 with .NET Framework 4.8, TIA Portal, a running Automation License Manager, and Openness access. Match the Scan build, TIA, and Openness API; the project cannot be newer than the selected TIA installation. Older projects from V14 onward use supported TIA migration paths; migrate earlier projects first and use the V21 build for V21 projects.
• Optimized/unknown-layout DBs, I/Q/M, and members without constructed absolute addresses are excluded; constructed but unverified addresses can remain for review.
• The GUI exports one Excel, CSV, or JSON review list; formal CLI scans can create Mingcedar communication-import JSON containing only points that pass address and type checks.
• Third-party SCADA/HMI or custom systems require explicit field mapping and compatibility testing.

Mingcedar Share provides common-document previews and controlled LAN file sharing. Browser login and roles govern preview, download, upload, rename, and delete actions. Manage accounts on the service host through the desktop or CLI.

Screen data starts in PowerPoint, is exported by Mingcedar Studio as a screen package, and is then loaded by Mingcedar. Site device data enters the runtime through Mingcedar 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 Mingcedar manual first. Protocols or interfaces outside official documentation require project confirmation before they become delivery scope.

Mingcedar Scan review exports contain standard-DB scalar points, absolute addresses, and verification status, including unverified rows. Communication-import files select only eligible addresses and types. Raw TIA projects, full project trees, internal rule state, optimized/unknown-layout DBs, and structural containers are excluded.

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 Mingcedar and Mingcedar Share 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.

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.