<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="stratmliso.xsl"?>
<StrategicPlan xmlns="urn:ISO:std:iso:17469:tech:xsd:stratml_core" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:ISO:std:iso:17469:tech:xsd:stratml_core http://xml.govwebs.net/stratml/references/StrategicPlanISOVersion20140401.xsd"><Name>Future Direction for AIIM iECM Committee (Proposed): Overall Scope and Specific Goals</Name><Description/><OtherInformation/><StrategicPlanCore><Organization><Name>iECM Committee</Name><Acronym>iECM</Acronym><Identifier>_d185abe8-2fda-11e0-ad4e-0f727a64ea2a</Identifier><Description>iECM – Current State: 
* iECM spawned what became the OASIS CMIS effort
* iECM concentrated most recently (2009-2010) on evaluating value of, and investigating best practices to leverage CMIS
* CMIS has been well accepted by vendors and users communities
* iECM’s CMIS based reference applications have been well received, and lessons learned have been published in online sites and blogs 
### 
iECM Committee in 2010: 
* iECM’s contribution to the CMIS spec itself, and the evaluation, as well as the resulting promotion of CMIS have shown past efforts to have been worthwhile
* The current public view of iECM’s past and current efforts is now “Been there, done that. Next!”
* iECM Committee participation is down, way down.
   -- This was not totally unexpected, and the committee has been discussing the need for refocusing and/or redefining itself for about 6 months</Description><Stakeholder StakeholderTypeType=""><Name>Thomas Pole</Name><Description>Co-Chair</Description></Stakeholder><Stakeholder StakeholderTypeType=""><Name>Laurence Hart</Name><Description>Co-Chair</Description></Stakeholder><Stakeholder StakeholderTypeType=""><Name>Betsy Fanning</Name><Description>Director of Standards, AIIM</Description></Stakeholder><Stakeholder StakeholderTypeType=""><Name>Pat Franks</Name><Description>Committee member</Description></Stakeholder><Stakeholder StakeholderTypeType=""><Name>Denise Bedford</Name><Description>Committee member</Description></Stakeholder><Stakeholder StakeholderTypeType=""><Name>Owen Ambur</Name><Description>Committee member</Description></Stakeholder></Organization><Vision><Description/><Identifier>_d185bac0-2fda-11e0-ad4e-0f727a64ea2a</Identifier></Vision><Mission><Description>To establish new direction for AIIM's iECM Committee</Description><Identifier>_d185bc82-2fda-11e0-ad4e-0f727a64ea2a</Identifier></Mission><Value><Name/><Description/></Value><Goal><Name>Adoption and Use of CMIS</Name><Description>Move from evaluation of CMIS to development of best practices for adopting and leveraging CMIS</Description><Identifier>_d185bd7c-2fda-11e0-ad4e-0f727a64ea2a</Identifier><SequenceIndicator>1</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation>Continuing Task</OtherInformation><Objective><Name/><Description/><Identifier>_d185be1c-2fda-11e0-ad4e-0f727a64ea2a</Identifier><SequenceIndicator/><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>CMIS Usefulness</Name><Description>Extend usefulness of CMIS by either adding to CMIS, or developing a parallel solution to the semantic related problems CMIS does not solve</Description><Identifier>_d185be9e-2fda-11e0-ad4e-0f727a64ea2a</Identifier><SequenceIndicator>2</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation>New Task</OtherInformation><Objective><Name/><Description/><Identifier>_d185bf2a-2fda-11e0-ad4e-0f727a64ea2a</Identifier><SequenceIndicator/><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Scope</Name><Description>Develop a process or system development life cycle model for interoperability projects. </Description><Identifier>_d185bfb6-2fda-11e0-ad4e-0f727a64ea2a</Identifier><SequenceIndicator>3</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation>Expanding Scope: Returning to the scope some in the original iECM committee proposed</OtherInformation><Objective><Name>New Scope</Name><Description>Determine the new scope beyond interconnectivity</Description><Identifier>_d185c042-2fda-11e0-ad4e-0f727a64ea2a</Identifier><SequenceIndicator>3.1</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation>* Beyond the CMIS scope of interconnectivity
* The full scope of development and operation of interoperable systems which include but are Not limited to Content Management (i.e. unstructured and semi-structured data)</OtherInformation></Objective><Objective><Name>SDLC</Name><Description>Develop a System Development Life Cycle Model for Interoperability Projects</Description><Identifier>_d185c0e2-2fda-11e0-ad4e-0f727a64ea2a</Identifier><SequenceIndicator>3.1.1</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Best Practices</Name><Description>Research industry interoperability best practices</Description><Identifier>_d185c178-2fda-11e0-ad4e-0f727a64ea2a</Identifier><SequenceIndicator>3.1.1.1</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Technologies and Procedures</Name><Description>Research evolving new technologies and procedures to support interoperability</Description><Identifier>_d185c218-2fda-11e0-ad4e-0f727a64ea2a</Identifier><SequenceIndicator>3.1.1.2</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Outreach</Name><Description>Reach out to other research, professional and standards organizations to coordinate interoperability research and solutions from multiple domains and markets</Description><Identifier>_d185c2f4-2fda-11e0-ad4e-0f727a64ea2a</Identifier><SequenceIndicator>3.1.1.3</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name>Research Organizations</Name><Description/></Stakeholder><Stakeholder StakeholderTypeType=""><Name>Professional Organizations</Name><Description/></Stakeholder><Stakeholder StakeholderTypeType=""><Name>Standards Organizations</Name><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Project</Name><Description>Specify the elements of the new project</Description><Identifier>_d185c39e-2fda-11e0-ad4e-0f727a64ea2a</Identifier><SequenceIndicator>3.2</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation>* Building on what has been accomplished
* Building toward a more full scope solution</OtherInformation></Objective><Objective><Name>IDDIM SDLCM</Name><Description>Specify an Interoperable Data Document and Image Management (IDDIM) Systems Development Life Cycle Model (SDLCM)</Description><Identifier>_d185c434-2fda-11e0-ad4e-0f727a64ea2a</Identifier><SequenceIndicator>3.2.1</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Organizational Change, Semantics, and Work Flows</Name><Description>Broaden scope beyond the system engineering process, to handle organizational change management as well as cross-enterprise semantic and work flow issues</Description><Identifier>_d185c4de-2fda-11e0-ad4e-0f727a64ea2a</Identifier><SequenceIndicator>3.2.1.1</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>O&amp;M</Name><Description>Broaden life cycle beyond new service development, by extending the model into the operation and maintenance phases of the life cycle</Description><Identifier>_d185c5ce-2fda-11e0-ad4e-0f727a64ea2a</Identifier><SequenceIndicator>3.2.1.2</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Resources</Name><Description>Identify additional resources</Description><Identifier>_d185c682-2fda-11e0-ad4e-0f727a64ea2a</Identifier><SequenceIndicator>3.3</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation>* New committee members/workers
* New organizations/partnerships</OtherInformation></Objective><Objective><Name>New Resources</Name><Description>Engage More Interested Members and Partners, with New Experience and Abilities</Description><Identifier>_d185c72c-2fda-11e0-ad4e-0f727a64ea2a</Identifier><SequenceIndicator>3.3.1</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name>Information Scientists</Name><Description>New Members</Description></Stakeholder><Stakeholder StakeholderTypeType=""><Name>Business process Analysts</Name><Description>New Members</Description></Stakeholder><Stakeholder StakeholderTypeType=""><Name>Librarians</Name><Description>New Members</Description></Stakeholder><Stakeholder StakeholderTypeType=""><Name>Ontologists</Name><Description>New Members</Description></Stakeholder><Stakeholder StakeholderTypeType=""><Name>Academia</Name><Description>New Partners</Description></Stakeholder><Stakeholder StakeholderTypeType=""><Name>“Other” Vendors</Name><Description>New Partners</Description></Stakeholder><Stakeholder StakeholderTypeType=""><Name>“Other” standards organizations</Name><Description>New Partners</Description></Stakeholder><Stakeholder StakeholderTypeType=""><Name>OCLC</Name><Description>New Partner</Description></Stakeholder><Stakeholder StakeholderTypeType=""><Name>ASIST</Name><Description>New Partner</Description></Stakeholder><Stakeholder StakeholderTypeType=""><Name>OMG</Name><Description>New Partners</Description></Stakeholder><OtherInformation/></Objective></Goal></StrategicPlanCore><AdministrativeInformation><PublicationDate>2011-02-03</PublicationDate><Source>http://xml.fido.gov/stratml/carmel/iso/iECMwStyle.xml</Source><Submitter><GivenName>Owen</GivenName><Surname>Ambur</Surname><PhoneNumber/><EmailAddress>Owen.Ambur@verizon.net</EmailAddress></Submitter></AdministrativeInformation></StrategicPlan>