Document Organization Sample Clauses

Document Organization. The remainder of this report is organized as follows:

Document Organization. This Component Specification documents the physical Polaris Architecture Components from the perspective of requirements and interfaces. The main body of this document is organized alphabetically by component or group name. For each component, a summary description including descriptions of the subfunctions that have been allocated to each component is provided. For each group, a corresponding list of components contained by the group is provided to point the reader to the correct sections. Appendix A describes the requirements that have been allocated to each component. Appendices B and C describe all the input and output data flows associated with each component.

Document Organization. This document is organized in a linear fashion corresponding with the timeline of the Design-Build procurement process. Appendix A – Projects of Division Interest (PoDI) Selection Process Appendix B – Design-Build Process Flow Chart Appendix C – AJR Guidance in Design-Build Projects Appendix D – FHWA and MoDOT Confidentiality Agreement Appendix E – FHWA Approval of Final Request for Proposal Letter Appendix F – MoDOT Request for Authorization Letter Appendix G - MoDOT Request for Concurrence in Award Letter Appendix H – FHWA Concur in Award Letter

Document Organization.  Section 1 provides an introduction to ASF and how to navigate this document.  Section 2 provides a high-level overview of the ASF file format organization.  Sections 3 and 4 define the various objects that comprise the ASF Header Object.  Section 5 describes the organization of the ASF Data Object.  Section 6 documents the internals of the ASF top-level index objects.  Section 7 documents various features of ASF and how to use them.  Section 8 details how to create content that is compatible with many existing ASF reading implementations; this concept is referred to as ―content reach.‖  Section 9 lists and describes standard ASF media types.  Section 10 contains a list of the ASF GUIDs used throughout this document.  Section 11 contains detailed information for specific codec data in ASF.

Document Organization. This document was written to provide a complete understanding of the adaptive management process as applied to the Restoration Project and to serve as a procedural and planning reference tool for Contemporary managers of the Restoration Project and Battle Creek fisheries. However, it was not written to be a “stand-alone” document in that it does not include all background and reference documentation; rather, it depends directly on key supporting documents including, primarily, the Battle Creek Salmon and Steelhead Restoration Plan (Restoration Plan), the CALFED Ecosystem Restoration Plan (CALFED 1999), and the Facility Monitoring Plan, which is currently being prepared per the MOU for matters of regulatory compliance. Users of this document who are 7 MOU 1.4.A 8 MOU 1.4.B 9 MOU 1.4.C 10 MOU 1.4.D 11 MOU 1.7 interested in learning more about the foundation of the Restoration Project and related actions, the initial steps in the adaptive management process used to develop this plan, or historical details of the restoration planning process are invited to read the Restoration Plan (Xxxx and Kier 1999a), MOU, and several other restoration plans that include Battle Creek (CALFED 1999; Xxxx and Kier 1999b; USFWS 1997; Xxxxxxx et al. 1996; CDFG 1996, 1993, 1990; USRFRHAC 1989; CACSST 1988; Xxxxxxx 1987). Users of this document who are interested in learning more about the current and proposed activities at Xxxxxxx National Fish Hatchery (CNFH) are encouraged to peruse the Biological Assessment (BA), which describes and assesses impacts of current or proposed operations of the CNFH and Xxxxxxxxxx Xxxxx National Fish Hatchery on listed populations of anadromous salmonids in the Central Valley under the Endangered Species Act (ESA) (USFWS 2001a). This AMP is divided into four major sections. The first section, Organization, describes the structure of the Adaptive Management technical and policy teams, the roles and responsibilities of the Parties to the MOU, Adaptive Management funding, and the term of the AMP. The following two technical chapters implicitly recognize the fact that many factors, including the Restoration Project and factors outside of the control of the Restoration Project, will affect the eventual restoration of salmon and steelhead in Battle Creek. Therefore, the section titled Adaptive Management Objectives describes specific Adaptive Management objectives pertaining to the future Adaptive Management of Restoration Project elements, and the scien...

Document Organization. ‌ The information in the sections below combine the content from the Alaska Health Information Technology (HIT) Strategic Plan (Master HIT Strategic Plan vNov2010.doc), the Alaska HIT Operations Plan (Master HIT Operations Plan vNov2010.doc) and the Alaska HIT Strategic Plan Addendum (HIE 2011 State Plan Addendum v 1.5) in the domain specific sections as well as the planning sections. The Landscape information from the strategic plan is not updated nor included in this document. The requirements outlined in the PIN to document changes in strategy are included in the narrative of each domain in a section labeled “2012 Update.” The requirements prescribed in the PIN to describe the current PIN Priority Strategies are included in Section 8. The PIN requirements to present the Sustainability Plan are addressed in Section 9. The table for tracking progress on key meaningful use HIE capabilities in their state and setting annual goals is included in Section 10. The description of the approach to assess the Privacy and Security Framework, identified Gaps and plans to address the gaps are included in Section 11. The description of the plans to evaluate the HIE Operations, the Lab Survey conducted in December 2011 and the Pharmacy Survey conducted in January 2011 are included in Section 13 and related appendices. 2 CHANGES TO HIE STRATEGY‌ This section includes both a table and narrative. The table contains only changes; the narrative contains a description of the previous and current strategies as well as the changes. This section combines the previous three documents into this one plan. Table 1: Changes to Alaska HIE Strategy Domain/Sections Short Description of Approved portion of SOP that Grantee is proposing to change (include page numbers) Proposed Changes Reason for the Proposed Changes Budget Implications of Proposed Changes 4.1 page 44 of the HIT Strategic Plan document submitted in November 2010 3.1 page 11 of the HIT Strategic Plan Addendum v1.5 submitted in March 2011 Included Alaska Pioneer Homes plans to participate in ePrescribing to support Medicare providers meeting Meaningful Use New initiative since previous submission of SOP None Strategies for Structured Lab Results Exchange 3.2 page 12 of the HIT Strategic Plan Addendum v1.5 submitted in March 2011 Pilot a point-to-point Lab Exchange solution that includes Direct as the data transport mechanism Participation in ONC sponsored Lab Summit (May 2012). Details to follow the completion of the Summit...

Document Organization. This document is organized into six major sections and one appendix. Section 1 is the Introduction: It defines the purpose and scope of this document, the organization of this document, and a list of applicable documents. Section 2 is the system overview for Pacor-A and OPUS and a listing of the responsible organizations. Section 3 provides a description of the products delivered to OPUS by Pacor-A. Section 4 provides a description of the data transmission between Pacor-A and OPUS. Section 5 provides a description of the data accountability function. Section 6 defines the points of contacts for Pacor-A and OPUS. Appendix A provides abbreviations and acronyms.

Document Organization. This document is organized in a linear fashion corresponding with the timeline of the Design Build procurement process.

Document Organization. This document is organized into seven sections, two appendices, and an acronym list. a. Section 1 introduces the document and defines its purpose, scope, and contents. Conventions used in preparing the document, as well as procedures for maintaining the document are provided. b. Section 2 contains a list of applicable documents. The list includes specifications, standards, and other applicable references. c. Section 3 provides an overview of EDOS and the ASTER GDS. d. Section 4 provides descriptions of EDOS data processing and construction of EDOS products delivered or provided to the ASTER GDS. e. Section 5 provides the delivery method for each of the EDOS products delivered to the ASTER GDS. f. Section 6 provides the methods and procedures for product anomaly resolution, contingency operations due to a disruption in delivery service, and failure recovery from system outages at either the ASTER GDS or at the EDOS Level Zero Processing Facility (LZPF). g. Section 7 provides methods of performing maintenance on either EDOS or the ASTER GDS system. h. Section 8 identifies the points-of-contact for EDOS and the ASTER GDS. i. Appendix A presents a list of EDOS-ASTER GDS product construction attributes. j. Appendix B provides details on the guidelines used by EDOS in order to delete raw data files. k. An Acronym List follows Appendix B.

Document Organization. A Product and Data Structure for each of documents handling shall be transferred. The T8x is structured into systems, subsystems and components. The coding of all documents, the file storage system as well as the part list follows a W2E/W2ET coding standard which are based on that T8x structure. The coding includes information about the project (T8x), component, variant, document character, subject area, author, sequential number, revision and language.