Web Site to create and manage work orders

Work Orders are maintenance tasks that workers must complete. For example a work order can be to repair a broken window or to replace a light bulb. This project involves you creating a C# .Net web site and various C# .Net Web services for job management on an iPhone and Android device. This project does not include work on the iPhone or Android Device - only the web site and web services that communicate to the device. A complete SOW, ICD and screen renderings are attached. See additional details below. ## Deliverables This information is also included in the attached file. The term IUSA refers to my company. I am creating this for a client. The attached files also contain an ICD. This project involves you creating a C# .Net web site and various C# .Net Web services for job management on an iPhone. Web Site Functionality **1.1. ** Narrative describing the web site functions 1.1.1. Customer will have a web based system in which all the information captured by the devices will be viewable and managed. View records submitted by phone users. Edit those records. Add notes. Approve/Decline work that has been submitted by contractor. Rejected jobs then need to somehow be viewable for Contractor as incomplete and needs more work done on the phone. 1.1.2. The contents of this system can be backed up and kept outside of the system for 7 years. The backup technology is not part of this proposal. IUSA Corp can show the customer how to make and store the back ups 1.1.3. New contractors will be added from the web site. Only contractors added by the customer to the web site can use the app. If the customer removes a contractor from the web site, the contractor will no longer be able to use the app. Simple enable/disable of contractor user credentials. Accessible only to Customer Admin and Customer Super Admin. 1.1.4. Customer staff can review and approve jobs that were either created from scratch or that were created using a previous document. This is approval of jobs that were created from previous jobs on the phone. If a job is not approved it cannot be assigned to a contractor. 1.1.5. Customer can change check lists, and type lists from the web site. When the customer makes a change on the web site, the change is automatically reflected on the app. This is limited to Customer Super Admin user rank. 1.1.5.1. Type list is the type of jobs (see 1.2.9.1-1.2.9.6). Controls the checklist items that will appear on report for each job on the phone. 1.1.6. Checklists are the questions and answers that show up on the phone in the report section of the phone. **1.2. ** Users 1.2.1. The following types of users will be supported: 1.2.1.1. Customer Super Admin - can do everything on the site. 1.2.1.1.1. Create/edit/delete users of all ranks. 1.2.1.1.2. Create/edit/disable forms and questions. 1.2.1.1.3. Create/edit/assign jobs. [login to view URL] new jobs. 1.2.1.1.3.2. Accept/Reject pending jobs. 1.2.1.2. Customer Admin - can only manage jobs in the system (no setting up questions/answers) and can add/edit users for Contractor and Contractor Supervisor role. Manage Contractor Supervisors. Assign records to a Contractor. 1.2.1.2.1. Create/edit/disable users of Customer Admin, Contractor Supervisor and Contractor role. [login to view URL] jobs. 1.2.1.2.2.1. Approve/Deny new jobs. 1.2.1.2.2.2. Accept/Reject pending jobs. 1.2.1.3. Contractor - this is the guy going out and doing the work on the phone. Can only see his own jobs. Are associated with a contractor supervisor. Cannot log into the website. 1.2.1.4. Contractor Supervisor -Assigned to one or many Contractors. Can access all records assigned to their contractors when logging in on the phone. Cannot log into the website. **1.3. ** Entities 1.3.1. The system will contain the following entities 1.3.1.1. Maintenance Work Orders - These are the Jobs. 1.3.1.2. Property - This is the address that the job is to be performed on. 1.3.1.3. Pictures 1.3.1.3.1. Images required for the job and captured on the phone. [login to view URL] for a job (submitted by mobile/tablet or uploaded from web site) will contain picture type and picture tag. Latest job picture tag for a picture type will be the default for new images. [login to view URL] will be allowed to change picture types. **1.3.1.3.4. ** **Convert images with tag button.** 1.3.1.4. Customer - Clients 1.3.1.5. Contractor - People hired to perform the jobs for Client. 1.3.1.6. Job Types List with associate Picture Types 1.3.1.7. Legacy system **1.3.1.7.1.****Access will be by HTTP (POST and GET)** **1.3.1.7.2. ** ** Access will be via login** **1.3.1.7.3. ** **Must be able to navigate the web site** **1.3.1.7.4. ** ** Screen scraping into web field/value pairs** **1.4. ** Checklist Forms 1.4.1. The system will contain the following Objects: 1.4.1.1. Templates - Read only generic Forms that the user can use a starting point 1.4.1.2. Questions - A unique question - this is pre-populated. 1.4.1.3. Answers - A unique answer (i.e. True, False, Yes, No) this is pre-populated. 1.4.1.4. Custom Job Type Form - A uniquely defined form by job type that the customer has developed by Form Designer. Contains list of versioned questions with specific versioned answers for this form. 1.4.1.5. Versioned Custom Job Type Form - These are the static forms that are approved by the customer for a job type. 1.4.1.6. Real Estate Definition - The user can define the page size and margins of each device type. There will be one definition for mobile, tablet and web site. 1.4.1.7. Job Form Version - For a job, a version is locked down once the first form answer has been saved. (whether on the web site or mobile) Up to that moment, the latest Custom Job Type Form is to be used. [login to view URL] will have Job Type which will have Picture Types 1.4.1.9. Validated Job Form Answers - This contains the job type, form version, and validated answers for a job. 1.4.1.9.1. Form Actions/Events - An example of an item included in the completion routine is a question asking if "any leaks were noticed at the location." An affirmative answer to this question will result in subsequent question: "Have you taken pictures of the roof?." Another example is "Did you meet with any 3rd parties on site?" An affirmative answer to this question will result in a subsequent question: "Did you take a picture of an estimate or receipt." **1.5. ** IUSA Support Screen (Beta) 1.5.1. The system will contain pages for IUSA support only accounts. [login to view URL] jobs and mark as "Require Update". This needs to on the job list download for the mobile to know this is a rewrite of the job and ignore the edit flag. } * * *This broadcast message was sent to all bidders on Thursday Aug 9, 2012 5:20:39 PM: Based on questions we have received, we are posting additional clarifications here: 1). The mobile app is already written. 2). "convert images with tag button" in 1.3.1.3.4... means: you have a picture and a text. Open image, resize image to extend the bottom, Place text on new space at bottom and save new image with tag. 3). 1.3.1.7. Legacy system means: We have a web applications that we need to login, lookup/search for available jobs by filter, and screen scrape the data off each job in the search list to a database * * *This broadcast message was sent to all bidders on Thursday Aug 9, 2012 5:33:35 PM: in your responses, please provide examples of sites that you have already built that are similar to the one described in this project. * * *This broadcast message was sent to all bidders on Friday Aug 10, 2012 2:13:25 AM: We have received additional questions. Here is additional clarification: 1.3.1.3.4. Convert images with tag text. Open image, resize image to extend the bottom, Place text on new space at bottom and save new image with tag. 1.3.1.7. Legacy system that isa a web applications that we need to login, lookup/search for available jobs by filter, and screen scrape the data off each job in the search list to a database. [login to view URL] will be by HTTP (POST and GET) 1.3.1.7.2. Access will be via login 1.3.1.7.3. Must be able to navigate the web site 1.3.1.7.4. Screen scraping into web field/value pairs Our Support - support staff for the app and website. Forms are PDF Form field data entry. Forms that have answers come from phone, tablet and website. Forms have questions and answers (radiobutton, checkbox, textbox). each answers field id is unique and contains ids that point back to the database definitions. Form designer allows you to create endless checklists with versions from a static list of questions and answers. Form validation is from the Form designer (web site) and are either validate at the web service level or embedded in the form at the event/action level. * * *This broadcast message was sent to all bidders on Monday Aug 13, 2012 12:57:29 PM: Additional clarification: Question from Worker: I am not sure about the layout - do you have graphical image only, or CSS/HTML styles? if no CSS/HTML styles, do you actually expect the contractor to develop these styles based on graphical layout? Answer: CSS/HTML styles - just one for the site based on the graphical work done. Question from Worker: Also, from what you explained above, I assume that AJAX functionality can be kept to minimum (no ajax means better scraping btw), is that correct? Answer: Yes - to a min.