Enterprise Content Management Sample Clauses

Enterprise Content Management. Contractor shall provide services to establish or maintain electronic document imaging, document management, document workflow, and associated technologies in the context of enterprise strategy, records management policies, and existing assets. The Association for Information and Image Management (AIIM) defines ECM as the technologies used to capture, manage, store, preserve, and deliver content and documents related to organizational processes. Following are Requirements and Capabilities for this Service: • Accomplish workflow analysis; • Develop/implement document indexing schemes and workload management; • Provide implementation and support services; • Develop system interfaces; • Develop/implement system migration strategies; • Provide document conversion services (hardcopy to electronic or electronic to electronic); • Provide performance monitoring/measurement; • Accomplish system stress testing/benchmarking; and, • Implement document and records retention/archiving strategies/plans. • Provide software maintenance and support activities, including staff training • Migrating data from network shares and/or other document repositories to repositories including SharePoint, Documentum or OnBase. • Optical Character Recognition (OCR) • Zonal OCR • Batch processing • Multiple formats • Large format Engineering documents in color • Microfilm • Record/archival • Presentation • Certified mail receipts – postcards • Medical records • Other non-standard sizes • Resolution options/standards • Integrating document intake with workflow • Indexing • Developing taxonomies and metadata • Working with existing taxonomy and metadata standards • Interface to applications such as SharePoint, Documentum, OnBase.
Sample 1Sample 2Sample 3See All (39)
AutoNDA by SimpleDocs
Enterprise Content Management. Contractor shall provide services to establish or maintain electronic document imaging, document management, document workflow, and associated technologies in the context of enterprise strategy, records management policies, and existing assets. The Association for Information and Image Management (AIIM) defines ECM as the technologies used to capture, manage, store, preserve, and deliver content and documents related to organizational processes. The Vermont State Archives & Records Administration has oversight: xxxxx://xxx.xxx.xxxxx.xx.xx/archives-records/records-management.aspx. Following are Requirements and Capabilities for this Service:  Accomplish workflow analysis;  Develop/implement document indexing schemes and workload management;  Design systems/networks/applications;  Develop application prototype(s);  Provide implementation and support services;  Develop system interfaces;  Develop/implement system migration strategies;  Provide document conversion services (hardcopy to electronic or electronic to electronic);  Provide performance monitoring/measurement;  Accomplish system stress testing/benchmarking; and,  Implement document and records retention/archiving strategies/plans.  Provide software maintenance and support activities, including staff training J. DBA/SQLDBA/Relational Database Support Contractor shall provide services to support the function of database administration. Following are Requirements and Capabilities for this Service:  Support of Oracle Software  Upgrades  PeopleSoft Applications
Sample 1Sample 2See All (4)
Enterprise Content Management. After deployment of the State’s Enterprise Content Management (ECM) external system, a Third-Party Software, into the Production environment the State shall submit a written request to the Contractor to shut down the existing ECM Managed Application. Contractor shall shut down the ECM Managed Application within 10 business days of receiving the State’s request, unless otherwise mutually agreed by Contractor and State. A separate request to the Hosting vendor will be required from State to decommission the corresponding servers for the identified Managed Application. Effective as of the next calendar month after the month in which Contractor shuts down the ECM Managed Application, the Core M&O Services monthly fee shall be reduced by the amount listed in Section 9.1.f. of Attachment B, and the ECM Managed Application’s scope shall be deemed modified as follows: a) “Enterprise Content Management” will no longer be an HSEP Managed Application; and b) The following requirements will be removed from Exhibit 1: Enterprise Content Management Services General Requirements 6.000 Confirm proper operation of the ECM infrastructure. Enterprise Content Management Services General Requirements 6.001 Support and resolve issues elevated from ADPC, BASU & AHS IT for problems encountered using deployed capabilities of ECM architecture (WC, provisioning, authentication, Fed Cloud access). Enterprise Content Management Services General Requirements 6.002 Perform schema changes to support application and environment changes. Enterprise Content Management Services General Requirements 6.003 Participate in maturity of ECM Governance, managed by the State. Enterprise Content Management Services General Requirements 6.004 Provide maintenance and support for middleware and supporting utilities, perform middleware system recovery, and perform controlled stops and restarts to ECM servers as needed. Enterprise Content Management Services General Requirements 6.005 Contractor shall perform those services, functions and responsibilities identified as their respective responsibilities with respect to the installation, configuration, and management of the Enterprise Content Management (ECM). Enterprise Content Management Services General Requirements 6.006 The Contractor shall participate in governance and change management process. Enterprise Content Management Services General Requirements 6.007 Provide, install, configure, maintain, and monitor availability, reliability, and performanc...
Sample 1
Enterprise Content Management. After deployment of the State’s Enterprise Content Management (ECM) external system, a Third-Party Software, into the Production environment the State submitted a written request to the Contractor via CR-031 to shut down the existing ECM Managed Application. Contractor shut down the ECM Managed Application effective November 20, 2019. Effective December 1, 2019 the Core M&O Services monthly fee was reduced by the amount listed in Section 9.1.g.(i) of Attachment B, and the ECM Managed Application’s scope was modified as follows:
Sample 1

Related to Enterprise Content Management

  • Service Management Effective support of in-scope services is a result of maintaining consistent service levels. The following sections provide relevant details on service availability, monitoring of in-scope services and related components.

  • Traffic Management 9.2.1 During the Operating Period, Developer shall be responsible for the general management of traffic on the Project. Developer shall manage traffic so as to preserve and protect safety of traffic on the Project and Related Transportation Facilities and, to the maximum extent practicable, to avoid disruption, interruption or other adverse effects on traffic flow, throughput or level of service on the Project and Related Transportation Facilities. Developer shall conduct traffic management in accordance with all applicable Technical Provisions, Technical Documents, Laws and Governmental Approvals, and in accordance with the Traffic Management Plan. 9.2.2 Developer shall prepare and submit to TxDOT and the Independent Engineer for TxDOT approval a Traffic Management Plan for managing traffic on the Project and Related Transportation Facilities after the commencement of traffic operations on any portion of the Project, addressing (a) orderly and safe movement and diversion of traffic on Related Transportation Facilities during Project construction, (b) orderly and safe movement of traffic on the Project and (c) orderly and safe diversion of traffic on the Project and Related Transportation Facilities necessary in connection with field maintenance and repair work or Renewal Work or in response to Incidents, Emergencies and lane closures. Developer shall prepare the Traffic Management Plan according to the schedule set forth in the Technical Provisions. The Traffic Management Plan shall comply with the Technical Provisions and Technical Documents concerning traffic management and traffic operations. Developer shall carry out all traffic management during the Term in accordance with the approved Traffic Management Plan. 9.2.3 Developer shall implement the Traffic Management Plan to promote safe and efficient operation of the Project and Related Transportation Facilities at all times during the course of any construction or operation of the Project and during the Utility Adjustment Work. 9.2.4 TxDOT shall have at all times, without obligation or liability to Developer, the right 9.2.4.1 Issue Directive Letters to Developer regarding traffic management 9.2.4.2 Provide on the Project, via message signs or other means consistent with Good Industry Practice, non-Discriminatory traveler and driver information, and other public information (e.g. amber alerts), provided that the means to disseminate such information does not materially interfere with the functioning of the ETCS.

  • Exit Management 58.1. The Service Provider shall perform its relevant Exit Management obligations as part of the Contract whether applicable on either the expiry or early termination of this Contract. 58.2. The Service Provider agrees that if it breaches (or attempts or threatens to breach) its obligation to provide Exit Management, the Purchaser and their respective customers and stakeholders shall be irreparably harmed. In such circumstance, the Service Provider agrees that the Purchaser may proceed directly to court notwithstanding anything to the contrary in the dispute resolution procedure outlined in Clause 53 (Dispute Resolution). If a court of competent jurisdiction finds that the Service Provider has breached (or attempted or threatened to breach) any such obligation, the Service Provider agrees that without any additional findings of irreparable injury, or other conditions to interdict, the Service Provider shall not oppose the entry of an appropriate order compelling performance by the Service Provider and restraining the Service Provider from any further breaches or attempted or threatened breaches of its obligations in relation to Exit Management. 58.3. A draft of the Exit Plan shall be produced by the Service Provider and supplied to the Purchaser within [three (3) months] after the Commencement Date and shall include or address the matters specified in Clause 59.3. The Purchaser shall provide to the Service Provider the Purchaser’s comments on the plan within one (1) month of the Purchaser’s receipt of the plan. The Service Provider shall take into account the comments and suggestions of the Purchaser and shall issue the final version of the Exit Plan to the Purchaser within ten (10) Working Days of receipt of the Authority’s comments. 58.4. The Service Provider shall throughout the period of the Contract review, maintain and continuously update the Exit Plan which shall include: 58.4.1. the activities required to enable the Purchaser to re-tender the Purchaser Requirements and/or the provision of the Services; 58.4.2. the activities necessary to support any Replacement Service Provider or the Purchaser in carrying out any necessary due diligence relating to all or part of the Services; 58.4.3. details of the Exit Management to be provided by the Service Provider prior to the Exit Management Date; 58.4.4. support for the Replacement Service Provider or the Purchaser during their preparation of any relevant plan for the transition of the System to the Replacement Service Provider or Purchaser, including prior to and during such transition period; 58.4.5. the maintenance of a ‘business as usual’ environment for the Purchaser during the period when Exit Management obligations are applicable; and 58.4.6. all other necessary activities to support the preparation for, and execution of, a smooth and orderly Exit Management and transfer of all or part of the Services to either a Replacement Service Provider or the Purchaser. 58.5. No amendment of the Exit Plan shall be made without prior written consent of the Purchaser.

  • Virus Management DST shall maintain a malware protection program designed to deter malware infections, detect the presence of malware within DST environment.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Network Management 60.1 CLEC and CenturyLink will exchange appropriate information (e.g., network information, maintenance contact numbers, escalation procedures, and information required to comply with requirements of law enforcement and national security agencies) for network management purposes. In addition, the Parties will apply sound network management principles to alleviate or to prevent traffic congestion and to minimize fraud associated with third number billed calls, calling card calls, and other services related to this Agreement. 60.2 The Parties will employ characteristics and methods of operation that will not interfere with or impair the Parties’ networks, or the network of any third parties or Affiliated companies, connected with or involved directly in the network or facilities of CenturyLink. 60.3 CLEC shall not interfere with or impair service over any circuits, facilities or equipment of CenturyLink, its Affiliated companies, or its connecting and concurring carriers. 60.4 If CLEC causes any impairment or interference, CenturyLink shall promptly notify CLEC of the nature and location of the problem and that, unless promptly rectified, a temporary discontinuance of the use of any circuit, facility or equipment may be required. The Parties agree to work together to attempt to promptly resolve the impairment or interference. If CLEC is unable to promptly remedy, then CenturyLink may, at its option, temporarily discontinue the use of the affected circuit, facility or equipment until the impairment is remedied. 60.5 Any violation of Applicable Law or regulation regarding the invasion of privacy of any communications carried over CenturyLink’s facilities, or that creates hazards to the employees of CenturyLink or to the public, is also considered an impairment of service. 60.6 CenturyLink shall give advanced notice to CLEC of all non-scheduled maintenance or other planned network activities to be performed by CenturyLink on any Network Element, including any hardware, equipment, software, or system, providing service functionality of which CLEC has advised CenturyLink may potentially impact CLEC End Users. 60.7 The Parties shall provide notice of network changes and upgrades in accordance with 47 C.F.R. §§51.325 through 51.335. CenturyLink may discontinue any Interconnection arrangement, Telecommunications Service, or Network Element provided or required hereunder due to network changes or upgrades after providing CLEC notice as required by this Section. CenturyLink agrees to cooperate with CLEC and/or the appropriate regulatory body in any transition resulting from such discontinuation of service and to minimize the impact to customers which may result from such discontinuance of service.

  • Beta Services From time to time, We may invite You to try Beta Services at no charge. You may accept or decline any such trial in Your sole discretion. Beta Services will be clearly designated as beta, pilot, limited release, developer preview, non-production, evaluation or by a description of similar import. Beta Services are for evaluation purposes and not for production use, are not considered “Services” under this Agreement, are not supported, and may be subject to additional terms. Unless otherwise stated, any Beta Services trial period will expire upon the earlier of one year from the trial start date or the date that a version of the Beta Services becomes generally available. We may discontinue Beta Services at any time in Our sole discretion and may never make them generally available. We will have no liability for any harm or damage arising out of or in connection with a Beta Service.

  • Web Services Our Web Services are designed to enable you to easily establish a presence on the Internet. Our Web Hosting and Design is composed of our Web Hosting and Design Publishing Component and other miscellaneous components. These components may be used independently or in conjunction with each other.

  • Telecommunications Services The offering of telecommunications for a fee directly to the public, or to such classes of users as to be effectively available directly to the public, regardless of the facilities used.

  • Network Services Preventive care: 100% coverage. Preventive services include, but are not restricted to routine physical exams, routine gynecological exams, routine hearing exams, routine eye exams, and immunizations. A $100 single and $200 family combined annual deductible will apply to lab/diagnostic testing after which 100% coverage will apply. A $50 copay will apply to CT and MRI scans.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!