AI01 Process Description

AI01: Solutions Development

Version 1.0

Printable Version

Version History

1. Description

Identification and analysis of the alternative opportunities measured against user requirements.

2. Service Activities

Information requirements definition: business requirements satisfied by the existing system and to be satisfied by the proposed new or modified system (software, data and infrastructure) are defined before a development, implementation or modification project should be approved. These include: analysis of the alternative courses of action that will satisfy the business requirements established for a proposed new or modified system. formulation of alternative courses of action and acquisition strategy, the identification of commercial software packages that satisfy the needs of a particular information system development or modification project before a final selection decision is made, the evaluation of the requirements and the specifications for an RFP (request for proposal) when dealing with a third-party service vendor, assurance that any standard or required procedures (eg. procurement) are adhered to when identifying potential system software programs that will satisfy its operational requirements, for licensed software acquired from third-party providers, assurance that the providers have appropriate procedures to validate, protect, and maintain the software product's integrity rights, negotiate with the supplier an acceptance plan for technology usage and facilities to be provided
Feasibility studies: examine the technological and financial feasibility of alternatives for satisfying the business requirements established for the development of a proposed new or modified information system project.
Business re-engineering services by: Leading high-level design of new information systems Supporting business process changes Assisting clients to continually improve quality and customer service; Monitoring projects and customer satisfaction on an ongoing basis.
Security controls: examine the costs and benefits of security to guarantee that the costs of controls do not exceed benefits.

3. Key Goal Indicators

Number or percent of projects restarted or redirected
Number or backlog of non-addressed solutions
Number or percent of solutions signed off by the chief technology officer or architect as in line with the IT strategy and IT architecture
Number or percent of solutions signed off by user as fully meeting user requirements
Number or percent of solutions that fully consider alternatives, feasibility and risk
Percent of implemented solutions formally approved by business owners and by IT

ebc Service Commitments

working with MOL CAO to obtain agreement of IFIS Steering Committee to move forward with OTEC, and to implement same in MOL,
implement desktop image/software monitoring capability to enables remote enforcement of desktop standardized image,
implement remote software download capability, based on 02-03 pilot which includes capability, measurement and subsequent implementation,
determine appropriate method to align desktop clock with servers based on national standard time,
review desktop image and testing process to ensure optimum performance for next refresh or remote fixing, if possible,
to pilot in production, the VISA 3rd party identification and authentication services. Proposed that PPSR's current Equifax authentication be replaced by the VISA service,
development and implement an Integrated Security Interface (ISI) screen prototype to register client IDs for accessing applications via the web.

4. Key Performance Indicators

Time lag between requirement definition and identification of a solution
Number or percent of solutions returned from acceptance testing
Lag time before approval of identified solution
Number of projects involving users in requirements definition and solution selection
Number of solutions subsequently affected by significant change requests due to functional changes

ebc Service Commitments

5. Critical Success Factors

There is good knowledge of the solutions available in the market
Practices are defined to address not only soundness of design and robustness of functionality, but also: operability, including performance, scalability and integration; acceptability, covering administration, maintenance and support; and sustainability, in respect of cost, productivity and appearance
Criteria for consideration of in-house development, purchased solutions and outsourcing options are defined
There is a general acquisition and implementation method or system development life cycle methodology that is clear, understood and accepted
There is a transparent, fast and efficient process for planning, initiation and approval of solutions
Key users are identified to support the solution analysis and recommendation
Solutions are constructed from pre-defined components
A structured requirements analysis process is implemented
There is a clear definition of supplier responsibilities
Use proven technology as a matter of principle and new technology only where needed, justified by a business case
There is awareness of the total cost of ownership of the solution
Security and control requirements are considered early on

6. Additional Information

Major systems supported

Maturity Level Characteristics


0	1	2	3	4	5