|
Introduction
The purpose of this appendix is to outline requirements that are particular
to submissions for information technology projects.
Submission requirements
In general, the information requirements outlined in appendices A and B must
be followed, with the modifications noted below.
1. Demonstrated compliance with government-wide strategies: Through
appropriate documentation, departments must demonstrate that the proposal
satisfies the strategic directions that the government has adopted for
information technology. These include:
1.1 Enhancing services through the innovative use of information and
technology: There are five major objectives in this area: renewing services and
program delivery; investing strategically; building partnerships; building an
open architecture and core infrastructure; and distributing computer power to
managers and staff;
1.2 Architecture - standards: Departments must have transition plans
for conforming to information technology standards as referenced in an open
systems environment model that defines a technical framework or architecture for
the development of computer and communications systems in the federal
government. This model encompasses the strategic directions of Open Systems
Interconnection (OSI), Electronic Service; Portability of Applications; and
enterprise-wide Open Systems. The technical approach in the project must comply
with Treasury Board Information and Technology Standards (TBITS), which should
be quoted in procurement requests; and,
1.3 Mandate of the Chief Informatics Officer: All information
technology projects must be consistent with government-wide policies, strategies
and technology standards. These policies, strategies and standards aim to
improve how government deliver services using information technology. They also
provide a basis for the development of more efficient administrative processes
in government. Functional direction will be provided by the CIO on
interdepartmental projects and cross-government initiatives, such as
administrative systems and telecommunications. Additionally, the CIO has issued
a draft Blueprint for the re-engineering of government service delivery through
improved use of information technology.
2. Departmental plans: The approach taken in the project must be
consistent with the department's strategies identified in its information
management plan. The proposed strategies will protect investments, foster
interoperability and allow competition among suppliers.
3. Use of business case methodology: The business-case approach is the
required methodology for identifying, justifying and selecting information
technology projects for investments. This approach relates specific project
proposals to departmental information technology strategies and plans in the
context of program priorities and measurable improvements in program
performance.
4. Costs: For either PPA or EPA, costs relate to project cost only. All
direct costs should be identified, including all departmental resources involved
in designing, developing and acquiring software; all implementation aspects (eg.
documentation, training, testing and installation), as well as the cost of
acquiring the information technology hardware.
5. Project brief: In most instances, a project brief will be required to
explain the complexities of the business case and of the systems development.
Additional information on the project brief is provided in Appendix F.
6. Human resource strategy: Information technology projects will usually
have significant impacts on job requirements, training and staff deployment. The
submission must include an analysis of the human resource impact of the proposed
project and the departmental strategies for addressing these impacts. Such
strategies would normally include a plan for consulting with unions and affected
personnel.
7. Other related legislation and policies: Proposed projects must
demonstrate compliance with the following:
7.1 Security requirements: These must be reviewed early in the project.
For guidance on technical security features, consult Treasury Board Information
and Technology Standards (TBITS) 6.6, Security Profile. This profile provides a
linkage to the Canadian Government Information Technology (I.T.) Security
policy, standards, and guidelines; and, provides guidance on the implementation
of secure interoperable systems.
7.2 Information management and privacy: The project must adhere to
government policy and departmental practices for information management and the
collection and use of personal information.
8. Funds: Departments must provide information on operating and
maintenance expenditures covering a five-year period following project
implementation. Departments must also indicate a source of funds for these
expenditures. The purpose of providing this information is to ensure that there
will be appropriate funding available to operate or maintain the deliverables
once the project is completed.
Further information on specific requirements for information technology
projects may be obtained from the Information Management volume of the Treasury
Board Manual or by contacting the Office of Information Management, Systems
and Technology.
|
