<div class="figure"> <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> </div> <a name="business-requirement-deliverable"></a> <h2>Business Requirement Deliverable</h2> <a name="introduction"></a> <h3>Introduction</h3> <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>Two new concepts complement the main business requirements model:</p> <ul class="simple"> <li>Deliverable lines</li> <li>Resource lines</li> </ul> <p>A field for pricelist estimation is available in the partner to be used in Deliverable and Resources lines valuation to customers.</p> <a name="what-is-a-deliverable-line"></a> <h4>What is a Deliverable Line?</h4> <p>Deliverable Lines (DL) contains products and services that will be delivered to the customer. They are <strong>customer oriented</strong> and can be either physical or service products:</p> <ul class="simple"> <li>Servers and procured goods</li> <li>Gap analysis services</li> <li>Module development services</li> <li>Training etc.</li> </ul> <p>These are the products that will appear in the SO and that the customer/stakeholder will receive.</p> <div class="figure"> <img alt="Business Requirement Deliverable lines" src="../business_requirement_deliverable/static/img/bus_req_deliverable.png" style="width: 600px;" /> </div> <a name="what-are-resources-lines"></a> <h4>What are Resources Lines?</h4> <p>Resources Lines (RL) are the different tasks or procurements needed to achieve one deliverable:</p> <ul class="simple"> <li>Service tasks (Development, consultant etc.)</li> <li>Procurement of other physical goods (server, etc.)</li> <li>Procurement of other virtual goods (templates, sub-contracting, etc.)</li> </ul> <p>RL depends on the DL or directly on BR</p> <div class="figure"> <img alt="Business Requirement Resources lines" src="../business_requirement_deliverable/static/img/bus_req_resource.png" style="width: 600px;" /> </div> <a name="what-is-the-difference-between-deliverable-and-resources"></a> <h4>What is the difference between Deliverable and Resources?</h4> <table class="docutils"> <colgroup> <col width="9%" /> <col width="46%" /> <col width="46%" /> </colgroup> <thead valign="bottom"> <tr><th class="head">Concept</th> <th class="head">Deliverables are:</th> <th class="head">Resources are:</th> </tr> </thead> <tbody valign="top"> <tr><td>Target</td> <td>Provided to the customer (“Functioning Website”)</td> <td>Executed internally (“Server+CSS modifications”)</td> </tr> <tr><td>Valuation</td> <td>Valued at Customer Sales Price</td> <td>Valued at Cost Price</td> </tr> <tr><td>Usage</td> <td>Used in Sales Quotations</td> <td>Used in Project management or procurement management</td> </tr> </tbody> </table> <p>Business Requirement contains Deliverable lines and Deliverable line contains Resource lines. Example of a structure:</p> <pre> <code>BR1 | |- DL1 | | | |- RL1 | |- RL2 | `- RL3 | |- DL2 | | | |- RL4 | |- RL5 | `- RL6 | BR2 | |- DL3 | | | |- RL7 | `- RL8 | |- DL4 | `- RL9</code> </pre> <a name="installation"></a> <h3>Installation</h3> <p>No specific steps required</p> <a name="configuration"></a> <h3>Configuration</h3> <a name="users"></a> <h4>Users</h4> <p>Estimation Pricelist: user can see the Sales price and revenue of the BR.</p> <a name="master-project"></a> <h4>Master project</h4> <p>You can define a master project linked to the business requirement. Default Customer from the project will be used to populate the BR. The customer can be changed if necessary.</p> <a name="valuation-of-the-deliverable-and-resources-lines"></a> <h4>Valuation of the Deliverable and Resources lines</h4> <p>When writing a BR the user has the possibility to add Deliverable and Resources lines. To value the Deliverable lines, you can specify an estimation price list in the customer, which will be used in 2 main places:</p> <ul class="simple"> <li>In Deliverable lines if the deliverable product is in pricelist</li> <li>In Resource lines if you want to value your deliverable from the resources</li> </ul> <p>NB: Here is the way Odoo will get a price in Deliverable and Resources Lines:</p> <ol class="arabic simple"> <li>If the Estimation Pricelist field is not empty use the Estimation pricelist</li> <li>If empty, use the standard customer pricelist field</li> <li>If no pricelist available (for example no customer defined in the project), use the product Sales price.</li> </ol> <a name="usage"></a> <h3>Usage</h3> <ol class="arabic simple"> <li>In the BR, you can add as many deliverable lines as necessary. Price of the deliverable lines will depend on the pricelist(s) in customer.</li> <li>Once the deliverable lines are created you can create as many resources lines as necessary in each DL. Cost price of the product will apply</li> <li>in RL you can already assign the responsible of the task if necessary</li> </ol> <div class="figure"> <img alt="Inputing the deliverables and resources lines" src="../business_requirement_deliverable/static/img/bus_req_deliverable2.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="bug-tracker"></a> <h3>Bug Tracker</h3> <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="known-issues-roadmap"></a> <h3>Known issues / Roadmap</h3> <ul class="simple"> <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="credits"></a> <h3>Credits</h3> <a name="contributors"></a> <h4>Contributors</h4> <ul class="simple"> <li>Eric Caudal &lt;<a class="reference external" href="mailto:eric.caudal&#64;elico-corp.com">eric.caudal&#64;elico-corp.com</a>&gt;</li> <li>Alex Duan &lt;<a class="reference external" href="mailto:alex.duan&#64;elico-corp.com">alex.duan&#64;elico-corp.com</a>&gt;</li> <li>Xie XiaoPeng &lt;<a class="reference external" href="mailto:xie.xiaopeng&#64;elico-corp.com">xie.xiaopeng&#64;elico-corp.com</a>&gt;</li> <li>Victor M. Martin &lt;<a class="reference external" href="mailto:victor.martin&#64;elico-corp.com">victor.martin&#64;elico-corp.com</a>&gt;</li> </ul> <a name="maintainer"></a> <h4>Maintainer</h4> <div class="figure"> <a class="reference external image-reference" href="https://odoo-community.org"><img alt="Odoo Community Association" src="https://odoo-community.org/logo.png" /></a> </div> <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>