Jan van Bon - ИТ СЕРВИС–МЕНЕДЖМЕНТ. Вводный курс на основе ITIL. Страница 67

146

Accessibility.

147

Scripts.

148

Business Operations Support Desk.

149

Operations Bridge.

150

Под отделом эксплуатации (операционным отделом) понимается группа обеспечения операционной деятельности – Operations Department. – Прим. ред.

151

Production, Operations.

152

Service Requests.

153

Accounts.

154

Operations.

155

Effectiveness.

156

Service Level Agreements – SLA.

157

Operational Level Agreements – OLA.

158

Underpinning Contracts – UC.

159

Service Quality Plan – SQP.

160

Promotion.

161

Scope.

162

Quantifying.

163

Compose Service.

164

Service Specifications (Spec Sheets).

165

Charging.

166

Capacity.

167

Effectiveness and Efficiency.

168

Management Reports.

169

Operations.

170

Charges.

171

Direct Costs.

172

Indirect Costs.

173

Fixed Costs.

174

Variable Costs.

175

Capital Costs.

176

Operational Costs.

177

Budgeting.

178

Accounting.

179

Costing.

180

Charging.

181

По мнению редакторов, в настоящее время для ИТ этот период составляет 6-12 месяцев, при периоде долгосрочного планирования около 3-х лет.

182

Business Unit.

183

Rates.

184

KPI.

185

Cost-benefit analysis (CBA).

186

Capacity Management – более точным переводом является Управление "емкостью", т.е. управление мощностью вычислительных и телекоммуникационных средств и их потенциальными возможностями. – Прим. ред.

187

Advantages.

188

Efficiency.

189

Efficiently.

190

В данном случае это перевод словосочетания ad hoc.

191

Effectively.

192

Operational Processes.

193

Scripts.

194

Change Advisory Board – CAB.

195

Capacity Plan.

196

Request for Change – RFC.

197

Capacity Database – CDB.

198

Cost/benefit analysis.

199

Capacity Plan.

200

Simulation.

201

Baseline Assessment (Benchmark).

202

Host.

203

Application Sizing.

204

Application Sizing.

205

Operations.

206

Profiles.

207

Designers.

208

Benchmarks.

209

PABX.

210

Denial of Service – DoS.

211

Benefits.

212

Scope.

213

Business Impact Analysis.

214

Scope.

215

Stronghold/Fortress approach.

216

Skirmish Capability.

217

Recovery Options.

218

Cold Stand-by.

219

Fixed Facility.

220

Mobile Facility.

221

Warm Stand-by.

222

Upgrade.

223

Hot Start, Hot Stand-by.

224

Contingency Plan.

225

Host Computers.

226

Crisis Manager.

227

Fault-tolerant Systems.

228

Midrange Platform.

229

Effective.

230

Assurance.

231

Reliability.

232

Resilience – устойчивость: способность сервиса сохранять доступность при себе одного или нескольких ИТ-компонент. – Прим. ред.

233

Maintainability.

234

Recoverability.

235

Serviceability.

236

Availability Plan.

237

Recoverability.

238

Single Points of Failures – SPOF.

239

Component Failure Impact Analysis – CFIA.

240

CCTA Risk Analysis and Management – CRAMM.

241

Component Failure Impact Analysis – CFIA.

242

Recoverability.

243

Serviceability.

244

Availability Plan.

245

Component Failure Impact Analysis – CFIA.

246

Fault Tree Analysis – FTA.

247

CCTA Risk Analysis and Management Method – CRAMM.

248

System Outage Analysis – SOA.

249

Technical Observation Post – TOP.

250

Policy.

251

Management Framework.

252

Information Security Steering Committee.