Technology Overview Clause Samples
The Technology Overview clause provides a summary of the key technologies, systems, or platforms involved in the agreement or project. It typically outlines the main components, their intended functions, and how they interact within the broader solution, offering context for the technical aspects of the contract. By presenting this information upfront, the clause ensures that all parties have a shared understanding of the technological framework, which helps prevent misunderstandings and sets clear expectations for the project's technical scope.
Technology Overview. 2.3.1 Genuity ATM Switches Genuity selected the Ascend models CBX-500 & GX-550 switch as its core network ATM switches.
Technology Overview. 2 2.3.1 Genuity ATM Switches.................................................................... 2 2.3.2 Integrated Local Management Interface (ILMI)............................................ 2
Technology Overview. Each Counterparty doing business with Owner is required to have access to computer hardware and software that meet the requirements of the Proliance® project management software. Proliance® software and licenses to use the project database will be provided by Owner or its parent, for the duration of the Project. The hardware and software required to access this system via the Internet is to be provided by each party accessing the software. Licenses to Owner’s or its parent’s database will permit access only to this project, in accordance with permission levels configured by Owner’s or its parent’s Proliance® administrator.
Technology Overview. The technology plan creates capabilities to enable secure data exchanges for clinical and payor data as illustrated below. Clinical data will be exchanged between each of the participating practices and hospitals and the Health Information Exchange New York (HIXNY), the regional health exchange serving northern New York. HIXNY is then capable of securely sending clinical data to the clinical data warehouse (QDC). The payor data will be submitted by participating health plans, by patient, to a separate, secure payor data warehouse. Information from both the payor and EHR warehouses will ultimately be available to participating practices, and both will provide the tools necessary for practice-level continuous quality improvement as well as clinical decision support for population health management. The patient Data Warehouse will include data from the primary care providers’ EHRs augmented by the HIXNY patient record, while the Payor Data Warehouse will contain a holistic view of the patient’s experience from all the providers who have filed claims with the Adirondack Medical Home health plans for the patient. These data warehouses leverage similar web based reporting tools but utilize different, yet complementary information. Combined, these two warehouses create a more comprehensive view of the patients’ experience that neither warehouse would be able to individually provide. In addition, the three Pods were designed to enable practices to leverage the clinical decision informatics now available, including population health management and continuous quality improvement activities. Additionally, the use of the information contained in these data warehouses will facilitate the practices’ and the Pods’ ability to improve chronic disease care management, population health improvement and continuous quality improvement, utilizing the “Plan Do Study Act” (PDSA) methodology.
Technology Overview. Autologous Engineered Skin Substitutes (ESS). Over more than 20 years, preclinical and clinical studies have resulted in development of autologous ESS. Classified as a medical devices, ESS currently consists of a lyophilized sponge of collagen and chondroitin-sulfate, populated with cultured dermal fibroblasts and epidermal keratinocytes which organize into an analog of skin tissue (Figure 1). The device develops epidermal barrier and basement membrane 13, and releases high levels of angiogenic growth factors, including but not limited to, Vascular Endothelial Growth Factor (VEGF), basic Fibroblast Growth Factor (bFGF), and Transforming Growth Factor-beta 1 (TGF-β1) 14-16. In addition, both eratinocytes and fibroblasts in culture are known to release inflammatory mediators which promote transient development of fibro-vascular tissue 17.
Figure 1. Histology of A) native human skin (NHS), and C) engineered skin substitute (ESS). The epidermal anatomy of ESS resembles closely that of NHS with proliferating keratinocytes of the epidermal component (e) attached to the dermal component (d), nucleated suprabasal cells analogous to the spinous layer in NHS, and a keratinized surface layer that resembles the protective stratum corneum. Adhesion of the epidermis results from development of basement membrane proteins, B) collagen IV and D) laminin 5; E) BrdU-positive nuclei; F) Integrin β4. Scale bar = 0.1 mm.
Technology Overview. Prudential’s Customer Service organization uses a standard, well-defined hardware and software suite to perform all operations in the course of satisfying Prudential’s Customer requests. This infrastructure consists of a PC for all data related activities. Workstation PCs are connected to a Local Area Network (“LAN”) segment, that is connected to a Wide Area Network (“WAN”), that is connected to Prudential’s primary and backup data processing centers.
Technology Overview. VPS is a framework built in Java to measure quantifiable data across clients and servers in an architecture, operating system and application independent method on the Internet (or the Intranet).
Technology Overview. The Company’s goal is to provide SMS-based mobile entertainment to any owner of a mobile phone on the GSM networks. The Mobile Warrior technology consists of a multi-player, location based mobile role-playing game.
Technology Overview. 6.5.1 The core technologies for the project are: • Java 8 • Spring framework, including Spring Boot and Spring MVC • Thymeleaf for web page templating • JUnit and Mockito for unit testing • SLF4J for logging • Liquibase for database schema management • Cucumber and Selenium Webdriver for automated end-to-end testing • Togglz for feature toggles Swagger for API documentation. • Gluu open source Identity Provider (IdP) Linux is required to run GLUU build
6.16 Compiling SCSS to CSS
6.16.1 The SCSS source files are located in digits-poc/src/main/scss.
6.16.2 IMPORTANT: Do NOT edit any of the SCSS files located in digitspoc/src/main/scss/govuk/. Any changes to the styling can be made directly in digits-poc/src/main/scss/digits.scss.
6.16.3 To compile the digits.css you will need to install SASS (if you haven't already). Instruction on how to install SASS on your machine (Linux, Windows, Mac) can be found here: ▇▇▇▇▇://▇▇▇▇-▇▇▇▇.▇▇▇/install
6.16.3.1 There are 2 ways to compile the CSS from digitspoc/src/main/scss/digits.scss
6.16.3.2 sass--watch scss/digits.scss:resources/static/assets/stylesheets/digits. css -- sourcemap=none It will detect any changes made to digits.scss and compile automatically