natgillin/translations-raw huggingface dataset:
But change has to be managed as it is underpinned by continuity of service considerations and by backward compatibility objectives so as to provoke minimal time and cost overheads to the operation of already deployed IT equipment providing TAF functionality (i.e. legacy IT facilities).
Toda spremembe je treba upravljati, ker morata biti zagotovljeni kontinuiteta storitev in cilji združljivosti nazaj, da se doseže čim krajši čas in čim nižji režijski stroški delovanja že razporejene IT opreme, ki zagotavlja funkcionalnost TAF (tj. obstoječa IT oprema).
It is therefore crucial to define a clear strategy of how to implement and manage change to legacy IT equipment to avoid disruption to railway operations without undermining the underlying objectives of guaranteeing continuity of service and interoperability.
Zato je bistvenega pomena, da se opredeli jasna strategija, kako izvajati in upravljati spremembe obstoječe IT opreme, da bi se izognili motnjam železniškega obratovanja in ne bi ogrozili temeljnih ciljev zagotavljanja kontinuitete storitev in interoperabilnosti.
the establishment of a configuration management framework defining the standards and procedures for managing system evolution.
vzpostavitev okvira za upravljanje konfiguracij z opredelitvijo standardov in postopkov za upravljanje razvoja sistema.
This should include how to record and process proposed system changes, how to relate these changes to system components and how to track system releases,
Ta bi moral vključevati tudi načine za zapisovanje in obdelavo predlaganih sistemskih sprememb, povezavo teh sprememb s sistemskimi komponentami in spremljanje sistemskih izdaj,
a policy for release of system baselines.
politika za izdajo osnovnih konfiguracij sistema.
the infrastructure managers and the railway operators that will have to handle various versions of systems providing TAF functionality,
upravljavcem infrastrukture in železniškim prevoznikom, ki bodo morali obvladovati različne verzije sistemov, ki zagotavljajo funkcionalnost TAF,
A baseline in essence embodies the concept of a stable kernel in terms of system functionality, performance and other non-functional characteristics (e.g. RAM) [9].
Osnovna konfiguracija dejansko vsebuje koncept stabilnega jedra v smislu sistemske funkcionalnosti, zmogljivosti in drugih nefunkcionalnih značilnosti (npr. RAM) [9].
However, past experience with this type of systems has shown that a number of version releases [10] are needed to achieve a stable and implementation-suitable baseline.
Toda pretekle izkušnje s takimi sistemi so pokazale, da so potrebne številne izdaje verzij [10], preden se doseže stabilna in ustrezna osnovna konfiguracija.
Working revisions
Delovna revizija
Flaw corrections
Odprava napake
Interoperability proving
Poskus interoperabilnosti
Set of consolidated Spec
Skupek konsolidiranih računov
Through its feedback loops, such a process is highly intertwined.
Prek svojih povratnih zank je tak proces močno prepleten.
This precludes putting several of those processes in parallel, an approach that would lead to unstable, confusing and operationally hampering situations.
To preprečuje vzporedno vzpostavljanje večjega števila teh procesov, ker bi tak pristop povzročil nestabilnost, zmedo in operativno moteče situacije.
Baselines have then to be processed in a series rather than in a parallel manner as illustrated below:
Osnovne konfiguracije je nato treba obdelovati zaporedno, ne pa vzporedno, kakor je ponazorjeno spodaj:
Version Releases
Izdaje verzije
Baseline 1
Osnovna konfiguracija 1
Baseline 2
Osnovna konfiguracija 2
4 years between baselines
4 leta med osnovnima konfiguracijama
Based on current experience the timing between different baselines can be estimated to be circa four to five years.
Na podlagi trenutnih izkušenj preteče po ocenah približno štiri do pet let med različnimi osnovnimi konfiguracijami.
the incorporation of set of today's national functions, where these can be generalized, within the interoperable kernel,
vključitev sklopa obstoječih nacionalnih funkcij, kjer jih je mogoče posplošiti, v interoperabilno jedro,
other future value-added services.
druge prihodnje storitve z dodano vrednostjo.
Debugging versions to repair system faults or security shortcomings should be handled as a version release of a particular baseline.
Verzije za iskanje in odpravljanje sistemskih napak ali varnostnih pomanjkljivosti bi bilo treba obravnavati kot izdaje verzij določene osnovne konfiguracije.
Unless prevented by security implications such version releases within the same baseline are to be backward compatible.
Če tega ne preprečujejo varnostne implikacije, bi take izdaje verzij v isti konfiguraciji morale biti združljive nazaj.
The added functionality that might be embodied in different baselines necessarily implies that different baselines are not backward compatible.
Dodana funkcionalnost, ki je morda vsebovana v različnih osnovnih konfiguracijah, nujno pomeni, da različne osnovne konfiguracije niso združljive nazaj.
However, in order to facilitate migration and in the extent possible from a technical view point, different baselines should encompass a common core of functionality for which backward compatibility should be ensured.
Toda da bi se olajšala prehod in obseg, ki sta možna s tehničnega vidika, bi različne osnovne konfiguracije morale vsebovati skupno jedro funkcionalnosti, za katero bi bilo treba zagotoviti združljivost nazaj.
Such a common core should provide a minimum kernel to enable interoperable data services under acceptable performance.
Tako skupno jedro bi moralo zagotoviti minimalno jedro, ki bi omogočalo interoperabilne podatkovne storitve glede na sprejemljivo zmogljivost.
Infrastructure managers and railway operators will never be in a position to switch from one baseline to the next over night.
Upravljavci infrastrukture in železniški prevozniki ne bodo nikoli mogli na hitro preiti z ene osnovne konfiguracije na drugo.
This is to address problems such as co-existence of TAF facilities compliant with different versions of the TAF specifications, preferred paths of migration (namely trackside priority, rolling-stock priority or simultaneous) as well as the indicative timeframes and the priorities for the migration.
To pomeni, da je treba upoštevati probleme, kakor so soobstoj opreme TAF, združljive z različnimi verzijami specifikacij TAF, zaželene načine prehoda (se pravi prioritete ob progi, prioritete voznega parka ali hkratne), okvirne časovne razporede in prioritete prehoda.
As mentioned earlier, change is a fact of life for large software based systems.
Kakor je bilo že povedano, je sprememba življenjsko dejstvo velikih sistemov, ki temeljijo na programski opremi.
Henceforth, change management procedures should be designed to ensure that the costs and benefits of change are properly analysed and that changes are implemented in a controlled way.
Zato bi bilo treba oblikovati postopke za upravljanje sprememb, kar bi zagotovilo ustrezno analizo stroškov in koristi sprememb in nadzorovano izvajanje sprememb.
This requires the defined change management process and associated tools to ensure that changes are recorded and applied to the specifications in a cost-effective manner.
To zahtevajo opredeljen proces upravljanja sprememb in ustrezna orodja, ki bi zagotovila stroškovno učinkovito ugotavljanje sprememb in njihovo uporabo v specifikacijah.
Whatever the specific details of such a process might eventually be, the latter should be broadly mapped on a structured approach as follows:
Ne glede na to, kakšne bodo specifične podrobnosti tega procesa, bi bilo treba v širši strukturirani pristop vključiti naslednje:
Formalisation of CR
Formalizacija CR
Analysis of CR
Analiza CR
Approval of CR
Odobritev CR
CR valid
CR veljavna
Implementation Strategy
Izvedbena strategija
File CR in DB
Vložitev CR v DB
New Version of Specifications
Nova verzija specifikacij
CR – Change Request
CR – Zahteva po spremembi
CCB – Change Control Board
CCB – Odbor za nadzor sprememb
The generic requirements for such a plan are described in paragraph 7.3.6.
Splošne zahteve za tak načrt so opisane v odstavku 7.3.6 spodaj.
The implementation strategy for the approved changes should be formalised (on the basis of due process and due documentation) into a change management plan that includes notably:
Izvedbeno strategijo za odobrene spremembe bi bilo treba formalizirati (na podlagi ustreznega procesa in ustrezne dokumentacije) v obliki načrta upravljanja sprememb, ki vključuje predvsem:
the policy for change management, release, migration and roll-out.
politiko upravljanja sprememb, izdajo, prehod in razvoj.
An important part of the change management process is the definition of the responsibilities for the delivery of the specifications and for both its quality assurance and configuration management.
Pomemben del procesa upravljanja sprememb je opredelitev odgovornosti za pripravo specifikacij in za njihovo zagotavljanje kakovosti ter upravljanje konfiguracij.
It is planned that most of these tasks will revert to or will be supervised by the European Railway Agency (established by Regulation (EC) No 881/2004) when this will begin operation.
Načrtuje se, da bo večino teh nalog znova prevzela in nadzorovala Evropska agencija za železniški promet (ustanovljena z Uredbo (ES) št. 881/2004), ko bo začela delovati.
The change management process should be formalised within the set of documentation referred to in Annex A.
Proces upravljanja sprememb bi moral biti formaliziran znotraj sklopa dokumentacije, navedene v Prilogi A.
Finally, it is essential that the Change Control Board (CCB), which eventually will act as overall system authority, is composed of a representative cross-section of the all interested parties — namely infrastructure managers, railway undertakings, supply industry, notified bodies and regulatory authorities alike.
In končno, bistvenega pomena je, da je Odbor za nadzor sprememb (CCB), ki bo deloval kot celovit sistemski organ, sestavljen iz tipičnega preseka vseh zainteresiranih udeležencev, to je upravljavcev infrastrukture, prevoznikov v železniškem prometu, dobaviteljske panoge, priglašenih organov in regulativnih organov.
Such affiliation of the parties should ensure a system perspective on the changes that are to be made and a global assessment of their implications.
Taka sestava bi morala zagotoviti sistemsko perspektivo sprememb, ki se uvajajo, in globalno oceno njihovih posledic.
The CCB ultimately will be put under the aegis of the European Railway Agency.
CCB bo končno deloval pod pokroviteljstvom Evropske agencije za železniški promet.
a description of the tools to be used for configuration management and the process to be applied when using these tools,
opis orodij, ki se bodo uporabljala za upravljanje konfiguracij, in proces, ki se bo uporabljal, ko se bodo uporabljala ta orodja,
The specific details of the configuration management processes are to be formalised through specifications to be incorporated in the list of specifications included under Annex A to this TSI.
Specifične podrobnosti procesov upravljanja konfiguracij bodo formalizirane v specifikacijah, ki bodo vključene na seznam specifikacij v Prilogi A k tej TSI.
These specific cases belong to two categories: the provisions apply either permanently (case P), or temporarily (case T).
Ti posebni primeri sodijo v dve kategoriji: določbe veljajo bodisi stalno (primer „P“) bodisi začasno (primer „T“).
In temporary cases it is recommended that the Member States concerned should conform with the relevant subsystem either by 2010 (case T1), an objective set out in Decision No 1692/96/EC of the European Parliament and of the Council of 23 July 1996 on Community guidelines for the development of the trans-European transport network [11], or by 2020 (case T2).
V začasnih primerih je priporočeno, da se zadevne države članice uskladijo z ustreznim podsistemom bodisi do leta 2010 (primer „T1“), cilj, določen v Odločbi Evropskega parlamenta in Sveta 1692/96/ES z dne 23. julija 1996 o smernicah Skupnosti za razvoj vseevropskega prometnega omrežja [11], bodisi do leta 2020 (primer „T2“).
‘T open’ is defined as an undetermined period, which will be fixed in a future revision of this TSI.
„Odprti T“ je opredeljen kot nedoločeno obdobje, ki bo določeno v prihodnji reviziji te TSI.
Specific case for EU member states with border to third countries
Posebni primeri za države članice EU, ki mejijo na tretje države
On the territories of EU Member States having a border with third countries, the requirements of this TSI are not obligatory to transports directly arriving from or going to these third countries (case T open).
Na ozemljih držav članic EU, ki mejijo na tretje države, zahteve te TSI niso obvezne za prevoze, ki prihajajo neposredno iz tretjih držav ali so vanje namenjeni (primer „odprti T“).
However if the transport journey will be extended to another EU Member State, then the requirements of this TSI must be applied in full, provided that there is not a bilateral or multilateral agreement between the States concerned or between RUs or IMs acting in the territory of those Member States
Če pa se bo potovanje nadaljevalo v drugo državo članico EU, je treba zahteve te TSI v celoti izpolniti pod pogojem, da ni nobenega dvostranskega ali večstranskega sporazuma med zadevnimi državami ali med PŽP ali UI, ki delujejo na ozemlju teh držav članic.
For a transport journey operated on lines with 1000 mm track gauge, national rules shall apply.
Za prevoze po progah s tirno širino 1000 se uporabljajo nacionalni predpisi.
OJ L 75, 15.3.2001, p. 29.
ûUL L 75, 15.3.2001, str. 29.
Directive as last amended by Directive 2004/49/EC (OJ L 164, 30.4.2004, p. 44, as corrected by OJ L 220, 21.6.2004, p. 16)
Direktiva, kakor je bila nazadnje spremenjena z Direktivo 2004/49/ES (UL L 164, 30.4.2004, str. 44, popravljeno z UL L 220, 21.6.2004, str. 16).
OJ L 75, 15.3.2001, p. 26.
UL L 75, 15.3.2001, str. 26.
Directive as last amended by Directive 2004/51/EC of the European Parliament and of the Council (OJ L 164, 30.4.2004, p. 164, as corrected by OJ L 220, 21.6.2004, p. 58).
Direktiva, kakor je bila nazadnje spremenjena z Direktivo Evropskega parlamenta in Sveta 2004/51/ES (UL L 164, 30.4.2004, str. 164, popravljeno z UL L 220, 21.6.2004, str. 58).
Under departure point the start point of the path is understood, which can be the train departure point for the journey or an interchange point.
Mesto odhoda pomeni začetno točko poti, ki je lahko mesto odhoda vlaka za potovanje ali mesto izmenjave.
The handover point is the end point of the path.
Točka primopredaje je končna točka poti.
This means, that the access to this information must be independent from which IM has stored the information or part of it.
To pomeni, da mora biti dostop do teh informacij neodvisen od tega, kateri UI je shranil informacije ali njihov del.
E.g. quality assurance standards, system development methodology, testing methodology, documentation planning.
Npr. merila zagotavljanja kakovosti, metodologijo sistemskega razvoja, metodologijo preskušanja, načrtovanje dokumentacije.
Existing telematic applications for freight are telematic applications for freight that are already in service before this TSI enters into force.
Obstoječe telematske aplikacije v tovornem prometu so telematske aplikacije v tovornem prometu, ki se že uporabljajo pred začetkom veljavnosti te TSI.
Versions of the system may have different functionality, performance or may repair system faults or safety or security shortcomings.
Verzije sistema lahko imajo različno funkcionalnost ali zmogljivost, lahko odpravljajo sistemske napake ali varnost ali varnostne pomanjkljivosti.
Decision as last amended by Decision No 884/2004/EC (OJ L 167, 30.4.2004, p. 1, as corrected by OJ L 201, 7.6.2004, p. 1).
Odločba, kakor je bila nazadnje spremenjena z Odločbo št. 884/2004/ES (UL L 167, 30.4.2004, str. 1, popravljeno z UL L 201, 7.6.2004, str. 1).
In contracts between RUs and IMs path availability to run trains will be clearly described in terms of a range of times at specified points.
PŽP/UI razpoložljivost vlakovne poti/načrtovana
Train specifications in terms of maximum length and gross weight, loading gauge etc., will also be covered in these contracts.
V pogodbah med PŽP in UI naj bo razpoložljivost poti za vožnjo vlakov jasno opisana v smislu časovnih razponov na določenih točkah.
CR rejected
CR zavrnjena
Reference Model
OSI – odprt povezan sistem
reporting location identifier (The reporting location for which the forecast is required. This is optional and, if not stated, the response refers to the final reporting point for that IM for this train.).
identifikator lokacije javljanja (lokacija javljanja, za katero se zahteva napoved; ta je neobvezna, in če ni navedena, se odgovor nanaša na končno točko javljanja določenega UI za ta vlak).
reporting location identification (The reporting location for which the forecast is required. This is optional and, if not stated, the response should be the final reporting point for that IM for this train.).
identifikacija lokacije javljanja (lokacija javljanja, za katero se zahteva napoved; ta je neobvezna, in če ni navedena, bi odgovor moral biti končna točka javljanja za določenega UI za ta vlak).
Commission Regulation (EC) No 63/2006
Uredba Komisije (ES) št. 63/2006
This Regulation shall enter into force on 17 January 2006.
Ta uredba začne veljati 17. januarja 2006.
to Commission Regulation of 16 January 2006 establishing the standard import values for determining the entry price of certain fruit and vegetables
k Uredbi Komisije z dne 16. januarja 2006 o določitvi pavšalnih uvoznih vrednosti za določanje vhodne cene nekaterega sadja in zelenjave
Commission Regulation (EC) No 64/2006
Uredba Komisije (ES) št. 64/2006
amending Regulation (EC) No 1695/2005 as regards the quantity covered by the standing invitation to tender for the export of common wheat held by the French intervention agency
o spremembi Uredbe (ES) št. 1695/2005, kar zadeva količino, zajeto v stalnem javnem razpisu za izvoz navadne pšenice iz zalog francoske intervencijske agencije
Commission Regulation (EC) No 1695/2005 [2] has opened a standing invitation to tender for the export of 500000 tonnes of common wheat held by the French intervention agency.
Uredba Komisije (ES) št. 1695/2005 [2] je odprla stalni javni razpis za izvoz 500000 ton navadne pšenice iz zalog francoske intervencijske agencije.
The invitations to tender made since this invitation to tender was opened have almost completely exhausted the quantities made available to the economic operators.
Razpisi, izvedeni v času od odprtja tega stalnega razpisa, so skoraj popolnoma izčrpali količine, dane na voljo gospodarskim subjektom.
In view of the strong demand recorded in recent weeks and the market situation, new quantities should be made available and the French intervention agency should be authorised to increase by 500000 tonnes the quantity put out to tender for export.
Ker je bilo v zadnjih tednih ugotovljeno veliko povpraševanje in ob upoštevanju stanja na trgu, je treba dati na voljo nove količine in pooblastiti francosko intervencijsko agencijo, da poveča količino za izvoz, zajeto v javnem razpisu, za 500000 ton.
Regulation (EC) No 1695/2005 should be amended accordingly.
V skladu s tem je treba spremeniti Uredbo (ES) št. 1695/2005.
Article 2 of Regulation (EC) No 1695/2005 is hereby replaced by the following:
Člen 2 Uredbe (ES) št. 1695/2005 se nadomesti z naslednjim besedilom:
The invitation to tender shall cover a maximum of 1000000 tonnes of common wheat for export to third countries with the exception of Albania, Bosnia and Herzegovina, Bulgaria, Croatia, the former Yugoslav Republic of Macedonia, Liechtenstein, Romania, Serbia and Montenegro and Switzerland.Article 2
Javni razpis zadeva največjo količino 1000000 ton navadne pšenice za izvoz v tretje države, razen v Albanijo, Nekdanjo jugoslovansko republiko Makedonijo, Bosno in Hercegovino, Bolgarijo, Hrvaško, Lihtenštajn, Romunijo, Srbijo in Črno goro ter Švico.Člen 2
OJ L 272, 18.10.2005, p. 3.
UL L 272, 18.10.2005, str. 3.
Including Kosovo as defined in UN Security Council Resolution 1244 of 10 June 1999.’
Vključno s Kosovom, kot je opredeljeno z Resolucijo Varnostnega sveta Združenih narodov 1244 z dne 10. junija 1999.“
Commission Regulation (EC) No 65/2006
Uredba Komisije (ES) št. 65/2006
Having regard to Regulation (EC) No 2320/2002 of the European Parliament and of the Council of 16 December 2002 establishing common rules in the field of civil aviation security [1], and in particular Article 4(2) thereof,
ob upoštevanju Uredbe Evropskega parlamenta in Sveta (ES) št. 2320/2002 z dne 16. decembra 2002 o določitvi skupnih pravil na področju varnosti civilnega letalstva [1], in zlasti člena 4(2) Uredbe,
The Commission is required, by virtue of Regulation (EC) No 2320/2002, to adopt measures for the implementation of common basic standards for aviation security throughout the European Community.
Na podlagi Uredbe (ES) št. 2320/2002 se od Komisije zahteva sprejem ukrepov za izvajanje skupnih osnovnih standardov za varnost letalstva v Evropski uniji.
Commission Regulation (EC) No 622/2003 of 4 April 2003 laying down measures for the implementation of the common basic standards on aviation security [2] was the first act containing such measures.
Uredba Komisije (ES) št. 622/2003 z dne 4. aprila 2003 o določitvi ukrepov za izvajanje skupnih osnovnih standardov za varnost letalstva [2] je bila prvi akt, ki je vseboval take ukrepe.
There is a need for measures giving greater precision to the common basic standards.
Potrebni so ukrepi, ki natančneje opredeljujejo skupne osnovne standarde.
In particular, it should be possible to test new technologies and processes, on a trial basis and for a limited period of time.
Poskusno je treba omogočiti zlasti testiranje novih tehnologij in procesov za določeno časovno obdobje.
Such trials should not prejudice the overall levels of aviation security.
Taki preizkusi ne smejo posegati v skupne stopnje varnosti letalstva.
Regulation (EC) No 622/2003 should be amended accordingly.
Uredbo (ES) št. 622/2003 je zato treba ustrezno spremeniti.
The following Article 3a is inserted into Regulation (EC) No 622/2003:
V Uredbo (ES) št. 622/2003 se vstavi naslednji člen 3a:
New Technical methods and Processes
Nove tehnične metode in procesi
Member States may allow a technical method or process for security controls that is used in place of those laid down in the Annex, provided that:
Države članice lahko odobrijo tehnično metodo ali proces za varnostne ukrepe, ki se razlikujeta od zadevnih iz Priloge, če:
it is being used for the purpose of evaluating a new way of performing the security control concerned, and
se uporabljata za ocenjevanje novega načina izvajanja varnostnih ukrepov; in
it will not negatively affect the overall level of security being attained.
ne bosta negativno vplivala na skupno doseženo stopnjo varnosti.
At least four months before its planned introduction the Member State concerned shall inform in writing the Commission and the other Member States of the proposed new method or process it intends to allow, enclosing an assessment indicating how it shall guarantee that the application of the new method or process will meet the requirement of point (b) of paragraph 1.
Najkasneje štiri mesece pred načrtovano uvedbo zadevna država članica pisno obvesti Komisijo in druge države članice o predlagani novi metodi ali procesu, ki ju namerava odobriti, s priloženo oceno o tem, kako bo zagotovljeno, da bosta nova metoda ali proces izpolnjevala določila iz odstavka 1(b).
The notification shall also contain detailed information on the location(s) where the method or process will be used and the intended length of the evaluation period.
Obvestilo vsebuje tudi natančne podatke o lokaciji(-ah), na katerih se bo metoda ali proces uporabljal(-a), in nameravano dolžino ocenjevalnega obdobja.