NAVSEA Philadelphia Code 94 NAVSEA Philadelphia Code 94 Integrated Logistics & Fleet Maintenance Department Content@ Implementation at NAVSEA Philadelphia

NAVSEA Philadelphia Code 94 NAVSEA Philadelphia Code 94 IntegratedIntegrated Logistics & Fleet Maintenance Department Logistics & Fleet Maintenance Department

Ships Systems Engineering Station

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)

Non-unique numbers are not additive

Ingalls Shipbuilding

TDMIS Configuration

System

Bath Iron Works

NNSB/AMSEC

QEDLCE *

Content@ TM

repository and

workflow

Content@ Web Server

TDKM Distribution Environme

nt

PDF on Web

Object and metadata updates

NAVSEAReviewers

NAVSEAEditors

NAVSEAEngineers

WorkflowActive lookup, not data replication

Content@ Interoperability ArchitectureNAVSEA Technical Manuals

Others

Learning

Proposed…

Notification and Distribution of finished goods to other systems

CDI Marine

* NAVSSES Support Contractors



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



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



The Right Information to the Right Personin the Right Format at the Right Time

Re-use driven auto publishing

Assembly and Formatting

Process

Re-usable Objects

Looseleaf updates

Technical Manuals

Interactive Electronic Technical

Manuals

Distance Support Right InformationRight 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



Content@ FunctionalityData Reuse/Effectivity


Ships Systems Engineering StationMultiple Data Sets, Configurations,

and Delivery Formats

Ships Information Books

Propulsion Operating Guides

Training Aid Booklet

Ship Alteration Data

Technical Manuals

PaperPaper

CD-ROMCD-ROM

WebWebDDG51DDG52DDG53DDG54DDG55DDG56DDG57DDG58DDG59

Other Alteration Data

Source DataSource Data Delivery FormatsDelivery FormatsVersionsVersions



Share & Re-use Content for Multiple Products

Owner’s Guide

Support ProcedureWeb Support Page

Using the 6160

Using The 6160

1. Charge the handset 2. Power on the device3. Refer to graphic



Building Blocks

Content@

SGML File• Split and import of source

file into shared or unique content units (MRUs)

• Transfer of metadataPC or

Web client

MRU



Editing the Component

Hierarchy built automatically upon import



Publication hierarchy for DDG 74 SIBUnderlying data may be shared between shipsOr may be unique to a ship

Tables and figures assumed toBe ship specific. These are all tables for DDG74

Master effectivity control file (XML) keeps track of which ship alterations are effective for each ship and each MRU



Medadata on SIB Object

List of effectivities (alterations) for this ship



Web Access

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



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>



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>



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.



Filtering (cont.)

<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.

s9ddg-bg-mma-070 with and ECN level of 0 would render the following SGML instance after filtering:



Filtering (cont.)

<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.

s9ddg-bh-mma-070 with and ECN level of A would render the following SGML instance after filtering:

Documents

NAVSEA Philadelphia Code 94 NAVSEA Philadelphia Code 94 Integrated Logistics & Fleet Maintenance Department Content@ Implementation at NAVSEA Philadelphia