Description

The state of North Carolina lacks a complete and effective statewide repository of criminal processes, including warrants and orders for arrest. Several counties maintain their own local repository. Some use a manual process, such as a collection of the paper warrants in a central location. Others are automated. The NCAWARE system provides an automated, web-based statewide warrant repository to maintain and track criminal processes and offender information. A primary goal of this project has been the migration of the existing Magistrate System from a client-server platform to a web browser-based environment, providing secure, broad access to all of the criminal justice and law enforcement communities. Initially the system will be populated by data from both the existing Administrative Office of the Courts (AOC) Magistrate System and the Automated Criminal Infraction System (ACIS). The completion of the NCAWARE system provides increased compliance with AOC's new technical architecture and completes a significant part of the many modules that together will make up the AOC's modernized Court Information System (CIS). The goals of the NCAWARE system are to:

• provide an automated statewide warrant repository to maintain and track criminal processes and offender information
• provide system access to all North Carolina court officials and law enforcement agencies
• move the AOC Magistrate System from client-server platform to a web browser-based environment
• convert existing Magistrate System data and outstanding processes in ACIS to NCAWARE

Benefits

The benefits of the new NCAWARE system are to:

• provide real-time statewide access to all law enforcement and court officials from any location with web access
• reduce risk to personal safety of the public, law enforcement officers, and court officials by equipping them with information about offenders in a timely manner
• provide the ability to print and serve outstanding processes from any county in the state
• perform automatic searches for outstanding processes on any defendant, complainant, or witness entered on a process

NCAWARE User Advisory Committee and Subcommittees

The NCAWARE User Advisory Committee is made up of a representative group of magistrates, clerks, law enforcement officers, district attorneys, and one judge. The purpose of the advisory committee initially was to help define and confirm the scope of the project and later to approve system business flows and screen prototypes. During the early stages of the project, the committee was broken down into three subcommittees: the magistrate subcommittee, the clerk subcommittee, and the law enforcement subcommittee. The purpose of each of these subcommittees was to assist the NCAWARE analysts in making decisions regarding business logic and process flows in their respective areas of expertise. The NCAWARE analysts held working sessions with each of these committees to define and confirm functionality that would be included in the system. The NCAWARE User Advisory Committee continues to be an integral part of the project as they provide input on the definition and prioritization of new features.

System Architecture

Distributed Architecture – With the help of the Gartner Group, AOC's Technology Services Division has embarked on a strategic initiative to move all supported applications to a distributed architecture built around a central enterprise server. NCAWARE is the first major AOC project in this initiative and will set the groundwork for other projects.

Development – NCAWARE has been developed as a multi-tiered J2EE web application. The design separates the logical layers of User Interface, Business Logic, and Data Access that are characteristic of n-tier systems. The advantages of using the N-tier approach for NCAWARE are as follows:

• shared code with common functions promoting code re-usability, and
• easier maintenance as common functions are developed to be independent and re-usable, meaning there is less room for error and fewer places to change code.

NCAWARE interfaces to external applications are compliant with the National Information Exchange Model (NIEM) XML standard. NCAWARE was developed using JAVA programming language, JAVA Server Pages (JSPs), and STRUTS development framework. Additionally, the team used WebSphere Application Developer (WSAD) and Rational requirements management and defect management tools.

Deployment – The NCAWARE system is deployed on the AOC Enterprise Server (IBM Mainframe) and runs on IBM's WebSphere Application Server. The database is DB2, and the messaging component is WebSphere MQ Series, also running on the Enterprise Server.

Security – Login security is handled by AOC's single sign-on process, using LDAP managed by RACF on the mainframe for user authentication. Once authenticated, user permissions are granted using DB2 table-based rules.

NCAWARE Project Update

Action	Purpose	Timeline
Major Enhancements	1. Add Orders for Arrest for Child Support	TBD
	2. Interface with eCitation	TBD
	3. Direct Criminal Contempt	TBD
	4. Department of Correction Interface	TBD
	5. Build Interfaces - local law enforcement systems, - DOC Offender Population Unified System (OPUS) and local jail systems for prison / jail status, release dates and other person data	TBD

Rollout to 64% of the counties	Deploy system to the following counties:	Timeline:
	1.  Greene	July 15, 2009
	2.  Wake	July 22, 2009
	3.  Martin	August 5, 2009
	4.  Wayne	August 5, 2009
	5.  Orange	August 19, 2009
	6.  Chatham	August 19, 2009
	7.  Person	August 26, 2009
	8.  Durham	September 9, 2009
	9.  Alamance	September 16, 2009
	10. Caswell	September 16, 2009
	11. Lenoir	September 23, 2009
	12. Jones	September 23, 2009
	13. Cumberland	September 30, 2009
	14. Hoke	October 7, 2009
	15. Brunswick	October 14, 2009
	16. Duplin	November 4, 2009
	17. Pender	November 4, 2009
	18. New Hanover	November 18, 2009
	19. Craven	December 2, 2009
	20. Pamlico	December 2, 2009
	21. Northampton	December 9, 2009
	22. Perquimans	December 9, 2009
	23. Hertford	December 16, 2009
	24. Chowan	December 16, 2009
	25. Washington	January 6, 2010
	26. Tyrrell	January 6, 2010
	27. Dare	January 20, 2010
	28. Currituck	January 20, 2010
	29. Beaufort	January 27, 2010
	30. Hyde	January 27, 2010
	31. Pasquotank	February 3, 2010
	32. Camden	February 3, 2010
	33. Gates	February 10, 2010
	34. Bertie	February 10, 2010
	35. Onslow	February 17, 2010
	36. Carteret	February 17, 2010
	37. Halifax	February 24, 2010
	38. Franklin	February 24, 2010
	39. Pitt	March 3, 2010
	40. Guilford	March 17, 2010
	41. Moore	March 24, 2010
	42. Granville	March 24, 2010
	43. Vance	April 7, 2010
	44. Warren	April 7, 2010
	45. Forsyth	April 14, 2010
	46. Stokes	April 14, 2010
	47. Sampson	April 21, 2010
	48.  Rockingham	April 21, 2010
	49. Columbus	April 28, 2010
	50. Bladen	April 28, 2010
	51. Robeson	May 5, 2010
	52. Randolph	May 12, 2010
	53. Montgomery	May 12, 2010
	54. Richmond	May 19, 2010
	55. Scotland	May 19, 2010
	56. Davidson	June 2, 2010
	57. Yadkin	June 2, 2010
	58. Wilkes	June 9, 2010
Statewide rollout	Deploy system in remaining counties statewide	Mid 2010 – Late 2010

 The Future

After successful implementation of the top five major enhancements, the AOC will develop additional system features and other interfaces.

« this page last modified 06/10/10 »