Re: [Ccglrit-gcclrit] LRIT Ad Hoc Engineer Group Meeting Sept 6, 7, 8
by RyanS＠DFO-MPO.GC.CA
Dear Colleagues,
Attached pleased find the following documents related to the upcoming
September 6-8 meeting of the LRIT Ad Hoc Engineering Group at the IALA/AISM
headquarters in Saint Germain en Laye:
· The meeting Agenda
· Three draft papers - which will serve as a departure point for
discussions at next week's meeting - on:
1) LRIT International Data Centre (IDC) : OPI Bill Cairns
2) LRIT International Data Exchange (IDE) : OPI Neil Trainor
3) LRIT Communications Protocol (CP) : OPI Craig Hayley
· For those who were not at the Vancouver meeting, a detailed Record of
Discussion from the Vancouver meeting. (Please note that this document
should serve as a background only. Concepts discussed will have evolved in
some cases in the development phase of the three papers.)
Just a reminder that the meeting commences at 8:30 on Wednesday, September
6. For those of you staying at the Villas de Impressionistes in Bougival,
IALA has kindly arranged a shuttle service to and from their offices in
Saint Germain en Laye (cost is 8 euros). Shuttle will leave from the hotel
lobby at approximately 8:15. Those of you staying at the Coq Vert can walk
to IALA .
Please note that the dress code is business casual.
If you have any questions, comments or concerns, please don't hesitate to
contact myself or a member of my team. Craig Hayley, Tracy Peverett and
myself are all staying at the Villas de Impressionistes should you need to
contact us Tuesday in advance of the meeting.
Should you require any additional logistical details about the meeting and
are unable to contact my team, contact info and coordinates for IALA are as
follows:
Address: 20 ter rue Shnapper 78100 Saint Germain en Laye
Tel : + 33(0) 1 34 51 70 01
Fax : + 33 (0) 1 34 51 82 05
e-mail: iala-aism(a)wanadoo.fr <mailto:iala-aism@wanadoo.fr>
website : http://www.iala-aism.org
Looking forward, as always, to a productive and fruitful meeting,
Regards,
Sam.
Sam Ryan
A/Director Service Delivery - Directeur int. Prestation des services
Canadian Coast Guard - Garde côtière canadienne
613 998-1505 | facsimile / télécopieur 613 998-9258
ryans(a)dfo-mpo.gc.ca
Fisheries and Oceans Canada | 200 Kent St., 7S036
Pêches et Océans Canada | 200, rue Kent, 7S036
Ottawa, ON, K1A 0E6
Government of Canada | Gouvernement du Canada
17 years, 8 months
FW: LRIT Ad Hoc Engineer Group Meeting Sept 6, 7, 8
by RyanS＠DFO-MPO.GC.CA
Attached is the second zip file containing the paper from Working Group 3.
Regards,
Sam.
_____
From: Ryan, Sam
Sent: August 31, 2006 5:50 PM
To: 'ccglrit-gcclrit(a)lists.ncf.ca'
Subject: RE: LRIT Ad Hoc Engineer Group Meeting Sept 6, 7,8
Dear Colleagues,
Attached pleased find the following documents related to the upcoming
September 6-8 meeting of the LRIT Ad Hoc Engineering Group at the IALA/AISM
headquarters in Saint Germain en Laye:
· The meeting Agenda
· Three draft papers - which will serve as a departure point for
discussions at next week's meeting - on:
1) LRIT International Data Centre (IDC) : OPI Bill Cairns
2) LRIT International Data Exchange (IDE) : OPI Neil Trainor
3) LRIT Communications Protocol (CP) : OPI Craig Hayley
· For those who were not at the Vancouver meeting, a detailed Record of
Discussion from the Vancouver meeting. (Please note that this document
should serve as a background only. Concepts discussed will have evolved in
some cases in the development phase of the three papers.)
Just a reminder that the meeting commences at 8:30 on Wednesday, September
6. For those of you staying at the Villas de Impressionistes in Bougival,
IALA has kindly arranged a shuttle service to and from their offices in
Saint Germain en Laye (cost is 8 euros). Shuttle will leave from the hotel
lobby at approximately 8:15. Those of you staying at the Coq Vert can walk
to IALA .
Please note that the dress code is business casual.
If you have any questions, comments or concerns, please don't hesitate to
contact myself or a member of my team. Craig Hayley, Tracy Peverett and
myself are all staying at the Villas de Impressionistes should you need to
contact us Tuesday in advance of the meeting.
Should you require any additional logistical details about the meeting and
are unable to contact my team, contact info and coordinates for IALA are as
follows:
Address: 20 ter rue Shnapper 78100 Saint Germain en Laye
Tel : + 33(0) 1 34 51 70 01
Fax : + 33 (0) 1 34 51 82 05
e-mail: iala-aism(a)wanadoo.fr <mailto:iala-aism@wanadoo.fr>
website : http://www.iala-aism.org
Looking forward, as always, to a productive and fruitful meeting,
Regards,
Sam.
Sam Ryan
A/Director Service Delivery - Directeur int. Prestation des services
Canadian Coast Guard - Garde côtière canadienne
613 998-1505 | facsimile / télécopieur 613 998-9258
ryans(a)dfo-mpo.gc.ca
Fisheries and Oceans Canada | 200 Kent St., 7S036
Pêches et Océans Canada | 200, rue Kent, 7S036
Ottawa, ON, K1A 0E6
Government of Canada | Gouvernement du Canada
17 years, 8 months
RE: [Ccglrit-gcclrit] LRIT Conference #2
by Chris.Henny＠marlink.com
Please advise agenda and address of IALA meeting on LRIT as I plan to attend
next week.
KInd regards
Dr. Chris Henny
Senior Project Manager
Marlink, part of the Telenor Satellite Service Group
Direct No.: +32 2 371 7229
Mobile: + 32 4963 00066
Fax No.: +32 2 371 7125
www.marlink.com
Please check our new service: http://www.marlinkonline.com
<http://www.marlinkonline.com/>
- Benefit from being in control -
-------------------------------------------------
This message is intended only for the personal and confidential use of the
designated recipient(s) named. If you are not the intended recipient of
this message, you are hereby notified that any review, dissemination,
distribution or copying of this message is strictly prohibited. This
communication is for information purposes only and should not be regarded as
confirmation of any transaction. Email transmission cannot be guaranteed to
be secure or error-free. Therefore, we do not represent that this
information is complete or accurate and it should not be relied upon as
such. All information is subject to change without notice.
-----Original Message-----
From: BertorelliJ(a)DFO-MPO.GC.CA [mailto:BertorelliJ@DFO-MPO.GC.CA]
Sent: Thursday, August 10, 2006 5:30 PM
To: ccglrit-gcclrit(a)lists.ncf.ca
Cc: secgen.iala(a)wanadoo.fr
Subject: [Ccglrit-gcclrit] LRIT Conference #2
Ladies and Gentlemen, there may be a hotel space issue for the week of
September 4rth in Paris and the longer we wait to make our reservations the
more difficult it will be to add rooms if our numbers exceed those already
reserved by IALA. As a result, I would ask that you please make your hotel
bookings as soon as possible. Once again, you must make your reservations
through IALA in order to benefit the negotiated hotel rates.
I thank you in advance for your cooperation and if you have any questions
please feel free to contact me.
Kind Regards,
John Bertorelli
17 years, 8 months
Update on IDC spec
by Cairns, William
Colleagues,
I have included Olaf's block diagram (in jpg since I don't have Visio)
in place of the earlier version. I also included the second SDL block
diagram at the end of the document in the Use Case section (4.2). Is
this the right location for this diagram?
I generally agree with Sadatoshi's note (and Olaf's response) about
duplicating MSC functions. However, I think somehow we need to capture
those functions as "shall" statements in the IDC specification.
Can we get some guidance from the commercial sector on this? Is it
better/would you prefer to simply incorporate by reference the MSC
functional requirements or "translate" them into a
functional/performance specification (which could be used in a tender or
request for proposal)?
We are now two weeks away from our meeting in St. Germain en Laye.
Please get your comments/recommendations to me as soon as you can. I
will make every effort to get them all incorporated in time for the
meeting.
Best regards
Bill Cairns, FRIN
Principal Engineer
Long Range Identification & Tracking
Commandant (G-PWN-3) USCG
Electronics Navigation Division
William.R.Cairns(a)uscg.mil
V: 202-372-1557
F: 202-372-1930
17 years, 8 months
RE: [Ccglrit-gcclrit] WG1 International LRIT Data Centre spec
by Olaf.Jansen＠dnv.com
Bill and all,
First I need to correct myself; SDL = Specification and Description Language (ref. e.g. ITU-T Z.100).
Secondly I attach my thoughts about the IDC in a (standard) block diagram (1) and the first drawing/page of the IDC as an SDL-diagram (2).
(1)
"Top-level block diagram" (.vsd & .jpg files attached, .jpg is included for those who cannot read MS Visio files). This drawing is my understanding of the drawing to be included in 3.1 in Bill's document.
(2)
"Block LRIT SDL" (also included as .vsd and .jpg files). This drawing shows the (proposed) processes of the IDC with the input and output signals (without parameters). When this drawing, the naming convention and interfaces and signals are agreed upon, each process can be further specified in detail in SDL process diagrams.
My recommendation for the further work is, as indicated in my previous email, that complete sets of SDLs are written for the IDC as well as the IDE. The IDC SDLs will be quite similar to the National and Regional LRIT Data Centre functional descriptions. Hence, the IDC and IDE SDLs will together with an interface description and some additional descriptive text be an LRIT System Definition Manual (SDM) that fully describes the necessary parts and functions required to meet the LRIT system expectations of MSC.
Best regards,
Olaf Jansen
DNV
-----Original Message-----
From: ccglrit-gcclrit-bounces(a)lists.ncf.ca [mailto:ccglrit-gcclrit-bounces@lists.ncf.ca] On Behalf Of Olaf.Jansen(a)dnv.com
Sent: 3. august 2006 17:05
To: ccglrit-gcclrit(a)lists.ncf.ca
Subject: RE: [Ccglrit-gcclrit] WG1 International LRIT Data Centre spec
Dear all,
Thanks to CCG for arranging a useful and interesting meeting in Vancouver. (I have had summer vacation until last week and has not been able to give my comments earlier.)
A)
First, I will give my comments to the items raised by Mr. Rolf Zetterberg:
1. Billing functions required in the DCs and IDE. I agree, however, the IDE will have the "global" billing function to handle the cost of data requested through the IDE, while the DCs (at least the regional and International DCs) need billing functions to handle the relevant costs from the contracting governments connected to the each DC. (A national DC may not need this since the connected contracting government probably pay the development and operational cost of his own DC anyway.)
2. Error messages are included in the draft document for the LRIT Data Exchange, see ch. 2 "Summary of DE messages", see Msg.no. EM.
3. SAR retrieval of present data and request for new data is included in the draft document for the LRIT Data Exchange, see ch. 2 "Summary of DE messages", see Msg.no. SS & SR.
B)
I understand the comments given by Mr. Sadatoshi Koike. However, I regard the draft "Functional specification For The International LRIT DC" as a temporary working document, and the reason for copying text from MSC.210(81) was to ensure all relevant functions applicable for the International DC were remembered. Functions not relevant to the Int. DC was skipped.
In the further work, I assume that the Top Level Int. DC Block Diagram referred to under item 3.1 will show that the necessary main functions are included. Then, the detailed description of the Int. LRIT DC should be visualized as a set of SDL (System Definition Language) drawings or by any other suitable Event-Based Architecture Definition Language intended for fairly complex software systems.
Then, in the final version, the copied text from MSC.210(81) may be skipped as Mr. Koike says, and a reference to MSC.210(81) can be included instead.
In a similar way the IDE needs to be specified in the same language. This, together with the requested Technical Specification for communication within the LRIT System (ref. MSC 81 report Annex 4 .3) will ensure compatibility when the whole LRIT system is connected.
C)
It should be remembered that the specification documents for the Int. DC and the IDE will be used by the LRIT co-ordinator as stated in MSC.210(81)item 14.2 .1 & .2 to retrieve the necessary proposals for development and operation.
D)
I am not yet sure if I can attend the meeting in September, but I will come back to this later.
Best regards,
Olaf Jansen
Head of Section/Principal Engineer
Nautical Safety & Communication Systems
Det Norske Veritas, Høvik, Norway
-----Original Message-----
From: ccglrit-gcclrit-bounces(a)lists.ncf.ca [mailto:ccglrit-gcclrit-bounces@lists.ncf.ca] On Behalf Of Sadatoshi Koike
Sent: 3. august 2006 09:20
To: ccglrit-gcclrit(a)lists.ncf.ca
Subject: Re: [Ccglrit-gcclrit] WG1 International LRIT Data Centre spec
Dear Sirs,
Thank you for drafting international LRIT DC
specifications.
However, I think this document contains too many copies
from MSC210(81) - Performance standards and functional
requirements for LRIT(See attachment). As I stated some
weeks ago, copies from other official resolutions must be
avoided since this may cause conflicts between the two
documents. We can insert references to MSC210, but copies
must be deleted. The new information, which is not
contained in MSC210, is just the following CAPACITY
paragraph.
ADDRESS SYSTEM CAPACITY...
The International LRIT Data Centre shall be capable of
processing 50,000 SOLAS Class ships. Based on the
requirement for ships to transmit LRIT information four
times per day, this results in 50,000 x 4 reports per day
= 200,00 reports per day.
In this case, perperps amendments to the existing MSC210
should be proposed in IMO.
I think our task contained in the term of reference is to
develop "technical specifications". However, if there is
no need to develop additional documents, proposing
amendments to the existing MSC210 might be one of the
options.
Regards,
Sadatoshi Koike
--- "Cairns, William" <WCairns(a)comdt.uscg.mil> wrote:
> Colleagues,
>
> I have taken a first cut at re-packaging the
> International LRIT Data Centre
> functional spec (Note the doc name change with
> date). Because of the many
> changes, I have not presented this in track changes
> mode...I accepted all
> changes as I went through it. I am hopeful that you
> will find this version
> a "clean" place from which to continue. I welcome
> your comments, additions,
> etc. (Fresh ideas, too!)
>
> Note the diagram in progress which should eventually
> capture the data flows
> (at a high level) for the IDC. If anyone feels
> adept at powerpoint or some
> other electronic crayon, feel free to make me look
> bad and offer another
> diagram!
>
> Best regards
>
>
> Bill Cairns, FRIN
> Principal Engineer
> Long Range Identification & Tracking
> COMDT (G-PWN-3) USCG
> Electronics Navigation Division
> V: 202-372-1557
> F: 202-372-1930
>
>
> > _______________________________________________
> Ccglrit-gcclrit mailing list
> Ccglrit-gcclrit(a)lists.ncf.ca
> http://lists.ncf.ca/mailman/listinfo/ccglrit-gcclrit
>
**************************************************************
Neither the confidentiality nor the integrity of this message can be vouched for following transmission on the Internet. All messages sent to a DNV email addressee are swept by Sybari Antigen for the presence of malicious code. DNV acknowledges that unsolicited email represents a potential security risk, and DNVs filters to block unwanted emails are therefore continuously adjusted.
**************************************************************
_______________________________________________
Ccglrit-gcclrit mailing list
Ccglrit-gcclrit(a)lists.ncf.ca
http://lists.ncf.ca/mailman/listinfo/ccglrit-gcclrit
**************************************************************
Neither the confidentiality nor the integrity of this message can be vouched for following transmission on the Internet. All messages sent to a DNV email addressee are swept by Sybari Antigen for the presence of malicious code. DNV acknowledges that unsolicited email represents a potential security risk, and DNVs filters to block unwanted emails are therefore continuously adjusted.
**************************************************************
17 years, 8 months
LRIT Conference #2
by BertorelliJ＠DFO-MPO.GC.CA
Ladies and Gentlemen, there may be a hotel space issue for the week of
September 4rth in Paris and the longer we wait to make our reservations the
more difficult it will be to add rooms if our numbers exceed those already
reserved by IALA. As a result, I would ask that you please make your hotel
bookings as soon as possible. Once again, you must make your reservations
through IALA in order to benefit the negotiated hotel rates.
I thank you in advance for your cooperation and if you have any questions
please feel free to contact me.
Kind Regards,
John Bertorelli
17 years, 8 months
WG3 LRIT communications within the LRIT network
by HayleyCR＠DFO-MPO.GC.CA
Dear Colleagues,
I have taken a first cut at producing a draft version of the technical
specification for communication within the LRIT network (item #3 in the
terms of reference for the LRIT performance standards). Please review and
provide feed back via e-mail as well as at our next meeting. I look forward
to receiving comments on the content of the material as well as input on
other items or details that we should add to the document.
P.S. I will be on vacation for the next two weeks and thus won't be
responding.
Best regards,
Craig Hayley
Canadian Coast Guard
Electronic System Engineer
709-772-7740
<<WG 3 LRIT Communications AdHoc Aug16.doc>>
17 years, 8 months
VISA Requests - Invitation Letters
by BertorelliJ＠DFO-MPO.GC.CA
IALA will write an invitation letter to those requiring visas to enter the
country. In your visa request, please make sure that you include the
following information:
1) The Purpose of the visit (LRIT Conference) and the date of entry
for France; and,
2) Your passport details including your full name, date of birth
and passport number.
The primary point of contact at IALA for such requests will be Ms. Virginia
Butler and she can be reached at 011 33 1345 1 7001.
It must also be noted that the invitation letters will be sent via DHL and
if the receiving country does not have a DHL account, it will need to
reimburse IALA directly for the service.
If you require additional information, please do not hesitate to contact me.
Regards,
John Bertorelli
17 years, 9 months
RE: [Ccglrit-gcclrit] WG1 International LRIT Data Centre spec
by Olaf.Jansen＠dnv.com
Dear all,
Thanks to CCG for arranging a useful and interesting meeting in Vancouver. (I have had summer vacation until last week and has not been able to give my comments earlier.)
A)
First, I will give my comments to the items raised by Mr. Rolf Zetterberg:
1. Billing functions required in the DCs and IDE. I agree, however, the IDE will have the "global" billing function to handle the cost of data requested through the IDE, while the DCs (at least the regional and International DCs) need billing functions to handle the relevant costs from the contracting governments connected to the each DC. (A national DC may not need this since the connected contracting government probably pay the development and operational cost of his own DC anyway.)
2. Error messages are included in the draft document for the LRIT Data Exchange, see ch. 2 "Summary of DE messages", see Msg.no. EM.
3. SAR retrieval of present data and request for new data is included in the draft document for the LRIT Data Exchange, see ch. 2 "Summary of DE messages", see Msg.no. SS & SR.
B)
I understand the comments given by Mr. Sadatoshi Koike. However, I regard the draft "Functional specification For The International LRIT DC" as a temporary working document, and the reason for copying text from MSC.210(81) was to ensure all relevant functions applicable for the International DC were remembered. Functions not relevant to the Int. DC was skipped.
In the further work, I assume that the Top Level Int. DC Block Diagram referred to under item 3.1 will show that the necessary main functions are included. Then, the detailed description of the Int. LRIT DC should be visualized as a set of SDL (System Definition Language) drawings or by any other suitable Event-Based Architecture Definition Language intended for fairly complex software systems.
Then, in the final version, the copied text from MSC.210(81) may be skipped as Mr. Koike says, and a reference to MSC.210(81) can be included instead.
In a similar way the IDE needs to be specified in the same language. This, together with the requested Technical Specification for communication within the LRIT System (ref. MSC 81 report Annex 4 .3) will ensure compatibility when the whole LRIT system is connected.
C)
It should be remembered that the specification documents for the Int. DC and the IDE will be used by the LRIT co-ordinator as stated in MSC.210(81)item 14.2 .1 & .2 to retrieve the necessary proposals for development and operation.
D)
I am not yet sure if I can attend the meeting in September, but I will come back to this later.
Best regards,
Olaf Jansen
Head of Section/Principal Engineer
Nautical Safety & Communication Systems
Det Norske Veritas, Høvik, Norway
-----Original Message-----
From: ccglrit-gcclrit-bounces(a)lists.ncf.ca [mailto:ccglrit-gcclrit-bounces@lists.ncf.ca] On Behalf Of Sadatoshi Koike
Sent: 3. august 2006 09:20
To: ccglrit-gcclrit(a)lists.ncf.ca
Subject: Re: [Ccglrit-gcclrit] WG1 International LRIT Data Centre spec
Dear Sirs,
Thank you for drafting international LRIT DC
specifications.
However, I think this document contains too many copies
from MSC210(81) - Performance standards and functional
requirements for LRIT(See attachment). As I stated some
weeks ago, copies from other official resolutions must be
avoided since this may cause conflicts between the two
documents. We can insert references to MSC210, but copies
must be deleted. The new information, which is not
contained in MSC210, is just the following CAPACITY
paragraph.
ADDRESS SYSTEM CAPACITY...
The International LRIT Data Centre shall be capable of
processing 50,000 SOLAS Class ships. Based on the
requirement for ships to transmit LRIT information four
times per day, this results in 50,000 x 4 reports per day
= 200,00 reports per day.
In this case, perperps amendments to the existing MSC210
should be proposed in IMO.
I think our task contained in the term of reference is to
develop "technical specifications". However, if there is
no need to develop additional documents, proposing
amendments to the existing MSC210 might be one of the
options.
Regards,
Sadatoshi Koike
--- "Cairns, William" <WCairns(a)comdt.uscg.mil> wrote:
> Colleagues,
>
> I have taken a first cut at re-packaging the
> International LRIT Data Centre
> functional spec (Note the doc name change with
> date). Because of the many
> changes, I have not presented this in track changes
> mode...I accepted all
> changes as I went through it. I am hopeful that you
> will find this version
> a "clean" place from which to continue. I welcome
> your comments, additions,
> etc. (Fresh ideas, too!)
>
> Note the diagram in progress which should eventually
> capture the data flows
> (at a high level) for the IDC. If anyone feels
> adept at powerpoint or some
> other electronic crayon, feel free to make me look
> bad and offer another
> diagram!
>
> Best regards
>
>
> Bill Cairns, FRIN
> Principal Engineer
> Long Range Identification & Tracking
> COMDT (G-PWN-3) USCG
> Electronics Navigation Division
> V: 202-372-1557
> F: 202-372-1930
>
>
> > _______________________________________________
> Ccglrit-gcclrit mailing list
> Ccglrit-gcclrit(a)lists.ncf.ca
> http://lists.ncf.ca/mailman/listinfo/ccglrit-gcclrit
>
**************************************************************
Neither the confidentiality nor the integrity of this message can be vouched for following transmission on the Internet. All messages sent to a DNV email addressee are swept by Sybari Antigen for the presence of malicious code. DNV acknowledges that unsolicited email represents a potential security risk, and DNVs filters to block unwanted emails are therefore continuously adjusted.
**************************************************************
17 years, 9 months
RE: [Ccglrit-gcclrit] Hotel Bookings...
by Chris.Henny＠marlink.com
ted.
I do not need a hotel but will attend. My father in law lives in MArly le
Roi right next to St Germain.
Kind regards
Dr. Chris Henny
Senior Project Manager
Marlink, part of the Telenor Satellite Service Group
Direct No.: +32 2 371 7229
Mobile: + 32 4963 00066
Fax No.: +32 2 371 7125
www.marlink.com
Please check our new service: http://www.marlinkonline.com
<http://www.marlinkonline.com/>
- Benefit from being in control -
-------------------------------------------------
This message is intended only for the personal and confidential use of the
designated recipient(s) named. If you are not the intended recipient of
this message, you are hereby notified that any review, dissemination,
distribution or copying of this message is strictly prohibited. This
communication is for information purposes only and should not be regarded as
confirmation of any transaction. Email transmission cannot be guaranteed to
be secure or error-free. Therefore, we do not represent that this
information is complete or accurate and it should not be relied upon as
such. All information is subject to change without notice.
-----Original Message-----
From: BertorelliJ(a)DFO-MPO.GC.CA [mailto:BertorelliJ@DFO-MPO.GC.CA]
Sent: Thursday, August 03, 2006 2:52 PM
To: ccglrit-gcclrit(a)lists.ncf.ca
Cc: secgen.iala(a)wanadoo.fr
Subject: [Ccglrit-gcclrit] Hotel Bookings...
There has been some confusion on the hotel booking method for the September
LRIT meeting in Paris. Please be advised that all participants must book
through the IALA Secretariat: <BLOCKED::mailto:iala-aism@wanadoo.fr>
iala-aism(a)wanadoo.fr in order to benefit the negotiated hotel rates. This
also allows IALA to maintain its logistic records.
I thank you all in advance for your cooperation,
Regards,
John Bertorelli
17 years, 9 months
