Skip to content

Commit

Permalink
Merge remote-tracking branch 'upstream/hotfixes' into release
Browse files Browse the repository at this point in the history
  • Loading branch information
fit-alessandro-berti committed Apr 1, 2024
2 parents b4dd032 + fc3a408 commit a6ba08e
Show file tree
Hide file tree
Showing 49 changed files with 1,383 additions and 0 deletions.
23 changes: 23 additions & 0 deletions examples/llm/PET/doc-1.1
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
A small company manufactures customized bicycles.

Whenever the sales department receives an order , a new process instance is created.

A member of the sales department can then reject or accept the order for a customized bike.

In the former case , the process instance is finished.

In the latter case , the storehouse and the engineering department are informed.

The storehouse immediately processes the part list of the order and checks the required quantity of each part.

If the part is available in-house , it is reserved.

If it is not available , it is back-ordered.

This procedure is repeated for each item on the part list.

In the meantime , the engineering department prepares everything for the assembling of the ordered bicycle.

If the storehouse has successfully reserved or back-ordered every item of the part list and the preparation activity has finished , the engineering department assembles the bicycle.

Afterwards , the sales department ships the bicycle to the customer and finishes the process instance .
11 changes: 11 additions & 0 deletions examples/llm/PET/doc-1.2
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
A customer brings in a defective computer and the CRS checks the defect and hands out a repair cost calculation back.

If the customer decides that the costs are acceptable , the process continues , otherwise she takes her computer home unrepaired.

The ongoing repair consists of two activities , which are executed , in an arbitrary order.

The first activity is to check and repair the hardware , whereas the second activity checks and configures the software.

After each of these activities , the proper system functionality is tested.

If an error is detected another arbitrary repair activity is executed , otherwise the repair is finished .
25 changes: 25 additions & 0 deletions examples/llm/PET/doc-1.3
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
The Evanstonian is an upscale independent hotel.

When a guest calls room service at The Evanstonian , the room-service manager takes down the order.

She then submits an order ticket to the kitchen to begin preparing the food.

She also gives an order to the sommelier ( i.e.

, the wine waiter ) to fetch wine from the cellar and to prepare any other alcoholic beverages.

Eighty percent of room-service orders include wine or some other alcoholic beverage.

Finally , she assigns the order to the waiter.

While the kitchen and the sommelier are doing their tasks , the waiter readies a cart ( i.e.

, puts a tablecloth on the cart and gathers silverware ).

The waiter is also responsible for nonalcoholic drinks.

Once the food , wine , and cart are ready , the waiter delivers it to the guest ’ s room.

After returning to the room-service station , the waiter debits the guest ’ s account.

The waiter may wait to do the billing if he has another order to prepare or deliver .
21 changes: 21 additions & 0 deletions examples/llm/PET/doc-1.4
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
Whenever a company makes the decision to go public , its first task is to select the underwriters.

Underwriters act as financial midwives to a new issue.

Usually they play a triple role : First they provide the company with procedural and financial advice , then they buy the issue , and finally they resell it to the public.

Established underwriters are careful of their reputation and will not handle a new issue unless they believe the facts have been presented fairly.

Thus , in addition to handling the sale of a company ’ s issue , the underwriters in effect give their seal of approval to it.

They prepare a registration statement for the approval of the Securities and Exchange Commission ( SEC ).

In addition to registering the issue with the SEC , they need to check that the issue complies with the so-called blue-sky laws of each state that regulate sales of securities within the state.

While the registration statement is awaiting approval , underwriters begin to firm up the issue price.

They arrange a road show to talk to potential investors.

Immediately after they receive clearance from the SEC , underwriters fix the issue price.

After that they enter into a firm commitment to buy the stock and then offer it to the public , when they haven ’ t still found any reason not to do it .
5 changes: 5 additions & 0 deletions examples/llm/PET/doc-10.1
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
The MPON sents the dismissal to the MPOO.

The MPOO reviews the dismissal.

The MPOO opposes the dismissal of MPON or the MPOO confirmes the dismissal of the MPON .
15 changes: 15 additions & 0 deletions examples/llm/PET/doc-10.10
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
The fault detector reports a failure to the MPO or MPO has a suspicion of their own fault.

The MPO shall examine the failure.

The MPO rejects the failure of the fault detector or the MPO confirms the failure of the fault detector.

If the MPO confirms the failure of the fault detector , he informes the GO and the MSP.

The MPO fixes the fault at the measuring device.

The MPO shares the results of the repairs carried out with the fault detector.

The MPO will inform the GO about the resolution of the interference.

The MPO will inform the MSP about the resolution of the interference .
13 changes: 13 additions & 0 deletions examples/llm/PET/doc-10.11
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
The GO requests the measurements to the MSP.

The MSP checks the received request.

The MSP denies the request of the GO or the MSP performs the measurement.

The MSP informs the GO about the failure of the reading or the MSP transmits the measured values to the GO.

The GO processes the measured values.

The GO sends the changed values to the MSP.

The GO transmit the readings to the SP .
7 changes: 7 additions & 0 deletions examples/llm/PET/doc-10.12
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
The EC tells the INQ about the change of his master data.

The INQ notifies the IP of the change.

The IP checks whether the master data can be changed at the desired time.

The IP confirmes the changes of the INQ or the IP rejectes the changes of the INQ .
7 changes: 7 additions & 0 deletions examples/llm/PET/doc-10.13
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
The INQ transmits the transaction data request to the IP.

The IP checks the request of the INQ.

The IP answers the question of the INQ depending on the outcome of the examination , i.e.

Transmission of data or rejection .
9 changes: 9 additions & 0 deletions examples/llm/PET/doc-10.14
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
If the MPOO sends the bill for the temporary continuation of the metering point operations to the GO , the GO examines the bill.

If the MSPO sends the bill for the temporary continuation of the measurement to the GO , the GO examines the bill.

If the MSPO sends the bill for additional readings to the GO , the GO examines the bill.

If the MPOO sends the bill for the equipment acquisition to the MPON or the GO , the MPON or the GO examines the bill.

The GO or the MPON confirms the invoice with payment advice to the MPOO or the MSPO , or the GO or the MPON rejects the invoice of the MPOO or the MSPO .
27 changes: 27 additions & 0 deletions examples/llm/PET/doc-10.2
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
The MPON reports the meter operation to the GO.

The GO examines the application of the MPON.

The GO rejects the application of the MPON or the GO confirmes the application of the MPON.

The GO informs the MPOO about the registration confirmation of the MPON.

The GO informs the MSPO about the registration confirmation of the MPON.

The MPON and the MPOO perform the equipment acquisition and / or equipment changes.

The MPON informs the GO about the failure of the entire process or the MPON informs the GO about the successful completion of the entire process.

The GO informs the MPON about the failure of the overall transaction by deadline if after a maximum time limit no message of the MPON is present at the GO.

If the MPON informs the GO about the failure of the entire process , the GO confirms the failure of the assignment to the MPON.

If the MPON informs the GO about the successful completion of the overall process , the GO assigns the MPON.

The GO confirms the assignment to the MPON.

The GO informs the MPOO about the failure of the assignment of the MPON or the GO informs the MPOO about the assignment of the MPON.

The GO informs the MSPO about the failure of the assignment of the MPON or the GO informs the MSPO about the assignment of the MPON.

The GO informs the SP about the assignment of the MPON .
21 changes: 21 additions & 0 deletions examples/llm/PET/doc-10.3
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
The MPOO deregisters at the GO.

The GO verifies the deregistration.

The GO rejects the deregistration of the MPOO or the GO preliminarily confirms the deregistration of the MPOO.

The GO prepares the readmission of the measuring point.

Optionally , the GO may oblige the MPOO to continue the operations.

If the GO binds the MPOO to continue the operation , the MPOO confirmes the continuation to the MPOO.

The GO performs the equipment acquisition and / or equipment changes.

The GO assigns the GO as MPO.

The GO informs the MPOO about the end of the assignment of the MPOO and the beginning of the assignment of the GO.

The GO informs the MSPO about the assignment of the GO.

The GO informs the SP about the assignment of the GO .
17 changes: 17 additions & 0 deletions examples/llm/PET/doc-10.4
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
The MPON notifies the MPOO about equipment change intentions.

The MPOO announces self dismounting to the MPON or the MPOO shall notify the MPON about no self-dismounting of the MPOO.

The MPON or the MPOO perform the final reading.

The MPON or the MPOO dismount the old equipment.

The MPON mounts the new device.

The MPON reads the meter count from the installed meter.

The MPON sents the values of the final reading to the GO.

The MPON tells the GO about the device changes , the master data and the meter count at installation.

The GO shall notify the MSP about the device changes , the master data , the meter count at dismounting , and the meter count at installation .
7 changes: 7 additions & 0 deletions examples/llm/PET/doc-10.5
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
The MPON requests a device takeover bid of the MPOO.

The MPOO sends a tender for the equipment takeover to the MPON.

The MPON places an order at the MPOO.

The MPOO confirms the order of the MPON and sends the master data .
5 changes: 5 additions & 0 deletions examples/llm/PET/doc-10.6
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
The MSPN sents a dismissal to the MSPO.

The MSPO reviews the dismissal.

The MSPO rejects the dismissal of the MSPN or The MSPO confirms the dismissal of the MSPN .
13 changes: 13 additions & 0 deletions examples/llm/PET/doc-10.7
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
The MSPN registers the measurement at the GO.

The GO examines the application of the MSPN.

The GO rejects the application of the MSPN or the GO confirmes the application of the MSPN.

The GO assigns the MSPN.

The GO informs the MSPO about the assignment of MSPN.

The GO informs the MPO about the assignment of the MSPN.

The GO informs the SP about the assignment of MSPN .
13 changes: 13 additions & 0 deletions examples/llm/PET/doc-10.8
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
The MSPO deregisters at the GO.

The GO verifies the deregistration.

The GO rejects the deregistration of the MSPO or the GO preliminarily confirms the deregistration of the MSPO.

The GO assigns himself as MSP.

The GO informs the MSPO about the end of the assignment and the beginning of the assignment of the GO.

The GO informs the MPO about the assignment of the GO.

The GO informs the SP about the assignment of the GO .
9 changes: 9 additions & 0 deletions examples/llm/PET/doc-10.9
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
The SP / PU / GO request changes to the MPO or the MPO himself causes a change.

The MPO reviews the change request.

The MPO rejects the change of the measuring point by the SP / PU / GO or the MPO confirmes the request of the SP / PU / GO.

The MPO performs the measuring point change.

The MPO reports the implementation to the SP / PU / GO or notifies the SP / PU / GO about the failure of the changes .
79 changes: 79 additions & 0 deletions examples/llm/PET/doc-2.1
Original file line number Diff line number Diff line change
@@ -0,0 +1,79 @@
At the beginning the customer perceives that her subscribed service has degraded.

A list with all the problem parameters is then sent to the Customer Service department of TELECO.

At the customer service an employee enters ( based on the received data ) a problem report into system T.

. Then the problem report is compared to the customer SLA to identify what the extent and the details of the service degradation are.

Based on this , the necessary counter measures are determined including their respective priorities.

An electronic service then determines the significance of the customer based on information that has been collected during the history of the contractual relationship.

In case the customer is premium , the process will link to an extra problem fix process ( this process will not be detailed here ).

In case the customer is of certain significance which would affect the counter measures previously decided upon , the process goes back to re-prioritize these measures otherwise the process continues.

Taking together the information ( i.e.

contract commitment data + prioritized actions ) a detailed problem report is created.

The detailed problem report is then sent to Service Management.

Service Management deals on a first level with violations of quality in services that are provided to customers.

After receiving the detailed problem report , Service management investigates whether the problem is analyzable at the level of their department or whether the problem may be located at Resource Provisioning.

In case Service Management assesses the problem to be not analyzable by themselves , the detailed problem report is sent out to Resource Provisioning.

If Service Management is sure they can analyze it , they perform the analysis and based on the outcome they create a trouble report that indicates the type of problem.

After Resource Provisioning receives the detailed problem report , it is checked whether there are any possible problems.

If no problems are detected , a notification about the normal service execution is created.

If a problem is detected this will be analyzed by Resource Provisioning and a trouble report is created.

Either trouble report or the normal execution notification will be included in a status report and sent back to Service Management.

Service Management then prepares the final status report based on the received information.

Subsequently it has to be determined what counter measures should be taken depending on the information in the final status report.

Three alternative process paths may be taken.

For the case that no problem was detected at all , the actual service performance is sent back to the Customer Service.

For the case that minor corrective actions are required , Service Management will undertake corrective actions by themselves.

Subsequently , the problem resolution report is created and then sent out to Customer Service.

After sending , this process path of Service Management ends.

For the case that automatic resource restoration from Resource Provisioning is required , Service Management must create a request for automatic resource restoration.

This message is then sent to Resource Provisioning.

Resource Provisioning has been on-hold and waiting for a restoration request but this must happen within 2 days after the status report was sent out , otherwise Resource Provisioning terminates the process.

After the restoration request is received , all possible errors are tracked.

Based on the tracked errors , all necessary corrective actions are undertaken by Resource Provisioning.

Then a trouble-shooting report is created.

This report is sent out to Service Management ; then the process ends.

The trouble-shooting report is received by Service Management and this information goes then into the creation of the problem resolution report just as described for ii ).

Customer Service either receives the actual service performance ( if there was no problem ) or the problem resolution report.

Then , two concurrent activities are triggered , i.e.

i ) a report is created for the customer which details the current service performance and the resolution of the problem , and ii ) an SLA violation rebate is reported to Billing & Collections who will adjust the billing.

The report for the customer is sent out to her.

After all three activities are completed the process ends within Customer Service.

After the customer then receives the report about service performance and problem resolution from Customer Service , the process flow at the customer also ends .
Loading

0 comments on commit a6ba08e

Please sign in to comment.