ARCHITECTURE DESCRIPTION Sample Clauses

ARCHITECTURE DESCRIPTION. The architecture as shown in figure 23 is made up of three principal components: the neuGRID Single Sign-On (SSO) system, the neuGRID dashboard (menu – in orange) and the neuGRID JSR286/WSRP 2.0 compliant portal.
Sample 1
AutoNDA by SimpleDocs
ARCHITECTURE DESCRIPTION. There are three main technical components of the anonymization service: • The neuGRID pseudonymization library • The Pseudonymization Web Service • The Pseudonymization applet/stand alone application The neuGRID pseudonymization library is a Java library providing the necessary methods required to pseudonymize DICOM images in a reusable form. In order to leverage the work and reuse what has already been done the library is using an already existing DICOM manipulation library, the dcm4che2 toolkit. dcm4che2 is a high performance, open source implementation of the DICOM standard. The neuGRID pseudonymization library allows sharing of the pseudonymization code between both the Pseudonymization Web Service and the pseudonymization applet/standalone application ensuring that the same coherent level of pseudonymization is used throughout the neuGRID infrastructure. The Pseudonymization Web Service is the point of entry in the neuGRID infrastructure to pseudonymize and upload the images. It allows users to send images for pseudonymization and once done, these images can be uploaded on the GRID, registered into LORIS and used by neuGRID users. The Pseudonymization applet/stand alone application is a tool that will be provided to neuGRID's users to help them pseudonymize images without having to send the images outside the walls of the hospital. The pseudonymization applet will make full usage of the latest Java features allowing the creation of an applet that can be dragged out of a browser and that can be used outside of the browser's context without having to be connected to the Internet. To provide a web- friendly access, the following two steps have been planned initially: • The development of an applet for the pseudonymization of images. • The adaptation of the applet to allow it to be fully functional outside of the browser. The data anonymization process is described through the steps shown in figure 30 whereas in figure 31 an overview of the Service deployment is shown.
Sample 1
ARCHITECTURE DESCRIPTION. From the requirement analysis in the previous chapter it becomes clear that the EUMSSI system should fulfil three main functions:  Collect and store (meta-)data of multimedia resources from several sources in a unified format.  Enrich the existing data with the (combined) outcomes of audio, video and text analysis.  Provide end-users (journalist and second-screen users) with useful and/or entertaining suggestions, background information and recommendations. Along with discussions on the system’s functionality, several iterations of architecture sketches have been created with the intention to communicate the envisaged functionality to the consortium partner, and to facilitate the selection of components. In the next section, we summarize the different iterations, to provide a historical background on the design decisions, as reflected in the current architecture. The current software architecture design is discussed in Section 4.2. We will first provide an overview of the four main components, followed by a more detailed description of the main functionality and – where applicable – the framework or tools that will be used for implementing the component. The second part of the architecture design involves the process flows, which are illustrated in section 4.2.2.
Sample 1
ARCHITECTURE DESCRIPTION. 26 -------------------------------------------------------------------------------- HP InkJet Commercial Division Monday, December 10, 2001 HP SW RIP External Reference Specification [hp logo] --------------------------------------------------------------------------------
Sample 1
ARCHITECTURE DESCRIPTION. When talking about RP requirements we say that the RIP will act as a "Front End (FE)", so in this section we will use this term instead of the usual RIP one. In the Remote Proofing (RP, in short) service, the Front Ends (FE) can act as two different actors: o Front End as a consumer of Remote Proofs: in this role, the Front End prints proofs. o Front End as a producer of Remote Proofs: in this role, the Front End generates the proof file that is going to be proofed. o The proof file must follow the Remote Proof Data Exchange Format Specification. The FE (SW RIP) described in this specification will work ONLY as a consumer of proof jobs. The FE communicates with a local application that it's installed at the same time (so, it's always available). We call this application the HP Remote Proofing (RP) engine. In the picture below you can see the different components in the system, and the interfaces among them. The FE can receive files through the input hot folder from the PS driver (regular path) or from the remote proofing service (remote proofing path). -------------------------------------------------------------------------------- HP InkJet Commercial Division Monday, December 10, 2001 HP SW RIP External Reference Specification [hp logo] -------------------------------------------------------------------------------- -------------- Graphic design -------- application \ Internet -------------- \ TIFF, JPEG,... -------- \ | App file | \ | --------- \ ---------------------------- PS driver \ HP RP engine --------- \ (with UI) \ \ ---------------------------- PS \ \ / | \ \ / | \ \ / JDF file with a | \ \ / reference to a | \ \ / PDF job file | ----------------------------------------- | Input Hot | Folder | ----------------------------------------- | | ----------------------------------------- FE engine ----------------- (no RP UI) -------------- Output Hot folder ----------------------------------------- XML ----------------- | notifications | (job status) | | ----------------------------------------- Printer/Proofer ----------------------------------------- The interfaces between the HP RP engine and the FE server are: o The RP-to-FE Input Hot Folder for reception of JDF job files. The format of these files is defined in the document: "HP Remote Proofing Data Exchange Format Specification". o The FE-to-RP Output Hot Folder for notifications from the FE engine to the HP RP engine. This Hot Folder will consist of a queue of events (Remote Proofing Events fro...
Sample 1

Related to ARCHITECTURE DESCRIPTION

  • Project Description In two or three brief sentences, provide a concise description of your exhibition. Include the subject matter, type of objects to be included (paintings, sculpture, manuscripts, etc.), those responsible for organizing the exhibition, and catalogue author(s).

  • Service Description The Parties will provide Common Channel Signaling (CCS) to one another via Signaling System 7 (SS7) network Interconnection, in accordance with prevailing industry standards. Use of a third party provider of SS7 trunks is permitted.

  • GENERAL SERVICE DESCRIPTION Service Provider currently provides active medical, pharmacy(Rx) and dental administration for coverages provided through Empire and Anthem (medical), Medco(Rx), MetLife(dental) and SHPS (FSA) (Empire, Anthem, Medco, MetLife and SHPS collectively, the “Vendors”) for its U.S. Active, Salaried, Eligible Employees (“Covered Employees”). Service Provider shall keep the current contracts with the Vendors and the ITT CORPORATION SALARIED MEDICAL AND DENTAL PLAN (PLAN NUMBER 502 EIN 00-0000000) and the ITT Salaried Medical Plan and Salaried Dental Plan General Plan Terms (collectively, the “Plans”) and all coverage thereunder in full force through December 31, 2011 for Service Recipient’s Covered Employees. All claims of Service Recipient’s Covered Employees made under the Plans and incurred on or prior to December 31, 2011 the (“2011 Plan Year”) will be adjudicated in accordance with the current contract and Service Provider will continue to take such actions on behalf of Service Recipient’s Covered Employees as if such employees are employees of Service Provider. All medical, dental, pharmacy and FSA claims of Service Recipient’s Covered Employees made under the Plans (the “Claims”) will be paid by the Vendors on behalf of the Service Provider. Service Recipient will pay Service Provider for coverage based on 2011 budget premium rates previously set for the calendar year 2011 and described in the “Pricing” section below. Service Recipient will pay Service Provider monthly premium payments for this service, for any full or partial months, based on actual enrollment for the months covered post-spin using enrollments as of the first (1st) calendar day of the month, commencing on the day after the Distribution Date. Service Recipient will prepare and deliver to Service Provider a monthly self xxxx containing cost breakdown by business unit and plan tier as set forth on Attachment A, within five (5) Business Days after the beginning of each calendar month. The Service Recipient will be required to pay the Service Provider the monthly premium payments within ten (10) Business Days after the beginning of each calendar month. A detailed listing of Service Recipient’s employees covered, including the Plans and enrollment tier in which they are enrolled, will be made available to Service Provider upon its reasonable request. Service Provider will retain responsibility for executing funding of Claim payments and eligibility management with Vendors through December 31, 2013. Service Provider will conduct a Headcount True-Up (as defined below) of the monthly premiums and establish an Incurred But Not Reported (“IBNR”) claims reserve for Claims incurred prior to December 31, 2011 date, but paid after that date, and conduct a reconciliation of such reserve. See “Headcount True-Up” and “IBNR Reconciliation” sections under Additional Pricing for details.

  • Product Description The lead products covered by this Settlement Agreement is limited to following Amazon Identification Number (ASIN) B0BBMRLNV9, with the description, "Lesnow 63-37 Tin Lead Rosin Core Solder Wire for Electrical Soldering 0.8mm Soldering Wire Electronics Solder Content Solder Flux 1.8% (0.8mm, 50g)," which was offered for sale by the Settling Entity on xxxxxx.xxx, hereinafter the “Product” or “Products.”

  • SERVICE LEVEL DESCRIPTION The Fund Accounting Agreement is hereby amended by deleting the Service Level Description attached thereto and replacing it in its entirety with the Service Level Description attached hereto.

  • Aircraft Description The Option Aircraft are described by Boeing Detail Specification D6-38808, Revision E, dated September 15, 1995, as amended and revised pursuant to the Agreement.

  • Configuration The configuration for the Purchase Right Aircraft will be the Detail Specification for Model 767-3S2F aircraft at the revision level in effect at the time of the Supplemental Agreement. Such Detail Specification will be revised to include (i) changes required to obtain required regulatory certificates and (ii) other changes as mutually agreed upon by Boeing and Customer.

  • Property Description A document prepared as an exhibit for the conveyance of a property interest, reflecting a boundary survey, signed and sealed by a Registered Professional Land Surveyor (RPLS), attached to an acquisition deed as Exhibit A, and consists of the following two (2) parts:

  • Investment Description Each Fund will invest and reinvest its assets in accordance with the investment objective(s), policies and limitations specified in the prospectus (the “Prospectus”) relating to such Fund filed with the Securities and Exchange Commission (the “SEC”) as part of the Fund’s Registration Statement on Form N-1A, as it may be periodically amended or supplemented and in accordance with exemptive orders and no-action letters issued to the Trust by the SEC and its staff.

  • Description of Work (a) that has been omitted or

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