You can use the ProjectPlanner sample to explore and adapt a MDriven Turnkey project-planning application with resource assignment, field reporting, map-based activity positions, tool handling, reports, and interactive HTML5-based views.
Get the sample
Download the sample archive:
File:ProjectPlanner DatabaseCompact.zip
ProjectPlanner is an example application intended for learning and adaptation. It demonstrates how one model can support office planning and work performed in the field. For the broader example-app workflow, including requesting a demo site and applying an available sample, see Documentation:Example Gist.
What you can explore
The sample uses project activities, people, positions, tools, and status reporting to show several ways of working with the same planning data.
| Area | What the sample demonstrates | Example |
|---|---|---|
| Resource allocation | View people and assigned activity actions, then change an assignment through an interactive board-style view. | A planner moves an activity card from one person's list to another to reassign the work. |
| Geographic planning | Store and interact with the position of an activity action through a Google map. | A planner places an activity at the location where it must be performed. |
| Field work | Provide a phone-oriented view of activity actions assigned to a person. | Rita opens her assigned actions on her phone after the plan has changed and sees the updated assignment. |
| Check-in and progress | Let a field worker report their current position and update the status of a selected action. | Rita checks in her current position, then reports an action as 10%, 50%, 75%, or 100% complete. |
| Project reporting | Produce a project-detail report from a Word ODT template. | A project manager generates a report listing details for a project. |
| Tool handling | Model tools and tool types, show tool status, and use a QR code to reach the tool-assignment flow. | A field worker scans a tool's QR code and checks the tool out to themselves, making its holder visible to other users. |
| Excel integration | Expose application data to Excel and support Excel-driven searches, imports, or updates according to the UI you build. | A user retrieves planning data in Excel, or imports updated data back into the application. |
Try the planning workflow
Use this sequence to understand how the views relate to the underlying planning information:
- Open the project and identify an activity action that needs a person assigned.
- Use the person-oriented board view to move the activity action to the intended person's list. This changes the assignment through the application's interactive UI.
- Open the activity action's map-oriented view and inspect or set its geographic position.
- Sign in as a field worker who has assigned actions. Use the phone-oriented view to check the worker's current position.
- Select an assigned action and report its progress using one of the available percentage choices: 10%, 50%, 75%, or 100%.
- Return to the planning views and verify that assignment and status information now reflects the reported work.
- Open the tool overview, select a tool, and use its QR code as the entry point for checking the tool out to a person.
- Generate a project-detail report to inspect the information delivered through the ODT template.
These steps are a useful starting point for deciding which workflow solves your own business problem. The sample is deliberately reduced; extend the cloned model with the rules, fields, and views required by your users.
Adapt it for your own application
Start with a specific planning scenario rather than copying every feature. For example, a service business could retain activities, people, geographic positions, and field status reporting, then adapt the activity information to represent service visits.
- Create or obtain a MDriven Turnkey site using the setup process described in Documentation:Example Gist.
- Apply the ProjectPlanner sample to establish the starting model and data.
- Identify the planning concepts you need to keep. For example, keep Person, Activity Action, and position if workers perform location-based work.
- Adapt the model and its views to your terminology and process. For example, change an activity action from a generic task into a service visit, inspection, or delivery task.
- Test the planner workflow and the field-worker workflow separately. A planner needs an overview of allocation; a field worker needs their own assigned actions and a fast way to report status.
- Add only the reporting, tool handling, and Excel workflows that your users need.
The business logic in the example is declaratively defined in the UML model. Keep related rules in the model as you extend the sample so that the behavior remains understandable when the application grows.
HTML5 components and client assets
ProjectPlanner is useful when you want to study advanced interactive components in a Turnkey application. If your adaptation requires JavaScript or CSS files, package those files in a folder named <yourModelName>_AssetsTK. During cloud upload, Turnkey looks for that folder, uploads it to the TurnkeyServer, and expands it there.
For an example focused on the asset-folder convention and client-side JavaScript/CSS assumptions, see Documentation:Turnkey treeview. For another HTML5 component playground, see Documentation:Turnkey sample Board Map Balls Gantt.
Scope and implementation notes
- ProjectPlanner is a starting point, not a complete implementation of every real-world planning process.
- The sample demonstrates a Google map interaction for activity positions; confirm your own map, location, and privacy requirements before deploying a derived solution.
- The field-worker experience is designed with the phone as the primary device. Test your own field views on the devices your workers use.
- Assignment, check-in, progress reporting, reporting, and tool checkout are connected workflows. When you change the model, test each workflow end to end.
Walkthrough
Watch the ProjectPlanner walkthrough for a tour of resource allocation, map positions, field status reporting, reports, QR-code tool assignment, and Excel integration.