ROLE DEFINITIONS. Characteristics of People Employed at SPCA: Our People's Role
ROLE DEFINITIONS. Add: For the purposes of this agreement the roles covered are defined as below, regardless of the titles used by individual employers.
1. OOHMA is an abbreviation of Out of Hours Music and Art. A person employed to coordinate a programme of community education courses or out of hours music and art run by a board or boards of trustees of a state or integrated school or schools is an ACE Coordinator. (Coordinator) is. • A Teaching Coordinator is a coordinator, who either: o is employed concurrently as a teacher within the same school under the terms of the applicable teacher’s collective agreement, or o no longer teach classes within the school BUT was previously employed as a teaching coordinator within that school and continues as a coordinator even though they. • A Non-teaching Coordinator is a coordinator who is not a teaching coordinator and is graded either One, Two or Three, defined as follows. • Grade One: a position where the primary role is to administers and coordinates the community education/OOHMA programme on a day-to-day basis. • Grade Two: in addition to the grade one duties this position has a strategic focus including significant community liaison and marketing and may include professional leadership. • Grade Three: this is a position which, in addition to the Grade Two duties and responsibilities, would involves: • professional leadership in the development of ACE or OOHMA networks; and • identifying and meeting wider community needs; and • responsibility for the professional development of tutors and others within the ACE or OOHMA sector.
2. A person employed to assist the Coordinator and whose duties include the assessment of, coaching of, and providing guidance to, tutors is a Professional Supervisor. is.
3. A person employed to assist the Coordinator and whose duties do not include the assessment of, coaching of, and providing guidance to, tutors is a Coordinator Assistant is.
4. A person employed by the board of trustees of a state or integrated school to instruct a class or a course conducted as part of an ACE or OOHMA programme is a Tutor.
2. CPI adjustment to all ACE rates/allowances (and extending coverage of these rates to OOHMA)
ROLE DEFINITIONS. The following table defines the roles that take part in the SESAMO process’ activities.
ROLE DEFINITIONS. For the purposes of this agreement the roles covered are defined as below, regardless of the titles used by individual employers. A Coordinator is a person employed to coordinate a programme of community education courses or out of hours music and art run by a school board or boards of a state or state integrated school or schools. A Teaching Coordinator is a coordinator, who either: ▪ is employed concurrently as a teacher within the same school under the terms of the applicable teacher’s collective agreement, or ▪ was previously employed as a teaching coordinator within that school and continues as a coordinator even though they no longer teach classes within the school.
A Non-teaching Coordinator is a coordinator who is not a teaching coordinator and is graded as follows. • Grade One: administers and coordinates the community education/OOHMA programme on a day-to-day basis. • Grade Two: in addition to the Grade One duties has a strategic focus including significant community liaison and marketing, and may include professional leadership. • Grade Three: in addition to the Grade Two duties and responsibilities, involves: - professional leadership in the development of ACE or OOHMA networks; and - identifying and meeting wider community needs; and - responsibility for the professional development of tutors and others within the ACE or OOHMA sector. A Professional Supervisor assists the coordinator and their duties include the assessment of, coaching of, and providing guidance to tutors. A Coordinator Assistant assists the coordinator and their duties do not include the assessment of, coaching of, and providing guidance to tutors. A Tutor instructs a class or a course which is part of an ACE or OOHMA programme.
ROLE DEFINITIONS. A TPA may be between specific parties or between some combination of specific parties and arbitrary parties (roles). The <Role> tag defines the relationships between roles and actual parties. It is optional and should be omitted if roles are not used. A TPA containing one or more roles is referred to as a prototype TPA or a reusable TPA. The resulting TPA, with the roles replaced by specific parties, is called a fully qualified TPA. The syntax of the role definition section is: <Role> <RoleDefn> <!--one or more--> <RoleName>role_name</RoleName> <!--example: hotel, airline --> <RolePlayer>player_name</RolePlayer> <!--example: Hotelco, Airlineco--> </RoleDefn> </Role> In a prototype TPA, the value of <RolePlayer> may be null, blank, or an arbitrary character string. This must be replaced by an actual party name when a party is assigned to a role. An arbitrary party is referred to as a role and is denoted by a role parameter. The <RoleName> tag defines role parameters. Any alphanumeric string may be used as a role parameter. This string is case sensitive and must be written the same way wherever it appears in the TPA. The actual party name is given in the associated <RolePlayer> tag. It is case sensitive. A specific party must be assigned to play each unfilled role during the instantiation of a TPA from a prototype TPA. To identify a specific party to play a role, the role parameter must be replaced by the actual party's organization name. Role parameters are used in the <PartyName> tags. In these tags, the role parameter must be preceded by @. For example, where the role parameter is airline: <PartyName Partyname="_airline">@airline</PartyName> NOTE: The @ has been chosen as the designator since it is one of the few special characters that have no significance to XML. The leading underscore on the value of PartyName is to satisfy an XML requirement that ID attributes must not begin with numeric characters. Adding the underscore allows for party names such as 3COM and 3M. The <OrgName> tag identifies the parties in other places in the TPA. The identification is via the Partyname attribute. See "Party Names and Reference Attributes". In addition, party-dependent tags must be given the appropriate values. In general, these tags are in a subtree below the tag of which <OrgName> is a subelement. For example, when the value of <PartyName> is converted from a role parameter to an actual party name, most tags under <Member> must be given party-specific values. The <...
