Leadership through Partnership: One step at a time

1
Leadership throughPartnershipOne step at a time

• Alistair Rondeau PSEPC - Data Standards
  Secretariat Mgr.
• Ed Buchinski TBS/CIOB - IM E-enabler
  POC PM
• Aziz Abouelfoutouh PWGSC -
  Registry/Repository PM
• Susan Berg HC / RCMP - SSDUE II PM
• Ken Dagg Fujitsu Consulting -
  Industry Partner

2
Agenda

• Presentation Objectives
• Background
• Definition of Terms
• Collaborative Project Involvement 5
  Perspectives
• Conclusions
• Managing Collaborative Projects

3
COLLABORATION

• A process through which parties who see
  different aspects of a problem can explore
  constructively their differences and search for
  (and implement) solutions that go beyond their
  own limited vision of what is possible.
  Taylor-Powell et al., 1998

4
Purpose of Presentation

• Collaborative Project - 5 Perspectives
• Architecture..BTEP / UMM
• Information Design.....PSEPC - PSID
• Supporting Infrastructure...PWGSC reg/rep
• Business / Project MgmtSSDUE II
• Technology...Industry

5
Implications for Information Mgmt.

• Changing focus from IT to IM
• Cross Departmental Perspective
• Access to Information
• Privacy Impact Assessment
• Document Security Designation
• Audit Trail
• Business Process Analysis
• Records Management
• Long Term Storage / Archives Management
• Data Integration
• Acceptance of Electronic Signatures

6
SSDUE 1 PARTNERS
7
Current Activity Volume
8
Process Inefficiencies

• Redundant Form/Data Entry
• Inaccurate/Missing/Lost data (data quality and
  integrity)
• Process latency
• Inefficient use of resources (human/paper)
• Difficulty tracking documents and process status

9
SSDUE 1 Accomplishments

• Business Transformation Methodology
• Partnerships / E-collaboration Value
• Interoperability in multi departmental
  environment
• Information Sharing (common data element / XML)
• Tool Integration (eform / business process /
  security)
• ebXML application framework for government
• Non Proprietary solution
• Security must be at the application / transaction
  level not network level

10
IM e-Enabler / SSDUE II Collaborative Project
Objectives

• Tactical (SSDUE II)
• To implement an operational drug offense and
  disposition system
• Strategic (IM e-Enabler)
• To assess the viability of using evolving
  standards, technologies and methodologies
• To apply standards based solutions and innovative
  technology to the extent possible
• To assess the risk of adopting these standards,
  technologies and methodologies
• To assess the ability of an ebxml registry /
  repository to facilitate the discovery and reuse
  of shareable project artefacts

11
The Broad Challenge

• Create a secure, high-performance electronic
  environment through which government departments
  can collaborate and interoperate for service
  delivery.

12
The Broad Challenge

• Utilization of the secure, high-performance
  electronic environment by government departments
  to collaborate, interoperate and discover / offer
  services.

13
Definition of Terms

• Collaboration
• Interoperability
• Business Transformation
• Its important to begin with a common
  understanding of these terms

14
Interoperability

• The ability of different types of computers,
  networks, operating systems, and applications to
  work together effectively in order to exchange
  information in a useful and meaningful manner.
  SATBs Aug 10, 2004
• The end result is seamless sharing of trusted and
  reliable information between partners in
  compliance with GoC policies, security and
  privacy directives.

15
Business Transformation

• Fundamentally rethinking and redesigning the
  underlying structure of a government program
  service and how it is delivered. (TBS - BTEP)
• Business Transformation will result in the
  improvement of the quality and / or delivery of
  Programs, Services and Processes
• Attempting to achieve dramatic improvements in
• Client satisfaction
• Cost efficiencies / savings
• Achievement of policy outcomes / compliance
• Accountability and transparency

16
 Interoperability Framework
17
Architecturea BTEP/UMM Perspective

• Ed Buchinski
• Treasury Board Secretariat

18
 Architecture BTEP / UMM
19
Business Transformation Enablement Program (BTEP)
row 1 2

• BTEP Goal
• to enable coherent business design across the
  government with a formal, standards-based
  approach that will guide and expedite business
  transformation to meet the governments high
  level business objectives. BTEP Program
  Synopsis 1.5b Feb. 18, 2004
• BTEP Elements
• Transformation Framework - (govt version of
  Zachman Framework)
• A defined set of "deliverables" that
  transformation teams would produce (i.e.
  visions, strategies, designs, )
• Government Strategic Reference Models (GSRM)
• Enablers - logical groupings of core business
  capabilities (row 3-5)

20
United Nations Modelling Methodology (UMM) row
1- 3

• Subset of Unified Modelling Language (UML) and
  Rationale Unified Process (RUP) specialized by
  UN/CEFACT / OASIS to support business process and
  information modeling
• Simpler
• Business process meta model
• Based on international standards for Open-EDI,
  data definition and interchange
• Designed to enable small /medium enterprise to
  participate in electronic commerce.

21
UMM Framework
CPSIN
SSDUE
22
GSRM Program Services Top Model
23
UMM Sample Worksheet
24
BTEP/UMM Zachman
25
Making BTEP/UMM Visible and Real

• VISIBLE
• Defined IM e-Enabler Proof-of Concept to
• Implement and validate that a registry can be
  used to register, share and manage metadata,
  information models and business processes
• Collaborate with PWGSC, PSID Data Standards
  Secretariat and SSDUE II partners to realize IM
  e-Enabler objectives
• Investigate registry requirements and options for
  XML standards adoption
• Explore inter-working between web services and
  ebXML registry technologies

26
Making BTEP/UMM Visible and Real

• REAL
• Collaborate with SSDUE II implementation project
  to
• Use UMM worksheets (including UML state diagrams)
  to define the business requirements and business
  transactions views for SSDUE II
• Confirm that the CPSIN data dictionary, GSRM
  (BTEP) classification schemas, information models
  and business processes could be shared using a
  registry/repository
• Investigate potential of modelling tools and
  e-form applications to exchange re-usable design
  information with the registry repository

27
BTEP/UMM Relationship

• BTEP Methods and Models add Government dimension
  to UMM by providing
• business semantics that are understandable at
  federal, provincial and municipal levels,
• contextual domains (Govt. Programs and
  Services),
• patterns for government services (BTEP) versus
  industry processes (UMM),
• a classification methodology - (GSRM Top Model),
• a more rigorous definition of the key UMM
  concepts,
• alignment of business process and transaction
  models (e.g. UML analysis models) across
  government services and programs

28
Information DesignPSID / CPSIN Perspective

• Alistair Rondeau - PSEPC

29
Public Safety Interoperability Directorate
30
PSID Contextual Influence decision on common
vision

• Standard for exchange of information only.
• 2 programs are required
• One to send
• One to receive
• Same program can be re-used to interact with any
  other partner.

31
PSID Contextual (contd) Influence decision on
common vision
SSDUE II Data Exchange Environment

• CBSA seizes drugs
• RCMP sends data to HC
• HC gives permission to destroy the drug

32
PSID Conceptual Clarify information concepts
SSDUE II Data Requirements
CPSIN Logical Data Model
        Defendant         Name        
Sex         Place of Birth         Date of
Birth         Address        
Occupation         Citizenship
MAPPED
33
PSID Logical Provide names, definitions and
code values
CPSIN ISO 11179 Template
Code Values
34
PSID Physical Provide guidance on XML
ltcOffendergt
ltpTravelTimegt8
35
PSID Implementation Proper use of CPSIN Data
Standards
A Business Transaction Schema validates XML for
Partner applications.
36
CPSIN Perspective of the Project

• Proved that CPSIN data standards are relevant and
  applicable
• Data standards plus UMM worksheets enabled the
  development of SSDUE II data exchange
  transactions
• SSDUE II has built an instance of CPSIN
• Leverages common infrastructure design using
  e-collaboration hw / sw
• Extending CPSIN data standards to GoC requires an
  enhanced governance structure

37
Supporting Infrastructurea PWGSC Perspective

• Aziz Abouelfoutouh

38
PWGSC
39
Registry Services

• Enables analysts to discover and reuse project
  artifacts (data elements, business processes,
  business information entities etc.)
• Enables analysts to create and register new
  artifacts and supports application design
• Allows cross referencing of data standards /
  project artifacts across multiple domains
  nationally and internationally
• Facilitates registration and discovery of
  services

40
Registry POC (IM e-Enabler Project)

• Implemented an ebXML registry for the POC
• Loaded the CPSIN data dictionary in the registry
• Loaded GSRM classification in the registry
• Made registry information available to partners
• Demonstrated the applicability of the registry to
  an interoperability project during design time
• Reviewed available registry products

41
Registry POC Findings

• Standards are still evolving
• ebXML specifications
• Format for binding data elements to a registry

42
Registry POC Findings

• Products are maturing
• No product meets all the requirements
• There are risks of being limited by a vendor
  specific implementation
• Product not compliant with ebXML specs
• Product does not have the full functionality
  implemented
• Product has additional functionality that is not
  covered by specs

43
Registry POC Conclusions

• Current standards products are sufficient to
  begin initial implementation
• To guarantee interoperability, acquire standards
  compliant products and avoid vendor extensions
• Models developed for this project are highly
  relevant to the completion of several
  international standards as the OASIS CAM and
  UN/CEFACT CCTS
• Gov agencies must pay attention, use and
  contribute to international standards that are
  critical to interoperability

44
ebXML Registry Functionality

• Lifecycle management
• Query management
• Event notification
• Content management
• Security
• Version control
• Registry Interoperability (co-operating)

45
Shared Registry Services Pilot

• Funds approved for shared registry services pilot
• PWGSC resources committed
• Additional partnerships formed (PSCIOC, Ontario
  MBS, Industry Canada, etc.)
• Pilot Project charter and plan being developed
• Registry at http//ebxml.pwgsc.gc.ca

46
Business Implementationan SSDUE Perspective

• Susan Berg

47
SSDUE II
48
Re use Value

• BTEP / UMM Methodology
• PSID Data Dictionary (XML Schema)
• Registry
• Business Area Analysis Artifacts
• BPA, PIA, MOUs, IRA, TRA, System Requirement
  Specification, Data Model)

• Next Steps
• SSDUE III
• Other processes / communities of interest

49
Technology Prototypean Industry Perspective

• Ken Dagg

50
Industry
51
IM / IT Industry Objective
Beyond satisfying client expectations for a
standards based, technology independent solution

• To demonstrate re-usability and extensibility of
  the proposed solution
• To confirm that the BTEP vision CAN be realized
  TODAY
• to enable coherent business design across the
  government with a formal, standards-based
  approach that will guide and expedite business
  transformation to meet the governments high
  level business objectives.

52
BTEP UMM Findings

• Worksheets useful but repetitive in documenting
  business information and system requirements
• Extensions added to
• document the difference between current and
  proposed process
• reference internal legacy system interaction
• map the business information model to the data
  model
• Additional clarity needed in applying the
  methodology and worksheets

• Bottom Line
• BTEP is a Public Sector extension to UMM
• business requirements are isolated from the
  technical solution

53
Data Standards Findings

• The generic nature of the model allows use by
  public and private sectors for data exchange
• PSIDs application of ISO 11179 allows a wide
  range of government business information to be
  defined in an application and technology neutral
  manner
• Guidance and assistance from the DSS Secretariat
  required to apply data standards in a consistent
  manner
• Additional documentation and tools would
  facilitate use of these standards

• Bottom Line
• facilitate design, development and implementation
  of the prototype
• should enable reuse and extension

54
Prototype Findings

• Secure, ebXML interoperability with bilingual and
  internationalisation capabilities can be
  implemented
• Standards-based B2B protocols can fulfill the
  needs of the SSDUE initiative
• While cross-vendor ebXML communication (ebMS) is
  possible, products from different vendors are not
  at the same level / versions of standards
• Custom coding is required
• Technical skills / expertise is available

• Bottom Line
• Technology is no longer the limiting factor
• Level of maturity of the industry requires extra
  support

55
Generic Technology Configuration
56
Prototype Technology Architecture

• RCMP

• Health Canada

57
Fujitsu Consultings Perspective

• BTEP, as a Public Sector extension of UMM, is
  usable and valuable
• Data Standards facilitated design and should
  facilitate development and implementation as well
  as reuse and extension
• The prototype showed that technology is no longer
  the limiting factor

58
Conclusions

• Susan Berg

59
INTEROPERABILITY

• Does not require all participants to adopt the
  same internal architecture / technology solution
• Requires consensus on the inter -organizational
  architectural aspects of
• Business
• Information
• Technical Standards
• Supporting Infrastructure

60
INTEROPERABILITY SOLUTIONS

• Feasible / Viable / Affordable
• Technology neutral (not ebXML or XML dependant)
• Hospitable to evolving standards
• Non intrusive to existing systems
• Extensible to new partners, new processes, new
  data with minimal changes
• Highly modular (does not break if one piece
  changes)
• Secure and Reliable

61
Interoperability Next Steps

• Extended deployment must be supported by
• - Next generation of BTEP / UMM
• - Enhanced standards development and management
  process
• - Extended supporting infrastructure robust,
  operational registry system and modeling tools
• - Incentives for the development and re-use of
  business information and technology components

62
Critical Success Factors

• Governance is key (roles / responsibilities /
  authority)
• Senior Executive understanding / commitment to
  taking a strategic approach to implementing
  tactical solutions
• Understand what the true barriers are
  (interoperability can occur without huge upheaval
  or cost)
• Collaboration is key to an interoperable project
• Focus on what we have in common not on how we
  differ
• Focus on the business first and use technology as
  an enabler
• Effective management of strategic and tactical
  considerations
• Address security and privacy issues from
  beginning to end

63
Managing Collaborative Projects
64
Challenges

• Engendering a common purpose
• Doing the right things for the right reasons
• Competing priorities
• Horizontal / vertical management (authority,
  accountability, resources)
• Technology then business
• Continual adjustment and reframing
• Tunnel Vision dept / employee
• Politics, Power and People

65
Collaborative Project Management

• Governance
• Enterprise view
• Human element
• Roles (delegation of authority)
• Cultural differences
• Competing Priorities
• Synchronization of schedules
• Shift in human resource commitments
• Communication

66
Positive Results

• Strong interdepartmental relations encourage and
  facilitate
• Multi level collaboration (business, technology,
  privacy, security, legal, ATIP)
• Common
• Understanding / message / standards
• Economies of scale (centralized budget, TRA, PIA,
  IRA, BPA)
• Harmonization of policy, procedures, processes
• Re-use