1 GISWG Services Committee Report Scott Fairholm, Chair October 5, 2006 Alexandria, Virginia

Global Information Sharing Initiatives Executive Briefing Global Information Sharing Initiatives Executive Briefing 2 Resolution The Services Committee agrees with the EAC recommendation of a services capability approach. We agree that two documents are needed: 1) Service Identification Methodology, and 2) Service Specification. The law enforcement domain was selected for capability identification. This was further initially narrowed to single class of capabilities (i.e., Fingerprint Identification) Rationale: Balancing risk and value, we believe that this set of capabilities gives high return, and the governance issues are largely understood (and acknowledged/considered by the Services Committee) and not anticipated to pose significant concerns/impediments.

Global Information Sharing Initiatives Executive Briefing Global Information Sharing Initiatives Executive Briefing 3 Resolution The Service Specification, with Fingerprint Identification as example, will be addressed first. Subsequently, the Committee will address the Methodology.

Global Information Sharing Initiatives Executive Briefing Global Information Sharing Initiatives Executive Briefing 4 Deliverable The draft Services Definition Principles document was tentatively approved, pending further Committee review Schedule: next two weeks – final vetting To be incorporated into the JRA, Services Specification, and/or Methodology document

Global Information Sharing Initiatives Executive Briefing Global Information Sharing Initiatives Executive Briefing 5 Assignment to Services Interaction Committee Develop a Registry Taxonomy that fully specifies a service and facilitates input into a repository Will address metadata issues, for inclusion into the Services Specification document

Global Information Sharing Initiatives Executive Briefing Global Information Sharing Initiatives Executive Briefing 6 Issue for Resolution by the EAC The JRA does not address user-specific issues. How do we address user/system-level security concerns in the JRA, and should we address this issue in the service specification? E.g.: -- An agency has a policy that X information will only be provided to Y people; OR --Juvenile information will not be provided to certain people? --Don’t know until you see the data

Global Information Sharing Initiatives Executive Briefing Global Information Sharing Initiatives Executive Briefing 7 Product from this Meeting Jim Douglas (with Iveta) will draft an initial Service Identification Methodology document Outline for Services Specification document Considering discussions in Alexandria, Sharad to flesh out outline, for vetting by Committee The next anticipated deliverable from this group, tentatively slated for completion by December To be validated by first instance Outline as follows:

Global Information Sharing Initiatives Executive Briefing Global Information Sharing Initiatives Executive Briefing 8 Services Specification Document: Draft Outline I.Service Name – [Fingerprint Identification Service] A.Version B.Lifecycle management II.Context A.“Real world effect of this service is…” B.Applicability III.Service Overview A.Description B.Scope IV.Business Scenarios (elaboration/illustration of the Overview) V.Assumptions and Dependencies Purpose: Expectation management.

Global Information Sharing Initiatives Executive Briefing Global Information Sharing Initiatives Executive Briefing 9 Services Specification Document: Draft Outline VI.Information Model a.Includes logical description of model b.Include an IEPD(s) directly, or by reference c.If IEPD is unavailable, includes comparable artifacts VII.Behavioral Model a.Processing Rules i.Functional model ii.BPMN (recommended) for this specific use case (sequence diagram) b.Fault Handling c.Profiles VIII.Service Interface a.Including formal service interface specification (e.g., WSDL) service template

Global Information Sharing Initiatives Executive Briefing Global Information Sharing Initiatives Executive Briefing 10 Services Specification Document: Draft Outline X.Visibility (Taxonomy) a.Naming b.Versioning c.Lifecycle Management XI.Considerations a.Security b.Service Interaction Profiles (SIPs) c.Execution Context i.Performance ii.Deployment iii.Enabling