• V2Planning

V2 Planning Notes

V2Master

• Contents

  1. V2 Planning Notes
  2. Version Information
  3. First Release Goals
     1. Priorities Codes
  4. V2
  5. MAPS
  6. Reviewers and Prototype Systems
     1. Reviewers
     2. Prototype System Types
     3. Prototype Systems - Group 1
  7. Infrastructure
     1. Open Design Decisions
     2. Automated Procedures
  8. Marketing Activities
     1. Acquisition Strategy
     2. Promotional Material
     3. Web Site
     4. Other Issues
  9. Work Schedules
     1. JK Work Schedule

Version Information

• 2013-07-02 AH - Initial draft and updates based on TN feedback
• 2013-07-04 AH - Updates from discussion/review AH/DS
• 2013-07-04 AH - Updates from discussion/review AH/JK
• 2013-07-08 AH - Added JK work schedule
• 2013-09-18 AH - Updated JK work schedule
• 2013-09-28 AH - Updated JK work schedule, based on AHJK discussion on 26

• 2014-01-28 AH - Added Prototype Systems and Acquisition Strategy sections

First Release Goals

Complete V2 and the required supporting infrastructure to show to the public at Hydro-2013, which starts on 2013-10-07

• Best Case Scenario

  1. Online Sales with automated payment collection and system delivery

• Fall-Back Scenarios - Listed in decreasing order of desirability:

  1. Online Delivery of Free Trial Systems with automated system delivery

  2. Online Demo System with hydroelectric project specific configuration

  3. Public Prototype that demonstrates most application features

Priorities Codes

• P1 - Critical - Cannot launch without it. Implement now

• P2 - Important - Implement immediately after critical items complete

• P3 - Nice to have - Implement at the end

• P4 - Can wait - Implement if we have time

V2

1. User management (P1)

   1. New update/user
   2. Invite user to V2

   3. Invite user to MAPS (P4)

   4. Ability to purchase V2 without having to register in MAPS -- Design required

      1. Auto-registration?

      2. Devise grace period

2. User role management (P4) -- Design required

   1. Design concept and user screens (P1)

   2. Implementation (to be defined)

3. Authorization and authentication (P1) -- To review

   1. Folder management
   2. Protection of data based on folders and user roles

      1. Tasks & Task Notes

      2. Documents & Revisions (must be stored in same folder)

4. Documents and Revisions (P1) -- To review (AH/JK)

   1. Detail display
   2. Update document
   3. Update revision
   4. Revision file management

      1. File upload progress bar (P2)

      2. New/update revision detail

5. Tasks (P1) -- To review (AH/JK)

   1. Detail display
   2. New/update
   3. Task note new/update

6. Classification (P1)

   1. High-level description of concept and use cases in Wiki
   2. User screen (re-)design:
      1. Display/update classification
      2. Classification administration
   3. Apply to:
      1. Documents

      2. Revisions (P3)

      3. Tasks

      4. Users (P4)

   4. New/update classification applied to an object
   5. Classification search block
   6. Administration
      1. Classification trees definition/update
      2. Management of which classifications can be applied to which objects

   7. Classification report (P3)

      1. Outline display of all classification structures

7. Searching and Lists (P1)

   1. Proof of concept
      1. Investigate to see if there is a suitable gem
      2. Search by basic fields

      3. Search by dependent record fields fields (P2)

      4. Display basic fields

      5. Display dependent record fields (e.g. classification and workflow fields) (P2)

      6. Ability to sort by fields in dependent records (P3)

   2. Screen mockups
      1. Search screen - Search by main fields, foreign record fields, classification fields
      2. Lists - Sort by main fields, foreign record fields, classification fields
   3. User lists
   4. Document lists
   5. Task lists

   6. File lists (P2)

   7. Transmittal lists (P3)

   8. Naming and saving searches (P4)

   9. Naming and saving report layouts (generic reporting) (P4)

8. Administration screens (P1)

   1. Task types
   2. Revision file types

   3. Company list -- Remove and make part of classifications

9. Customer feedback screen (P2)

   1. Build into navbar so that feedback can be collected from anywhere
   2. Use current_path/url global to capture context

   3. Send email v2-suggestions@softxs.ch and CC the user

10. Dossiers (formerly named baskets)

    1. User dossiers (P2)

    2. Named dossiers (P4)

11. Transmittals (P2)

    1. Design concept and user screens
       1. Email delivery
       2. Creation of PDF (not in the first release)
       3. Download of ZIP file
       4. Are baskets required?
    2. Implementation
       1. Front-end

       2. Back-end - Event Daemon

12. Document and Task links (P2)

    1. Design concept and user screens

13. Notifications (P3)

    1. Design concept and user screens
    2. Notification role management
       1. Based on folders

       2. Based on individual objects (tasks & documents)

    3. Generation of notification events
    4. Screen notifications - Dashboard

    5. Email notification (P4)

14. Workflow (P4)

    1. Design concept and user screens

    2. Fall-back - Classification workflows (P3)

       1. Simulate workflows with a classifications
    3. Design user screens
       1. Display/update workflow
       2. Workflow administration
    4. Apply to:
       1. Revisions
       2. Tasks
    5. Display in detail screens
    6. Update workflows
    7. Administration screens for defining workflows
    8. Search by workflow values (search block)
       1. Workflow type
       2. Person responsible
       3. Status
    9. Export data

15. Export (P3/P4?)

    1. Automated export of all documents and metadata
    2. Needed to reassure customer that they can always retrieve all their project data (possibly also for satisfying auditors and internal backup regulations)

MAPS

1. Login/logout (P1)

2. Register (P1)

   1. Email verification

3. Invitations - Part of V2 functionality? (P1)

4. V2 purchase (P2)

   1. Payment processing
      1. Single payment

      2. Recurring payment (P3)

   2. System delivery - instantiation of V2 system
   3. Event Daemon

5. Product catalog and prices (P3) -- create product catalog DB records by hand

   1. Browse list
   2. Display detail

   3. New/update catalog entries (P4)

   4. Coupons (P4)

Reviewers and Prototype Systems

We will setup prototype systems:

1. For developing configurations for specific uses of V2 (hydro project, metro project, proposals, etc.)
2. To animate friends and colleagues to use and promote V2
3. To solicit feedback for improving existing and proposed features

Reviewers

1. Group 1

   1. AH

   2. JK

   3. TN

   4. RB - Robert Bartlett - Roadways specialist

   5. HS - Harald Schmitt - Civil engineer

   6. MM - Mary McGrath - Rail expert

2. Group 2

   1. AJ - Aegir Johansson - Civil engineer & project manager

   2. GS - Geraud Soubrier - Hydraulics expect & project manager

   3. MS - Martin Smith - Contracts manager

   4. MW - Marcel Winter - Project manager?

3. Group 3

   1. AS - Anthony Sullivan - Contracts manager?

   2. AE - Alan Edwards - Mechanical engineer

   3. FB - Federik Bok - Maintenance and replacements parts supplier and service provider

   4. WB - Werner Bruderer - Project management services provider

Prototype System Types

1. Proposal preparation
2. Hydropower project management
3. Metro project management
4. Engineering collaboration and design management
5. Engineering reference library
6. Ebook library
7. Software and sprint tracking system
8. Customer relationship management (CRM) and customer support
9. Personal productivity and todo manager
10. Photo management

Prototype Systems - Group 1

1. AH

   1. SoftXS tracking system

   2. EBook library

2. JK

   1. Hydropower project management
   2. Engineering reference library

3. TN

   1. University lecture video library

4. RB

   1. Proposal preparation

   2. Road Notes library

5. HS

   1. Engineering collaboration and design management

6. MM

   1. Metro project management

Infrastructure

V2 instances will be Amazon EC2 based. MAPS will also be hosted on an EC2 instance:

1. To make communication between MAPS and V2 instances more efficient
2. To reduce sys admin effort be re-using the knowledge and techniques used hosting the V2 instances

Open Design Decisions

1. Define strategy for allocating multiple V2 instances on a single VM (P1)

   1. Based on points. Each VM can host a number of points, each product uses a number of points

   2. Tune the VM and product points based on experience
   3. Add DB tables/fields in MAPS for managing VMs, deployed products and their points

2. How to register VMs and application instances in MAPS? (P1) -- Design required

   1. Issues:
      1. Does MAPS need to know this?
      2. Where else to store it?
      3. In an operational database
   2. Uses
      1. For storing access keys
      2. For identification and tracking

3. Define VM provision strategy (P1)

   1. Use copy of pre-defined image, which is created by hand, called the gold image

   2. Define the requirements for the gold image

Automated Procedures

1. VM creation and provisioning (P1) -- Design required (Need to learn AWS & EC2)

   1. Registration in MAPS - Is this needed?
   2. Instantiation
      1. Access key management
   3. Provisioning

2. Application installation (P1)

   1. Registration in MAPS
   2. Provisioning the initial user
   3. Rails application installation
   4. Application configuration
   5. Notification to customer
      1. New app's event daemon could send email informing customer that app is ready

      2. MAPS could use the App is up monitoring facility mentioned below (P4)

3. Backups (P2)

   1. Daily backups of MAPS
   2. Daily backups of customer systems

4. Monitoring (P3)

   1. App is up facility

   2. Monitoring data collection
   3. Centralized repository and presentation

Marketing Activities

Acquisition Strategy

Listed roughly in priority order:

1. Reviewers Group 1

2. Reviewers Groups 2 & 3

3. Existing DrawMGT customers
   1. Poyry
   2. Poyry Thailand
   3. Iceland
4. High Value contacts from ITA and Hydro conferences
   1. Via ITA WG3
5. South American spanish speaking countries (at ITA-2013 in May)
6. Small engineering consultancies (at Hydro 2014 in October)

Promotional Material

1. Hydroelectric project configuration for demo and trial systems (P2)

2. Works Organiser Quick Start Guide (P2)

3. Flyers (P3)

   1. Spanish language 1-2 page flyer for ITA-2014 conference (P2)

4. PM Handbook:

   1. Rudimentary - only most important chapters and appendices complete (P2)

   2. Complete handbook (P3)

5. Screencast (P4)

Web Site

1. Buy it page with payment processing (P1)

2. Terms & conditions page (P2)

3. Product pages, including features list and specification (P2)

4. News (P3)

Critical pages:

1. Works Organiser pages (P2)

   1. Features
   2. Specification
   3. Demo
   4. Pricing (try alternate pricing with narrower boxes and images on the right)
   5. Pricing Details

Place-holder material for the following pages:

1. Services (P3)

   1. Document handling - Take from existing web site
   2. Data handling - Write based on material from existing web site
   3. Customization
   4. Training

2. About Pages (P3)

   1. Do we need an overall 'About SoftXS' page?
   2. News
   3. Testimonials
   4. References
   5. Conference papers

   6. Contact Us - Including a send us feedback page (P1)

3. DrawMGT pages (P3)

   1. Features - Take from existing web site
   2. Demo

4. Web-site search (P4)

Other Issues

1. Security review (P1) - Can probably outsource this

2. Internationalization (P4)

   1. English
   2. Spanish
   3. German

3. Documentation (P3)

4. Help pages (P3)

Work Schedules

JK Work Schedule

1. Pre-Conference

   1. 2013-09-30 - Review of V2 checking recent Usability Review P1 updates

      1. Check for show-stoppers and items that must be fixed before the conference

   2. 2013-10-03 - Text for Works Organiser Demo and Hydro Demo pages:

      1. Need suitable descriptive text, including
         1. Explanation of the demo
         2. Suitable project roles (user logins) that can be used to show the system
      2. Pages to review

         1. http://v2.softxs.ch/maps/works/demo

         2. http://v2.softxs.ch/maps/works/demo/hydro

   3. 2013-10-05 - Demo classification and Sample Data complete

      1. Classification data
         1. Hydroelectric project
         2. Reduced configuration for bidding teams
         3. Reduced configuration for engineering team collaboration
      2. Hydroelectric Project Demo Sample Data
         1. Define the personnel and project roles comprising the project team
         2. Sample document and drawing lists
         3. Sample tasks
         4. Sample work packets

      3. AH & TN to implement a folder structure & classification data extractor that gets data directly from the database

   4. 2013-10-06 - Re-worked Features page

2. Post-Conference

   1. PM handbook outline. How to construction manage projects using V2
      1. List of Chapter and Sections
      2. List of Appendices:
         1. List of processes and workflow types required
         2. Configuration checklists
         3. Lists of recommended configurations
   2. V2 Quick Start Guide
   3. Specifications page

      1. Should be the bridge document between business terminology V2 application specific terminology

   4. PM handbook chapters
   5. Design for incoming email and chat processing
      1. List business requirements

      2. Correspondence & email follow-up

      3. Contact DS & DM and ask how chat is used at UBS

      4. Investigate how incoming email and online chat is integrated with other applications