Decision in T 172/03 - Order management/RICOH

1. The appeal complies with the requirements of Articles 106 to 108 and Rules 1(1) and 64 EPC and is thus admissible.
2. The appeal, however, is not allowable since the claims now under consideration do not meet the requirements of the EPC.

   Indeed, it is sufficient to look at the respective claim 1 only, although there are a number of independent claims, since in all three requests the first claim already falls short of meeting the requirement of inventive step in respect of Articles 52(1) and 56 EPC.

   Inventive step: relevant case law and practice of the EPO

3. According to the case law and practice of the EPO, the patentability of an invention, for which inventive step is a requirement, must arise from features and aspects of the invention from which a technical solution to a technical problem can be inferred and which are thus of a technical character (see, for example, the PBS-decision (T 931/95 - Controlling pension benefits system/PBS PARTNERSHIP) and the COMVIK decision (T 641/00 - Two identities/COMVIK, OJ EPO 2003, 352), points 2 and 3, respectively).

   In the case of a mixed-type invention (including nontechnical aspects), examination for patentability normally requires an analysis of the invention and the construction of the claims to determine the technical content of the claims as a prerequisite step (see, in respect of inventive step, the COMVIK and PBS decisions, points 7 and 8, respectively). The required analysis of claim features is possible only ex post facto, i.e. in knowledge of the patent application and the invention to which it relates.

4. The appellant objected to the application of the principles of the PBS decision to the present case, essentially arguing that the examination approach in this decision was based on a fictitious kind of prior art and unlawful ex post facto considerations, with the illegitimate result that technical and mixed-type inventions were treated differently.
5. As already indicated in point 7 of the COMVIK decision, however, the prerequisite step of determining the technical features and aspects of a mixed-type invention is not part of the prior art analysis. Certainly, an ex post facto knowledge of the patent application and the claimed invention cannot be avoided completely in judging inventive step; what should strictly be avoided are retrospective considerations and conclusions in evaluating the technical contribution the invention provides to the relevant prior art (see decision T 967/97 – Chipkarte/OVD KINEGRAM AG, not published in OJ EPO, point 3.3).
6. Turning now to the meaning to be given to the term “person skilled in the art” of Article 56 EPC. According to the decision under appeal this term refers, in the present case, to a computer science expert, a programmer and a business expert, a view which is not in compliance with the case law of the Board. According to the COMVIK decision, point 8, the “skilled person will be an expert in a technical field”. The decision goes on to state: “If the technical problem is concerned with a computer implementation of a business, actuarial or accountancy system, the skilled person will be someone skilled in data processing, and not merely a businessman, actuary or accountant.”
7. Indeed, Article 18 EPC determines that an examining division in principle consists of three technically qualified examiners. The examining division is thus, due to its composition, neither professionally competent to evaluate the state of “non-technological art” nor to assess innovations in a non-technological field. It would be inconsistent with the terms and objects of the EPC to attribute an essentially different professional competence to the “person skilled in the art” within the meaning of Article 56 EPC, for example by construing this term to include business experts or practitioners in other non-technological fields. Even if there may be borderline areas, like system analysis and design which are based on rather abstract and intellectual activities but nevertheless provide important results for developing complex software systems (see decision T 49/99Information modelling/INTERNATIONAL COMPUTERS, not published in OJ EPO, point 7), this should not divert from the principle that the skilled person within the meaning of Article 56 EPC is a technical expert, professional or practitioner.
8. Finally, the decision under appeal (see point 1.1 of the reasons) identifies the closest prior art as “the existing order placing mechanism” as if such a business scheme qualified as prior art as any other piece of technical information. The appellant apparently shares this view, at least regarding the identification of the closest prior art.

   However, as explained in the COMVIK decision, point 2, the term “state of the art” in Article 54 EPC should, in compliance with the French and German text, be understood as “state of technology”, which in the context of the EPC does not include the state of the art in commerce and business methods.

9. The term “state of the art” should be interpreted in its legal context, and in the light of the object and purpose of the patentability requirements of the EPC. It can hardly be assumed that the EPC envisaged the notional person skilled in the (technological) art to take notice of everything, in all fields of human culture and regardless of its informational character. A consistent construction of the patentability provisions requires the term “everything” in Article 54(2) EPC to be understood as concerning such kind of information which is relevant to some field of technology.
10. From these considerations it follows that anything which is not related to any technological field or field from which, because of its informational character, a skilled person would expect to derive any technically relevant information, does not belong to the state of the art to be considered in the context of Articles 54 and 56, even if it had been made available to the general public before the relevant priority date. Prerequisite examination concerning technical character
11. All three requests relate to an order management and office system which serves to control and satisfy the inventory needs of business and other kinds of administrative entities (see the published application, in particular column 1, lines 16 to 42). Therefore, in the present case it is expedient to analyse first the technical character of the claim features before approaching the inventive step requirement. As has been shown above, the starting point and the basis of the invention is an order management method which as such is missing any technical character. Therefore, it is appropriate to identify first the claim features which define this non-technological part of the invention. The required claim construction has to take into account that terms like system, unit or means do per se not have any technical connotation. They may simply define business units or methods, but they may nevertheless, at the same time, refer to corresponding technical components of the system.
12. The purely business-related aspects in claim 1 (of all requests), are considered to be displayed in the following claim features:

    For placing an order with one of a plurality of suppliers, the order management system comprises a central management unit for receiving the order information from one of a plurality of (business) sections identifiable by a section code; an order information including a section code of the orderer, said central management unit including:

    (a) collection processing means for

    • managing, with respect to each orderer, order history information and section information and
    • calculating a momentary sum on the basis of a total cost of the previous orders of a section based on the order history information of one of the orderers sending the order information including the section code of this orderer and of order information sent from said one of said orderers; and

    (b) order permission means for permitting execution of an ordering process when the momentary sum is within a budget of the section of the orderer;

    wherein said order management system ensures appropriate book-keeping, the business records including a section master file comprising said order history information and said section information for each section including a section code and a budget of each section, and said collection processing means places said order when said order information is input by said one of a plurality of orders if the ordering process is permitted by said permission means.

13. Having regard to the technical features of the claimed invention, it may first be recalled that a computer system suitably programmed to perform or support a business activity has technical character (see the PBS decision, point 5). The same holds, in the context of inventive step, for features and aspects of the system which ensure that the computer system provides some useful function, irrespective of the purpose and the use of the function.
14. Claims 1 of all three requests define a distributed computer system comprising terminal units A-N, a communication network 6, a table-oriented database system 82 and a computer system 7, 76, 82, all components linked via the communication network for collecting, transmitting and processing data.
15. As explained in the application, the computer system 7, 76, 82 may consist of multiple general purpose computers at different locations (departments), properly programmed and set up (see for example the published application, column 4, lines 8 to 13, column 5, lines 12 to 16, and lines 34 to 45, and column 10, lines 39 to 48).

    According to the application, therefore, the order management method can be implemented on a normal office information system by using standard hardware components, without essentially changing the network structure of the system. The claims encompass embodiments where the claiming of various units and functions for performing the order activities and transactions has no technical meaning or implications but serves merely definitional purposes. In such embodiments, the functions and data structures are implemented essentially by software programming.

    Inventive step: considerations common to all requests

    The relevant person skilled in the art

16. For the software implementation of an information system, normally a software project team is responsible, typically consisting of programmers. The Board thus considers appropriate to define, in the present case, the relevant “person skilled in the art” within the meaning of Article 56 EPC as such a software project team. For the reasons given above, it does not include any business expert, but it has knowledge of the business-related features and aspects of the order management method, in the kind of a requirements specification, as part of the formulation of the technical problem to be solved.

    The closest prior art

17. An invention lacks an inventive step if the skilled person, starting from some point in the prior art (the “closest prior art”), would consider to follow a “solution path” which leads him to the claimed invention (see the Chipkarte decision, catchword II).
18. Having regard to the rather few technical aspects and structural elements claimed for the invention, the closest prior art appears to be a distributed information system comprising multiple general purpose computers at different locations and connected by a communication network as known and in use in a vast number of companies for office automation well before the priority year 1995. Such a distributed information system and its use for office automation form part of the common general knowledge as can, for instance, be seen from the prior art referred to by the appellant; the existence of such kind of system before the priority date of the application does not require further evidence.

    Main request

    The distinguishing features

19. The claimed invention is distinguished therefrom by functional features and data structures for implementing the essentially business-related aspects and features of the order management method.

    The technical problem

20. Providing an implementation of a business-related method on a computer system is basically a technical problem, appropriate for use with the problem and solution approach for assessing inventive step. As stated in the COMVIK decision, point 7, it is legitimate to include the non-technical aspects and features of the invention, i.e. in the present case the business-related features of the order management, into the formulation of the technical problem. From the point of view of the relevant person skilled in the art, the task of programming an office information system or of implementing commercial features on such a system is per se a normal and obvious aim.

    The technical contribution to the prior art

21. Considering an embodiment on the basis of a pure software implementation of the order management method using standard PC and hardware components, it is clear that claim 1 (main request) defines technical subject-matter (functions, data structures etc.) which distinguishes such an embodiment from a normal distributed information system only in terms of the business-related processes and data of the order management method.

    These technical features of the implementation, however, follow directly from the requirements specification concerning the order management method. The claimed technical solution does not go beyond the concept of a mere automation of constraints imposed by the business-related aspects. Such automation using conventional hardware and programming methods must be considered obvious to a skilled person.

22. The Board does not see any other technically relevant subject-matter which may have to be taken into account. The appellant argued that by centralizing the ordering process the network load was reduced. Claim 1 indeed does define a centralisation but of the order management, not of the computer system. The “central management unit” might rather be a distributed computer system producing an important overhead of data traffic. In addition, saving time or energy, reducing traffic load etc. by applying purely administrative or business solutions do not confer a technical character to such solutions and are thus in any case not relevant to the issue.

    Hence, claim 1 of the main request is not allowable (Article 56 EPC).

    Auxiliary request 1

23. Turning to the auxiliary requests, claim 1 of the first auxiliary request includes the subject-matter claimed in the second auxiliary request. Lack of inventive step in the second thus entails, novelty given, the very same deficiency in the first auxiliary request, rendering it sufficient to consider inventive step in respect of claim 1 of the second auxiliary request only.

    Auxiliary request 2

    The distinguishing features

24. The second auxiliary request on the one hand expands the order management concept as defined according to the main request, and on the other hand defines the “order management system” itself in a subtly different manner, namely now as an “office system” with order management for a company or office comprising a plurality of terminal units with personal computers and copy machines and/or facsimile apparatus. It further defines a “system environment” having a plurality of sections in which the terminal units are located corresponding to sections of the company or office. In this system environment, the order placement is performed (the “orders ordering copy papers and/or toner cartridges”).
25. The extended order management concept according to the second auxiliary request encompasses following additional features:

    An item master file is provided which indicates the item information for the items to be ordered by each department or section so as to determine whether or not the product or item name included in the received order information corresponds to one of the registered item names to which an order can be placed. For each order, an item name and in addition an information (the “order condition”) as to whether the supplier is selected on a price priority basis or a supplier priority basis are provided. The item master file is searched so as to determine whether or not the item name included in the received order information corresponds to one of the registered item names to which an order can be placed;

    • if it is determined by the order manager that the item name corresponds to none of the registered item names, an error message is sent to the orderer, which error message indicates that the input item name does not correspond to the registered item name which can be ordered;
    • if it is determined that the input item name corresponds to one of the registered item names, the input item name is compared with the item name in the item master file to find the item name corresponding to the input item name;
    • when the corresponding item name is found, the item name, an item code, a unit price and a supplier code are read and stored in an item table file, respectively;
    • an order priority of a supplier master file is read based on the supplier code and the order priority is stored in the item table file;
    • the order condition received is checked whether the selection of the supplier should be made according to the price priority basis or the supplier priority basis,

      and

    • the item table file is sorted accordingly.
26. Furthermore, according to claim 1, the order costs are calculated by multiplying the unit price read in the item table file and the amount of order included in the order information;
    • a sum of the order costs for the department or section which places the order at this time is calculated by searching the section master file based on the section code of the terminal unit included in the order information, said calculation being formed by adding the order costs at this time to the total cost of orders corresponding to the section code;
    • when the summed cost of the previously ordered supplies exceeds the budget of the department or section, an error message is sent to the orderer, wherein the supplier selecting unit calculates a total cost of received orders for each of said suppliers based on the order history information, the order information and the produced item table and one of said suppliers whose total cost of received orders is within an order limit is selected.
27. The technical problem of the implementation of such a order management concept on a computerized office system is solved, as follows from the claim wording, by providing appropriate table constructs for holding the product, supplier and other accounting data and appropriate computing units for performing the necessary order processes automatically.
28. As indicated in the decision T 49/99-Information modelling/INTERNATIONAL COMPUTERS cited above, modelling a physical system as a step in developing a corresponding software system does not provide a technical contribution, if it is not exceptionally part of a technical solution to a technical problem. The organization of the computer data in direct correspondence to the business data and an algorithm merely reflecting the business processes and transactions are part of the abstract modelling of the order management method. The various ordering steps and the organisation and content of the various files according to this auxiliary request do not serve any technical purpose and are thus considered to form part of the non-technical aspects of the invention.

    The technical features of the invention

29. Undoubtedly, there are also technical aspects involved. These are first those claim features which only define a direct carry over of the abstract model to software features, which is considered as a routine work within the professional realm of a software project team.
30. The data construct “item table file” and the steps using it for selecting the supplier make a difference since for this file there seems not to exist any direct counterpart in the form of a collection or an item of business data already present within the order management concept.
31. Therefore, the Board considers technical aspects involved in the following claim definitions:

    the order management system is configured to perform automatically …

    • when the corresponding item name is found, the item name, an item code, a unit price and a supplier code are read and stored in an item table file, respectively;
    • an order priority of a supplier master file is read based on the supplier code and the order priority is stored in the item table file;
    • the supplier selecting unit checks the order condition received from the terminal unit whether the selection of the supplier should be made according to the price priority basis or the supplier priority basis;
    • if the price priority basis is selected, the item table file is sorted according to a lower price order;
    • if there are more than two suppliers having the same price, they are sorted by the order priority basis;
    • if the supplier priority basis is selected by the order condition, the item table file is sorted according to the order priority basis

    As follows from the patent application (see, for example, Figures 8 and 9, steps S5 and S6, with the accompanying parts of the text), the item table file is a temporary data construct for storing the intermediate results of the order processing and for selecting the supplier according to a predetermined priority scheme, giving preference either to the price or to a predefined order priority of the supplier. The concrete meaning of the data stored in the item table results directly from the business-related data used with the order management method and does thus not have any technical relevance.

    The technical contribution to the prior art

32. The technical problem to which the item table file and the related process steps form the solution is the automatic production of particular output data the meaning of which, at the business level, is to indicate an appropriate supplier of the item to be purchased under the constraint of the order priority chosen.

33. The same problem is addressed in document D2, for example on page 2, lines 4 to 9, page 3, lines 7 to 11, and page 8, lines 5 to 15.

34. The solution proposed in document D2 (see pages 20 to 25 with Tables IV and V) is a table construct listing the item code (part number), the unit price (COST and U/I), and the supplier code (SPLR). The table may permit order entry from the screen on which the table is displayed (see page 25, first paragraph).

35. This renders obvious the technical idea to produce a temporary list in table format displaying in a row the relevant business data concerning item, supplier and price which allow to select the best price or supplier. Which additional data are displayed, as for example item name and order priority, is a question of the order management method and has no technical relevance.

36. Finally, sorting as claimed is a standard function for this type of table-oriented data processing, and does thus not involve any additional aspects relevant to inventive step.

37. In summary, the technical contribution provided by the claimed invention to the prior art is to be considered obvious so that neither one of auxiliary requests 1 and 2 complies with the requirement of inventive step as set out in Article 56 EPC.