WPC,Claris_ZClaris D WP_TV73750730WPTVWPC2WPTVWPC2:6ntrol.Pae !Extensi.ons !Microso.ftl Microsoft !Shared.Cod ShaQ{WP}01  8{WP}018\$  HH  2$HH  Geneva  2K}443!#4$*$$*$ KK  Geneva  Geneva .,6  '8{WP}01Q{WP}01  8 WordPerfect WPC0>IX\ b?ZZ  HIl/ Geneva  TimebZ`bZTbwwww>$Zb8)Zb$b 2b $b $b 8ffb 8f>`b8f>lbflbf` sl / Geneva 1 weekb$b$b$b$b$ Dl/ Genevah1 repeat cycle (35 days)b'8ffb(flb)f`b*8f2`b+8f2l , l,/ Geneva1 repeat cycle (35 days)b-~Z~Bb.ZBb/BHb0BHb1~ZTb2~ZxT 3 f*N/ Geneva ,PEP 4*N/ Geneva DMOPb5~b6~b7b8~~b9~ :/ Geneva 2 weeks ;0 8/ Geneva0Planning period =8/ GenevaPlanning periodb>#b?8b@bAbC82bD82bEB F0/ Geneva D2 weeks H HIl/ Geneva TimebIbJbKbL~bMbN R*</ Geneva DMOPbSbTbUbVbW X~& / Geneva 2 days YHl / Geneva%Pfig. 2:long term planning cycle [Il / Geneva$lfig. 3: nominal planning cycle \ l / Geneva $PEP  >YI >IY >ZJpZ?ZZ?Z tH lIl H HIlIl  H lI, Geneva .(T Time >ZJpZ`Z`pTZZTt$>ZZ>$>$ZZ> t*8ZZ8*8*ZZ8p*8ZZ8*8*ZZ8t8n88nn8p8n88nn8ppppf8ff8fp`8f>f8`>pf8l>f8l>pflflp`ff` t>&&>>&&> >&(=1 week >ZJp8n8np8>8>p8>8>phnnhphnnhtlJJlJlJ lJ(xJ1 repeat cycle (35 days) >ZJpf~f2f2f~pf~lf~lp`~ff~`p`2f8f8`2pf2l8f8l2tl8ll88 l8(x1 repeat cycle (35 days) >ZJpB~Z~Z~B~pBZZBpBHBHpBHBHpT~ZZ~TpTxZ~Z~Tx 0rT(<rPEP 0T)HDMOP >ZJp~~p~~pp~~~~p~~ (2 weeks >ZJth$$hh$$h h$(hPlanning period >ZJt(((( (('Planning period >ZJpp88ppp2882p2882pBBt,,,, ,(2 weeks >ZJt (Time >ZJpppp~~pp (DMOP >ZJpppp  p  t 88  88  8(,2 days >ZJt (fig. 2:long term planning cycle >ZJt@YY@@YY @Y+fig. 3: nominal planning cycle >ZJtxxxx x(xPEPR >Y@ IY >ZJpZ?Z>YI $ZWPC0Ldc bx00bj00b00bh00 x&*/@ Geneva0AOS downlink LOS x&*/@ GenevaDAOS downlink LOSb xb bfbffbfbbxbbzbzbbbbbbxDDbD2b22b 2Db!DtDb"tDt2b#t22b$2Db%DDb&0\b'0\b(h0h\b)0\b0 b12b2b3b4b5b6b7b8t2tb9zz b:hb;tnb<tnb=zb>z ?z/@ Geneva(d"fig.1 : nominal tape dump scenario @/@ Geneva% overlap  B/@ Geneva% overlap  Cxfx/@ Geneva record ETxfx/@ Geneva recordbHbI J = /@ Geneva standby LzS= /@ Geneva standby NYxfx/@ Geneva 4record Ot/@ Geneva($playback QAt/@ Geneva,playback R~2 D/@ Geneva 0off T~2 D/@ Geneva off UQ~2 D/@ Geneva off V 2/@ Genevaon X  2/@ Genevaton YNxl /@ Geneva 4TR1 [nNxl /@ Geneva TR2 \T2rJ /@ Geneva MRCb] b^2b_b`babbbc L  L  L p0x00x0t0111001t/222//2t/h22h2//h2h t*8*8*8* *8, Geneva .+$AOS downlink LOS L t[* *[[ * *[ [* (#ZAOS downlink LOS L pxxppffpffffpffppxxppzzpzzppppppDxDDxDp2DD2p2222p2D2DpDDtDDtp2tDtDt2tp2t22t2p2D2DpDDDD t0\0\\00t0\0\\00t0h\i0h\h\i0i0ht0\0\\00t   t2222pppppppt2t2ttpz zz zphhpnttnpnttnpzzpzz tnnn n(z"fig.1 : nominal tape dump scenario L t  (overlap L t ( overlap L tfxxxxfxfxxx fxx (rxrecord L tl~~ll~~ l~(wrecord L pptJJJ J(standby L t (standby L tOOO O(record L t (playback L tTffTTff Tf(_playback L t,x>>x,x,>>x ,x>(8xoff L t2D4D224D4D 2D4+off L t2DD22DD 2D)off L t 22  22  2(,on L t 22  22  2(+on L t~NlN~N~llN ~Nl(NTR1 L tLkLLkkL Lk(LTR2 L t8NPlPN8N8lPlPN 8NPl+RMRC L p  p22pppppR L?@   L p0x0L t0`'& &\ ^1-xWPC0"8"8-   $gb/L GenevaXR  ENVISAT1 MISSION  .MANAGEMENT   H(EMM) :/L GenevaROP Generation Tools bu/L Geneva'!Mission Phase-Scenario Definitionb]~b~ub~u /L GenevaROP  Files generation Mission planning rules    BRM, RM GMb~b b!b"b&h\hb'hqb(h_b)q$$b*q??b+qHHb,q$zb-q$z-b.q6z-b/q6z?b0qHz?b1qHzQ 3 $/L Geneva1`+ARTEMIS     4-?/L Geneva xAOP 5?Q/L Geneva hUsers 66~_E/L GenevaSM 5   5  )PDS   (PDCC)b7b9 :,3/L GenevaicFiles:  parameter table  cal scenarios  cal requestb;2b=2; >L;/L GenevaSM 1   1  %FOS  (FOCC)b?';b@;2bA;2bBbC;bD;2bE;2 Fz$*/L Geneva0d*Definitions, rules,  filesbGDMDbHMDD;bIMDDM J2;V/L Geneva GMDbKD:DbLhMhbMh_bNhq O V:{/L Geneva<PEP-DMOPbPhDhbQMbRbSbTMDbUMD VzD/L Geneva5\/  Parameter  tablesbWDbXMMbYbZMDb[MDb\MVb]MVb^zb_b`zba bD h/L Geneva AOP dq /L Geneva <Artemisbe~hlhbf~huqbg~hu_ h-Ml/L Geneva[DUUser RM  requests:  ASAR HR  MERIS FR i$"8"8xQ2L/L Geneva/ )Fig. 2: Envisat1 mission planing synopticbj"8"8~bm"8"8PP o"8"8 /L Geneva,  Satellitebp"8"8 7bq"8"8,br"8"8,bs"8"8bt"8"8bw"8"882bz"8"88, {"8"8"&/L Geneva*$command and  controlb~"8"8b"8"8b"8"8>8b"8"8>8b"8"8JhDbb"8"8JhDn - - - t]q]q]q] ]q, Geneva .+,ENVISAT1 MISSION+ MANAGEMENT +(EMM) -p]q]q]q]t~M~~MM ~M(ROP Generation Tools -p~M~~MMtcuuccuu cu(n!Mission Phase-Scenario Definition -p]~]~pu~~upu~~ut~~~~ ~(ROP*2Files generation Mission planning rules* ;BRM, RM GM -p~~~~p~~pppp]hh]hhphqhqp_hh_p$q$$q$p6q66q6pHqHHqHpq$z$qzp$q-z$q-zp-q6z6q-zp6q?z6q?zp?qHzHq?zpHqQzHqQzt---- -('ARTEMIS -t-??--?? -?*AOP -t?QQ??QQ ?Q*Users -t;~~;~;~ ;~(iPDS(y(PDCC) -p;~~;~;~ppt?33??33? ?3(>Files:*parameter table* cal scenarios* cal request -p22p2;2;t;MM;M;M ;M(itFOS(yk(FOCC) -p;MM;M;Mp;;p2;;2p2;;2pp;;p2;;2p2;;2t*q*q*q* *q(Definitions, rules,*files -pDDMDDMp;DDMDM;DpDDMMDMMDt2V;V22;V;V 2V;+GMD -pDD;DD;phhMhhMp_hh_phqhqtV{D{VVD{D{ V{D(bPEP-DMOP -phhDhhDpMMpppDMMDpDMMDtzDzzDD zD+$ Parameter+ tables -pDDpMMMMppDMMDpDMMDpMVMVpMVMVpzzppzzptDh hDD h h Dh (PAOP -tq qq   q *-Artemis -phlh~h~hlphuq~h~qup_uh~h~_utM-l-M-Mll- M-l(Y-User RM* requests:*ASAR HR*MERIS FR -t +o!)Fig. 2: Envisat1 mission planing synoptic -p~~pPPPPt ( Satellite -pp88p,,p,,ppp2882p,88,t&&&& &( command and*control -ppp8>>8p8>>8pbDhJhJbDphDnJhJnDR -7 h - t-q])3.13.1, 1989, 1994 Novell, Inc.(3.1Created with WordPerfect 3.1.G*$?u֮:TVxHH +6G{HH d'*@ / : versbWBOXzTStlStylPJobPSet STR RMMT"PICT.WBFNRWDatvPtPt /l /xu@ 2/Ti 66/2 g&/,!KU,kb1e /!K?/,# {,k*  -/ / "e/u@ ,/Ti Z/ 2 /u@ 5/Ti ef/2 H//t){WP}20{WP}10{WP}22{WP}01{WP}10{WP}20{WP}22{WP}21&  &:6{WP}10<Px2K} <<KK ..,,..,,  ۪:6& &:6{WP}10<Px2K} <<KK   ۪:6{WP}21۫Ы:6Times:7SO96.3.6&  &$ & &$ =THE ENVISAT1 MISSION PLANNING SYSTEM 0'&  &0'3nFrancois Spoto, Franz Demond, Francois Allard3?$?K& &$< :6Arrus BT Italic European Space Agency, ESTEC, Envisat1 Project System Division0K[KK& &0fax: 31(0)7185617 $[k& &$"email: fspoto@jw.estec.esa.nl, fdemond@jw.estec.esa.nl, fallard@jw.estec.esa.nl:6Times0 k{kk&  &0$ {&  &$ܪ ߫ 0  &  &0ܪ0߫  ABSTRACT: The paper presents the strategy which has been selected for the Envisat1]Mission Planning System (MPS) definition. The Envisat1 MPS aims at coherently operatingUUthe 9 payload instruments and the platform functions of the satellite which are associated to thecommand and control functions and to the retrieval (in real or differed time) of scientific datavia X band stations, or via the European data relay satellite Artemis. The functionalities provided by the Envisat1 ground segment elements, and provided by the;satellite itself in order to plan and schedule the mission operations are presented. Thisdescription allows to identify the two basic sets of user data which are to be provided by thet]Envisat1 system: the Global Monitoring Mission, and the Background Regional or RegionalMission.$ &  &$ܪ0߫0 #&  &0ܪ0߫0#/##&  &01 Overall Envisat1 mission objectives.$/;&  &$0;G;;&  &0v'The main objectives of the Envisat1 programme is to endow Europe with an enhanced;capability for the remote sensing observation of the Earth from space. This objective isachieved by developing:Gkkw a package of instruments aimed at meeting the need to observe the earth and its atmospherefrom space in a synergetic fashion, addressing global warming, climate change, ozonedepletion and ocean and ice monitoring.!w"v' a ground segment including: the Flight Operation Segment (FOS) dedicated to spacecraft andmission control and operations, and to the operation planning of the Envisat1 Global Mission.tThe Payload Data Segment ensuring payload operations planning for the Envisat1 Regional33Mission, scientific data acquisition and processing, data distribution, archiving, and userservices.'$(&  &$2 The concept of Envisat1 Regional and Global Mission.0)&  &0$*&  &$I%There is a need to provide both GLOBAL and REGIONAL data to scientific and application&  &users on various time scales.,-+bv Continuous and coherent GLOBAL DATA sets are needed in order to understand betterUclimatic processes and to improve for example climate models via the quantitative observationqof radiative processes, oceanatmosphere heat and momentum exchange, interaction between33atmosphere and land, ocean dynamics and variability, etc...Those objectives which require[nonly scientific products available offline, that is to say days to week from sensing, needhowever permanent and continuous data sensing.J3+s gg33s hJܿ4Some global applications require near real time data delivery, from a few hours to one day from.data sensing. Specific examples include forecast of sea state conditions, sea surface$temperature, atmospheric species, atmospheric variables (temperature, pressure, watervapour).89P Continuous and coherent REGIONAL DATA sets are needed in order to achieve a variety ofobjectives such as seaice strategic offshore applications, snow and ice detection and mapping,coastal processes and pollution monitoring, etc...Some of the regional objectives require nearreal time data products (within a few hours from sensing) generated according to user requests.= >The Envisat1 mission planning system is therefore tailored to the fulfilment of those twospecific Global and Regional Mission objectives.!@$"A+&  &$3 The Envisat1 payload complement.0#B+7+&  &0$C7CIn order to fulfil the Envisat1 Global and Regional Mission objectives, a set of payload'binstruments is at present being developed. Multi mode instruments like ASAR can contribute toboth the Regional and Global Mission depending on the operational modes selected. The table1 below characterises the contribution of each payload instrument to the Regional and GlobalMission.$%HC&  &$&I} }K+###K  & &*Ϊ:6 ЫInstrument:6s:8:60'& &0FN(   & &N"ΪGlobal missionN)   & &NΪRegional mission* Z+###Z K+J7+b77K& &ܪЫAdvanced Synthetic Aperture+& &Radar (ASAR)B+; & &BFor Global monitoring+&  &mode and wave mode,$-& &$Low Rate Modes B.S & &BFor Image mode,+&  &Alternating polarisationmode, and Wide swath& &mode: High Rate Modes/S Z++J7+b77Z Kb+b++K& &Medium Resolution Imagingb& &Spectrometer (MERIS)B0r & &BFor the Reduced Resolutionb&  &data:$1& &$Low Rate ModeB2 ~ & &BFor the High resolution data:03b&  &0$4& &$High Rate Mode5 ~ Zbb+b++Z K+++K& &Radar Altimeter, Microwave&  &Radiometer, Laser Retro$6,& &$Reflector (RA,MWR, LRR)B7,8, & &BܪЫBY98  & &9AN9  Z+++Z m;++;+;+m& &ܪЫMichelson Interferometer0:;K;&  &0for Passive Atmospheric& &Sounding (MIPAS)B;KcW & &BܪЫBY9<;K; & &9ܪЫFor Special Event Monitoring0=;K;& &0mode>KWK |;;++;+;+| Kf++f+K& &Global Ozone Monitoring byf&  &Occultation of Stars$?f& &$(GOMOS)B@ & &BܪЫBY9Afvf & &9ANBfvf Zff++f+Z KE77!7K& &ܪЫScanning Imaging&  &Absorption Spectrometer forAtmospheric Cartography$C& &$(SCIAMACHY)BD6 & &BܪЫBY9E & &9ANF ZE77!7Z KEp++EX+K& &ܪЫAdvanced Along TrackE&  &Scanning Radiometer& &(AATSR)BGa & &BܪЫBY9HE & &9ANIE ZEEp++EX+Z E hK ... .K& &ܪЫDoppler Orbitography and&  &Radiopositioning Integrated& &by Satellite (DORIS)BJ+  & &BܪЫBY9K  & &9ANL Z ... .Z  H J  Ht .1. .1. .1.&  & Gtable 1: Payload instrument contribution to the Envisat1 mission0MJ1=1.&  &00NK=I=:&  &04 Components of the Envisat1 mission.$OLIU&  &$0PMUaUR&  &0LThe Envisat1 payload complement is fulfilling Global and Regional mission objectivesaccording to the 3 mission elements defined below:QOay The Global Monitoring MissionRPyܪ+$$$$+Ы]The Background Regional Mission, defined by default by the Mission Management inabsence of specific user requestsSR The Regional Mission driven by user requestTSUTThe Global Monitoring Mission is defined in form of orbit scenarios enabling detailed and&  &tconflict free planning of instruments operations by the Reference Operation Plan generation&  &tool (ground infrastructure supporting the Envisat1 Mission Management). The GlobalMonitoring Mission is based on :6a:6 routine and continuous sensing of data.VXWYThe Background Regional Mission is defined as a set of orbital segments with resourceconflicts solved by the Reference Operation Plan generation tool.X[ Y\ nPDS user requests for Regional Mission operations are expressed in term of zones or timeOsegments, and transformed into orbital segments using a software function (a zone is definedas a set of points at the surface of an ellipsoid modelling the earth, a time segment is the timeinterval along the orbit along which the instrument mode is kept unchanged during the wholetime interval.ZaQ[bQ]""The user request are only applicable to the Regional Mission and will be merged with thetBackground Regional Mission. Usually, user requests cannot specify the data downlink on[ntheir request, except station operators who may request explicitly downlink of HR data to theirstation (X or Ka band) as part of their operation request.$\f]&  &$0]g&  &05 Envisat1 satellite recording and data transmission capabilities.0^h&  &0 _iThe Envisat1 Polar Platform will offer:`jakpΪ:$$$$ $$:Ы A global recording capability via a set of 4 onboard recorders of 30 Gbits capacity per recorder operable independently.bm (recording will be performed at 4.5 Mb/s and playback at 50 Mb/s)$cn&  &$ X band direct to ground transmission at 100 Mb/s per channel with:0do&  &0 One specific RF channel dedicated to ASAR:6 (in its regional mission modes):6, $ep&  &$ܪ?$ $$$$$?ЫOne specific RF channel dedicated to:0fq&  &0ܪI$$$$$-H$IЫ. MERIS Full Resolution multiplexed with the global mission data, and transmitted in real time. This data set is called the Medium Rate :6C:6omposite (MRC)$gs)&  &$. Playback data of one tape recorder.0ht)5)&&  &0OKa band transmission via Artemis, providing the same data transport as the X bandcommunication channels at 100 Mb/s  :6per channel:9 :6 (2 channels of 100 Mb/s available).iv5MjwMYThis system does offer possible simultaneous operation of all X and Ka band channels.$kxYe&  &$0lyeqeb&  &06 General ground station definitions.Jmzq} qnGz} hJܿ$n{&  &$The following types of X band stations will be used for data downlink:0o| &  &0 ESA ground stations which are the PDHSK (Kiruna), the PDHSE (Ka band User EarthTerminal at ESRIN) and the PDAS (Fucino).p~ National X band stations of ESA member states providing ESA services (NSE)q Other X band foreign stations not from ESA member states (FS)r National Ka band UET.stI%All the X band station visibility segments, and the orbital segments during which Artemis is;geometrically visible from the Envisat1 Ka band terminal will be calculated using a specificsoftware package developed by the Agency and delivered as a CFI to the Ground Segment.u$v&  &$7 Data retrieval scenarios.0w)&  &0x)5""The Envisat1 mission will make optimum use of the capabilities offered by the ESA Data RelaySatellite Artemis which will be available in the time frame of Envisat1.y5MzMYThe Global Mission data recovery (one tape recorder playback per orbit) will be performednpartially via Artemis with the data acquired at the User Earth Terminal (UET) located inESRINFrascatiItaly (PDHSE), and partially via the ESA X band Kiruna station (PDHSK).{Y}|}xxFor the Regional mission, it is planned to use Artemis in order to acquire via the UET datascenes from any part of the world (provided Artemis is visible from the Envisat1 Ka bandtransmission system, that is to say circa 40% of the orbital time).$}&  &$0~ &  &0Over Europe, X band direct acquisitions will still be possible via the two ESA stations ofKiruna and Fucino (circa 10 minutes of acquisition time per station and per  :6100.5 min :: :6orbit).KKThe Envisat1 satellite will continue to serve regional users in any part of the world via direct Xband reception, using in particular the network of stations already acquiring the ERS data. The Envisat1 mission planning system will therefore be based on the dual capability for X banddirect transmission, and Ka band transmission via Artemis.     %I%The Global Mission which is based on a permanent and continuous earth sensing process isnominally recorded on board and downlinked once per orbit either via Artemis or X band, aswell as downlinked in real time when possible as a subset of the Medium Rate Composite. % I I UThe nominal Global Mission is characterized by the following 3 tape recorders scenarios: U a a m Utilisation of 2 Tape recorders alternating on an orbit basis (1 orbit = 100.5 min) m yUtilisation of PDHSK for X band, PDHSE for Ka band y Downlink of 1 TR per orbit ;This scenario assumes that Artemis is available, with 7 consecutive orbits dumped via Kirunapand 7 consecutive orbits dumped via Artemis in order to share on a daily basis the Globalmission processing load on the ground (14.3 orbits per day for Envisat1). $ &  &$b  4 40 h&&bV:6H{TiHVڿ0  &  &0Utilisation of up to 4 TRs to cope with up to 5 orbits without downlink possibility utilisation of PDHSK and PDAS for X band downlink  deferred downlink to PDAS  This scenario assumes that Artemis is temporarily not available.  ' ' 3Utilisation of 2 TRs alternating on an orbital basis 3 ?Utilisation of PDHSK and of a 2nd high latitude station for X band downlink ? Kdownlink of 1 TR per orbit K WThis scenario assumes a permanent unavailability of Artemis and therefore the utilisation of anadditional X band station. W o o {iiThe BRM or RM requires a data downlink in real time either via Artemis or via X bandchannels (specific 100 Mb/s link for ASAR HR data, and part of the 50 Mb/s MRC for MERISDDFull Resolution data). The ASAR LR and MERIS LR data are recorded on board together withthe Global Mission Data, and are also embedded within the MRC. { $ &  &$ܪ:6& &:6{WP}10<Px2K} <<KK   ۪:6{WP}21۫& &:6{WP}10<Px2K} <<KK   ۪:6{WP}21۫ի8 The Envisat1 Ground Segment mission planning concept.0  &  &0$ &  &$;The ground segment architecture of the Envisat1 mission planning system is built up around &  &the following elements: The PDCC (Payload Data Command and Control) mission planning system used to plan the/acquisition of Regional Mission data and to plan the processing, archiving anddissemination of all acquired data to users.  The FOCC (Flight Operation Command and Control) mission planning system used to plan'bthe satellite operations and utilisation of satellite resources, and to plan the acquisition ofGlobal Monitoring data. /%The DRS mission planning system, external to Envisat1 and used to plan the Ka banddownlink. $ / G&  &$b G S Gj Gj S h&  &bThe Envisat1 mission management providing the Reference Operation Plan (using a set of.software tools known as ROP generation tools for files generation), interfacing withffscientists, with Anouncement of Opportunity Instrument providers, and with the Artemismission authority. c The users providing requests for regional mission instrument modes $ &  &$0  H&  &0v'The mission management of Envisat1 will issue a Reference Operation Plan (ROP) for each T&  &Umission phase (commissioning, routine, change of reference orbit if applicable) which is adetailed specification of the mission planning operation.  *The Reference Operation Plan will be supported by software tools developed within theEnvisat1 project in order to allow:   The definition and the validation of mission scenarios  The provision of parameter tables used for onboard and/or on ground processing activities  #bv The definition and the validation of calibration scenarios and implementation of changes tothem based on long loop of calibration and monitoring data. # ; Scheduling of specific calibration activities. ; G$ G S&&$V:6H2H7V0 Sk S&  &00kwk&  &0w9 Mission planning strategy.$&  &$:;0,&  &0The Payload Data Segment (PDS) schedules the Regional Mission, Background Regionalv'Mission, and the MERIS and ASAR calibration activities via the generation of the PreferredExploitation Plan (PEP) issued to the FOS: It converts RM user request, provided in form of zones, into orbital segments.$&  &$ It merges the RM request and the BRM segments according to a strategy solving conflictsbh h h&  &b It generates the merged BRM and RM mission planning in terms of orbital segments perinstrument mode It selects the X band and Ka band Ground Stations for High rate data downlink  The Flight Operation Segment (FOS) schedules the Global Mission based on the definitionsof the rROP generation tool generating: orbit scenario files, Tape Recorders operationalLscenarios, and all necessary payload instrument files like instrument mode dependantconfiguration tables:G It merges the RMBRMGM mission and generate a detailed sequence of operations for all the9Envisat1 instruments. It particularly resolves conflicts between the Preferred ExploitationPlan issued by the PDS (merge of BRM and RM) and the satellite resources available (e.g.power)GwIt schedules calibration measurement for the Global Mission instruments.w It merges Ka and X band link operations according to the requests.It schedules the calibration measurement for the BRM and RM instruments (ASAR, MERIS)%It ensures the I/F with the Artemis Mission Control Centre for the booking of Artemiscommunication time slots.%It provides detailed scheduling reporting back to the PDS and to the mission management inthe form of a Detailed Mission Operation Plan (DMOP).$&  &$10 Mission planning priority level definitions.0&  &0In order to resolve conflicts of operations, rules of priority have to be applied by the groundSegment, as indicated in the table below.mThe safety of the satellite has the highest priority. The FOS therefore takes the necessarymeasures to ensure the satellite safety through the entire mission.++7 KI~;:<) P7g)  & &Ϊ:6 KI~;:<ЫPriorityN7I7P   & &NΪSubpriorityN7I7P   & &N"ΪDefinitionN7I7P   & &NΪGMN7I7P   & &N ΪBRMN7I7P   & &NΪRM7I7P 8P7 P7g8 ) gNz)  & &Ϊ0NN^Ng   & &NΪNN^Ng   & &NܪЫSatellite safetyNN^Ng   & &NΪЫYNN^Ng   & &NΪYNN^Ng   & &NΪYN^Ng 8gN gNz8 m,zazazam& &19aqaz & &9ܪЫ9aqaz & &9ܪЫnatural disaster,0aqaz& &0major pollutionBq}q & &BΪЫY9aqaz & &9Y9aqaz & &9Y(aqaz |za,zazaza| m,m& &(ܪЫ29 & &99 & &9Instrument calibration,0& &0maintenanceB & &BY9 & &9Y9 & &9N( |,| m,CCCCm& &(39 & &99 & &9Request issued by&  &classes of RM usersassigned by the PDS in liaison with mission& &managementB & &BN9 & &9N9 & &9Y |,CCCC| ) )& &39 & &919 & &9Commercial users9 & &9N9 & &9N9 & &9Y 8 8 ) !)& &39 & &929 & &9Governmental users9 & &9N9 & &9N9 & &9Y 8 !8 ) !4)& &39! & &939! & &9Scientific institutions9! & &9N9! & &9N9! & &9Y! 8! !48 m, 4J" 4V"" 4J"m& &49+4  & &99+4  & &9 GlobalBRM nominal4& &activitiesB7+D  & &BY9+4  & &9Y9+4  & &9Nb+4 |4, 4J" 4V"" 4J"|  H   HKI~Z;:< V=V V=V V=V V=V V=V V=V&  &butable 2: Definition of mission related priorities0=I=V&  &0:6:60IUIb&  &0Y: means impact to the mission planningbUaUn Una h&  &b:<11 Planning cycle.q}$}&  &$All planned activities within an orbit are defined with respect to the ascending node. The update&  &of the time of events in UTC is performed by replacing the reference ascending node crossingI(ANX) time by the predicted ANX time provided by the FOS (Flight Dynamics system). Thisactivity, reflected by the DMOP generated by the FOS will take place 6 days prior to the event.   The following types of mission planning will be implemented:  A long term planning cycle covering between 1 repeat cycle and 1 year, allowing to reserveresources like Artemis, and to plan the BRM and the GM. A nominal planning cycle covering 1 week. An emergency planning covering 1 to several orbits per day for user requests issued up to 2days prior to the measurement.:=  %The configurable scenario applicable to the planning cycles is illustrated below:%11=$=I&&$V:6H Gu@H?V0IhI&  &0!:6!:60hth&  &0!:6!:612 Conclusions.t$&  &$The Envisat1 Mission Planning System is at present undergoing a requirement definition&  &Iphase. Because of the split of functions imposed by the share of responsibilities between the PDS and the FOS within the ground segment for the scheduling of the BRMRM and of theGMM, the Envisat1 project team has issued two formal documents applicable to the overallMPS to ensure the completeness and the coherence of the MPS development. !V" c" h&  &V":6#":6:> The Reference Operation Plan which defines the generic rules applicable to the variousUUelements of the ground segment, and specifies the format of the various files to be either;uplinked to the payload complement, or to be implemented within the scientific data algorithmprocessors.& ' ,. The Operational Constraints Document which describes all satellite design driven detailedjconstraints and operational rules relevant for the routine operations of Envisat1. The document'bprovides also the list, content and formats of the instrument onboard mode dependant referenceconfiguration tables to be regularly uplinked to the payload complement.+,\,\hIn order to perform coherently all calculations related to the planning of the Envisat1 mission,the Project has initiated the development and the documentation of mission software functionswhich are to be delivered and integrated as part of the mission planning system within the33Envisat1 ground segment, or as part of the ROP generation tool. This approach ensures that allmission planning datas provided to the PDS or to the FOS are properly ):6verified):6):6ͳverrified,):6):6, and also):6coherent and consistent with physical elements like satellite orbit and performances, time$reference transformation, instrument design characteristics, ground stations characteristics,tutilisation of star catalogues, definition of operational zones, definition of Artemis visibilitysegments, etc...