|
|
 |
|
|
 |
 |
 |
| |
| |
| |
| Services for our customer form a complete design and developmet cycle: |
| |

|
| |
| |
|
|
| |
|
Our design and development is based on Design and development cycle concept. Within the cycle we esatblish processes for documentation generation and individual phases verification. The cycle is composed of individual design and development phases with well defined activities which minimizes design and development errors. |
| |
|
|
|
|
|
For the system and each of its subsystems there is a requirement specification. The requirement specification details also the functions that are risk-related. This includes functions that control risks arising from possible malfunctions or causes elsewhere in the system. The requirement specification shall include the information necessary to assure that risk control measures satisfactorily reduce the identified risks. |
|
|
|
|
| |
Hazard analysis: hazard identification is carried out. Hazards are identified for all reasonably foreseeable circumstances including normal use and incorrect use. Each identified hazard and its initiating causes are recorded.
Risk estimation: for each identified hazard the risk shall be estimated. The estimation of the risk is a product of the likelihood of each hazard and/or the severity of the consequences of each hazard.
Risk control: risks are so controlled that the estimated risk of each identified hazard is made acceptable, which means that the risk is less than or equal to the maximum tolerable risk and the risk is made as low as reasonably practicable. Methods of risk control can reduce the likelihood of the hazard or reduce the severity of the hazard or both.
|
| |
|
|
|
|
|
The architecture specification shall satisfy requirement specification. Where appropriate, the architecture specification of a system and its subsystems addresses the risk control requirements by reducing the corresponding likelihood of the hazard or by reducing the severity of the hazard or both. |
|
|
|
|
| |
|
As the design is decomposed from the requirements, the functional building blocks, architectures and technology are decided. The decomposition process end when the design information enables components to be built. Examples of such design information are circuit diagrams or software code. |
|
|
|
|
| |
|
A verification plan is produced to show how specification and safety requirements will be verified. |
| |
|
|
| |
|
Electronic subsystem design:
-
schematics design
-
PCB design
Software design:
Mechanical subsytems design
Advanced 3D mechanical construction and modeling.
Optical subsystems design
Optical simulation assisted subsystem design.
|
| |
| |
|
|
| |
|
Verification is carried out as the components are integrated to determine whether or not the implementation satisfies the requirements. Verification of the implementation of the safety requirements is also carried out. |
| |
|
|
| |
|
At the conclusion of the integration process, a validation is carried out to determine whether or not the system works as intended. Validation is designed to assure that the right product is built. Validation of the safety of the system under the conditions of the intended use is also carried out. |
| |
|
|
| |
|
The product file is the base for
CE declaration of conformity and CE marking. We can offer you the whole system CE certification procedure or we can assist you only on individual CE certification phases (for example EMC testing, testing according EN60950, ...). |
| |
| |
| |
|
|