Project definable values for usage status.
The values are to be defined in the specific project.
CDATA
Attribute "anvstatus" in module start element <period.uh>.
The entity declaration enables a standardized use of values in the attribute "anvstatus" in the specific project or materiel system.
Example: (forradsstalld , ejforradsstalld)
Project definable values for descriptive information type classification.
The values are to be defined in the specific project.
CDATA
Attribute "avsnittstyp" in Element <avsnitt> and <foreskr.avsnitt>.
The entity declaration enables a standardized use of values in the attribute "avsnittstyp" in the specific project or materiel system. Can also be used for required headings.
Example: (overgripande , historik , ing.objekt , uppgifter , funktioner , taktiska.funkt , taktiska.delfunkt , tekniska.funkt, tekniska.delfunkt , prestanda , kallforteckning)
Project definable values for type of data.
The values are to be defined in the specific project.
CDATA
Attribute "datatyp" in Element <grunddata> in Module tekngrunddata.
The entity declaration enables a standardized use of values in the attribute "datatyp" in the specific project or materiel system.
Example: /Admin , fys)
Project definable values for operation intervals.
The values are to be defined in the specific project.
CDATA
Attribute "driftintervall" in module start elements <period.uh> and <oversyn>.
The entity declaration enables a standardized use of values in the attribute "driftintervall" in the specific project or materiel system.
The example values are built up in two parts, according to the following syntax:
Parts are divided by a word space ( ).
The first part is a numerical value (a positive integer).
The second part gives the measurement unit. There is no limitation on units that can be used in the second part, but they should be given as a Swedish standardised abbreviation for the measurement unit.
All values used in this entity must be built on this syntax.
Examples:
'100 km', '500 km', '1000 km', '5000 km', '10000 km',
'10 drifth', '25 drifth', '50 drifth', '100 drifth', '200 drifth',
'10 flygh', '25 flygh', '50 flygh', '100 flygh', '200 flygh',
'50 skott', '100 skott', '250 skott', '500 skott', '1000 skott'
Project definable values for operation status.
The values are to be defined in the specific project.
CDATA
Attribute "driftlage" in module start element <period.uh>.
The entity declaration enables a standardized use of values in the attribute "driftlage" in the specific project or materiel system.
Example: (fore.anv , under.uppeh , efter.anv , vid.tankn)
Project definable values for type of regulation.
The values are to be defined in the specific project.
CDATA
Attribute "foreskr.typ" in module start element <foreskrift> , and in Element <foreskr> in Element <fore> in all procedural information.
The entity declaration enables a standardized use of values in the attribute "foreskr.typ" in the specific project or materiel system.
Recommended use: Use all, or a subset, of the following values:
miljo , skydd , sakerhet
Any extension to the recommended values here must be reported to FMV.
Project definable values for type of action for storage.
The values are to be defined in the specific project.
CDATA
Attribute "forrads.atgardtyp" in Element <forrads.atgard> in Module forradsstallning.
The entity declaration enables a standardized use of values in the attribute "forrads.atgardtyp" in the specific project or materiel system.
Example: (kontroll , just , byte , smorjn , pafylln , torrluftsforvaring)
Project definable values for storage status.
The values are to be defined in the specific project.
CDATA
Attribute "forradslage" in module start element <forradsstallning>.
The entity declaration enables a standardized use of values in the attribute "forradslage" in the specific project or materiel system.
Example: (fore.forv , forradsstallning , vid.utlamning)
Project definable values for types of test suites.
The values are to be defined in the specific project.
CDATA
Attribute "kontrolltyp" in module start element <kontroll>.
The entity declaration enables a standardized use of values in the attribute "kontrolltyp" in the specific project or materiel system.
Example: (system , funktion , prestanda , tillstand)
Project definable values for types of target groups.
The values are to be defined in the specific project.
CDATA
Attribute "malgrupp"in Elements <nlok.varianter> and <nlok.modul> in Module lankar.
The entity declaration enables a standardized use of values in the attribute "malgrupp" in the specific project or materiel system.
Example: (forare , laddare , skytt , vagnchef , alla)
Example: (erfaren , nyborjare)
Example: (elektriker , mekaniker , allm.tekniker , alla)
Project definable values for module status.
The values are to be defined in the specific project.
CDATA
Attribute "modulstatus" in Elements <nlok.varianter> and <nlok.modul> in Module lankar.
The entity declaration enables a standardized use of values in the attribute "modulstatus" in the specific project or materiel system.
Recommended use: Use all, or a subset, of the following values:
planerad , arbetsutg , godkand , faststalld , upphavd
Any extension to the recommended values here must be reported to FMV.
Project definable values for alternative type of materiel.
The values are to be defined in the specific project.
CDATA
Attribute "mtrltyp.alt" in Element <detalj> in Module mtrldata.
The entity declaration enables a standardized use of values in the attribute "mtrltyp.alt" in the specific project or materiel system.
Values should correspond directly to values in %mtrltyp.varden, except for the full-stop at the end of the name in this entity.
Example: resdel. , uh. , specverkt. , standverkt. , emballage. , tillb. , fbrmtrl..
Project definable values for type of materiel.
The values are to be defined in the specific project.
CDATA
Attribute "mtrltyp" in Element <detalj> in Module mtrldata.
The entity declaration enables a standardized use of values in the attribute "mtrltyp" in the specific project or materiel system.
Values should correspond directly to values in %mtrltyp.alt.varden, except for the full-stop at the end of the name in that entity.
Example: resdel , uh , specverkt , standverkt , emballage , tillb , fbrmtrl.
Project definable values for types of representations of an object.
The values are to be defined in the specific project.
CDATA
Attribute "obj.repres"in Elements <nlok.obj> and <lok.obj> in Module lankar.
The entity declaration enables a standardized use of values in the attribute "obj.repres" in the specific project or materiel system.
Example: (LSAR , FREJ , MicroRit , ingen)
Project definable values for observe type classification.
The values are to be defined in the specific project.
CDATA, Implied
Attribute "obstyp" in Element <obs>.
The entity declaration enables a standardized use of values in the attribute "obstyp" in the specific project or materiel system.
Example: (maskinskada , allvarlig maskinskada) #IMPLIED
It's also possible to define a default value here:
Example: (maskinskada , allvarlig maskinskada) "maskinskada"
Project definable values for type of diagram.
The values are to be defined in the specific project.
CDATA
Attribute "schematyp" in module start element <schema>.
The entity declaration enables a standardized use of values in the attribute "schema" in the specific project or materiel system.
Example: (princip , block , krets , koppl , fluid , disposition , oversikt)
Project definable values for types of special conditions.
The values are to be defined in the specific project.
CDATA
Attribute "specforutsattn"in Elements <nlok.varianter> and <nlok.modul> in Module lankar.
The entity declaration enables a standardized use of values in the attribute "specforutsattn" in the specific project or materiel system.
Example: (krig , kris , fred , alla)
Example: (kyla , normal.temp , hetta , alla)
Example: ' (sommar , vinter , alla) '
Example: ' (dag , natt , torrt , vått , alla) '
Example: ' (varm , kall , alla) '
Project definable values for language types.
The values are to be defined in the specific project.
CDATA
Attribute "sprak"in Elements <nlok.varianter> and <nlok.modul> in Module lankar and in element <status> in Module admindata.
The entity declaration enables a standardized use of values in the attribute "sprak" in the specific project or materiel system.
Example: (svenska , engelska , tyska)
Project definable values for table type classification.
The values are to be defined in the specific project.
CDATA
Attribute "tabklass" in Element <tabell>.
The entity declaration enables a standardized use of values in the attribute "tabklass" in the specific project or materiel system.
The recommended values are built up in several parts, according to the following syntax:
Parts are divided by a period (.).
The first part gives the number of columns for the table and is defined as a positive integer followed by the text string "kol".
The following parts describe each column. At this point in time, it consists of a positive integer giving the proportional measure of the column, in proportion to the other columns and the entire table, i.e. the value "2" means "twice as wide as a column with value '1'".
Recommended use: Use all, or a subset, of the following values:
2kol.1.1 , 2kol.1.2 , 2kol.1.4 , 2kol.1.8 , 2kol.2.1 , 2kol.4.1 ,
3kol.1.1.1 , 3kol.1.1.2 , 3kol.1.1.4 , 3kol.1.1.7 , 3kol.1.2.1 , 3kol.1.2.2 , 3kol.1.2.4 , 3kol.1.4.4 , 3kol.2.1.1 , 3kol.2.1.3 ,3kol.4.4.1 ,
4kol.1.1.1.1 , 4kol.1.2.2.2 , 4kol.1.2.1.2 , 4kol.1.4.1.4 , 4kol.1.2.3.4 , 4kol.1.5.2.2 , 4kol.2.1.2.3 , 4kol.2.1.1.1 , 4kol.7.1.1.1 ,
5kol.1.1.1.1.1 , 5kol.1.2.2.2.2 , 5kol.1.2.3.3.3 , 5kol.1.4.2.2.2 , 5kol.3.1.1.1.1 , 5kol.6.1.1.1.1 , 5kol.3.2.1.1.1 ,
6kol.1.1.1.1.1.1 , 6kol.1.2.2.2.2.2 , 6kol.1.4.2.2.2.2 , 6kol.3.1.1.1.1.1 , 6kol.5.1.1.1.1.1 , 6kol.3.2.2.1.1.1 ,
7kol.1.1.1.1.1.1.1 , 7kol.5.1.1.1.1.1.1 ,
8kol.1.1.1.1.1.1.1.1 , 8kol.5.1.1.1.1.1.1.1
Any extension to the recommended values here must be built on the same syntax, and must be reported to FMV.
Project definable values for time intervals.
The values are to be defined in the specific project.
CDATA
Attribute "tidsintervall" in module start elements <period.uh> and <oversyn>.
The entity declaration enables a standardized use of values in the attribute "tidsintervall" in the specific project or materiel system.
The example values are built up in two parts, according to the following syntax:
Parts are divided by a word space ( ).
The first part is a numerical value (a positive integer).
The second part gives the measurement unit, and must be one of the following:
h , d , v , man , ar
(which stands for hours, days, weeks, months, and years).
All values used in this entity must be built on this syntax.
Examples:
'1 d', '2 d', '3 d', '4 d', '5 d',
'1 v', '2 v', '3 v', '4 v',
'1 man', '2 man', '3 man', '6 man', '9 man', '12 man', '18 man',
'1 ar', '2 ar', '3 ar', '4 ar', '5 ar', '6 ar', '12 ar', '15 ar'
Project definable values for types of maintenance task.
The values are to be defined in the specific project.
CDATA
Attribute "uhatgard.typ" in module start element <uh.atgard>.
The entity declaration enables a standardized use of values in the attribute "uhatgard.typ" in the specific project or materiel system.
Example: (bort , dit , isär , ihop , just , inst , smorjn , kalibr , rengor , packn , uppackn , kamofler)
.
Project definable values for maintenance level.
The values are to be defined in the specific project.
CDATA
Attribute "uh.niva" in Elements <nlok.varianter> and <nlok.modul> in Module lankar.
The entity declaration enables a standardized use of values in the attribute "uh.niva" in the specific project or materiel system.
Example: '(A , B , C) .
Project definable values for storage hand out (dispatch).
The values are to be defined in the specific project.
CDATA
Attribute "utlamningslage" in module start element <forradsstallning>.
The entity declaration enables a standardized use of values in the attribute "utlamningslage" in the specific project or materiel system.
Example: (fred , mobilisering)
Project definable values for warning type classification.
The values are to be defined in the specific project.
CDATA, Implied
Attribute "varntyp" in Element <varn>.
The entity declaration enables a standardized use of values in the attribute "varntyp" in the specific project or materiel system.
Example: (livsfara , hogspanning , klamskada , fratskada , brannskada) #IMPLIED
It's also possible to define a default value here:
Example: (livsfara , hogspanning , klamskada , fratskada , brannskada) "livsfara"