Technical feasibility

PART B: VALORISATION PLAN

SECTION I: Testing

 

1

Has the R & D result been tested?

YES

X

NO

 

 

The following question is replied according to the reply in question 1

 

If yes

 

1a

In what mode has the result been tested?

•             Prototype

•             Pilot Application

•             Alpha/BETA testing

 

Face detection is a branch of computer vision – the science and technology that allow machines to “see”.  The meaning of “see”, in this case, is that the machine is able to extract information from an image. That information is used to execute some task. The information is extracted from a digital or digitized image by the way of real-time and optimized algorithms that have to be extremely robust when used in context as e.g. access control.

Eye-GO is a face detection software specialized to the task of recognizing faces in a scene. The main functionality is to permit the access to a protected place (e.g. a bank) only to people whose face is not totally or partially occluded.

At the current level of development the software is available on PC/Windows platform and has been tested in a laboratory context. The validation on the field requires the integration of the vision system in a CCTV circuit connected to a bank double door. In the context of the bank light conditions, camera sensitivity and resolution may be different from the laboratory and may need some tuning of the software parameters.

This is the reason why the R&D result is considered at a prototype level and it is currently in an early stage of test.

 

1b. Please describe and discuss the testing results
The software has been positively tested in a controlled environment: the laboratory.

Test activities have been made by some standard data sets used in face recognition and with some dedicated methods to include cases as partially occluded faces. The research result need to be tested in real operation conditions and in connection with a statistically significant number of events to characterize also the frequency of false alarms.

 

If no:

 

1c

Describe what type of testing does the R&D result need?
N/A

 

 

 

1d. What is the time needed for testing?
N/A
1e. What is the cost needed for testing?
N/A

 

 

SECTION 2: Current Stage of Development

 

2a

To what extent does the development team have technical resources for supporting the production of a new product? (Researchers, human resources, hardware, etc. )
Given the current stage of development and test, the activities to be completed need the integration with a real system (double door, camera, etc.) that should be provided from a third party already working in that market. Provided the access system, the laboratory may support the engineering of the product (the software). The hardware strictly necessary for the validation – with exclusion of the “door system” – is already available in the laboratory. Human resources (1 researcher) should be dedicated to the activity over a 6-months period.

 

 

 

2b

What are the technical issues that need to be tackled for full deployment, if needed?
From the software viewpoint, the main issues to be faced are related to the use of a different digital camera and to the different light conditions that may occur in the environment included between the  bank double door system.

 

 

2c

What additional technical resources are needed for the production of this new product?
The main technical issue to be faced is the physical integration with the extra hardware (doors, etc.) in a real environment. To perform that part of validation it is necessary to explore the possibility to operate in conjunction with a company that could provide a commercial solution for that hardware.

 

2d

Overall assessment of the current stage of technical development.
The result is based on some essential bricks already tested in other projects (e.g. software libraries) and on the customization related to totally or partially occluded faces. The steps needed to complete the development are mainly about some engineering activities followed by test and validation activities. The test and validation activity provides a feedback to developers for bug fixing, performance and robustness improvements.

Provided that the research result is a software that need some extra validation, and given the applicable resources and the experience of the team, it can be stated that the R&D result is in a advanced stage of development. The integration with a real system, considered necessary to complete the validation has not been started yet.

 

SECTION 3: Deployment

3a

Define the demands for large scale production in terms of
  • Materials
Negligible for the research result, the application in a product has to be made in co-operation with a third party responsible for the production.

 

 

 

  • technologies, tools, machineries
As for the previous point.

 

 

 

  • Staff effort
Given the integration on a system made before the deployment, the staff may be involved in some “after sales” activities as bug fixing or some tuning on special cases not foreseen during validation.

 

 

 

 

 

 

SECTION 4: Overall Assessment

 

1

What is you overall assessment of the technical feasibility of the research result?
The challenge is complete the validation in a real scenery, and tune the software in reasonably defined conditions. About the completion of the test environment, the main dependency is that some third parties are still to be found out. Provided the completion of the validation, the  the level of confidence about feasibility is considered good.

 

 

 

 

 

 

 

KEYWORDS QUANTITATIVE ASSESSMENT (0-5).

 

Please put X as appropriate. 1 2 3 4 5
Adequacy of testing activity undertaken so far     X    
Adequacy and availability of technical resources of the development team       X  
Current development stage       X  
Overall technical feasibility       X  

 

 

 

Bookmark the permalink. Follow any comments here with the RSS feed for this post. Post a comment or leave a trackback: Trackback URL.

Post a Comment

You must be logged in to post a comment.

Request a proposal

Valorisation Plan Authors

Related Documents

There in no related documents

Visit the other applications of the INTERVALUE Platform: R&D Repository | IP Agreements

© 2009-2010 INTERVALUE Project