AGTEK R & D Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
===== Release Contents =====
All stories (0-3) comprise this first release. It includes the internet keys (permanent, timed, and rental) for Windows desktops and android phone support. This is in fact the bulk of the product. Pieces that may be left out for this release are some reporting (some are critical like Rental reports). It does not require one time keys (ala' authorizations) or software keys (once a year authorization) for this release. We will be running in parallel with the Solo Server at this time and do not expect to physically turn the Solo Server off as we attempt to transition users. There will probably be some effort necessary to port existing users to the new system.


=== Requirements ===
  * Rental Report for billing
  * Permanent keys
  * Timed keys
  * Rental Keys
  * Simple mechanism to create and extend keys. This can be crude a first since the users are AGTEK employees.
  * Prevent key copying and clock skew. 

=== Roll out Strategy ===

A rough count shows roughly 100 Earthwork 4D/Trackwork customers. I believe we will be rolling this out in parallel with the existing Solo server and in fact the Solo server will have to continue to exist for some time after due the software only keys that exist in the field.

Rough order

  - First release version of Earthwork 3D/GradeModel/Trackwork with support for new server to AGTEK Corporate and Sales.
  - Release same versions to new customer orders with keys entered in only the new server.
  - General release to existing Internet key (Solo) users. The danger here is that these users need new software but we cannot have the keys both places for very long because then they effectively could have two keys per number if the they run a mix of software. It will have to be a campaign with notifications to the customer and then eventually turn off their keys on the Solo software.
        * We will have to attempt to port user information to the new system.
  - When software keys are enabled on the server we need to roll Graphic Grade MC. The process of changing those systems over may be so difficult that we run the solo server for several years. More thought on the numbers of systems involved and the rollover method is needed.



===== Story 0 =====

  * Define other stories and do time estimates.
  * Breakdown into pieces,
  * Familiarization with AGTEK Access
  * Define client API (work with Dave)
  * Mockup key managment tool
  * Define abstract key model (what parameters and what do they mean)
  * Define database tables

===== Story 1 =====

Core Implementation - SmartDirt Release

  * Manual (developer key creation)
  * Full key model
  * Key infrastructure complete
  * Reporting is developer driven
  
===== Story 2 =====

Windows C API Release

  * Integratable in Windows app
  * Key Creation tool
  
===== Story 3 ======

  * Deployment Plan to server.
  * Roll smartdirt and windows products to access.agtek.com

===== Story 4 Site License Capability ======

A site license is designed to propagate mobile apps further into companies by removing the barriers to anybody who needs the products in that company. The customer buys a site license rather than individual apps and in return has that products for his site (office) with the only limits being total users per company. There are likely two parts to this, an update to mobile products and a server update with provisioning software changes.

==== Implementation Thoughts ====
None of this set in stone because decisions on how to best implement on the server are to be determined. The provisioning method also factors in.

=== Provisioning Ideas ===

First thought is to have a flag on the company similar to AGTEK Access & Tracking that enables a SmartPlan, SmartTrack, or SmartDirt license ( I don't see us doing RTK under Site license at this point). The mobile apps would likely need to be updated to understand this change and bypass the key selection page entirely when the flag is encountered. One small downside to this approach is future site license types would have to be added as they occur however I don't anticipate many others. 

Second though is to create a site license product code that when placed on a key essentially creates a site license for those key codes. The benefit would be that essentially any software that had been enabled to support site licenses could be used. The downside would be inadvertent provisioning with the key code (don't know if it's ever happened) has far more cost. 


=== App Behavior ===

I'm imagining that any app that sees a matching site license indication bypasses the key selection screen entirely and goes directly to files or tracks.
 















===== Future Story =====

  * Geolocation and geolocation pattern reporting.
  * Hash check .exe security
AGTEK R & D Wiki

User Tools

Site Tools

Page Tools
