Choose the display platform
The starting platform should match the installation, content and interaction. A change to the enclosure, panel, controller or operating system can change the documents and tests the project needs.
Define the customization scope
| Workstream | Project input | Confirmation needed |
|---|---|---|
| Branding and packaging | Logo artwork, label language, carton requirements and destination | Approved artwork, label content and packing dimensions |
| Mechanical design | Orientation, available space, mounting and maintenance access | Revision-controlled drawing, weight and mounting method |
| Panel and optical stack | Content, lighting, reflections and operating schedule | Quoted panel, brightness conditions, glass and optical configuration |
| Compute and connections | Player, OS, application, network and peripherals | Board identity, firmware, port map and software responsibilities |
| Inspection and documentation | Acceptance criteria, target market and handover needs | Agreed tests and documents applicable to the final model |
From requirements to production release
Use the following review sequence to define the project. The responsible parties and approval method are agreed for each order. A proposal becomes a release baseline only after the required approvals are recorded.
- Create the requirement record. Identify the application, location, size, orientation, operating schedule, power supply, software, quantity and installation responsibilities.
- Review feasibility and exceptions. Separate standard options from engineering changes; record unresolved dimensions, thermal conditions, application dependencies and documents.
- Confirm the configuration and offer. Agree the model, configuration revision, drawings, sample scope, quantities and project-specific commercial terms.
- Evaluate the sample. Test the actual content, host connections, operating behaviour and service access. Record the sample identity and distinguish measurements from requested features.
- Approve the baseline. Close or explicitly accept outstanding issues. Retain the approved specification, artwork, sample record and acceptance criteria for production.
- Inspect and hand over. Compare the delivered configuration with the release record and assemble the agreed operating, packing, inspection and service documents.
What belongs in a sample acceptance record
Record the exact model, serial number, hardware revision, OS build and application version. State the test conditions and expected result before evaluating the sample; then keep the observation and issue disposition together. A video can illustrate the test, but the written record identifies what was actually checked.
- Mechanical fit: final dimensions, mounting drawing, port access, ventilation and service clearance.
- Display performance: representative files, orientation, readability and the agreed brightness or colour test conditions.
- Software behaviour: installation, sign-in, playback, reboot, offline operation and recovery using the intended application.
- Host and peripherals: agreed video input, touch return, camera, microphone and network path.
- Packing and documents: actual packing dimensions, approved configuration sheet and model-specific evidence requests.
Control changes after sample approval
A replacement panel, board, firmware, application or mechanical revision may affect the approved result. Identify the change, its reason, affected documents and required rechecks before agreeing a revised baseline. Record which sample or order the approval covers.
- Keep a configuration revision and approval date on the specification and drawing.
- Assign each open issue an owner, expected evidence and next review point.
- Agree the service route and supported recovery method for the final build.
Use model-specific evidence
Request test and market documents that identify the actual model and applicable configuration. Check the issuer, date, scope and report identity. Enclosure protection, electrical requirements and software licensing cannot be inferred from a general factory description. TZD Display has not obtained Google EDLA; Google Play or GMS availability must not be assumed.
Project requirements in practice
Our anonymized project accounts show how maintenance access, customer-player evaluation and meeting-display changes shape a configuration. Each account states its documented stage.
Prepare your OEM/ODM enquiry
Send the application and market, installation photos or layout, target size and orientation, operating schedule, power supply, content examples, software requirements, quantity, acceptance criteria and required delivery date. Include the changes you need and the documents you expect. We will review the suitable platform and items requiring confirmation.
Frequently asked questions
Can I customize an existing display platform?
Branding, mechanical, panel, compute and packaging requirements can be reviewed against a suitable platform. Feasibility and the final scope are confirmed in the written project offer.
What should I approve before production?
Agree the configuration revision, drawings, artwork, sample results, outstanding issue disposition and acceptance criteria. Retain the approved record for inspection and handover.
Do you guarantee compatibility with every CMS?
No. Compatibility requires evaluation of the intended application on the exact board, operating system, firmware and network configuration. Installation alone does not establish playback or recovery performance.
Are MOQ, lead time and certificates the same for every model?
These depend on the final model, customization, quantity and destination market. Obtain written project-specific terms and documents with the applicable model scope.