<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0"><channel><title><![CDATA[ERM Community Blogs]]></title><link><![CDATA[http://www.aiim.org/community/Blogs/Community?topic=ERM]]></link><description /><language>en-us</language><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/aiim/ERM-Community-Blogs" /><feedburner:info uri="aiim/erm-community-blogs" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item><title><![CDATA[Leverage Big Data to Improve Asset Reliability and Reduce Maintenance Outages]]></title><link><![CDATA[http://www.aiim.org/community/blogs/community/Leverage-Big-Data-to-Improve-Asset-Reliability-and-Reduce-Maintenance-Outages]]></link><description><![CDATA[<p>
	The impact of equipment failures and plant outages on a company&rsquo;s bottom line can be more devastating than one might imagine. Initially, because production capabilities are reduced or even shut down, the company&rsquo;s top-line revenue plummets; and then the costs to produce additional product units go up as well.</p>
<p>
	Additionally, equipment and plant-related problems can lead to even bigger issues: heightened risk of environmental damages, increased legal and compliance costs, greater risk to maintenance workers&rsquo; safety, and brand deterioration. A company&rsquo;s only defense is to ensure higher equipment reliability and a clear record of all maintenance activities, so they can proactively take action to prevent unplanned downtime that could affect their bottom line.</p>
<p>
	Plant maintenance and equipment failure analysis stretches across departments, divisions, regions, and even different organizations. You need to include all appropriate stakeholders, both within and outside of the organization, in collaborative processes that make it easy to track any information gathered along the way.</p>
<p>
	Collecting, storing, and retrieving all this data is critical to resolving an unplanned equipment failure. For example, vibration analysis, nondestructive testing results, and digital images should all be stored with the equipment data. This way, maintenance planners can more easily analyze relevant information to determine what improvements the regularly scheduled maintenance needs and improve maintenance frequency.</p>
<ul>
	<li>
		Having plant maintenance hierarchy and associated content &ndash; such as images of failed components &ndash; available from a single interface can cause the epiphany moment that makes you change the required lubrication frequency of a machine, thus extending the component&rsquo;s run life</li>
	<li>
		Accessing historical vibration analysis results allows you to replace a bearing before it fails, ensuring a shorter, planned outage rather than a lengthy, unplanned repair that might also cause collateral damage</li>
</ul>
<p>
	A big-data strategy that integrates all relevant content with your plant operations means you can:</p>
<ul>
	<li>
		Enhance internal and external collaboration around plant maintenance</li>
	<li>
		Improve equipment reliability</li>
	<li>
		Reduce outages and costs due to a simplified process for collecting, storing, and retrieving maintenance information</li>
	<li>
		Improve failure analysis and reporting</li>
	<li>
		Increase regulatory compliance and reduce legal exposure through better records management, traceability, and auditability</li>
</ul>]]></description><comments /><category domain="http://www.aiim.org/Community/search/keyword?w=Big+Data"><![CDATA[Big Data]]></category><category domain="http://www.aiim.org/Community/search/keyword?w=Information+Governance"><![CDATA[Information Governance]]></category><category domain="http://www.aiim.org/Community/search/keyword?w=Enterprise+Asset+Management"><![CDATA[Enterprise Asset Management]]></category><category domain="http://www.aiim.org/Community/search/keyword?w=ECM"><![CDATA[ECM]]></category><category domain="http://www.aiim.org/Community/search/keyword?w=Enterprise+Content+Management"><![CDATA[Enterprise Content Management]]></category><category domain="http://www.aiim.org/Community/search/keyword?w=Plant+Maintenance"><![CDATA[Plant Maintenance]]></category><category domain="http://www.aiim.org/Community/search/keyword?w=" /><pubDate>Wed, 23 May 2012 09:12:36 GMT</pubDate><dc:creator><![CDATA[Bil Khan]]></dc:creator><guid /></item><item><title><![CDATA[PDF - Not dead yet!]]></title><link><![CDATA[http://www.aiim.org/community/blogs/community/PDF-Not-dead-yet]]></link><description><![CDATA[<p>
	I&nbsp;read a blog post several weeks or so ago touting that PDF should die and die fairly soon. This blog post stirred a bit of angst amongst many PDF product developers and individuals who devote time to develop standards to in fact make PDF more open and a better file format. As I read the post and the many comments that were offered, I remembered a phrase from Monty Python, not that I am a Monty Python fan, that goes something like &quot;I&#39;m not dead yet, in fact, I am feeling much better!&quot; I think this phrase summarizes very well the state of PDF.</p>
<p>
	Let me first state, that PDF is not the ONLY file format available and won&#39;t be the ONLY file format that should be used for archiving, turning a revisable electronic documents into a ePaper documents or for exchanging documents. For now, it is available, accepted and is very robust. This robust nature was what prompted NPES and the Graphics Communications Industry along with Adobe Systems to develop what was the first of several specific focused PDF standards to satisfy the needs of prepress printing of advertisements (ISO 15930). From here, we developed variations for archiving (ISO 19005), engineering (ISO 24517), healthcare, universal accessibility (ISO 14289), variable data exchange (ISO 16612) and others. Each of these PDF subset standards was developed to satisfy a specific industry need.</p>
<p>
	The fact that many variations of the PDF standard were developed all based on the PDF Specification shows the versatility of the PDF specification. It is important to remember that even the PDF specification is now an open standard no longer controlled solely by Adobe Systems.&nbsp; In 2007, Adobe Systems approached AIIM (<a href="http://www.aiim.org/standards">www.aiim.org/standards</a> ) requesting that AIIM help foster the PDF Specification through the ISO standardization process. On behalf of ANSI, the American National Standards Institute (<a href="http://www.ansi.org">www.ansi.org</a>), AIIM did just that and ISO was able to publish the PDF specification as ISO 32000-1 in 2008. Yes, Adobe Systems is a player in the development of ISO 32000 and its subsequent versions but there are a host of other PDF developers at the table including Microsoft who along with NetCentric&nbsp;Technologies are the current project leaders for the work on ISO 32000-2.</p>
<p>
	The work on the PDF standards marches onward. With each part of the standard, the file format becomes even more feature rich and better. The ISO working groups will be meeting next week in Canada to focus their attention on the PDF standards as well as on other topics such as trusted repositories, quality issues, document management vocabulary and many other topics.</p>
<p>
	We should remember that PDF is here and available now.&nbsp; Until an alternate file format is available, let&#39;s work together to make this one better. If there are problems with PDF or if there is something you wish PDF did that it does not do today, send your ideas to me at <a href="mailto:bfanning@aiim.org">bfanning@aiim.org</a> or post your ideas as comments to this blog post. I will take them forward to the appropriate PDF committee.</p>
<p>
	When an alternate file format becomes available, make sure you are making an intelligent decision as you decide to adopt it. Some of the factors you should consider when deciding to go to another file format are:</p>
<ul>
	<li>
		Maturity of definition &ndash; Is it&nbsp;based on a beta or draft standard or is it based upon a published standard?</li>
	<li>
		Adoption &ndash; Have the solution providers developed products that support the standard? How many solutions support the&nbsp;standard? How many files have been created using the&nbsp;standard file format?</li>
	<li>
		Endurance &ndash; How long has the standard been available? Are there any implementations of the&nbsp;standard?</li>
	<li>
		Product standards vs infrastructure standards based &ndash; Is the&nbsp;standard developed for a limited number of products or limited to a specific operating system or is it technology neutral and able to be used by many products?</li>
</ul>
<p>
	In addition to the above, you should also give consideration to the sustainability of the file format you choose. In another blog post, I will deal the characteristics of sustainable file formats.</p>
<p>
	While PDF may not be the perfect file format, it is what we currently have to work with. As we wait, remember that you have an opportunity to make the current file formats as good as they can be by making recommendations for improvements to the standards upon which the file formats are based.</p>
<p>
	For more information on standards, please visit <a href="http://www.aiim.org/standards">http://www.aiim.org/standards</a>.<br />
	&nbsp;</p>]]></description><comments><![CDATA[http://www.aiim.org/community/blogs/community/PDF-Not-dead-yet#commentList]]></comments><category domain="http://www.aiim.org/Community/search/keyword?w=ERM"><![CDATA[ERM]]></category><category domain="http://www.aiim.org/Community/search/keyword?w=PDF"><![CDATA[PDF]]></category><category domain="http://www.aiim.org/Community/search/keyword?w=File+Formats"><![CDATA[File Formats]]></category><category domain="http://www.aiim.org/Community/search/keyword?w=PDF/A"><![CDATA[PDF/A]]></category><category domain="http://www.aiim.org/Community/search/keyword?w=PDF/E"><![CDATA[PDF/E]]></category><category domain="http://www.aiim.org/Community/search/keyword?w=PDF/UA"><![CDATA[PDF/UA]]></category><pubDate>Thu, 17 May 2012 16:27:06 GMT</pubDate><dc:creator><![CDATA[Betsy Fanning, CIP,]]></dc:creator><guid /></item><item><title><![CDATA[PDF/A compliance and long-term archiving for SharePoint]]></title><link><![CDATA[http://www.aiim.org/community/blogs/community/PDFA-compliance-and-long-term-archiving-for-SharePoint]]></link><description><![CDATA[<p>
	The City of Hamburg&mdash;the second largest city in Germany&mdash;has deployed a new, electronic information workflow management system named HIM (Hamburg Information Management) to replace the city&#39;s existing paper-based document routing process. The goal of the new system is to accelerate business processes and achieve greater transparency in the enterprise. To handle the conversion of all documents into a uniform PDF/A format, the Hamburg Department of Finance licensed the Hyper.Net&reg; PDF/A Compliance Automator from Coextant Systems.</p>
<p>
	A distinguishing feature of Hamburg&#39;s approach is the use of a single format to store the main content of each e-record managed by the system. This is currently the TIF format. Through the use of the Hyper.Net&reg; PDF/A Compliance Automator, the Hyper.Net&reg; Workload Manager and Hyper.Net Web Services, the city has been able to ensure the long-term readability of content by eliminating the use of proprietary file formats going forward. For this reason, documents in the HIM workflow are now converted after each modification into PDF renditions that are attached back into the corresponding e-record. When a workflow process has been completed, all documents associated with the workflow and the workflow&#39;s audit trail itself are date stamped and comverted into a single compound PDF/A file and transferred to the e-record storage area on the tamper-proof EMC Centera information archive.</p>
<p>
	Throughout the various Hamburg departments and agencies, the HIM workflow&mdash;implemented on the Microsoft SharePoint 2010 platform&mdash;support mores than 10,000 regular users and automates approximately 4,5 million workflow tasks and the conversion of over 40 million pages per year (and correspondingly more when accounting for documents that are subsequently modified).</p>]]></description><comments><![CDATA[http://www.aiim.org/community/blogs/community/PDFA-compliance-and-long-term-archiving-for-SharePoint#commentList]]></comments><category domain="http://www.aiim.org/Community/search/keyword?w=PDFA"><![CDATA[PDFA]]></category><category domain="http://www.aiim.org/Community/search/keyword?w=Compliance"><![CDATA[Compliance]]></category><category domain="http://www.aiim.org/Community/search/keyword?w=SharePoint"><![CDATA[SharePoint]]></category><pubDate>Tue, 08 May 2012 05:02:12 GMT</pubDate><dc:creator><![CDATA[Paul Caspers]]></dc:creator><guid /></item><item><title><![CDATA[Nightmare in the Digital Archives - Digital Preservation Standards]]></title><link><![CDATA[http://www.aiim.org/community/blogs/community/Nightmare-in-the-Digital-Archives-Digital-Preservation-Standards]]></link><description><![CDATA[<p>
	The movie Night at the Museum is a fun way to picture artifacts being preserved for future generations. Just as we preserve these artifacts of societies long past and our current societal relics, we must also be about the business of preserving our digital information. Take a minute to think about how creating information has changed over the last 30 years, not that long of a time period.&nbsp; I can remember at my first job that when I wanted to have a document created, I either wrote the document in long hand or dictated the document into a recorder and either the long hand document or the recording were taken off to a central word processing department where typists made it look &quot;pretty&quot; and like a &quot;real&quot; document. Fast forward a little and now I am my own typist trying to make my documents look professionally done and perfect. Not only do I have to worry about the content but the visual appearance of the document.&nbsp; We also used to wait with anticipation for magazines to come out to give us the latest details about the industry from noted experts, now we are the experts and sharing our knowledge wherever we like to &quot;live&quot; online whether it is a blog, Twitter, an online community and, yes, Facebook and LinkedIn.</p>
<p>
	All of this digital content still needs to be preserved whether it is considered as traditional ERM content or what some may consider &#39;peripheral&#39; content from a social media environment. Like with email, it&#39;s the content that is important and not the container or location of the content. There are many standards available to help you and your organization to properly preserve your digital information. Standards is not a bad word but is a document that you can place your trust in because they are developed by groups of experts who make decisions as to the appropriate requirements to be included in the standard. They are documents that are established by consensus and approved by recognized bodies that have rigorous approval processes and provide common and repeatable rules, guidelines or characteristics.</p>
<p>
	Standards are made available so that you do not need to recreate the wheel, if there is a standard, it is best to use it. There are more important things to be done than to reinvent processes.</p>
<p>
	The following are a few of the standards you should be aware of that will help you to preserve information:</p>
<ul>
	<li>
		&nbsp;ISO 14721, Space data and information transfer systems &ndash; Open archival information systems &ndash; Reference model (OAIS) which is a digital standard freely available on the web and as an ISO standard. It presents a set of theoretical models that represent many aspects of digital preservation from representation of information through metadata to functions and processes that are needed in digital preservation.</li>
	<li>
		&nbsp;ISO 15489, Information and documentation &ndash; Records management is a two part standard often referred to as the &quot;Records Management Bible&quot; that standardizes the best practices for records management. It uses an Australian Standard, AS4390 as its basis to provide guidance on managing records of original documents.</li>
	<li>
		&nbsp;ISO/TR 18492, Long-term preservation of electronic document-based information provides practical methodological guidance for the long-term preservation and retrieval of authentic electronic document based information taking into consideration the role of technology neutral information technology standards that support long-term access to information.</li>
	<li>
		&nbsp;ISO 19005, Document management &ndash; Electronic document file format for long-term preservation which is a three part standard specifying a file format based on PDF, Portable Document Format, that is technology neutral. Two of the three parts have been published. The third part that will be published soon will allow for files to be embedded in the PDF/A file without the file losing its archival nature.&nbsp; This means you will be able to store the native file or XML within the PDF/A file.</li>
</ul>
<p>
	These are just a fraction of the standards available to help you with your digital preservation. Each of them will help your organization to preserve your digital history by ensuring a better success rate with digital preservation and will help to reduce your risks because of the best practices they offer.</p>
<p>
	Instead of a Night at the Museum, I wonder what it would be like at a Night at the Digital Archives. Imagine all the bits and bytes coming to life and surrounding you. It may be more of a nightmare unless we embrace and use some of the industry standards that are available!</p>
<p>
	For more information about standards, <a href="http://www.aiim.org/standards">http://www.aiim.org/standards</a>.<br />
	&nbsp;</p>]]></description><comments><![CDATA[http://www.aiim.org/community/blogs/community/Nightmare-in-the-Digital-Archives-Digital-Preservation-Standards#commentList]]></comments><category domain="http://www.aiim.org/Community/search/keyword?w=Digital+Preservation"><![CDATA[Digital Preservation]]></category><category domain="http://www.aiim.org/Community/search/keyword?w=ERM"><![CDATA[ERM]]></category><category domain="http://www.aiim.org/Community/search/keyword?w=archiving"><![CDATA[archiving]]></category><category domain="http://www.aiim.org/Community/search/keyword?w=standards"><![CDATA[standards]]></category><pubDate>Mon, 07 May 2012 09:19:52 GMT</pubDate><dc:creator><![CDATA[Betsy Fanning, CIP,]]></dc:creator><guid /></item></channel></rss>

