Challenge Summary
Welcome to "iPad App Physical Access Control System" Wireframe Update Contest. This application will provide a user interface to our Physical Access Control System (ACS). We already concluded with the first wireframe contest and for this contest we need to update the provided wireframe.
At the end of this contest, the Client is looking to have a clean, intuitive, and easy-to-use set of wireframes that will be great input into a storyboard design contest.
NOTE: This contest will be run as a private competition. This means all documentation and forum discussion will be private and only available to members who have signed a CCA.
Primary Goal & Design Considerations
The primary goal of this application is to translate an existing web application into an iPad application. The current web application is implemented using Adobe Flex technology that is not viewable in an iPad. Also the page layout of the current application is designed in a screen size that is not optimal for an iPad application. This wireframe contest will illustrate how a subset of the applications pages will flow within an iPad environment.
For this contest, you will update the provided wireframe for Physical Access Control System (ACS) with the features and pages outlined below. The target platform of this application will be the Apple iPad.
Requirements
You need to update the following features/pages keeping in mind the iOS standard. We are looking for a native iOS GUI, the app should use as the native/iOS User Gestures. It is critical that your design takes advantage of user gestures - multi-touch, swipe, pinch, grab, tapping, etc. Please clearly document how you intend users to physically interact with your interface. For guidelines on iOS standard, please refer to this page (http://developer.apple.com/library/ios/#documentation/userexperience/conceptual/mobilehig/UIElementGuidelines/UIElementGuidelines.html)
1) Login and loading screen
2) Monitoring
2.1) Schedule View tab
2.2) Input/Output Screen
2.3) Anti-Passback reset
2.4) Diagnostics screen
3) Access Management
3.1) Areas - Area Definition screens
3.2) Reader Groups screen
4) Reports menu option
4.1) Access history report
4.2) Credential report
4.3) Reader access report
4.4) Roll call report
4.5) Roster report
5) System Admin
5.1) System Settings
5.1.1) System Information tab
5.1.2) Date and Time tab
5.1.3) Network configuration tab
5.1.4) Security tab
5.1.5) User-defined fields tab
5.2) Operator Roles
5.3) Backup / Restore Database
5.4) Save / Reset System Settings
5.5) Card Formats
Target Audience
Security Resource
This resource is responsible for using the access control system on a day to day basis to: set up other people with the appropriate access controls. Lock/Unlock doors as needed using the iPad interface. Monitor the property being managed by this access management system
Installation Resource
This resource will use this application to help setup the access control system at the client location.
Judging Criteria
Your submission will be judged on the following criteria:
- Completeness and accuracy of the wireframe as defined in the attached requirements.
- How well your wireframes provide a consistent user flow
- How well you implement the required data and any suggestions, interactions and user flow you recommend (provide any notes or comments for the client)
- iPad standard implementation
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
All 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.
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.