7700H-CV9D0P0_releasenotes.doc

RELEASE NOTES FOR:

MIL-DTL-7700H Appendix C – Abbreviated Flight Manual

Checklist

VERSION: 7700H-CV9D0P0

LAST UPDATED:

July 2014

DTD CHANGES LISTED BELOW:

TCN: None. V9 Update.

Description:

1) Updated external DTD calls to 38784STD-BV9

2) Removed tctolist, ratddesc, and tmimprep from fpi content model. Not used in checklist.

3) Foldouts removed. Not used in checklist.

TCN: 7700G-C-05299-01

Description: Allow indication of both W and C when both appear in the Flight Manual.

TCN: 7700G-C-06220-01

Description: Request to refine clstep definition. (Too many clitem, amplification placement). In the process, this content model was modified and moved from an entity declaration directly to clitem. Content model now matches App A to improve compatibility.

TCN: 7700G-C-07215-01

Description: This TCN requests that labels be added to the procsteps to add step numbering capability. The interpretation is that numbering should be allowed in the coordinated action table, which is contrary to spec. Para 3.2.12.2.1 states that “Actions in the tabular format shall be written in sentence form without numbered steps.” For a coordinated action checklist (3.2.12.2), clsteps/steps should be used rather than procstep, as clstep/step are numbered. Label attribute added in V8A DTD was not removed from procstep, procstep2, procstep3, procstep4. There was no V8a FOSI. Support for labels not added in V9 FOSI.

FOSI CHANGES LISTED BELOW:

TCN: None. V9 Update.

Description:

1) Removed duplicate code for tctolist, ratddesc, and tmimprep.

2) Removed code for foldouts.

3) Added entity call for graphic symbols (esds, et. al.) there was only support for esds and hcp but DTD allows more.

4) In step code only esds and hcp graphics supported. Substituted entity calls for standard graphics to support all in DTD. Added applicref, change, and verstat to support DTD.

5) There were issues with graphic depth in the performance data section. Decreased footer in 4x7, 5x8nograd, and 5x9nograd pagsets from .75in to .5in.

6) Removed header strings that were leftover from borrowing the pageset code from 5096.

7) Removed volume references from pagesets as volumes are not allowed in checklists.

8) Removed “verstat-titles” from FOSI. Could not find entity that matched this.

9) Duplicate gi=”title” context=”subpara1” thru “subpara3 * front” removed.

10) In graphic att logic, changed “bodypgland” to DSS appropriate code.

11) Removed change bar info from the 5.25 x 11 and 5.75 x 11 front pagesets. Change bars are not allowed in front matter.

12) Noticed in lepcontents for smaller page sizes that some font sizes were set to 17pt and some to 7pt. Given the size of the checklist, changed all to 7pt.

13) Distribution type value other than “A” or “other” had no output. Added support for type “C” to match 38784.

14) Change bars were not alternating right/left in Normal Procedures. See TCN 7700G-C-05047-10 for Emergency Procedures below.

15) Added support for change attribute support for elements in DTD that require it.

16) DTD allows a step4 in procstep. Added FOSI code to support.

17) Element consid was removed from DTD as some point. Removed FOSI code for this.

18) The 5.25x11 and 5.75x11 emergency pagesets did not have the etitle being output on the recto page. Added this to be consistent with the other size checklists.

19) Underline was restored to 38784 emphasis, removed checklist-specific underline and revert to 38784.

20) Cleared etitle.str in emergproccl occur=all so the string wouldn’t carry over from one emergency section to the next when there is more than one.

21) Found wiring/schematic diagram code in if/then code. Not supported in DTD. Removed.

22) Noticed that the etitle string was appearing in the Performance Data section. Cleared the string at the beginning of Performance Data.

23) Spec para 3.2.12.1 states that step 4 shall be (a). Removed underline from step number and added parenthesis.

24) Removed [AL] in conrule for step. Incorrect syntax.

25) There is no ifstep4 in DTD. Removed code from FOSI.

26) Added tabmat support and brought over missing table e-i-c from 38784.

27) Changed newpgmdl from global to local for landscaped pages.

28) Ulabelfmt removed in 38784. Removed here, also.

TCN: 7700-C-04084-02

Description: The * output by the bothmem or navmem attribute is causing misalignment of step numbers. Corrected.

TCN: 7700-C-04084-03 (Part 1 of 2 part TCN)

Description: Problems with LEP formatting. Corrected.

TCN#: 7700-C-04084-03 (Part 2 of 2 part TCN)

Description: Problems with graphic placement in performance data section. The problem is combination of inconsistent graphic sizes (should be 3.5in wide and 5.5in deep) and a too deep footer (fixed in the pagesets).

TCN: 7700-C-04112-08

Description: Set procedures to start directly after each section's TOC. Currently, the first one starts on a recto resulting in blank pages. Removed the textbrk in the main charlist so output would rely on newpage attribute. Added spacing in newpage = 0 to push the procedure title down a bit from the TOC.

TCN: 7700G-07253-01

Description: Added support for subproc1, 2, and 3.

TCN: 7700G-14080-01

Description: Remove foreword and preface. DTD allows only intro.

TCN: 7700G-C-05047-10

Description: In the emergency section, the change bars do not alternate right and left. Corrected by adding chgmkplc to page set.

TCN: 7700G-C-05299-01

Description: Allow indication of both W and C when both appear in the Flight Manual. manwc (w | c | wc) Also added to ifstep to support DTD.

TCN: 7700G-C-06032-01

Description: Security markings on emergency pages in graduated pageset are an issue. Suggest the classification marking appear just above the tab titles.

TCN: 7700G-C-06039-01

Description: "NOTE:" is not per 38784. Removed colon. Also re-formatted to match 38784.

TCN: 7700G-C-06039-02 (This is part 1 of a 2-part TCN.)

Description: FOSI does not center page number. Once the change number was removed from the footer the page number was centered.

Change number is not appearing under the TMIDNO as required for graduated pages. Moved change number from footer to below the TMIDNO.

TCN: 7700G-C-06039-02 (This is part 2 of a 2-part TCN.)

Description: The "tab titles" are not appearing on either side of the page number as required by the spec. The spec says that the left tab title will reflect the data contained on the preceding page and the tab title on the right will reflect the data contained on the current page.

TCN: 7700G-C-06158-01

Description: Add verstat entity clstep/step/ifstep to support DTD.

TCN: 7700G-C-06165-01

Description: orient(port|land1) added to coordprocs in V8a DTD. Added support for it in FOSI.

TCN: 7700G-C-07215-01

Description: This TCN requests that labels be added to the procsteps to add step numbering capability. The interpretation is that numbering should be allowed in the coordinated action table, which is contrary to spec. Para 3.2.12.2.1 states that “Actions in the tabular format shall be written in sentence form without numbered steps.” For a coordinated action checklist (3.2.12.2), clsteps/steps should be used rather than procstep, as clstep/step are numbered. Support for labels not added in V9 FOSI.

TCN: 7700G-C-07269-01

Description: Added amplification as implemented in 7700 App A.

(This was in V6aD3P0, but the TCN was still open.) Added chgatts.

TCN: 7700G-C-10140-01

Description: Added code for generic clsection added in V8a DTD. Added clsectctr for clsection page numbering.

SCRIPT CHANGES LISTED BELOW:

TCN#:

None

Description:

None

MISCELLANEOUS INSTRUCTIONS AND/OR ADVICE:

Section TOCs may be hand tagged if desired. The autobuild attribute should be set to ‘0’ on element <secttoc> if hand tagging will occur. An example of a hand-tagged section TOC:

<secttoc autobuild="0"><parano>1<paratitle>Purpose</paratitle>

<pgnumber>2</pgnumber>

<paratitle>Scope</paratitle><pgnumber>4</pgnumber>

<paratitle>Manual Structure</paratitle><pgnumber>4</pgnumber>

<paratitle>WP Breakout</paratitle><pgnumber>4</pgnumber>

<subparano>5<paratitle>Locating Information</paratitle><pgnumber>4</pgnumber>

<parano>6<paratitle>Abbreviations and Acronyms</paratitle><pgnumber>4</pgnumber>

<parano>7<paratitle>Related Publications</paratitle><pgnumber>4</pgnumber>

<parano>8<paratitle>Time Compliance Technical Orders</paratitle><pgnumber>5</pgnumber>

<parano>9<paratitle>Leading Particulars</paratitle><pgnumber>5</pgnumber>

<parano>10<paratitle>Principles of Operation</paratitle><pgnumber>6</pgnumber>

<subparano>10.1<paratitle>TPS Software</paratitle><pgnumber>6</pgnumber>

<subparano>10.2<paratitle>TPS Hardware</paratitle><pgnumber>6</pgnumber>

<subparano>10.3<paratitle>Operational Description</paratitle><pgnumber>7</pgnumber>

<parano>11<paratitle>Maintenance Concept</paratitle><pgnumber>8</pgnumber>

<parano>12<paratitle>Tolerances,Clearances, and Wear Limits</paratitle><pgnumber>8</pgnumber>

<parano>13<paratitle>Part Identification</paratitle><pgnumber>8</pgnumber>

<parano>14<paratitle>One-Time Use Items</paratitle><pgnumber>8</pgnumber>

<parano>15<paratitle>Improvement Records</paratitle><pgnumber>8</pgnumber></secttoc> If the <secttoc> will be built automatically, autobuild must be set to ‘1’, which is the default value.

More than one emergency procedure section is now allowed. If there is only one <emergproccl>, the numbering will look like: E-1, E-2,……, E-?. If there is more than one <emergproccl>, the numbering will be: EH-1, EH-2,……,EE-1, EE-2, ……, EF-1, EF-2,……, EO-1, EO-2,……, EO-?. HEFO will automatically number. If different numbering is desired, or if more <emergproccl> sections are needed beyond HEFO, the emergsysltr should be used to provide the letter to number with. For example, if you tag <emergproccl emergsysltr=”T”>, numbering for that section will look like: ET-1, ET-2,……ET-?.

Step numbers can be circled for coordinated steps if a coordinated procedures checklist (coordprocs) is not desired. This can be accomplished by setting the attribute crewcoordcirc to ‘1’ on clsteps 1-4 ONLY. Example:

<clstep1 crewcoordcirc=”1”>

If a landscape table is desired, set the orient attribute to land. Example: <table orient=”land”>. Also, pgwide must equal ‘1’.

Note: If the “morerows” attribute is used on an entry in a table that contains a seqlist, or if there are other table problems such as a column separator running the length of the page, the output may not appear correctly and morerows should be removed.

(========== Step Prefixes ========( Step prefixes:

There has been a need expressed for <clstepX> prefixes for the following occurrences:

1) Preceding any checklist step means the step is contained in section II and that a response is required when the flight engineer reads the item (feresponse).

2) A "through-flight" type of operation, where a crewmember will perform, as a minimum, those steps indicated. One example of this is an ERCC (Engines Running Crew Change) where a crew lands the jet, and only accomplishes enough steps in a shutdown checklist to make the jet safe while leaving the engines running, and a fresh crew gets on board and makes the jet ready for flight again, by accomplishing the "through-flight" items (thruflt).

3) Indicate specific checklist steps the engineer will accomplish when a mission crew is not present. This would only happen when training is being accomplished which does not require the mission crew, such as pattern work, or perhaps air refueling (nomisscrw).

The requirement exists that the exact symbol preceding the <clstepX> should have the capability to be set by the author according to the system. To set the symbol the author will have to use attributes on the <docfmcl> element to set the symbol for the publication. The attributes are: thrufltsym, feresponsesym, nomisscrwsym.

When a <clstepX> needs one or more symbols as a prefix, simply select the corresponding attribute: thruflt, feresponse, and nomisscrw, respectively.

(========== emergsysltr attribute ========( If you have made use of the emergsysltr attribute, it may be necessary to edit the file, final.sgml to set the emergsysltr attribute to the correct case. If you notice the final.ps file emergency page numbers are numbering lower case and should be upper case, and you’ve populated the emergsysltr attribute in your original instance in upper case, it could have been transformed to lower case by a script. Once the file is edited, a simple composition should give the proper output.

The "procedure" element must have the attribute "clrank" set. The "clrank" attribute will rank order the procedures. Whether the procedures are sorted by Phase of Flight or by System does not matter as long as the procedures are numbered by the grouping. For example, if the System is "engine" and it will be the first group in the checklist to appear, all procedures relating to the engine system will have the attribute "clrank" set to "1". The next system will have "clrank" set to "2", etc. The same goes for Phase of Flight.

To include a specific "ifthen" or "amplification", the "cl" attribute should be set to "1" but will only be included if these elements fall somewhere inside a procedure marked with the "clrank" attribute. If the "cl" attribute is not set to "1" on either of these elements, nothing will be included in the extraction, including child elements. (NOTE: Amplifications should be kept to a minimum, per specification paragraph 3.3.2.6). Also be aware that front matter will always have to be manually tagged.

The "ifthen" tables in the checklist must appear on the right-hand page with 'Other Conditions" on the left-hand (facing) page. Since there is no way to judge the page breaks with a script, the user must manually do this. (HINT: The best way is to compose as is, then manually break pages based on the output). To facilitate manually forced page breaks, the "addcond" element was added to the checklist DTD. This will break to a left-hand page, allowing "Other Conditions" to be placed opposite the "ifthen" table on the following right-hand (facing) page. If the page break must occur before the end of the "ifthen" table, you must manually break the table and continue it after the "addcond" (see below for more details).

For any questions and/or concerns with this release please contact SGML Support at SGMLSupport@us.af.mil. Thank you!