That is a tricky question. :) Drools 4 has no special semantics for date and time, and so, the only date and time you can get is the Java date/time, and for that you need to use an eval() to call a function (or API) to return current date and time: eval( currentDateFunction() == $someOtherDate ) Drools 5, on the other hand, has the concept of session clock, as part of the incoming support for events. The session clock can be used to write rules against it, as well as add temporal constrainst to events. For instance: $aPhoneCall : PhoneCall( ) $anotherCall : PhoneCall( this after[10,60] $aPhoneCall ) The above constraint will be true, when $anotherCall happens 10 to 60 time units after $aPhoneCall. But when did the calls occurred? that is determined by the clock abstraction chosen for the given session, that may be either a system synchronized clock, as well as a pseudo-clock implementation (that enables session re-executions and scenario simulations), or an externally stamped timestamp (that keeps the events timestamps frozen), etc. It will also allow for the explicit definition of time windows (see our presentation at JBoss World, etc). All the above, just to tell you all users that time is not a simple concept to support. Drools 4 didn't tried to do it, but Drools 5 will bring some interesting modeling power to the table. Edson 2008/5/7 Christine <christine(a)christine.nl&gt;: -- Edson Tirelli JBoss Drools Core Development Office: +55 11 3529-6000 Mobile: +55 11 9287-5646 JBoss, a division of Red Hat @ www.jboss.com