Resources
- Identity Use Cases & Scenarios.
- FIDIS Deliverables.
- Identity of Identity.
- Interoperability.
- D4.1: Structured account of approaches on interoperability.
- D4.2: Set of requirements for interoperability of Identity Management Systems.
- D4.4: Survey on Citizen's trust in ID systems and authorities.
- D4.5: A Survey on Citizen’s trust in ID systems and authorities.
- D4.6: Draft best practice guidelines.
- D4.7: Review and classification for a FIDIS identity management model.
- D4.8: Creating the method to incorporate FIDIS research for generic application.
- D4.9: An application of the management method to interoperability within e-Health.
- D4.10: Specification of a portal for interoperability of identity management systems.
- D4.11: eHealth identity management in several types of welfare states in Europe.
- Profiling.
- Forensic Implications.
- HighTechID.
- Privacy and legal-social content.
- Mobility and Identity.
- Other.
- IDIS Journal.
- FIDIS Interactive.
- Press & Events.
- In-House Journal.
- Booklets
- Identity in a Networked World.
- Identity R/Evolution.
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:
What do partners want to do?
Do partners want to exploit the FIDIS research commercially?
Do partners only want to continue the research and transfer knowledge through the portal on their publications, conferences, courses, etc?
Will partners be willing to support other organisations (either FIDIS partners or third parties) in exploiting the FIDIS results?
How much effort in terms of personnel, equipment, finance and other resources are partners willing to commit and over what period?
What is the “bottom line” for each partner?
What are the issues concerning agreements on intellectual property?
Who in the partner organisations will make the decisions?
Sales and marketing issues to be considered include:
The need for performing a market survey on the implementation and application of an identity management portal
How large is the European market for such a portal?
What is the global market for such a portal?
Financial considerations include:
What are the envisaged potential revenues for operating a portal commercially?
What fees, if any, should be charged for using the portal, possibly on an annual subscription basis?
Will organizations be willing to sponsor the portal?
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:
Specifying the aims and objectives of operating the portal on a commercial basis
Establishing a commercial organisation. Does any partner(s) wish to take on this role?
Specifying technology requirements and establishing a website
Managing the installation and exploitation strategy
Managing the transition of the results of FIDIS to the portal
Portal Website Development Lifecycle
Phases | Guidelines | Duties | Personnel |
Structure
|
|
| Practitioners (WP Leaders) and web designer |
Content
|
|
| Practitioners (WP Leaders) |
Design
|
| Web designer | |
Programming
|
|
| Programmers |
QA
|
| Practitioners (WP Leaders) | |
Maintenance
|
|
|
|
Chart 1: Portal Website Implementation
10 / 12 |