4.3. Enterprise Electronic Agreement Customization - Business Use Case
This use case applies to the negotiation process conducted between the enterprise and the trading partner expecting to result in a customized electronic model agreement from a UN/CEFACT or industry electronic model agreement.
4.3.1 Customize
|
Business Process Use Case |
|
|
Name |
Create and Customize |
|
Use Case ID Number |
Electronic Agreement (EA) 1 |
|
Description |
The enterprise contract administrator accesses industry or enterprise library to obtain model electronic agreement based upon UN/CEFACT Electronic model agreement and process. The enterprise contract administrator customizes the enterprise version of the electronic model agreement and ensures the agreement is accessible the enterprise site for public access by potential trading partners. |
|
Initiating Actor |
Contract Administrator |
|
Event Flow |
Main Scenario Contract Administrator obtains industry model of electronic model agreement. Contract Administrator customizes the agreement with enterprise unique requirements. Contract Administrator determines which of the clauses will include the feature to accept / reject options, and will be allowed and activated in the electronic model agreement. Contract administrator will place the enterprise electronic model agreement on the public enterprise portal for access (or delivery by other means) by the trading partner contracts administrator. Example 1: An aerospace contractor accesses the Aerospace & Defense Industry library and downloads an industry developed electronic model agreement which may be customized into a enterprise electronic model agreement. This electronic model agreement may be posted on the enterprise's public enterprise site. |
|
Expected Outcome |
The enterprise instance of the electronic agreement will utilize UN/CEFACT based electronic model agreement format and rules which will provide the 1st step in producing a non-refutable electronic agreement and auditable process. |
|
Exception |
To be defined. |
|
Business Process Data Categories |
Contract agreement header data |
These use cases apply once the enterprise has customized its electronic agreement model and makes it available for the purpose of electronic negotiation with its potential trading partners.
electronic model agreement
This is the most typical negotiation scenario that occurs between potential trading partners when jointly developing a contractual agreement defining the basis of their electronic business relationship with one another.
|
Business Process Use Case |
|
|
Name |
Negotiated electronic model agreement |
|
Use Case ID Number |
EA 2 |
|
Description |
The Trading Partner obtains the intended enterprise electronic model agreement. The Trading Partner reviews and may accept or produce counter proposal using the electronic model agreement negotiation process. The trading partner uses the standard negotiation process to develop a joint electronic agreement for final execution as evidenced by digital signature. |
|
Initiating Actor |
Trading partner contracts administrator |
|
Participating Actor |
|
|
Event Flow |
Main Scenario Trading partner contract administrator obtains intended enterprise's electronic model agreement, e.g. via public enterprise portal, web service, email, etc. Trading partner's contract administrators negotiate a joint agreement. Intended enterprise contract administrator reviews trading partner's proposed joint electronic agreement and rejects or accepts with negotiated terms. Electronic exchanges are made to the electronic model agreement are exchanged until both partners either reject or accept the document. When both trading partners accept the negotiated joint electronic agreement final digital sign off (EA 3) process begins. Example 1: Aerospace trading partner wishes to sell parts to a major aerospace Original Equipment Manufacturer (OEM). The trading partner accesses the public portal of the OEM to obtain a Enterprise Electronic model agreement to determine the terms and conditions for conducting business electronically with the OEM. The OEM has used the UN/CEFACT Electronic model agreement rendered in The Aerospace Industry of America's Global Trading Partner Agreement (GTPA). The trading partner accepts the terms and completes the GTPA electronic model agreement by using the UN/CEFACT negotiation process. The trading partner submits the accepted GTPA electronic model agreement to the OEM who accepts it. They both agree to move to the digital sign off process in EA 3. |
|
Expected Outcome |
The final joint electronic model agreement will be negotiated using the UN/CEFACT standard negotiation process and document electronic model agreement. The final agreement will be digitally signed in use case EA 3. This standard electronic model agreement and process will produce a non-refutable electronic agreement. |
|
Exception |
At any time either partner may choose to terminate the negotiation. |
|
Business Process Data Categories |
Contract agreement header data |