Service Component Reference Model Sample Clauses

Service Component Reference Model. (SRM) The SRM categorizes service components that support agencies’ business and performance objectives. The SRM is focused on standardizing technology and application service components to support government business operations. The SRM framework promotes the sharing, consolidation, and “re-use” of business processes and services capabilities across the federal government. IT investments must be aligned with service capabilities required to support agencies’ business operations. The Application Services address requirements for service components that support enterprise and organizational processes. The Application Services provide support for mission-critical business applications and collaborative service capabilities. These services include support for developing and implementing enterprise and departmental-level business applications. These applications may be “cross-cutting” in nature, with inter-related service processing components extending across/beyond the enterprise, or unique to a particular agency/department’s mission requirements. The Application Services are aligned with the service domains defined in the FEA SRM: Customer Services; Process Automation; Business Management Services; Digital Asset Services; Business Analytical Services; Back Office Services; and Support Services. The Alliant SB GWAC also includes services for developing and implementing systems required to support unique agency and departmental-level mission requirements. Detailed information pertaining to the FEA SRM is available at the following URL: xxxx://xxx.xxxxxxxxxx.xxx/omb/egov/a-4-srm.html
AutoNDA by SimpleDocs

Related to Service Component Reference Model

  • Schematic Design Phase Services § 3.2.1 The Architect shall review the program and other information furnished by the Owner, and shall review laws, codes, and regulations applicable to the Architect’s services.

  • Product References a. “Or Equal” In all Solicitations or Bid Specifications, the words “or equal” are understood to apply where a copyrighted, brand name, trade name, catalog reference, or patented Product is referenced. References to such specific Product are intended as descriptive, not restrictive, unless otherwise stated. Comparable Product will be considered if proof of compatibility is provided, including appropriate catalog excerpts, descriptive literature, specifications and test data, etc. The Commissioner’s decision as to acceptance of the Product as equal shall be final.

  • OPEN SOURCE COMPONENTS The DS Offerings may include open source components. Whenever notices (such as acknowledgment, copies of licenses or attribution notice) are required by the original licensor, such notices are included in the Documentation of the DS Offerings. Moreover, some open source components may not be distributed and licensed under the terms of the Agreement but under the terms of their original licenses as set forth in the Documentation of the DS Offerings themselves. Source code for open source software components is available upon request. Except for components mentioned in the section EXCLUSIONS below, the warranty and indemnification provided by DS under the Agreement apply to all open source software components and shall be provided by DS and not by the original licensor, but only for the use of the DS Offerings that is in compliance with the terms of the Agreement, and in conjunction with the DS Offerings. The original licensors of said open source software components provide them on an “as is” basis and without any liability whatsoever to Customer.

  • Alternative Work Schedule An alternate forty (40) hour work schedule (other than five (5) uniform and consecutive eight (8) hour days in a seven (7) day period), or for hospital personnel an eighty (80) hour workweek in a fourteen (14) day period and other mutually agreed upon schedules that comply with applicable federal and state law. Employee work schedules normally include two (2) consecutive days off.

  • LIMITATIONS ON REVERSE ENGINEERING, DECOMPILATION AND DISASSEMBLY You may not reverse engineer, decompile, or disassemble the Software, except and only to the extent that such activity is expressly permitted by applicable law notwithstanding this limitation.

  • Software Components At any time during the contract period of performance, the Government may require the Contractor to remedy any failure of the software to comply with the requirements of this contract. Support shall consist of correction of errors, provision of modifications, improvements, and other products the original manufacturer makes available to the Government without charge. The Government shall also be provided full documentation of changes and/or modifications to the software provided to meet the Government's requirements.

  • Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.

  • Technical References Technical References that describe the practices, procedures and specifications for certain services (and the applicable interfaces relating thereto) are listed on Schedule 2.3 (the “Technical Reference Schedule”) to assist the Parties in meeting their respective responsibilities hereunder.

  • Post-Commercial Operation Date Testing and Modifications Each Party shall at its own expense perform routine inspection and testing of its facilities and equipment in accordance with Good Utility Practice as may be necessary to ensure the continued interconnection of the Large Generating Facility with the Participating TO’s Transmission System in a safe and reliable manner. Each Party shall have the right, upon advance written notice, to require reasonable additional testing of the other Party’s facilities, at the requesting Party’s expense, as may be in accordance with Good Utility Practice.

  • Program Components Activities and services delivered under this Program Element align with Foundational Programs and Foundational Capabilities, as defined in Oregon’s Public Health Modernization Manual, (xxxx://xxx.xxxxxx.xxx/oha/PH/ABOUT/TASKFORCE/Documents/public_health_modernization_man ual.pdf) as well as with public health accountability outcome and process metrics (if applicable) as follows:

Time is Money Join Law Insider Premium to draft better contracts faster.