We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.
For more information visit our privacy policy.Software Requirements 7 Developer shall prepare the Project Schedule using Oracle’s Primavera P6.
Maintenance Requirements The Contractor shall ensure and procure that at all times during the Maintenance Period, the Project Highway conforms to the maintenance requirements set forth in Schedule-E (the “Maintenance Requirements”).
Course Curriculum, Instruction, and Grading X. Xxxx College courses offered as dual credit, regardless of where they are taught, follow the same syllabus, course outline, textbook, grading method, and other academic policies as the courses outlined in the Hill College catalog. B. Approved courses being taught for dual credit must follow the approved master syllabus of the discipline and of Hill College. C. Textbooks should be identical to those approved for use by Hill College. Should an instructor propose an alternative textbook, the textbook must be approved in advance by the appropriate instructional department of Hill College and the Vice President of Instruction. Other instructional materials for dual credit/concurrent courses must be identical or at an equivalent level to materials used by Hill College. D. Courses which result in college‐level credit will follow the standard grading practices of Hill College, as identified by college policy and as identified in the appropriately approved course syllabus. The grades used in college records are A (excellent), B (above average), C (average), D (below average), F (failure), I (incomplete), W (withdrawn), WC (withdrawn COVID). The lowest passing grade is D. Grade point averages are computed by assigning values to each grade as follows: A = 4 points, B = 3 points, C = 2 points, D = 1 point, and F = 0 points. Grading criteria may be devised by Hill College and the ISD to allow faculty the opportunity to award high school credit only or high school and college credit depending upon student performance. E. Faculty, who are responsible for teaching dual credit/concurrent classes, are responsible for keeping appropriate records, certifying census date rosters, providing interim grade reports, certifying final grade reports at the end of the semester, certifying attendance, and providing other reports and information as may be required by Hill College and/or the School District.
Closet I Urinal Requirements Employees Closets Urinals
Monitoring Requirements This Schedule sets out the contract management requirements which are applicable to the delivery of the Services.
DATA ESCROW REQUIREMENTS Registry Operator will engage an independent entity to act as data escrow agent (“Escrow Agent”) for the provision of data escrow services related to the Registry Agreement. The following Technical Specifications set forth in Part A, and Legal Requirements set forth in Part B, will be included in any data escrow agreement between Registry Operator and the Escrow Agent, under which ICANN must be named a third-‐party beneficiary. In addition to the following requirements, the data escrow agreement may contain other provisions that are not contradictory or intended to subvert the required terms provided below.
DBE Requirements A. Notice is hereby given to the CONSULTANT and any SUB-CONSULTANT, and both agree, that failure to carry out the requirements set forth in 49 CFR Sec. 26.13(b) shall constitute a breach of this Contract and, after notification and failure to promptly cure such breach, may result in termination of this Contract or such remedy as INDOT deems appropriate. The referenced section requires the following assurance to be included in all subsequent contracts between the CONSULTANT and any SUB-CONSULTANT: The CONSULTANT, sub recipient or SUB-CONSULTANT shall not discriminate on the basis of race, color, national origin, or sex in the performance of this Contract. The CONSULTANT shall carry out applicable requirements of 49 CFR Part 26 in the award and administration of DOT-assisted contracts. Failure by the CONSULTANT to carry out these requirements is a material breach of this Contract, which may result in the termination of this Contract or such other remedy, as INDOT, as the recipient, deems appropriate. B. The CONSULTANT shall make good faith efforts to achieve the DBE percentage goal that may be included as part of this Contract with the approved DBE SUB-CONSULTANTS identified on its Affirmative Action Certification submitted with its Letter of Interest, or with approved amendments. Any changes to a DBE firm listed in the Affirmative Action Certification must be requested in writing and receive prior approval by the LPA and INDOT’s Economic Opportunity Division Director. After this Contract is completed and if a DBE SUB- CONSULTANT has performed services thereon, the CONSULTANT must complete, and return, a Disadvantaged Business Enterprise Utilization Affidavit (“DBE-3 Form”) to INDOT’s Economic Opportunity Division Director. The DBE-3 Form requires certification by the CONSULTANT AND DBE SUB-CONSULTANT that the committed contract amounts have been paid and received.
Quality Assurance Requirements There are no special Quality Assurance requirements under this Agreement.
Interface Requirements 2.4.5.1 The NID shall be equal to or better than all of the requirements for NIDs set forth in the applicable industry standard technical references.
New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to: (1) Limit system access to the types of transactions and functions that authorized users, such as students, parents, and LEA are permitted to execute; (2) Limit unsuccessful logon attempts; (3) Employ cryptographic mechanisms to protect the confidentiality of remote access sessions; (4) Authorize wireless access prior to allowing such connections; (5) Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity; (6) Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions; (7) Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles; (8) Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services; (9) Enforce a minimum password complexity and change of characters when new passwords are created; (10) Perform maintenance on organizational systems; (11) Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance; (12) Ensure equipment removed for off-site maintenance is sanitized of any Student Data in accordance with NIST SP 800-88 Revision 1; (13) Protect (i.e., physically control and securely store) system media containing Student Data, both paper and digital; (14) Sanitize or destroy system media containing Student Data in accordance with NIST SP 800-88 Revision 1 before disposal or release for reuse; (15) Control access to media containing Student Data and maintain accountability for media during transport outside of controlled areas; (16) Periodically assess the security controls in organizational systems to determine if the controls are effective in their application and develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems; (17) Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems; (18) Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception); (19) Protect the confidentiality of Student Data at rest; (20) Identify, report, and correct system flaws in a timely manner; (21) Provide protection from malicious code (i.e. Antivirus and Antimalware) at designated locations within organizational systems; (22) Monitor system security alerts and advisories and take action in response; and (23) Update malicious code protection mechanisms when new releases are available.