!-------------------------------BEGIN ADD---------------------------------
!An ADD file has declarations, derived type definitions, etc. to be included at...
!the top of the Client Module, followed by CONTAINS statement and then all of ...
!the procedures developed by the analyst to include in the Client Module of a ...
!given model.
!-----
!Insert model-level declarations here, if any
CHARACTER(len=25),DIMENSION(0:20,2):: strResults
!-----
CONTAINS !the following procedures...
!-----
!Insert procedures here, if any

FUNCTION dblfSignalDelay(bigCustomer)
INTEGER(KIND=big):: bigCustomer
REAL(KIND=dbl):: dblfSignalDelay !When procedure is a function, its type should be declared
!-----
!strResults is a model level array; and this function is a model level procedure...
!Since this function is hosted in the Client Module and strResults is declared...
!at the top of Client Module, strResults is available to this function through...
!"host association." It is also available to the calling network object through...
!host association, because all network object subroutines are housed in Client...
!Module, too.
!-----
!The following have no real-world meaning. They are just numbers.

&B.Customer = bigCustomer !Just to demonstrate the use of ORMSware notation in ADD file

!Also, since system, global, customer and surrogate properties are components ...
!of data structures, they cannot be used as dummy arguments in subroutine and...
!function statements. That is why we used bigCustomer as dummy argument in Func statement
!-----
!Internal reading of a number from a character variable (strResults array)...

READ ( strResults(&B.Customer,1), * ) dblfSignalDelay !Value of number of pieces per hour

!-----
!Since ORMSware notation in ADD file is translated just as the contents of NET...
!file are, we can use all of the notations permitted in NET file here as well

END FUNCTION dblfSignalDelay
!--------------------------------END ADD----------------------------------