Sales Engineering

From UG

Revision as of 18:14, 1 December 2011 by Denise (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)
Jump to: navigation, search


Contents

Info

0002875: [Sales Engineering] ..... <proj>

This article's about supporting our global sales team with a CT2 demo environment, which is for them to use to demonstrate to new prospective clients and existing clients, the current functionalities that JFS offers.

Requirements

  • Need to keep running list of Jaguar sales, management and IT users
    • Simon Kaye (simon@jaguarfreight.com)
    • Marc Selter (marc@jaguarfreight.com)
    • Robert Link (robert@jaguarfreight.com)
    • George Saives (george@jaguarfreight.com)
    • Joe Chiapetta (joe@jaguarfreight.com)
    • Jeanine Favia (jeanine@jaguarfreight.com)
    • Denise Guastella (denise@jaguarfreight.com)
    • Montira Renfrew (montira@jaguarfreight.com)
    • Tracie Eisenberg (tracie@jaguarfreight.com)
  • Need to have same features (current & new) that's on production client app

History

0002882: [Sales Engineering] Finalize/Test new demo envir t with Vlad (see 0002867) and train/coord Harry on how/when to set up demos

0002867: Establish Sales Demo CT2 environment and procedures (and migrate to Rackspace)

  • See mantis here: 2867

Additional procedures needs to be established:

  • how/when to update CT2 version on this environment
  • what users to keep there
  • do we need automated scripts/features to:
    • "scrumble" real client info
    • create demo environment for particular prospect

IMPORTANT NOTE: scheduled reports and other features "affecting live clients/users" must be disabled after migration. http://ct.jaguarfreight.com/wiki/Data_Migration_From_Production_Envir_to_X_Envir_%28procedure%29 [^]

Related wiki : http://ct.jaguarfreight.com/wiki/Jaguar_Servers_Systems_Applications#Sugar_CRM_and_EA_Demo_server [^]

0003200: [IT/Misc][Sales Engineering] Resolve speed issues with Sales demo

  • See mantis here: 3200
  • Spec updated: Yes
  • Solution was to create a script and contain only the last 6 months worth of data, after each release to keep the size of the DB down. As well as to keep it as to keep this site current as production.

Notes

http://en.wikipedia.org/wiki/Sales_engineering

Personal tools