Pennsylvania s Global XML Document Creation Process (DCP) Pilot Project

Transcription

1 Pennsylvania s Global XML Document Creation Process (DCP) Pilot Project

2 Problem Statement JNET recognized a need for a repeatable Global XML compliant message exchange process. Process must define artifacts describing the exchange. Technical guidelines must assist agencies in developing Global XML schemas & other required artifacts from the message development procedures.

3 Problem Statement Message repository must be developed to store Global XML message development artifacts. The repository would be used by state agencies to create applications to produce and/or consume XML messages defined by existing schemas & artifacts. The message repository would be used to provide starting points for new message exchanges & promote consistent usage of the Global XML.

4 Project Introduction 2004: Pennsylvania awarded grant; Perform Global XML Document Creation Process (DCP). Successfully completed proposed pilot project activity: Developed Project Charter & Business Requirements Assessed Resource Allocation Developed Communication Plan Developed Message Development Process Documentation Evaluated, Selected & Implemented Tools Validated the defined Process

5 Documents Created Create a repeatable process for Global XML compliant message exchanges in the JNET infrastructure. A process was documented that identified a clear set of artifacts describing each Global XML message exchange. The resulting artifacts were grouped into two major sets of documents: 1. JNET GJXDM Message Development 2. JNET GJXDM Message Technical Guidelines

6 Repository Requirements A message repository will store message development artifacts. The repository will be used by state agencies to facilitate creation of applications that produce and/or consume Global XML compliant messages defined by schemas & other artifacts stored therein. The message repository will be used to provide a starting point for new message exchange & to promote Global XML consistency.

7 Keys to Success Agency commitment & participation. Buy in throughout participation. Develop a project charter & set scope. Gather business requirements. Driven by business not by technology. Allocate resources & evaluate throughout the project. Create a Communications Plan & market it. Create a clear task plan.

8 Keys to Success Schedule weekly meetings & insist on coordination & collaboration. Assign appropriate resources, driven by stakeholders: SME s GJXDM trained XML Savvy Assign a Project Manager. Assign an architecture resource. Ensure strong executive leadership. Engage all stakeholders & provide feedback.

9 Outcomes & Benefits For the user: Consistency across domains. Process absent technical detail for business users. Business user can become comfortable with a single dictionary (GJXDM, NIEM). For the public: Consistency across justice entities compliments public safety initiatives. Timely development of interagency exchanges. Implementation of PACSES warrant event message enables child support collection effort. For the practitioner: Guidelines for development teams. Documented deliverables for contract or project proposals.

10 Lessons Learned What went well: Obtained Executive sponsorship. Appropriate personnel resources. Documented Project Charter. Preliminary walkthrough identified gaps in documentation & process. Input & participation of business process owner. Remained focused throughout project lifecycle. Task list & communication plan were implemented & monitored by PM. Consistent input from all team members. Implemented repeatable process & began using the tools.

11 Lessons Learned What could have gone better: Challenging to complete some assignments & attend meetings due to other commitments. Additional brainstorming sessions in the initial phase would have distributed efforts & resulted in a more comprehensive document. Educating the user community (business owner) on GJXDM. Creating various documents that were required during pilot. Repository selection constraints.