Cityworks Server PLL is designed for public agencies that manage permits, projects, inspections, and other activities related to permitting, planning, and engineering review.  An intuitive workflow engine accurately tracks the process from application or request through departmental plan reviews, fee collection, inspections, regulatory meetings, hearings, and more.

Most permits and applications span an array of public departments, including building, planning, and engineering.  Cityworks Server PLL enables agencies to share and access pertinent information easily and efficiently, streamlining the application and review process across departments, and delivering substantially higher levels of customer service for contractors and citizens.

Through an easy-to-use map-based, web interface, agency staff can initiate applications from contractors and citizens, efficiently managing the review, inspection and oversight process.  With consistent and uniform data, fees are quickly and accurately calculated while inspections are handled more timely through e-mail and text messages.  Flagged items and issues can be dealt with throughout the project with conditions added to meet specific regulatory requirements.

Unique to Cityworks Server PLL, GIS data is available directly within the application, allowing agencies full access to the geo-database spatial and attribute data.  Map views can be customized per user, group, or department, while permits and projects can be attached to any GIS (asset) feature.

A Common Interface

Building Departments are responsible for reviewing construction plans, issuing permits, and ensuring adherence to code requirements on commercial and residential projects.  Planning staff manages proposed development to stimulate safe, livable communities and a sustainable economy.  Proper planning governs how land use interacts with housing, transportation, open space, and economic development, giving a community its personality.  Engineering guides the construction of public infrastructure necessary to sustain communities, including roadways, utilities, storm runoff, and right-of-way usage.

Cityworks Server PLL is the common link between these and other departments enabling them to share critical information and ensure that all permits and projects are processed efficiently and correctly.

Tasks and Workflows

Operational accountability and efficiency are a top priority of public officials now more than ever before. Most all business processes span the array of agency departments, requiring the proper review and approval from several key staff.  Though the consequences of an oversight vary, it can lead to costly mistakes and the potential for litigation.

Public agencies look to technology to automate, streamline and accurately manage key business processes, building accountability, staff productivity, and optimal customer service.  The workflow engine in Cityworks Server PLL is designed specifically to meet these needs and others.

The Cityworks Server PLL workflow engine is the “work horse” of the system enabling organizations to configure business processes that meet a single, specific task or span multiple departments.  Once a permit or case is created, several people may interact with it, updating tasks in the workflow.  Workflows create two levels of accountability.  Workflow tasks can be setup for a specific user or group of users, drawing accountability through a critical path methodology, requiring the completion of tasks and events before proceeding.

Workflows consist of tasks and events required by a permit, project, case, or other application type. Tasks include review, inspection, and hearing with the difference being how the task may be scheduling.  Inspections can be scheduled on demand, while review tasks are automatically scheduled in association with due dates defined for the given workflow.   Hearings are typically scheduled based on the type assigned to the task.

Tasks are organized into milestones, which dictate the progression of the permit or case.  Tasks can also span milestones.  For example, a task can be made available in Milestone 1 and “float” until Milestone 4, enabling the workflow to track complex phases of a project, common to public agencies.

The result of each task determines the next step in the workflow.  A permit or case may close at the completion of a task, create a child permit or case, redirect the workflow, open the next milestone, create a work order or simply update the status.  Those associated to the permit or case can be notified via email the result of a task.

 

Print Friendly, PDF & Email