Justification for Uncovered Requirements Sample Clauses

Justification for Uncovered Requirements. ‌ The following tables summarize all system requirements identified as “uncovered” by a demonstration scenario. Several types of justification arise: - Requirement will be solely verified by review of the design, therefore no test or demonstration is required. - Requirement formulation was too detailed for the initial phase of the project. It is therefore transferred as a Technical Requirement to be verified in the next phase of the project. - Requirement is no longer applicable to the revision dLSAFFE design, following SRR. The requirement is therefore discarded. - Requirement is no longer considered relevant for the current design of PULSAR. In this case, a specific justification is provided. SR Id SR Title SR Description Justification PULSAR-REQ-Core-F- 080 Object pose estimation using model-based tracking Position and orientation of the object of interest shall be estimated with respect to the camera frame. The approach is based on the knowledge of the object CAD model to track visual features and compute the object pose. This method is less robust than pose estimation from fiducial marker detection and does not produce more accurate results. Moreover, model-based tracking method needs to be set with an initial pose and this is done usually using a fiducial marker. PULSAR-REQ-dPAMT- S/C-D-010 Work place connected to S/C The work place for robotized assembly is rigidly connected to the S/C platform Requirement will be verified by review PULSAR-REQ-dPAMT- dRAS-F-010 Manipulator The manipulator shall have a redundant kinematics with at least 7-dof Requirement will be verified by review PULSAR-REQ-dPAMT- dRAS-D-020 Joints of Manipulator Each joint of the manipulator contains following components at least: · drive · gear box · control unit · internal position and force/torque sensors internal power supply Requirement will be verified by review PULSAR-REQ-dPAMT- dRAS0-P-030 Performance of Manipulator The payload of the RAS should not be higher than 7kg. The inner diameter of the hexagonal shape should not be larger than 30 cm (TBD) Requirement will be verified by review PULSAR-REQ-dPAMT- dRAS-F-040 Gripper Interface The robot arm is equipped with an actuated SIROM interface (TBC) Requirement will be verified by review PULSAR-REQ-dPAMT- dRAS-F-060 Robot Control Unit (RCU) RAS should have a dedicated control computer Requirement will be verified by review PULSAR-REQ-dPAMT- dRAS-F-070 Deterministic real time operating system The operating system for the RCU sho...
Sample 1
AutoNDA by SimpleDocs

Related to Justification for Uncovered Requirements

  • Child Abuse Reporting Requirement Grantee will:

  • Child Abuse Reporting Requirements A. Grantees shall comply with child abuse and neglect reporting requirements in Texas Family Code Chapter 261. This section is in addition to and does not supersede any other legal obligation of the Grantee to report child abuse.

  • Minimum System Requirements The following summarizes the minimum office system requirements for all Contractors and Architect/Engineer to possess in order to participate. It is the responsibility of all Contractors and Architect/Engineer to possess these minimum requirements at no additional cost to Princeton University.

  • Testing/Trouble Reporting 1.15.1 TWTC will be responsible for testing and isolating troubles on Network Elements. TWTC must test and isolate trouble to the AT&T network before reporting the trouble to the Network Elements Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from AT&T at the time of the trouble report, TWTC will be required to provide the results of the TWTC test which indicate a problem on the AT&T network. Version: 4Q06 Standard ICA 11/30/06

  • Compliance with Accessibility Standards All parties to this Agreement shall ensure that the plans for and the construction of all projects subject to this Agreement are in compliance with standards issued or approved by the Texas Department of Licensing and Regulation (TDLR) as meeting or consistent with minimum accessibility requirements of the Americans with Disabilities Act (P.L. 101-336) (ADA).

  • Loop Testing/Trouble Reporting 2.1.6.1 Think 12 will be responsible for testing and isolating troubles on the Loops. Think 12 must test and isolate trouble to the BellSouth portion of a designed/non- designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Think 12 will be required to provide the results of the Think 12 test which indicate a problem on the BellSouth provided Loop.

  • FLORIDA CONVICTED/SUSPENDED/DISCRIMINATORY COMPLAINTS By submission of an offer, the respondent affirms that it is not currently listed in the Florida Department of Management Services Convicted/Suspended/Discriminatory Complaint Vendor List.

  • Quality- and Cost-Based Selection Except as ADB may otherwise agree, the Borrower shall apply quality- and cost-based selection for selecting and engaging consulting services.

  • Certification Regarding Debarment, Suspension, Ineligibility and Voluntary Exclusion First Tier Participants:

  • Trunk Forecasting Requirements 14.2.1 Initial trunk forecast requirements. At least ninety (90) days before initiating interconnection in a LATA, Alltel shall provide Verizon a two (2)-year traffic forecast that complies with the Verizon Interconnection Trunking Forecast Guide, as revised from time to time. This initial traffic forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Interconnection Trunk groups in the LATA over the next eight (8) quarters.

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