.. figure:: https://img.shields.io/badge/licence-AGPL--3-blue.svg
:target: https://www.gnu.org/licenses/agpl-3.0-standalone.html
:alt: License: AGPL-3
================================
Business Requirement Deliverable
================================
Introduction
============
This module is part of a set of modules (`Business Requirements <https://github.com/OCA/business-requirement/blob/8.0/README.md>`_)
Two new concepts complement the main business requirements model:
* Deliverable lines
* Resource lines
A field for pricelist estimation is available in the partner to be used in Deliverable
and Resources lines valuation to customers.
What is a Deliverable Line?
---------------------------
Deliverable Lines (DL) contains products and services that will be delivered to the
customer. They are **customer oriented** and can be either physical or service products:
* Servers and procured goods
* Gap analysis services
* Module development services
* Training etc.
These are the products that will appear in the SO and that the customer/stakeholder will receive.
.. figure:: ../business_requirement_deliverable/static/img/bus_req_deliverable.png
:width: 600 px
:alt: Business Requirement Deliverable lines
What are Resources Lines?
-------------------------
Resources Lines (RL) are the different tasks or procurements needed to achieve one deliverable:
* Service tasks (Development, consultant etc.)
* Procurement of other physical goods (server, etc.)
* Procurement of other virtual goods (templates, sub-contracting, etc.)
RL depends on the DL or directly on BR
.. figure:: ../business_requirement_deliverable/static/img/bus_req_resource.png
:width: 600 px
:alt: Business Requirement Resources lines
What is the difference between Deliverable and Resources?
---------------------------------------------------------
=========== ======================================================== ========================================================
Concept Deliverables are: Resources are:
=========== ======================================================== ========================================================
Target Provided to the customer (“Functioning Website”) Executed internally (“Server+CSS modifications”)
Valuation Valued at Customer Sales Price Valued at Cost Price
Usage Used in Sales Quotations Used in Project management or procurement management
=========== ======================================================== ========================================================
Business Requirement contains Deliverable lines and Deliverable line contains Resource lines. Example of a structure:
::
BR1
|
|- DL1
| |
| |- RL1
| |- RL2
| `- RL3
|
|- DL2
| |
| |- RL4
| |- RL5
| `- RL6
|
BR2
|
|- DL3
| |
| |- RL7
| `- RL8
|
|- DL4
| `- RL9
Installation
============
No specific steps required
Configuration
=============
Users
-----
Estimation Pricelist: user can see the Sales price and revenue of the BR.
Master project
--------------
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.
Valuation of the Deliverable and Resources lines
------------------------------------------------
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:
* In Deliverable lines if the deliverable product is in pricelist
* In Resource lines if you want to value your deliverable from the resources
NB: Here is the way Odoo will get a price in Deliverable and Resources Lines:
#. If the Estimation Pricelist field is not empty use the Estimation pricelist
#. If empty, use the standard customer pricelist field
#. If no pricelist available (for example no customer defined in the project), use
the product Sales price.
Usage
=====
#. 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.
#. 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
#. in RL you can already assign the responsible of the task if necessary
.. figure:: ../business_requirement_deliverable/static/img/bus_req_deliverable2.png
:width: 600 px
:alt: Inputing the deliverables and resources lines
.. figure:: https://odoo-community.org/website/image/ir.attachment/5784_f2813bd/datas
:alt: Try me on Runbot
:target: https://runbot.odoo-community.org/runbot/222/8.0
Bug Tracker
===========
Bugs are tracked on `GitHub Issues <https://github.com/OCA/business-requirement/issues>`_.
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.
Known issues / Roadmap
======================
* As of version 8.0.5.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.
Credits
=======
Contributors
------------
* Eric Caudal <eric.caudal@elico-corp.com>
* Alex Duan <alex.duan@elico-corp.com>
* Xie XiaoPeng <xie.xiaopeng@elico-corp.com>
* Victor M. Martin <victor.martin@elico-corp.com>
Maintainer
----------
.. figure:: https://odoo-community.org/logo.png
:alt: Odoo Community Association
:target: https://odoo-community.org
This module is maintained by the OCA.
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.
To contribute to this module, please visit https://odoo-community.org.
Raw data
{
"_id": null,
"home_page": "https://www.elico-corp.com/",
"name": "odoo8-addon-business-requirement-deliverable",
"maintainer": "",
"docs_url": null,
"requires_python": "",
"maintainer_email": "",
"keywords": "",
"author": "Elico Corp, Odoo Community Association (OCA)",
"author_email": "support@odoo-community.org",
"download_url": "",
"platform": "UNKNOWN",
"description": ".. figure:: https://img.shields.io/badge/licence-AGPL--3-blue.svg\n :target: https://www.gnu.org/licenses/agpl-3.0-standalone.html\n :alt: License: AGPL-3\n\n================================\nBusiness Requirement Deliverable\n================================\n\nIntroduction\n============\n\nThis module is part of a set of modules (`Business Requirements <https://github.com/OCA/business-requirement/blob/8.0/README.md>`_) \n\nTwo new concepts complement the main business requirements model:\n\n* Deliverable lines\n* Resource lines\n\nA field for pricelist estimation is available in the partner to be used in Deliverable\nand Resources lines valuation to customers.\n\nWhat is a Deliverable Line?\n---------------------------\n\nDeliverable Lines (DL) contains products and services that will be delivered to the \ncustomer. They are **customer oriented** and can be either physical or service products:\n\n* Servers and procured goods\n* Gap analysis services\n* Module development services\n* Training etc.\n\nThese are the products that will appear in the SO and that the customer/stakeholder will receive.\n\n.. figure:: ../business_requirement_deliverable/static/img/bus_req_deliverable.png\n :width: 600 px\n :alt: Business Requirement Deliverable lines\n\n\nWhat are Resources Lines?\n-------------------------\n\nResources Lines (RL) are the different tasks or procurements needed to achieve one deliverable:\n\n* Service tasks (Development, consultant etc.)\n* Procurement of other physical goods (server, etc.)\n* Procurement of other virtual goods (templates, sub-contracting, etc.)\n\nRL depends on the DL or directly on BR\n\n.. figure:: ../business_requirement_deliverable/static/img/bus_req_resource.png\n :width: 600 px\n :alt: Business Requirement Resources lines\n\nWhat is the difference between Deliverable and Resources?\n---------------------------------------------------------\n\n=========== ======================================================== ========================================================\nConcept Deliverables are: Resources are:\n=========== ======================================================== ========================================================\nTarget Provided to the customer (\u201cFunctioning Website\u201d) Executed internally (\u201cServer+CSS modifications\u201d)\nValuation Valued at Customer Sales Price Valued at Cost Price\nUsage Used in Sales Quotations Used in Project management or procurement management\n=========== ======================================================== ========================================================\n\nBusiness Requirement contains Deliverable lines and Deliverable line contains Resource lines. Example of a structure:\n\n::\n\n BR1\n |\n |- DL1\n | |\n | |- RL1\n | |- RL2\n | `- RL3\n |\n |- DL2\n | |\n | |- RL4\n | |- RL5\n | `- RL6\n |\n BR2\n |\n |- DL3\n | |\n | |- RL7\n | `- RL8\n |\n |- DL4\n | `- RL9\n\n\n\nInstallation\n============\n\nNo specific steps required\n\nConfiguration\n=============\n\nUsers\n-----\n\nEstimation Pricelist: user can see the Sales price and revenue of the BR.\n\nMaster project\n--------------\n\nYou can define a master project linked to the business requirement. Default Customer \nfrom the project will be used to populate the BR. The customer can be changed if necessary.\n\nValuation of the Deliverable and Resources lines\n------------------------------------------------\nWhen writing a BR the user has the possibility to add Deliverable and Resources lines.\nTo value the Deliverable lines, you can specify an estimation price list in the customer,\nwhich will be used in 2 main places:\n\n* In Deliverable lines if the deliverable product is in pricelist\n* In Resource lines if you want to value your deliverable from the resources\n\nNB: Here is the way Odoo will get a price in Deliverable and Resources Lines:\n\n#. If the Estimation Pricelist field is not empty use the Estimation pricelist \n#. If empty, use the standard customer pricelist field\n#. If no pricelist available (for example no customer defined in the project), use\n the product Sales price.\n\n\nUsage\n=====\n\n#. In the BR, you can add as many deliverable lines as necessary. Price of the deliverable \n lines will depend on the pricelist(s) in customer.\n\n#. Once the deliverable lines are created you can create as many resources lines as necessary\n in each DL. Cost price of the product will apply\n\n#. in RL you can already assign the responsible of the task if necessary\n\n.. figure:: ../business_requirement_deliverable/static/img/bus_req_deliverable2.png\n :width: 600 px\n :alt: Inputing the deliverables and resources lines\n\n\n.. figure:: https://odoo-community.org/website/image/ir.attachment/5784_f2813bd/datas\n :alt: Try me on Runbot\n :target: https://runbot.odoo-community.org/runbot/222/8.0\n\nBug Tracker\n===========\n\nBugs are tracked on `GitHub Issues <https://github.com/OCA/business-requirement/issues>`_.\nIn case of trouble, please check there if your issue has already been reported.\nIf you spotted it first, help us smashing it by providing a detailed and welcomed feedback.\n\nKnown issues / Roadmap\n======================\n* As of version 8.0.5.0.0, the estimation pricelist has been moved from Project to\n Partner object. There is no migration script for the change and the data will \n have to be migrated manually.\nCredits\n=======\n\nContributors\n------------\n\n* Eric Caudal <eric.caudal@elico-corp.com>\n* Alex Duan <alex.duan@elico-corp.com>\n* Xie XiaoPeng <xie.xiaopeng@elico-corp.com>\n* Victor M. Martin <victor.martin@elico-corp.com>\n\nMaintainer\n----------\n\n.. figure:: https://odoo-community.org/logo.png\n :alt: Odoo Community Association\n :target: https://odoo-community.org\n\nThis module is maintained by the OCA.\n\nOCA, or the Odoo Community Association, is a nonprofit organization whose\nmission is to support the collaborative development of Odoo features and\npromote its widespread use.\n\nTo contribute to this module, please visit https://odoo-community.org.",
"bugtrack_url": null,
"license": "AGPL-3",
"summary": "Manage the Business Requirement Deliverables and Resources for your customers",
"version": "8.0.5.0.1",
"split_keywords": [],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "452bed68ddddf13a50aa45fe631fdc8e99795f0f158dc064ab3f1b4ff58e8744",
"md5": "6e33f1fe685d7719b62651af3de233ae",
"sha256": "7a481b85492ef02de222bf78b143a826d7846b881ca7c3d2de0b3b0830b125cd"
},
"downloads": -1,
"filename": "odoo8_addon_business_requirement_deliverable-8.0.5.0.1-py2-none-any.whl",
"has_sig": false,
"md5_digest": "6e33f1fe685d7719b62651af3de233ae",
"packagetype": "bdist_wheel",
"python_version": "py2",
"requires_python": null,
"size": 284153,
"upload_time": "2017-05-10T04:30:22",
"upload_time_iso_8601": "2017-05-10T04:30:22.029249Z",
"url": "https://files.pythonhosted.org/packages/45/2b/ed68ddddf13a50aa45fe631fdc8e99795f0f158dc064ab3f1b4ff58e8744/odoo8_addon_business_requirement_deliverable-8.0.5.0.1-py2-none-any.whl",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2017-05-10 04:30:22",
"github": false,
"gitlab": false,
"bitbucket": false,
"lcname": "odoo8-addon-business-requirement-deliverable"
}
JSON