Purpose and scope
This policy applies to the English-language product pages, category pages, application notes, technology explanations, engineering guides and policy pages published on optronicworks.com. It explains how content is sourced, how technical language is reviewed and how readers can request a correction.
The policy is written for engineers, OEMs, systems integrators and technical procurement teams who need to understand the status of a product claim before they request a quotation. It is also a public statement of the standard the Optronic Works Engineering Desk applies to its own work.
Nothing on this website is a substitute for a signed contract, a controlled data sheet, an interface control document or a programme-specific test plan. When those documents conflict with a web page, the controlled project document governs.
Who prepares the content
Content is prepared under the collective byline of the Optronic Works Engineering Desk. The desk coordinates product information with specialist manufacturing partners and with the people responsible for application review and commercial follow-up. The company is based in Shenzhen, Guangdong, China.
The desk is responsible for the public explanation, not for inventing product performance. Supplier documents remain the source for model-specific values. If a manufacturing partner changes a lens, sensor, connector, firmware function or qualification status, the desk should update the affected page or mark the configuration as programme-specific.
Individual biographies may be limited where personnel work on confidential or export-controlled programmes. The collective byline therefore identifies editorial responsibility while avoiding disclosure of programme assignments. A reader who needs a named technical contact for an active project can request one through the inquiry process.
How product information is sourced
Product pages draw on controlled supplier data sheets, model matrices, interface notes, presentation material and written clarification. The desk checks the model identity first. Products with similar exteriors, such as separate long-range turret variants, are kept as separate pages when their configuration or intended mission differs.
Where possible, the page records the sensor format, lens, mass, dimensions, power, stabilization axes, environmental rating and interface information relevant to selection. Claims are written in the context of the configuration. A detection range without a target class, contrast condition and atmosphere is incomplete, so the page should either state the condition or present the number as supplier-stated.
We do not use a competitor’s marketing number as proof of our own performance. We do not copy a customer’s private requirement into a public page. We do not imply that a supplier’s certification applies to a different model or to a configuration that has not been qualified.
When two source documents disagree, the desk records the issue and seeks clarification. If the difference cannot be resolved before publication, the page should use the narrower claim or explicitly identify the configuration to which each value applies.
Documented, supplier-stated and programme-specific
A “documented” value appears in a controlled source that identifies the model and configuration. A “supplier-stated” value is reported by the manufacturing partner but has not been independently measured by Optronic Works. A “programme-specific” value depends on the final integration and must be confirmed in the quotation or technical agreement.
This distinction matters most for range, stabilization, latency, power and environmental performance. A laboratory result may not transfer directly to a moving platform. A visible-band detection range may not apply to a low-contrast target. A thermal range may change with humidity, background temperature and lens selection.
Readers should ask for the test method, target size, contrast, atmosphere, installation and acceptance criteria. If those details are not available, the figure should be treated as an indication for shortlisting rather than a guaranteed field result.
Product pages include a data note where appropriate. That note is not boilerplate for its own sake: it is a reminder that a public catalogue cannot reproduce the full conditions of a controlled test report.
How technical guides are prepared
Guides begin with a practical engineering decision. The desk defines the reader, the decision and the evidence needed. It then builds a sequence: the variables that matter, the common mistakes, a comparison method and the questions to put to a supplier.
General principles may be supported by educational or standards references. Product examples link to the relevant category or model page so that a reader can inspect the configuration. The guide should not become a disguised product advertisement. Where a product is mentioned, the reason for the example should be clear.
Guides are reviewed for unit consistency, terminology and internal links. A page may use “detection”, “recognition” and “identification” only when the distinction is meaningful. A range claim should state the target and conditions. A power claim should distinguish startup, average and peak demand.
External sources are selected for educational value, not as borrowed authority. A link to a generic explanation of stabilization does not prove a specific gimbal’s residual error. Product evidence must still come from the controlled model data.
Review and publication
Before publication, the desk checks the page title, description, heading structure, product family, canonical URL, structured data and inquiry path. It also checks that the page does not promise a certification, price, lead time or performance level that has not been confirmed.
Pages are reviewed when a product changes, when a supplier issues a new data sheet, when a reader provides a documented correction, or when the surrounding product architecture changes. The review date is visible on guides and policy pages. A page without a recent review date should be treated as a starting point for verification, not as a permanently current specification.
The website team is responsible for publishing the correction. The engineering desk is responsible for deciding whether the evidence supports the change. Commercial teams should not silently alter a technical figure to make a quotation more attractive.
Reviews also consider the reader experience. A page should make its key point visible without forcing a reader to search through a wall of text. Tables, summaries and captions are used only when they clarify a decision or preserve an important condition.
Corrections and reader feedback
Send corrections to sales@optronicworks.com with the page URL, the exact statement, the proposed replacement and the supporting document. A screenshot is helpful but a controlled source is more useful. Please identify whether the issue is a typographical error, a product-data error, a missing qualification or a change in availability.
The desk will review the request and may ask the supplier or programme team for confirmation. If a correction is accepted, the page will be updated and the reviewed date changed where appropriate. If the request cannot be supported, the desk may explain why and retain the original wording.
We do not remove a valid technical caveat simply because it makes a product sound less impressive. Trust depends on preserving the conditions under which a number is useful.
Commercial relationships and independence
Optronic Works publishes this site to explain its product range and support commercial inquiries. The existence of a commercial relationship does not permit a false technical claim. Product pages may link to an inquiry form, catalogue or quotation route, but those links should be clearly commercial in context.
We do not operate paid rankings that pretend to be independent reviews. We do not publish a competitor comparison as if it were a neutral laboratory test unless the method and evidence are available. We do not use customer logos or programme names without permission.
Supplier-stated data is attributed as such. Where a page discusses a general technology, the explanation should remain useful even if the reader chooses a different supplier.
Images and product representation
Product images are used to identify the general form, sensor arrangement or integration concept. A rendered, cropped or supplier-provided image may not show the final connector set, mount, lens or finish. The image is not a dimensional drawing and should not be used for mechanical integration without the controlled envelope drawing.
Images are optimised for web delivery and may be resized or cropped for layout. We do not alter an image to imply a capability that the product does not have. Where an image is a configuration study or a representative platform, the page should say so in the surrounding copy.
Product images must not contain another company’s branding unless the relationship and permission are clear. A file name or embedded metadata should not contradict the page’s stated brand.
Automation and human review
Automation may assist with formatting, link checking, image conversion or repetitive page assembly. It is not used to invent a technical claim or to replace engineering review. Product values, qualifications, certifications and safety statements require a human source and a human decision.
If an automated process produces wording that changes the meaning of a specification, the page should be corrected. The reviewed date and change history should reflect material updates rather than cosmetic differences.
Structured data and metadata are generated from the same public product information used on the page. They must not introduce a claim that a human reader cannot find and verify in the visible content.
Contact and policy status
This policy is maintained by the Optronic Works Engineering Desk. Questions about a technical page, a correction or the use of supplier data can be sent to sales@optronicworks.com. The policy was last reviewed on 30 October 2026.
The policy describes current editorial practice. It does not create a warranty, a certification or a contractual commitment. Project-specific obligations are defined in the applicable quotation, contract and controlled technical documents.
For the people and review workflow behind this policy, see the Engineering Desk page. For data handling, see the privacy policy. For website use, see the terms of use.