Home

Results 1 - 10 of 476,151 for software aids. Search took 1.676 seconds.  
Sort by date/Sort by relevance
With regard to the “Education Grants Job Aid”, the Tribunal notes that it provides guidance to Human Resources officials in administering education grants, but they are not binding rules and regulations. 80. (...) According to the Applicant’s contract with the school, specialized technology services fees are defined as “software, laptop, materials, maintenance, interactive white boards, multimedia”. 95. (...) To support this decision, the Respondent submits that under the “Education Grants Job Aid”, “[c]omputers ([the] purchase of)” are not admissible expenses. 99.
Language:English
Score: 1196826.6 - www.un.org/en/internalj...dt/judgments/undt-2020-215.pdf
Data Source: oaj
\nReference software is useful in aiding users of a video coding standard to establish and test conformance and interoperability, and to educate users and demonstrate the capabilities of the standard. For these purposes, the accompanying software is provided as an aid for the study and implementation of Rec.  (...) For these purposes, the accompanying software is provided as an aid for the study and implementation of Rec. 
Language:English
Score: 1155909 - https://www.itu.int/t/aap/recdetails/10235
Data Source: un
It is important that the software can operate offline and store all data in a local database. (...) Sarvar Abdullaev: Most of the existing software is designed as web programmes for farmers. (...) Furthermore, our software is designed to keep records of several farms at the same time.
Language:English
Score: 1103957.6 - https://www.undp.org/uzbekista...ome-more-accessible-uzbekistan
Data Source: un
PowerPoint Presentation Report on the work of the task force on cyber security and over-the air updates 10 September 2021 Dr Darren Handley, UK Department for Transport ‹#› Content Overview of assignments for the task force Overview of Regulations R155 and R156 Overview of proposed guidance for Contracting Parties to the 1998 Agreement Conclusion ‹#› Background – task force formed December 2016 Cyber Security Regulatory proposal for CP’s to 1958 Agreement => R155 Interpretation document to aid harmonised uptake of R155 Technical requirements for CP’s to 1998 Agreement Software Update Processes Regulatory proposal for CP’s to 1958 Agreement => R156 Interpretation document to aid harmonised uptake of R156 Technical requirements for CP’s to 1998 Agreement Assignments for the tasks force ‹#› All tasks done, if the work on the technical requirements is accepted 3 The cyber security regulation Cyber Security Management System Requirements Vehicle Requirements Organizational structure & processes Design of the vehicle architecture, risk assessment and implementation of mitigations cyber security management system This requires vehicle manufacturers to have, at an organisational level, the following: Processes to identify and manage cyber security risks in the design of a vehicle Processes to verify that the risks are managed, including testing Processes to ensure that risk assessments are kept current Processes to monitor for cyber attacks Processes to assess if cyber security measures remain effective in light of new threats or vulnerabilities identified Processes to respond to attacks Processes to support analysis of successful or attempted attacks These processes must cover the period of a vehicle’s life from its conception to the last of its type Type Approval Requirements 6 For every vehicle type that is declared and approval sought, the following must be provided: Evidence that the CSMS applies to the vehicle type, particularly for vehicles in the field The risk assessment for the vehicle type, identifying what is critical and the risks posed to them Mitigations to reduce the risks identified to a justifiable level Evidence, through testing, that the mitigations work as intended Measures to detect and prevent cyber attacks Measures to support data forensics Monitoring activities specific for the vehicle type Reporting the outcome of monitoring activities for a vehicle type to the relevant type approval authority and confirmation the mitigations implemented remain effective The Software Update regulation Organizational structure & processes, incl. management of RxSWIN Implementation of RxSWIN in existing system regulations Software Update Management System Requirements Software Identification Requirements Vehicle Requirements Requirements for safe execution, protection of RxSWIN and user information Software update management system This requires vehicle manufacturers to have, at an organisational level, the following: Processes for configuration control for recording the hardware and software versions relevant to a vehicle type, including integrity validation data for the software Processes for identifying the software and hardware on a vehicle relevant to a specific UN regulation and tracking if that software changes (the RxSWIN concept) Processes for verifying the software on a vehicle component is what should be there Processes for identifying interdependencies of systems, particularly with respect to software updates Processes for identifying target vehicles and verifying their compatibility with an update Processes to assess if a software update will affect type approvals or other legally defined parameters for a given target vehicle (including adding or removing functionality) Processes to assess to assess if an update will affect the safety of safe driving of a vehicle Processes to inform vehicle owners of updates Processes to document all of the above and make it available for inspection at an audit Processes to ensure the cyber security of software updates before they are sent to a vehicle Software update management system This requires vehicle manufacturers to have, at an organisational level, the following: Processes for configuration control for recording the hardware and software versions relevant to a vehicle type, including integrity validation data for the software Processes for identifying the software and hardware on a vehicle relevant to a specific UN regulation and tracking if that software changes (the RxSWIN concept) Processes for verifying the software on a vehicle component is what should be there Processes for identifying interdependencies of systems, particularly with respect to software updates Processes for identifying target vehicles and verifying their compatibility with an update Processes to assess if a software update will affect type approvals or other legally defined parameters for a given target vehicle (including adding or removing functionality) Processes to assess to assess if an update will affect the safety or safe driving of a vehicle Processes to inform vehicle owners of updates Processes to document all of the above and make it available for inspection at an audit Processes to ensure the cyber security of software updates before they are sent to a vehicle Type Approval Requirements For every vehicle type that is declared and approval sought, the following must be provided: Evidence that the CSMS applies to the vehicle type, particularly for vehicles in the field The risk assessment for the vehicle type, identifying what is critical and the risks posed to them Mitigations to reduce the risks identified to a justifiable level Evidence, through testing, that the mitigations work as intended Measures to detect and prevent cyber attacks Measures to support data forensics Monitoring activities specific for the vehicle type Reporting the outcome of monitoring activities for a vehicle type to the relevant type approval authority and confirmation the mitigations implemented remain effective The Interpretation documentS - example Aim: help all stakeholder have a common understanding of how to evidence the regulation Approach Define technical requirements that CP’s can use when formulating national/regional regulation or legislation Use R155 and R156 as a basis and ensure there is alignment A GTR is not possible as it is difficult to define acceptance criteria and test criteria that would cover all possibilities Guidance document It covers both cyber security and software update processes It lists technical requirements for the vehicle and technical requirements for management systems It covers the whole life management of a vehicle It permits the RxSWIN concept to be used Overview of guidance for CP’s to the 1998 Agreement ‹#› 12 Recommended use of the guidance document As a minimum, CP’s should use the technical requirements relating to the vehicle en mass when formulating regulation or legislation on either cyber security or software update processes.
Language:English
Score: 1091284.9 - https://www.itu.int/en/ITU-T/e...E_TF_CS-OTA_status_report.pptx
Data Source: un
Douglas Semon Steven Saunders Project Director, Home Networking Software, CableLabs Steve Saunders is currently the Project Director of Home Networking Software at CableLabs®. (...) Upon joining Vexcel, Steve served as Senior Software Engineer. A year later, Steve assumed responsibility for the software department as Director of Software Development. (...) In his early career, Steve developed large-scale computer aided design and engineering software products for Auto-trol Inc., and later Structural Dynamics Research Corporation Inc.
Language:English
Score: 1090506.4 - https://www.itu.int/ITU-T/work...s/cvs/hnhs_0604_s3p1_ss_cv.doc
Data Source: un
Saunders Steven Saunders Project Director, Home Networking Software, CableLabs Steve Saunders is currently the Project Director of Home Networking Software at CableLabs®. (...) Upon joining Vexcel, Steve served as Senior Software Engineer. A year later, Steve assumed responsibility for the software department as Director of Software Development. (...) In his early career, Steve developed large-scale computer aided design and engineering software products for Auto-trol Inc., and later Structural Dynamics Research Corporation Inc.
Language:English
Score: 1090506.4 - https://www.itu.int/ITU-T/work...s/cvs/hnhs_0604_s6p0_ss_cv.doc
Data Source: un
As negative impacts of HIV / AIDS prevalence cover all population and development indicators, seeking effective strategies to prevent and control the spread of HIV / AIDS remains a priority on the international agenda. (...) We hope that development and utilization of this software will contribute positively to standardizing population forecasting methodologies, upgrading quality of popUlation data, and enhancing capacity building of developing countries in data collection. Availing myself of this opportunity, I would like to once again thank the Population Division for their great technical support to the software. Thank you, Mr. Chair.
Language:English
Score: 1081954 - https://www.un.org/en/developm.../country/agendaitem7/china.pdf
Data Source: un
He points to an Umoja Job Aid document which shows “library fees” as an admissible expense. (...) He says that the Educational and Accessory Services Contracts for the two school years in question were intended to cover “software, laptops, materials, maintenance, interactive whiteboards and multi-media”. (...) Such costs cover current and future use of these devices, their software programmes and other necessary support services, including potentially even after the children have left the school.
Language:English
Score: 1076293.5 - www.un.org/en/internalj...t/judgments/2022-UNAT-1221.pdf
Data Source: oaj
Steve has also managed the development of cable network support software. Prior to joining CableLabs, Steve worked in a number of capacities at Vexcel Imaging, a company that develops and manufactures aerial photography scanning hardware and image processing software. Upon joining Vexcel, Steve served as Senior Software Engineer. A year later, Steve assumed responsibility for the software department as Director of Software Development. (...) In his early career, Steve developed large-scale computer aided design and engineering software products for Auto-trol Inc., and later Structural Dynamics Research Corporation Inc.
Language:English
Score: 1072179.7 - https://www.itu.int/ITU-T/work...etworking/bios/s7-saunders.pdf
Data Source: un
Simply put, open source software is customer constructed software, which adheres to internationally accepted open source development standards. (...) Bob Young, president of RedHat software , has compared buying proprietary software to buying a car with the engine compartment welded shut. (...) We all know the alternative with “closed” software: re-install the software and tinker with the controls and see if the symptoms go away.
Language:English
Score: 1066480.1 - https://www.itu.int/itudoc/itu...health/addinfo/info003_ww9.doc
Data Source: un