Search 1.9 billion lines of Odoo code on GitHub
business_requirement_deliverable_cost
<a class="reference external image-reference" href="https://www.gnu.org/licenses/agpl-3.0-standalone.html"><img alt="License: AGPL-3" src="https://img.shields.io/badge/licence-AGPL--3-blue.svg">
</a>
<a name="business-requirement-deliverable-cost-control"></a>
<h2>Business Requirement Deliverable Cost Control</h2>
<a name="introduction"></a>
<h3>Introduction</h3>
<p>This module is part of a set ("Business Requirement").</p>
<p>The Business Requirements features start as independent entities, and can be
used as standalone.</p>
<p>Additional modules integrate them with other business areas, such as Sales,
Procurement, Project or Analytic Accounting. For example:</p>
<ul class="simple">
<li>Sales Quotation can have an estimation supported by a BR analysis</li>
<li>Project Tasks can be related to the BRs they implement or support</li>
<li>Procurement and purchase can be generated out of the BR</li>
</ul>
<div class="figure">
<img alt="Business Requirement List view" src="static/img/bus_req_tree.png" style="width: 600px;" />
</div>
<p>The following diagram gives a simplified view of the universe:</p>
<div class="figure">
<img alt="Business Requirement modules diagram" src="static/img/bus_req_module_diag.png" style="width: 600px;" />
</div>
<p>This module is part of a set ("Business Requirement") and provides the basic
models for business requirement management and project time/cost estimation.</p>
<p>This module is part of a set ("Business Requirement").
The Business Requirements features start as independent entities, and can be used as standalone.
Additional modules integrate them with other business areas, such as Sales, Procurement, Project or Analytic Accounting. For example:
* a Sales Quotation can have an estimation supported by a BR analysis,
* Project Tasks can be related to the BRs they implement or support.
* Procurement and purchase can be generated our of the BR.</p>
<p><img alt="Business Requirement List view" src="business_requirement_deliverable_cost/static/img/bus_req_tree.png" style="width: 800px;" /></p>
<p>The following diagram gives a simplified view of the universe:</p>
<p><img alt="Business Requirement modules diagram" src="business_requirement_deliverable_cost/static/img/bus_req_module_diag.png" style="width: 800px;" /></p>
<a name="what-is-a-business-requirement"></a>
<h3>What is a Business Requirement?</h3>
<p>A Business requirement (BR) is the expression of a business need by a customer
or internal project user.</p>
<p>A BR can contain multiple different parts depending on the company needs:</p>
<ul class="simple">
<li>Customer Story: this is the requirement as expressed by the customer</li>
<li>Scenario: How/where the current solution can provide a suitable scenario to
answer the customer story</li>
<li>Gap: For the uncovered part of the scenario, elaborate the gap/need for specific
developments/setup</li>
<li>Deliverables to be provided to the customer/user</li>
<li>Resources necessary to achieve the deliverables</li>
<li>Additional information (approval, cost control etc.)</li>
</ul>
<p>These modules were originally designed for the service/IT industry but the
requirement management is generic and can apply to many cases/industries (customer
or internal projects):</p>
<ul class="simple">
<li>Construction</li>
<li>Trading (New product development)</li>
<li>Business Consultancy</li>
<li>IT development</li>
</ul>
<p>What is the difference between a BR and CRM lead?</p>
<ul class="simple">
<li>CRM leads are sales oriented</li>
<li>BR are project and workload estimation oriented</li>
</ul>
<p>This module is part of a set of modules (<a class="reference external" href="https://github.com/OCA/business-requirement/blob/10.0/README.md">Business Requirements</a>)</p>
<p>This module improves the cost control of the original module with the following:</p>
<ul class="simple">
<li>Estimation sales price on resource lines. It provides a simple way to
calculate the sales price of the deliverable based on the necessary
resources lines (see usage).</li>
<li>Adds ACL for sales price and resource cost confidentiality.</li>
<li>Creates a tab Cost control in the Business Requirement for simple Gross Profit
control.</li>
<li>Multi-currency compatible: sales price is valued at currency Pricelist and
converted back to the reporting company currency for the cost control.</li>
</ul>
<a name="configuration"></a>
<h4>Configuration</h4>
<a name="users"></a>
<h5>Users</h5>
<ul class="simple">
<li><strong>Business Requirement Sales Estimates</strong>: Can See the sales prices in DL and RL (ideal for sales/presales)</li>
<li><strong>Business Requirement Cost Control</strong>: Can See the cost prices for project profit control (Manager/Finance dept)</li>
</ul>
<p>Without Sales Estimate nor Cost Control rights:</p>
<p><img alt="No access to sales or cost control information (Simple user)" src="business_requirement_deliverable_cost/static/img/bus_req_acl1.png" style="width: 800px;" /></p>
<p>Without Cost Control rights:</p>
<p><img alt="Access to sales price with no cost control (Salesmen)" src="business_requirement_deliverable_cost/static/img/bus_req_acl2.png" style="width: 800px;" /></p>
<p>With both Sales Estimate and Cost Control rights:</p>
<p><img alt="Full access to sales price and cost control (Financial dept)" src="business_requirement_deliverable_cost/static/img/bus_req_acl3.png" style="width: 800px;" /></p>
<a name="estimation-pricelist"></a>
<h5>Estimation Pricelist</h5>
<p>You can define the Estimation price list in the Master Project which will be
used in deliverable lines and sales price for the resource lines.</p>
<a name="usage"></a>
<h4>Usage</h4>
<p>The pricelist stored in the Project/Estimation pricelist field will be used to help the calculation
of the expected revenue of a Deliverable based on the sum of related RL.</p>
<ol class="arabic simple">
<li>In the BR, you can add as many deliverable lines as necessary. You can keep the price empty at that stage.</li>
<li>Once the deliverable lines are created you can create as many resources lines as necessary in each DL.</li>
<li>in RL, the estimation sales price will be display per resource.</li>
<li>The total Revenue from the resources (sum of the sales estimation for all RL) can be manually added back to the deliverable line.</li>
<li>you can review the cost control tab of your BR as followed (only available for ACL Cost Control)</li>
<li>Eventually you can manually update the price of all resource clicking on the Update button.</li>
</ol>
<div class="figure">
<img alt="Control your cost for the BR" src="static/img/bus_req_control.png" style="width: 600px;" />
</div>
<div class="figure">
<a class="reference external image-reference" href="https://runbot.odoo-community.org/runbot/222/10.0"><img alt="Try me on Runbot" src="https://odoo-community.org/website/image/ir.attachment/5784_f2813bd/datas" /></a>
</div>
<a name="known-issues-roadmap"></a>
<h4>Known issues / Roadmap</h4>
<ul class="simple">
<li>Display the currency in the cost control panel and deliverable</li>
<li>As of version 10.0.1.0.0, the estimation pricelist has been moved from Project to
Partner object. There is no migration script for the change and the data will have
to be migrated manually.</li>
</ul>
<a name="bug-tracker"></a>
<h4>Bug Tracker</h4>
<p>Bugs are tracked on <a class="reference external" href="https://github.com/OCA/business-requirement/issues">GitHub Issues</a>.
In case of trouble, please check there if your issue has already been reported.
If you spotted it first, help us smashing it by providing a detailed and welcomed feedback.</p>
<a name="credits"></a>
<h4>Credits</h4>
<a name="contributors"></a>
<h5>Contributors</h5>
<ul class="simple">
<li>Eric Caudal <<a class="reference external" href="mailto:eric.caudal@elico-corp.com">eric.caudal@elico-corp.com</a>></li>
<li>Alex Duan <<a class="reference external" href="mailto:alex.duan@elico-corp.com">alex.duan@elico-corp.com</a>></li>
<li>Xie XiaoPeng <<a class="reference external" href="mailto:xie.xiaopeng@elico-corp.com">xie.xiaopeng@elico-corp.com</a>></li>
<li>Luke Zheng <<a class="reference external" href="mailto:luke.zheng@elico-corp.com">luke.zheng@elico-corp.com</a>></li>
<li>Victor Martin <<a class="reference external" href="mailto:victor.martin@elico-corp.com">victor.martin@elico-corp.com</a>></li>
</ul>
<a name="maintainer"></a>
<h5>Maintainer</h5>
<a class="reference external image-reference" href="https://odoo-community.org"><img alt="Odoo Community Association" src="https://odoo-community.org/logo.png" /></a>
<p>This module is maintained by the OCA.</p>
<p>OCA, or the Odoo Community Association, is a nonprofit organization whose
mission is to support the collaborative development of Odoo features and
promote its widespread use.</p>
<p>To contribute to this module, please visit <a class="reference external" href="https://odoo-community.org">https://odoo-community.org</a>.</p>