You are here: Resources > FIDIS Deliverables > Interoperability > D4.10: Specification of a portal for interoperability of identity management systems > 
Home Page  Foreword


Implementation and Exploitation

The proposed development lifecycle for the portal website is shown in Chart 1. A major aim for implementing the portal is to provide a vehicle for establishing sustainability of the FIDIS project research after its completion. One or more partners may decide to develop the portal so that it can be exploited commercially, after the completion of the FIDIS project. If this is the case a business plan will need to be established. 

Developing the Business Plan 

An initial business plan should be prepared that focuses on the exploitation of the FIDIS research activities, through the application of the proposed portal, by interested FIDIS partners. The plan should be based on discussions with partners and answers from them to the following questions: 

  1. What do partners want to do? 

  2. Do partners want to exploit the FIDIS research commercially? 

  3. Do partners only want to continue the research and transfer knowledge through the portal on their publications, conferences, courses, etc? 

  4. Will partners be willing to support other organisations (either FIDIS partners or third parties) in exploiting the FIDIS results? 

  5. How much effort in terms of personnel, equipment, finance and other resources are partners willing to commit and over what period? 

  6. What is the “bottom line” for each partner? 

  7. What are the issues concerning agreements on intellectual property? 

  8. Who in the partner organisations will make the decisions? 

Sales and marketing issues to be considered include:  

  1. The need for performing a market survey on the implementation and application of an identity management portal 

  2. How large is the European market for such a portal? 

  3. What is the global market for such a portal? 

  4. Financial considerations include: 

  1. What are the envisaged potential revenues for operating a portal commercially? 

  2. What fees, if any, should be charged for using the portal, possibly on an annual subscription basis? 

  3. Will organizations be willing to sponsor the portal? 

  4. What are the envisaged costs of developing and maintaining the portal over say a 5 to 10 year timeframe? 


Issues relating to setting up and operating the portal include:

  1. Specifying the aims and objectives of operating the portal on a commercial basis 

  2. Establishing a commercial organisation. Does any partner(s) wish to take on this role? 

  3. Specifying technology requirements and establishing a website 

  4. Managing the installation and exploitation strategy 

  5. Managing the transition of the results of FIDIS to the portal 

Portal Website Development Lifecycle 







  1. Simplicity and coherency. to allow ease of use to potentially diverse audience groups.

  2. Complexity (given range and amount of info) should not be reflected in the structure presented (i.e., at GUI level, homepage /introductory pages) but instead by linking to sub pages (“behind the screen”).

  1. Specify site map 

  2. Specify page types (templates + update requirements) 

Practitioners (WP Leaders) 

and web designer 



  1. Relevance and appropriateness. A selective approach should be applied. Not “everything” should go in.

  2. Completeness and non-repeatability. Content-wise, pages should be self-contained. similar info should not appear more then once

  3. Standardisation. In terms of headings, language style etc.

  1. Review content  

  2. Proof read/ Rewrite content pages 


(WP Leaders) 



  1. Optimal user orientation (GUI)

  1. Clean, elegant look 

  2. Standardisation. In terms of navigation mechanism, graphic elements, and overall style

  3. Enhancements in the future (“smart” templates)

Web designer 



  1. Avoid limitations resulting from reliance on rigid ready-made templates 

  1. Coding designed template 

  2. Upload site onto server 




  1. Quality testing and corrections before release  


(WP Leaders) 




  1. Simple structure and selective approach to content should minimize maintenances requirements

  2. Robust design of templates and inclusion of built-in editors should allow simple updating ability.




Chart 1: Portal Website Implementation 


Home Page  fidis-wp4-del4.10.specification_of_a_portal_for_interoperability_of_identity_management_systems.sxw  Conclusions
10 / 12