January 29, 2013 Iden Fy Organiza Ons Formalize Collabora .
January 29, 2013Federal Enterprise ArchitectureFrameworkVersion 2ServiceDeliveryGovernance(SRM)Security Controls(Ex 53/ 300)(EVM)Program Mgmt.Capital PlanningHuman Capital Mgmt. (KSAs)ReportingTransition PlanStandardsAuthoritativeReference1.1Engage Sponsor andAssess StakeholderNeeds2.1Iden fy Organiza onsand Service Providers toEngage3.1Formalize Collabora vePlanning Team andLaunch Planning4.1Define Funding Strategyand Make Decision5.1Operate with the NewCapabili es1.2Analyze and ValidateNeeds2.2Analyze Opportuni esto Leverage3.2Refine the Vision forPerformance andOutcomes4.2Obtain Resources andValidate Plan5.2Measure PerformanceAgainst Metrics1.3Formulate Case toAddress the Needs2.3Determine Whether toLeverage3.3Analyze the CurrentState, DetermineAdjustments, and Planthe Target State4.3Execute the Plan5.3Analyze and ProvideFeedback1.4Iden fy and EngageGovernance3.4Formulate theIntegrated Plan andRoadmap3.5Ini ate Execu ic Plan/Goals (PRM)RoadmapStrategicPlan/Goals (PRM)Strategic Plan/Goals(PRM)BusinessStrategic Plan/Goals(PRM)Strategic Plan / BusinessData ost(IRM)InfrastructureInfrastructure
January 29, 2013Table of Contents1 Introduction to the Federal Enterprise Architecture Framework (FEAF) v2 . 112 Overview of the Collaborative Planning Methodology . 133 Step 1: Identify and Validate . 153.1 Purpose . 153.2 The Planner’s Role. 153.3 Outcome . 164 Step 2: Research and Leverage . 164.1 Purpose . 164.2 The Planner’s Role. 164.3 Outcome . 165 Step 3: Define and Plan . 175.1 Purpose . 175.2 The Planner’s Role. 175.3 Outcome . 176 Step 4: Invest and Execute . 186.1 Purpose . 186.2 The Planner’s Role. 186.3 Outcome . 187 Step 5: Perform and Measure . 187.1 Purpose . 187.2 The Planner’s Role. 187.3 Outcome . 198 Overview of the Consolidated Reference Model . 209 Introduction to the Performance Reference Model . 239.1 Purpose of the Performance Reference Model . 239.2 Structure of the Performance Reference Model . 2310 Using the Performance Reference Model Taxonomy . 2410.1 Integrating CPIC (Exhibit 300) Performance Reporting with the FEA PRM . 2411 PRM Touchpoints with other Reference Models . 2512 Associated Methods/Best Practices for the PRM . 252
January 29, 201312.1 Line of Sight. 2512.2 Selecting a Balanced Set of Exhibit 300 Performance Measures. 2813 PRM Summary. 2814 Introduction to the Business Reference Model . 3014.1 Purpose of the Business Reference Model . 3014.2 Structure of the Business Reference Model . 3015 Using the Business Reference Model Taxonomy . 3115.1 Identifying opportunities to share services government-wide . 3115.2 Reducing costs by eliminating duplication within the enterprise . 3116 BRM Touchpoints with other Reference Models. 3217 Associated Methods/Best Practices for the Business Reference Model . 3317.1 Business Architecture for Decision Support . 3317.2 Business Process Modeling . 3418 BRM Summary . 3419 Introduction to the Data Reference Model . 3519.1 Purpose of the Data Reference Model . 3519.2 Structure of the Data Reference Model. 3520 Using the Data Reference Model Taxonomy . 3620.1 Using the DRM to Compare Data Sources across Federal Agencies . 3620.2 Using the DRM to Create a Standardized Information Exchange . 3621 DRM Touchpoints with other Reference Models . 3722 Associated Methods/Best Practices for the Data Reference Model . 3722.1 Data Description . 3722.2 Data Context . 3822.3 Data Sharing . 3923 DRM Summary . 3924 Introduction to the Application Reference Model . 4124.1 Purpose of the Application Reference Model. 4124.2 Structure of the Application Reference Model . 4125 Using the Application Reference Model . 4225.1 IT Cost Reduction through IT/ Application Portfolio Management . 4225.2 Using the ARM with the entire Consolidated Reference Model (CRM) . 433
January 29, 201326 ARM Touchpoints with other Reference Models . 4327 Associated Methods/Best Practices for the Application Reference Model. 4427.1 Capability Modeling and Analysis . 4427.2 Service Oriented Architecture . 4427.3 Portfolio Management . 4528 ARM Summary . 4529 Introduction to the Infrastructure Reference Model . 4629.1 Purpose of the Infrastructure Reference Model. 4629.2 Structure of the Infrastructure Reference Model. 4630 Using the Infrastructure Reference Model Taxonomy . 4730.1 Using the IRM to Create an IT Asset Management (ITAM) . 4730.2 Using the IRM to Identify Opportunities for Shared Services . 4831 IRM Touchpoints with other Reference Models . 4832 Associated Methods/Best Practices for the Infrastructure Reference Model . 4932.1 Methods . 4932.2 Best Practices . 4933 IRM Summary. 5034 Introduction to the Security Reference Model . 5134.1 Purpose of the Security Reference Model . 5134.2 Structure of the Security Reference Model . 5135 Using the Security Reference Model Taxonomy . 5235.1 Using Standards to classify Policy at the International, National, Federal, Sector, Enterprise orDepartment Level . 5235.2 Using Policy to select Controls at the Agency or Segment Level . 5335.3 Enforcing Design with Controls at the System or Application Level . 5336 SRM Touchpoints with other Reference Models . 5437 Associated Methods/Best Practices for the Security Reference Model . 5437.1 Risk Based Design. 5437.2 Security Controls . 5538 SRM Summary . 5539 Artifacts . 5739.1 Strategy Sub-Architecture Domain . 584
January 29, 201339.2 Business Sub-Architecture Domain. 5939.3 Data Sub-Architecture Domain . 6039.4 Applications Sub-Architecture Domain. 6239.5 Infrastructure Sub-Architecture Domain . 6339.6 Security Sub-Architecture Domain. 64Appendix A: Collaborative Planning Methodology Guidance Document . 65A.1 Overview of the Collaborative Planning Methodology . 65A.1.1 Step 1: Identify and Validate . 67A.1.2 Step 2: Research and Leverage . 68A.1.3 Step 3: Define and Plan. 68A.1.4 Step 4: Invest and Execute. 69A.1.5 Step 5: Perform and Measure. 70A.2 Step 1: Identify and Validate . 71A.2.1 Step At-a-Glance . 72A.2.2 A Note on Core Artifacts . 73A.2.3 Activity 1.1: Engage Sponsor and Assess Stakeholder Needs . 73A.2.4 Activity 1.2: Analyze and Validate Needs . 76A.2.5 Activity 1.3: Formulate case to address the needs . 78A.2.6 Activity 1.4: Identify and Engage Governance . 81A.3 Step 2: Research and Leverage . 85A.3.1 Step At-a-Glance . 86A.3.2 A Note on Core Artifacts . 87A.3.3 Activity 2.1: Identify Organizations and Service Providers to Engage . 87A.3.4 Activity 2.2: Analyze Opportunities to Leverage . 89A.3.5 Activity 2.3: Determine Whether to Leverage . 92A.4 Step 3: Define and Plan. 94A.4.1 Step At-a-Glance . 95A.4.2 A Note on Core Artifacts . 97A.4.3 Activity 3.1: Formalize Collaborative Planning Team and Launch Planning . 97A.4.4 Activity 3.2: Refine the vision for performance and outcomes . 100A.4.5 Activity 3.3: Analyze the Current State, Determine Adjustments, and Plan the Target State . 104A.4.6 Activity 3.4: Formulate the Integrated Plan and Roadmap . 1255
January 29, 2013A.4.7 Activity 3.5: Initiate Execution Governance. 131A.5 Step 4: Invest and Execute . 135A.5.1 Step At-a-Glance . 137A.5.2 A Note on Core Artifacts . 137A.5.3 Activity 4.1: Define Funding Strategy and Make Decision . 138A.5.4 Activity 4.2: Obtain Resources and Validate Plan. 139A.5.5 Activity 4.3: Execute the Plan . 139A.6 Step 5: Perfo
January 29, 2013 1 Federal Enterprise Architecture Framework Version 2 Service Delivery Authoritative Reference on l n Future Views Current Views Transition Plan d Governance Standards g Host Infrastructure Enabling Applications Data and Information Business Services Strategic Plan/Goals (PR
Push-to-talk (PTT) is instant one-to-many or one-to-one mobile voice communication without protracted dialing, ringing, and answering steps a regular phone call. . the Nextel iDEN service was purchased and subsequently shut-down by Sprint in 2013, iDEN is still used in numerous markets globally. Like LMR, iDEN is a narrowband 2G technology .
The Motorola iDEN Approved Lithium Ion chargers provide optimum performance. Other chargers may not fully charge the iDEN Lithium Ion battery or may yield a reduced number of lifetime charge cycles. Extreme temperatures degrade battery performance. Do not store the battery where temperatures exceed 140 F (60 C) or fall below -4 F .
Figure 1.1. An overview of ITIL and ITSM (Iden and Eikebrokk, 2013). Among these, ITIL is considered as a framework of best practices which aims for facilitat-ing the delivery of high quality IT services at a reasonable cost. IT departments can employ ITIL best practices in order to achieve IT service management (Iden & Eikebrokk, 2013).
Volume 29, Issue 21 Virginia Register of Regulations June 17, 2013 2526 PUBLICATION SCHEDULE AND DEADLINES June 2013 through June 2014 Volume: Issue Material Submitted By Noon* Will Be Published On 29:21 May 29, 2013 June 17, 2013 29:22 June 12, 2013 July 1, 2013 29:23 June 26, 2013 July 15, 2013 29:24 July 10, 2013 July 29, 2013
Volume 5 Issue 1 January, 2020 January 1 January 6 January 12 January 15 January 15 January 20 January 28 Church Office Closed Women of the Church Meeting 11:00 am Vestry Meeting 11:30 am St. Jude’s Prayer Guild 11:00 am Outreach Committee Meeting 3:00 pm Church Office Closed for MLK Day Men’s Group Meeting 6:00 pm .
Winter Break Begins/No Classes December 20 December 16 December 17 December 16 College Closed December 21 December 17 December 18 December 17 SPRING SEMESTER Spring Semester Begins : January 7, 2020 . January 5, 2021 : January 4, 2022 . January 4, 2023 : Martin Luther King Day/College Closed January 20 January 18 January 17 January 16
GENERIC RISK ASSESSMENT INDEX: Risk Assessments Version Issue Date Mobile Scaffold Towers 3 May 2013 Working on Scaffolds 3 May 2013 Excavations 3 May 2013 Working in Confined Spaces 3 May 2013 Working Near Buried Spaces 3 May 2013 Crane Operations 3 May 2013 Maintenance & Repair of Plant 3 May 2013 Welding 3 May 2013 Demolition 3 May 2013 Work Involving Asbestos Products 3 May 2013 Excessive .
US 9,203,881 B2 Page 3 (56) References Cited 2013/0157699 Al * 6/2013 Talwar et al. 455/466 2013/0212497 Al 8/2013 Zelenko et al. U.S. PATENT DOCUMENTS 2013/0247216 Al 9/2013 Cinarkaya et al. 2013/0086245 Al * 4/2013 Lu et al. 709/223 2013/0091204 Al * 4/2013 Loh et al. 709/204 * cited by examiner
