Quality
What is in place today, and what is still being built.
ORBNEX Optic is developing a documented qualification and traceability framework for approved products and manufacturing partners. This page separates the practices that operate today from the framework still in development, because the difference matters to anyone deciding whether to rely on us.
Every practice below is marked either operating today or in development, so you can tell at a glance which is which. Test results, certificates and accreditations are published only once ORBNEX Optic holds the documentation to support them.
Read this first
Ratings, listings and test results are published here only once the supporting manufacturer documentation has been reviewed and approved. That review is still in progress, so this site currently publishes product families and configurable options rather than specifications or certifications. The rule is enforced in the build: a claim can only be published alongside a registry entry naming its evidence and its approver.
In place today
Practices that operate now.
These are procedural rather than technical. They are the disciplines that make a configuration repeatable and a discrepancy identifiable — which is what can honestly be claimed at this stage.
The configuration is written down before anything is built
Family, construction, fiber mode and count, jacket option, connector interface, polarity, length, labeling, and packaging are agreed in writing. A build has a definition to be checked against rather than a verbal brief.
Documentation is issued against that configuration
Technical documentation is prepared for the configuration that was agreed, with its revision and issue date recorded, so a reader can tell which version they hold.
Claims require approved evidence
A compliance, certification, or performance claim may be published only where supporting documentation has been reviewed and approved, with the evidence and the approver recorded. The registry is empty today, which is why no such claim appears.
Unverified values are marked, never estimated
Where a technical value is not yet supported by approved documentation, it is shown as pending. It is not estimated, rounded from a supplier sheet, or quietly omitted in a way that reads as absence of a problem.
First-article approval where a build repeats
Where a configuration will be produced more than once, a first article can be approved before the remainder is built. It is the cheapest place to find a labeling error or a polarity misunderstanding.
In development
The framework being built.
These are stated as intent. None is operating today, and none should be relied upon in a procurement decision until this page says otherwise.
Not yet operating
Supplier qualification criteria
A documented basis on which a manufacturing partner is assessed and approved, and a record of what was assessed.
Not yet operating
Incoming material documentation
A defined set of documentation expected with material, and a record of what was received against it.
Not yet operating
Production-lot traceability
A record connecting a delivered assembly to the lot and configuration it came from.
Not yet operating
Assembly serialization
Per-assembly identifiers recorded against the configuration record, so an individual item can be traced after installation.
Not yet operating
Controlled technical revisions
A defined process for revising a published technical document, including who approves a change and how prior revisions remain identifiable.
Not yet operating
Nonconformance handling
A defined route for raising, recording, and resolving a discrepancy between what was agreed and what was delivered.
Testing and inspection
How testing and inspection are handled.
Testing is the area where a supplier is most tempted to overstate, so the arrangement is set out precisely.
- Testing is performed by the manufacturer
- Any testing of a supplied assembly is carried out by the manufacturing partner in their own facility. ORBNEX Optic operates no laboratory or inspection facility of its own, so nothing on this site should be read as an ORBNEX Optic test result.
- Testing requirements can be specified
- Where a project requires testing, that requirement can be written into the configuration and discussed with manufacturing partners. What can be provided in a given case is established during review and confirmed in writing.
- Documentation is passed through, not authored
- Where documentation exists for an approved product or partner, it can be provided as it was received, subject to its confidentiality. It is not restated, summarised, or re-badged as an ORBNEX Optic result.
Next step
Ask what can be evidenced for your requirement.
The most useful question at this stage is a specific one. Describe the configuration and what you need to be able to demonstrate, and the reply will state what documentation exists for it.