Access to add and change pages is restricted. See: https://cwiki.apache.org/confluence/display/OFBIZ/Wiki+access

Add custom screens for different kinds of assets

1) Add IT Assets: Sceen is custom for adding computer and related assets into system.

2) Add Automobile Assets: Screen customized for adding automobile assets

Use cases for IsMgr application

Use case will be something like
1) Buyer creates purchase order for certain number of computer of certain specification.
Does the buyer do this or does the buyer negotiate a purchase order agreement with the vendor and then the vendor creates the purchase order?
3) Purchase order is send to vendor.
What is the difference between a "vendor" and a "supplier"? Why do you use the term "vendor" here and not "supplier"?
4) Vendor delivers ordered quantity of computer of ordered specification.
5) Computers are received as fixed assets by system administrator.
6) Computers are assigned to company employee and hence put in service.
7) Maintenance schedule is prepared for each computer placed in service.
8) Computer is reclaimed (unassigned) from an employee.
9) Maintenance order is created for new setup on the computer.
10) Computer is reassigned to an employee.
 

  • No labels

10 Comments

  1. Ron Wheeler

    Normally vendors/suppliers prepare quotes and buyers prepare POs. The PO may or may not contain the same terms as the quote depending who wants the order more.

    The vendor/supplier accepts or rejects the PO. If accepted, it becomes the legal contract.
    There can be many quotes leading up to a PO and none of them are contracts.

     

  2. Pierre Smits

    This outline of steps involves more applications and business domains than are facilitated within the asset maintenance application.  Keeping these included might lead to an unnecessary complicated application and thus degradation of choice (by the potentially applying/implementing party) and user experience.

    1. Jacques Le Roux

      Hi Pierre, are you claiming that we should get rid of this page (in favour of keeping Asset Maintenance Setup only)?

  3. Ron Wheeler

    Pierre,

    Can you clarify your point.

    Are saying that the Use case covers more than one component or that the use case is not supported?

    Would it be clearer if the parts of the use case that refered to Asset Management were identified.

    This Use Case is only 1 thing that people can do with assets and it would be helpful to have the other Use Cases presented so that the scope of the Asset Management is clearer.

    I have a minor disagreement with the Use Case in that it omits quotes and does not include the PO acceptance step which is critical to forming a legal contract (at least in the parts of the world that use law derived from British and American legal structures).

    I am not sure what parts of the Use case are supported by OFBiz currently or are in outstanding JIRAs or are dreams of the person who wrote the Use Case.

    Some are clearly outside OFBiz (vendor activities - quote creation, delivery)  but they are still part of the Use Case.

     

  4. Pierre Smits

    This page is a duplicate of Complete implementation of Asset Management application. There shouldn't be a need to have 2 pages describing the same.

  5. Ron Wheeler

    Agreed. This one has a few more steps in the use case than the duplicate and has more interesting comments:-)

    Can we delete the other page and rename this one?

  6. Pierre Smits

    IT asset mgt is already in place. The aspects regarding automotive assets can be captured in a wish through JIRA.

     

    1. Jacques Le Roux

      It's not clear to me if the original page is already completely implemented or not. Two ways to know it, reverse engineer it, or easier an answer from Anil Patel

  7. Ron Wheeler

    Pierre,

    Perhaps we are at cross purposes here.

    My understanding is that this page is supposed to be the complete description of the Use Cases and design overview for this component.

    It is more complete than the page that it copies but must be missing a lot of Use Cases and design goals that are met by the current Asset Management.

    From your comments, it appears that you believe that the "Add...." items never got added and are, in fact, things that belong on a wish list or a separate child page of future features open for discussion or a JIRA if someone has a definite specification that could be implemented.

    My original comments were meant as a correction of the Use Case rather than any assertion about what feature is part of which component.

    The current Use Case is an important Use Case to almost every company but does cross many boundaries even when looking at it from an organizational viewpoint.

    It would be helpful to include a few more restricted Use Cases that are satisfied wholely within the Asset Management component.

    These would seem to address your concerns about the overly broad scope of the sole current Use Case.

     

     

    1. Jacques Le Roux

      Maybe we could somehow add the use cases of this page on the original one in a new section with some explanations (kinda overriding the initial section). Having both is undoubtedly confusing.