Web based photo app with database
Budget: $750 – $1,500 USD
We are looking for a web-based application that will facilitate the organizing of photos.
The data should be stored in Sharepoint/Azure Cosmos DB to be used to provide status pages, as well as back-end processes. THe web-front end will be Azure hosted as well. All functions that are run on a schedule will also be Azure based.
Overall:
- Estimator will be taking pictures of containers, and the door will always have a code that will be used as part of a unique ID.
- First picture will be the door, which should be recognized on the screen, and confirm the ID
- The next photo(s) will be pictures of the container/damage.
- The last photo(s) of the "set" will be the written work order. Possibly multiple pages
UI/UX Mobile
- Authentication via M365 account
- Initial screen will have company Logo, and a "Start" button
- First picture used will read the container ID. Will be saved as the Album picture. User should confirm/edit the ID to ensure accuracy.
- Screen will then have a Title Bar indicating the Container ID so that the user has a visual reminder of the container. The screen will have 2 actions, Take Picture, or Scan Work Order.
- If they click "Scan Work Order", the will then start taking pictures of the work order. Each page after taking a picture should have 2 buttons - Add Page / Submit Work Order
- Submit Work Order Screen will present the user with 2 choices. "Approve Unit for Repair" or "Submit for Approval"
- Return to First Screen
Backend Processes:
- Images of Containers - JPG format, with a max resolution of 1024x1024. This should be a backend option, in case we need to increase to 1280x1280, etc. We definitely don't need 20MP pictures...
- Work Order - Should be combined and converted to single PDF.
- Original Data should be stored in Primary Sharepoint Library - We will provide parent URL
- Data will be duplicated to a different Sharepoint Library (Customer facing) - we will provide Parent URL
- Data will be organized in a folder (In primary and secondary storage) with YYYY-MM\AZAZ-1234567-YYYYMMDD. Each picture should be renamed similarly, with the time it was taken HHMMSS unitID-YYYYMMDD-HHMMSS.jpg. The Work order will be the "unitID-YYYYMMDD.pdf"
- Phone should be able to confirm that all data was transferred before removing from local temp storage. We should continue to keep all pictures on phone camera roll in case we need to recover. Phone's camera roll is currently backed up to individual OneDrive accounts.
- When a set is complete, an email will be sent to address(es) with link to secondary storage files. This will let office user click the link to open folder containing pictures/work order for easy reference.
Database - should be very small, as all data is minimal, and links to photos/pdf. Keeping track of device used to capture pictures.
Admin Functions on admin portal:
- Login with M365
- Restore Pictures - If pictures/pdf go missing, this will copy them again to the customer facing Library from the Primary
- Manual Process - if we find one didn't process, we can grab pictures from OneDrive, and type in unit number, Drag drop pictures into boxes for pictures, one box for work order. Let the system resize, combine work order pictures, and process as normal.
The data should be stored in Sharepoint/Azure Cosmos DB to be used to provide status pages, as well as back-end processes. THe web-front end will be Azure hosted as well. All functions that are run on a schedule will also be Azure based.
Overall:
- Estimator will be taking pictures of containers, and the door will always have a code that will be used as part of a unique ID.
- First picture will be the door, which should be recognized on the screen, and confirm the ID
- The next photo(s) will be pictures of the container/damage.
- The last photo(s) of the "set" will be the written work order. Possibly multiple pages
UI/UX Mobile
- Authentication via M365 account
- Initial screen will have company Logo, and a "Start" button
- First picture used will read the container ID. Will be saved as the Album picture. User should confirm/edit the ID to ensure accuracy.
- Screen will then have a Title Bar indicating the Container ID so that the user has a visual reminder of the container. The screen will have 2 actions, Take Picture, or Scan Work Order.
- If they click "Scan Work Order", the will then start taking pictures of the work order. Each page after taking a picture should have 2 buttons - Add Page / Submit Work Order
- Submit Work Order Screen will present the user with 2 choices. "Approve Unit for Repair" or "Submit for Approval"
- Return to First Screen
Backend Processes:
- Images of Containers - JPG format, with a max resolution of 1024x1024. This should be a backend option, in case we need to increase to 1280x1280, etc. We definitely don't need 20MP pictures...
- Work Order - Should be combined and converted to single PDF.
- Original Data should be stored in Primary Sharepoint Library - We will provide parent URL
- Data will be duplicated to a different Sharepoint Library (Customer facing) - we will provide Parent URL
- Data will be organized in a folder (In primary and secondary storage) with YYYY-MM\AZAZ-1234567-YYYYMMDD. Each picture should be renamed similarly, with the time it was taken HHMMSS unitID-YYYYMMDD-HHMMSS.jpg. The Work order will be the "unitID-YYYYMMDD.pdf"
- Phone should be able to confirm that all data was transferred before removing from local temp storage. We should continue to keep all pictures on phone camera roll in case we need to recover. Phone's camera roll is currently backed up to individual OneDrive accounts.
- When a set is complete, an email will be sent to address(es) with link to secondary storage files. This will let office user click the link to open folder containing pictures/work order for easy reference.
Database - should be very small, as all data is minimal, and links to photos/pdf. Keeping track of device used to capture pictures.
Admin Functions on admin portal:
- Login with M365
- Restore Pictures - If pictures/pdf go missing, this will copy them again to the customer facing Library from the Primary
- Manual Process - if we find one didn't process, we can grab pictures from OneDrive, and type in unit number, Drag drop pictures into boxes for pictures, one box for work order. Let the system resize, combine work order pictures, and process as normal.