Challenge Summary
The Global Service Activity System (SAS) is a web based application used to track project related service activities. Users can create and edit service activity data, perform on-line inquiry, filtering/sorting of that data, and generate either a service activity summary or detailed reports.
For this contest, we need you to create Wireframes for the new SAS web application.
We look forward to seeing your creative designs!
Round 1
Round 1 will focus on the following user functionality for the SAS web application:
1) Dashboard
2) Service Activity
3) Reporting
a) Only the Reports Wizard screen is required for Round 1 (the rest of Reporting will be included in Round 2).
NOTE: See the requirements in "AR-ServiceActivitySystem-131213-2019-36.pdf" to understand the screens / functionality for these areas. The screen shots located in the Current system section of the file AR-ServiceActivitySystem-131213-2019-36.pdf show how the functionality is implemented today and should work in the new web application.
Round 2
In Round 2, you will need to include all Round 1 screens (updated based on milestone feedback). For Round 2, you must also include all the remaining functionality descibed in the prior wireframes and project documentation, including:
4) Reporting
a) All Reporting functionality, including Reports Wizard from Round 1.
5) Admin
Primary Goals
The goal of this project is to design and develop a new Global Service Activity System (SAS) web based application. This project is a re-write of an existing FLASH based system to a JAVA based system with an improved architecture.
For this contest, we are asking you to put together wireframes for the new SAS web application. The requirements for the SAS web application are detailed in the attached documentation.
The screen shots located in the Current system section of the file "AR-ServiceActivitySystem-131213-2019-36.pdf" show how the functionality is implemented today in the current system. The attached wireframes and storyboard for the service request tool have been provided to show an example of the "ATLAS" look and feel and the general flow we want this project to have.
General Requirements:
- Produce HTML click through wireframes that can be used to demonstrate all mentioned functionalities as required in each round.
- The web application must be very easy to use and intuitive. Keep that in mind when designing your solution.
- You MUST cover all use cases mentioned and described in the project document.
- Your wireframe must represents all pages and flows from project documentation. You should use that as a guide, but if there is better way to display any information, feel free to reflect that on your wireframe.
- You MUST use wireframes note pane in every single page you design, to explain what all items are addressed in that page, what things you added/changed/removed, use it to make your idea clearer and help the client to give you constructive feedback.
Project Description
The Global Service Activity System (SAS) is a hosted web based application used to track project related service activities. Users can create and edit service activity data, perform on-line inquiry, filtering/sorting of that data, and generate either a service activity summary or detailed reports. The reports can either be on demand or the user can setup a schedule for the report and it is then emailed based on that schedule. The user can setup and maintain N number of reporting schedules. The tool provides a dashboard area that the user can add canned graphs that show services activities by date for a specific division. The user can add a graph for each division present in the data set and then reorder them. There is also an administrative function to create and maintain the Areas that are used in the tool.
This project will design and develop a new Service Activity System (SAS) web based application by re-writing the existing FLASH based system to a JAVA based system with an improved architecture.
Project Documentation:
The file "SASProjectDocs.rar" (attached) contains the documentation for the SAS project. The following docs are in the attached RAR file:
1. AR-ServiceActivitySystem-131213-2019-36.pdf - Summary level document that includes screen shots from the current system. This is a very important document to review for this contest!
2. AR-ServiceActivityMainApplicationFrameSpec-131213-2020-38.pdf - This shows the spec for the main application frame
3. AR-SASMenuBarSpecification-131213-2020-40.pdf - This shows the spec for the SAS menu bar
4. AR-CommonTasksspecification-131213-2021-42,pdf - The common tasks spec
5. AR-SASTables,Pagination,Filtering,andGrouping-131213-2021-44.pdf - This spec for how we want table filtering, pagination, etc.
6. AR-ManageServiceActivitiesFunctionalSpecification-131213-2022-48.pdf - This contains the draft of the spec for the Manage Service Activities view. Shows the view as well as the Create and Edit Service activities dialogs
7. AR-ServiceActivityDashboardFunctionalSpecification-131213-2022-46.pdf - This is the spec for the Service Activity dashboard with references to the add dashboard dialog.
8. AR-AddDashboardDialog-131213-2024-52.pdf
Wireframe Requirements:
Please see the file "AR-ServiceActivitySystem-131213-2019-36.pdf" for detailed requirements and current system screenshots! Below are some of the big requirements to help you understand the new SAS application being built:
- Dashboard: The dashboard provides the user with the ability to create a dashboard of division specific service activity data.
- Service Activities: This screen allows the user to View, Create, Edit, Delete, and Clone of Service Activities. Viewing can be done with grouping or without grouping (see current system screenshots for an example of this).
- Administrative Screen: Includes Area Master Maintenance (Add, Delete, or Update areas).
- Reporting: The reporting functions allows the user to create reports with filtering and sorting criteria, report format options, and a report scheduler and distribution mechanism.
NOTE: Please see the file "AR-ServiceActivitySystem-131213-2019-36.pdf" for detailed requirements and current system screenshots! This file includes current system screenshots starting on p.3, as well as detailed requirements under the "Future System Requirements" section that starts on p.9 of this file.
Look and Feel:
The new SAS web application should have the ATLAS look and feel (i.e. the look and feel that we came up with during earlier TC contests and are adopting as a baseline standard for apps that we develop). There will be a main frame with similar elements as ATLAS. For SAS these will consist of a menu bar area, common tasks, status bar, and did you know section. The menu bar will have help, preferences, exit, and service request menu items. The service request menu will have a drop down menu showing the current services request with options to manage existing in progress service requests and create a new service request.
IMPORTANT: The attached wireframes and storyboard for the service request tool have been provided to show an example of the "ATLAS" look and feel and the general flow we want this project to have. These are examples of projects that have been accepted that have this look and feel.
Files Provided (attached to contest spec):
1) "ServiceRequestTool WF Ver 5.rar" - Wireframes for the service request tool. Provided to show an example of the "ATLAS" look and feel and the general flow we want this project to have.
2) "SASProjectDocs.rar" - Contains project documentation, current system screenshots and requirements.
Target Audience
Existing users of the SAS web application.
Judging Criteria
- User Experience
- Simplicity and Consistency
- Completeness and accuracy of the wireframe.
- How well your wireframes provide a consistent user flow.
- How well you implement the idea
- Any suggestions, interactions and user flow you recommend (provide any notes or comments for the client)
What to Submit
Preview JPG/PNG Image File
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission ZIP File
All requested contest requirements as clickable HTML files generated by Axure. All the content must be listed and the pages are linked together to show page flow.
Source ZIP File
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.
All fully editable original source files of the submitted wireframe as required by the contest under "Source Files" in the side bar should be included in your Source zip file.
Final Fixes
As part of the final fixes phase you may be asked to complete one round of minor changes to ensure your submission meets the stated requirements of this contest. See more information about Final Fixes.
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.