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
DETAILED SCOPE. Lot 1 – Automotive Parts and Supplies
DETAILED SCOPE description of the
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 description of the practice Design: Define an event collection and reporting mechanism suitable to the context: Standardization of traces Completeness of information Development: At each event, update -- and verify the updating of -- trace files: add the error type, severity, and transaction ID in the appropriate fields. Operation: Analyze the trace files and determine the cause of the failure P.S.: at this point we manage technical errors only, not application errors Content: The diagnosis of incidents shall follow two major themes: Setting up of supervision indicators for both tracking activity and detecting any abnormal behaviour: drop in daily data/transaction volume, change in average response times, etc. The trace details errors with in particular: standardized error logging (format, tools), explicit error messages about the type of error and the execution context. In the logging system, each transaction shall have a unique ID across all runtime modules, in order to enable detailed tracking. Thus it is necessary to include a field in the log files indicating the transaction ID. At every step in a transaction, traces shall systematically include a field indicating the transaction ID. Means/resources: Tools: Log collector (GES), Syslog, Surveillance tools, Automatic analysis tools (e.g. Webalyzer, HDC Syslog). Audit table Automatic alert tool (e.g. sendmail) Resources: Architect: design (rule definitions), validation of development Developer: Implementation of the rules Operator Check: Prepare a test plan including scenarios related to the presence of this ID in the traces Results of the technical acceptance testing: Verification that each possible case of a technical error results in the requested trace The acceptance testing phase shall not simply test passing cases. Each potential error case identified shall have a specific acceptance test sheet. Application behaviour during operation and diagnosis associated with an incident 6.17. BPS # CIS-17 – PKI-BASED TRACEABILITY Practice summary Comply with traceability requirements related to Identity and Access Management (IAM) based on a Public Key Infrastructure (PKI). Purpose The objectives cover the following: 1) Identification and Authentication 2) Role Information assignment to the subject or object 3) Audit Logs CIS Integrity Usability requirement(s) concerned Availability Performance Capacity Maintainability Resilience Security Project phase(s) concerned Dev...
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. • 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 previously as part of t...
