Please enable JavaScript.
Coggle requires JavaScript to display documents.
Jan-Pro (Languages (coffeescript, javascript, json, mongo, jade/pug/html,…
Jan-Pro
-
-
features
Incident logging and tracking, incident escalations (Initial Phase)
-
-
-
tech
db
-
Service: IBM Compose
Durability
Every MongodDB deployment on Compose is built as a highly-available clustered-configuration. Each deployment's shard has multiple data nodes for redundancy. Combining Mongos/HAProxy at the front end, the configuration is able to transparently switch to the current primary, and multiple Mongos/HAProxies nodes add another layer of failover capability.
Backups
Automated backups are made every day and retained for 7 days along with 4 weekly backups and 3 monthly backups. The on-demand option of Compose backups allows up to 10 backups to be made a week. Backups are included at no extra cost and can also be created and retrieved using the Compose API.
Autoscaling
As disk usage grows, the Compose platform will automatically allocate extra resources to maintain a proportional ratio between storage and memory so your database is always performant. Users can also manually control scaling via the Compose console for specialized workloads or events.
-
Features
-
Custom CRUD
Custom create, read, update, delete interface that can evolve with user needs
Proposal Questions
Is this browser based or do we have options for an app, do we even need an app?
It is designed for the browser but mobile friendly. It can also be packaged into an app for IOS and Android and use the same codebase.
At this point I’d advise packaging the app for the mobile stores (simply due to the user base and demographic) and don’t see a need for native hardware. Estimate 5 hours for mobile packaging.
When packaged the app can also access native phone functions like GPS which sometimes is superior to web based protocols.
What database technology will be used, how will deployment be handled
MongoDB, at least for development. It’s linked to Meteor. When the app is stable/ready for deployment I could transfer to any DB. No tech benefit, MongoDB is fine, just don’t know about they’re needs.
Phases
Initial
Cleaning crew bio’s
Details of exactly who the members of the cleaning crew are, a bit about their history along with photos of the team.
Maybe we can include details of other accounts that they service along with any special expertise that the team has, to give a more rounded picture of their capabilities.
-
User registration, manually or via the associated office, lost password etc (Initial Phase)
Customers much be linked to a regional office to ensure that the incident tracking and escalation
process works correctly
The user registration process must ensure that a customer is linked to the correct local office that services the account. We must ensure accurate linkage so that incidents are correctly logged and escalated via the relevant office.
Subsequent
Overview of products and extra services available, maybe in the form of a menu of services with associated
costs or the ability to build up a composite cost based on input parameters
Admin consoles must allow for user creation and maintenance, incident tracking and escalation
definition along with notification paths and workflow definition
Where any part of the system relies on configured values and workflows, there will need to
-
-
-
-
office, they will not be able to see or update data from any other office.
Detailed system usage reports must be available in terms of users registering and logging in,
incidents raised based on their statuses and where they are within the resolution process
-
level. The local Jan-Pro offices must be able to report on their own data, while the PFB
-
Examples of reports would be incidents along with resolution history, cleaning histories by
customer and type of clean, online payments processed, registered system users, login
history, contact data updates etc.
-