1 / 19

Content@ Implementation at NAVSEA Philadelphia

Content@ Implementation at NAVSEA Philadelphia. Current Content@ Data Load. Total Number of HM&E TMs Loaded: 3531 Ship Applicability Combatants: 631 unique (1424 non-unique) Minewarfare: 253 (763) Carriers: 162 (1136) Auxiliaries: 158 (1412) Submarines: 50 (335) Amphibs: 275 (1409).

herne
Download Presentation

Content@ Implementation at NAVSEA Philadelphia

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Content@ Implementation at NAVSEA Philadelphia

  2. Current Content@ Data Load • Total Number of HM&E TMs Loaded: 3531 • Ship Applicability • Combatants: 631 unique (1424 non-unique) • Minewarfare: 253 (763) • Carriers: 162 (1136) • Auxiliaries: 158 (1412) • Submarines: 50 (335) • Amphibs: 275 (1409) Non-unique numbers are not additive

  3. Content@ Interoperability Architecture NAVSEA Technical Manuals NNSB/ AMSEC QED LCE * Ingalls Shipbuilding Bath Iron Works PDF on Web Proposed… Content@ Web Server CDI Marine Learning Others Active lookup, not data replication Workflow TDMIS Configuration System Content@ TM repository and workflow Object and metadata updates TDKM Distribution Environment NAVSEA Editors Notification and Distribution of finished goods to other systems NAVSEA Reviewers NAVSEA Engineers * NAVSSES Support Contractors

  4. Requirements for Implementation • Current: • Epic Editor 4.3# • Compiled NAVSEAC2 DTD * • Navy customizations for content@* • Content@ client 3.0.C7 with Navy customizations* • VPN client (requires coordination with firewall admins.), provided by JCALS* • Future • Epic Editor 4.3# • Compiled NAVSEAC2 DTD * • Navy customizations for content@* • Web Access with 128 bit browser * Provided by NAVSSES # Requires purchase by local site

  5. Security • Cisco DEU and VPN; FIPS140 Compliant • JCALS Web Access uses https protocol with 128 bit encryption (future implementation, post SWP3.1.2). • Currently being implemented

  6. The RightInformation to the Right Personin the Right Format at the Right Time Assembly and Formatting Process Re-usable Objects Re-use driven auto publishing Right Information Looseleaf updates Technical Manuals Interactive Electronic Technical Manuals Distance Support Right Format Print Shipped to ships On-Line Accessible to user on-demand via search portal PDF Distributed on CD-Rom Secure Intranet Distributed via TDKM infrastructure Right Person & Right Time

  7. Content@ FunctionalityData Reuse/Effectivity

  8. Paper CD-ROM Web Multiple Data Sets, Configurations, and Delivery Formats Source Data Versions Delivery Formats Ships Information Books DDG51 DDG52 DDG53 DDG54 DDG55 DDG56 DDG57 DDG58 DDG59 Propulsion Operating Guides Training Aid Booklet Ship Alteration Data Technical Manuals Other Alteration Data

  9. Using The 6160 1. Charge the handset 2. Power on the device 3. Refer to graphic Owner’s Guide Web Support Page Support Procedure Using the 6160 Share & Re-use Content for Multiple Products

  10. Building Blocks SGML File • Split and import of source file into shared or unique content units (MRUs) • Transfer of metadata PC or Web client Content@ MRU

  11. Editing the Component Hierarchy built automatically upon import

  12. Master effectivity control file (XML) keeps track of which ship alterations are effective for each ship and each MRU Tables and figures assumed to Be ship specific. These are all tables for DDG74 Publication hierarchy for DDG 74 SIB Underlying data may be shared between ships Or may be unique to a ship

  13. Medadata on SIB Object List of effectivities (alterations) for this ship

  14. Web Access The reviewer, having received email notification via the workflow trigger, accesses a the PDF file for review.

  15. Tracking Effectivity Applying effectivity in a loose-leaf publishing environment is not only a question of filtering applicable data, it is also vitally important to know when and how the effectivity applies to the specific instance. Therefore it is essential to build an effectivity markup scheme with enough intelligence that, during the filtering process, not only is data filtered, but that the appropriate change markup is generated for the filtered data. For the purposes of sharing data, this information will be stored in an XML instance. <Modification ecn=”1092”> <NavyID id=”TMDER-1024”/> <Description>Replaced switchboard 3S with load center 42 </Description> <UsedIn pubno=”s9ddg-bg-mma-070” level=”0”/> <UsedIn pubno=”s9ddg-bh-mma-070” level=”A”/> </Modification>

  16. Marking Effectivity When a change is marked, either text is wrapped with the change element or certain elements are marked with change attributes (delchlvl/inschlvl/chglvl). Effectivity markup mirrors this practice. However, instead of specifying a change level, the user specifies an effectivity control number. <subpara2 tocentry="0" id="i56"> <title>SSGTG 2SG NBPS.</title> <para>SGTG 2SG NBPS, is energized from ship service <effect baseeff="1092-default" deleff="1092">switchboard 3S</effect> <effect inseff="1092">load center 42</effect>. </para> <subpara3 id="i57" inseff="1092"> <title>Load Center 42</title> <para>This para is only effective for those vessels that have load center 42</para> </subpara3> </subpara2>

  17. Filtering When data is exported for publishing the applicable effectivity control information is also exported. Using this information the shared data is filtered to reflect a specific technical manual. Using the preceding ECN and data example, a TM not listed in the ECN entry for 1092 would render the following: <subpara2 tocentry="0" id="i56"> <title>SSGTG 2SG NBPS.</title> <para>SGTG 2SG NBPS, is energized from ship service switchboard 3S. </para> </subpara2> Since the effectivity marking “switchboard 3s” had an effectivity of “1092-default” the filtering program new to include it since this TM did not have and ECN of 1092.

  18. Filtering (cont.) s9ddg-bg-mma-070 with and ECN level of 0 would render the following SGML instance after filtering: <subpara2 tocentry="0" id="i56"> <title>SSGTG 2SG NBPS.</title> <para>SGTG 2SG NBPS, is energized from ship service load center 42. </para> <subpara3 id="i57"> <title>Load Center 42</title> <para>This para is only effective for those vessels that have load center 42</para> </subpara3> </subpara2> Since a level of 0 was associated to this ECN, the filtering program treats any data marked with this value as baseline data.

  19. Filtering (cont.) s9ddg-bh-mma-070 with and ECN level of A would render the following SGML instance after filtering: <subpara2 tocentry="0" id="i56"> <title>SSGTG 2SG NBPS.</title> <para>SGTG 2SG NBPS, is energized from ship service <change change=“delete” level=“A”>switchboard 3S</change> <change change=“add” level=“A”>load center 42</change>. </para> <subpara3 id="i57" inschlvl=“A"> <title>Load Center 42</title> <para>This para is only effective for those vessels that have load center 42</para> </subpara3> </subpara2> Since this TM had an ECN level specified as “A”, the filter treats any data marked with the value as data added post-baseline. Any effect tags are converted to change tags and any effectivity attributes are marked with the appropriate change attributes.

More Related