GENERAL RECORDS SCHEDULE 3.1: General Technology Management Records
|
|
|
- Shon Walker
- 10 years ago
- Views:
Transcription
1 GENERAL RECORDS SCHEDULE 3.1: General Technology Management Records This schedule covers records created and maintained by Federal agencies related to the general management of technology. It includes records related to developing, operating, and maintaining computer software, systems, and infrastructure improvements; complying with information technology policies and plans; and maintaining data standards. This schedule does not apply to system data or content. This schedule does not apply to records documenting the Office of Management and Budget and the US Federal Chief Information Officers Council government-wide information management planning and programming. There may be copies of the Exhibit 300 records within these case files. However, agencies should continue to file the recordkeeping copy as part of IT Capital Investment Records. Records needed to support contracts should be in procurement files, which are scheduled under the GRS for General Financial Management Records. Item Records Title/Description 010 Information technology development project records. Infrastructure project records. Information Technology (IT) infrastructure, systems, and services project records document the basic systems and services used to supply the agency and its staff with access to computers and data telecommunications. Includes requirements for and implementation of functions such as: maintaining network servers, desktop computers, and other hardware, installing and upgrading network operating systems and shared applications, and providing data telecommunications; and infrastructure development and maintenance such as acceptance/authorization of infrastructure components, analysis of component options, feasibility, costs and benefits, and work associated with implementation, modification, and troubleshooting. after project is terminated, but 0006 Includes records such as: installation and testing records installation reviews and briefings quality assurance and security review requirements specifications technology refresh plans operational support plans test plans models, diagrams, schematics, and technical documentation 42
2 Item Records Title/Description Exclusion: Records relating to specific systems that support or document mission goals are not covered by this item and must be scheduled individually by the agency by submission of a records schedule to NARA. Note: Records concerning the development of each information technology (IT) system and software application are covered under the item for System Development Records. 011 System development records. These records relate to the development of information technology (IT) systems and software applications through their initial stages up until hand-off to production which includes planning, requirements analysis, design, verification and testing, procurement, and installation. Records include case files containing documentation of planning, decision making, designing, programming, testing, evaluation, and problem solving. Includes records such as: project plans Plan of Action and Milestones (POA&M) feasibility studies Configuration Management Plan cost analyses Resource Management Plan requirements documents Risk Assessment/Mitigation Plan compliance documents including: Security Plan o Privacy Threshold Analyses (PTAs) Disaster Recovery Plan o Privacy Impact Assessments (PIAs) Test /Acceptance Plan o Security Plan Quality Control Plan o Information Protection Plan Deployment Guide change control records User Guide Project Schedule Training Guide Exclusion: This item does not apply to system data or content. Note 1: For certain technical documentation (e.g., data dictionaries, file specifications, code books, record layouts, etc.) related to the detailed, as-built design or maintenance of an electronic system containing permanent records, use the GRS item Documentation Necessary for Preservation of Permanent Electronic Records. after system is superseded by a new iteration, or is terminated, defunded, or no longer needed for agency/it administrative purposes, but
3 Item Records Title/Description Note 2: This is consistent with the fact that the most complete version of system documentation is retained within the maintenance phase. 012 Special purpose computer programs and applications. Computer software programs or applications that are developed by the agency or under its direction solely to use or maintain a master file or database authorized for disposal in a GRS item or a NARA-approved records schedule. Exclusion 1: This item does not include software or applications necessary to use or maintain any unscheduled master file or database or any master file or database scheduled for transfer to the National Archives. Exclusion 2: This item does not cover commercial, off-the-shelf (COTS) programs or applications, unless the agency has modified such programs or applications considerably to perform a missionrelated function. Note: Computer software needs to be kept as long as needed to ensure access to, and use of, the electronic records in the system throughout the authorized retention period to comply with 36 CFR Sections , , , and Information technology operations and maintenance records. Information Technology Operations and Maintenance records relate to the activities associated with the operations and maintenance of the basic systems and services used to supply the agency and its staff with access to computers and data telecommunications. Includes the activities associated with IT equipment, IT systems, and storage media, IT system performance testing, asset and configuration management, change management, and maintenance on network infrastructure. Includes records such as: files identifying IT facilities and sites files concerning implementation of IT facility and site management equipment support services provided to specific sites: 44 Delete when related master file or database has been deleted, but Destroy 3 years after agreement, control measures, procedures, project, activity, or transaction is obsolete, completed, terminated or
4 Item Records Title/Description o reviews o site visit reports o trouble reports o equipment service histories o reports of follow-up actions o related correspondence inventories of IT assets, network circuits, and building or circuitry diagrams equipment control systems such as databases of barcodes affixed to IT physical assets, and tracking of [approved] personally-owned devices requests for service work orders service histories workload schedules run reports schedules of maintenance and support activities problem reports and related decision documents relating to the software infrastructure of the network or system reports on operations o measures of benchmarks o performance indicators o critical success factors o error and exception reporting o self-assessments o performance monitoring o management reports website administration o frames o templates o style sheets o site maps o codes that determine site architecture o change requests 45 superseded, but
5 Item Records Title/Description o site posting logs o clearance records o requests for correction of incorrect links or content posted o requests for removal of duplicate information o user logs o search engine logs o audit logs records to allocate charges and track payment for software and services Note 1: If any maintenance activities have a major impact on a system or lead to a significant change, those records should be maintained as part of the Configuration and Change Management Records. Note 2: Records needed to support contracts should be in procurement files, which are scheduled under the GRS for General Financial Management Records. 030 Configuration and Change Management Records. Records created and retained for asset management, performance and capacity management, system management, configuration and change management, and planning, follow-up, and impact assessment of operational networks and systems. Includes records such as: data and detailed reports on implementation of systems, applications and modifications application sizing, resource and demand management records documents identifying, requesting, and analyzing possible changes, authorizing changes, and documenting implementation of changes documentation of software distribution (including COTS software license management files) and release or version management Note 1: If any maintenance activities have a major impact on a system or lead to a significant change, those records should be maintained as part of the Configuration and Change Management Records. Note 2: Per NARA practice, documentation for permanent electronic records should be transferred with the related records using the disposition authority for the related electronic records rather than the GRS disposition authority. after system is superseded by a new iteration, or is terminated, defunded, or no longer needed for agency/it administrative purposes, but
6 Item Records Title/Description Note 3: Agencies may retain a copy of documentation related to permanent electronic records. This copy may be destroyed at any time after the transfer request has been signed by the National Archives. 040 Information technology oversight and compliance records. Information Technology (IT) Oversight and Compliance records relate to compliance with IT policies, directives, and plans. Records are typically found in offices with agency-wide or bureau-wide responsibility for managing IT operations. Includes records such as: recurring and special reports responses to findings and recommendations reports of follow-up activities statistical performance data metrics inventory of web activity web use statistics comments/feedback from web site or application users internal and external reporting for compliance requirements relating to the Privacy Act, and electronic and Information technology accessibility under Section 508 of the Rehabilitation Act system availability reports target IT architecture reports systems development lifecycle handbooks computer network assessments and follow-up documentation vulnerability assessment reports assessment and authorization of equipment Independent Verification and Validation (IV&V) reports contractor evaluation reports quality assurance reviews and reports market analyses and performance surveys benefit-cost analyses make vs. buy analysis reports on implementation of plans compliance reviews after the project/activity/ transaction is completed or superseded, but
7 Item Records Title/Description data measuring or estimating impact and compliance Note: Copies of security plans are scheduled under the GRS for Information Security Records. There may be copies interfiled within this series. 050 Data administration records. Data Administration includes maintenance of data standards, corporate data models, registries, and data definitions and dictionaries. Records relate to administrative support for the maintenance of data standards, data definitions and data dictionaries. This schedule includes records that explain the meaning, purpose, logical relationships, and use and origin of data. It also Documentation necessary for preservation of permanent electronic records. Data administration records and documentation relating to electronic records scheduled as permanent in the GRS or in a NARA-approved agency schedule must be transferred to the National Archives to allow for continued access to the records, including: data/database dictionary records data systems specifications file specifications code books Note 1: Per NARA practice, documentation for permanent electronic records must be transferred with the related records using the disposition authority for the related electronic records rather than the GRS disposition authority. Note 2: Agencies may retain a copy of documentation related to permanent electronic records. This copy may be destroyed at any time after the transfer request has been signed by the National Archives. 051 All documentation for temporary electronic records and documentation not necessary for preservation of permanent records. Data administration records and documentation relating to electronic records that are scheduled as temporary in the GRS or in a NARA-approved agency schedule or any types of data administration records not listed as permanent in item 0002, including data/database dictionary records data systems specifications file specifications code books record layouts metadata user guides output specifications record layouts metadata user guides output specifications 48 Permanent. Transfer to the National Archives with the permanent electronic records to which the documenttation relates. after the project/activity/ transaction is completed or superseded, or the associated system is terminated, or
8 Item Records Title/Description includes any documentation related to electronic records, whether the records are part of an electronic system or stand-alone, that allows a user to understand or access the information. and also the following records for all electronic records whether scheduled as temporary or permanent software operating manuals data standards table and dependency descriptions taxonomies schemas registries source code physical data model logical data model the associated data is migrated to a successor system, but business use 49
Frequently Asked Questions (FAQs) about GRS 3.1, General Technology Management Records
Frequently Asked Questions (FAQs) about GRS 3.1, General Technology Management Records INTRODUCTION 1. What is the purpose of GRS 3.1? This schedule provides disposition authority for records related to
NIH Records Management Program
Background: The (GRS) are issued by the Archivist of the United States to provide disposition authorization for records common to several or all agencies of the Federal government. These schedules provide
2.2 INFORMATION SERVICES Documentation of computer services, computer system management, and computer network management.
3 Audit Trail Files Data generated during the creation of a master file or database, used to validate a master file or database during a processing cycle. GS 14020 Retain for 3 backup cycles Computer Run
3. Ensure the management of information is compliant with legislative requirements to maximise the benefits and minimise risks;
Enterprise Content Management (ECM) Policy Version Information A. Introduction Purpose 1. Outline and articulate the strategy for enterprise content management across Redland City Council (RCC). This document
Interagency Science Working Group. National Archives and Records Administration
Interagency Science Working Group 1 National Archives and Records Administration Establishing Trustworthy Digital Repositories: A Discussion Guide Based on the ISO Open Archival Information System (OAIS)
DELAWARE PUBLIC ARCHIVES POLICY STATEMENT AND GUIDELINES MODEL GUIDELINES FOR ELECTRONIC RECORDS
DELAWARE PUBLIC ARCHIVES POLICY STATEMENT AND GUIDELINES MODEL GUIDELINES FOR ELECTRONIC RECORDS STATEMENT OF PURPOSE The Delaware Public Archives (DPA) has issued "Model Guidelines for Electronic Records"
Validating Enterprise Systems: A Practical Guide
Table of Contents Validating Enterprise Systems: A Practical Guide Foreword 1 Introduction The Need for Guidance on Compliant Enterprise Systems What is an Enterprise System The Need to Validate Enterprise
Office of IT Planning, Architecture, and E-Government Office of the Chief Information Officer
Your Records Management Responsibilities Office of IT Planning, Architecture, and E-Government Office of the Chief Information Officer July 2010 Table of Contents INTRODUCTION RECORDS MANAGEMENT IN THE
University of Wisconsin System Information Technology Records
University of Wisconsin System Information Technology Records General Records Schedule AUGUST2012 APPROVAL SUBJECT TO 10-YEAR SUNSET. RESUBMITTAL REQUIRED PRIOR TO GLuQWt? 3Q^k AUG II 2012 UNIVERSITY OF
Business Process Design As-Is and To-Be Checklists Introduction
Business Process Design As-Is and To-Be Checklists Introduction These business process design checklists were developed to help Federal IT staff, Records Managers, and Program Managers identify records
U.S. Nuclear Regulatory Commission Privacy Impact Assessment
ADAMS ML052920123 Yes No Make Public After President Submits Budget (For OIS Use Only) U.S. Nuclear Regulatory Commission Privacy Impact Assessment Instructions: Section A, B, C, and D must be completed
RECORDS AND INFORMATION MANAGEMENT AND RETENTION
RECORDS AND INFORMATION MANAGEMENT AND RETENTION Policy The Health Science Center recognizes the need for orderly management and retrieval of all official records and a documented records retention and
TERRITORY RECORDS OFFICE BUSINESS SYSTEMS AND DIGITAL RECORDKEEPING FUNCTIONALITY ASSESSMENT TOOL
TERRITORY RECORDS OFFICE BUSINESS SYSTEMS AND DIGITAL RECORDKEEPING FUNCTIONALITY ASSESSMENT TOOL INTRODUCTION WHAT IS A RECORD? AS ISO 15489-2002 Records Management defines a record as information created,
5 FAM 440 ELECTRONIC RECORDS, FACSIMILE RECORDS, AND ELECTRONIC MAIL RECORDS
5 FAM 440 ELECTRONIC RECORDS, FACSIMILE RECORDS, AND ELECTRONIC MAIL RECORDS (CT:IM-158; 12-29-2014) (Office of Origin: A/GIS/IPS) NOTE: In October, 2014, the Department issued an interim directive superseding
Information Management Advice 18 - Managing records in business systems: Overview
Information Management Advice 18 - Managing records in business systems: Overview Introduction The purpose of this Advice is to assist agencies to identify and manage State records in business systems,
From Chaos to Clarity: Embedding Security into the SDLC
From Chaos to Clarity: Embedding Security into the SDLC Felicia Nicastro Security Testing Services Practice SQS USA Session Description This session will focus on the security testing requirements which
PHASE 9: OPERATIONS AND MAINTENANCE PHASE
PHASE 9: OPERATIONS AND MAINTENANCE PHASE During the Operations and Maintenance Phase, the information system s availability and performance in executing the work for which it was designed is maintained.
UNITED STATES DEPARTMENT OF THE INTERIOR BUREAU OF LAND MANAGEMENT MANUAL TRANSMITTAL SHEET. 1283 Data Administration and Management (Public)
Form 1221-2 (June 1969) Subject UNITED STATES DEPARTMENT OF THE INTERIOR BUREAU OF LAND MANAGEMENT MANUAL TRANSMITTAL SHEET 1283 Data Administration and Management (Public) Release 1-1742 Date 7/10/2012
Section 28.1 Purpose. Section 28.2 Background. DOT Order 1351.28 Records Management. CIOP Chapter 1351.28 RECORDS MANAGEMENT
CIOP Chapter 1351.28 RECORDS MANAGEMENT TABLE OF CONTENTS Section 28.1 Purpose... 1 Section 28.2 Background... 1 Section 28.3 Scope and Applicability... 2 Section 28.4 Definitions... 4 Section 28.5 Policy...
State of Michigan Records Management Services. Frequently Asked Questions About E mail Retention
State of Michigan Records Management Services Frequently Asked Questions About E mail Retention It is essential that government agencies manage their electronic mail (e mail) appropriately. Like all other
Request for Proposal for Application Development and Maintenance Services for XML Store platforms
Request for Proposal for Application Development and Maintenance s for ML Store platforms Annex 4: Application Development & Maintenance Requirements Description TABLE OF CONTENTS Page 1 1.0 s Overview...
Information Security Policy September 2009 Newman University IT Services. Information Security Policy
Contents 1. Statement 1.1 Introduction 1.2 Objectives 1.3 Scope and Policy Structure 1.4 Risk Assessment and Management 1.5 Responsibilities for Information Security 2. Compliance 3. HR Security 3.1 Terms
REMEDY Enterprise Services Management System
for the Enterprise Services Management System April 28, 2016 Contact Point Marshall Nolan Border Enforcement and Management Systems Division Office of Information Technology U.S. Customs & Border Protection
GRS 6.1 Email Managed Under a Capstone Approach
GRS 6.1 Email Managed Under a Capstone Approach This file contains three documents. The Draft Schedule is the proposed text of the new GRS in publication format. The FAQ supplements the new GRS, and will
Subject: 1268-1 Information Technology Configuration Management Manual
Form 1221-2 (June 1969) UNITED STATES DEPARTMENT OF THE INTERIOR BUREAU OF LAND MANAGEMENT Release 1-1741 Date MANUAL TRANSMITTAL SHEET 06/19/2012 Subject: 1268-1 Information Technology Configuration Management
INFORMATION MANAGEMENT
United States Government Accountability Office Report to the Committee on Homeland Security and Governmental Affairs, U.S. Senate May 2015 INFORMATION MANAGEMENT Additional Actions Are Needed to Meet Requirements
--j except for Items that may be marked "disposition not 3 MINOR SUBDIVISION approved" or "withdrawn" In column 10
' REQUEST FOR RECORDS DISPOSITION AUTHORITY JOB NUMBER 1\)1-237- 09 -I :>. To: NATIONAL ARCHIVES & RECORDS ADMINISTRATION Date received 8601 ADELPHI ROAD COLLEGE PARK, MD 20740-6001 q - 2/- '2.00 't FROM
GLOSSARY: A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, W, X, Y, Z
A Accession. A group of records that have been transferred to a Federal Records Center (FRC) for storage, or into the National Archives and Records Administration s (NARA) Electronic Records Archives (ERA).
PROCEDURES FOR ELECTRONIC MANAGEMENT OF RULEMAKING AND OTHER DOCKETED RECORDS IN THE FEDERAL DOCKET MANAGEMENT SYSTEM
Issued by the EPA Chief Information Officer, Pursuant to Delegation 1-19, dated 07/07/2005 PROCEDURES FOR ELECTRONIC MANAGEMENT OF RULEMAKING AND OTHER DOCKETED RECORDS IN THE FEDERAL DOCKET MANAGEMENT
CONTENTS. List of Tables List of Figures
Prelims 13/3/06 9:11 pm Page iii CONTENTS List of Tables List of Figures ix xi 1 Introduction 1 1.1 The Need for Guidance on ERP System Validation 1 1.2 The Need to Validate ERP Systems 3 1.3 The ERP Implementation
Publication 805-A Revision: Certification and Accreditation
Postal Bulletin 22358 (3-7-13) Policies, Procedures, and Forms Updates Publication 805-A Revision: Certification and Accreditation Effective immediately, the January 2013 edition of Publication 805-A,
Technical Competency Framework for Information Management (IM)
Technical Competency Framework for Information Management (IM) Office of the Chief Information Officer (OCIO) June 15, 2009 Table of contents IM Competency Framework...1 Competency 1: Information Management
Department of the Interior Privacy Impact Assessment Template
Department of the Interior Template May 28, 2014 Name of Project: Consolidated Financial System (CFS) Bureau: Office of the Secretary Project s Unique ID: 010-000000308 A. CONTACT INFORMATION: Teri Barnett
RECORDS MANAGEMENT VITAL RECORDS MANAGEMENT
RECORDS MANAGEMENT AND VITAL RECORDS MANAGEMENT OBJECTIVES Explain the purpose of Records Management (RM). Teach you how to properly create, maintain, and preserve all Marine Corps records. Help you understand
Union County. Electronic Records and Document Imaging Policy
Union County Electronic Records and Document Imaging Policy Adopted by the Union County Board of Commissioners December 2, 2013 1 Table of Contents 1. Purpose... 3 2. Responsible Parties... 3 3. Availability
Systems Development Life Cycle (SDLC)
DEPARTMENT OF BUDGET & MANAGEMENT (SDLC) Volume 1 Introduction to the SDLC August 2006 Table of Contents Introduction... 3 Overview... 4 Page 2 of 17 INTRODUCTION 1.0 STRUCTURE The SDLC Manual consists
Significant Revisions to OMB Circular A-127. Section Revision to A-127 Purpose of Revision Section 1. Purpose
Significant Revisions to OMB Circular A-127 Section Revision to A-127 Purpose of Revision Section 1. Purpose Section 5. Definitions Section 6. Policy Section 7. Service Provider Requirements Section 8.
FHFA. Privacy Impact Assessment Template FM: SYSTEMS (SYSTEM NAME)
FHFA Privacy Impact Assessment Template FM: SYSTEMS (SYSTEM NAME) This template is used when the Chief Privacy Officer determines that the system contains Personally Identifiable Information and a more
Information Technology Policy
Information Technology Policy Systems Development Life Cycle Policy ITP Number ITP-APP012 Category Recommended Policy Contact [email protected] Effective Date May 1, 2013 Supersedes Scheduled Review
United States Department of State Global Financial Management System (GFMS) Privacy Impact Assessment
United States Department of State Global Financial Management System (GFMS) Privacy Impact Assessment CGFS/DCFO/GFMS 1. Contact Information Privacy Impact Assessment (PIA) Department of State Privacy Coordinator
4.01. Archives of Ontario and Information Storage and Retrieval Services. Chapter 4 Section. Background
Chapter 4 Section 4.01 Ministry of Government Services Archives of Ontario and Information Storage and Retrieval Services Follow-up on VFM Section 3.01, 2007 Annual Report Background The Archives of Ontario
CHAPTER 9 RECORDS MANAGEMENT (Revised April 18, 2006)
CHAPTER 9 RECORDS MANAGEMENT (Revised April 18, 2006) WHAT IS THE PURPOSE OF RECORDS MANAGEMENT? 1. To implement a cost-effective Department-wide program that provides for adequate and proper documentation
Records Management Policy. EPA Classification No.: CIO 2155.3 CIO Approval Date: 02/10/2015. CIO Transmittal No.: 15-005 Review Date: 02/10/2018
INFORMATION POLICY Records Management Policy Issued by the EPA Chief Information Officer, Pursuant to Delegation 1-19, dated 07/07/2005 Records Management Policy 1. PURPOSE To advance a focus on overall
AUDIT REPORT. The Energy Information Administration s Information Technology Program
U.S. Department of Energy Office of Inspector General Office of Audits and Inspections AUDIT REPORT The Energy Information Administration s Information Technology Program DOE-OIG-16-04 November 2015 Department
Implementing an Electronic Document and Records Management System. Key Considerations
Implementing an Electronic Document and Records Management System Key Considerations Commonwealth of Australia 2011 This work is copyright. Apart from any use as permitted under the Copyright Act 1968,
APPENDIX 8 TO SCHEDULE 3.3
EHIBIT Q to Amendment No. 60 - APPENDI 8 TO SCHEDULE 3.3 TO THE COMPREHENSIVE INFRASTRUCTURE AGREEMENT APPENDI 8 TO SCHEDULE 3.3 TO THE COMPREHENSIVE INFRASTRUCTURE AGREEMENT EHIBIT Q to Amendment No.
Records Management and SharePoint 2013
Records Management and SharePoint 2013 SHAREPOINT MANAGEMENT, ARCHITECTURE AND DESIGN Bob Mixon Senior SharePoint Architect, Information Architect, Project Manager Copyright Protected by 2013, 2014. Bob
Best Practices for Long-Term Retention & Preservation. Michael Peterson, Strategic Research Corp. Gary Zasman, Network Appliance
Best Practices for Long-Term Retention & Preservation Michael Peterson, Strategic Research Corp. Gary Zasman, Network Appliance SNIA Legal Notice The material contained in this tutorial is copyrighted
BPA Policy 236-1 Information Governance & Lifecycle Management
B O N N E V I L L E P O W E R A D M I N I S T R A T I O N BPA Policy 236-1 Table of Contents 236-1.1 Purpose & Background... 2 236-1.2 Policy Owner... 2 236-1.3 Applicability... 2 236-1.4 Terms & Definitions...
Draft Information Technology Policy
Draft Information Technology Policy Version 3.0 Draft Date June 2014 Status Draft Approved By: Table of Contents 1.0 Introduction... 6 Background... 6 Purpose... 6 Scope... 6 Legal Framework... 6 2.0 Software
Records Management. Training 101
Records Management Training 101 Learning Objectives This training is designed to help you: Understand the importance of Records Management and why records are maintained Understand your RM responsibilities
Information Management Advice 61 How to review your records holdings
Information Management Advice 61 How to review your records holdings There are many reasons why agencies may decide to survey records holdings. Agencies may be implementing information security classification,
IT General Controls Domain COBIT Domain Control Objective Control Activity Test Plan Test of Controls Results
Acquire or develop application systems software Controls provide reasonable assurance that application and system software is acquired or developed that effectively supports financial reporting requirements.
Office of Financial Research Constituent Relationship Management Tool Privacy Impact Assessment ( PIA ) April, 2015
Office of Financial Research Constituent Relationship Management Tool Privacy Impact Assessment ( PIA ) April, 2015 A. Identification System Name: OMB Unique Identifier: System Owner: Constituent Relationship
PHASE 5: DESIGN PHASE
PHASE 5: DESIGN PHASE During the Design Phase, the system is designed to satisfy the requirements identified in the previous phases. The requirements identified in the Requirements Analysis Phase are transformed
Report of Audit OFFICE OF INSPECTOR GENERAL. Information Technology Infrastructure Project Management A-07-02. Tammy Rapp Auditor-in-Charge
OFFICE OF INSPECTOR GENERAL Report of Audit Information Technology Infrastructure Project Management A-07-02 Tammy Rapp Auditor-in-Charge FARM CREDIT ADMINISTRATION Memorandum Office of Inspector General
Scotland s Commissioner for Children and Young People Records Management Policy
Scotland s Commissioner for Children and Young People Records Management Policy 1 RECORDS MANAGEMENT POLICY OVERVIEW 2 Policy Statement 2 Scope 2 Relevant Legislation and Regulations 2 Policy Objectives
Public Records (Scotland) Act 2011. Healthcare Improvement Scotland and Scottish Health Council Assessment Report
Public Records (Scotland) Act 2011 Healthcare Improvement Scotland and Scottish Health Council Assessment Report The Keeper of the Records of Scotland 30 October 2015 Contents 1. Public Records (Scotland)
Services Providers. Ivan Soto
SOP s for Managing Application Services Providers Ivan Soto Learning Objectives At the end of this session we will have covered: Types of Managed Services Outsourcing process Quality expectations for Managed
Queensland recordkeeping metadata standard and guideline
Queensland recordkeeping metadata standard and guideline June 2012 Version 1.1 Queensland State Archives Department of Science, Information Technology, Innovation and the Arts Document details Security
Audit Report. The Social Security Administration s Management of Electronic Message Records
Audit Report The Social Security Administration s Management of Electronic Message Records A-14-15-25025 February 2016 MEMORANDUM Date: February 19, 2016 Refer To: To: From: The Commissioner Inspector
United States Secret Service Enterprise Architecture Review Board (EARB) Project Briefing for NAME OF PROJECT
United States Secret Service Enterprise Architecture Review Board (EARB) Project Briefing for NAME OF PROJECT Presenter Name(s) Date 1 Introduction: An Enterprise Architecture Review Board (EARB) review
39C-1 Records Management Program 39C-3
39C-1 Records Management Program 39C-3 Sec. 39C-1. Sec. 39C-2. Sec. 39C-3. Sec. 39C-4. Sec. 39C-5. Sec. 39C-6. Sec. 39C-7. Sec. 39C-8. Sec. 39C-9. Sec. 39C-10. Sec. 39C-11. Sec. 39C-12. Sec. 39C-13. Sec.
August 24, 2012 MEMORANDUM FOR THE HEADS OF EXECUTIVE DEPARTMENTS AND AGENCIES AND INDEPENDENT AGENCIES
EXECUTIVE OFFICE OF THE PRESIDENT OFFICE OF MANAGEMENT AND BUDGET WASHINGTON, D.C. 20503 NATIONAL ARCHIVES AND RECORDS ADMINISTRATION WASHINGTON, D.C. 20408 August 24, 2012 M-12-18 MEMORANDUM FOR THE HEADS
Texas State Library and Archives Commission. Information Technology Detail. August 26, 2010
Texas State Library and Archives Commission Information Technology Detail 82 th Regular Session, Agency Submission, Version 1 August 26, 2010 PAGE: 1 of 6 5005 ACQUISITN INFO RES TECH 4 Computer Resources/Network
Exhibit to Data Center Services Service Component Provider Master Services Agreement
Exhibit to Data Center Services Service Component Provider Master Services Agreement DIR Contract No. DIR-DCS-SCP-MSA-002 Between The State of Texas, acting by and through the Texas Department of Information
Module: Sharepoint Administrator
Module: Sharepoint Administrator Mode: Classroom Duration: 40 hours This course teaches IT Professionals to design and deploy Microsoft SharePoint 2010. Course Outline: Module 1: Designing a Logical Architecture
OCCUPATIONAL GROUP: Information Technology. CLASS FAMILY: Security CLASS FAMILY DESCRIPTION:
OCCUPATIONAL GROUP: Information Technology CLASS FAMILY: Security CLASS FAMILY DESCRIPTION: This family of positions provides security and monitoring for the transmission of information in voice, data,
9. GOVERNANCE. Policy 9.8 RECORDS MANAGEMENT POLICY. Version 4
9. GOVERNANCE Policy 9.8 RECORDS MANAGEMENT POLICY Version 4 9. GOVERNANCE 9.8 RECORDS MANAGEMENT POLICY OBJECTIVES: To establish the framework for, and accountabilities of, Lithgow City Council s Records
Department of Defense INSTRUCTION
Department of Defense INSTRUCTION NUMBER 5015.02 February 24, 2015 DoD CIO SUBJECT: DoD Records Management Program References: See Enclosure 1 1. PURPOSE. This instruction reissues DoD Directive (DoDD)
~'ID. Request for Records Disposition Authority
r-------~------------------~.~ ----------------------------_, ---~~----------------------------, Request for Records Disposition Authority Leave Blank (NARA Use Only) =-~~ ~~~~ ~~(S~e~e~ln~st~ru~c=tl~o=ns~on~re=v~e=rs~e~)~~
ELECTRONIC RECORDS ARCHIVES REQUIREMENTS DOCUMENT (RD v4.0)
ELECTRONIC RECORDS ARCHIVES REQUIREMENTS DOCUMENT (RD v4.0) for the NATIONAL ARCHIVES AND RECORDS ADMINISTRATION ELECTRONIC RECORDS ARCHIVES PROGRAM MANAGEMENT OFFICE (NARA ERA PMO) Final 07/30/2010 Revisions
Project Management Guidelines
Project Management Guidelines 1. INTRODUCTION. This Appendix (Project Management Guidelines) sets forth the detailed Project Management Guidelines. 2. PROJECT MANAGEMENT PLAN POLICY AND GUIDELINES OVERVIEW.
United States Department of the Interior
United States Department of the Interior NATIONAL PARK SERVICE 1849 C Street, N.W. Washington, D.C. 20240 DIRECTOR'S ORDER #lld: RECORDS AND ELECTRONIC INFORMATION MANAGEMENT Effective Date: \ Duration:
Gatekeeper PKI Framework. February 2009. Registration Authority Operations Manual Review Criteria
Gatekeeper PKI Framework ISBN 1 921182 24 5 Department of Finance and Deregulation Australian Government Information Management Office Commonwealth of Australia 2009 This work is copyright. Apart from
TITLE III INFORMATION SECURITY
H. R. 2458 48 (1) maximize the degree to which unclassified geographic information from various sources can be made electronically compatible and accessible; and (2) promote the development of interoperable
Electronic Records Management Guidelines
Electronic Records Management Guidelines Contents Section 1: Authority... 1 Section 2: Purpose and Scope... 1 Section 3: Records Custodian Responsibilities... 2 Section 4: Information Systems that produce,
Idaho Records Center A Program of the Idaho State Archives
Idaho Records Center A Program of the Idaho State Archives Data Processing Records Retention Schedule of the Records Management Guide (This Schedule Revised April, 2008) C.L. BUTCH OTTER, GOVERNOR Idaho
Information Management Advice 39 Developing an Information Asset Register
Information Management Advice 39 Developing an Information Asset Register Introduction The amount of information agencies create is continually increasing, and whether your agency is large or small, if
APPENDIX 8 TO SCHEDULE 3.3
APPENDI 8 TO SCHEDULE 3.3 TO THE COMPREHENSIVE INFRASTRUCTURE AGREEMENT APPENDI 8 TO SCHEDULE 3.3 TO THE COMPREHENSIVE INFRASTRUCTURE AGREEMENT APPENDI 8 TO SCHEDULE 3.3 TO THE COMPREHENSIVE INFRASTRUCTURE
