Procedure Database and Document Generator

  • Status Closed
  • Budget N/A
  • Total Bids 17

Project Description

[url removed, login to view]

Procedure Database and Document Generator

Project Scope

This project will include the creation of a database, and graphical database editor for the creation and editing of process documents.

Detailed Project Specifications

[url removed, login to view]


The following features are what will be included in this iteration.

1. A graphical front-end that allows a user to create new steps and tasks and apply them to templates to build process documents.

2. A server-based database to keep stored data centralized.

3. A word document and pdf document generator.

4. User controlled system, with different credentials.


Python version 2.7 will be used to program the interface and backend. C# should also be considered.

Database will be MySQL since it’s very well supported and easy to work with.

A server will be required to host the database so that multiple machines can run the app and access the same data pool. This can either be a hosted server or a physical machine at the customer site. We can discuss this further as the project progresses.

Time Estimate and Costs


Since this project is large-scale and has extreme potential for initial requirements changing and evolving we recommend a time and materials approach with payment every other week based on actual hours. A timeline with a set of deliverables as described in the Timeline section of this document will be followed.

On average every 1-3 weeks there will be incremental milestones that will be evaluated in a meeting with the Edwards project managers. The timeline is expected evolve but the frequency of deliverables should remain constant.

Once delivered, all code and documentation is the property of Edwards Vacuum and shall not be sold or used elsewhere.


This should be completed over a 6 month period from the date of purchase. Please provide quote.

Additional Features

As with any project we should anticipate additional features and unforeseen technology hurdles. Due to the large number of unknowns we should plan for this.


In our experience, after any project is completed, on average about 20% of time can be attributed to maintenance. We should plan for this over the next 2 years.

Development Practices


Start by reviewing and revising the our feature list and determine what data we want stored in the database.


We will be employing Agile methods of development which means the project can evolve and even change requirements as it moves along.

Weekly Updates will be submitted to project contacts Eric Bond and Mike Bryan at Edwards Vacuum each Sunday evening stating what was completed the last week, what is planned for the current week and any open issues.

Testable releases of the application will also be released as often as possible, likely every 1 - 3 weeks there will be a new current working application that allows testing of all features up to that point.


The project will be considered completed once we are satisfied with the application.

We will need the following at the end of the project:

1. All source code and any executables for the tested and working application.

2. A database including tables for templates, tasks, and steps.

3. Instructions on how to use and install the application.


This needs to be defined by the contractor and should be included with the quote.

Get free quotes for a project like this

Looking to make some money?

  • Set your budget and the timeframe
  • Outline your proposal
  • Get paid for your work

Hire Freelancers who also bid on this project

    • Forbes
    • The New York Times
    • Time
    • Wall Street Journal
    • Times Online