Escolar Documentos
Profissional Documentos
Cultura Documentos
0
® ®
Solutions Guide
Table Of Contents
Section 1: Introduction
FrameMaker 7.0—XML smart, enterprise ready ..............................................................1-1
FrameMaker Server ....................................................................................................................1-1
FrameMaker 7.0 benefits .............................................................................................................1-2
Adobe FrameMaker 7.0 Solutions Guide .............................................................................1-2
Focus on usage areas and vertical markets .......................................................................1-2
Organization of the Solutions Guide .....................................................................................1-3
Next steps ............................................................................................................................................1-4
Section 2: Identifying the Business Challenges
Business challenges in usage areas ........................................................................................2-2
XML authoring and publishing...............................................................................................2-2
Server-based publishing ..........................................................................................................2-2
Technical documentation .......................................................................................................2-3
Enterprise authoring and publishing ..................................................................................2-3
Business challenges in vertical markets ...............................................................................2-4
Aerospace ......................................................................................................................................2-4
Automotive and transportation ............................................................................................2-4
Government .................................................................................................................................2-5
High technology .........................................................................................................................2-6
Manufacturing .............................................................................................................................2-7
Financial .........................................................................................................................................2-8
Section 3: Meeting the Business Challenges
Assessing the current infrastructure .....................................................................................3-1
Building blocks for meeting business challenges ...........................................................3-2
Template-driven publishing ...................................................................................................3-2
Integrated XML and SGML authoring and publishing ..................................................3-3
Features for managing large documents ..........................................................................3-3
Single-source, multichannel publishing ............................................................................3-3
Platform integration with existing infrastructure and workflows ............................3-3
Solutions in the key usage areas ..............................................................................................3-3
XML authoring and publishing ..............................................................................................3-4
Server-based publishing ..........................................................................................................3-4
Technical documentation .......................................................................................................3-6
Enterprise authoring and publishing ..................................................................................3-7
Solutions by vertical market ......................................................................................................3-8
Aerospace ......................................................................................................................................3-8
Automotive and transportation ............................................................................................3-9
Government .............................................................................................................................. 3-10
High technology ...................................................................................................................... 3-10
Manufacturing .......................................................................................................................... 3-11
Financial services ..................................................................................................................... 3-12
Templates.................................................................................................................................... 10-3
WebWorks .................................................................................................................................. 10-3
Section 11: Where to buy FrameMaker 7.0
Company matrix ........................................................................................................................... 11-2
Company descriptions ............................................................................................................... 11-3
Today, FrameMaker 7.0 software has become a powerful application for authoring and
delivering information across the enterprise. Adobe has combined the word-processing
capabilities of FrameMaker with the robust structured authoring environment of
FrameMaker+SGML, and added the capability for creating and editing valid XML
documents from within a single application. Users can choose the structured authoring
environment to address single-source multichannel publishing needs and create valid XML,
or a simpler interface for general word-processing usage to create well-formed XML.
FrameMaker Server
For organizations that need server-based print and PDF output, FrameMaker Server 7.0
allows automated content assembly, rendering, and delivery from server applications,
including databases, application servers, and Web services. FrameMaker Server 7.0 can work
in tandem with the desktop version of FrameMaker. Both products are based on the
template-driven workflow, so templates for FrameMaker 7.0 Server can be created on any
desktop version of FrameMaker 7.0.
We examine six vertical markets representing a broad range of information publishing requirements:
• Aerospace
• Automotive and transportation
• Government
• High technology
• Manufacturing
• Financial services
3: Meeting the Business Challenges—This section outlines the types of publishing solutions that
businesses have implemented to solve today’s problems in authoring, managing, and delivering
information. Presented by industry sector and application area, these solutions can help you to identify
possible solutions that you might adopt. The section discusses the business motivator for each solution,
including return on investment, knowledge management across the enterprise, and decreased time-to-
market.
4: The Adobe Solution—This section shows how the FrameMaker 7.0 platform can be a key
architectural component in a variety of informationmanagement solutions. Examples of real-world
architectures and implementation details for the four usage areas are provided, which you can reuse or
adapt for your needs.
5: Selecting the Right Tools—This section presents a methodology for evaluating information
solutions, and provides a checklist that you can use as a guide when evaluating FrameMaker 7.0 against
competing solutions.
6: FrameMaker Success Stories—Here we present more than 30 case studies that demonstrate how
Adobe FrameMaker effectively meets customer requirements in enterprise-wide authoring and
publishing solutions, organized by industry sector and publishing requirements.
10: FrameMaker 7.0 User Resources—This section provides tips and advice for driving your
FrameMaker 7.0 evaluation, implementation, and migration processes.
11: Where to Buy FrameMaker 7.0—The Adobe partners listed in this section can assist you throughout
the process of identifying publishing issues within your organization and evaluating and implementing
solutions.
Next steps
After you have read this Solutions Guide, you may want to do some or all of the following:
• Consider how the ideas presented here might benefit your organization.
• Sketch out or prototype some architectures based on your requirements, processes, and workflow.
• Contact an Adobe reseller or systems integrator to discuss your current needs and obtain
FrameMaker 7.0 evaluation software.
• Learn more about FrameMaker 7.0 and FrameMaker Server 7.0 by visiting the Adobe Web.
Adobe, the Adobe logo, Acrobat, and FrameMaker are either registered trademarks or trademarks of Adobe Systems Incorporated in the United
States and/or other countries. All other trademarks are property of their respective owners.
In sections 2, 3, and 4 of the Adobe® FrameMaker® 7.0 Solutions Guide, we examine the
business problems, processes, benefits, and strategies of a variety of conventional and re-
engineered approaches to information management and publishing. Section 2 focuses on
the business challenges behind managing and distributing information. Section 3 and
Section 4 provide business and architectural solutions for implementing or improving each
of these areas.
We examine these issues and solutions from two points of view—usage areas and vertical
markets. The four major usage areas we discuss here represent specific applications of
information creation, management, and delivery: XML authoring and publishing, server-
based publishing, technical publishing, and enterprise authoring and publishing. The six
vertical markets present a broad range of information publishing requirements: aerospace,
automotive and transportation, government, high tech, manufacturing, and financial.
Almost any industry or vertical market shares challenges with the markets presented here.
Organizations are increasingly building knowledge management systems, Web applications, and Web-
based document architectures around XML. It provides a wealth of capabilities for information
publishing and distribution—customizing documents for a particular audience, pushing content to new
devices such as personal digital assistants (PDAs), and automated publishing from an application server
or database, to name a few.
In order to take advantage of the capabilities of XML-based information management and publishing,
an organization must be able to author valid XML content. Yet many currently available methods for
generating XML content are severely limited when it comes to general deployment:
• The few “XML editors” that can write human-readable documents (not just XML data files) are
complex and expensive. Some have no print or PDF functionality without a complex or expensive
add-on product.
• Some applications that claim the capability to “save as XML” actually save only to the application’s
built-in Document Type Definition (DTD), and cannot provide the rich metadata required for
many XML applications.
• Some companies use document conversion services to obtain XML versions of certain documents.
Such conversion services can be expensive and produce poor-quality results.
Server-based publishing
Server-based solutions support creating and publishing readable documents from database information,
making the information that is tailored to a wide audience via appropriate publishing formats, and—
with minimal human intervention at the moment of publishing—enabling high-quality layout and
typography standards for printed materials.
The server system also needs to be able to accept or import a wide variety of formats (such as PDF,
HTML, or XML), delivering internal content that supports the organization’s activities and external
content that meets customers’ expectations. For example, consider a catalog-based parts reseller that
collects information from a vast number of original equipment manufacturers (OEMs), maintains and
updates that information in a relational database, and publishes that information in print, PDF, and
HTML formats.
When dealing with large volumes of information, process automation and efficiency are key to
minimizing resource requirements and cost. Server-based publishing may be used for creating
thousands of pages filled with complex information from industrial-sized databases, to single-page
customized and personalized reports. In all cases, efficient server-based publishing relies on tightly
integrated components, turnkey operation, and minimal manual intervention.
Technical documentation
Almost every product or service requires documentation. Organizations that create, manage, and deliver
this kind of technical content face unique business challenges, including improving time-to-market,
reducing costs, finding opportunities for content reuse, enhancing quality, and maximizing customer
satisfaction. Forward-thinking companies consider technical documentation to be a “manufactured”
product that must meet manufacturing schedules. These companies plan and evaluate the life cycle of a
product and its documentation in tandem.
Delivery of technical documentation also presents several business problems. Paper manuals are
appropriate for many applications, but are expensive to produce and deliver and cannot be updated
easily. Customer expectations for access to technical information are growing. Customers often want
print (or printable) documentation, online help, and Web access to relevant information. A company’s
customer and technical support staffs also typically need written technical materials, while the training
organization uses the same information in different ways. A major challenge is to author this
information most efficiently so it can be delivered to a variety of audiences in different formats.
Many organizations see creating, managing, and delivering internal information as an administrative
task. Each document is created and managed in isolation. Companies that want to maximize the value of
the intellectual property locked within those documents, and create a knowledge base from their
content, have discovered that by proactively managing their internal content they can dramatically
improve its value in supporting the business goals of the organization. In addition, this information
needs to be shared with customers and suppliers. Customers, for example, need access to product
information so that they can make better, more informed purchasing decisions.
Each of these vertical markets faces particularly interesting challenges. Together, they represent a broad
cross-section of enterprise publishing activities.
Aerospace
Information management and delivery plays a critical supporting role in the aerospace industry. Few
industries have products as complex, strict safety and regulatory requirements , and low error tolerance.
The extremely long product development cycles and lifespans require correspondingly long
documentation cycles. For example, the Boeing 747, still one of the most popular commercial aircraft,
was introduced in 1970.
The aerospace industry shares many basic information management requirements with manufacturing
and any industry with volumes of information to manage. For example, an individual aircraft’s flight
operation manual is customized for the airline buying the plane, but consists largely of material
common to all flight operations manuals for that particular aircraft model and even for that
manufacturer.
The aerospace industry also has extremely rigorous information management requirements. Because the
content supports mission-critical, high-stakes operations—for example, the manufacture, maintenance,
and repair of commercial aircraft—it must be thoroughly reviewed for accuracy and all changes must be
approved and verified. The industry must securely maintain its document sources, and publish content
to customers in nonmodifiable formats.
Consider the opportunities for information reuse in just one document—the vehicle owner’s manual,
shipped with every new car. The procedure for changing a tire, for example, might be the same for all
models of a given manufacturer. Compare this to the inefficiency of writing and maintaining this
procedure separately for every automobile model.
The information management and publishing needs of this sector are similar to aerospace and
manufacturing. Like aerospace, automobile manufacturers support a massive infrastructure for vehicle
maintenance. Whether purchased for military, commercial, or consumer use, motor vehicles present
enormous information requirements to support service, maintenance, and repair. However, unlike in
aerospace, many organizations provide these functions. Delivering current, accurate maintenance data
in a usable form to users from junior mechanics to fleet managers is a tremendous challenge—further
complicated by the rapid changes in vehicle production. A typical car model is completely redesigned
every three to five years, while smaller manufacturing changes can be introduced as often as every six
months.
Other demands drive this sector. Consumers and service providers alike expect to access pre- and post-
sale maintenance and repair information on the Web. In many cases, they also need to print that
information on demand.
In summary, the business challenges facing the automotive and transportation industries include:
Government
Government enterprises—law-making bodies, government departments, regulatory agencies, and
government-managed service providers such as the United States Postal Service—create, collect,
manage, maintain, and distribute information for a wide array of purposes. They provide content in the
form of public policy, laws and statues, legal records, regulatory guidelines, general instructions, and
forms, including information that supports critical decision-making processes. Furthermore, as an
employer of large numbers of people, governments also manage and maintain traditional internal
information, such as content related to human resources and policies and procedures.
Government bodies all need to make information accessible to everyone, regardless of visual or motion
impairment. This effort involves both information and application design. Content can be designed to
maximize accessibility through consistent structure and metadata annotations. Likewise, applications
can be designed to render content through visual, tactile, and aural means for people with disabilities.
The United States has formalized requirements for information accessibility in Section 508 of the
Rehabilitation Act Amendments of 1998. A major focus of Section 508 is to make electronic documents
available to visually impaired users , and to make software accessible to users with visual or motor
impairments.
Because information published by governments serves a diverse audience and wide range of purposes,
the publishing process presents special challenges. Government officials responsible for creating,
assembling, and publishing content can expect to receive content from staff members with a diverse set
of expertise and skill levels and a variety of software applications.
The vast amount of information published by governments makes traditional paper publishing
impractical in many instances. Paper-based publishing results in long lead times and high costs, which
frequently means that publication of updated information is infrequent, which in turn causes decisions
to be made based on inadequate or outdated information. Paper-based publishing also does not
promote effective accessibility.
Governments are beginning to rely heavily on electronic distribution, including HTML Web content
and richly formatted PDF documents distributed by Web or CD-ROM. In addition, governments must
update content to regulatory and other agencies very quickly, often in real time, for mission-critical
agencies such as the Federal Aviation Administration and U.S. Department of Transportation.
High technology
High technology includes a diverse range of markets—semiconductors to biotechnology; computer
software to instrumentation—and provides perhaps the broadest opportunities for process
improvement and positive return on investment from re-engineering information management
solutions. Consider the array of information that supports a typical high-technology organization:
• Technical documents
• Database content
• Corporate knowledge
• Supply-chain management collateral
The large amount of information in the life cycle of a high tech product or service begins with marketing
surveys, product requirements, product specifications, and engineering documents. Much of this
information, if properly managed, provides source material for the technical documents and marketing
collateral that accompany each product or service. Enabling information reuse throughout the
organization and the product life cycle is critical for maximizing business efficiency.
Because products and product specifications change frequently in high tech, maintaining the quality and
integrity of information remains critical. With each revision, a manufacturer must provide current and
accurate documentation for those who use the device, whether they are other manufacturers or the end
consumer.
Product documentation has its own specialized requirements. Product documents must be completed
on the same manufacturing timetable as the corresponding product. Efficiency and time-to-market are
key motivators for product document creators—the less time the writer must spend on formatting, the
more time is available to ensure the accuracy and completeness of the content.
Finally, information must be delivered in a form the user expects. Many customers now expect
information to be available electronically, on CD-ROM, through online help, or via the Web. Electronic
distribution brings many business benefits, including a far lower cost than paper-based distribution, as
well as drastically reduced update cycle times. Multichannel publishing is a requirement for meeting
these distribution needs.
Manufacturing
Manufacturers deal with a tremendous stream of information that is critical to their profitable
operation. The kind of information they receive, manage, and generate includes:
• Documentation accompanying supplier-provided raw materials and components
• Documentation relating to equipment used in the manufacturing process
• Internal research and design documents, supporting product development and protection of
intellectual property and patents
• Internal documents supporting ongoing business operations
• Internal operating procedures ensuring efficient and safe working practices that meet regulatory
standards
• Marketing materials supporting the sales channel
• Maintenance documentation for the support channel
• Product documentation that is delivered to the customer
How information is created and managed can significantly impact the manufacturer. Proper
documentation on raw materials and components can affect the quality and cost of production, while
other internal documentation can affect business operations and planning. The accuracy and timeliness
of content that relates to safety, regulatory or customer-facing matters can be critical.
Manufacturing information must be managed and integrated into external product documentation, as
well as data-heavy catalogs and other information materials to support the sales channel. Producing
these materials is labor intensive, lead times are long, and conventional publishing formats such as paper
catalogs are expensive. Changes might take a year or more to appear in an annual paper catalog, and
much of the information is often rekeyed from an original paper copy.
• Managing and integrating information from a diverse array of sources to support the manufacturing
process and to provide documentation for manufactured products and components
• Integrating information from suppliers into the process
• Managing documentation about procedures and processes to meet certification requirements
Financial
The financial services sector creates, maintains, publishes, and distributes large numbers of documents.
These documents contain very dense raw financial data, and are extremely important for supporting
financial-based decisions. Consumers of this information are often key decision makers—investors,
corporate executives, investment fund managers, or members of the public—who need time-critical
support for determining actions and strategies. The financial publishing industry directly supports
homeowners in choosing a mortgage, investors in choosing stocks, and corporate executives in
providing the information they need to manage their organizations. Accuracy, legal validity,
predictability, and timely publication are also crucial in financial services.
The industry also is experiencing a growing demand for customized, personalized documents. Those
financial institutions that can quickly create personalized knowledge products have a competitive
advantage.
Information offered by the financial services industry tends to have the following characteristics:
• Financial data tends to be very personal in nature. Customers of financial information are generally
very particular about the exact types of information that they personally need.
• Financial data must be accessible. Users must be able to find the information they need quickly.
• Financial data must be accurate. Mistakes can lead to incorrect or misguided decision-making, with
potentially dire results.
The financial services industry is very competitive. Since financial information is considered a
commodity, many consumers seek out companies that can provide easy access to that information. For
example, a company without a Web portal is at a competitive disadvantage, since consumers of financial
data now expect the option of obtaining their information from the Web.
In summary, the business challenges facing the financial services industries include:
Adobe, the Adobe logo, and FrameMaker are either registered trademarks or trademarks of Adobe Systems
Incorporated in the United States and/or other countries. All other trademarks are property of their respective
owners.
In Section 2, “Identifying the Business Challenges,” we described (1) the challenges that
organizations face in creating, managing, and delivering information; and (2) the benefits of
properly managing information to improve decision-making, increase customer
satisfaction, decrease time to market, and reduce costs. Eight key business activities drive
the process:
• Take advantage of all possible avenues for minimizing costs
• Reduce the cycle time for delivery of new and updated information to customers and to
the field
• Decrease the time to market for content while maximizing quality and accuracy
• Provide on-demand information to those who need it
• Provide customized or personalized information where appropriate
• Provide consistent information, regardless of its source
• Provide a competitive advantage
• Meet regulatory and accessibility requirements at minimum cost
• Can the organization effectively maintain its intellectual capital? Can people find the information
they need to support their decisions, build on past experiences, and avoid redundant efforts?
• Can the organization integrate its publishing platform with its content management, supply-chain
management, or knowledge management infrastructures?
A “no” answer to any of these questions may indicate that the organization can improve its information
publishing processes. This section focuses on the business improvements that are available to
organizations that wish to pursue them.
Template-driven publishing
Authoring and publishing tools that support template-driven workflows maximize the content authors’
productivity and facilitate reuse and repurposing of content. Unlike design-driven publishing, in which
the author must explicitly apply formatting characteristics to each block of text, authors in template-
driven publishing environments “tag” each word, phrase, or text block with a style or format name (such
as “Bullet,” “Heading2,” or “ProductName”). The formatting characteristics of each style are specified in
a separate template. Because content tags provide information about the meaning and usage of each
tagged component, tagging facilitates easier interpretation of documents than is possible based on
appearance alone.
• Software applications can intelligently process content. For documents, this can mean the automatic
production of tables of contents, indexes, lists of figures, and other lists that assist the user in
navigating through the document.
XML-based solutions can provide personalized or customized content, drive interactive document-
based applications, offer rich server-based publishing solutions, and populate enterprise knowledge
management systems or supply-chain automation engines.
delivering information. In Section 2 we identified the business challenges for each area. Here we address
how organizations can meet those challenges by using conventional and reengineered approaches to
information management and publishing.
Solution requirements
Most vendors of XML authoring tools have ignored the “human” requirements of content creators:
• Author in XML without specialized XML knowledge
• Work in the easy-to-use WYSIWYG environment with familiar publishing tools (for example, spell
checking, book features, and graphics handling)
• Specify and control metadata (elements and attributes) using intuitive tools
• Easily validate XML content and fix errors
• Seamlessly publish content via conventional channels, including print, PDF, and HTML
Companies planning to deploy enterprise-wide XML authoring cannot ignore these requirements. If
they do, XML content will continue to be a niche or novelty item, created and used only by the few who
make the formidable investment in learning non-intuitive tools. These organizations will fail to realize
the substantial return on investment that enterprise-wide XML content management can provide.
Solution components
Building an effective enterprise-wide XML infrastructure requires the following components:
Authoring tool—The tool must present an intuitive word processing interface and features that authors
expect, and write valid XML for information reuse and repurposing.
Content management tool—The tool must present individual XML elements to authors for reuse
where appropriate. It also might perform workflow management and version control functions.
Multichannel publishing—An XML solution should easily enable publishing of XML documents via
numerous formats, including print and PDF.
Server-based publishing
Many organizations use a relational database to store content that must be published in a conventional
format. A catalog-based parts reseller, for example, must collect information from a vast number of
OEMs, organize and update it, and publish it in a variety of formats, including print, CD-ROM, and
Web. Other applications include personalized financial documents and customized eBooks.
Solution requirements
Server-based publishing solutions must meet the following business requirements:
• Create human-readable documents from information maintained in a database or delivered by an
application server or Web service
• Meet high standards of publishing quality (for example, layout and typography) for printed
materials
• Utilize rules to make appropriate layout and typography choices automatically, with minimal, if any,
human intervention at the moment of publishing
• Publish to print and to several popular online formats such as PDF, HTML, XML, and SGML
Database publishers rely on the enterprise database for creating and managing an organization’s content.
While databases excel at providing data entry tools, managing and maintaining data, and generating
reports, additional components are needed to provide the ability to create professional-quality
documents, in multiple output formats directly from the database.
Server-based publishing requires a publishing engine that tightly integrates into enterprise databases. It
must be capable of reliably processing thousands of pages of complex content. Its template-driven
publishing engine must ensure consistency in formatting database-published documents. Its ability to
provide multiple output formats must support publishing database content to the most appropriate
delivery format.
An enterprise database can provide a large number of diverse reports from a company’s data set. By
choosing a publishing tool that tightly integrates into enterprise databases, an organization can
customize the documents that it creates for its customers. This is especially useful for online-only
distribution formats, like PDF, HTML, or XML. An organization can provide the most up-to-date
information without re-editing content, and can deliver on-demand content to readers.
Solution components
A server-based publishing system has several key components:
Database—The database tends to perform the functions of validating, configuring, and assembling data
for publishing, and might perform pagination. It is typically designed by information architects and
maintained by database administrators. It could be relational or object-oriented.
Rendering engine—This system or application paginates (if pagination is not performed by the
database) and renders data for publishing. Some systems can publish to multiple output channels.
Communication layer—This interface provides communication capabilities between the database and
rendering engine. It can be a flat file system, if the database is writing files that are manually opened by
the rendering engine, or a customized application written using the API provided by the rendering
engine.
Database-driven publishing—Organizations using this model want to create and maintain their
content at a central point—the enterprise database. They are most interested in leveraging their
corporate content for multiple purposes. Again, at worst these organizations manually extract and
format database content for each purpose. They could benefit from an integrated solution that uses not
only the content of the database, but also the implicit structure of that content as stored in the database
Database publishing for multiple outputs—This model is for organizations that want to deliver
information in a variety of formats, including paper, HTML, PDF, XML, and SGML. These
organizations typically want the flexibility to create customized, one-time documents as well as mass
communications. This process avoids the terrible inefficiences of manual production work for each
output format.
Technical documentation
The challenge in technical publishing is to provide a complete and high-quality set of documentation for
a product or service, while meeting a variety of business demands (such as budget and resource
constraints) and schedule demands (dictated by product development).
Solution requirements
An effective technical documentation solution must meet these requirements:
• Reliably create the technical documentation to accompany products or services
• Effectively manage and publish what can be very large volumes of information, possibly spanning
thousands of pages for complex machines or software suites
• Manage document authoring and production so that documents follow the product development
and manufacturing timeline
• Reuse information that applies to multiple documents, such as documentation for many product
lines or models
• Integrate information from other applications, such as technical drawings, line art, or engineering
data
• Translate documents into other languages
• Publish in the formats that are most appropriate for the organization’s products, customers, and
business requirements
• Distribute updated content to the field in a timely manner
• Save money by deploying alternatives to print
Solution components
Technical documentation publishers need a solution with the following components:
Authoring tool—The solution must support integrating information from diverse sources and creating
structured documents. Multiple authors must be able to collaborate on a single publication, and the
solution must scale to support large volumes of documentation and be robust and easy to use.
Publishing platform—The solution must support multichannel publishing to print, PDF, HTML,
XML, or SGML, or one of several popular online help delivery formats.
Consider the experience of one company that used XML to create a set of interactive documents that
customers can use to instantly assemble tailored documentation. The company produces high-quality
XML content that matches the original structure of its documents. A template-driven authoring tool
helped to ensure the creation of consistent, professional quality documentation throughout the
company, providing easy-to-use controls for applying uniform attributes to fonts, paragraph styles, and
values. Adobe Acrobat® software and Adobe Portable Document Format (PDF) speed document review
and approval at the company and improve the quality and quantity of comments from staff.
Solution requirements
An effective information management solution can meet the following requirements:
• Share business-critical information across the enterprise
• Manage content workflows across projects and departments
• Support consistency in content contributors’ work and in output formats
• Exchange information in a common format (typically XML) with partners and suppliers, to support
supply-chain management and business-to-business communication
• Support information reuse
• Populate information portals
• Publish to appropriate formats (print, PDF, Web, HTML, XML)
Solution components
Authoring tool—The solution’s authoring tool must support content aggregation from a variety of
original source applications, and the creation of long, complex documents with extensive graphical and
tabular content. The tool should be template-based, to enforce consistency in internal and external
documentation and to free content authors from formatting tasks. In an XML-based solution, the tool
should support creation of rich XML content on every desktop and without specialized skills or
expensive add-on components. The tool should be easy to use, robust, and reliable, so it can be installed
widely without massive support requirements. It also needs to be affordable when purchased in volume.
Multichannel delivery—The system must be able to efficiently publish to multiple channels, meeting
demands as diverse as printed output, PDF, Web-based delivery, personalization, and delivery to
handheld devices. The best tools come with integrated ways to publish to the various media, and
support publishing to XML for personalization and other sophisticated delivery mechanisms.
Each of these vertical markets faces particularly interesting challenges. Together, they represent a broad
cross-section of publishing activities.
Aerospace
Aerospace shares many basic information-management requirements with manufacturing and other
industries that have a large publishing component. As information management needs grow, new ways
of creating, managing, and distributing information are necessary.
Solution requirements
Tools and architectures must be able to perform the following tasks:
• Manage vast amounts of information over the life span of each product
• Support content review cycles, ensure accuracy, and meet regulatory requirements
• Support content required for mission-critical operations, including manufacturing, training,
maintenance, and operations
• Integrate information from a variety of sources—engineering data, technical content, other text
• Publish information to a variety of media without redundant effort by content creators and with
maximum information reuse
• Reuse content across similar product lines and for shared components
• Maintain integrity of information at all phases of the information life cycle, including distribution
(distribute information in secure forms that cannot be modified by the receiver)
Solution components
The optimal information publishing solution for aerospace consists of these major components:
Authoring tool—The authoring tool must be either template-based, to ensure consistency in content
and format across similar documents, or XML-based, so authors can tag information components with
appropriate XML metadata. XML tagging supports rich content management and customization.
Furthermore, both template-based and XML authoring solutions allow easy format customization,
supporting information sharing and reuse among manufacturers and customers.
PDF delivery—The aerospace industry is highly dependent on PDF and print for online editing and
review of operation and maintenance documentation. Review in digital form can meet regulatory
requirements, automate data entry, and reduce paper dependency, thus cutting costs and saving time.
However, electronic devices do not yet provide the resolution and convenience of paper documents for
maintenance support.
Content management—This system should support reuse of information components from template-
based documents or XML document components. For example, a repair procedure may be cited in
manufacturing, training, and operation manuals.
Maintenance manual files from aircraft manufacturers are customized to meet an airline's requirements.
Airline engineers frequently make urgent updates to these manuals, which must reach the airline’s
worldwide maintenance mechanics as fast as possible. Tools supporting single-source information
authoring and turnkey multichannel publishing make this possible.
Solution requirements
An information management solution for the automotive and transportation industry must accomplish
the following:
• Convert engineering data into operational and maintenance data
• Manage and publish a variety of documents that support several activities (for example,
manufacturing, maintenance, training, and operation)
• Maintain consistency in appearance across document sets
• Manage and reuse information in multiple documents (such as product lines and models)
• Translate documents into other languages
• Integrate information from other applications (such as technical drawings, line art, or engineering
data).
Solution components
The optimal information publishing solution for the automotive and transportation sector comprises
these major components:
Authoring tool—The authoring tool might be either template-based, to ensure consistency in content
and format across similar documents, or XML-based, to allow authors to tag information components
with appropriate XML metadata. Either supports rich content management and customization of
documentation deliverables. The tool must be robust and able to handle large, complex documents, and
to incorporate diverse file formats, for reuse of materials such as engineering drawings.
Multichannel delivery—Exceptional multichannel delivery capabilities are crucial for this industry to
meet the expectations of its customer and maintenance channels. As printed information becomes
exorbitantly expensive, particularly training and maintenance materials, users are increasingly expecting
it to be available on the Web.
Content management—Many organizations in the automotive and transportation sector can benefit
from a solution supporting reuse of information components. For example, “changing a tire” might be a
reusable information component in operator manuals for many different vehicle models. Using an
XML- or SGML-based document production tool can increase content author productivity eight-fold
over a word processor tool. The XML or SGML rules engine identifies missing content pieces in each
document’s structure and automatically formats the document. Documents are consistent and high in
quality. Through multichannel publishing, information can be created and distributed in both printed
form and rich PDF files. Because the document’s content is structured, translators can create higher-
quality translations in less time than previously possible.
Government
Governments must create, collect, manage, maintain, and distribute tremendous amounts of
information for a wide array of purposes. They provide content in the form of public policy, laws and
statues, legal records, regulatory guidelines, general instructions, and forms.
Solution requirements
Government bodies have the following requirements for their information management tools and
infrastructures:
• Collect information from a variety of content contributors and software applications.
• Manage a large number of documents of various types.
• Distribute documents in a variety of forms (print, PDF, Web, CD-ROM).
• Distribute documents to the field (for example, regulatory agents) in a timely manner.
• Provide content that is accessible to everyone, including persons with visual or motor impairments.
Solution components
The information publishing solution for the government sector consists of the following major
components:
Authoring tool—Government authoring must support content aggregation from a variety of source
applications, and the creation of long, complex documents with large amounts of graphical and tabular
content.
Multichannel delivery—A publishing tool for the government should have exceptional capabilities for
generating PDF documents. This digital format provides the ability to create accessible, digital
documents with rich print capabilities for archiving and distribution purposes, especially important for
agencies that deal with the public and for crucial government regulatory agencies that must provide
updated content very quickly to affected parties.
Content management—Government bodies may benefit from a publishing solution that manages
content components for repurposing and reuse.
High technology
The high technology sector includes a diverse range of markets with a wide array of information
publishing needs. It has perhaps the broadest opportunities for process improvement and positive
return on investment from reengineering information management solutions, mostly due to the large
amount of information that supports a typical high-technology organization.
Solution components
Given these business drivers, we can propose the characteristics of the authoring tools and system
architectures that will meet these requirements.
Authoring tool—The authoring tool used by the high tech sector must be template-based, to improve
consistency across the corporation’s content. The tool should allow authors to incorporate information
from a variety of sources, supporting the reuse of content created in a diverse set of applications. The
tool should be robust in the face of thousands of pages of complex documentation, and should be easy
to install and administer.
XML authoring and publishing—High tech organizations need an XML authoring tool that empowers
all of the organization’s content contributors to create XML content. A tool that spreads XML
throughout that corporation can improve the value of nearly all corporate content—not just content in
niche areas, provided by specific contributors. This corporate-wide XML can expose opportunities for
improving knowledge management and supply-chain management, and for reusing corporate content.
Server-based publishing—High tech organizations that publish large amounts of content, such as
component catalogs, can benefit from a server-based publishing solution that pulls data directly from
application servers, database stores, Web services, or other data repositories. This solution also can meet
the needs for automatically creating customized and personalized information products.
Content management system—This system can improve knowledge management at the enterprise level
and support maintaining, sharing, and reusing valuable intellectual property across the corporation. It
also can improve decision-making by making relevant information available and easy to find, and
support identifying appropriate information for sharing with partners and providers.
Manufacturing
Manufacturers process and manage information from many sources, including suppliers of raw
materials, components, and equipment. They generate content internally for process control and
business planning. They create outward-facing sales materials, product documentation, and product
maintenance information.
Much of the information manufacturers receive is still in paper form, and must be rekeyed to create
internal and customer documentation—an error-prone, time-consuming, and costly process. In
addition, paper-based data does not flow through the manufacturing process as components do.
Manufacturers need information to flow in and to be repurposed easily for internal or external
documentation needs.
Solution components
An information publishing solution with these major components can meet these business
requirements:
Authoring tool—The tool must support content aggregation from a variety of source applications, and
the creation of long, complex documents with large amounts of graphical and tabular content. It should
be template-based, to enforce consistency in a manufacturer’s internal and external documentation, to
free content authors from formatting tasks, and to support the need for rebranding content contributed
by component suppliers. The tool also should support creation of rich XML content across the
manufacturing organization, without the need for additional software tools or training.
Server-based publishing—The architecture should support publishing parts catalogs and other data-
intensive materials directly from a content management system or database repository, which can yield
significant economic and resource benefits.
Multichannel delivery—Built-in multichannel publishing can free manufacturers from the expense and
lead-time constraints of paper publishing. Manufacturing organizations that have migrated hard-copy
catalogs to Web or CD-ROM distribution have realized significant benefits in cost, resource
requirements, and time-to-market for the catalog information.
Content management—Many manufacturers need to manage large amounts of content used for diverse
purposes and created by a wide variety of applications, and to support change control, reuse, and
repurposing of information.
Financial services
Financial services companies distribute large numbers of documents, each containing a high density of
raw financial data that is extremely important for supporting financial-based decisions. Consumers of
this information are often key decision-makers who need time-critical support for determining actions
and strategies. For example, the financial publishing industry directly supports homeowners in choosing
a mortgage, investors in choosing stocks, and corporate CEOs in managing their organizations.
Solution requirements
Financial services organizations have particularly strong requirements for publishing customized and
personalized on-demand content in formats that their customers expect.
Furthermore, documents published by the financial services industry frequently must meet legal
requirements. This sector requires an infrastructure that supports the creation of accurate, legally valid
documents in a predictable and timely manner.
Finally, the financial services industry is experiencing a growing demand for personalized documents.
Financial services institutions that can quickly create customized financial reports and other
personalized knowledge products have a competitive advantage over other financial services institutions.
Solution components
The optimal information publishing solution for the financial services sector consists of the following
major components:
Content management—Customers of the financial services industry expect highly customized and
highly personalized information. A content management system can support the creation of specialized
“information products” as an additional revenue stream.
Multichannel publishing—Given the industry’s highly competitive nature, financial services requires
excellent multichannel publishing support. Not only is the industry heavily dependent on print and
PDF, but also it must provide information to newer devices such as personal digital assistants (PDAs), to
meet the expectations of today’s and tomorrow’s customers.
A publishing system designed around an XML- or SGML-based data repository, in which financial
information is maintained and automatically extracted, consolidates the XML or SGML data with the
text portions of each document, automatically formats each document based on rules specified for each
document type, and publishes each document to print, PDF, and the Web. For one financial services
company, each of 2,800 subscribing institutions receives 11 credit opinion handbooks of more than
1,000 pages each. Production that once took four person-weeks of work now takes two person-days.
Adobe, the Adobe logo, Acrobat, and FrameMaker are either registered trademarks or trademarks of Adobe Systems Incorporated in the United
States and/or other countries. All other trademarks are property of their respective owners.
The rich feature set of Adobe® FrameMaker® 7.0 software makes it a key architectural
component for a variety of information management solutions. In sections 2 and 3, we
discuss the business challenges enterprises face in creating and publishing information, and
present the types of solutions that can meet these challenges. In this section, we show how
FrameMaker based architectures could help implement such solutions.
This section presents solutions in the following general application areas, along with the
business requirements of each.
XML authoring and publishing—Create XML content for driving Web applications or for
other XML-based applications. Provide a productive environment in which authors can
create richly structured XML documents without learning XML syntax. Manage XML
content for publishing and distribution. Create and publish customized XML documents.
Enterprise authoring and publishing —Create and maintain documents that support the
operation of an organization. Support the creation of consistent, reusable content. Provide
XML content that can be managed and reused.
The ideas and architectures presented here are presented as examples that have been chosen
to provide a broad perspective into the capabilities of the FrameMaker platform for
creating, managing, and delivering content for a wide range of applications. In some of
these application areas, we present several different architectures that cover a range of
functional and business requirements.
The FrameMaker user interface makes the product simple enough for people familiar with word
processing to learn the basics within a few minutes, but also provides access to the rich and powerful
features that professional documentation specialists require. Menus can be customized to add or remove
features, and new user-interface items (dialogs, palettes, and so on) can be created using the FDK.
The FrameMaker user interface can operate in two modes. Common style-tagged documents can be
created and edited in Unstructured mode. Structured mode provides a complete guided editing
environment for producing valid XML and SGML.
To assist visually impaired users, the user interface integrates with many of the accessibility features
available on the Microsoft® Windows® platform, providing keyboard shortcuts, high-contrast and large-
text displays, and compatibility with common screen readers.
The user interface is available in English, French, German, and Japanese localized versions. FrameMaker
runs on Windows, Macintosh, and UNIX® platforms with consistent interfaces.
FrameMaker also provides many text and graphics filters for importing and exporting, including
support for Microsoft Office formats (for example, Rich Text Format 1.6) and common graphics types
such as EPS, TIFF, JPEG, GIF, PDF, SVG®, and CGM. These allow FrameMaker to be used in an
enterprise environment where content is created and exchanged by numerous users employing many
different tools.
Template-based authoring
Documents can be created in many ways with a broad variety of authoring tools and processes. For
example, graphic designers for magazines use a design-driven workflow, where the components of a page
(such as the story title, the lead paragraph, the body copy, and the illustrations and photos) are
considered separate assets. Designers manually position and manipulate these components on
individual pages. Word-processing users, on the other hand, often follow a format-driven workflow. They
select text and manually format it by choosing a font size, applying a font, using line feeds to determine
space between paragraphs, and so on.
These workflow models require user skill and dedication to lay out the content correctly. The output of
these types of workflows tends to be channel-specific. For example, a magazine page or a word-
processing document is often inappropriately sized for other media such as the Web.
These issues can be effectively addressed by moving to a template-driven process model, which
FrameMaker supports at a fundamental architectural level. In this workflow, the format of the content is
controlled by a style sheet that is part of a template, which in turn controls the physical layout of the
finished publication. Users tag the content to identify components such as chapter names, words to be
emphasized, product names, cautions and warnings, and so on. The style sheet associates format and
layout information with these tags to ensure, for instance, that chapter names always start on a new
right-hand page and appear in 16-point centered Myriad® Bold type, with three line spaces between the
heading and the first paragraph of the text that follows. The template includes a set of style sheet
definitions plus one or more standardized master layout pages that apply consistent parameters for the
positioning of text and graphics on various types of pages (such as cover and contents pages, ad pages,
and inside text pages).
A template-driven workflow offers automatic, consistent formatting and layout of the content, reducing
the need for users to manipulate publication components manually.
• Full support for valid XML authoring and publishing, enabling integration with XML-based
applications and publishing to multiple formats via Extensible Stylesheet Language Transformations
(XSLT)
• Support for scalable vector graphics (SVG), allowing output of SVG source files to print and PDF,
and enabling integration of high-quality vector-based graphics for Web output
• Anchored graphics and tables that reflow graphic content as new templates are applied
• Conditional text feature—manage multiple document variants in a single file so that users can pick
and choose text, graphics, or tables for selected media
Each object on a FrameMaker page can be created, modified, or deleted through the FrameMaker API.
This is particularly powerful when integrating FrameMaker with other infrastructure applications such
as databases or content management systems. For example, a systems integrator or third-party solution
provider can write a FrameMaker API client to automatically extract database content, create
appropriate document objects for each item, and publish the result.
FrameMaker Server
FrameMaker Server can accept text and graphics in a wide variety of formats. It provides built-in
context-sensitive styling for XML-based textual content, and SVG for XML-based graphics generation.
Files for FrameMaker can be generated directly from other applications using MIF, or FrameMaker
software’s layout engine can be directly driven programmatically using the FDK.
Documents of any size or complexity can be handled by FrameMaker Server, from single-page invoices
to complex catalogs covering hundreds of thousands of pages. An individual book may contain
hundreds of chapters, each of any length and layout. Tables can span thousands of pages and millions of
cells, and a table cell can contain almost any document element, including graphics and other tables (via
built-in support for “anchored frames”). The FrameMaker document model supports cross-references
and automatic generation of multiple tables of contents and indices. FrameMaker Server provides the
same multilanguage support as does desktop FrameMaker 7.0, including Chinese, Korean, and Japanese
language content, and uses the same page-composition engine.
FrameMaker Server can be deployed with the desktop version of FrameMaker in a client-server
environment. This allows, for example, integration with a document management system where, as files
are checked in, they are automatically converted to PDF by FrameMaker Server. When working with the
desktop version of FrameMaker in a client-server environment, FrameMaker Server can accept files in
FrameMaker software’s binary file format.
FrameMaker Server is applicable to a wide variety of industries and applications, including these:
• Banking and finance
• Insurance
• Investment fund management
• Directory publishing
• Book and eBook publishing
• Industrial catalogs
• Health care
• Complex billing systems
• Government volume publishing
MIF provides an intermediate format for manipulating FrameMaker documents programatically, via an
external application. Text documents are relatively easy to generate, parse, and manipulate. The MIF
language and syntax are thoroughly documented in the Adobe MIF Reference, provided as a PDF
document with FrameMaker (see Section 10 of this Solutions Guide for more information on MIF
documentation).
The MIF application integration format can be employed for a number of purposes. For example, a
database publishing application may extract and wrap database content in the appropriate MIF code for
automatic publishing. Likewise, application-generated data (perhaps from a monitoring application or a
Web service) may be translated to MIF for publishing via FrameMaker. Other types of automatic
processing that MIF enables include replacing book-specific cross-references with hyperlinks for online
viewing; globally modifying the relative target of document hyperlinks; and inserting content from a
database or application server into a FrameMaker document.
• Reading and writing the XML document type definition (DTD), which specifies the XML tag set
and legal structure of an XML document, and validating XML content against a DTD during the
authoring process
• Guided editing—at any given place in the document, FrameMaker in Structured mode presents
elements to the author that are legal in that context
• Automated conversion of unstructured documents to XML, based on existing paragraph and
character formats, allowing the author to “tag” unstructured content with XML mark-up
• Word processing and WYSIWYG
• Rich formatting on the printed page and PDF file via FrameMaker Element Definition Document
(EDD) and templates
• Round-tripping—exporting XML documents and reimporting them later for further editing or
publishing
• Mapping between XML elements and FrameMaker objects via read-write rules, with further
customization supported via the Structured API
FrameMaker API
The FrameMaker API completely exposes FrameMaker software’s functionality and document model,
and provides a mechanism for automating FrameMaker and integrating it with other applications. It
supports creation of C-language programs, called FDK clients, that can take control of a FrameMaker
product session and communicate interactively with the user. With the API, a client can do anything an
interactive user can do, and more. The API gives a client direct access to the text and graphic objects in
documents. It includes a set of header files, libraries, and makefiles for each supported platform. These
and other types of clients can be created with the FrameMaker API:
• Automated publishing from databases and application servers
• Content management utilities
• Filters to exchange files between FrameMaker products and other desktop publishing applications
• Grammar checkers
• Bibliography utilities
• Voice-control utilities
• Document-reporting utilities
• Version-control systems for documents
• Table utilities, such as sorting and totaling
Structured API
The FrameMaker Structured API provides control over the import and export of XML and SGML
documents to and from FrameMaker in Structured mode. With the Structured API, FrameMaker clients
can parse XML and SGML documents and associate XML and SGML elements with the FrameMaker
application’s document objects for automatic rendering and publishing. Developers should build
database publishing applications with the Structured API when the database or other content-
generating application presents content as XML and SGML mark-up.
Accessible documents
FrameMaker users easily can create documents accessible in many ways to visually impaired people.
• Through the FrameMaker template-based single-source multichannel publishing support, large-
print editions and a tagged PDF that can be reflowed for a variety of reading devices can be output.
• Conditional tags can be used, for example, to swap a low-contrast image in a document for a high-
contrast image in large-print versions of the document, or even to replace the image altogether with
a text description for visually impaired users.
• Authors can provide alternative text tags for graphics output to PDF and the Web.
• Documents can be output as raw text for input to accessibility tools that require ASCII text files.
• Template-driven HTML conversion capabilities allow generation of multiple versions of a Web site,
including a version with large font sizes and high-contrast graphics or accessibility tags.
• Valid XML output can be transformed with XSLT to generate accessible file formats such as
VoiceXML.
In Section 2 we identify the business challenges for each area, and in Section 3 we address how
organizations can meet those challenges by using conventional and reengineered approaches to
information management and publishing. Here we look at detailed architectures for creating
FrameMaker-based publishing systems in each area, and we present an example from one of the six
vertical markets we are examining in this Guide—aerospace, automotive and transportation,
government, high technology, manufacturing, and finance.
Architecture overview
The three key components of an XML authoring and publishing solution are content creation,
rendering, and publishing and distribution.
Content creation
Authors can create content in a familiar word-processing environment, integrating information as
needed from various application and graphics formats with FrameMaker 7.0 software’s template-driven
authoring and document structuring capabilities.
FrameMaker 7.0 hides the details of XML from authors, eliminating the expensive need to train authors
in XML syntax. Authors are free to do what they do best—create content for the organization. Contrast
these features with other popular XML editors, many of which lack even the most basic word-processing
features and are designed for creating data, not documents.
Rendering
Generating richly formatted printed or PDF documents from XML is not a trivial task. Again, many
popular XML editors provide no capability for doing this, or require additional expenditures to make it
work. The FrameMaker 7.0 XML authoring environment is combined with a professional print
rendering engine. Through FrameMaker 7.0 software’s Element Definition Document (EDD), or
through the FrameMaker API, FrameMaker 7.0 can format XML documents based on their XML
structure.
The EDD is where template designers associate formatting characteristics with XML elements. It allows
very powerful formatting specifications, including context-sensitive formatting and formatting based on
the value of attributes in the XML content. For example, a second-level numbered list should have
different format characteristics from a first-level numbered list, such as numbering style and indent.
These distinctions are specified in the EDD and are applied automatically when an XML document is
imported.
Most other products require complex mechanisms to format XML documents for print or PDF, based
on immature technologies. FrameMaker software’s EDD allows template designers to apply the same
skills that they use when designing FrameMaker templates to create EDDs for formatting XML or SGML
documents.
FrameMaker allows authors to create structured or content components (fragments of XML content) as
well as structured documents. The FrameMaker XML export feature controls the output, and the XML
can be used as a basis for these and other applications:
• XML Web pages
• XML Web applications (such as interactive content learning systems)
• Custom XML documents that are not Web-based
• XML content management systems that manage and distribute XML content
PDF
A crobat Reader is available on many platf orms,
W Y SIW Y G including W indow s, M ac, UNIX , Palm, and W indow s CE
editing
environment
HTM L
FDK
clients
FrameM aker
.fm, .mif
PDF .mif .mif
SGM L XM L HTM L HTM L W eb brow ser
XM L WML WML
Many XML-based applications use the capabilities of the XML transformation language (XSLT). XSLT is
language specified by the World Wide Web Consortium (www.w3.org) for manipulating and
transforming XML documents:
• XSLT selects and sorts specific parts of an XML document based on XML metadata; often used to
create specific versions of an XML document for specific audiences
• XSLT transforms XML to other languages; for example, to HTML for display in a Web browser, to
Wireless Markup Language (WML) for display on a mobile phone’s screen
XML can also be dynamically manipulated in Web applications via the XML Document Object Model
(DOM) and technologies such as Active Server Pages (ASP).
FrameMaker can be integrated with a database or other data sources to provide a user interface for XML
content authoring and editing. XML documents or content components can be manually imported into
FrameMaker, or automatically imported using third-party database integration products or the
FrameMaker API. FrameMaker assembles, renders, and publishes the final content. Much more than
simply a structured authoring tool, is a powerful platform for integrating, rendering, and publishing
XML content.
Using FrameMaker software, content authors can create XML content without learning XML syntax.
FrameMaker meets the industry’s need for print and PDF distribution by providing print capabilities on
every desktop, without requiring complex add-on software or immature technologies to print XML
documents. Finally, FrameMaker provides built-in multichannel distribution capabilities.
Server-based publishing
The FrameMaker 7.0 architecture is a rich platform that provides integration and data management
options with many types of data sources, including databases, repositories, and data-sharing
applications. FrameMaker 7.0 supports direct interaction with a database, transforming the information
into professional-quality published documents. FrameMaker 7.0 software’s full book management
capabilities can handle documents of several thousand pages and formatting such features as running
headers and footers, cross-references, and tables of contents.
Template-driven FrameMaker software automatically can format information as it comes from the
database, with no human intervention, and deliver it in the formats the organization needs, including
print, PDF, HTML, XML, and SGML.
FrameMaker software's API enables complete integration with the database, application server, or Web
service. FrameMaker can play any of these roles in a server-based publishing application:
• Configure and assemble data, controlling data acquisition from the data source; for example, the
FrameMaker API can query a database via a database protocol
• Paginate and render (layout) data “pushed” to FrameMaker by the database
• Convert data from the database; for example, to XML, HTML, or SGML
Architecture overview
A database publishing architecture has four key components:
Content creation, selection, and management—Content can be created from the database, or via a
combination of database-hosted data and FrameMaker input.
Content selection—A tool to query, organize, link, and deliver content to FrameMaker. The database
could drive this via its query mechanism, or FrameMaker can query the database via the FrameMaker
API.
Content rendering—There are several options: XML from the database can be imported into
FrameMaker; a FrameMaker client can extract data to populate an object in a FrameMaker document;
or a database can call FrameMaker and populate a FrameMaker object.
Multichannel publishing—Publishing can be to PDF, XML, HTML, SGML. Some or all data could be
published back to the database. Figure shows the typical interaction of these components.
Database
lorum epsom lorum epsom Section 3: Meeting the Business Challenges Section 3: Meeting the Business Challenges
FrameMaker content easily can be delivered to a database for storage and maintenance. Designed to
organize information, FrameMaker lends itself to mapping to database structures and behaviors. For
example, the element and attribute model of FrameMaker in Structured mode closely parallels the basic
data objects found in a database. In a FrameMaker environment, frequently some database content is
created in FrameMaker, and some comes from a manual data entry system or is computer-generated
from another application.
Database
Adobe FrameMaker 7.0 Solutions Guide 3-1
Database publishing applications may fall into one of these two categories:
Data-centric—This category includes financial documents that consist primarily of numerical data in
tables. Whether manually entered into database form or generated by an application, this data can be
maintained at the database. No word-processing component or document-centric content management
system is required.
When designing a solution’s content creation component, developers need to assess how much of the
published information is text and how much is raw data.
Content rendering
Several options exist for importing and rendering database content:
FrameMaker
Server 7.0
• Write database content as MIF and then import it into FrameMaker for automatic rendering.
• Directly extract database fields via the FrameMaker API and database interface language (such as
ODBC), then translate database content to appropriate FrameMaker document objects.
• Export XML or SGML from database, then import it into FrameMaker in Structured mode. Format
the content via rules encoded in the EDD.
FrameMaker software can automatically render content based on its structure. Third-party or
customized products can wrap content from a database or application server in appropriate MIF
statements for rendering by FrameMaker. FrameMaker can be integrated with a database via FDK to
create a turnkey system in which FrameMaker automatically queries the database or application server
and converts the returned content to FrameMaker objects. Furthermore, XML can provide an
intermediary format between a database or application server and FrameMaker. FrameMaker can open
XML documents and render their contents as FrameMaker document objects.
When implementing a database publishing architecture, developers should first map database objects to
the FrameMaker template via paragraph and character styles, Creating XML or SGML from the database
and importing to FrameMaker 7.0 allows for rich rules-based formatting using the FrameMaker EDD
and also provides other reuse options for the XML output.
Multichannel publishing
The appropriate publishing channel depends on the desired output and audience. PDF provides richly
formatted output that can be delivered on demand via HTTP, on CD-ROM, in another online format,
or in print. HTML and XML are Web-centric formats that also can be delivered on demand. Print is the
most expensive and slowest distribution format, but is demanded by many industries and applications.
If the output from FrameMaker Server is a binary FrameMaker file, then final rendering and publishing
of database content can be totally automated with FrameMaker Server, or performed through
FrameMaker 7.0 on the desktop to enable quality checking or final customization.
Technical documentation
Technical publishers need to create complex, dense, and often very detailed content that must be highly
organized and controlled. Technical documentation consists of more than text; it also includes
procedures, specifications, and reference materials, one or more tables of contents, lists of figures, tables,
equations, running headers and footers with text and page numbers, and usually one or more indices.
Technical documents frequently are books, with separate (and possibly separately maintained) chapters
or sections, and typically include cross-references within the document and to figures, tables, and other
supporting materials.
Numbering of components in technical documents is a major issue. Not only do technical documents
have numbered pages, but also they are likely to have numbered tables, numbered figures, numbered
equations, and numbered (or procedural) lists. Numbered lists could be nested within other numbered
lists, in which case a subnumbering scheme is required.
Each component of a technical document can present a substantial challenge to the author. Support
from a professional authoring tool is crucial. The author should not have to set up these components,
verify that they work correctly before the document is published, and inevitably fix problems when they
break.
FrameMaker 7.0 software’s template-driven publishing model, with the ability to aggregate content from
a variety of sources and publish to multiple channels on a robust platform, make it an excellent choice
for technical documentation.
Architecture overview
Consider the following scenario for creating, managing, and delivering technical documentation:
• Authors check out appropriate content from WebDAV-enabled content management system.
• Content management system manages approvals.
• Publish to PDF using Adobe Acrobat® and HTML using WebWorks software.
• Distribute content globally via HTTP.
FrameMaker 7.0 supports this scenario’s requirements with the following architecture:
• Full-featured, robust professional authoring
• Flexibility with source files
• Multichannel publishing
• Content management
lorum epsom
lorum epsom
Technical documents
FrameMaker architecture for technical documentation
Because the FrameMaker book architecture manages the sections or chapters that form a book without
loading all book components into memory, FrameMaker is exceptionally robust and well performing,
even when only a limited amount of system memory is available. Many other authoring tools load all
book components into memory, decreasing both performance and reliability. In addition, FrameMaker
can reliably and efficiently handle documents of several thousand pages.
Likewise, graphic information including line art, flow charts, screen shots, illustrations, and schematics
are typically included in a technical document, and must be easy to place and to update. FrameMaker
easily manages graphics in a large number of popular graphic file formats.
Multichannel publishing
The FrameMaker 7.0 solution includes WebWorks Standard Edition software, which provides additional
publishing capabilities beyond print and PDF, including templates for HTML 3.2, HTML 4.0
(DHTML), XML, Microsoft® Reader, and Palm Reader. The optional WebWorks Professional Edition
also provides online help formats.
FrameMaker 7.0 software’s graphics-handling capabilities include integration of the XML scalable vector
graphics (SVG) format. For print and PDF, FrameMaker 7.0 automatically rasterizes SVG graphics at a
selectable resolution. For HTML, XML, and SGML, the rasterized version can be output or the original
SVG code can be passed through, thereby streamlining the process of publishing text and SVG-based
vector graphics directly to the Web, and supporting additional SVG scripting functionality—particularly
useful for complex diagrams or interactivity.
FrameMaker automatically produces Web-safe GIF, JPG, and PNG versions of any graphics format. This
eliminates manual graphics conversions, easing the print-to-Web conversion process. Users can exercise
a high level of control over HTML output, such as the way large documents are divided into logical Web
pages. Using Adobe GoLive® software, users can easily modify and customize the professional-quality
templates included with WebWorks Publisher. TMicrosoft Reader and Palm Reader formats are included
to enable complete control over content look and feel on these devices and platforms.
FrameMaker 7.0 for Windows® and Macintosh includes Acrobat Distiller® 5.0, which generates PDF 1.4
and distills documents from within FrameMaker. PDF file generation is supported on the Solaris™, HP,
and AIX® platforms. Tagged PDF creation is now supported, facilitating high-quality viewing on next-
generation PDF applications as well as improved accessibility for visually impaired users.
FrameMaker 7.0 also supports the Extensible Metadata Protocol (XMP) standard for describing asset
properties to increase their usability in a collaborative production workflow, which enables highly
effective work with content management systems.
Authoring tools
FrameMaker 7.0 can save to many file formats, including Adobe PostScript®, PDF, HTML, XML, and
SGML. Numerous application filters enable document export and import between FrameMaker and
Microsoft Rich Text Format, ASCII text, Microsoft Word, WordPerfect, and other platforms.
Content management
Technical documentation publishers should consider employing a third-party content management
system to maximize the value of their information resources and leverage reuse of their content. A
content management system can provide the following capabilities:
Source management—Organizing, associating, and importing many source files in formats created by
multiple applications.
Content identification—Labeling documents and their components so that authors can identify and
reuse content.
Workflow support—Generating automatic change notifications to everyone who needs them, avoiding
costly production errors that can occur when appropriate manual notifications do not take place. The
product development team can be notified automatically when a relevant document has been created or
modified. The editorial or production team can be notified automatically when a document is ready for
the next stage in the production workflow.
Commercial content management solutions fulfill these capabilities in several different ways. Some store
FrameMaker documents as binary objects, without modifying the FrameMaker binary file format.
Others parse FrameMaker content, convert it to an application-independent language (XML or SGML),
and store it so its elements can be reused anywhere.
Manage large amounts of information at several levels—Keep document content and format
consistent through FrameMaker software’s template-based authoring. Manage book-length documents
through FrameMaker software’s book-handling features. Integrate with content management systems
enterprisewide.
Repurpose information by publishing in a variety of print and online formats from the desktop—
Use XML to further increase publishing options.
Maximize quality and minimize cost with a robust authoring tool that allows authors to focus on cre-
ating content and rely on document templates for consistent formatting—Use template-based
authoring for working with source file formats, and provide XML and multichannel publishing
capabilities in a single package.
Deploying a reliable, maintainable, and extensible enterprisewide solution requires as much workflow
and process design as technical and infrastructure design. We will discuss both solution categories here.
Architecture overview
The FrameMaker platform provides a powerful business architecture for enterprise authoring and
publishing. Just by deploying FrameMaker 7.0, an organization can dramatically improve its capabilities
for creating, managing, and delivering the internal content that drives any business.
Content creation
Because FrameMaker software is template-driven, content authors can create consistently structured
documents without worrying about formatting details. FrameMaker also can also incorporate content
from a variety of sources, including Microsoft Word and many popular graphics formats. If XML
content is required, authors can use FrameMaker in Structured mode. Workflows can be flexible and
metadata can be used to identify content for reuse throughout the organization.
Content management
Especially for large volumes of content, version-control issues, source management, document
management, and security are critical. Automated workflow can also provide additional efficiencies in
larger organizations. Content management issues in the enterprise are similar to those in technical
documentation (see page 4-17).
Generating richly formatted printed or PDF documents from XML is not a trivial task. Many popular
XML editors provide no capability for generating PDF or print documents, or require additional
expense.
FrameMaker and FrameMaker Server provide an XML authoring environment combined with a
professional print rendering engine. FrameMaker can format XML documents based on the XML
structure via the FrameMaker EDD, while and render it XML document through the FrameMaker API.
FrameMaker 7.0 for Windows and Macintosh includes Acrobat Distiller 5.0, which generates PDF 1.4
and distills documents from within FrameMaker. PDF generation is supported on the Solaris, HP, and
AIX platforms. PDF files can be tagged, facilitating high-quality viewing on next-generation PDF
applications as well as improved accessibility to visually impaired readers.
lorum epsom
lorum epsom
lorum epsom
Further efficiencies are possible. If suppliers, manufacturers, and buyers agree upon a standard set of tag
names in their FrameMaker templates, each with formatting characteristics unique to the individual
organization, documents can be converted to different page layouts simply by using the organization’s
own template.
Adobe, the Adobe logo, Acrobat, Distiller, Frame, FrameMaker, Myriad, and PostScript are either registered trademarks or trademarks of Adobe
Systems Incorporated in the United States and/or other countries. Macintosh is a trademark of Apple Computer, Inc., registered in the United
States and other countries. HP is a registered trademark of Hewlett-Packard Company. AIX is a registered trademark of IBM Corporation in the
United States. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or
other countries. Palm OS is a registered trademark of Palm, Inc. UNIX is a registered trademark of The Open Group. Solaris is a trademark or
registered trademark of Sun Microsystems, Inc., in the United States and other countries. SVG is a trademark of the World Wide Web
Consortium. All other trademarks are property of their respective owners.
This methodology will assist in identifying and understanding the core components and
behaviors of the products to be evaluated. Buyers will discover how a particular tool would
work in the context of project or organizational requirements for a workgroup or
enterprise. These criteria support the evaluation team in considering not only each
product’s feature set, but also equally important considerations such as usability,
performance, extensibility, reliability, and maintenance and support.
We have identified 12 evaluation criteria for enterprise authoring and publishing tools:
• Usage areas
• Feature set
• Usability
• Performance
• Workgroup capabilities
• Accessibility
• Ecosystem and adoption
• Extensibility
• Reliability
• Purchase options
• Maintenance, support, and upgrades
• Return on investment
After employing these evaluation criteria, the following assessments will be possible:
• Impact of change and evaluation of risk
• Acceptance of new software and systems
• Head-to-head feature and performance comparisons
• How well new software and systems meet functional and organizational requirements
Evaluation process
A well-defined evaluation process is crucial to the goal of obtaining ample data of sufficient
quality to support the decision-making process. If evaluations are based exclusively on
feature comparisons, the selected tool might offer short-term benefits but long-term
limitations.
The software evaluation process may be undertaken by a single person or, more likely, by a
team. Consider these factors when determining the composition of an evaluation team:
• Number of applications and solutions to be evaluated
• Skills and background of the team members
• Amount of time each team member can devote to the evaluation process
• Number of different segments (departments, divisions, workgroups) within the
organization that will be affected by the new system
In planning and executing the evaluation process, a team might create the following supporting
materials:
• A matrix for comparing the features of different applications (seepage 5-8 pages 5-8 —5-10 for a
sample)
• Architecture diagrams that define and constrain the components to be evaluated
• Proof-of-concept systems that build implementation experience for the team members
• Lists of qualified vendors that offer products, solutions, or services to facilitate information creation,
management, and delivery
After all items are rated, adding the values quickly gauges how well a solution meets the criteria. Key
items also might have an additional weight factor assigned . For example, if WYSIWYG (What You See Is
What You Get) is a critical feature and it is in the software or solution, factor a +10 rating by +5 to
increase it to +15.
Planning ahead
The information collected during this process can be detailed. These issues should be resolved before
requests go out to providers:
• Who creates the request? Who reviews it?
• How will the responses be collected and tallied?
• How will the responses be weighted?
• Who will evaluate the results (committees, subject matter experts, others)?
• How will the evaluation deal with conflicting or missing information?
• How will the evaluation deal with responses indicating that it might take more than one vendor to
provide a complete solution?
• How will follow-up questions be communicated to each respondent?
Evaluation criteria
Usage areas
It is important to evaluate the software not only for its features and capabilities, but also in the context of
the systems or solutions into which the software must integrate. For example, if one or more of the
following application areas are important—database publishing, technical documentation, XML
authoring and publishing, server-based publishing, or enterprise authoring and publishing—evaluate
each product with respect to its capabilities in that specific application area. Evaluation criteria for each
application area are included in the following sections.
Database publishing
The solution being evaluated might need to be the mechanism to query a database, import markup,
organize data, or render and deliver content, or it might be integrated into a larger database publishing
system as the rendering component. For deployment in this application area, the software must:
• Be easily configured into a database publishing solution
• Have an API and developer environment
• Allow for control (via the API) of all document and object elements
• Enable the user to easily control design, process, output, and delivery
Technical documentation
For suitability in a technical publishing environment, a software application must:
• Be recognized as a professional tool in the technical publishing industry
• Be reliable in mission-critical environments
• Provide the ability to control and organize dense technical data
• Support the import of differing content and the output of common delivery data formats
Feature set
Software must meet a minimum set of feature requirements to enable users to perform their tasks,
whatever those tasks might be. Feature-set evaluations tend to be simple but tedious, often consisting of
comparison tables that present the differences between products.
Features and functions need to be evaluated not only on their presence or absence, but also on their
performance and usability. For example, identifying that an application has a table-building feature does
not indicate the robustness or ease of use of the feature. Furthermore, some applications provide certain
features only at additional cost. It is appropriate to consider whether the additional cost of a given
feature is worthwhile when evaluating applications that use this pricing model.
The sample matrix beginning on page 5-8 provides a list of features that the evaluation team might want
to consider.
Usability
Software must be easy to use. Complex software increases training time, development time, resource
requirements, and operation costs.
WYSIWYG applications have resulted in large productivity gains for content publishers. By viewing the
content as it develops, users can predict and anticipate the process and save considerable time and effort.
In addition, quality and accuracy are greatly improved because the user is working in real time and can
see the final product immediately.
Managing the application components is also important in evaluating usability. A simple application
with integrated components that are all based on the same architecture and workflow reduces the
complexity of the application and leverage the skill and knowledge that the user develops. For example,
Adobe FrameMaker software’s structured rules document, the Element Definition Document (EDD), is
a FrameMaker structured template that uses the same end-user authoring skill for defining and for
validating rules. In addition, the EDD also includes formatting rules that specify how each element will
be rendered, so a separate style document does not have to be built in a different application.
Easy-to-use software increases productivity, quality, and accuracy. Here are some questions to ask when
evaluating software usability:
• Does the software have a user interface similar to other programs on the same platform?
• Is the software WYSIWYG?
• Does the software have an organized, easy-to-learn user interface?
• Can the user customize the user interface?
• Are the software’s menus and commands positioned in predictable locations and do they behave in a
predictable manner?
• Does the software provide keyboard shortcuts, and are the shortcuts easy to learn and use?
• What are the minimum computer skills required to use the software?
• Are skills learned from other software applications applicable to this software?
• Does the software provide appropriate options and feedback to the user?
Performance
Performance comprises the response time of commands, functions, and behaviors. These must meet the
enterprise’s minimum acceptance criteria. Develop performance tests that relate to real-world data. Test
documents that represent a range of document sizes and complexities that users will create, edit, and
publish.
Be flexible in interpreting the responses on performance questions. Different tools work in different
ways. Performance bottlenecks in one method can often be solved by using a tool slightly differently.
Workgroup capabilities
Workgroup and enterprise capabilities are critical for supporting effective information management
solutions. The software should provide workgroup features that will maximize the productivity in a
collaborative work environment, including both desktop and server capabilities.
Accessibility
Accessibility is critically important to both content developers and end users of the data product. The
software must provide visual and audio enhancements to support users with vision or motor
impairments, and must be capable of producing content that does the same.
• How easy is it to find consultancy services, deployment and customization services, and training
services?
Extensibility
The software must be evaluated on the ability of its features and behaviors to meet additional
production and processing requirements as they develop. Consider the following when evaluating
extensibility:
• Does the software provide a robust API to enhance its features and behaviors and enable integration
with other applications?
• Does the software provide a software developers’ kit?
• Are training and support available?
• Does the software have a scripting language or another mechanism for automating user tasks?
• Can the software be integrated with other software applications?
Reliability
Reliability is difficult to measure directly. It is often based on a product's reputation. Useful reliability
information is often found in case studies, user forums and product reviews. These questions should
elicit a positive response:
Purchase options
The software can be evaluated on the purchase options provided by the software vendor and its resellers.
Small workgroups and publishing organizations may require smaller up-front purchases, and then build
to a larger deployment after the first project is deployed. An enterprise may choose to evaluate large-
purchase discounts and license management services. Consider the following questions:
• What are the different purchase options?
• Do the purchase options support the size of the workgroup or organization?
• Do maintenance options provide for automatic updates and upgrades?
Return on investment
Cost reductions are not just attributable to lower software acquisition costs. Improvements in
productivity and turnaround result in time savings that translate into additional productivity and
reduced project costs. Fewer errors improve productivity. Easy-to-use WYSIWYG software reduces
project training and support requirements. A simplified development environment and a stable and
reliable application hold down the cost of developers and support staff.
Often the acquisition and implementation costs of a new system are evaluated against the savings,
improvements, and increased revenue during the first 12 to 24 months. Consider the following
questions when evaluating return on investment:
• When will users become productive on the new software?
• Can the migration process be implemented over an extended period of time?
• What are the projected cost savings in software, training, support, and staff?
• What are the projected productivity gains of higher quality, fewer errors, and faster turnaround?
• What are the projected revenue streams from new data products?
Column control
Master pages
Reference pages
Paragraph styles
Character styles
Thesaurus
Pagination
Integrated structure
Auto-generated index
Embedded documents
WebDAV integration
HTML
SGML
SVG
JPG
GIF
TIFF
EPS
HTML
SGML
SVG
JPG
GIF
Ease of use
Tagged PDF
Article threading
Automatic bookmarks
OS Macintosh
compatibility
UNIX®
Windows®
Training
Contractors
Adobe, the Adobe logo, Acrobat, Frame, FrameMaker, and GoLive are either registered trademarks or trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Companies profiled in these success stories are some of the most successful in their
industries in the world. These quotes describe how a few of them benefited from
FrameMaker:
• “To become more efficient, we want to move from a paper culture to an electronic one.
FrameMaker makes the transition easier by providing a single authoring environment
for producing documents for print or publication online in Adobe Portable Document
Format (PDF).” (American Airlines)
• “The ability [of FrameMaker software] to reuse content, generate indexes, create tables
of contents, and build in cross- references allows us to quickly develop lengthy, easy-to-
navigate documentation.” (Bombardier Transportation)
• “With shrinking product design cycles, faster time-to-information, and resulting faster
time-to-market are not just nice benefits for our customers, they are a business
imperative. By eliminating steps from production, FrameMaker supports a mission-
critical process.” (Hitachi)
• “The primary financial benefit is that with SGML we can produce three deliverables—
paper, CD-ROM, and Web—without any incremental costs beyond producing paper
only. Before we had SGML capabilities, it took two people four to six weeks to convert a
document to SGML in preparation to put it on the Web.” (Xerox)
• “Cisco calculates its savings from publishing electronically as approximately US$50
million a year. FrameMaker and Adobe Acrobat® combine to create an easy, attractive,
economical solution for electronic publishing.” (Cisco)
• “FrameMaker support for XML is instrumental in allowing us to quickly assemble
customized, detailed documentation. With FrameMaker and XML, we can create one
set of interactive documents that our staff and customers can use to build materials
tailored to their needs. The combination of Adobe software, Web technologies, and
wireless communications are helping us redefine what it means to have immediate
access to relevant information.” (Marconi)
• “Some of the software we looked at offered ease of use, but only for specific outputs,
such as HTML or Windows® Help. Others offered powerful SGML functionality, but
were difficult to learn and use. Only FrameMaker provided both: the power of SGML
and the ease of use our authors expected.” (Novell)
For each story, the business driver(s) that led the organization to the FrameMaker platform are
indicated:
• XML/SGML authoring and publishing
• Multichannel delivery
• Delivery of interactive document-based applications
• Customization and integration via the Frame® Developer’s Kit (FDK) or Maker Interchange Format
(MIF)
• Automated publishing
To access a success story, click the company name in the matrix and download the PDF file.
Note: Several of the case studies discuss the Adobe FrameMaker+SGML product. FrameMaker 7.0 replaces
and includes all features of FrameMaker+SGML.
Vertical XML/SGML
Organization Multi- Integration
market authoring Interactive Automated
channel via FDK or
and applications publishing
publishing delivery MIF
Gables Engineering X X X
McDonnell Douglas X X X
Druckhaus X X
Waiblingen
Vertical XML/SGML
Organization Multi- Integration
market authoring Interactive Automated
channel via FDK or
and applications publishing
delivery MIF
publishing
Hitachi X X X
Semiconductor
(America), Inc.
IBM Personal X
Systems Group
Motorola X X
Semiconductor
Products Sector
Cisco Systems X X
Fujitsu Network X X
Communications
Marconi plc X X X
Novell
Laitram X
Corporation
USDATA X
Xerox X X X
Carnegie Mellon X
University
Financial Fidelity X X X X X
services and Investments, U.K.
insurance
Moody’s Investors X X X X X
Service
SAFECO X X X X
National Heritage X X
Insurance Company
Adobe, the Adobe logo, Acrobat, Frame, and FrameMaker are either registered trademarks or trademarks of Adobe Systems Incorporated in the
United States and/or other countries.
Additional third-party solution providers are listed at the Adobe Partner Web site at
http://partners.adobe.com. In addition, Section 11 of this Solutions Guide provides a list
of resellers that sell FrameMaker and FrameMaker Server and provide training, consulting,
integration, and customization services.
Partner matrix
The companies listed here have provided information about their services to Adobe for publication.
Each company operates as a separate entity and is affiliated with Adobe only as a partner.
Note: Throughout this section, U.S. regions served are indicated as follows: northeast (NE); northwest
(NW); southeast (SE); and southwest (SW).
Automotive/Transportation
Value-Added Reseller (VAR)
FrameMaker development
Partner
Software manufacturing
served
FrameMaker integration
Consultant to industry
Database publishing
Technical publishing
Legacy conversion
Plug-in provider
Manufacturing
Government
Aerospace
High-tech
Financial
Training
Automotive/Transportation
Value-Added Reseller (VAR)
FrameMaker development
Partner
Software manufacturing
served
FrameMaker integration
Consultant to industry
Database publishing
Technical publishing
Legacy conversion
Plug-in provider
Manufacturing
Government
Aerospace
High-tech
Financial
Training
Automotive/Transportation
Value-Added Reseller (VAR)
FrameMaker development
Partner
Software manufacturing
served
FrameMaker integration
Consultant to industry
Database publishing
Technical publishing
Legacy conversion
Plug-in provider
Manufacturing
Government
Aerospace
High-tech
Financial
Training
Partner Descriptions
This section introduces each third-party solution provider in detail, including how the partner’s product
and service relate to the Solution Guide’s four Usage Areas.
Apt Solutions works with customers to refine the electronic publishing processes by:
• Analyzing existing processes for the creation of information products
• Enhancing single sourcing of electronic information products
• Providing expertise to implement electronic information products quickly and easily
• Industry knowledge of the top publishing tools and how these tools can work together across
processes
• Insight into future development and technologies
• Options that fit both budget and environment
• Training
• Practical working methods and techniques to optimize and enhance tools without added costs
• Simple information processing development that is easy to maintain and replicate.
Apt Solutions is an Adobe Certified Training provider for FrameMaker and Adobe Acrobat®, a
WebWorks University Affiliate for Quadralay WebWorks Publisher Professional, and a reseller and
training provider for Finite Matters PatternStream.
Regions served
U.S. : NE, NW
Usage areas
Database Publishing
Helps customers build database publishing solutions as a reseller and trainer for PatternStream.
Technical Publishing
Training, support, and development services for customers implementing and/or extending the
FrameMaker platform in their technical publishing environment. Has built templates for specialized
markets such as aerospace and FDA. Other development projects include:
• Airline industry applications using the Air Transport Association’s standards and specifications in
SGML, XML, and HTML
• Open Travel Alliance applications and ebXML application development using various industry
vocabularies for cross-enterprise interchange
XML Authoring and Publishing
Helps customers build XML delivery solutions by enhancing the FrameMaker and WebWorks
applications.
Vertical markets
Aerospace, Automotive/Transportation, High Tech, Manufacturing, Financial
Axial InfoSolutions
425-820-6708 12040 100th Avenue. NE #F-101, Kirkland, WA 98034, USA
www.axialinfo.com Fax: 425-820-7590
E-mail: scarlisle@axiainfo.com
Contact: Sheila Carlisle
Axial InfoSolutions develops and implements “open” automated publishing solutions that create
dramatic savings in time and money. The solutions automatically gather and consolidate data from
multiple sources and instantly compose high-quality pages for print and electronic distribution.
Regions served
U.S.: NE, NW, SE, SW
Usage areas
Database Publishing
The company integrates Miramo, a robust database publishing tool, with FrameMaker. This integration
provides a publishing system that automatically formats information extracted from databases and/or
other data sources, including XML. This combination of technologies elevates FrameMaker to a
powerful and very fast automated publishing system.
Technical Publishing
Training, support, and development services for customers implementing and/or extending the
FrameMaker platform in their technical publishing environment.
Vertical markets
Government; High Tech; Manufacturing; Financial
Beyond Print runs the Annual FrameUsers Workshop—the largest gathering of FrameMaker users and
experts in the world.
Regions served
U.S.: NE, NW, SE, SW
Usage areas
Database Publishing
Integrates PatternStream with FrameMaker to build complete database publishing solutions.
PatternStream connects to a database and publishes directly into FrameMaker with no interim markup
needed. Once in FrameMaker, users can publish to print or electronically to the Web or CD.
PatternStream also automates the multiple-output delivery of FrameMaker documents.
Technical Publishing
Assesses the current publishing process and recommends changes or shortcuts to save time, money, last-
minute headaches, and unnecessary stress.
Vertical markets
Government, High Tech, Manufacturing, Financial
The company provides complete FrameMaker software and project support. Services include Adobe
software product demonstrations; publishing process evaluations; FrameMaker, Structured
FrameMaker, XML, and Quadralay WebWorks Publisher training; XML, HTML, and online help
implementations; template creation; conversion services for legacy data; EDD and DTD development;
WebWorks Publisher template creation; general consulting services for publishing issues; FrameMaker
to PDF and Acrobat troubleshooting; and on-site and hotline technical support for FrameMaker,
Structured FrameMaker, WebWorks, and Acrobat.
Regions served
U.S.: NE, NW, SE, SW
U.K.
Usage areas
Database Publishing
Consulting services to support the development of complete database publishing solutions.
Technical Publishing
FrameMaker platform training, support, and development services; Structured FrameMaker
development services including: XML, TML, and SGML application setup; DTD and EDD
development; and legacy conversion into structure.
Vertical markets
Aerospace, Automotive/Transportation, Government, High Tech, Manufacturing, Financial
Datalogics Incorporated
312-853-8200 101 N. Wacker Drive, Suite 1800, Chicago, IL 60606, USA
www.datalogics.com Fax: 312-853-8282
E-mail: info@datalogics.com
Contact: Jennifer Milton
Datalogics is a leading provider of innovative publishing solutions dedicated to delivering the highest-
quality software products and services that meet the most demanding publishing needs. The company
offers flexible options for Web publishing, electronic document delivery, and high-speed variable print,
and provides solutions that easily generate one-to-one communications and XML-to-PDF
transformation documents.
Regions served
U.S.: NE, NW, SE, SW
France; Germany; Sweden; U.K.
Usage areas
Database Publishing
Consulting services to support the development of complete, innovative database publishing solutions
that maximize content value. The Datalogics DL Formatter variable-data solution integrates with
FrameMaker to provide users with advanced personalization capabilities.
Technical Publishing
FrameLink and FrameLink+SGML plug-ins that connect FrameMaker to the Documentum Content
Management System.
Vertical markets
Aerospace, Automotive/Transportation, Government, High Tech, Manufacturing, Financial
Regions served
U.S.: NE, NW, SE, SW
Usage areas
Technical Publishing
The company provides training, support, and development services for customers implementing and/or
extending the FrameMaker platform in their technical publishing environment.
Vertical markets
Aerospace, Automotive/Transportation, Government, High Tech, Manufacturing, Financial
DocuCentric Corporation
918-592-1919 427 South Boston, Suite 604, Tulsa, OK 74103, USA
www.docucentric.com Fax: 918-592-1918
E-mail: sales@docucentric.com
Contact: Kim McLeod
DocuCentric provides sales, integrated publishing, and software development solutions for major
corporations and universities across the nation. DocuCentric specializes in the enterprise publishing
family of Adobe products, and its expertise includes SGML/XML conversions from legacy format,
custom Structured FrameMaker template creation, application creation, and custom integration
programming.
Regions served
U.S.: NE, NW, SE, SW
Usage areas
Database Publishing
Consulting services to support the development of complete database publishing solutions.
Technical Publishing
Training, support, and development services for customers implementing and/or extending the
FrameMaker platform in their technical publishing environment.
Vertical markets
Aerospace, Automotive/Transportation, Government, High Tech, Manufacturing, Financial
Documentum
925-600-6800 6801 Koll Center Parkway., Pleasanton, CA 94566, USA
www.documentum.com Fax: 925-600-6850
Documentum provides content-management software, services, and solutions for enterprise customers.
Documentum 4i is both a server content-management application and a development toolset that
integrates with the FrameMaker platform to provide powerful content and document system
management for FrameMaker authoring and publishing. The 4i application is designed for managing,
distributing, and exchanging content between small workgroups and the enterprise and customers,
partners, and suppliers.
Documentum can be implemented as the core data-management and storage component for a
FrameMaker publishing solution. Documentum 4i provides these benefits and features:
• Fully integrated FrameMaker and Documentum architecture using the Datalogics FrameLink plug-
in through custom integration. The Documentum document-management commands and features
are exposed through the FrameMaker menu interface for ease of learning and use.
• Version control to manage documents and objects throughout the life of a project.
• Security to manage users, documents, and workflow.
• Content management and delivery, including an XML architecture that extends the content
authoring of FrameMaker to the most advanced XML Web applications.
• Complete content management including component re-use and object referencing.
Regions served
U.S.: NE, NW, SE, SW
Canada; Mexico; France; Germany; U.K.; Japan
Usage areas
Database Publishing
FrameMaker and Documentum 4i combine to build an architecture for rich database publishing. The 4i
core database engine manages and stores the data collected from many sources, including other
databases and even FrameMaker binary and XML documents. The Documentum 4i SQL layer enables
extensive customizing and automation of data collection and organization before a document is handed
off to FrameMaker for pagination, rendering, and delivery as paper, PDF file, or XML file.
Technical Publishing
The FrameMaker platform is easily extended to incorporate the 4i suite of document-management,
control, and security capabilities. The Datalogics FrameLink plug-in completely integrates the
FrameMaker and Documentum applications, enabling seamless check-in, check-out, document
versioning, and managing advanced FrameMaker objects. The system can be configured to manage
Structured FrameMaker subdocuments, and element and attribute metadata.
Vertical markets
Aerospace, Automotive/Transportation, Government, High Tech, Manufacturing, Financial
Finite Matters Ltd. sells three different FrameMaker value-add licenses: PatternStream, FrameScript, and
FrameTools.
Regions served
U.S.: NE, NW, SE, SW
France; Germany; Sweden; U.K.
Usage areas
Database Publishing
PatternStream is the company’s award-winning database publishing application that allows users to
rapidly set up, publish, modify, and save database publishing projects using its graphical user interface.
PatternStream connects directly to one or multiple ODBC/SQL-compliant databases and flat files and
publishes directly to FrameMaker. PatternStream works on the desktop, in a network environment, or
on Web servers to publish documents for print and electronic distribution.
Technical Publishing
Training, support, and development services for customers implementing and/or extending the
FrameMaker platform in their technical publishing environment.
Vertical markets
Aerospace, Automotive/Transportation, Government, High Tech, Manufacturing, Financial
Group Wellesley
412-363-3481 933 Wellesley Road, Pittsburgh, PA 15206, USA
www.groupwellesley.com Fax: 412-363-3482
E-mail: info@groupwellesley.com
Contact: Alan Houser
Group Wellesley provides XML and FrameMaker consulting, training, and content-development
services for technology-based businesses, including these value-added services:
• FrameMaker template design
• Structured FrameMaker EDD design
• Publishing workflow and process consulting
• FDK development for FrameMaker and Structured FrameMaker
• Complete XML consulting services, including information modeling, DTD and schema design,
XSLT stylesheet authoring, and XML publishing
• Training in FrameMaker, Structured FrameMaker, and XML and related technologies, including
XSLT, XSLFO, and XML DTD and schema design
Regions served
U.S.: NE, SE, NW, SW
Usage areas
Database Publishing
Consulting services to support the development of complete database publishing solutions.
Technical Publishing
Training, support, and development services for customers implementing and/or extending the
FrameMaker platform in their technical publishing environment.
Vertical markets
Aerospace, Automotive/Transportation, High Tech, Financial
Regions served
U.S.: NE, NW, SE
Usage areas
Technical Publishing
The company uses FrameMaker to convert Microsoft® Word documents to structured formats and
output SGML, XML, and PDF files; customized software development using the Frame Developer’s Kit;
FrameMaker and Structured FrameMaker training.
Vertical markets
Aerospace, Government, High Tech, Manufacturing, Financial
Regions served
U.S.: NE, NW, SE, SW
Usage areas
Technical Publishing
Training, support, and development services for customers implementing and/or extending the
FrameMaker platform in their technical publishing environment.
Vertical markets
Government, High Tech, Manufacturing, Financial
Regions served
U.S.: SW
Germany
Usage areas
Database Publishing
Consulting services to support the development of complete database publishing solutions.
Technical Publishing
Training, support, and development services for customers implementing and/or extending the
FrameMaker platform in their technical publishing environment.
Vertical markets
Aerospace, Automotive/Transportation, High Tech
Regions served
U.S.: NE, NW, SE, SW
Canada; Mexico; France; Germany; U.K.; Japan
Usage areas
Technical Publishing
The Astoria-FrameMaker Bridge connects FrameMaker to the Astoria content database and provides
complete access to documents and content through the FrameMaker interface.
Vertical markets
Aerospace, Automotive/Transportation, Government, High Tech, Manufacturing, Financial
Markzware
800-300-3532 www.markzware.com
949-756-5100 1805 East Dyer Road, Suite #101, Santa Ana, CA 92705, USA
Fax: 949-756-5108
E-mail: info@markzware.com
Contact: Mark Singelyn, ext. 252
Regions served
U.S.: NE, NW, SE, SW
France; Germany; Sweden; Japan; U.K.
Markzware sells four FrameMaker-related products that cater to the worldwide graphics, printing, and
publishing industries—FlightCheck, FlightCheck Collect!, MarkzScout, and MarkzNet. These software
applications prepare FrameMaker documents for printing by:
• Preflighting FrameMaker documents
• Collecting all linked images, fonts, colors, and so on used in the FrameMaker document to process
for output
• Sorting and/or incorporating FrameMaker into a workflow management solution
Usage areas
Technical Publishing
Enterprise Authoring and Publishing
The company’s products provide a level of security to FrameMaker and Structured FrameMaker
documents by pre-flighting them before printing and/or output to PDF.
Vertical markets
High Tech, Manufacturing
Quadralay Corporation
512-719-3399 9101 Burnet Road, Austin, TX 78758, USA
www.webworks.com Fax: 512-719-3606
E-mail: sales@quadralay.com
Contact: Mike Fabry
Quadralay Corporation creates and sells software products that provide comprehensive online
publishing and help-system delivery capabilities for FrameMaker and Structured FrameMaker. The
company creates and sells WebWorks Publisher Standard Edition, which gives FrameMaker users
immediate online publishing capability.
Regions served
U.S.: NE, NW, SE, SW
France; Germany; Sweden; Japan; U.K.
Usage areas
Technical Publishing
WebWorks Publisher Standard Edition allows FrameMaker users to quickly, easily, and automatically
convert FrameMaker documents for online delivery in a choice of popular Web-based formats,
including XML, HTML, and HTML+CSS. WebWorks Publisher Standard Edition is also fully integrated
with Adobe GoLive®, using GoLive style sheets and master pages for online delivery.
Vertical markets
Aerospace, Automotive/Transportation, Government, High Tech, Manufacturing, Financial
Sandybrook Software
207-294-7430 456 Boom Road, Saco, ME 04072
www.sandybrook.com Fax: 207-294-7473
E-mail: info@sandybrook.com
Contact: David Lyall
Sandybrook Software creates and sells FrameMaker plug-ins and provides custom programming
services to the FrameMaker user community.
Regions served
U.S.: NE, NW, SE, SW
France; Germany; Sweden; Japan; U.K.
Usage areas
Database Publishing
Consulting services to support the development of complete database publishing solutions.
Technical Publishing
Enhance, the company’s FrameMaker plug-in, provides advanced outlining and drag-and-drop text
editing functionality to FrameMaker. Using Enhance, a user can collapse a document so that only its
heading paragraphs are displayed, then quickly find and expand just the section they wish to work on.
Any edits or changes made while in Enhance are immediately reflected in the underlying FrameMaker
document. Enhance supports multiple document views so that a user can view multiple parts of a
document at the same time.
Vertical markets
High Tech, Financial
Regions served
U.S.: NE, SE, NW, SW
Usage areas
Technical Publishing
The company’s plug-ins enhance the technical publishing process.
Vertical markets
Aerospace, Automotive/Transportation, Government, High Tech, Manufacturing, Financial
Regions served
U.S.: NE, NW, SE
Germany; Sweden; Japan; U.K.
Usage areas
Technical Publishing
Training, support, and development services for customers implementing and/or extending the
FrameMaker platform in their technical publishing environment.
Vertical markets
Aerospace, Government, High Tech, Financial
Regions served
U.S.: NE, NW, SE, SW
France; Germany; U.K.
Usage areas
Database Publishing
Consulting services to support the development of complete database publishing solutions.
Technical Publishing
Training, support, and development services for customers implementing and/or extending the
FrameMaker platform in their technical publishing environment.
Vertical markets
Aerospace, High Tech, Manufacturing, Financial
Adobe, the Adobe logo, Acrobat, Frame, FrameMaker, and GoLive are either registered trademarks or trademarks of Adobe Systems
Incorporated in the United States and/or other countries. Microsoft is either a registered trademark or a trademark of Microsoft
Corporation in the United States and/or other countries. All other trademarks are property of their respective owners.
Migration is typically motivated when a workgroup or enterprise needs to solve some set of
business problems: (see section 2 for details on these). The severity of these problems and
the urgency to address them motivates the migration schedule and determines whether the
migration is for a single project, a set of projects, a workgroup, or the entire enterprise.
Many organizations continue using outmoded tools and architectures long after those tools
have been proven inadequate to new business challenges. In some cases, this happens
because of budgetary concerns or because the organization’s focus is elsewhere. Others,
however, have the budget, the management interest, and the resources to move to a new
platform, but delay for one reason—the migration task is considered to be too onerous to
take on.
Objections to migration
Migrating to a new platform does not need to be overly difficult or complex. With careful
planning and execution, benefits arise because of the move to a better way of doing business.
However, migrating to a new information authoring, editing, and management system
requires a commitment of time, effort, and resources. Approaching migration with the most
detailed plan possible is crucial.
Third-party support for this pre-migration activity is available from many of the partners
listed in Sections 7 and 11.
• Efficiencies need improvement. Reduced cycle times, improved time-to-market for information
products, and marketing, product development, and manufacturing schedules are not being met.
The organization cannot re-use information (create information once, distribute and package it
many times and in many ways) and reduce the costs of information creation, maintenance, and
delivery.
• Quality is at risk. Because tools are old, rare, and less user-friendly, and knowledgeable staff
resources are more difficult to find, more errors are being introduced.
• Regulatory compliance is required. Current tools cannot tightly manage and control information
to meet compliance requirements.
Authoring and publishing Microsoft Office Fine tuned for basic word Combines content author-
from the desktop QuarkXPress processing or layout and ing, structure, management,
Corel WordPerfect design layout and design, and pub-
Corel Ventura lishing workflow capabili-
ties. Provides template-
driven authoring, ability to
integrate content from many
sources, and multichannel
publishing capabilities .
Database publishing Oracle to a print mark-up Often complex and Integration options via MIF,
system Difficult to manage and XML, the FDK, template-
update driven rendering of content,
multichannel publishing,
and a highly configurable
user interface.
Migration strategies
Every organization’s toolset, workflow, and requirements are different, so every organization tends to
have a unique migration strategy. Minimize disruptions and maximize chances for success by choosing
an appropriate migration strategy. The three strategies described here are the most common. No matter
which one is selected, migrating requires a commitment of time, effort, and resources that minimizes
disruptions and maximizes chances for success.
Clean-slate strategy
Here the organization fully implements the FrameMaker solution for a specified prototype project. After
the prototype project is fully integrated and tested, other projects are migrated into FrameMaker at the
information-authoring phase. Interoperability or continuity with legacy processes and tools are not
necessary with this strategy. Use this strategy when these factors are in play:
• Current tools do not meet needs for creating, managing, and delivering content.
• The current publishing solution is exclusively paper-based.
• A candidate project exists that is relatively segregated from the rest of the workgroup or
organization.
Parallel-development strategy
In this strategy the new FrameMaker system runs in parallel with the legacy system, which is maintained
as a backup until the new architecture is thoroughly tested and proven. Legacy content and workflows
are then migrated to the new system. Here are some situations that call for this strategy:
• Current publishing processes are mission-critical; any loss of capabilities during the transition
would be unacceptable.
• Current tools adequately meet existing requirements, but will not meet future requirements.
• No projects exist that are relatively segregated from the rest of the workgroup or organization.
Component strategy
Here the organization migrates only individual component areas of the information workflow, for
example, content authoring or Portable Document Format (PDF) file production. Acute problems can
be solved in these areas before a large-scale migration. Turn to this strategy in these situations:
• The workflow is highly structured.
• Specific individuals and departments have specific roles; for example, content contributors are
responsible solely for content, and production staff are responsible solely for distribution.
Migration tasks
Migration to FrameMaker typically is motivated by business drivers outlined in Section 2 of this Guide.
Their severity and urgency determine the scope of the migration. To execute any migration strategy, the
organization must work through five sequential steps: evaluate needs, specify requirements, design and
implement architecture, migrate legacy content, and train and deploy users.
Evaluate needs
Understand the workgroup or enterprise’s need to migrate. Consider the forces driving the migration.
Assess how the current tool’s capabilities meet and fail to meet current and future requirements.
Evaluate whether any requirements should be changed.
Specify requirements
These are set at the busines level. Return on investment is the key motivator in this step. Specify the
baseline functionality, performance, and stability requirements. In an enterprisewide deployment,
consider the different requirements of individual users, workgroups, and the enterprise as a whole.
Requirement considerations typically include toolset, workflow, delivery mode, content management,
application integration, competitive strategies, production efficiencies, quality control, and regulatory
and compliance issues. An example business driver might be: “deliver high-quality, personalized content
to customers on demand.” The potential solution: A server-based publishing system, with FrameMaker
7.0 Server as the on-demand rendering engine for delivering PDF documents via HTTP over the Web.
Architecture design
Design the architecture to address high-level business requirements (see Section 4, “The Adobe
Solution” for example architectures). Determine whether the information architecture will be template-
based (unstructured) or XML-based (structured). If template-based, the possibility of migrating to an
XML-based solution in the future must still be open.
Component implementation
Designing and implementing the individual components of the architecture includes these stages:
• Supporting integration of components (for example, creating Frame® Developer’s Kit, or FDK
clients to integrate FrameMaker with application servers for server-based publishing)
• Information modeling, including database schema and XML DTD design to support authoring and
delivery requirements. With FrameMaker, the user or designer creates an XML application that
associates templates, an XML DTD, read/write mapping rules, and optional processing plug-ins.
• Creating authoring and publishing templates. For an unstructured solution, this is valuable and
necessary, so that a future migration to XML can leverage the templates designed now.
Component deployment
Scheduling component deployment, including time for testing and modification.
Location of legacy content—Where does the organization’s content reside (that is, its location in the
organization’s file system, content management system, or database)?
Format of legacy content—Does the legacy content exist in its original application format? Is the
original application still available and supported? Does FrameMaker recognize the original application
format? If not, does the original application save in a more widely readable file format?
Some legacy content may be available only in a presentation format that cannot be easily edited and
updated. These formats include hard copy (paper), TIFF images, and older versions of PDF that do not
support saving as other formats. In this case, the organization should consider the services of third-party
companies that specialize in migrating legacy content to current application formats.
Consistency of legacy content—If the legacy content exists in the original application format, was a
common set of templates and/or styles used to create the content? Is the content consistently style-
tagged? FrameMaker will generally recognize style tags in legacy application formats and convert those
tags to FrameMaker paragraph and character styles.
Condition of graphics—If the legacy content includes graphics, are the original graphic files available?
Is the original application that was used to create the graphics available?
Many word-processing programs destroy the integrity of imported graphic images by modifying the
graphic file format for the convenience of the word-processing program. When migrating legacy
graphics, return to the original graphics file format, upgrade that format as necessary to a current
format, and import the updated graphics into the FrameMaker documents by reference. This solution
retains the integrity of the original graphics file, allows further updates to each graphic (if necessary),
and minimizes the size of the FrameMaker source files for better application performance and
robustness.
Relevance of legacy content—Is the legacy content important for deployment of the new publishing
solution? Will the new system focus primarily on delivering new content? If only a subset of the legacy
content is required going forward, is it easy to identify that subset?
Target of legacy content—Are the legacy files “flat” or do they include structure information and
metadata? Most unstructured documents have these characteristics in their original styles. For example,
a “Heading” style is a strong indicator of a document heading.
A “conversion table” in FrameMaker helps convert unstructured content to structured documents, based
on the documents’ existing paragraph and character styles. Depending on the XML publishing
requirements, the results of the conversion table operation may be complete, or they may provide
simplified XML documents that can be augmented with additional metadata in FrameMaker as part of
the migration process.
Converting content
After clean-up comes conversion to FrameMaker:
• Programmatically convert the content using an off-the-shelf or custom filter (for example, the
FrameMaker filter for Microsoft Word)
• Convert the content as a whole with in-house resources or with assistance from a consultant or a
data-conversion company.
Post-conversion clean-up
Virtually every conversion will require clean-up in FrameMaker. Repetitive tasks in FrameMaker can
frequently be automated by a scripting language for FrameMaker called FrameScript, available from
Finite Matters Ltd. (www.framescript.com). Post-conversion clean-up may be required in the following
areas:
Untagged or rogue tagged text—Where formatting is missing or was misapplied, FrameMaker styles
can be applied in batch mode using the global update options in FrameMaker, or individually.
Tables—Ad hoc use of ruling, shading and cell straddles (merging) can fool converters, which prefer
regular patterns. Table Cleaner, a FrameScript from Carmen Publishing, removes custom ruling and
shading and performs other useful functions. For more information, see www.frameexpert.com.
Special symbols and equationsReinstate the symbol characters that had been replaced by special
character sequences during legacy clean-up to avoid exporting isues. Many filter applications do not
support equations. FrameMaker includes an equation editor for re-creating equations in documents.
Although an investment in training usually offers a rapid return on investment when increased
productivity and improved business processes are considered, training can be a significant line item in a
migration budget. By intelligently planning the organization’s needs and timetable, the benefits of
investing in training can be maximized.
A scaled training deployment is effective for many organizations. Begin by selecting a group of key
people who have proven their ability to quickly learn new tools and processes, and who can support
others during the migration process. Train this group early in the migration process, with advanced-
level courses that will allow them to fully support the migration process. As the new publishing system is
deployed, train more users, with courses appropriately targeted. For example, content authors who are
not supporting template and DTD design functions do not need to be trained on those functions.
Adobe, the Adobe logo, Acrobat, Frame, FrameMaker, and GoLive are either registered trademarks or trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
An enterprise information management solution must have the capabilities and features
necessary for solving today’s business problems. Anything less leads to inefficiencies,
workarounds, and wasted resources. As we have seen in sections 2, 3, and 4 of this Solutions
Guide, the optimal information publishing solution meets the following business
requirements:
• Ability to create valid XML content on every desktop
• Supports a template-based workflow
• Integration with an organization’s existing infrastructure, including application servers,
databases, and content management systems
• Server-based publishing
• Integration from a variety of sources
• Publishing to a wide array of delivery formats including print and Web
Simply meeting these requirements is not enough. The solution must do so at a reasonable
cost that assures a positive return on investment. Furthermore, the solution must be easy to
install, configure, administer, learn, and use.
For authoring, FrameMaker 7.0 software is the only application that supports editing,
formatting, and structure within a single application. No additional software is required.
On the publishing side, FrameMaker 7.0 software's integration with PostScript® and
Portable Document Format (PDF) make print production simple and inexpensive. For
delivery in online and Web-based formats, FrameMaker publishes to XML, SGML, HTML,
and eBook formats.
The rich feature set and robust architecture of FrameMaker and FrameMaker Server
software make this solution highly useful for the four key usage areas of enterprise and
workgroup information publishing: XML authoring and publishing, database publishing,
technical documentation, and enterprise authoring and publishing.
FrameMaker software can be scaled to create one- or two-page documents, and is robust and reliable
with documents comprising thousands of pages. The user interface is WYSIWYG and the basic features
take only minutes to learn, yet FrameMaker software is rich enough to provide content creators with all
the tools and controls they need. A single copy of FrameMaker includes a self-contained set of
capabilities for single-source authoring and multichannel publishing. The product can be deployed on
thousands of desktops, used in a collaborative environment, be customized via the Frame® Developer’s
Kit (FDK), and integrated into a complex infrastructure that includes desktop clients, servers,
repositories and Web-based systems.
Change the authoring mode to fit different needs—The power of structured authoring is standard in
FrameMaker software. Switch between Structured and Unstructured modes through the Preferences
dialog box at any time. Create valid XML that conforms to a chosen DTD with guided editing in
Structured mode, or create well-formed XML in Unstructured mode.
Define the structure of XML content—Import the XML DTD into FrameMaker software’s Element
Definition Document (EDD) to maintain and edit the structure rules in FrameMaker. Enhance the EDD
with context-based formatting rules, as easy to create as FrameMaker templates. Define read-write rules
to automatically map XML elements to headings, lists, tables, graphics, footnotes, cross-references, and
index markers.
Open, edit, and save XML files and DTDs—FrameMaker software’s XML parser examines each XML
document to verify that it is well-formed and to validate its structure and content against a chosen DTD.
After authoring and tagging is complete, easily save valid XML files for future editing with FrameMaker
or for further processing by other XML applications, such as Extensible Stylesheet Language
Transformations (XSLT).
Work with namespaces, CSS, and Unicode—Use namespaces to provide a label prefix for XML element
names when combining content from multiple sources. Automatically generate Cascading Style Sheet
(CSS) style definitions for use with a broad variety of media. Take advantage of FrameMaker software’s
ability to automatically map Unicode (UTF-8/UTF-16) characters in XML files to the appropriate
characters for printing.
Use industry-standard structured applications—FrameMaker 7.0 ships with three sample applications
for structured authoring: DocBook 4.1, xDocBook 4.1.2, and XHTML. DocBook 4.1 and xDocBook
4.1.2 conform fully to the industry-standard DocBook (SGML) and xDocBook (XML) DTDs for
technical documentation. The XHTML sample application conforms to the DTD for the next
generation of HTML—the XHTML version 1.0 transition DTD, a redefinition of HTML in XML syntax.
Generate PDF files easily—FrameMaker 7.0 provides a PDF-generation interface that supports
predefined distiller options saved with FrameMaker documents and templates. FrameMaker for the
Windows® and Macintosh platforms includes Adobe Acrobat® Distiller® 5.0, which generates PDF 1.4
and distills documents from within FrameMaker.
Create PDF files on the UNIX® platform—Generate Adobe PDF files on the Sun™ Solaris™, HP-UX®,
and IBM AIX® platforms.
Generate accessible PDF documents—Create Tagged PDF files on the Windows and Macintosh
platforms to enable high-quality viewing on a variety of devices and to make PDF documents more
accessible to visually impaired readers.
Exercise maximum control over HTML output—Authors can control how large documents are
divided into logical Web pages. FrameMaker 7.0 software includes professional-quality templates that
can be modified and customized with such tools as Adobe GoLive®, for precisely tailoring the look and
feel of Web pages to specific needs.
Work with SVG—Import scalable vector graphics (SVG®) on Windows, Macintosh, and Solaris
platforms and automatically rasterize them. With HTML, XML, and SGML files, output the raster
version or pass through the original, which streamlines the process of publishing text and SVG directly
to the Web and facilitates the use of complex diagrams and interactivity.
Create eBooks—Save books created on the Macintosh or Windows platforms as Tagged PDF files, which
are readable with the Adobe eBook Reader and with the Acrobat Reader® for Palm OS® and Windows
CE devices. Publish to Microsoft Reader and Palm Reader formats using the included WebWorks
Standard Edition. This powerful new functionality provides complete control over content look and feel
on multiple devices and platforms.
Choose from a broad range of layout options— New book templates and structured templates have
been added to FrameMaker 7.0.
Enjoy rich UNIX font selection options—FrameMaker supports TrueType, OpenType, and Type 1
fonts. Drag and drop fonts to install them, and quickly begin sharing documents with Windows and
Mac OS users without any loss of type quality.
Use a wide range of printers for Asian languages—Enhanced Asian language support enables font
downloading and subsetting, partially or completely eliminating the need to purchase special printers
supporting Chinese, Japanese, and Korean fonts.
Import a wide array of files—Import new graphics file formats, including SVG, on Windows,
Macintosh, and Solaris platforms, PDF 1.4 on Windows and Macintosh platforms, and (via PDF
support) native Adobe Illustrator® files. After incorporating graphics, easily resize them to fit
publication needs. An updated set of Microsoft Office text import filters support RTF 1.6, Microsoft
Word, and Microsoft Excel.
Create accessible documents—Generate tagged PDF files on Windows and Macintosh that facilitate
high-quality viewing on a broad variety of accessible devices and platforms. Output documents as raw
text for compatibility with accessibility tools that require ASCII text input. Template-driven HTML
conversion generates versions of standard Web sites that use large font sizes and high-contrast graphics
or accessibility tags. Create valid XML output that can be transformed with XSLT to generate accessible
file formats such as VoiceML.
Word processing
Content authors and editors have a complete set of word-processing features at their disposal. These
include find and change, spell-checking, change bars, and a thesaurus. FrameMaker organizes and
manages content with paragraph and character format tags, tables, elements and attributes, cross-
references, variables, conditional text, and markers. Page layout is enhanced with master pages for
consistent design and reference pages for repeating design elements. FrameMaker 7.0 has an easy-to-use
WYSIWYG interface for creating and editing valid XML content. Elements, attributes, validation rules,
and element context formatting extend a user’s ability to organize and structure XML and SGML
content while working in the familiar word-processing mode.
Cross-media capability
A rich set of text and graphics import filters perfectly position the product in the content creation and
delivery workflow in environments where contributors use a variety of text and graphic creation tools.
Export filters enable workgroup data delivery in various formats, especially important in just-in-time
publishing—when introducing additional tools and procedures at delivery time can cause errors and
delays. FrameMaker can export content in PDF, XML, XHTML, SGML, HTML, and ASCII text. When
content is saved in HTML, XHTML, or XML for Web-based distribution, FrameMaker automatically
generates Web-compliant versions of all graphics and illustrations, even from formats that are not Web
compliant, such as EPS, WMF, and TIFF.
Content contributors can share books and documents without limitation when working on the
Windows, Macintosh, or UNIX platforms. WebDAV integration extends FrameMaker into existing
document management systems. FrameMaker Server 7.0 adds powerful server-based publishing
capabilities, including variable data publishing, database publishing, and automated publishing from
application servers and Web services.
Information management
The FrameMaker Document Object Model provides the architecture for building and managing book
and document objects, such as files, pages, text frames, variables, graphics, formats, and element
definitions. The intuitive user interface makes organizing and managing multiple documents easy.
Whether the book contains hundreds of files or just two documents, management of chapter and page
numbers, references, and generated table of contents and indexes is automated. Cross-references,
referenced objects, formatting and page layout, and element schema rules (Structured FrameMaker) are
also managed from the book.
Multiple users
Multiple users can access and work with a given FrameMaker file set during authoring and production.
Change bars, conditional text, cross-platform capabilities, WebDAV, text insets, elements and attributes,
structure rules, templates, and import and export filters support collaboration among small and large
workgroups.
Developer tools
The FrameMaker API and the FDK provide the communication layer and tools to enhance FrameMaker
software and integrate it with other applications for large, complex content management and publishing
solutions. The FrameMaker API can connect FrameMaker and FrameMaker Server with databases,
custom PDF, XML, XHTML, and HTML delivery applications, and content and document management
systems.
FrameMaker software’s XML Edit, Import, and Save features provide complete control over XML use
and delivery . FrameMaker has all of the tools needed for XML authoring and delivery. FrameMaker also
manages graphics, cross-references, text insets, and variables so that each of these objects can round-trip
(save and reopen) as valid XML without loss of content or behavior.
Server-based publishing
Automated database-content publishing can be accomplished in several ways. The FDK provides an
interface with FrameMaker software’s API layer for building C-based plug-ins to directly connect
FrameMaker or FrameMaker Server to any database, application server, or content management server
that presents an API or scripting interface. The FDK enables real-time connectivity with the API layer
between FrameMaker or FrameMaker Server and the database. The API layer supports bidirectional
communication for interactive processing, and either the database or FrameMaker (or FrameMaker
Server) can control the database query and determine the pagination and rendering of the server
content.
As XML grows in popularity, databases and application servers more frequently present it as an
intermediate format for further processing. FrameMaker and FrameMaker server can render and
publish XML content in an automated fashion. FrameMaker Server can validate and render XML
content to PDF or print via formatting rules specified in the FrameMaker EDD and template.
FrameMaker also provides a text markup language, Maker Interchange Format (MIF), which can be
generated by a database engine and then read and rendered by FrameMaker or FrameMaker Server.
FrameMaker Server can work with documents of any size or complexity, from simple one-page invoices
to complex catalogs covering hundreds of thousands of pages. An individual book may contain
hundreds of chapters, each of any length and layout. Tables can span thousands of pages and millions of
cells, and table cells can contain almost any document element, including graphics and other tables. The
FrameMaker document model supports cross-references and automatic generation of multiple tables of
contents and indices. Like the desktop version of FrameMaker, FrameMaker Server provides support for
numerous languages, including Chinese, Korean, and Japanese.
FrameMaker Server uses the same page-composition engine as FrameMaker for the desktop. Users can
design document templates using the WYSIWYG FrameMaker desktop application and be confident
that they will be the same in FrameMaker Server. This workflow can dramatically reduce the cost and
time required to create or modify templates.
FrameMaker Server can be deployed in a client-server environment with the desktop version of
FrameMaker and integrated with a document management system where, as files are checked in, they
are automatically converted to PDF by FrameMaker Server. FrameMaker Server can accept files in
FrameMaker software’s binary file format, in addition to XML or MIF formats.
Technical documentation
Technical content is often complex, graphically intensive, highly organized, and mission-critical.
Increasingly, companies consider published technical content to be important as the product or service
to which the content relates. An aircraft operations manual, for example, provides both technical and
operational data required to safely fly the aircraft. The plane cannot be certified or delivered without a
current and accurate user guide.
FrameMaker software’s organization and validation features for mission-critical content include format
tagging, elements and attributes, conditional text, and variables. These features give the content designer
ways to configure information for process, function, user, and context. In addition, authors can write
content once and publish it to multiple channels, instead of rewriting it specifically for each channel.
Both labor and distribution costs are reduced, as are opportunities for error, and customers can receive
content in the most convenient format.
can be delivered in many formats. FrameMaker 7.0 software’s reuse capabilities add value to developed
content by extending its use. Other FrameMaker features such as template-based authoring, change
bars, conditional text, cross-platform capabilities, WebDAV, text insets, elements and attributes, and
structure rules help keep the information organized and simplify the flow of content from the
contributors to delivery.
Adobe, the Adobe logo, Acrobat, Acrobat Reader, Distiller, Frame, FrameMaker, GoLive, Illustrator, and PostScript are either registered
trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. Mac and Macintosh are trademarks of
Apple Computer, Inc., registered in the United States and other countries. HP-UX is a registered trademark of Hewlett-Packard Company. AIX
is a registered trademark of IBM Corporation in the United States. Microsoft, OpenType, and Windows are either registered trademarks or
trademarks of Microsoft Corporation in the United States and/or other countries. Palm OS is a registered trademark of Palm, Inc. UNIX is a
registered trademark of The Open Group. Solaris and Sun are trademarks or registered trademarks of Sun Microsystems, Inc., in the United
States and other countries. SVG is a trademark of the World Wide Web Consortium. All other trademarks are property of their respective
owners.
The following documents provide detailed information about Adobe FrameMaker 7.0
software and its capabilities.
FrameMaker 7.0: XML tips and techniques—Understanding and working with XML, for
novices and experienced users alike.
(PDF: 916 KB)
Service Providers
Adobe FrameMaker Service Providers are businesses that deliver complete output solutions to
customers using Adobe software. For more information, visit http://partners.adobe.com/asn/
partnerfinder/search_service.jsp.
User Guide
The Adobe FrameMaker 7.0 User Guide contains detailed information about the FrameMaker tools and
commands. It is designed to be used as a reference tool in your everyday work. The User Guide is
included in hard-copy format within the FrameMaker 7.0 product box.
Templates
FrameMaker includes simple templates that users can open and use to get started with FrameMaker.
These templates and accompanying samples are located in the FrameMaker 7.0 Templates and Samples
folders.
WebWorks
WebWorks Standard Edition—WebWorks Standard Edition, included in the Adobe FrameMaker 7.0
product box, is a powerful tool for converting documents produced with Adobe FrameMaker into
multiple online formats. WebWorks Standard Edition style templates enable document conversions to
basic HTML, dynamic HTML (which uses CSS), XML with CSS, and XML with Extensible Stylesheet
Language (XSL).
WebWorks Standard Edition User’s Guide—Intended for beginning users, the User’s Guide explains
how to perform common tasks, such as setting preferences, working with project files, and mapping
styles.
WebWorks Standard Edition Template Reference—The Template Reference explains the features
available in the various templates included with WebWorks Standard Edition.
Adobe, the Adobe logo, Acrobat, Frame, FrameMaker, and PageMaker are either registered trademarks or trademarks of Adobe Systems
Incorporated in the United States and/or other countries. Mac is a trademark of Apple Computer, Inc., registered in the United States and other
countries. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other
countries. UNIX is a registered trademark of The Open Group. All other trademarks are property of their respective owners.
In addition to the channel partners listed here, FrameMaker and FrameMaker Server can
also be purchased through the following Adobe channels:
• Retail, mail-order, and online—Any Adobe Authorized Reseller or Authorized Adobe
License Center (ALC). These are listed on the Adobe Web site at www.adobe.com.
• Direct—The Adobe Store, at www.adobe.com/store.
Additional third-party solution providers are listed at the Adobe Partner Web site at http://
partners.adobe.com. In addition, Section 7 of this Solutions Guide lists companies that focus
on the four key usage areas: XML publishing, server-based publishing, technical
documentation, and enterprise content management; and six vertical markets: aerospace,
automotive/transportation, government, high technology, manufacturing, and financial.
Company matrix
The companies listed here have provided information about their services to Adobe for publication.
Each company operates as a separate entity and is affiliated with Adobe only as a partner.
Note: Throughout this section, U.S. regions served are indicated as follows: northeast (NE); northwest
(NW); southeast (SE); and southwest (SW).
Product and
service focus
Customization
Integration
Consulting
Training
Teltek Systems, Inc. . . . . U.S.: NE, NW, SE, SW Adobe Authorized Licensing Center
888-2-TELTEK Adobe Certified Expert
(888-283-5835) Adobe Certified Training Provider
www.telteksys.com
Company descriptions
This section introduces each solution reseller in detail, focusing on each partner’s FrameMaker training,
consulting, integration, and customization services.
DocuCentric Corporation
918-592-1919 427 South Boston, Suite 604, Tulsa, OK 74103 USA
www.docucentric.com Fax: 918-592-1918
Contact: Kim McLeod
The company provides FrameMaker pre-sales support, including on-site visits, customer-focused
product demonstrations, technical information, consulting, installation and integration with existing
software and hardware. The company also provides continuing support and immediate problem
resolution.
Consulting
Evaluates client’s needs, partners with other vendors for full solutions, trains end users, provides on-site
support, supports end-user workload through transition.
Integration
In-depth knowledge of FrameMaker and Structured FrameMaker allows for the use of third party
programs, such as databases and content managers, for a complete integrated solution.
Customization
Extensive experience with application and plug-in programming for FrameMaker allows customization
of the authoring environment to meet each client’s specific needs.
Regions served
US: NE, NW, SE, SW
The company helps FrameMaker users leverage their software purchases with training, support, and
technical seminars. KnowHow Pro Services provides pre-sales, on-site visits to assess customer needs,
customer-focused product seminars, customized checklists, and syllabi before all on-site classes. Class
attendees receive 30 days of free technical support.
Consulting
KnowHow Pro evaluates the customers needs to find a total solution and provides project analysis,
coaching, and mentoring services.
Integration
Extensive FrameMaker, Structured FrameMaker, Acrobat, InDesign, and WebWorks knowledge assists
customers with seamless integration between products and their existing databases and content
management systems.
Regions served
U.S.: NW, SW
Mekon Ltd.
+44 (0) 20 8722 8400 1-35 St. Nicholas Way, Sutton, Surrey, SM1 1LN, United Kingdom
3www.mekon.com Fax: +44 (0) 20 8722 8500
Contact: Julian Murfitt
The company provides a full range of services to FrameMaker users, including technical support, system
integration, FDK development, template design, training, license management/supply, and consultation
to evaluate client workflow and production needs. The company covers a broad range of markets
including aerospace, government, professional publishing, finance, and technology companies.
Consulting
Evaluates client’s needs, partners with other vendors for full solutions, document analysis for SGML and
XML DTD development.
Integration
System integration with existing or new database applications, on-demand printing technology, or
content management.
Customization
Extensive experience with application and plug-in development using the Adobe Acrobat SDK and the
FDK.
Regions served
France, Germany, Sweden, United Kingdom
The company provides FrameMaker pre-sales services, including on-site visits, customer-focused
product demonstrations, technical information, and consulting. The company also provides continuing
support, plug-in development, databased publishing of extensive and high-quality documents with
Maker Interchange Format (MIF), and development of customer-focused PDFmark-statements to
provide high-quality and highly interactive PDF-documents.
Consulting
Evaluates client’s needs, partners with other publishing providers for full solutions, trains and supports
end users through transition.
Integration
Development of professional publishing processes for publishing on-demand solutions.
Customization
Extensive experience with FrameMaker application and plug-in programming allows customization of
the authoring environment to meet each client’s specific needs. Develops solutions with PDFmark.
Regions served
Germany
Through its core competence in technical documentation services and comprehensive know-how of
tools and solutions systems for document and content management, translation memory, and service
information, the company helps to make the documentation and information processes work together.
Consulting
Evaluates client’s needs, partners with other vendors for full solutions, trains end-users, provides on-site
support, supports end users through transition.
Integration
In-depth FrameMaker and Structured FrameMaker knowledge allows use of third-party programs, such
as databases and content managers, for a complete, integrated solution.
Customization
Extensive experience with FrameMaker application and plug-in programming allows customization of
the authoring environment to meet each client’s specific needs.
Regions served
Germany
Services include product demos and corporate briefings/seminars; pre- and post-sales support;
consulting services (SGML/XML document conversion, template design, application creation); product
training on FrameMaker and Acrobat; and consulting support to assist companies in taking their
FrameMaker documents to print, PDF, HTML, and XML.
Consulting
FrameMaker consulting. Partnering with third-party providers to provide total solutions. Additional
resources for time-critical projects.
Integration
FrameMaker integration solutions with such third-party programs as PatternStream, WebWorks
Publisher, and others.
Customization
Customized FrameMaker solution offerings for plug-ins, database publishing, XML authoring and
publishing, and technical document publishing.
Regions served
US: NE, NW, SE, SW
Adobe, the Adobe logo, Acrobat, Frame, FrameMaker, Illustrator, and Photoshop are either registered trademarks or trademarks of Adobe
Systems Incorporated in the United States and/or other countries. UNIX is a registered trademark of The Open Group. All other trademarks are
property of their respective owners.