List of Operator’s Subprocessors [Box 26] [Box 27] [Box 28] [Box 29]
Federal Medicaid System Security Requirements Compliance Party shall provide a security plan, risk assessment, and security controls review document within three months of the start date of this Agreement (and update it annually thereafter) in order to support audit compliance with 45 CFR 95.621 subpart F, ADP System Security Requirements and Review Process.
Construction Document Phase 1.4.1 Based on the approved Design Development Documents, Guaranteed Maximum Price, coordinated models and any further adjustments in the scope or quality of the Project or in the Amount Available for the Construction Contract authorized by the Owner, the Architect/Engineer shall prepare, for approval by the Owner and review by the Construction Manager, Construction Documents consisting of Drawings, Schedules and Specifications derived from the model(s) in accordance with Owner’s written requirements setting forth in detail the requirements for construction of the Project, including, without limitation, the BIM Execution Plan and “Facility Design Guidelines”. The Plans, Drawings and Specifications for the entire Project shall be so prepared that same will call for the construction of the building and related facilities, together with its built-in permanent fixtures and equipment which will cost not more than the Guaranteed Maximum Price accepted by Owner, or the Amount Available for the Construction Contract established by Owner if no Guaranteed Maximum Price proposal has been accepted by Owner. The Architect/Engineer will be responsible for managing the design to stay within such Guaranteed Maximum Price proposal or Amount Available for the Construction Contract. The Architect/Engineer shall review the Construction Documents as they are being prepared at intervals appropriate to the progress of the Project with the Owner and Construction Manager at the Project site or other location specified by Owner in the State of Texas. The Architect/Engineer shall utilize the model(s) to support the review process during Construction Documents. The Architect/Engineer shall provide the Construction Manager with a compact disc containing documents and data files derived from the model to assist the Construction Manager in fulfilling its responsibilities to the Owner.
1.4.2 As a part of Construction Documents Phase, Architect/Engineer shall accomplish model coordination, aggregation and “clash detection” to remove conflicts in design between systems, structures and components. Architect/Engineer shall demonstrate and provide written assurance to Owner that all conflicts/collisions between models have been resolved.
1.4.3 The Architect/Engineer shall consult with the Owner and Construction Manager on matters such as construction phasing and scheduling, bid or proposal alternates, liquidated damages, the construction contract time period, and other construction issues appropriate for the Project. The Architect/Engineer shall assist the Owner and Construction Manager in the preparation of the necessary bidding information, bidding forms, RFP information, and RFP forms, and the Conditions of the Contract.
1.4.4 The Architect/Engineer shall assist the Owner in connection with the Owner’s responsibility and procedures for obtaining approval of all building and accessibility authorities having jurisdiction over the Project.
1.4.5 The Architect/Engineer shall provide coordination and inclusion of sequence of operations for all operable systems in the facility as defined by Owner during Design Development.
1.4.6 The Architect/Engineer shall review the Estimated Construction Cost prepared by the Construction Manager, and shall provide written comments.
1.4.7 The Architect/Engineer shall participate in a final review of the Construction Documents and model(s) with the Owner and Construction Manager at the Project location or other location specified by Owner in the State of Texas. Prior to the Owner’s approval of the Construction Documents, the Architect/Engineer shall incorporate such changes as are necessary to satisfy the Owner’s review comments.
1.4.8 Before proceeding into the Bidding and Proposal Phase, the Architect/Engineer shall obtain Owner’s written acceptance of the Construction Documents and approval of the Final Amount Available for the Construction Contract as approved by the Board of Regents.
Project Documentation All documentation provided to the City other than Project drawings shall be furnished on a Microsoft compatible compact disc.
Construction Documents Phase Bidding or Negotiation Phase:
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.
ENVIRONMENTAL DOCUMENTATION Each environmental service provided by the Engineer shall have a deliverable. Deliverables shall summarize the methods used for the environmental services, and shall summarize the results achieved. The summary of results shall be sufficiently detailed to provide satisfactory basis for thorough review by the State, The Federal Highway Administration (FHWA), and (where applicable) agencies with regulatory oversight. All deliverables shall meet regulatory requirements for legal sufficiency, and shall adhere to the requirements for reports enumerated in the State’s NEPA MOU.
a. Quality Assurance/Quality Control Review For each deliverable, the Engineer shall perform quality assurance quality control (QA/QC) reviews of environmental documents and on other supporting environmental documentation to determine whether documents conform with:
1) Current Environmental Compliance Toolkit guidance published by the State’s Environmental Affairs Division and in effect as of the date of receipt of the documents or documentation to be reviewed;
2) Current state and federal laws, regulations, policies, guidance, agreements, and memoranda of understanding between the State and other state or federal agencies; and
3) FHWA and American Association of State Highway and Transportation Officials (AASHTO) guidelines contained in “Improving the Quality of Environmental Documents, A Report of the Joint AASHTO and American Council of Engineering Companies (ACEC) Committee in Cooperation with the Federal Highway Administration” (May 2006) for: DocuSign Envelope ID: F9E4AA24-4672-4529-8EFA-00D1CA218520
a) Readability, and
b) Use of evidence and data in documents to support conclusions. Upon request by the State, the Engineer shall provide documentation that the QA/QC reviews were performed by qualified staff.
b. Deliverables shall contain all data acquired during the environmental service. All deliverables shall be written to be understood by the public and must be in accordance with the State’s Environmental Toolkit guidance, documentation standards, current guidelines, policies and procedures.
c. Electronic versions of each deliverable must be written in software which is compatible to the State and must be provided in a changeable format for future use by the State. The Engineer shall supplement all hard copy deliverables with electronic copies in searchable Adobe Acrobat™ (.pdf) format, unless another format is specified. Each deliverable shall be a single, searchable .pdf file that mirrors the layout and appearance of the physical deliverable. The Engineer shall deliver the electronic files on CD-R, CD-RW media in Microsoft Windows format, or through the ftp site.
d. When the environmental service is to apply for a permit (e.g., United States Coast Guard (USCG) or United States Army Corps of Engineers (USACE), the permit and all supporting documentation shall be the deliverable.
e. Submission of Deliverables
1) Deliverables shall consist of reports of environmental services performed in addition to a Categorical Exclusion (CE) determination form and supporting documentation including the required form or Environmental Assessment (EA) document, when applicable.
2) All deliverables must comply with all applicable state and federal environmental laws, regulations and procedures and include all items listed in the Environmental Document Review Checklist and the Administrative Completeness Review Checklist.
3) On the cover page of each environmental assessment (EA), finding of no significant impact (XXXXX), environmental impact statement (EIS), and record of decision (ROD) prepared under the authority granted by this MOU, and for any memorandum corresponding to any CE determination it makes, the Engineer shall insert the following language in a way that is conspicuous to the reader or include it in a CE project record: "The environmental review, consultation, and other actions required by applicable DocuSign Envelope ID: F9E4AA24-4672-4529-8EFA-00D1CA218520 Federal environmental laws for this project are being, or have been, carried-out by TxDOT pursuant to 23 U.S.C. 327 and a Memorandum of Understanding dated December 16, 2014, and executed by FHWA and TxDOT."
f. The State shall provide the State’s and other agency comments on draft deliverables to the Engineer. The Engineer shall revise the deliverable:
1) to include any State commitments, findings, agreements, or determinations (e.g., wetlands, endangered species consultation, Section 106, or Section 4(f)), required for the Transportation Activity as specified by the State;
2) to incorporate the results of public involvement and agency coordination;
3) to reflect mitigation measures resulting from comments received or changes in the Transportation Activity; and
4) include with the revised document a comment response form (matrix) in the format provided by the State.
g. All photographs shall be 3.5” x 5” color presentation printed on matte finish photographic paper or 3.5” x 5” color presentation printed on matte white, premium or photo quality laser or inkjet paper. All photographs shall be well focused and clearly depict details relevant to an evaluation of the project area. Provision of photographs shall be one original print of each image or electronic presentations of comparable quality. Comparable quality electronic photograph presentations shall be at least 1200 x 1600 pixel resolution. Photographs shall be attached to separately labeled pages that clearly identify project name, project identification (ID) number, address or Universal Transverse Mercator (UTM) of resource, description of the picture and direction of the photographic view. In addition to the hard-copy prints, an electronic version of each will be submitted with the same identification information as the hard-copy.
Design Development Documents See Section 2, Part 1, Article 2.1.5.
Technical Requirements 4.5.3.1 Tandem Switching shall have the same capabilities or equivalent capabilities as those described in Telcordia TR-TSY-000540 Issue 2R2, Tandem Supplement, June 1, 1990. The requirements for Tandem Switching include but are not limited to the following:
4.5.3.1.1 Tandem Switching shall provide signaling to establish a tandem connection;
4.5.3.1.2 Tandem Switching will provide screening as jointly agreed to by <<customer_short_name>> and BellSouth;
4.5.3.1.3 Where applicable, Tandem Switching shall provide AIN triggers supporting AIN features where such routing is not available from the originating end office switch, to the extent such Tandem switch has such capability;
4.5.3.1.4 Where applicable, Tandem Switching shall provide access to Toll Free number database;
4.5.3.1.5 Tandem Switching shall provide connectivity to Public Safety Answering Point (PSAP)s where 911 solutions are deployed and the tandem is used for 911; and
4.5.3.1.6 Where appropriate, Tandem Switching shall provide connectivity for the purpose of routing transit traffic to and from other carriers.
4.5.3.2 BellSouth may perform testing and fault isolation on the underlying switch that is providing Tandem Switching. Such testing shall be testing routinely performed by BellSouth. The results and reports of the testing shall be made available to <<customer_short_name>>.
4.5.3.3 BellSouth shall control congestion points and network abnormalities. All traffic will be restricted in a non-discriminatory manner.
4.5.3.4 Tandem Switching shall process originating toll free traffic received from <<customer_short_name>>’s local switch.
4.5.3.5 In support of AIN triggers and features, Tandem Switching shall provide SSP capabilities when these capabilities are not available from the Local Switching Network Element to the extent such Tandem Switch has such capability.
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.
