logging in or signing up coval Carlton Download Post to : URL : Related Presentations : Share Add to Flag Embed Email Send to Blogs and Networks Add to Channel Uploaded from authorPOINTLite Insert YouTube videos in PowerPont slides with aS Desktop Copy embed code: (To copy code, click on the text box) Embed: URL: Thumbnail: WordPress Embed Customize Embed The presentation is successfully added In Your Favorites. Views: 236 Category: Entertainment License: All Rights Reserved Like it (0) Dislike it (0) Added: November 05, 2007 This Presentation is Public Favorites: 0 Presentation Description No description available. Comments Posting comment... Premium member Presentation Transcript Navy Technical Manuals: A New Publishing InfrastructurePresented at Open Publish ConferenceJune 24, 2003: Navy Technical Manuals: A New Publishing Infrastructure Presented at Open Publish Conference June 24, 2003 Bernie Coval NSWCCD-SSES 5001 S BROAD ST PHILADELPHIA, PA 19112-1403 covalbe@nswccd.navy.milTopics for Discussion: Topics for Discussion Overview of Navy’s Technical Manual Process Content management through the full information lifecycle Use of “Building block” information components that are assembled into documents and other deliverables Use of standards to achieve reuse and re-purposing Fully integrated automation of multiple applications Controlled access to information based on security access levels Extensive use of metadata to locate and track components and govern access Robust loose-leaf processing capabilities The results thus farTechnical Manuals: Technical Manuals Describe the systems on every ship in the fleet as well as foreign Navies Created and updated by wide range of authoring, engineering and logistics personnel including manufacturers Distributed to individual ships, users, schools The challenges: Timeliness of information Usability of content Format of information – editing, viewing, printing (plus loose-leaf updates) Effectivity – managing the matrix of re-usable changes and the schedules in which they are deliveredTechnical Manual Goals : Technical Manual Goals Faster delivery to users Benefit broad sets of target users, applications, and data Customize based on ship profile and product or data set Integrated efficient and automated processes with other enterprise systems Enhance remote user capabilities to support virtual teams Get the right valuable information to the right person in the right format at the right time Creating a solution that serves business and technical needsYesterday’s Way of Doing Business: Yesterday’s Way of Doing Business Paper TMs Changes Revisions Foldouts Rapid Action Changes [RACs] The First IETMs Single Source Document SGML Publishing System: SGML Publishing System Implementation Issues Document Analysis DTD Legacy Documents Data Neutrality Viewers Data functionality Output Change Schema Managing Expectations Technical Manual Publishing : Technical Manual Publishing SGML published to Postscript for Print PDF with hyperlinks distributed on CD-Rom Looseleaf packages New: Distribution through Tech Data Knowledge Management (TDKM) EnvironmentContent Management System: Content Management System The Right Information to the Right Personin the Right Format at the Right Time: The Right Information to the Right Person in 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 Information 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 Defining the Solution: Defining the Solution Software considerations are important System needs to support a wide variety of functions and features that facilitate a successful solution Analysis process often defines the critical product features required However: This process does not always include solution factors important to implementation success CRITICAL POINT: Data, user, and operability requirements, and extensibility need to drive the Implementation Plan Standards can work: Content Structure, Organization, Metadata – SGML and XML “Internet” (communications, access, interfaces) standards Creating the Solution: Creating the Solution A long term process including the following components: SGML Data Normalization Automated Publishing Tools for rapid, multi-format delivery Migration to a content management component re-use environment Local and remote user access with workflows that meet critical business process Integration defined and established with other systems Coordination with manufacturers, subject matter experts, and other resources in the enterprise and virtual enterpriseSolution Inventory: Solution Inventory Comprehensive System for SGML content management, re-use, publishing and electronic delivery Highly granular SGML management and re-use Building Blocks of SGML components Content management system to to facilitate dynamic interaction, support, and update of critical data assets Import of data and metadata management Effectivity management of changes Desktop interfaces and new implementation of Web technology for remote users and systems integration Authoring, review, publishing, distribution Automated publish and delivery tool integration Looseleaf updates, print documents, PDF on CD-Rom Building Blocks of the Solution –TM Example: Building Blocks of the Solution –TM Example Content@ SGML File Split and import of source file into shared or unique content units (MRUs) Transfer of metadata PC or Web client MRU Copyright © 2003 XyEnterpriseContent Configuration for Navy TMs: Content Configuration for Navy TMs Source content managed as granular components at subpara2 level from Navy TM DTD Tools and views are based on user profile and workflow status Metadata on each component and document – based on known attributes of Navy data and properties useful in other Navy systems Workflow templates built for source content updates, review, publishing, and interaction by local and remote users Content Hierarchy and Re-use Model: Content Hierarchy and Re-use Model Publication hierarchy for DDG 74 SIB Underlying data may be shared between ships may be unique to a ship Tables and figures are ship specific. These are tables for DDG74 Master effectivity control file (XML) keeps track of which ship alterations are effective for each ship and each MRU Slide17: Metadata on Content Objects List of effectivities (alterations) for this ship Author and other systems can view, access, and act upon metadata and effectivities for this content and documents in which it is used.Editing Content Components: Editing Content Components Hierarchy built automatically upon import Granularity of objects for editing and re-use based on data model and interoperability requirements Web Access: Web Access The reviewer, having received email notification via the workflow trigger, accesses a the PDF file for review. TM Approval and Update: TM Approval and Update The results of the update workflow can be seen in the history and version information stored with each object. Other important information can also be viewed in the metadata view and shared with other systems…Slide21: Ingalls Shipbuilding TDMIS Configuration System Bath Iron Works NNS AMSEC Remote users Content@ TM repository and workflow Content@ Web Server TDKM Distribution Environment PDF on Web Object and metadata updates NAVSEA Reviewers NAVSEA Editors NAVSEA Engineers Workflow Active lookup, not data replication Content@ Interoperability Architecture NAVSEA Technical Manuals Others Learning Proposed… Notification and Distribution of finished goods to other systemsUS Navy Tech Data Knowledge Management: US Navy Tech Data Knowledge Management Prototype project for integrated content management and distribution environment A New approach to a Distance support system Uses content management system for component management, assembly and “posting” of updates with synchronization system for ship-specific Integrates distribution CMS assembles and publishes the content to the desired formatTechnical Data Knowledge Management (TDKM): Technical Data Knowledge Management (TDKM)Application Strategies : Application Strategies Know your group, its data, users, and goals Identify tools that can leverage XML/SGML and other standards to support these goals Understand the requirements – from a software and implementation perspective Content, Structure, Searching, Meta-data User interaction, training, costs IT impact, available tools, roll-out methods Deliverables – and in what format Business impact and ROI Work with experienced experts in the fieldThe Success Factors: The Success Factors Solid data model and an understanding of the data and content lifecycle and use Defined current and future business practices Empowered personnel Multi-department support – IT, management, end-users, third parties Commitment to meeting the stated goalsExtensibility: Extensibility Processes and Models can be used in other Navy and Defense programs Core product functionality and custom add-ons are extensible to other programs Data preparation and process modeling critical to success You do not have the permission to view this presentation. In order to view it, please contact the author of the presentation.
coval Carlton Download Post to : URL : Related Presentations : Share Add to Flag Embed Email Send to Blogs and Networks Add to Channel Uploaded from authorPOINTLite Insert YouTube videos in PowerPont slides with aS Desktop Copy embed code: (To copy code, click on the text box) Embed: URL: Thumbnail: WordPress Embed Customize Embed The presentation is successfully added In Your Favorites. Views: 236 Category: Entertainment License: All Rights Reserved Like it (0) Dislike it (0) Added: November 05, 2007 This Presentation is Public Favorites: 0 Presentation Description No description available. Comments Posting comment... Premium member Presentation Transcript Navy Technical Manuals: A New Publishing InfrastructurePresented at Open Publish ConferenceJune 24, 2003: Navy Technical Manuals: A New Publishing Infrastructure Presented at Open Publish Conference June 24, 2003 Bernie Coval NSWCCD-SSES 5001 S BROAD ST PHILADELPHIA, PA 19112-1403 covalbe@nswccd.navy.milTopics for Discussion: Topics for Discussion Overview of Navy’s Technical Manual Process Content management through the full information lifecycle Use of “Building block” information components that are assembled into documents and other deliverables Use of standards to achieve reuse and re-purposing Fully integrated automation of multiple applications Controlled access to information based on security access levels Extensive use of metadata to locate and track components and govern access Robust loose-leaf processing capabilities The results thus farTechnical Manuals: Technical Manuals Describe the systems on every ship in the fleet as well as foreign Navies Created and updated by wide range of authoring, engineering and logistics personnel including manufacturers Distributed to individual ships, users, schools The challenges: Timeliness of information Usability of content Format of information – editing, viewing, printing (plus loose-leaf updates) Effectivity – managing the matrix of re-usable changes and the schedules in which they are deliveredTechnical Manual Goals : Technical Manual Goals Faster delivery to users Benefit broad sets of target users, applications, and data Customize based on ship profile and product or data set Integrated efficient and automated processes with other enterprise systems Enhance remote user capabilities to support virtual teams Get the right valuable information to the right person in the right format at the right time Creating a solution that serves business and technical needsYesterday’s Way of Doing Business: Yesterday’s Way of Doing Business Paper TMs Changes Revisions Foldouts Rapid Action Changes [RACs] The First IETMs Single Source Document SGML Publishing System: SGML Publishing System Implementation Issues Document Analysis DTD Legacy Documents Data Neutrality Viewers Data functionality Output Change Schema Managing Expectations Technical Manual Publishing : Technical Manual Publishing SGML published to Postscript for Print PDF with hyperlinks distributed on CD-Rom Looseleaf packages New: Distribution through Tech Data Knowledge Management (TDKM) EnvironmentContent Management System: Content Management System The Right Information to the Right Personin the Right Format at the Right Time: The Right Information to the Right Person in 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 Information 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 Defining the Solution: Defining the Solution Software considerations are important System needs to support a wide variety of functions and features that facilitate a successful solution Analysis process often defines the critical product features required However: This process does not always include solution factors important to implementation success CRITICAL POINT: Data, user, and operability requirements, and extensibility need to drive the Implementation Plan Standards can work: Content Structure, Organization, Metadata – SGML and XML “Internet” (communications, access, interfaces) standards Creating the Solution: Creating the Solution A long term process including the following components: SGML Data Normalization Automated Publishing Tools for rapid, multi-format delivery Migration to a content management component re-use environment Local and remote user access with workflows that meet critical business process Integration defined and established with other systems Coordination with manufacturers, subject matter experts, and other resources in the enterprise and virtual enterpriseSolution Inventory: Solution Inventory Comprehensive System for SGML content management, re-use, publishing and electronic delivery Highly granular SGML management and re-use Building Blocks of SGML components Content management system to to facilitate dynamic interaction, support, and update of critical data assets Import of data and metadata management Effectivity management of changes Desktop interfaces and new implementation of Web technology for remote users and systems integration Authoring, review, publishing, distribution Automated publish and delivery tool integration Looseleaf updates, print documents, PDF on CD-Rom Building Blocks of the Solution –TM Example: Building Blocks of the Solution –TM Example Content@ SGML File Split and import of source file into shared or unique content units (MRUs) Transfer of metadata PC or Web client MRU Copyright © 2003 XyEnterpriseContent Configuration for Navy TMs: Content Configuration for Navy TMs Source content managed as granular components at subpara2 level from Navy TM DTD Tools and views are based on user profile and workflow status Metadata on each component and document – based on known attributes of Navy data and properties useful in other Navy systems Workflow templates built for source content updates, review, publishing, and interaction by local and remote users Content Hierarchy and Re-use Model: Content Hierarchy and Re-use Model Publication hierarchy for DDG 74 SIB Underlying data may be shared between ships may be unique to a ship Tables and figures are ship specific. These are tables for DDG74 Master effectivity control file (XML) keeps track of which ship alterations are effective for each ship and each MRU Slide17: Metadata on Content Objects List of effectivities (alterations) for this ship Author and other systems can view, access, and act upon metadata and effectivities for this content and documents in which it is used.Editing Content Components: Editing Content Components Hierarchy built automatically upon import Granularity of objects for editing and re-use based on data model and interoperability requirements Web Access: Web Access The reviewer, having received email notification via the workflow trigger, accesses a the PDF file for review. TM Approval and Update: TM Approval and Update The results of the update workflow can be seen in the history and version information stored with each object. Other important information can also be viewed in the metadata view and shared with other systems…Slide21: Ingalls Shipbuilding TDMIS Configuration System Bath Iron Works NNS AMSEC Remote users Content@ TM repository and workflow Content@ Web Server TDKM Distribution Environment PDF on Web Object and metadata updates NAVSEA Reviewers NAVSEA Editors NAVSEA Engineers Workflow Active lookup, not data replication Content@ Interoperability Architecture NAVSEA Technical Manuals Others Learning Proposed… Notification and Distribution of finished goods to other systemsUS Navy Tech Data Knowledge Management: US Navy Tech Data Knowledge Management Prototype project for integrated content management and distribution environment A New approach to a Distance support system Uses content management system for component management, assembly and “posting” of updates with synchronization system for ship-specific Integrates distribution CMS assembles and publishes the content to the desired formatTechnical Data Knowledge Management (TDKM): Technical Data Knowledge Management (TDKM)Application Strategies : Application Strategies Know your group, its data, users, and goals Identify tools that can leverage XML/SGML and other standards to support these goals Understand the requirements – from a software and implementation perspective Content, Structure, Searching, Meta-data User interaction, training, costs IT impact, available tools, roll-out methods Deliverables – and in what format Business impact and ROI Work with experienced experts in the fieldThe Success Factors: The Success Factors Solid data model and an understanding of the data and content lifecycle and use Defined current and future business practices Empowered personnel Multi-department support – IT, management, end-users, third parties Commitment to meeting the stated goalsExtensibility: Extensibility Processes and Models can be used in other Navy and Defense programs Core product functionality and custom add-ons are extensible to other programs Data preparation and process modeling critical to success