SOW Estimation Engine & Technical Analysis - EV Route Charger Mobile Application Proposal

Expected Effort

⏱️

0 hrs

95% Range: 0h - 0h

Calculated Budget

💰

₹0

Base: ₹0 | Cont: 0%

Risk Multiplier

⚠️

1.00x

Risk Score: 0/100

Project Duration

📅

0 Days

UI Dev: 0d | Integration: 14d

Effort Distribution by Module Hours allocated per BRD module area

Proposal Metadata

Project Title

Client / Partner

Author / Architect

SOW Draft Version

Enable/Disable modules below. Disabled modules automatically zero-out relevant estimates and mark items as "Out of Scope" in the proposal.

Development progress is calculated based on the selected scope. The project covers a strict 6-month development timeline (26 Weeks / 13 Sprints).

Overall Development Progress

0%

0 of 13 Sprints In-Scope 0 of 0 Total Hours

Interactive Project Roadmap & Sprint Schedule

Click on any colored sprint bar to inspect scope, view task details, or update the progress status.

Planned In Progress Completed Excluded

Phase / Module	S1 W1-2	S2 W3-4	S3 W5-6	S4 W7-8	S5 W9-10	S6 W11-12	S7 W13-14	S8 W15-16	S9 W17-18	S10 W19-20	S11 W21-22	S12 W23-24	S13 W25-26

The backend interfaces with the OCPI 2.2.1 protocol. Toggle endpoints below to include them in the client integration scope.

	Method	Endpoint Route	OCPI Module	Backend Complexity	SOW Requirement Mapping

Module	Task Description	Role	Opt (O)	Likely (M)	Pess (P)	PERT (E)	StdDev

Configure team roles and hourly billing rates. Backend and QA roles are excluded as per project constraints.

Resource Role	Hourly Billing Rate (₹)	Assigned Capacity (FTE)	Subtotal Cost Share

6-Month (180 Days) Development Capacity Validation

The total project development effort of 1,969.3 hours aligns precisely with the resource capacity of the team over the 180-day (6-month) calendar timeline:

6 Months Calendar duration = 180 days, which translates to exactly 128.5 working days (excluding weekends).
At 8 working hours per day, a 1.0 FTE resource has a maximum capacity of 1,028 hours over 6 months.

Resource Role	Total Mapped Effort	Available FTE Capacity	FTE Allocation %
Junior UI Developer (1.0 FTE)	1,025.0 hrs	1,028.0 hrs	99.7%
Junior API Developer (1.0 FTE)	367.5 hrs	1,028.0 hrs	35.7%
Senior UI Developer (2.0 FTEs)	576.8 hrs	2,056.0 hrs	28.0%
Total Dev Effort	1,969.3 hrs	4,112.0 hrs	47.9%

Note: The Junior UI Developer is 99.7% allocated to UI development. The Junior API Developer is engaged at 35.7% to build API integrations in parallel. The Senior UI Developers (28% allocation) provide architectural guidance, code reviews, and governance to ensure success within the 180-day deadline.

Project risk assessment parameters aligned with Section 9 of the Client BRD. Risk ratings directly determine the project contingency buffer applied to the base development cost.

Risk Score Calculation Basis & Methodology

Individual Risk Score Formula: Risk Score = Likelihood (1-5) × Impact (1-5). Individual scores range from 1 (Very Low) to 25 (Critical).
Total Project Risk Score: Sum of scores across all active BRD risk categories (Current score: 56 / 150).
Contingency Buffer Formula: Contingency Buffer % = (Total Risk Score / 100) × 30%.
Current Contingency Buffer: At a risk score of 56, the applied contingency buffer is 16.8% (17%), added directly to base labor cost to insulate against third-party CPO delays and OCPI telemetry integration risks.

Risk Item	Mitigation Strategy	Likelihood (1-5)	Impact (1-5)	Risk Score

Document Status

CONFIDENTIAL DRAFT

Includes risk buffers, OCPI API scoping details, and client-side integration tasks.