CT2 Resources Demand Supply Allocation

From UG

Revision as of 14:39, 18 May 2010 (edit) Alex (Talk | contribs) (→TMS Integration) ← Older edit		Revision as of 15:48, 18 May 2010 (edit) (undo) Alex (Talk | contribs) (→Inventory Management) Newer edit →
Line 182:		Line 182:
	* Estimates		* Estimates
-	** start: July - Sept	+	** start: July - Aug
	** length low: 6 month		** length low: 6 month
	** length high: 12 month		** length high: 12 month

---

Revision as of 15:48, 18 May 2010

Contents 1 General Info 2 Metrics 2.1 Assumptions 2.2 Types of load 2.3 FTD 2.3.1 1 FTD 2.3.2 1/4 FTD 2.3.3 1/2 FTD 2.4 FTL 2.4.1 full load 2.4.2 medium load 2.4.3 low load 2.4.4 very low load 3 2010 June to December Forecast 3.1 Existing modules 3.1.1 Acc Component 3.1.2 Client Component 3.1.3 Ops Component 3.1.4 Ops Pdfs Component 3.1.5 Ops Reps Component 3.2 New Modules 3.2.1 TMS Integration 3.2.2 CT2 TMS features (Trucking Domestic Optimization) 3.2.3 Rates Interface 3.2.4 EDI 3.2.5 Inventory Management 3.2.6 www.jaguarfreight.com website re-design 3.3 Etc 4 Misc 4.1 Development based on Requirements not Detailed Design

General Info

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! ))

• parent mantis: http://mantis.jaguarfreight.com/mantis/view.php?id=2054

Metrics

Assumptions

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

Types of load

There are 2 types of activities:

• continuous: bugfix, tweaking (small to medium changes)
• projects

FTD

FTD = full time developer

1 FTD

40 h per week ~ 160 per month

1/4 FTD

10 h per week ~ 40 per month

1/2 FTD

20 h per week ~ 80 per month

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).

full load

• 1 ftl (full load)

if average numb of hours required: 30 to 40 per week ~ 120-160 per month

medium load

• 3/4 ftl (med load)

if average numb of hours required: 20 to 30 per week ~ 80-120 per month

low load

• 1/2 ftl (low load)

if average numb of hours required: 10 to 20 per week ~ 40-80 per month

very low load

• 1/4 ftl (very low load)

if average numb of hours required: 1 to 10 per week ~ 4-40 per month

2010 June to December Forecast

Existing modules

Acc Component

• continuous bug-fix/tweaking:
  • emh low = 5 per week
  • emh high = 10 per week

• project: P&L Re-design
  • Re-design cost mapping and P&L for CTs, Groups, Masters
  • emh = TBD
  • deadline: asap

• project Salesman module
  • see Category:Salesman
  • emh = TBD
  • deadline: asap

Client Component

• continuous bug-fix/tweaking:
  • emh low = 10 per week
  • emh high = 30 per week

• project: IM feature
  • see #0001707 Replace Skype with our own Instant Messaging feature
  • emh = TBD
  • deadline: asap

• project: Agent Interface
  • see #0001999 Create Agent Interface component/application
  • emh = TBD
  • deadline: asap

Ops Component

• continuous bug-fix/tweaking:
  • emh low = 20 per week
  • emh high = 40 per week (could be even more)

• project: TBD
  • emh = TBD

Ops Pdfs Component

• continuous bug-fix/tweaking:
  • emh low = 10 per week (will be getting lower soon)
  • emh high = 20 per week (will be getting lower soon)

• project: TBD
  • emh = TBD

Ops Reps Component

• continuous bug-fix/tweaking:
  • emh low = 10 per week (will be getting lower soon)
  • emh high = 30 per week (will be lower if no new reports requested)

• project: All fields
  • #0001998 Have all CT fields available on all CT reports
  • emh = TBD

New Modules

TMS Integration

Jaguar is planning to purchase a large TMS system that has to be integrated with CT2. This would mean:

• supporting real time integration / flow of data between 2 systems (one or both directions)
• potentially adding additional fields and features to support above

• Estimates
  • start: June-Aug
  • length low: 1 month
  • length high: 3 month
  • emh low = 30 per week
  • emh high = 40 per week

CT2 TMS features (Trucking Domestic Optimization)

Jaguar plans to add a number of complex TMS features to CT2

• Estimates
  • start: July-September
  • length low: 6 month
  • length high: 12 month
  • emh low = 20 per week
  • emh high = 40 per week

Rates Interface

Jaguar plans to add Rates Interface.

• Estimates
  • start: July-September
  • length low: 2 month
  • length high: 3 month
  • emh low = 20 per week
  • emh high = 40 per week

EDI

Jaguar plans to integrate with Clients, Vendors, etc through EDI (for example receive Traffic Sheets, send Invoices). Please note that there many companies Jaguar interface so if this is successful then EDI could be a constant task.

• Estimates
  • start: asap
  • length low: 2 month
  • length high: 12 month
  • emh low = 20 per week
  • emh high = 40 per week

Inventory Management

Jaguar plans to create Inventory Management components (as a CT2 feature or stand alone application)

• Estimates
  • start: July - Aug
  • length low: 6 month
  • length high: 12 month
  • emh low = 20 per week
  • emh high = 40 per week

www.jaguarfreight.com website re-design

Jaguar plans to integrate with Clients, Vendors, etc through EDI (for example receive Traffic Sheets, send Invoices)

• Estimates
  • start: asap
  • length low: 2 month
  • length high: 4 month
  • emh low = 20 per week
  • emh high = 40 per week

Etc

Misc

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