Documente Academic
Documente Profesional
Documente Cultură
Project Manager
(Print name)
Project Description
(signature)
(date)
Page 1 of 8
TABLE OF CONTENTS
SYSTEM OVERVIEW............................................................................................................................................ 3
NETWORK ARCHITECTURE.................................................................................................................................... 3
INTERFACES / RELATED SYSTEMS......................................................................................................................... 3
FILE TRANSFER / FILE HANDLING.......................................................................................................................... 4
APPLICATION....................................................................................................................................................... 4
APPLICATION ARCHITECTURE................................................................................................................................ 4
DEVELOPMENT TOOLS.......................................................................................................................................... 5
APPLICATION URLS............................................................................................................................................. 5
SECURITY / USER PROFILES................................................................................................................................. 5
SOURCE CODE / EXECUTABLE FILE....................................................................................................................... 5
DATABASE........................................................................................................................................................... 6
ENTITY RELATIONSHIP.......................................................................................................................................... 6
DATABASE LINKS.................................................................................................................................................. 6
ROUTINE OPERATIONAL TASKS....................................................................................................................... 6
JOB LIST.............................................................................................................................................................. 6
JOB DESCRIPTION TABLES.................................................................................................................................... 6
BACKUP AND RECOVERY PROCEDURES........................................................................................................ 7
START-UP AND SHUTDOWN PROCEDURES.................................................................................................... 7
SERVER SHUTDOWN AND START-UP...................................................................................................................... 7
APPLICATION SHUTDOWN AND START-UP............................................................................................................... 7
ADDITIONAL COMMENTS................................................................................................................................... 8
PREPARED BY..................................................................................................................................................... 8
REVIEWED BY...................................................................................................................................................... 8
APPROVALS......................................................................................................................................................... 8
Page 2 of 8
SYSTEM OVERVIEW
Network Architecture
Description
<< Each project usually contains unique characteristics which are important
to convey to the various Operational groups. Identify any project related
anomalies learned during development and testing. For example information
can be included on the following: Public Safety Issues, Show Stoppers,
Compatibility Matrices / Dependencies, Information Classification Warnings
(Data Sensitivity). >>
Hours of Availability
<< What are the hours of system availability? When the system can be
brought down for maintenance? >>
<< List any known critical periods for this system. Critical Periods are often a
factor in scheduling downtime, change management windows or assessing
criticality of an outage. >>
Important Note: Refer to the Batch Job section for detail information on
when jobs are supposed to be run, how to run them, and what to do if the run
is unsuccessful.
all
Page 3 of 8
<< Briefly explain how files (jobs, reports) are transferred once they have
been created. >>
File names
Direction
(Incoming or
Outgoing)
Destination
Encryption
Method
Schedule
<< encryption
method1 >>
<< schedule1
>>
APPLICATION
Application Architecture
Description
<< Provide a brief description of the application architecture and all of its
components >>
Development Tools
Development Tool
Operational Procedure Manual (OPM)
Template Version 3.9, 2013-11-13
Purpose
Page 4 of 8
Application URLs
Environment
Development
Description
Address (URL)
Description
Test
Production
Other: <<specify >>
Location
<< Provide the location of source
code / executable files >>
Comments
<< Provide any
information >>
other
notable
DATABASE
Entity Relationship
Description
Operational Procedure Manual (OPM)
Template Version 3.9, 2013-11-13
<< Briefly describe the entity relationship between the database tables. >>
Page 5 of 8
Database Links
Description
<< Briefly describe the all links / interfaces to other systems (e.g. FMS) >>
Database Link
Description
<< A Job List is a table which lists all programs that are run and their
schedule. In the table below list each job ID, the name and the schedule. >>
Job ID
<< Jobid1 >>
Job Name
<< jobname1 >>
Schedule
<< schedule1 >>
Job ID
<< The job description tables provide detailed notes on each job. In the table
below list each job ID, the description, the parameters required to run the job,
the fall-over or rerun instructions and the estimated time to run the job. >>
Job Description
(How to)
Parameters Required
to Run Job
Fall-over / Rerun
Instructions
Page 6 of 8
<<jobdescription1>>
BACKUP AND
<<parameters1>>
<<fallover1>>
<<timeframe1>>
RECOVERY PROCEDURES
Important Note
<< The backup schedule for each server is included in the servers Build
Book provided by the project team. Refer to the servers Build Book for the
backup schedule. >>
<< The order for starting and stopping servers and applications is very
important. List the steps in the order with which each piece will need to be
shutdown and/or restarted for each of the tables below. >>
Instructions
<<instructions1>>
Instructions
<<instructions1>>
ADDITIONAL COMMENTS
<< Provide any additional comments or other notable information in this section. If there is information that does
not fit into any of the categories above, then use this section as a place holder. >>
Page 7 of 8
PREPARED BY
Project Manager
(Print name)
(signature)
(date)
(Print name)
(signature)
(date)
(Print name)
(signature)
(date)
(Print name)
(signature)
(date)
REVIEWED BY
<< Title >>
APPROVED BY
Application Services
Manager
Operations Manager
Page 8 of 8