FUNCTIONAL DESIGN Sample Clauses

FUNCTIONAL DESIGN. 2.1 APPROACH For Field Activities (FA) created by City CSR: The following diagram illustrates the processes involved in the creation of the flat file that is interfaced to each Hauler. FDS – Create Download Staging This process looks for all field orders that are marked for extraction (a field order gets marked for extraction when it is first created if its dispatch group is dispatchable). For each record found, the system creates a field order download staging record. Each download staging record is marked with a batch control ID & run number when it’s created. • The batch control ID comes from the field order’s dispatch group. This ID corresponds with a specific extraction method. • The run number is the batch control ID’s current run number. FDL – Create Download Flat File This process reads all download staging records marked with a given batch control ID & run number, and creates the flat files for the Haulers. This process is re-runnable and the flat-files can be reproduced at any time. The no. of files created in each run is dependant on the distinct Distributor Ids (Haulers) for the batch and run number being processed. The file structure is as follows: PeopleSoft RM Field Name Structure Comments FA_ID AN (10) The Field Activity ID in PeopleSoft Revenue Management FA_TYPE_CD AN (8) The Field Activity type code FA_DESCR AN (30) The corresponding FA Description. SP_ID AN (10) The Service Point ID associated to the Field Activity SP_TYPE_CD AN (8) The SP Type Code for the SP_ID that is referenced on the FA. Since the same FA Type can be used across all services, the combination of the FA Description with the SP Type Code will indicate for which service the activity is being performed for. EXTRACT_DTTM DATE (26) CI_FO.EXTRACT_DTTM SCHED_DT DATE (10) CI_FO.SCHED_DT SCHED_TM TIME (15) CI_FO.SCHED_TM FA_STATUS_FLG AN (2) “P” € Pending INSTRUCTIONS AN (254) For applicable FA Types, the current and new Multi-Information will be transferred. This is only applicable for single-row SFDs or Yard Trimming/Street Sweeping Service. For e.g. multi- PeopleSoft RM Field Name Structure Comments row SDF and MFDs, the user (City CSR) is required to manually input the instruction for the Hauler. DESCR254 AN (254) Additional Comments. PREM_ID AN (10) CI_PREM.PREM_ID CU_LEGACY_SLN AN (50) Legacy Service Location Number CI_PREM_GEO.GEO_VAL Where GEO_TYPE_CD = ‘SLN’ (only populate if available) CU_APN AN (50) Current Parcel Number CU_SVC_ADDRESS AN (150) Custom Field. Servic...
Sample 1
AutoNDA by SimpleDocs
FUNCTIONAL DESIGN. Complete functional design layout for the proposed improvements. The primary focus will be on development of roadway geometrics, identify existing and proposed utility locations, identify existing and proposed right-of-way needs, and develop a general staging concept to construct the improvements. The work to be performed by the Consultant under the Functional Design phase shall consist of the following tasks: Task 1 - Develop Design Criteria The Consultant will summarize and submit to the City design criteria used to develop the project. Criteria will conform to the City, Iowa DOT, SUDAS, and AASHTO design standards. The criteria to be addressed include: • Functional classification and design type • Design speed and Regulatory speed • Design vehicles for intersection design • Widths of travel lanes, parking areas, and right-of-way • Preferred Clear Zone • Acceptable Clear Zone • Provisions for pedestrians and/or bicycles • Street lighting requirements • Utility corridor locations Prepare a brief technical memorandum documenting the proposed criteria. The memorandum will be reviewed, revised, and approved by the City prior to proceeding with subsequent tasks. Task 2 - Develop Typical Sections Develop typical sections for the mainline street improvements. This task includes lane widths, curb section/type, sidewalk widths, right-of-way widths, pavement types, and clear-zones. This task does not include pavement and subgrade design. This task also includes identifying potential storm sewer, sanitary sewer, water main, fiber optics, and other utility locations in the development of the typical sections. Detailed design calculations and capacity analysis for storm sewer, water main, or sanitary sewer is not included as part of this task. It is anticipated that three (3) typical cross sections will be developed for West First Street that includes widening to the north, widening to the south, or a symmetrical widening about the centerline of the existing roadway. Typical cross sections will also be developed for each of the side street connections. Task 3 - Develop Functional Geometrics Develop functional geometrics that includes intersection return radii, sidewalk locations, and driveway locations for the project. Included as part of this task is turning design vehicle templates at the intersections.
Sample 1
FUNCTIONAL DESIGN. 2.1 APPROACH For Field Activities (FA) created by City CSR: The following diagram illustrates the processes involved in the creation of the flat file that is interfaced to each Hauler. FDS – Create Download Staging This process looks for all field orders that are marked for extraction (a field order gets marked for extraction when it is first created if its dispatch group is dispatchable). For each record found, the system creates a field order download staging record. Each download staging record is marked with a batch control ID & run number when it’s created. • The batch control ID comes from the field order’s dispatch group. This ID corresponds with a specific extraction method. • The run number is the batch control ID’s current run number. FDL – Create Download Flat File This process reads all download staging records marked with a given batch control ID & run number, and creates the flat files for the Haulers. This process is re-runnable and the flat-files can be reproduced at any time. The no. of files created in each run is dependant on the distinct Distributor Ids (Haulers) for the batch and run number being processed. The file structure is as follows: PeopleSoft RM Field Name Structure Comments FA_ID AN (10) The Field Activity ID in PeopleSoft Revenue Management FA_TYPE_CD AN (8) The Field Activity type code FA_DESCR AN (30) The corresponding FA Description. SP_ID AN (10) The Service Point ID associated to the Field Activity
Sample 1
FUNCTIONAL DESIGN. A detailed functional design specification for the Network Status System will ensure that any reasonable requirements of BDB are met within the constraints of the CTI TOC system. SCHEDULE 4 SERVICES PROVIDED BY CTI GENERAL QUALITY CTI's operation is governed by a quality management system that is accredited to ISO 9001. As far as possible, CTI expects suppliers to operate under similar quality arrangements. CTI staff are chosen with appropriate skills and are kept up to date with training, as needed, in new techniques and systems. SAFETY CTI's internal Safety Policy (the "Safety Policy") fulfils the company's legal requirement under the Health and Safety at Work Xxx 0000. The Safety Policy is carried out through a series of Company Safety Instructions under the auspices of a full-time Company Safety Adviser (CSA). All staff receive relevant training to carry out their jobs in accordance with the Safety Policy. Such training is under continual review.
Sample 1
FUNCTIONAL DESIGN. Contractor shall develop and provide a comprehensive Functional Design Document (FDD) to Agency. Contractor shall maintain components of the design throughout the course of the Project and updated when any System design changes occur. The Contractor shall conduct a walkthrough of the FDD with the Oregon Votes Steering Committee and the External QA Consultant to validate the contents of the FDD. The FDD must incorporate all information from the design sessions and all Functional Requirements. Deliverable(s) and Acceptance Criteria Contractor shall provide the following:
Sample 1
FUNCTIONAL DESIGN. The term “Functional Design” means a written description, usually in technical language, setting forth the specifications for a computer program or configuration of a computer system that implements the Requirements.
Sample 1

Related to FUNCTIONAL DESIGN

  • PROPRIETARY/RESTRICTIVE SPECIFICATIONS If a prospective bidder considers the specification contained herein to be proprietary or restrictive in nature, thus potentially resulting in reduced competition, they are urged to contact the Procurement Division prior to bid opening. Specifications which are unrelated to performance will be considered for deletion via addendum to this Invitation for Bids.

  • Curriculum Development This includes the analysis and coordination of textual materials; constant review of current literature in the field, some of which are selected for the college library collection, the preparation of selective, descriptive materials such as outlines and syllabi; conferring with other faculty and administration on curricular problems; and, the attendance and participation in inter and intra-college conferences and advisory committees.

  • Technical and Organizational Measures The following sections define SAP’s current technical and organizational measures. SAP may change these at any time without notice so long as it maintains a comparable or better level of security. Individual measures may be replaced by new measures that serve the same purpose without diminishing the security level protecting Personal Data.

  • DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK Firms and/or individuals that assisted in the development or drafting of the specifications, requirements, statements of work, or solicitation documents contained herein are excluded from competing for this solicitation. This shall not be applicable to firms and/or individuals providing responses to a publicly posted Request for Information (RFI) associated with a solicitation.

  • Organizational Transition Local Church shall take all steps necessary to close and/or dissolve any legal entities of the Local Church and to settle, liquidate, or transfer all assets and obligations of such entities, or to establish any new legal entities, or to modify its current organizing documents as needed to effectuate its disaffiliation from The United Methodist Church, to the satisfaction of Annual Conference.

  • Appropriate Technical and Organizational Measures SAP has implemented and will apply the technical and organizational measures set forth in Appendix 2. Customer has reviewed such measures and agrees that as to the Cloud Service selected by Customer in the Order Form the measures are appropriate taking into account the state of the art, the costs of implementation, nature, scope, context and purposes of the processing of Personal Data.

  • REGISTRY OPERATOR CODE OF CONDUCT 1. In connection with the operation of the registry for the TLD, Registry Operator will not, and will not allow any parent, subsidiary, Affiliate, subcontractor or other related entity, to the extent such party is engaged in the provision of Registry Services with respect to the TLD (each, a “Registry Related Party”), to:

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