DETAILED SCOPE. This Contract consists of 9 separate Lots, each representing a different fuel type as specified in Section 1.1. All products provided shall be homogenous fuel oil, kerosene or Bio-fuel blends suitable for burner appliances, and they shall conform to the requirements of ASTM D396 (Fuel Oil), ASTM D3699 (Kerosene), ASTM D6751, Bio-fuels or latest revision(s) thereof, or approved equivalent method, except as listed differently elsewhere herein. There shall be no blending of other than pure distillates or unused residual fuel oils for product provided via this Contract.
DETAILED SCOPE. All products provided under the Contract shall be homogenous fuel oil, suitable for diesel engines, and shall conform to the requirements of ASTM D975-08, Table 1, or latest revision thereof, except as provided otherwise herein.
DETAILED SCOPE. A detailed scope of services related to the respective GMP Proposal, including a breakdown of the GMP as it relates to the applicable part of the overall Scope.
DETAILED SCOPE. Sub-Lot Sub-Lot Name Sub-Lot Description 1 Standardized List List of frequently purchased items that have been standardized. The Standardized List contains items that cross other Sub-Lots.
DETAILED SCOPE. Lot 3 – Basic Chemicals Basic Chemicals include products that contain basic and complex chemical compounds routinely used in laboratory or medical settings and are readily available in the marketplace. Examples are acids, bases, alcohols, desiccants, drying agents, detergents, surfactants, dyes, stains, indicators, water, resins, metals, standards, polymers, solvents, organics and inorganics. Lot 4 – Basic Biological Materials Basic Biological Materials include products that contain basic biological substances routinely used in laboratory or medical settings and are readily available in the marketplace. Examples are carbohydrates, lipids, nucleic acids, proteins, antibiotics, antimycotics, cells, culture reagents, growth factors, hormones and reagent kits.
DETAILED SCOPE. Lot 1 – Automotive Parts and Supplies Contractor will provide full products lines for each of the Part Groups listed below. This Lot includes the 29 Part Groups listed below. Contractor will provide a full catalog offering in this Lot for each of the 29 Part Groups listed below. This Lot includes automotive replacement parts and supplies. This Lot does not include Automotive Filters (Lot 2). Part Groups 01 - Brake Shoes & Linings (Rebuilt) 02 - Brake Parts 03 - Rotors and Drums 04 - Shock Absorbers 05 - Mirrors & Lamps 06 - Belts & Hoses
DETAILED SCOPE description of the practice Development Content: Any function or method which might trigger an error shall return the error to the caller (in the form of a return or exception code). This function shall trace the error then either handle it, or return it to its caller. All detected errors shall include an explicit error message to facilitate diagnosis during development or operation. Error messages may be externalized or generated on the fly in the related code sections. Error messages produced by the system shall be collected (log files, tool, console, etc.). The error message format is standardized and compliant with common practice. For example, severity levels comply with Syslog standardization. There is a total of eight levels, identified by a number ranging from 0 (Emergency) to 7 (Debug): ▪ 0 Emergency ▪ 1 Alert ▪ 2 Critical ▪ 3 Error ▪ 4 Warning ▪ 5 Notice ▪ 6 Informational ▪ 7 Debug This indication is particularly important because it standardizes the representation of the severity of a log message, which for example enables interoperability between log collection and alert generation equipment. Means/resources: The acceptance testing phase shall not simply test passing cases. Each potential error case identified shall have a specific acceptance test sheet. Tools: ▪ Log collector, ▪ Syslog, ▪ Surveillance tools, ▪ Automatic analysis tools (e.g. Webalyzer, HDC Syslog). ▪ Automatic alert tool (e.g. sendmail) Check: Relevant tracing of all operation incidents. Stack trace in case of error. Verbose tracing in development mode for debugging CEN/ISSS WORKSHOP Best Practice Sheet # CIS-13 Data timestamping Practice summary Perform data timestamping. Purpose To provide more meaningful and helpful information to clients and users by delivering key values together with their ‘freshness’ i.e. the time when they were entered into the system. CIS requirement(s) concerned Integrity Usability Availability Maintainability Performance Resilience Capacity Security Project phase(s) concerned Development Process: Operation Process: Requirements analysis Operational testing Architectural design System operation Detailed design User support Coding and unitary testing Maintenance Process: Testing and integration Problem and modification analysis Modification implementation Maintenance review/acceptance Migration Related deliverables For significant fields, give date and time when the value was entered into the system Economic impa...
DETAILED SCOPE. All products provided under the Contract shall be homogenous fuel oil, suitable for diesel engines, and shall conform to the requirements of ASTM D975-08, Table 1, or latest revision thereof, except as provided otherwise herein. The scope of each fuel type is detailed below. Regular The symbols 2D and/or 2-D shall be used as a grade designation for middle distillate diesel fuel oils used in vehicular diesel engines and in non-vehicular applications having frequently varying loads and speeds. Shall also be known as Regular.
DETAILED SCOPE. The Scope of Work that follows details the individual tasks and deliverables for the PROJECT. The individual (or sub-) tasks are grouped according to the phases of work as follows: • Task 100 – Preliminary Engineering, Evaluation and Design Basic Services: This section delineates the scope of basic services for the PROJECT. Task 100 – Preliminary Engineering, Evaluation, and Design Task 101 – Project Kick-off and Administration ENGINEER will complete the following activities / develop the following items as part of project planning and set-up activities: • Set-up (i.e., project budget / financials and work plan) • Subconsultant agreements • Invoicing and activity report templates • Project Management and Quality Plan (PMP / QMP) with baseline schedule • Health & Safety Plan (H&SP) (for ENGINEER’s staff and subconsultants only) • Risk Register • Communication tools for ENGINEER’s internal use (i.e., meeting / workshop scheduling and tracking, decision log, change log, and action item tracking) The PMP/QMP will outline the project goals and objectives, scope of work, baseline schedule, support tools, communications protocols, and quality review plan. The quality review plan will incorporate the approach for pointedly engaging technical advisors and specialty expertise in the early phases of the preliminary engineering and development. Project Meeting #1 (Preliminary Engineering and Design Kick-off Meeting) will be held with AWU to confirm key elements of the PMP/QMP, project scope objectives, and the baseline schedule. Throughout project execution, ENGINEER will conduct monitoring and control activities to track project progress and develop monthly invoices with project activity reports for submittal to AWU. Activity reports will document activities completed during the previous period, planned activities for the following month, key decisions made, needed decisions, and decision-related / critical path action items. For this task, up to eight (8) months is assumed for project administration during preliminary engineering, evaluation, and design. Deliverables: • Project Meeting # 1 – Preliminary Engineering and Design Kick-off • Meeting agenda and summary (.pdf format) • PMP / QMP with baseline schedule (.pdf format) • Monthly Invoices with Activity Report (including updated project schedule) Task 102 – Information / Data Collection and Review AWU will provide the ENGINEER with any supplemental information and data for the PBWTP filters (not obtain previousl...
DETAILED SCOPE description of the practice Architecture Design Load qualification Operation Content: List the application's incoming and outgoing flows. Prepare an exhaustive map of the application: prepare a detailed description of flows and flow processing centres; divide flows into categories -- vital vs. non-vital, incoming vs. outgoing, long vs. fast processing. Define possible upstream bottlenecks, and any actions to be taken to diagnose drops in quality of service while the application is running. Means/resources: Business Sponsor: Statement of requirements to clearly identify the amount of information entering the system either synchronously or asynchronously. Business Sponsor / IT team: Specify the volumes and frequency of data entering and leaving the system. Technical Architect: Define the technical architecture, map the flows between modules, and define the system processing capacity. Set up a synchronous or asynchronous call system between modules for processing information. Define specific supervision indicators for data flows and for the processing capacity of the various processors. Be able to accept an extensive workload, mainly during the design phase (to detect all possible flows and to define the flow control mechanisms) and when qualifying system performance. Be present during the development phase to make sure the development team is correctly implementing the specifications. Development Team: Comply with the technical recommendations in the Architecture Document (comply with the specified flows, optimize processing time for complex calculations). Set up a buffer zone and a flow regulator. Perform load tests. Integration Team: Comply with the technical recommendations in the Architecture Document (configuration of buffer zones, compliance with the size of input and output connection pools). Optimize the number of system threads. Operator: Monitor the application and if necessary perform manual interventions to change flow regulator settings. Capacity Planning Manager: Increase the platform's processing capacity. Check: During the technical certification phase: Simulate a heavy incoming flow workload and check that the information is processed correctly at each node in the linkage chain (set up probes or technical counters). Check that the flow control regulators are working correctly.
