Our "normal" projects have in the past followed the following 5 major steps:

Inventory High Level Impact Analysis phase Low Level Impact Analysis phase Rectification Final Testing

For more information on this project approach download our "Overview of Embedded Systems Project". As stated earlier this project requires intensive Engineer activity which meant that we were as accessible to organisations as our Engineers time allowed. We therefore developed this "Web Site Approach" to make our expertise and database more accessible.

This approach employs a number of the philosophies of the normal project except that the organisation is able to very quickly get a feel for the effect that the turn of the century will have on its devices and gauge the amount of work required to rectify the problematic areas. They are then able to decide for themselves what specialist skills (such as engineering time) they require to complete the project.

Essentially this involves the organisation completing an inventory in the manner prescribed by the methodology on worksheets provided and these are then e-mailed to Into2k. These inventories are then run against our database in order to obtain:

-a compliancy categorisation of each device
-a warning, in certain cases, about how the compliancy categorisation could affect the device itself or the environments in which it commonly operates.
-rectification suggestions
-supporting documentation

We normally experience a ratio of inventory devices to database hits of 60% to 80%. In the case of devices not identified on the database the engineer responsible for the run will discuss the device with the design engineer of the manufacturing company and will then express an opinion as per the standard report.

The minimum engineers cost for conducting the run and individual device investigation is £750.00 (or equivalent acceptable currency) per 500 devices.

Once you have received the results of the run you may then make a decision as to whether you want to utilise our engineers to conduct any low level tests (these are explained in the methodology) on site or not.