CT2 Resources Demand Supply Allocation

From UG

(Difference between revisions)
Jump to: navigation, search
(→2010 June to December Forecast)
(→2010 June to December Forecast)
Line 48: Line 48:
* ''continuous support/tweaking:''   
* ''continuous support/tweaking:''   
 +
** emh = 0-10 per week
-
* projects:
+
* project 1) Re-design cost mapping and P&L for CTs, Groups, Masters
-
:: need to re-design/fix mapping of cost mapping against CTs and groups of CTs and P/L  
+
** emh = TBD
-
:: sales person feature / commission report
+
** deadline: asap
 +
 
 +
* project 2) see [[:Category:Salesman]]
 +
** emh = TBD
 +
** deadline: asap
==== Client Component ====
==== Client Component ====
 +
 +
* ''continuous support/tweaking:'' 
 +
** emh = 10-20 per week
 +
 +
* project 1) see #0001707 Replace Skype with our own Instant Messaging feature
 +
** emh = TBD
 +
** deadline: asap
 +
 +
* project 2) see #0001999 Create Agent Interface component/application
 +
** emh = TBD
 +
** deadline: asap
==== Ops Component ====
==== Ops Component ====
 +
 +
* ''continuous support/tweaking:'' 
 +
** emh = 10-20 per week
 +
 +
* project 1)  ...
 +
** emh = TBD
==== Ops Pdfs Component ====
==== Ops Pdfs Component ====
 +
 +
* ''continuous support/tweaking:'' 
 +
** emh = 10-20 per week
==== Ops Reps Component ====
==== Ops Reps Component ====
 +
 +
* ''continuous support/tweaking:'' 
 +
** emh = 20-30 per week
=== New Modules ===
=== New Modules ===
 +
 +
==== Integration with TMS ====
==== Trucking Domestic Optimization ====
==== Trucking Domestic Optimization ====
==== Rates Interface ====
==== Rates Interface ====
-
 
-
==== Agent Interface ====
 
==== EDI ====
==== EDI ====

Revision as of 17:04, 17 May 2010


This article is about Demand for CT2 features and related Supply / Allocation of Human Resources.

We need to build smart Supply Chain for Software Development! ))

Contents

Metrics

There are 2 types of activities:

  • continuous
  • projects

ftl

It is proposed to use ftl (full time load) unit of measurement. This is to measure demand for IT staff (SAs, BAs, developers, QAs, Support Engineers).

Assumptions:

  • One full time employee works 8 m/h a day ~ 40 m/h a week ~ 168 m/h a month

The following metrics are suggested:

full load

  • 1 ftl (full load)
if average numb of hours required per week is 30 to 40

medium load

  • 3/4 ftl (med load)
if average numb of hours required per week is 20 to 30

low load

  • 1/2 ftl (low load)
if average numb of hours required per week is 10 to 20

very low load

  • 1/4 ftl (very low load)
if average numb of hours required per week is 0 to 10

2010 June to December Forecast

Existing modules

Acc Component

  • continuous support/tweaking:
    • emh = 0-10 per week
  • project 1) Re-design cost mapping and P&L for CTs, Groups, Masters
    • emh = TBD
    • deadline: asap

Client Component

  • continuous support/tweaking:
    • emh = 10-20 per week
  • project 1) see #0001707 Replace Skype with our own Instant Messaging feature
    • emh = TBD
    • deadline: asap
  • project 2) see #0001999 Create Agent Interface component/application
    • emh = TBD
    • deadline: asap

Ops Component

  • continuous support/tweaking:
    • emh = 10-20 per week
  • project 1) ...
    • emh = TBD

Ops Pdfs Component

  • continuous support/tweaking:
    • emh = 10-20 per week

Ops Reps Component

  • continuous support/tweaking:
    • emh = 20-30 per week

New Modules

Integration with TMS

Trucking Domestic Optimization

Rates Interface

EDI

Inventory Management

www.jaguarfreight.com website re-design

Etc

Development based on Requirements not Detailed Design

2 possible options:

  • Remote Developer (programmer) creates detailed design based on requirements
  • Remote Designer creates detailed design based on requirements

Both options would increase numb of hours required in Remote Team

Retrieved from "https://wiki.jaguarfreight.com/CT2_Resources_Demand_Supply_Allocation"
Personal tools