You are here: Resources > FIDIS Deliverables > Other > D8.3: Database on Identity Management Systems and ID Law in the EU > 
Example of Questionnaire response  Title:
EXAMPLE OF IMS RECORD
 Maintenance Plan

 

Example of IMS Record

select id_ims, imsname from ims order by imsname, id_ims select imsname from Ims where id_ims = #NextId# select imsname from Ims where id_ims = #PreviousId# select * from ims where id_ims=#url.id_ims#  

 

 

 

IMS Details  

 

 

 

 

 

 

 

 

Name : #imsname#  

 

  

Evaluator :  

#Evaluator# 

  

Organisation :  

#Organism# 

  

Date of evaluation :  

#dateformat(Dateofevaluation, "dd-mmm-yyyy")# 

 

 

 

  

Sources of information :  

#Reference#

  

Version :  

#Version# 

  

Manufacturer :  

#Manufacturer# 

  

Nature :  

#Nature# 

  

Country :  

#Country# 

  

Regions :  

#Geogscop# 

 

 

 

  

Language :  

#Language# 

  

State :  

#State# 

  

Open/Closed :  

Open IMS: the identities work with several systems or applications. Closed IMS: the scope of the identities is restricted to the IMS context.  

 

 

 

  

Requirements :  

 #Requirement#

  

Number of users :  

 #Userbase#

  

Standards :  

#Standard# 

  

Description of Server - 

Side components :  

#Server# 

  

Description of methods :  

#Control# 

  

Descriptor of Client - 

Side components :  

#Client# 

  

Seals :  

Yes: Privacy and other seals that certify that the IMS applies to law. No  

  

Which seal :  

#Whichseal# 

  

Third party :  

#Val3rdparty# 

  

Which third party :  

#Which3rd# 

 

 

 

  

Features :  

#Features# 

  

Screenshot picture :  

 

  

Flowchart :  

 

  

Price :  

#Price# 

  

Comment to the Cost :  

#CostComment# 

  

Type of IMS :  

Type 1: IMS for account management. 

Type 2: IMS for profiling of user data by an organisation. 

Type 3: IMS for user-controlled context-dependent role and pseudonym management.  

  

Class of IMS :  

Class 1: Pure IMS which main objective is to support or implement identity management functionality. 

Class 2: Systems/applications with another core functionality. 

Class 3: Systems/applications which are independent from identity management functionality. 

 

  

Functionality :  

#IMSFunction# 

  

Suggestions :  

#Suggestions# 

 

 

 

 

Every effort has been made to check the information shown with the manufacturer. Nevertheless errors may remain. 

If you would like to change any part of this record, please send your comments to the IMS team. 

 

 

 

 

 

 

 

 

 

 

 

Example of Questionnaire response  fidis-wp8-del8.3.DB_IMS_Law.20060224.sxw  Maintenance Plan
27 / 53