Difference between revisions of "Notice time"
Jump to navigation
Jump to search
| Line 8: | Line 8: | ||
|[[NTCHRS]]||noticeTimeHours||0..*||1 | |[[NTCHRS]]||noticeTimeHours||0..*||1 | ||
|- | |- | ||
| − | |[[NTCTXT]]||noticeTimeText||0.. | + | |[[NTCTXT]]||noticeTimeText||0..1||n/a |
|- | |- | ||
| − | |[[OPERAT]]||operation||0.. | + | |[[OPERAT]]||operation||0..1||n/a |
|} | |} | ||
That enabled us to model constructions like:<br> | That enabled us to model constructions like:<br> | ||
| − | Notice is required 24 hrs in advance or when leaving the previous port | + | Notice is required 48, 24, 6 hrs in advance or when leaving the previous port whichever is less.<br> |
| + | A further instance can be: Confirmation 2 hrs before arriving the xx-position.<br> | ||
| + | If notice time requires more than one instance it has to be defined in the ProdSpec. | ||
Revision as of 07:40, 30 October 2009
jens 09:54, 25 October 2009 (UTC) Notice time can become a complex attribute using the operation idea Raphael proposed and which is been used at Under Keel clearance. The construction can be like to following
| Sub-attribute | Camel Code Identifier | multiplicity | sequential |
|---|---|---|---|
| NTCHRS | noticeTimeHours | 0..* | 1 |
| NTCTXT | noticeTimeText | 0..1 | n/a |
| OPERAT | operation | 0..1 | n/a |
That enabled us to model constructions like:
Notice is required 48, 24, 6 hrs in advance or when leaving the previous port whichever is less.
A further instance can be: Confirmation 2 hrs before arriving the xx-position.
If notice time requires more than one instance it has to be defined in the ProdSpec.