Enterprise Information Management Standards Grantee shall conform to HHS standards for data management as described by the policies of the HHS Office of Data, Analytics, and Performance. These include, but are not limited to, standards for documentation and communication of data models, metadata, and other data definition methods that are required by HHS for ongoing data governance, strategic portfolio analysis, interoperability planning, and valuation of HHS System data assets.
Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:
Meets Standard The school materially complies with applicable laws, rules, regulations and provisions of the charter contract relating to financial reporting requirements, including but not limited to: • Complete and on-time submission of financial reports, including annual budget, revised budgets (if applicable), periodic financial reports as required by the authorizer and any reporting requirements if the board contracts with an Education Service Provider (ESP) • On-time submission and completion of the annual independent audit and corrective action plans, if applicable • No charging of tuition • Adequate management and financial controls • All reporting requirements related to the use of public funds
Industry Troubleshooter Where a difference arises between the parties relating to the dismissal, discipline, or suspension of an employee, or to the interpretation, application, operation, or alleged violation of this Agreement, including any question as to whether a matter is arbitrable, during the term of the Collective Agreement, Xxxxx XxXxxxxxxx, Xxxx Xxxxxx, Xxxxx Xxxxxxxx, or a substitute agreed to by the parties, shall at the request of either party:
General Guidelines Conduct yourself in a responsible manner at all times in the laboratory.
Minimum Necessary Standard Business Associate shall apply the HIPAA Minimum Necessary standard to any Use or disclosure of PHI necessary to achieve the purposes of this Contract. See 45 CFR 164.514 (d)(2) through (d)(5).
File Format Standard Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in XXX 0000, Section 5, including all the records present in the actual zone used in the public DNS. Sub-format is as follows: Each record must include all fields in one line as: <domain-name> <TTL> <class> <type> <RDATA>. Class and Type must use the standard mnemonics and must be in lower case. TTL must be present as a decimal integer. Use of /X and /DDD inside domain names is allowed. All domain names must be in lower case. Must use exactly one tab as separator of fields inside a record. All domain names must be fully qualified. No $ORIGIN directives. No use of “@” to denote current origin. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. No $INCLUDE directives. No $TTL directives. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. No use of comments. No blank lines. The SOA record should be present at the top and (duplicated at) the end of the zone file. With the exception of the SOA record, all the records in a file must be in alphabetical order. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.
Policies, Guidelines, Directives and Standards Either the Funder or the Ministry will give the HSP Notice of any amendments to the manuals, guidelines or policies identified in Schedule C. An amendment will be effective in accordance with the terms of the amendment. By signing a copy of this Agreement the HSP acknowledges that it has a copy of the documents identified in Schedule C.
Design Criteria and Standards All Projects/Services shall be performed in accordance with instructions, criteria and standards set forth by the Director.
Change Management BellSouth provides a collaborative process for change management of the electronic interfaces through the Change Control Process (CCP). Guidelines for this process are set forth in the CCP document as amended from time to time during this Agreement. The CCP document may be accessed via the Internet at xxxx://xxx.xxxxxxxxxxxxxxx.xxxxxxxxx.xxx.
