Services and Exchange Implementation

In today’s justice and public safety IT environments, most agencies employ largely standalone legacy systems that were primarily procured to facilitate a specific business function or need. These “stovepipe” systems are typically developed in an isolated environment without information sharing in mind and no plans to become part of an enterprise-wide integration effort. As a result, these systems are not readily compatible with other systems and cannot share or communicate information efficiently and effectively.

Many believe that if they invest in an entirely new system, they will fix this issue of standalone or stovepipe systems. Although this may be true, it’s most often not a cost-effective solution. At URL, we believe in saving you time and money by utilizing your existing legacy systems and complementing it with a standards-based approach using open technologies in the form of service-oriented architecture- (SOA) based Web services.

SOA-based Web services are a set of integrated business processes or services that are identified, standardized and organized as a result of a larger business process analysis for all related stakeholders and existing systems.  These identified services can then be accessed and delivered across two or more systems over the Internet to facilitate the business process. SOA is not a trivial undertaking; it requires the adoption of a service paradigm and infrastructure.  However, once this has been adopted and exchanges have been implemented, the open architecture enables agility and scalability without dependence upon proprietary vendor solutions.

The final outcome of a SOA-based Web services solution is the automation of the business process and workflow where information is automatically sent, or pushed, to agencies that need the information to support their component of the overall business process and workflow. The best part – by leveraging SOA-based Web services, information exchanges occurs automatically no matter where or what type of system the information originated from.

With URL’s Exchange Implementation services, you can expect the following results:

  • Creation of each service, based on previously defined business requirements that the sending and receiving agencies wish to exchange, including clear agreed upon rules, policies, security, and privacy provisions in support of business processes and workflows,
  • Development of IEPDs (Information Exchange Package Documentation) that will standardize and classify the content of the exchanges. This includes a combination of mutually supportive artifacts and NIEM-conformant schemas that share a common, unambiguous understanding and meaning of the information being exchanged,
  • Development of a Service Specification Package that defines the specific business context and behavior in which the service will operate. This includes the WSDL (Web Service Definition Language) in combination with IEPDs for each selected exchange to generate endpoint code used to facilitate the process of sending and receiving information and messages,
  • Implementation and deployment of Web services-based SOA mechanisms, including test plans, scripts, testing with each endpoint, and user end-to-end testing.