Challenge Summary
Welcome to “Planning and Zoning Report System - Order Processing Wireframes Challenges”. Our client would like to re-architect their current intranet Planning and Zonning Report (PZR) application into a modern technology and create several new features as an enhancement to the application. We already have the conceptualization and got several client documents for your references. In this challenge, we want to see a solution for the new application workflow that able to organize the content in a proper ways and create the functional areas of the application into an intuitive and easy to navigate.
At the end of this challenge, we would like to see a solution that meet all required functionality, user friendly, intuitive and easy to use.
Round 1
- Order Processor Workflow
- Project Coordinator Workflow
- Information Specialist Workflow
- Follow Up User Workflow
- Report Writer Workflow
Round 2
All requires Workflow Scenario as stated in challenge details along with client feedback applied
The client for this project is the Planning and Zoning Resource Corporation (PZR). PZR collects public zoning information on individual pieces of commercial properties, analyzes this information, and generates reports for a variety of clients and stakeholders.
In the United States, every city and county (jurisdiction) has its own zoning laws. Many of these zoning laws are available by going to the offices of the jurisdiction personally (although some are available online). Since the 1990’s PZR as amassed the zoning information for over 100,000 unique commercial properties in over 10,000 jurisdictions. This data is used to create a report which they provide to their customers and stakeholders.
The reports generated by PZR are made up of two parts:
1. The public information collected
2. The analysis performed by PZR.
In order to deliver a report, members of the PZR staff, segmented into groups who specialize in retrieving different types of data, must find and collect all the data needed to create the final report. Many steps of this process involve manual steps that are labor intensive. Once all the data has been collected and assessments have been made by members of the PZR staff, the data is aggregated and joined together to create the final report.
PZR has an existing system in place to help facilitate the workflow for creating reports and fulfilling orders. The main areas of the current process are:
1. Job creation – Adding the order to the system.
2. Job assignment – Assigning the order to a PZR resource to work on.
3. Process order and request documents – Collecting information and documents necessary to create the PZR report for the order.
4. Follow Up - Load deliverables on shared drive, update data in the PZR system, and deliver the report to the customer.
(Notes :These functionality needs to be re-create, you MUST watch the videos first to understand how the existing application works and then read the whole concept documents to find out how the new workflow should be created)
For this project, the client would like to re-write / re-architect their existing system to use modern, open source technologies. They would also like to enhance the existing system and add some new features to the new system. This project will include three major goals:
1. Re-design the existing PZR application / workflow using modern technology and to reduce manual or repetitive work.
2. Design a web-based platform for generating reports.
3. To design a system or process for extracting data from the existing system, which includes both moving the data (users, customers, etc) that is in the database as well as migrating / evaluating the data that is in the existing legacy reports.
In this contest, we want you to create a new workflow for this application that can achieve all those 3 major goals above, here are the workflow scenario that needs to be created :
Generic Workflow (should be applied to all user except customer) :
1. Login / Logout (4.2.1.1 - 4.2.1.2)
2. Register Account (4.2.1.3)
3. Recover Forgotten Password (4.2.1.4)
4. Print (4.2.1.5)
Order Processor Workflow :
5. View Job Request (4.2.2.1)
6. Manually Process Customer Order (4.2.2.2)
7. Manage Customer (4.2.2.3 - 4.2.2.6)
8. Process Order (4.2.2.7 - 4.2.2.9)
Project Coordinator Workflow :
9. Manage Jobs (4.2.3.1 - 4.2.3.5)
Information Specialist Workflow :
10. Manage Assigned Jobs (4.2.4.1 - 4.2.4.5)
Follow Up User Workflow :
11. Manage Documents (4.2.5.1 - 4.2.5.2)
Report Writer Workflow :
12. Manage Reports (4.2.6.1 - 4.2.6.4)
Administrator Workflow :
13. Manage Documents (4.2.8.1 - 4.2.8.4)
14. Configure Drop Down Values (4.2.8.5)
15. Fix Invoice Item (4.2.8.6)
16. Manage Teams (4.2.8.7)
17. Manage Venders (4.2.8.8 - 4.2.8.11)
18. Manage Users (4.2.8.12 - 4.2.8.15)
Billing User Workflow :
19. View Check Requests (4.2.7.1)
20. Bill Customer (4.2.7.2)
Customer Workflow :
21. Submit Order Request (4.2.9.1)
22. View My Orders (4.2.9.2)
23. Download Report (4.2.9.3)
24. Submit Credit Card Payment (4.2.9.4)
Supporting Documents
- Conceptualization Documents
- VM for the existing PZR application (by request in forum after you registered to the challenge)
- Compressed Video of the current PZR application (can be downloaded at http://sigalegale.com/pzr/)
- Sample Documents
- Client Questionnaire and summary of project.
Target Audience
- Customer
- Order Processing Specialist, which consist of the following audiences :
- Information Specialist
- Follow Up User
- Order Processor
- Project Coordinator
- Report Writer
- Billing Manager (Billing User)
- Client Manager
- Administrator
Notes : You must create all scenario for all those application user.
Judging criteria
Your submission will be judge using the following criteria:
- User experience
- Completeness and accuracy of the areas of functionality and content as described in challenge details
- How well your wireframes provide a consistent user flow and clear information architecture for the application
Submission & Source Files
Preview Image
Create your preview image as one (1) 1024x1024 JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
Generated HTML files with all the requested contest requirements stated above.
Source Files
Wireframes should be built in Axure. The resulting files should have generated HTML files. Also, all the content must be listed and the pages are linked together to show page flow.
Final Fixes
As part of the Final Fix phase, you may be asked to remove, update, or change some features of the wireframe.
Please read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. It is important that you monitor any updates provided by the client or Studio Admins in the forums. Please post any questions you might have for the client in the forums.