RFP Guide
For
Service: Entrepreneurship , Uruguay
How to Develop and Manage RFPs for ICT
Executive Summary
An RFP (Request for Proposals), also known as a bid, is a very effective tool for contracting and outsourcing services in the public as well as private sectors around the globe. This document, generated by the Computer Aided Strategic Planner (STRAP) after an interview, is intended to help government officials develop an RFP for ICT services (i.e., eservices). It consists of the following sections:
Section 1: Background Information about RFPs with some general guidelines for developing and managing RFPs
Section 2: Sample RFP Templates with links to sample RFPs and also a link to the STRAP Sample RFP for downloading
Section 3: Problem Specific RFP that shows the main results generated by STRAP. These results are very problem and project specific and form the Technical Content (or Terms of Reference) in the RFP. This is the most important part and differentiates one RFP from another. :
How to Use This Document
- Step 1: Read Section 1 for general information
- Step 2: Review Section 2 to select an RFP template that suits you, if you do not already have an RFP template for your organization.
- Step 3: Carefully read the contents of Section 3 to develop an understanding of all the information captured by STRAP.
- Step 4: Based on the type of RFP (i.e., outsource only a small part versus everything), you can build a customized RFP for your situation by extracting the needed portions from Section 3 and customizing the technical content from the information shown in Section 3. If needed, you can invoke the STRAP RFP Generator to create a draft customized RFP to get you started. .
The following diagram illustrates the overall process used by STRAP to produce the RFP Guide and also the Customized RFP:
- An RFP Guide is generated automatically at the end of STRAP processing. This Guide contains detailed technical specifications generated by STRAP based on the user interview.
- A Customized RFP is generated optionally by the user, i.e., a user can take the info in the RFP Guide and build an RFP manually or use the RFP Generator to build a Customized RFP.
- The RFP is generated based on some outsourcing options that could be based on an Outsourcing Advisor that allows the users to examine and evaluate different outsourcing options such as outsource everything, outsource project management only, outsource integration bus, etc.
SECTION 1: Overview and Background Information about RFPs
An RFP is a commonly used document for soliciting submittal of proposals in response to a scope of work. RFPs are used as a basic tool for contracting goods or services.
An RFP must be a clear, concise and consistent document that provides enough information to the prospective vendors but avoid unnecessary details. It must provide the following pieces of information:
- The issuing company
- The organizational and technical environment in which the goods or services will be used
- The specific goods and services needed (Technical Specifications/Terms of Reference)
- Vendor qualifications
- Timelines
- Submission and evaluation process
- Others
Many guidelines for developing RFPs are available on the Internet. Here are a couple of examples:
- http://www.pearsonhighered.com/assets/hip/us/hip_us_pearsonhighered/samplechapter/0201775751.pdf
- http://www.phila.k12.pa.us/offices/procurement/rfp/RFP-Guidelines%2007-22-09.pdf
Section 2: Sample RFP Templates
Many companies sell RFP templates for different types of packages for a fee. See, for example, http://rfp.technologyevaluation.com/store.asp
View STRAP RFP Technical Specifications
Download STRAP RFP Technical Specifications
.
Section 3: Technical Specification (Terms of Reference)
NOTE: The following specification shows the main results generated by STRAP. These results are very problem and project specific and form the Technical Content (or Terms of Reference) in the RFP. Carefully read the following report to develop an understanding of all the information that can be used to develop and manage an RFP.
This information is not in a format to be sent out for bidding. It covers many aspects of the service being provided.
Depending on the type of outsourcing (everything versus only one part), some of the information will be important to the RFP providers and the other to the RFP responders.
You need to build a customized RFP from the following information for your situation by extracting the needed portions and customizing the technical content from the information.
For help in creating a customized RFP, please invoke the STRAP RFP Generator it will create a draft customized RFP to get you started. . .
TECHNICAL SPECIFICATIONS |
|
Service: |
entrpurug |
|
Govt.: |
urgu1 |
A. Business process description |
|
Contents
Others as needed
|
Plan Generated Document for
Economic Development in Uruguay
Service Name: Entrepreneurship
Contents |
|
The report contains a mixture of generic and customized information. Specifically:
|
1. |
Government Model |
|
Reliance on Web |
No use of Web(Paper-based systems) |
Mobility Reliance |
No use of mobile computing |
|
E-Readiness Index |
0.5848 |
Networked Readiness Index (WEF) |
3.81 |
|
Desired use in Services |
Few Services |
Time Horizon |
One year |
|
Population (2008) millions |
3.35 |
GDP (Billion USD) (2008) |
23.09 |
|
Landline Phone Connections per
100 citizens |
28.64 |
Cellular Subscriptions per 100
citizens |
104.73 |
|
Internet Users per 100 citizens |
40.01 |
Broadband Users per 100 citizens |
7.3 |
|
Industry Pattern |
Owned by Government |
Regulated by Government |
Mode of Operation |
|
Education |
No |
Yes |
Centralized |
|
e-Government Services |
Yes |
Yes |
Centralized |
|
Law Enforcement and Public Safety |
Yes |
Yes |
Centralized |
|
Utilities |
No |
Yes |
Centralized |
|
Healthcare |
No |
Yes |
Centralized |
|
Transportation |
No |
Yes |
Centralized |
|
ICT |
No |
Yes |
Centralized |
|
Agriculture |
No |
Yes |
Centralized |
|
Social Services and Welfare |
No |
Yes |
Centralized |
|
Note: Govt. owned is shown
as |
private areas are shown 
.
2. |
Service Model |
|
Parameter |
Present Mode of Operation |
Future Mode of Operation |
|
Service Availability |
Not available at all |
Available to 20% of the population |
|
Service Quality |
Non existing, intolerable |
Mostly bad, occasionally good |
|
Provider Service Management |
Non Existing |
Initial, Ad hoc |
|
Business Strategy for the Service |
Non Existing |
Vision |
|
Legal, Technical and Human Infrastructure |
Non Existing |
Policies have been defined |
|
Overall Management, Technical and Human Infrastructure of Small to Medium Businesses |
Non Existing |
Policies have been defined |
3. |
Suggested Solutions |
|
Cost and Benefit Analysis: |
|
|
|
Should be Done Whenever Possible |
|
|
|
|
Policies · http://www.policiesandprocedures.com/ · Guide to Writing Policy and Procedure Documents · Policies, Procedures and Internal Controls - a Standard Framework · www.oracle.com/partners/en/knowledge-zone/applications/042908.html |
|
Centralized : Easy to implement uniform policies |
|
|
|
|
Tip: Large number of policies |
|
Business Processes: |
|
|
|
|
|
|
|
|
Application: |
||
|
|
Strategy |
Buy |
|
|
Apps |
None |
|
|
For Centralized |
It maximizes use of common resources. It makes standardization easier. It is easier to monitor and control. |
|
Platform: |
||
|
|
Computing Load |
Low |
|
|
Machine |
MOSS 2007 [4GB RAM, 90GB Hard Disk] HP c7000 Blade server HP Modular SAN Array 1000 |
|
|
Middleware |
Standard middleware (e.g., RPC, RDA, MOM) |
|
Network: |
|
|
|
Basic Network (Broadband network not required) |
|
Security: |
|
|
|
Basic security For Decentralized: Harder to secure and recover |
|
Architectural Consideration: |
|
|
|
a portlet will be needed (a portal that can handle all business processes within this business functional area) |
4. |
Management Considerations |
Business Continuity Planning Checklist
|
||
|
GOAL 1- Establish a good
foundation |
||
|
|
Action Plan Steps |
Status |
|
|
Identify a coordinator and/or team with defined roles |
N/A |
|
|
Conduct a business process and services inventory to understand which processes are mission-critical . |
N/A |
|
|
Determine acceptable levels of service during the recovery |
N/A |
|
|
Identify essential employees and other critical inputs (sub-contractors, services, logistics, etc.) |
N/A |
|
|
Conduct a technology asset inventory to determine and document the mission-critical technology components |
N/A |
|
|
Understand the rules or regulations governing your business operations. |
N/A |
|
|
Identify a budget: Quantify the potential costs of downtime or total business failure. |
N/A |
|
|
||
|
|
BCP Manager Name |
|
|
|
BCP Manager Email |
|
|
|
Alternate Manager Name |
|
|
|
Alternate Manager Email |
|
|
|
Senior management team |
|
|
|
HR & legal team |
|
|
|
Public relations team |
|
|
|
IT team |
|
|
GOAL 2—Develop a
thorough plan |
||
|
Perform inventory on company’s hard and soft assets |
||
|
|
Add Inventory Document Link (Hard Assets) |
|
|
|
Add Inventory Document Link (Soft Assets Data etc) |
|
|
|
||
|
|
Address |
|
|
|
Other Information |
|
|
|
Others Business Functions , Process |
|
|
|
||
|
|
Date : |
Feb-1-2011 |
|
|
Department / Business Unit |
|
|
|
Members |
|
|
|
Checklist Test Report |
|
|
GOAL
3—Maintain the plan diligently |
||
|
Maintaining plan |
||
|
|
Next Update Plan Date : |
Feb-1-2011 |
|
|
Policies & Procedures |
|
|
|
||
|
|
Date : |
Feb-1-2011 |
|
|
Objective |
|
|
|
Department / Business Unit |
|
|
|
Members |
|
|
|
||
|
|
(Last and Current test , missing item, enhancing features etc) |
|
5. |
General Integration Issues |
|
This architecture document uses a service oriented architecture (SOA) based on components that provide these services. The components consist of the following (see the diagram)
Overall Integration Strategy Using SOA SOA is especially suited for integration of diverse enterprise applications that include data warehouses and migration of applications. In particular, an SOA ESB (Enterprise Service Bus) provides a collection of technologies (middleware such as Web Services, adapters/gateways for protocol conversion, data transformers, transaction managers, and work/process flow systems) that allow diverse applications to talk to each other. For example, an ESB platform can allow new EB applications written for Web users to seamlessly communicate with back-end mainframe-based ERP systems, data warehouses and databases. At their best, ESB platforms hide all the complexity needed to enable interactions between applications that were developed at different times by using different middleware technologies. Thus ESB platform is not a new technology rather, it is a combination of well-known technologies that can integrate multiple applications. All applications (business components) provide services that are invoked through well defined interfaces
|
6. |
Country/Region Specific Details |
Special Recommendations Based on Country/Regional FactorsBusiness processes
Applications
Technologies (platforms, networks)
Security
Project Planning
Total Cost of Ownership
Total Time to Install
|
B. Required Solution/System |
|
Contents
Others as needed
|
Application Requirements Document
Entrepreneurship
General Template
Table of Contents
- Definitions and Terms
- 1. Overview and Business Drivers
- 2. background Information
- 3. Application Functional Requirements
- 4. Information Models (Use Cases, Class Diagrams, Sequence Diagrams)
- 5. Logical Architecture (Application Pattern)
- 6. Architecture and Integration Requirements (General)
- 7. Architecture and Integration Requirements (Specialized based on the Interview)
- 8. Operational Requirements (Generic)
- Security/Permission Requirements
- Performance Requirements
- Hardware Requirements
- Software Requirements
- 9. Vendor Support Requirements
- Application Service Provider (ASP) Support
- Back Up and Maintenance Support
- Documentation Support
- Training Support
- 10. SOA Considerations
Definitions
and Terms
|
ACL |
Authorized Control List |
|
ACM |
Association of Computing Machinery |
|
AI |
Artificial Intelligence |
|
AIA |
Application Integration Architecture |
|
API |
Application Programming Interface |
|
ASP |
Application Service Provider |
|
ASP |
Active Server Pages A Microsoft technology for building server side code |
|
ATM |
Asynchronous Transfer Mode a packet switching Technology used typically in high data rate networks |
|
ATM |
Automatic Teller Machine used in banking |
|
B2B |
Business to Business |
|
B2C |
Business to Consumer |
|
B2E |
Business to Employee |
|
B2G |
Business to Government |
|
BREW |
Binary Runtime Environment for Wireless |
|
BSP |
Business System Planning |
|
CAD |
Computer Aided Design |
|
CAM |
Computer Aided Manufacture |
|
CBX |
Computerized Branch Exchange |
|
CCITT |
Comit Consultatif Internationale de Tlgraphique et Tlphonique (The International Telegraph and Telephone Consultative Committee) |
|
CDMA |
Code Division Multiple Access |
|
CDPD |
Cellular Digital Packet Data |
|
CGI |
Common Gateway Interface - A Web gateway technology |
|
CIO |
Chief Information Officer |
|
CORBA |
Common Object Request Broker Architecture |
|
COTS |
Commercial Off-The-Shelf |
|
CPU |
Central Processing Unit |
|
CRM |
Customer Relationship Management |
|
CSF |
Critical Success Factors |
|
CSMA/CD |
Carrier Sense Multiple Access/Collision Detect |
|
DBMS |
Database Management System |
|
DCOM |
Distributed Component Object Model |
|
DDBMS |
Distributed Database Management System |
|
DDL |
Data Definition Language used in database management |
|
DDTMS |
Distributed Data and Transaction Management System |
|
DML |
Data Manipulation Language |
|
DOD |
Department of Defense |
|
DSL |
Digital Subscriber Loop |
|
DTM |
Distributed Transaction Manager |
|
DTMS |
Distributed Transaction Management System |
|
EAI |
Enterprise Application Integration |
|
EB |
Electronic Business |
|
EC |
Electronic Commerce |
|
EDI |
Electronic Data Interchange |
|
EJB |
Enterprise Java Beans |
|
ERP |
Enterprise Resource Planning |
|
ETSI |
European Telecommunication Standards Institute |
|
FCC |
Federal Communications Commission |
|
FDDI |
Fiber Distributed Data Interface |
|
FDM |
Frequency Division Multiplexing |
|
FSO |
Free Space Optics |
|
FTP |
File Transfer Protocol |
|
GUI |
Graphical User Interface |
|
I/O |
Input/Output |
|
IDL |
Interface Definition Language used in CORBA and other distributed object middleware services |
|
IEEE |
Institute for Electrical and Electronic Engineers |
|
IMS |
Information Management System - IBM DB/DC system on mainframes |
|
IP |
Internet Protocol |
|
IPC |
Interprocess Communication |
|
IRM |
Information Resource Management a management methodology |
|
ISDN |
Integrated Services Digital Network |
|
ISO |
International Organization for Standardization |
|
ISP |
Internet Service Provider |
|
IT |
Information Technology |
|
ITU |
International Telecommunications Union |
|
ITU-T |
International Telecommunications Union - Telecommunications Services Sector |
|
J2EE |
Java Version 2 Enterprise Edition |
|
J2ME |
Java Version 2 Mobile Edition |
|
JDBC |
Java Database Connectivity |
|
LAN |
Local Area Network |
|
LDBMS |
Local Database Management System |
|
LLC |
Logical Link Control |
|
LMDS |
Local Multipoint Distribution Service |
|
LU |
Logical Unit - an endpoint in the IBM SNA environment |
|
MAC |
Medium Access Control |
|
MAN |
Metropolitan Area Network |
|
Mbps |
Million bits per second |
|
MMIT |
Microsoft Mobile Internet Toolkit |
|
MOM |
Message Oriented Middleware |
|
MVS |
Multiple Virtual System - operating system on IBM's mainframes |
|
NBS |
National Bureau of Standards |
|
NFS |
Network File Services - SUN Microsystem's File System for Networks |
|
NIST |
National Institute of Standards and Technology |
|
OAG |
Open Application Group a standards organization |
|
ODBC |
Open Database Connectivity a de-facto standard for remote SQL |
|
OMA |
Open Mobility Alliance |
|
OMG |
Object Management Group the group that developed CORBA |
|
OODBMS |
Object-Oriented Database Management System |
|
OOPL |
Object-Oriented Programming Language |
|
OS |
Operating System |
|
OSF |
Open Software Foundation |
|
OSF-DCE |
OSF Distributed Computing Environment |
|
OSF-DME |
OSF Distributed Management Environment |
|
OSI |
Open System Interconnection |
|
PBX |
Private Branch Exchange |
|
PGP |
Pretty Good Privacy |
|
PKI |
Public Key Infrastructure |
|
QoS |
Quality of Service |
|
QPSK |
Quadrature Phase Shift Keying |
|
RDA |
Remote Database Access |
|
RFID |
Radio Frequency Identification |
|
RPC |
Remote Procedure Call |
|
SCM |
Supply Chain Management |
|
SET |
Secure Electronic Transaction a security standard |
|
SNMP |
Simple Network Management Protocol - TCP/IP Network management Protocol |
|
SOAP |
Simple Object Access Protocol part of Web Services |
|
SONET |
Synchronous Optical Network |
|
SQL |
Structured Query Language |
|
SSL |
Secure Socket Layer |
|
TCP |
Transmission Control Protocol |
|
TCP/IP |
Transmission Control Protocol/Internet Protocol |
|
UDDI |
Universal Description, Discovery and Integration - a registry for Web Services |
|
UDP |
User Datagram Protocol - a protocol that runs on IP |
|
UMTS |
Universal Mobile Telecommunication System (Mainly 3G Cellular Technology) |
|
UWB |
Ultra Wideband |
|
VAN |
Value-added Network |
|
VPN |
Virtual Private Network |
|
VXML |
Voice eXtensible Markup Language |
|
WAN |
Wide Area Network |
|
WAP |
Wireless Application Protocol |
|
WLL |
Wireless Local Loop |
|
WML |
Wireless Markup Language |
|
WS |
Web Services |
|
WSN |
Wireless Sensor Network |
1. Overview and Business Drivers
Web Publishing
Publishing content on the web is one of the oldest
application of web. You basically store your files (HTML/XML) on a web server so
that the customers can access this content through Web browsers. The growing
number of Web sites that publish content (known as "resources") to be
accessed transparently by Web users is the main strength of WWW. Examples of
the Web sites at present are corporate Web sites, university Web sites,
publishing/advertising Web sites, travel agency Web sites, and small business
Web sites. Web sites can be large (e.g., large corporations may dedicate
several machines as Web sites) or small (smaller companies may rent or lease
portions of a Web site).
Business Needs (edit and modify to fit your needs)
- need to improve sales
- need to improve customer satisfaction
- need to provide new services
- need to re-engineer business processes for efficiency
- need to standardize operational processes.
- need to gain economy in services, support, and buying power.
- need for better reporting. And tracking
- need to enable integration / automation with internal systems .
- need to enable integration / automation with external providers (B2B) .
- need to improve workflow mechanism to capture and manage business processes.
- need to eliminate individually programmed software that provides little or no compatibility between markets, regions, and headquarters.
- need for a support system that provides auditing, tracking, interfacing, and automation of tasks and workflows.
- need to reduce duplicity in data, processes, and effort.
- need to improve forecasting and budget tracking in all facets of the business.
- need to quickly design and implement processes and technology changes across the organization.
- need
to monitor depreciation of assets.
2.
Background Information
Web
Publishing
Additional Information
Although conceptually a Web site is a catalog of information for each content provider over the Web, in reality, a Web site consists of three types of components: :
- Content files such as the HTML documents
- A Web server (a program) that receives browser calls and accesses contents, and/or
- Gateways that can generate Web content (e.g., generate HTML pages) and provide access to non-Web content (e.g., relational databases).
Setting up a Web site involves a large number of issues such as the following:
- Deciding who will develop the Web site, i.e., your own organization or an outside service provider.
- Determining rent versus own issue, i.e., will the site be owned by your organization or will you rent/lease space on an existing Web site (this is called "virtual hosting").
- Choosing a Web site platform, i.e., will the Web server and contents reside on a UNIX or Windows NT platform.
- Choosing a sharing level, i.e., will a machine be dedicated as a Web site or the Web site software will coexist with other software (e.g., LAN software).
- Providing and controlling access to the site, i.e, determine the networking configurations and the security firewalls to be set up.
- Designing the site, i.e., designing home pages, assigning defaults, and server configurations.
- Management and support considerations such as backup/recovery, site security, site administration, hotline support, etc.
Many Web servers for different classes of Web users are state of the market.
Apache, Sun Server, and Netscape servers are examples. The choice of a server
depends on factors such as ease of installation, performance, security,
manageability, and user friendliness.
Web publishing represents the C2B - information services business pattern.
Business
Pattern
In this pattern, the enterprises are mainly information providers. No purchasing takes place (that is a different business pattern).
This is one of the oldest model of Web and is largely used for advertisements and information dissemination through Web sites. Users, who can be either internal or external to the enterprise, interact with enterprise transactions and data. In some cases, there may be a need to access back-end applications and data. This pattern is relevant to those enterprises dealing with goods and services not normally listed in and sold from a catalog. It encompasses all user-to-business interactions not covered by the User-to-Online Purchase pattern. Many (but not all) of the functions supported by the User to Business pattern relate to Customer Relationship Management (CRM) systems.
Examples:
Government
- Submit tax returns
- Renew automobile licenses
- Download forms/applications
- Submit forms/applications
Manufacturing
- Review required parts/services
- Locate service centers
- Register
for training classes
Submit/track orders
Insurance Industry
- Locate a nearby office
- Locate brokers or agents
- Financial planner and insurance needs analysis tool
- Portfolio summary
- Policy summary and details
- Claims submission and tracking
- Online billing
Discount Brokerage
- Portfolio summary
- Detailed holdings
- Buy and sell stocks
- Transaction history
- Quotes and news
Convenience Banking
- View account balances
- View recent transactions
- Pay bills/transfer funds
- Stop payments
- Manage
bank card
3.
Application Functional Requirements
Main Functional Requirements
- Support static content in HTML and XML documents
- Support dynamic content through gateways that can dynamically generate Web content from non-Web resources (e.g., relational databases).
- Intuitive and natural design.
- Support a Web standard Web server (MS IIS or Apache)
- Support Linux or Windows platform.
- Provide appropriate sharing level (dedicated versus shared machine)
- Support
backup/recovery, site security, site administration, hotline, etc.
4.
Information Models (Use Cases, Class Diagrams, Sequence Diagrams)
== Insert information models here
5.
Logical Architecture (Application Pattern)
EntrepreneurshipLogical Application Architecture
This logical architecture consists of the following (see the diagram)
- Business
Layer that provides the business services such as the following:
- Backend resources
- External (Partner/Supplier) Resources
- These may be government and/or regulatory agencies.
- The Front-end Integration Layer that allows different types of user devices (e.g., handhelds, voice over IP) to invoke the Business Layer. This layer:
- Integrates the diverse user device technologies
- Provides necessary security services
- Back-end Integration Layer that interacts with different back-end and external applications. This layer:
- Integrates the diverse back-end databases and applications
- Provides
necessary security services
6.
Architecture and Integration Requirements (General)
Distributed Architecture Requirements
== Modify the following as needed
- The application must be decomposed into well defined business components that can be deployed, installed, and invoked independently over the Internet.
- The application must support an N tiered (N > 2) architecture with client, server, and databases.
- The architecture must support a front-end as well as back-end integration tiers.
- The application must support a replication mechanism so that all data and processes do not reside on one location.
- All levels of the architecture must be both forward and backward compatible.
- The application must be highly configurable within the server environment allowing for multiple workflow options concurrently.
- The
application must allow for internal application customization in a GUI
environment.
Interface/Integration Requirements
== Modify the following as needed
- The application must support well defined interfaces for external integration.
- The application programming interface must be documented and supported.
- The application must provide loose coupling with external systems for flexibility
- The application must have a browser-based GUI for user interactions
- The application must have conversion capabilities for different financial and regional data items (e.g., dollars to Euro).
- The application must be able to download external data files .
- The application must be able to process transactions with third party systems.
- The application must be able to interchange status information with third party systems for logistics functions.
- The application should be capable of supporting data mining applications.
- The
application must provide an effective and efficient interface for highly
mobile personnel.
7.
Architecture and Integration Requirements
Front-end Considerations
- Simple Web browser interface over HTTP because of lightweight informational interaction
Back-end Considerations
- No interfaces with back-end systems
- No data translation needed for back-end applications
B2B Considerations
- No interfaces with external systems for B2B interactions
- No data translation needed for B2B applications
Special Considerations
- Scalability
of this service should be a (major) concern due to the population of
intended users.
8.
Operational Requirements (Generic)
Security/Permission Requirements
- The solution shall allow for the creation of privileges and permissions based on work groups composed of different users at different sites.
- The solution shall enforce privileges and permissions on data fields and user screens.
- The application will support privileges for read, delete, and edit.
- A local administrator will be able to assign all user privileges and permissions.
- The
application must conform to security standards, policies, and procedures
established by the company
Performance Requirements
- The system must provide adequate turnaround for interactive work.
- The system should be robust to handle user access needs without crashes and restarts
- The system must allow backup of needed data while being continually available to users for business as usual operations.
- The
system should degrade performance gracefully if workload increases
dramatically.
Hardware Requirements
- The application server must support the following platforms: Windows/Linux/Others (specify)
- The application server must support the following platforms: Windows/Linux/Others (specify)
- The application client must support the following platforms: Windows/Linux/Others (specify)
- The application must support a hardware High Availability environment through replicated servers.
- Add
more
Software Requirements
- The application server must utilize the most recent operating systems from the following list: Windows/Linux/Others (specify)
- The application client must utilize the most recent browser version from the following list: Internet Explorer/Netscape/FireFox (specify)
- The application must utilize relational databases.
- The application must utilize a commonly available and used development environment such as Rational Rose.
- Add
more
9.
Vendor Support Requirements
Application Service Provider (ASP) Support
- The ASP must guarantee, in writing, complete privacy and security of application and data.
- The ASP must support the application 24 hours a day, 7 days a week, 365 days a year.
- Response of an application failure must be made according to the failure types by the ASP. The application shall use 3 failure types: critical, important, and minor.
- Critical failure shall mean that the System is un-useable. The response to a critical shall be immediate to 3 minutes with 30 minutes to repair after vendor notification.
- An Important failure shall mean that some part of the system is un-useable. The response to an important failure shall be 1 hr with 4 hrs to repair after vendor notification.
- A Minor failure shall mean that impairment is affecting application performance. The response to a minor failure shall be within 24 hours with 7 days to repair after vendor notification.
- The ASP will support necessary upgrades of the software features.
- The
ASP must provide all the necessary documentation needed for the customer
to use the applications (e.g., a user guide, troubleshooting information,
etc).
Back Up and Maintenance Support
- The backup files shall be generated and stored according to the following IT standards
- backups will be taken once a day (recommended) or once a week (required)
- backup copies will be stored at an external site for safety
- The application shall support an incremental online backup of the complete system, including database, as well as a full weekly online backup..
- The application
vendor must provide maintenance and upgrades on a regular basis.
Documentation Support
The application provider, in the following discussion, may be an outsourced development house or an internal software development group.
- The application vendor must provide a Users guide for all user categories interfaces.
- The application vendor must provide an Administrators guide for the application.
- The application vendor must provide online Help on all client interfaces.
- The application vendor must supply documentation on the applications maintenance.
- The application vendor must provide documentation on each database used in the proposed solution.
- The application vendor must supply upgrade instructions and release notes 30 days before a release.
- The
application vendor must provide upgrade and rollback procedures for new
releases.
Training Support
- The application vendor must provide on-site and/or application vendors site training. .
- The
application vendor must provide interactive training on CD-ROM or through
Web.
10.
SOA Considerations
Main Suggestion:
|
Suggestion
For Interoperability: A common approach used in interoperability is an ontology
mapping table (OMT). Simply stated, ontology represents a vocabulary. An OMT
translates the terms in one system to the other and thus provides the bridge
between disparate systems (see a simple example below).
|
Term in System1 |
Term in System2 |
|
Customer |
Buyer |
|
Laptop |
Computer |
|
Item |
Product |
Many organizations are pushing the use of the Semantic Web (with XML) for interoperability with focus on eGovernment, eHealth or eBusiness. Examples are:
- eGovernment-based interoperability initiative in
- The European Commission provides a framework IDABC (Interoperable Delivery of European eGovernment Services to public Administrations, Businesses and Citizens)
- Large EU projects related to cross-border systems are https://mobile.harrisburgu.edu/exchweb/bin/redir.asp?URL=http://www.eu-spocs.eu/ and https://mobile.harrisburgu.edu/exchweb/bin/redir.asp?URL=http://ec.europa.eu/information_society/apps/projects/factsheet/index.cfm?project_ref=224993There is a Semantic Interoperability Centre Europe (SEMIC.EU).
- A European Land Information Service (EULIS) is a consortium of European National Land Registers.
- In
the
- In
the
C. Detailed Requirements |
|
Contents
Other as needed
|
Computer Aided Strategic Planner
Tools, Techniques and Standards Used
|
Planning Phases |
Activities Performed |
Tools, Techniques & Standards Used |
|
P0 (Government Modeler) Choose a Country and create a Government Pattern |
S1: Define the country Profile and specify the level of use for the ICT |
Fetch and use various indicators from sources such as World Economic Forum, UNPAN, ITU |
|
S2: Create a government pattern for the chosen country |
Use the Patterns Repository to fetch and display a generic government pattern |
|
|
S3: Customize the pattern based on user inputs |
Defaults for the patterns are based on external data sources |
|
|
P1 (Initializer): Choose an Area (Domain) and Do Information Gathering |
S1; Define a service in different areas that support the MDGs (e.g., healthcare, education, economic development) |
The services are based on the government pattern and use the ITIL ITIL (IT Infrastructure Library: http://www.itil-officialsite.com/ |
|
S2: Get general information, educational resources and best practices |
Extensive literature from diverse sources is accessed and displayed. |
|
|
S3: Do a self assessment of the PMO (present method of operation) and FMO (Future Method of Operaation) |
Uses the Capability Maturity Model (CMM) measures (0 to 5) for assessment. |
|
|
P2 (Strategic Planning): High Level Planning (Management Focus) |
Cost-benefits tradeoffs |
Uses the McFarland Model |
|
Strategic analysis (buy, rent, outsource) |
Uses an intuitive decision model based on time, in-house expertise, |
|
|
Policies and procedures needed for the service |
Policies from different sources are fetched and displayed. Oracle Policy Automation |
|
|
Business processes needed |
TOGAF (The Open Architecture Framework) and US-FEA (Federal Enterprise Architecture) |
|
|
Technologies (apps, platforms, networks) |
OAG (Open Application Group -Website: http://www.oag.org/, W3C (http://www.w3c,org/), ISODP (ISO Distributed Processing), Cisco guidelines |
|
|
Security & business continuity planning |
SSI (System Security Institute), and ISO 9000 (for quality mgmt) |
|
|
Project Management & Governance |
PMBOK (Project Management Book of Knowledge) by Proj Mgmt In.(PMI)COBIT (Control Objectives for Information |
|
|
Interoperability and Integration Considerations |
SOA, SPOCS (large European initiative for interoperability https://mobile.harrisburgu.edu/exchweb/bin/redir.asp?URL=http://www.eu-spocs.eu/) |
|
|
P3 (Detailed Planner): (Technology Focus) -- Through Simulations |
Consolidated Report that shows:
|
Requirements document is based on International Institute of Business Analysis): Website: http://www.theiiba.org/ |
|
Detailed Planning & Implementation Tools |
Games, simulations, planning tools, |
|
|
P4: Monitoring and Control (Quality Focus) |
Detailed project management for monitoring and controls with quality focus |
PMBOK (Project Management Book of Knowledge) by Project Mgmt In.(PMI), COBIT (Control Objectives for Information), ValIT and RiskIT. |
D. Project Management Requirements |
|
Contents
Others
|
1.Project Management Overview
|
Project Management Highlights at a GlancePMBOK Approach: Project Management Institute (http://www.pmi.org/) has developed A Guide to the Project Management Body of Knowledge (PMBOK Guide) that is accepted as providing best practice processes in project management. The PMBOK identifies 42 processes which are organized into five process groups (Initiating, Planning, Executing, Monitoring and Controlling, and Closing) which may roughly correspond to time periods within a project and into nine knowledge areas (Scope, Time, Cost, Quality, Human Resources, Communication, Risk, Procurement, and Integration) within the process groups. The discussion in this section is based on PMIBOK.
Lean Project Management: An alternate approach that deviates somewhat from the PMBOK approach is Lean Project Management which is based on lean manufacturing. A white paper on this approach can be found at http://www.qualiscope.ca/LPMRules_CEmond.pdf
Evaluating Project Success: Generally accepted project success criteria include:
Handling Large Scale Projects:
|
2. Checklist for Project ManagementProject management is primarily concerned with determination and documentation of project activities, roles and responsibilities. The following form provides a good project management checklist. In addition to the report produced by PISA, it is a good idea to fill out this form to capture overall project management information and customize it (of course!).
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
3. Detailed Project Management for Monitoring and Control
The Report contains Project management information on different project phases like:
- Initiating
- Planning
- Executing
- Monitoring
- Closing
Monitoring and ControlSummary Report |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
