In N-OC, the user can set up receivers in Automation Factory for various types of messages, They are divided into the following groups: | Users: | These are users of the N-OC system, with certain rights, they are defined in the user table, and can have email, mobile, type B etc for communication. | Facilities: | These are connected to airports and can have various user definable attributes connected to them. For example: Handling Agents, Police, Tower, Hotel, Fuel can be defined as a Facility Type, and then added to each Station. The user can then connect attributes to it (email, phone, open times, radio freq, payment type etc). These are also defined by the airline. | Companies: | These are companies the airline works with (not a user or connected to an airport). For example, they could be an airline, tour operator, authority, bank etc. For each defined company, the user can add contacts (type of contact, email address, type B, etc). | Free Addressees: | These are none of above, if the user does not want to connect to anything above, but rather define a Type B or email address which has no direct relation with any of the above. For example it could be the CEO's grandmother contact details. | These four types may all be used when setting up receivers for messages sent from N-OC. N-OC Events are designed to be very flexible, due to this flexibility you have to create events for e.g. each "SITA message type" and link the event to each station. It can seem as a lot work, but in the end it allow you to pin point a message to the exact receiver, and hopefully save money to you company because of lower message fee. Adding receiver addresses to events. To set up receivers for events in N-OC, please follow the guide below. Open Automation Factory | | Select the Events tab. The events are grouped as shown. This picture is only a selection of the available options | | Click on NEW to create a new receiver Select the event the system should generate an output on. The datatype is mandatory to choose what data the output should include Filter can be applied to the event only trigger on selected criteria STATION can be used instead of filter. Bounce message for: This can be use if you e.g. want a copy of outgoing SITA message to yourself without sending it out and back, the advance is that you don't pay for the message. The new Event will placed in one of the folders depending on which Event type you select. | | Visible to user When this option is ticked the message will be visible in the message dialog. The purpose of this option is to make sure that messages always are send. | | | Folder | Event | Data Type | System | Template | Comment | ACARS | ACARSMessageUplink | ACARS Message Uplink | Vehicle List | OwnMessage | Integration | | | | | | | | ASM | AdHoc | ASM | Schedule | SystemMessage | | | AdHoc Acknowledge | ASM ACK | Schedule | SystemMessage | | | AdHoc Administrative Change | ASM ADM | Schedule | SystemMessage | | | AdHoc Configuration Change | ASM CFG | Schedule | SystemMessage | | | AdHocCancel | ASM CNL | Schedule | SystemMessage | | | AdHocCancel | ASM CNL (LEG) | Company activity | SystemMessage | | | AdHoc Day Move | ASM DAY MOVE | Schedule | SystemMessage | | | AdHoc Delete | ASM DEL | Schedule | SystemMessage | | | AdHocEquipmentChange | ASM EQT | Schedule | SystemMessage | | | AdHoc Prefix OpNumber Suffix Change | ASM FLT | Schedule | SystemMessage | | | AdHoc New | ASM New | Schedule | SystemMessage | | | AdHoc Replace | ASM RPL | Schedule | SystemMessage | | | AdHoc Replace Leg Cancel | ASM RPL (CNL LEG) | Schedule | | | | AdHoc Replace Leg Divert | ASM RPL (DIV LEG) | Schedule | | | | AdHoc Replace Leg Create | ASM RPL (NEW LEG) | Schedule | | | | AdHoc Time Change | ASM TIM | Schedule | SystemMessage | | | Cancel | ASM_CNL (LEG) | Company activity | SystemMessage | | | New | ASM_NEW (LEG) | Company activity | OwnMessage | | | ReInstate | ASM_RIN | Company activity | SystemMessage | | | SSM | | SSM ACK | Schedule | SystemMessage | | | | SSM ADM | Schedule | SystemMessage | | | | SSM CNL | Schedule | SystemMessage | | | | SSM CON | Schedule | SystemMessage | | | | SSM DEL | Schedule | SystemMessage | | | | SSM EQT | Schedule | SystemMessage | | | | SSM FLT | Schedule | SystemMessage | | | | SSM MULTI | Schedule | SystemMessage | | | | SSM NEW | Schedule | SystemMessage | | | | SSM REV | Schedule | SystemMessage | | | | SSM TIM | Schedule | SystemMessage | | | | SSM_RPL | Schedule | SystemMessage | | | | SSM_RRT | Schedule | SystemMessage | | | Schedule | SSM | Schedule | SystemMessage | | | | SWAP | Company Activity list | | | | | SWAP EQT | Company Activity list | | | | MVT | | | | | | | Actual Block Off | MVT OFF | Company Activity | SystemMessage | | | Actual Block On | MVT ATA | Company Activity | SystemMessage | | | ActualTakeOff | MVT AIR | Company Activity | SystemMessage | | | COR | MVT COR | Company Activity | SystemMessage | | | Diversion | MVT DIV | Company Activity | SystemMessage | | | Estimated Touch Down | MVT ETA | Company Activity | SystemMessage | | | Estimated Block On | MVT ETA BO | Company Activity | SystemMessage | | | EstimatedBlockOff | MVT ETD | Company Activity | SystemMessage | | | Forced Return | MVT FR | Company Activity | SystemMessage | | | Movement | MVT | Company Activity | SystemMessage | | | NextInfo | MVT NI | Company Activity | SystemMessage | | | Return to Ramp | MVT RTR | Company Activity | SystemMessage | | | Actual Touch Down EstimatedBlock On | MVT TD EA | Company Activity | SystemMessage | | | Actual Block On_Reset | MVT (Reset AA) | Company Activity | SystemMessage | | Will be triggered when you reset the Actual arrival times. The option is only available when you have Actual times. | Actual Block Off_Reset | MVT (Reset AD) | Company Activity | SystemMessage | | Same as for Actual Block On_Reset | ActualOut ActualOff ActualOn ActualIn EstimatedOut EstimatedOff EstimatedOn EstimatedIn RemovedOut RemovedOff RemovedOn RemovedIn | | Company Activity | SystemMessage | | When changing times for flights new events are triggered. Following dialogues are affected: Departure Arrival Delay Return to ramp Forced return Cancel To test
Create new event messages in Automation factory with types ActualOut, ActualOff, etc,. If a time is changed and saved, a related event/message will be sent. For example when adding an actual out time, i.e. an actual blockoff time, ActualOff will be triggered. If adding an estimated on time, i.e. estimated touchdown, EstimatedOn will be triggered. The new events will only be triggered when the corresponding time is actually changed, in contrast to MVT messages that are triggered regardless. | MINT | SendCampMaintenance | CAMP MINT | Maintenance | OwnMessage | | | Maintanence | MNT | Maintenance | OwnMessage | | | Maintanence Delete | MNT DEL | Maintenance | OwnMessage | | | Maintanence Modified | MNT MOD | Maintenance | OwnMessage | | | Maintanence New | MNT NEW | Maintenance | OwnMessage | | | PAIRING | Block | PAR | Block | | | | Block Delete | PAR DEL | Block | | | | Block Modified | PAR MOD | Block | | | | Block New | PAR NEW | Block | | | | REF | Vehicle Reference Activity | REF | vehicle reference activity | OwnMessage | | | Vehicle Reference Activity Delete | REF DEL | vehicle reference activity | OwnMessage | | | VehicleReferenceActivityModified | REF MOD | vehicle reference activity | OwnMessage | | | Vehicle Reference Activity New | REF NEW | vehicle reference activity | OwnMessage | | | | | | | | | ADM/RAD | SendADM | ADM | Vehicle list | SystemMessage | | Aircraft Disposition Dessage | RAD | RAD | Vehicle list | SystemMessage | | Revision to Aircraft Disposition message | | | | | | | Roster | RevisionNotification | Roster REV | Human Resources | | | | Roster Activity | Roster Activity | Roster | OwnMessage | | | Roster Activity Delete | Roster Activity Delete | Roster | OwnMessage | | | Roster Activity Modified | Roster Activity Modified | Roster | OwnMessage | | | RosterActivityNew | Roster Activity New | Roster | OwnMessage | Integration | | RosterRelease | Roster Publ | Human Resources | OwnMessage | | | Roster Deleted | ROST DEL | | | | | Roster New Or Modified | ROST MOD NEW | | | | | SendRTC | RTC | | | | | Other | Send Flight Data Monitoring | DATA MON | Company activity list | | | | Demands_Calculation | DMD CALC | | | | | Send FLASH | FLASH | Company activity list | | | | Send Flights | FLT | Company activity list | | | | Fuel Entry | FUEL | Company activity | | | | CompanyAdHocEvent | Leg AdHoc | Company Activity | | | Additional parameter: Delay OPS Alert, ED, OPS Control Alert | CompanyAdHocEvent | Leg Adhoc Edit | Company Activity | | | | HR Save | HR Save | Human Resources | | | Triggered when you press save in the HR dialog | LoadEnter | LDM | Flight | SystemMessage | ADM | | | | | | | | Tail Move | MOVE | Company activity list | | | | NotCoveredPaxLoads | NOT COV PAX LOAD | | | | | Note | NOTE | Day Note | | | The function is not active. | Send Polaris | POLARIS | Company activity list | | | | SendPPS | PPS | | | | | | REFRESH | | | | | | RTC | | | | | SendAPIS | APIS | Human Resources | | | | Slot | SLT | Slot | SystemMessage | | SCR, SMA | Note: When using SystemMessage the Template can be anything. The system will know based on the Event. | | | | | | | | | | | | | Click on Next Select Template Type (System Message has a syntax defined by the system, this mean that the selected template can be any, templates for systemMessages are hardcoded. Own Message is a message template set up in Integration Factory, System Report is the a standard report, Own Report is a report set up in Dynamics Factory and Event Flow is a Defined Even Flow set up in the integration factory. When one of these has been selected please select template or report and if applicable, a criteria for the template. Template and Header Template are linked to the selected Datatype which again are linked to Integration factory - Message Template | | Click on Next again… Select the COM Channel and the COM Channel Instance. Select the Receivers for this event. Example: SITA Search for a USERS/Facilities/Companies/Free Adresses that contains KEF Use the arrow to add your selection(s). Click submit. Send as unique: If the COM channel is EMAIL you have the option  , this will send individual emails | | It now looks like this. | | |
Click Add if you want to add more COM channels. E.g. Email | | It now looks like this: Note: Remember to tick the channels you want to use. Click on Finish. If the COM Channels are active, Sleipner will generate a message when you make a change that will trigger your event. | | |