This object represents any resource object that is not already described in SIF AU by an existing object (such as RoomInfo or LearningResource). It is intended for use with ResourceBooking, so it can represent any bookable resource; but it is not limited to that usage. While the obvious type of equipment described for booking purposes are things like computers and projectors, the types of equipment that can be booked depends on the educational organisation, and can easily extend to things like vehicles or animals.

Name of the equipment.

Description of the equipment.

The Local Id of the equipment.

Asset number of the equipment; may be distinct from Local Id.

The SIF RefId of the invoice for the equipment.

The SIF RefId of the purchase order for the equipment.

Type of equipment.

The SIF RefId of the owner/location of the equipment.

The type of SIF object that the SIF_RefId element identifies.

This object represents a booking for any resource for a single contiguous time period. This could be either a room or another resource, such as equipment.

The ID (GUID) of the resource being booked. Provided only if the resource being booked is a SIF object with a GUID.

The type of SIF object that the ResourceRefId element identifies.

The Local Id of the resource being booked. Provided whether the resource is a SIF object or not.

Starting date and time for booking.

Finish date and time for booking.

Starting period for booking. If specified, the booking is intended to align with bell times.

Finish period for booking. If specified, the booking is intended to align with bell times.

Indicates who booked the room. Points to a StaffPersonal record. This will normally (but not necessarily) be the teacher who will be occupying the room.

A free-text explanation of the reason for the room booking.

Links the room-booking to a ScheduledActivity.

If ScheduledActivity is provided, 'true' means the booker wishes to retain all rooms already specified for the ScheduledActivity. 'false' means that room(s)/resources are now available for other uses.

This object contains all of the information about a school's room. This object may contain a reference to a room type so that it may represent anything from a gym, cafeteria, to a standard classroom. The StaffList element usually contains the homeroom teacher.

GUID that identifies this room.

GUID that identifies the school that this room belongs to.

The locally assigned identifier for the room.

Room number as presented to the user/application. It is intended to be human readable and user-friendly corresponding to the physical label of the Room.

Friendly name that can be assigned to the room (e.g. Staff Cafeteria).

Extra building information. In the future Building could become its own object in which case this element will need to be changed to a RefId. Currently it is only required as a free text field.

When a room is designated as a homeroom it may have a different number. Usually blank when room is not a homeroom.

Size in square meters.

Number of persons (usually students) that this room can hold.

Phone number for the room

Type of room, for use in timetabling.

Is this Room available to be Timetabled?

This object provides a broader range of scheduled activities than just normal teaching classes (as covered by SessionInfo).

The ID (GUID) of the school for which this attendance information is being reported.

An optional Id (GUID) for the timetable cell that this activity is scheduled in. Instances of cyclical classroom sessions will have this element, but one-off events such as excursions will not use this element.

Day Id.

Period Id within the Day Id

The GUID of the TimeTable to which this Cell belongs

Date for which the activity is scheduled. This element is mandatory even if the object is used for preplanning excursions: a tentative or notional date and time should be provided if a finalised date is not available.

Starting time for activity. This element is mandatory even if the object is used for preplanning excursions: a tentative or notional date and time should be provided if a finalised date is not available.

Finish time for activity. This element is mandatory even if the object is used for preplanning excursions: a tentative or notional date and time should be provided if a finalised date is not available.

Type of Lesson/Session eg Teaching, Lunch etc.

Optional to link the GUID of the Subject, if this is a piece of curriculum being scheduled.

A listing of the teachers assigned to the activity, and the type of supervision they are credited with. If no teachers are listed, the activity is assumed to be unsupervised.

List of rooms in which the scheduled activity is held. Used for onsite venues which are represented in the source system as rooms. Can include large venues (ovals, library, etc), if they have been represented as rooms; source system practice varies.

The address(es) associated with the scheduled activity.

Text description of venue. Can be used for either onsite or offsite venues. Can be used if neither RoomList nor AddressList is appropriate or supported by the source system. (E.g. the venue is the oval, which is not represented as a room; the venue is a specific part of the park). If RoomList, AddressList, and Location conflict, the order of priority in interpreting the object is RoomList, then AddressList, then Location.

The type of activity undertaken.

This element is required if this is a one-off event, i.e. there is no TimeTableCellRefId provided, in order for excursions to be uniquely identified.

Allows free-text information, e.g. for excursions. Comment should not be used to identify the location of the venue, since the contents of Comment are open-ended.

Students who are scheduled to attend the event. Not required for cyclical events, as this would be expected to be provided from TimeTableCell/TeachingGroup instead.

Teaching groups which are scheduled to attend the event. Not required for cyclical events, as this would be expected to be provided from TimeTableCell/TeachingGroup instead.

List of year levels offered by the school.

This flag should be used to indicate whether or not this ScheduledActivity overrides a previous ScheduledActivity. In any initial provisioning this element should NOT be provided.

This object is for course information.

All local ids in non-authoritative objects are optional. It is therefore up to the provider and the actual agent's design and choreography to determine whether or not to use or local ids from parent objects. There are cases in some subscribing systems where it might not possible to add RefId columns and therefore the RefId of related objects cannot be stored. For example a target system that listens to TimeTableSubject events and updates them may not be able to store the associated SchoolCourseInfoRefId with that object. The only way it can link the TimeTableSubject object with the appropriate course might be through its local course id. Having local ids that link the parent objects with the child object can simplify the agent design. Generally it is suggested to use the appropriate RefIds whenever possible and only use local ids if there is no other way to use RefIds.

The ID (GUID) that uniquely identifies the school course.

The ID (GUID) that identifies the school where the course is offered.

The locally-assigned identifier for this school/campus.

School year for which the information is applicable, expressed as the four-digit year in which the school year ends (e.g. 2007).

The ID (GUID) that uniquely identifies this TermInfo (reportable time period). Either SchoolYear or TermInfoRefId must be provided.

School-defined local code for the course.

State-defined standard course code used to report information about courses.

The corresponding district course code.

Subject matter areas.

Title of the course.

Textual description of the course.

An indication of the general nature and difficulty of instruction provided.

The number of credits awarded upon course completion.

Does the course meet the state definition of a core academic course?

Does the state require that the course be completed for graduation?

Department with jurisdiction over this course.

Description of course content.

This object provides information about the section, the specific time period a session of the course meets. Australian Implementations have been using TeachingGroup as a representation of a class;

The Id (GUID) that uniquely identifies this section entity.

The Id (GUID) that identifies the course being taught in this section.

The locally-assigned identifier for this course section.

Description of the course section.

School year for which the information is applicable, expressed as the four-digit year in which the school year ends (e.g. 2013 for the 2013 school year). Either SchoolYear or TermInfoRefId must be provided.

The Id (GUID) of the term to which this schedule information relates. Either TermInfoRefId or SchoolYear must be provided.

Medium through which the student receives instructional communication from the teacher.

Language in which the section is taught.

Description of the location in which the section is taught.

Is this a summer school assignment?

Optional overrides of the course information for this section.

A section code that is linked to a course. This should be a unique identifier within the school year and course (i.e. the class instance number for a course). For example, Algebra I: Section 23 is different from English II: Section 23.

A unique identifier of the section for the school year and across courses (i.e. unique across all courses). For example, Algebra I sections range from 00122 to 00140 and English II courses range from 00141 to 00152.

Indicates if attendance in this section is collected and used in attendance calculations.

This object contains information about a student's enrollment in a section of a course.

The Id (GUID) that uniquely identifies this StudentSectionEnrollment entity.

The Id (GUID) of the student to whom the enrollment information applies.

The Id (GUID) of the section in which this student is enrolled.

School year for which the information is applicable, expressed as the four-digit year. e.g. 2013

Date from when this course section enrollment is valid.

The last school calendar day (membership day) the student was enrolled in the course section (inclusive).

This object identifies a particular Teaching Group or class in a particular a time table.

The proposed object is based on the UK B1: TeachingGroup object. For the Australian object, a subject being taught at any one year level can have more than one teaching group in any one time table. Also a teaching group can be brought together for more than one subject.

All local ids in non-authoritative objects are optional. It is therefore up to the provider and the actual agent's design and choreography to determine whether or not to use or local ids from parent objects. There are cases in some subscribing systems where it might not possible to add RefId columns and therefore the RefId of related objects cannot be stored. For example a target system that listens to TimeTableSubject events and updates them may not be able to store the associated SchoolCourseInfoRefId with that object. The only way it can link the TimeTableSubject object with the appropriate course might be through its local course id. Having local ids that link the parent objects with the child object can simplify the agent design. Generally it is suggested to use the appropriate RefIds whenever possible and only use local ids if there is no other way to use RefIds.

The GUID of the TeachingGroup

School year for which the information is applicable, expressed as the four-digit year in which the school year ends (e.g., "2007").

LocalId of the Teaching Group (previously ClassIndicator).

Short free format label that describes the group.

Longer description if required.

Added to allow local implementations to filter on categories of Teaching Group. Where there is a need to filter particular groups based on their types for particular functions; group type provides the means of identifying the type of group such as roll class or subject class for instance and treat them accordingly.

Set Number (UK)

Block (UK)

Assessment Stage eg VELS Level

GUID of SchoolInfo object this teaching group belongs to.

Local School Id.

GUID of SchoolCourseInfo object this teaching group is part of.

Local Course Id.

GUID of TimeTableSubject object this teaching group belongs to.

Local subject Id.

Semester, Term, or Quarter subject offered.

List of Students in this Teaching Group

A List of teachers associated with the group - may or may not include the teacher timetabled in the schedule.

Minimum class size.

Maximum class size

A List of schedule information that can be published by an SIS which is a subset of information available in the TimeTableCell object.

PeriodId or StartTime must be provided.

The purpose of this object is to define a schedule or Time Table structure/skeleton for the school. The Time Table is produced by the Time Tabling software. Once the Time Table is produced, the time tabling software creates the schedule based on business rules and constraints to fit into the time table structure.

The proposed Time Table object is based on a combination of the proposed UK B6 – Timetable Cycle Object and Timetable Scope Object.

The Time Table is identified uniquely in the SIF Zone by its GUID, School and School Year. A Time Table is linked to a particular school.

All local ids in non-authoritative objects are optional. It is therefore up to the provider and the actual agent's design and choreography to determine whether or not to use or local ids from parent objects. There are cases in some subscribing systems where it might not possible to add RefId columns and therefore the RefId of related objects cannot be stored. For example a target system that listens to TimeTableSubject events and updates them may not be able to store the associated SchoolCourseInfoRefId with that object. The only way it can link the TimeTableSubject object with the appropriate course might be through its local course id. Having local ids that link the parent objects with the child object can simplify the agent design. Generally it is suggested to use the appropriate RefIds whenever possible and only use local ids if there is no other way to use RefIds.

GUID that identifies this TimeTable object.

Optional, the GUID of the SchoolInfo Object if this object is known in the zone.

School year for which the information is applicable, expressed as the four-digit year in which the school year ends (e.g., "2007").

Local TimeTable ID

Unique Name of the proposed Time Table

Max Number of days per Time Table cycle

Max Number of periods per Time Table Day

Teaching periods per day if different to PeriodsPerDay

Optional Local School Id

The school name in plain text.

Date Schedule was created or last edited.

First day of TimeTable.

Last day of the TimeTable.

Container for TimeTableDays in Schedule

The purpose of this object is to identify a specific cell within a particular TimeTable. A time table is a structure that represents all the available days and times (periods) for which a particular teaching group, or subject can be scheduled.

A TimeTableCell is uniquely identified in the ZIF zone by its GUID.

And the following must be provided at object creation:

• the timetable it belongs to,
• the subject that is being scheduled,
• the teaching group (representing the students, teachers and subject),
• the room that is allocated,
• the allocated teacher.

All local ids in non-authoritative objects are optional. It is therefore up to the provider and the actual agent's design and choreography to determine whether or not to use or local ids from parent objects. There are cases in some subscribing systems where it might not possible to add RefId columns and therefore the RefId of related objects cannot be stored. For example a target system that listens to TimeTableSubject events and updates them may not be able to store the associated SchoolCourseInfoRefId with that object. The only way it can link the TimeTableSubject object with the appropriate course might be through its local course id. Having local ids that link the parent objects with the child object can simplify the agent design. Generally it is suggested to use the appropriate RefIds whenever possible and only use local ids if there is no other way to use RefIds.

The GUID of the TimeTableCell

The GUID of the TimeTable to which this Cell belongs

The GUID of the Subject that this Cell is scheduling

The GUID of the TeachingGroup being scheduled

The GUID of the Resource being Scheduled

The GUID of the Staff Member being Scheduled

Time Table Local Identifier

Subject Local Id

Teaching Group

Room number as presented to the user/application.

Staff LocalId

Day Id

Period Id within the Day Id

Type of Lesson/Session eg Teaching, Lunch etc

Optional, the GUID of the SchoolInfo Object if this object is known in the zone

Optional, Local School Id

A listing of the teachers assigned to the activity, and the type of supervision they are credited with. If no teachers are listed, the activity is assumed to be unsupervised.

List of rooms in which the scheduled activity is held. Used for onsite venues which are represented in the source system as rooms. Can include large venues (ovals, library, etc), if they have been represented as rooms; source system practice varies.

This purpose of this object is to define and communicate the subject or distinct piece of curriculum that needs to be scheduled by the time table generator. This is a new object proposed to meet SIF-AU needs. Reviews of the existing specifications identified two relevant objects - SchoolCourseInfo, defined in SIF US 2.2 specification and SchoolGroup, defined within the SIF UK 1.1 specification. These objects appear to have some similar context but seem overly complex considering that Australian requirements, which are limited to the Student Administration System or Curriculum Delivery System providing base information to the Time Tabling application about what curriculum offerings are being proposed. When this data is sent in a Request/Response only those subjects that are relevant to be scheduled (or active), should be sent to the TimeTabling application.

All local ids in non-authoritative objects are optional. It is therefore up to the provider and the actual agent's design and choreography to determine whether or not to use or local ids from parent objects. There are cases in some subscribing systems where it might not possible to add RefId columns and therefore the RefId of related objects cannot be stored. For example a target system that listens to TimeTableSubject events and updates them may not be able to store the associated SchoolCourseInfoRefId with that object. The only way it can link the TimeTableSubject object with the appropriate course might be through its local course id. Having local ids that link the parent objects with the child object can simplify the agent design. Generally it is suggested to use the appropriate RefIds whenever possible and only use local ids if there is no other way to use RefIds.

GUID that identifies this TimeTableSubject.

SubjectLocalID - Distinct piece of curriculum that is to be scheduled.

Subject Year Level. Either AcademicYear or AcademicYearRange must be provided.

Range of Academic Years subject spans. Either AcademicYear or AcademicYearRange must be provided.

Local Course Id, if associated with a Course.

The GUID of the SchoolCourseInfo object.

Faculty

SubjectShortName

SubjectLongName

Core or Elective or ?

Suggested maximum class size for this subject.

Suggested minimum class size for this subject.

Optional the GUID of the SchoolInfo Object if this object is known in the zone.

Optional Local School Id

Semester, Term, or Quarter subject offered.

School year for which the information is applicable, expressed as the four-digit year in which the school year ends (e.g., "2007").