Documentation Template Sample Clauses

Documentation Template doc Data Center ABS PROD - DAccount Policy & (User’s) Procedures Method and criteria for enable / disable of D Accounts Data Center DCS Policy and Procedure for Activating D Accounts.doc Data Center Access Administraation Policy and Procedures Policies and Procedures used by Access Administration staff to process requests for system accounts. Access Admin Access Admin Access_Administration_Policy.pdf B. Schedule M M - 17 Health Net / Cognizant Confidential Final Execution Version OTHER HEALTH NET POLICIES AND PROCEDURES OTHER HEALTH NET POLICIES Tower Policy Name Description Category Notes Help Desk Remedy Incident Priority Category Definitions Defines Incident Priority Incident and Problem Management Help Desk Remedy Problem Priority Category Definitions Defines Problem Priority Incident and Problem Management Help Desk Remedy Problem Management Policy and User Guide Remedy Problem Management Policy and User Guides. Problem Management Help Desk Point of Contact Guide Provides procedure for calls in to the Help Desk Help Desk Cross-Functional Change Management User Guide Remedy Change Management User Guide describes basic Change Management functions. Change and Release Management Cross-Functional Change Management Policy- Change and Release Management Help Desk Remedy User Guide Change and Release Management Cross-Functional Change Management Quick Reference Guide Change and Release Management Cross-Functional Oracle Naming Standards Cross-Functional Health Net Disaster Recovery Policies and Procedures Document ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇▇.▇▇▇/business_units/itg/ policies_and_procedures/Disaster_Recovery/ DR_Critical_Applications_Policies__Procedures_Revised_July_2.pdf IT Continuity & Disaster Recovery Services Cross-Functional Mission Critical Applications Policies and Procedures IT Continuity & Disaster Recovery Services Schedule M M - 18 Health Net / Cognizant Confidential Final Execution Version Cross-Functional DR Account Management Procedure IT Continuity & Disaster Recovery Services Cross-Functional 2007 ITG Disaster Recovery Program Overview IT Continuity & Disaster Recovery Services Cross-Functional Disaster Recovery Critical Path IT Continuity & Disaster Recovery Services Cross-Functional Disaster Recovery Process Lifecycle IT Continuity & Disaster Recovery Services Cross-Functional Plan to Ensure Continued Preservation of Electronically Stored Information (ESI) Storage Management, Data Retention Data Center Internal Policies for ISeries Describes...
View SourceView Similar (2)
Documentation Template doc Data Center ABS PROD - DAccount Policy & (User’s) Procedures Method and criteria for enable / disable of D Accounts Data Center DCS Policy and Procedure for Activating D Accounts.doc
View Source

Related to Documentation Template

  • TEMPLATE A software file containing all possible prize values for a Game Set to be created, indicating the number of prizes for each prize value that will appear in the Game Set.

  • Implementation Report Within 150 days after the Effective Date, Ensign Group shall submit a written report to OIG summarizing the status of its implementation of the requirements of this CIA (Implementation Report). The Implementation Report shall, at a minimum, include: 1. the name, address, phone number, and position description of the Compliance Officer required by Section III.A, and a summary of other noncompliance job responsibilities the Compliance Officer may have; 2. the names and positions of the members of the Compliance Committee required by Section III.A; 3. the names and positions of the members of the Board of Directors who are responsible for satisfying the Board of Directors compliance obligations described in Section III.A.3; 4. a copy of Ensign Group’s Code of Conduct required by Section III.B.1; 5. the number of individuals required to complete the Code of Conduct certification required by Section III.B.1, the percentage of individuals who have completed such certification, and an explanation of any exceptions (the documentation supporting this information shall be available to OIG upon request); 6. a summary of all Policies and Procedures required by Section III.B (copies of the Policies and Procedures shall be made available to OIG upon request); 7. the following information regarding each type of training required by Section III.C: a. a description of such training, including a summary of the topics covered, the length of sessions, and a schedule of training sessions; b. the number of individuals required to be trained, percentage of individuals actually trained, and an explanation of any exceptions. A copy of all training materials and the documentation supporting this information shall be made available to OIG upon request. 8. a description of the Disclosure Program required by Section III.E; 9. the following information regarding the IRO(s): (a) identity, address, and phone number; (b) a copy of the engagement letter; (c) information to demonstrate that the IRO has the qualifications outlined in Appendix A to this CIA; (d) a summary and description of any and all current and prior engagements and agreements between Ensign Group and the IRO; and (e) a certification from the IRO regarding its professional independence and objectivity with respect to Ensign Group; 10. a description of the process by which Ensign Group fulfills the requirements of Section III.F regarding Ineligible Persons; 11. a list of all of Ensign Group’s locations (including locations and mailing addresses); the corresponding name under which each location is doing business; the corresponding phone numbers and fax numbers; each location’s Medicare and state Medicaid program provider number and/or supplier number(s); and the name and address of each Medicare and state Medicaid program contractor to which Ensign Group currently submits claims; 12. a description of Ensign Group’s corporate structure, including identification of any parent and sister companies, subsidiaries, and their respective lines of business; and

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Documentation and compliance (a) The data importer shall promptly and adequately deal with enquiries from the data exporter that relate to the processing under these Clauses. (b) The Parties shall be able to demonstrate compliance with these Clauses. In particular, the data importer shall keep appropriate documentation on the processing activities carried out on behalf of the data exporter. (c) The data importer shall make available to the data exporter all information necessary to demonstrate compliance with the obligations set out in these Clauses and at the data exporter’s request, allow for and contribute to audits of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non-compliance. In deciding on a review or audit, the data exporter may take into account relevant certifications held by the data importer.

  • Licensed Documentation If commercially available, Licensee shall have the option to require the Contractor to deliver, at Contractor’s expense: (i) one (1) hard copy and one (1) master electronic copy of the Documentation in a mutually agreeable format; (ii) based on hard copy instructions for access by downloading from the Internet