MCC-12-9009-RFQ-60.doc

ADDENDUM TO FAR 52.212-1 INSTRUCTIONS TO OFFERORS—COMMERCIAL ITEMS (JUN 2008)

1. Change (a) to add “The NAICS code is 541519 and the small business size standard is $25,000,000.”

2. Change (b) (8) to add “FAR 52.212-3 shall be accomplished on-line through the Online Representations and Certifications Application (ORCA) implemented in FAR Clause 52.212-3. ORCA is located at http://orca.bpn.gov.

3. Paragraph (b) (10) is applicable and must include information related to the services in the Statement of Work.

4. Change (c) to show 60 calendar days.

5. Delete (e).

6. Delete (i).

PART I

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

A. Disclosure of Organizational Conflict of Interest (OCI)

1. Contractors submitting quotes in response to this RFQ are reminded that they are required to promptly disclose to the contracting officer all facts relevant to the existence or potential existence of organizational conflicts of interest as that term is used in FAR Subpart 9.5.

(See clause entitled “ORGANIZATIONAL CONFLICTS OF INTEREST: Current MCC Contractors and Subcontractors Notice, paragraph 13).

2. Contractors have continuing obligations to make prompt and full disclosure, in writing, to the contracting officer of any organizational conflict of interest or potential conflict of interest discovered after submission of quote.

B. General Guidance

1. This section of the instructions to Offerors provides general guidance for preparing the quotation as well as specific instructions on the format and content of the quotation. The Offeror shall be compliant with the requirements as stated in the Statement of Work. Furthermore, the Offeror's quotation shall be submitted in accordance with the Offeror Submission Instructions. Non-conformance with the instructions may result in an unfavorable quotation evaluation.

2. The Offeror’s quotation shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The quotation should not simply rephrase or restate the Government's requirements, but rather shall provide convincing rationale to address how the Offeror intends to meet these requirements. The Offeror shall assume that the Government has no prior knowledge of their experience, and will base its evaluation on the information presented in the Offeror's quotation.

3. If an Offeror does not understand these instructions, then it should write to mcmilliancr@mcc.gov for clarification sufficiently in advance of the dead line for receipt of the quote to get an answer in time to meet that deadline.

4. Discrepancies. If the Offerors believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the Offerors shall immediately notify the Point of Contact in writing with supporting rationale.

5. Request for Clarification (RFC). All requests for solicitation clarifications should be submitted directly to mcmilliancr@mcc.gov via e-mail not later than 2 p.m. (EST) December 29, 2011. The Government does not guarantee that it will answer any request for clarification received later than this date. Requests for clarification that result in specific information necessary to submit quotes will be provided to all contractors. Therefore, questions/comments shall not be marked with a restrictive legend and shall not include proprietary information. The Government is not obligated to provide responses to all RFCs, but will consider them and incorporate changes into the solicitation as deemed necessary.

6. Exclusion of Quotes and Communications.

(a) At any time prior to award, including upon receipt of quotes, the Government may exclude a quote from further consideration for reasons such as (but not limited to): non-compliance with instructions related to this solicitation; the quote is not among the most highly rated; or the quote is not likely to be selected for award. The Government need not notify an offeror that its quote has been excluded from further consideration nor need it provide the offeror with a pre-award debriefing. However, the offeror will be provided post-award notification and if requested, a brief explanation of the basis for the award decision.

(b) After receipt of quotes, the Government will conduct an evaluation. The Government intends to evaluate quotes and issue a contract without communications with offerors. However, during the evaluation process, the Government may, solely at its discretion, communicate with an offeror for any purpose, such as to gain a better understanding of the quote. As a result of such communication, the Government may allow offerors to submit quote revisions. If quote revisions are allowed, the Government may, solely at its discretion, impose non-common due dates for the revisions. In other words, the Government may elect to have a quote revision date for an offeror that is different than the quote revision date for another offeror(s). The Government need not conduct communications with all offerors. Rather, the Government may, at its discretion, conduct communications with one or only some offerors. Furthermore, the Government need not permit all offerors to submit quote revisions. Rather, the Government may, at its discretion, seek quote revisions from only one or only some offerors.

C. Quote Structure

1. The offeror shall submit one (1) paper copy of the non-price quote, and one (1) paper copy of the price quote, bound with the identification of the offeror. The non-price and price sections of the quote must be physically separate. The offeror shall also provide an electronic copy of each quote, using the format identified below.

2. Text shall be presented on 8 ½ x 11 inch paper, front only, in Times New Roman or Courier typeface, no smaller than 12-point. Smaller fonts are acceptable for limited use for graphics, figures, tables, footnotes and legends. Text shall have 1” margins. Where needed for effective presentation, two page foldouts may be used which will count as two pages for quote page limitation purposes. All quote pages must be numbered.

3. The content and format of electronic copies of the quote must be identical to the hard copy quote submitted in response to this solicitation. The Government is not responsible for identifying inconsistencies between the two and may rely on either version at its discretion.

4. Information shall be confined to the appropriate section to facilitate independent evaluation. The quotes should be clear and concise, logically assembled, and indexed. Pages over the maximum page limitation for any section will be excluded from evaluation. Page limits shall include any diagrams, figures, offeror tables, or reference material. However, page limits shall not include cover pages, table of contents, indices, list of tables, and list of acronyms.

5. Electronic Copy Submission.

a. The electronic versions of text shall be in Microsoft 2010, uncompressed files. A directory identifying the file names and contents of each file shall accompany the submission. The price information shall be submitted as a separate file.

b. The electronic versions of spreadsheets shall be in Excel 2010. The electronic spreadsheets shall not be compiled or password protected. All cells and formulas shall be visible, and unprotected. Offerors shall not establish links within these files.

c. All quote data (e.g., graphs, figures, tables) shall be in a format capable of being highlighted, copied, and pasted into another application using any standard Windows software.

6. Quote Revisions.

All quote revisions shall be submitted as page changes to the paper copy, accompanied by a complete electronic resubmission of the electronic file. Revisions shall reference the appropriate section of the quote, paragraph and page number. Each revision page shall be identified by date, as well as by appropriate page number. New or changed information shall be identified by a vertical line in the margin next to the change and/or by using redline and strikeout features.

7. Quote Breakout.

a. Offerors shall submit the following information, with cover letter:

(1) Volume I - Non-Price Quote

(2) Volume II - Price Quote

b. The paper copies of the quote shall be submitted to: Conni McMillian (Contractor Representing MCC), Contracts and Grants Management Division, 875 Fifteenth Street NW, Washington, D.C. 20005, 2nd Floor. For hand delivery of quotes, offerors must arrange for delivery by contacting the POC identified above, at (202) 521-2692.

c. The electronic copy shall be forwarded to the following e-mail addresses: mcmilliancr@mcc.gov and smith-kulleylm@mcc.gov. Offerors should not send e-mail with attachments that, when combined, exceed 5 megabytes. Any e-mail in excess of this limitation may be automatically rejected by the e-mail system or the system may automatically remove and delete the attachments.

D. Offeror’s Submission Instructions

1. Proposal Preparation Instructions

a. Volume 1 – Technical/Management Capability/Key Personnel: The section shall address the offerors management approach, organizational chart, staffing plan and technical capabilites applicable to the SOW. For each labor category reflected in the schedule, offerors shall include a description of the specialized experience, technical competence, professional and technical qualifications and licenses necessary for satisfactory performance of required services in the SOW.

Resumes shall be provided for Key Personnel. The section is limited to 20 single sided pages (excluding Resumes).

b. Volume 1 – Past Performance References: The offeror shall provide the information pursuant to FAR 52.212-1 (b)(10), along with a concise narrative of each project, for three (3) projects of similar nature within the previous three year period. References from institutions that have characteristics similar to Millennium Challenge Corpration are preferred.

c. Volume 2 – Price Proposal: The price proposal will include proposed loaded hourly billing rates in the format presented in the Schedule.

2. Evaluation – Commercial Items a.The Government will award a Blanket Purchase Agreement resulting from this solicitation to the responsible offeror whose offer conforming to the solicitation will be most advantageous to the Government, price and other factors considered. The Government may elect to award a single BPA or to award multiple BPAs for the same or similar services to two or more sources under this solicitation. However, only one award is anticipated.

The following factors shall be used to evaluate offers:

Factor 1:

Technical/Management Capability/Key Personnel Factor 2:

Past Performance Factor 3: Price The Technical/Management Capability/Key Personnel is more important than Past Performance. When combined Technical/Management Capability/Key Personnel and Past Performance factors are significantly more importance than price.

b. Options. The Government will evaluate quotes for award purposes by adding the total price for all options to the total price for the basic requirement. The Government may determine that a quote is unacceptable if the option prices are significantly unbalanced. Evaluation of options shall not obligate the Government to exercise the option(s).

Part II

EVALUATION CRITERIA

1. EVALUATION CRITERIA

Factor 1: Technical/Management Capability/Key Personnel

The Government will evaluate the methodologies and approaches based on the degree that they are detailed, complete, effective, and tailored to accomplishing the DCO’s requirements as stated in the Statement of Work. The offeror’s proposed staffing and key personnel qualifications will be evaluated based on the relevance of their experience and certifications in terms of their proposed role in the project.

Factor 2: Past Performance The MCC will evaluate the offeror’s past performance on the basis of its past projects, which are similar in type, magnitude and complexity to the projects contemplated under this BPA. MCC’s evaluation of the quality and success of the offeror’s past performance on projects will be used to assess the overall probability of successful performance for this procurement.

In the case of an offeror without a record of relevant past performance or for whom information on past performance is not available, the offeror will not be evaluated favorably or unfavorably on past performance.

Factor 3: Price Price will be evaluated for reasonableness based upon an assessment of the Offeror’s total proposed price, including the base period and the option periods.

2.Evaluation Methodology The Government will perform a comparative analysis of quotes and will assess the advantages and disadvantages of each offeror’s quote as related to the evaluation factors above.

PART III

SCHEDULE AND SOW

SECTION B – Supplies or Services and Prices

As provided in this BPA, the Contractor shall provide the necessary services to accomplish the requirements described herein, when required and as ordered via Call Orders issued in accordance with Section C - Statement of Work.

Following are the fixed price labor categories, fully loaded hourly billing rates, ODC burden rates, and ceiling amounts applicable under this BPA.

(TO BE COMPLETED BY THE OFFEROR):

BASE PERIOD

Hours

ODCS

$ 25,000.00

Material and Handling ____%

Total

OPTION PERIOD ONE

Hours

ODCS

$ 25,000.00

Material and Handling ____%

Total

OPTION PERIOD TWO

Hours

ODCS

$ 25,000.00

Material and Handling ____%

Total

OPTION PERIOD THREE

Hours

ODCS

$ 25,000.00

Material and Handling ____%

Total

OPTION PERIOD FOUR

Hours

ODCS

$ 25,000.00

Material and Handling ____%

Total

Note 1. Offerors are authorized to map the above labor categories to their own contract labor categories. Offerors must use the government established LOE which is for evaluation purposes.

Note 2. The other direct cost “plug” figures should not be adjusted in Section B. Offerors should propose a handling charge percentage, if any, that equates with their normal accounting practice, and apply that to the ODC costs in the extended amount.

Note 3. All services and labor categories described in the offeror’s Volume I, Technical Proposal, must be included in the labor mix and pricing provided in Section B. Any subcontractor labor costs should be added as a separate contract line item under Other Direct Costs.

Note 4. Offerors are free to team with other vendors to meet the requirements of the solicitation.

SECTION C – Description / Specifications

STATEMENT OF WORK

MCC MIS Support Services

C.1 INTRODUCTION

The Millennium Challenge Corporation (MCC) is a Federal Corporation created under Title VI of the Foreign Operation, Export Financing, and related Programs Appropriations Act, 2004. MCC is based on the principle that aid is most effective in countries that promote good governance, economic freedom, and investments in people. MCC provides large grants to a number of eligible developing countries.

C.2 BACKGROUND

The MCC Director of Compact Operations (DCO) leverages information technology and management consulting resources to support long-term and equitable economic growth and advance U.S. foreign policy objectives by supporting economic growth, agricultural and trade, global health, and, democracy, conflict and humanitarian assistance. Through Millennium Challenge Account (MCA) Compacts the DCO coordinates assistance in four regions of the world: Sub-Saharan Africa, Asia and the Near East, Latin America and the Caribbean, and Europe and Eurasia. With its headquarters in Washington, D.C. MCC administers Compacts in 23 countries around the world.

The DCO IT and Consulting Services Contract will provide the full-lifecycle of Information Technology and Management Consulting Services including the following support services: management consulting; business operations; systems and software analysis and development; document analysis, development of systems design documents; computer programming; computer center operations; configuration management; software maintenance, testing, and troubleshooting; computer security; technical writing; training; and word processing.

The objective of MCC’s DCO requirement is to efficiently, effectively, and economically provide and maintain a services platform and technology infrastructure to support MCC employees in meeting MCC’s mission

C.3 SCOPE OF WORK

The contractor shall supply the qualified personnel and other services necessary to perform the specific and generic tasks needed to provide management consulting; business operations; systems and software analysis and development; document analysis, development of systems design documents; computer programming; computer center operations; configuration management; software maintenance, testing, and troubleshooting; computer security; technical writing; training; and word processing.

C.4 TASKS

Call Orders will be issued for services outlined in the following sections. Each Call Order will provide details of required services, deliverables, performance measures, and time and place of performance.

C.4.1 Strategic Vision, Planning, and Management

Align strategy and planning with DCO’s business goals to include definition of long-term strategic responsibility for MCC’s systems. Optimize approaches through an understanding of evolving business needs and capabilities. Manage risks associated with information and IT assets through appropriate standards and security policies. Develop and manage reports to include OMB reporting, audit tracking/reporting, metrics definition and management, and dashboard development. Provide input to and/or developing policies, standards and guidelines that direct the selection, development, implementation and use of programs and systems within the enterprise. IV&V for MCC systems to validate that the policies, initiatives, and systems are consistent with the agency’s strategies, comply with federal mandates, support business needs, and meet contractual requirements.

C.4.2 Capital Planning and Investment/Financial Management

Support related to MCC and MCA IT investment aligning with the DCO’s mission and strategic goals. Provide expertise to ensure business processes are appropriately reengineered before investing to support those processes. Provide an analysis of investments to ensure that they demonstrate a strong business case documenting the financial, technical and strategic merits justifying the investment.

Investments shall:

Align with MCC Enterprise Architecture (EA).

Fill a performance gap in MCC’s ability to meet strategic goals and objectives at the lowest life cycle cost among viable alternatives.

Have an acceptable business case demonstrating strong project management capabilities as well as sound investment planning.

Achieve a positive return on investment that is equal to or greater than that achievable through alternative use of resources.

Provide risk-adjusted cost and schedule goals, and measurable and achievable performance goals.

Provide a comprehensive risk management plan.

Assure that earned value management (EVM) processes are in place to manage DCO programs. Support DCO reporting functions to include developing/updating OMB 300/53s.

C.4.3 Policy and Procedure

In support of the DCO, assist in the development and update of operations policies and procedures in support of MCC and its interface with the MCAs.

C.4.4 IT Planning

Identification, evaluation and recommendation of solutions and opportunities, including the modification and process re-engineering of existing systems to encourage and facilitate the development of integrated systems, provide added functionality and improve productivity.

C.4.5 Requirements Analysis

A set of procedures followed by the project team to learn how the present system operates and what are its benefits and shortcomings. Users’ requirements are documented meaningfully. It is assumed that the user knows what they want, but has difficulty in translating requirements into data-processing terminology. This procedure helps get the requirements in writing to guide the subsequent efforts of the systems design and implementation. This sub-phase is one of the most important in the entire project life-cycle.

C.4.6 Systems and Database Design

Includes the design approach, alternative designs and analysis, and impact analysis. Maps and maintains traceability of the design to requirements; develops user interfaces; identifies the major components and interfaces of the system; determines impact on work flow processes; and develops testing strategies, test cases and testing plans. Also includes conducting design reviews to clarify design drivers; select an IT platform and/or architecture; identify and weigh portability considerations, potential capacity and performance implications; identify existing systems that may be reused, and other pertinent design information.

C.4.7 Systems Procedures and Standards

Devising systems procedures and standards using all applicable standards and procedures as required by the Federal Information Processing Standards, other standards, and the client organization’s standards and policies. Includes identifying the applicable standards and procedures and making recommendations about their use to the client organization.

C.4.8 Systems Development and Testing

Translating system specifications and detailed design documentation into system components, code or both. May include initial development of a prototype of the system that will be tested and evaluated before the systems development effort. Includes: developing code, conducting peer reviews and providing summary progress of the development effort; establishing and maintaining the integrity of baseline configuration, software version descriptions and related documentation; establishing test and verification procedures to ensure system integrity so that the system meets functional requirements; and, conducting unit, system and integration testing to validate the system's capabilities.

C.4.9 Systems Documentation

Development of all documentation, including manuals, e.g., operations, system maintenance, user and training, and plans, e.g., system integration and site implementation. The document is dynamic in that it will be modified to take advantage of new methodologies, techniques and tools. The documentation follows the latest approved standards at the time of development of the system.

C.4.10 Systems Installation and Acceptance

All activities associated with the installation and operation of the system. During systems implementation, includes providing support through the development of prototype installation test plans, installation test reports and the preparation of systems manuals including operations, maintenance and user manuals customized by site. Delivery of the system and all documentation and products associated with the system. Installation, integration, testing and implementation of the systems developed to include all activities associated with data conversion, data collection, capture, validation, and verification, user training and system turnover.

C.4.11 Systems Programming

Programs are written using the programming standards established by the client organization. Substantial emphasis is put on a structured process for preparing a test plan, which outlines all of the testing to be done. The programmer plans testing problems thoroughly before the testing begins. The results of the testing are then reviewed by qualified personnel to decide that each program and module is operating satisfactorily.

C.4.12 Systems Integration

Includes the analysis of the distribution of functionality across systems, development of system interface concepts, designs and specifications, and the development of specifications and standards for information transfer between systems.

C.4.13 Interoperability Verification and Testing

Verification and testing to ensure interoperability with existing systems. May include access to existing mainframes and servers, compatibility with operating systems, COTS software and client organization applications, and communications and telecommunications systems.

C.4.14 Systems Conversion

Converting systems from current environments to new ones, for example, from assembler language to 4GL. May include the development of specifications, programming, testing and documentation. Legacy systems may also be selected for the development of new front-end user interfaces.

C.4.15 Systems Enhancements, Support and Maintenance

All requests for system modification and/or enhancements, received after the systems design freeze and after the system is implemented, are classified as planned software maintenance. These requests consist of actions that are important for corrections to the design and future enhancements to the system. Systems support is provided to ensure the successful operation of the system in an accurate, efficient and timely manner. Any necessary fine-tuning and re-testing are done following client organization standards and procedures.

C.4.16 Systems Configuration Management

Systems configuration management activities commence early in the systems development life-cycle and continue for the life of the system. Configuration Management responsibilities include the review of all software, hardware, network and application changes and the identification of potential issues, conflicts or problems relating to the proposed changes, or the timing of the changes. Changes include installation of new products and components, new versions, upgrades, engineering changes, new agency-developed applications and modifications to agency applications. May include the development and implementation of a Configuration Management database and associated plans. Data to be maintained include parameters and configuration information on existing systems, reasons for the changes, associated changes and other items as recommended by the Contractor or required by the client organization. Preparation of reports and briefings to give client organization management recommendations and alternatives.

C.4.17 Database Administration

The Database Administrator (DBA) is responsible for database and data dictionary design and establishment, performance monitoring and timing, database reorganization, database backup and recovery, DBMS service utilities, DBMS software maintenance, disk-space management and software planning and evaluation. The DBA is responsible for safekeeping the data and for control of the data and its structure. The DBA is also concerned with the various design methods used in developing databases.

C.4.18 Data Conversion

Data conversion and migration services to move data between existing client organization systems and between existing and new systems. This could be across operating systems and/or hardware platforms or between different databases. It applies to client organization application files and end-user database files. Activities include creating file inventories, developing procedures for, and conducting, data conversions and ports, and acceptance testing activities. Also includes developing procedures and proposed methods for performing file migration with a minimum disruption to end-users.

C.4.19 Information Security

IT Security design services will be a critical component of DCO’s ongoing work with the MCAs around the world. The IT security design of local MCA systems, as well as, the interfaces with MCCnet is critical for the secure operation of the various management information systems that are used to operate the both MCAs and MCC. In particular, enhancing IT security of data residing in computer files or during transmission, assessing IT risks relating to privacy, fraud and abuse and the adequacy of internal controls to eliminate and/or mitigate risks to systems being built. Also includes the conduct of risk analyses and the development of recommendations and implementations for how the MCAs interface with MCC. Identification and recommendation of new security-related technology product versions and enhancements to existing products and services. Developing implementation, transition and verification testing plans for installing these products within the existing client organization technology infrastructure.

C.4.20 Telecommunication Systems, incl. Local, Metropolitan and Wide-area Networking

Design and development of services relating to MCA stand-up of all prototype hardware, firmware, software, proof-of-concept capability and prototype engineering maintenance and support to initiate and complete the end-to-end transmission of data. May also include the end-to-end transmission of voice and video traffic.

C.4.21 User Training

Schedules for implementation are completed, and the users are given their manuals and comprehensive training in the operation of the system. The production files are created or converted to make the system operational. User training also includes formal instruction on the use of commercially available COTS software.

C.4.22 Data Entry

Initialization of data collection processes to capture existing unstructured data to validate data being captured, verify integrity of data collected, and assure all data captured complies with data administration standards. Includes system data dictionaries and documentation to support data collection functions. Personnel may operate keyboard-controlled data entry devices to transcribe data into forms suitable for computer processing. The work requires experience and judgment in searching, interpreting and selecting items from a variety of source documents.

C.4.23 Object Oriented Design/Programming

Transforming an object-oriented model into the specifications required to create the system. Moving from object-oriented analysis to object-oriented design is accomplished by expanding the model into ever more detail. Object-oriented programming is more flexible than standard programming. It is an evolutionary form of modular programming with more formal rules that allow pieces of software to be reused and interchanged among programs. Each object can then be examined, discussed, modeled, designed, programmed, tested and implemented.

C.4.24 Technical Support

Providing a full range of technical expertise in all areas of computer knowledge. This includes programming, systems design and development, systems analysis and other software tasks. It includes the ability to operate computer systems and associated peripheral equipment including servers, monitors, disk-drives, printers and modems. Support may be requested in mainframe, minicomputer and/or personal computer environments, help desk/InfoCenter, and in field sites. The technical assistance may include database maintenance, performance monitoring and tuning, networking and telecommunications support.

C.4.25 Workflow Processing

The use of automated methods for the routing and control of documents and transactions through a process such as procurement requests, personnel requests, etc. Also involves scanning and storing information in digital form on computers. The information may be pictures, drawings or text. This process may also be described as the combining of single work units and their (partial) products as they are aggregated in an overall process, such as data entry to verification to populating a database to query and reporting. It could be represented in a flowchart or a process model where each function is shown with inputs, methods and controls from other functions, outputs to other functions that serve these purposes, and the overall initiating activity and end-product.

C.4.26 Records/Document Management and Information Distribution

Use of automated systems to manage and distribute records and documents. Records management includes, but is not limited to, data entry, tracking, archiving and destruction, reporting and security of paper records through the use of automated tools such as bar-coding. Document management includes, but is not limited to, records management and the use of automated tools to assist in gaining control over revision cycles, tracking revision history, setting user authorizations, redlining, multiple department communications and data-sharing, and storing the data about an organization’s documents to assist in search and retrieval.

C.4.27 Joint Requirements Planning (JRP)

JRP consists of workshops with key end-users for planning and designing a system. The users are encouraged to do most of the talking. Information Systems staff translate what the users want into structured specifications and design so that users can understand and discuss the results. JRP sessions do not contain technical detail. They often involve higher-level managers and sometimes top-management. They establish requirements and justification for a system and the detailed functions it will perform. A major benefit of JRP is making executives think creatively about how information systems can help them. The workshops cause an examination of goals, problems, success factors and strategic opportunities in information strategy planning.

C.4.28 Joint Applications Development (JAD)

In the JAD session, several knowledgeable people in the subject organization or in the subject functional area meet for extensive and intensive discussions and brain-storming sessions. These sessions are professionally facilitated and discussion/conclusions and disagreements are formally captured and distributed. These sessions strive to accomplish agreement or consensus on the topics of the session. Disagreements are resolved so everyone understands what the target/new process/function/system will and will not accomplish.

C.4.29 Rapid Applications Development (RAD)

An approach to systems development that incorporates a variety of automated design tools. RAD focuses on human management and user involvement as much as on technology. RAD aims for rapid development of a single, stand-alone system of limited scope. The use of tools is a necessity for this path, as are rapid development techniques and features such as time-box management, reusability and user workshops. RAD techniques are largely a subset of Systems and Information Engineering techniques.

C.4.30 Feasibility Study

Identifies objectives, requirements, system concepts, and candidate approaches. It researches possible solutions and analyzes commercial off-the-shelf (COTS) products available for achieving the objectives. May include making recommendations on the approach to be taken. The feasibility studies will be used by managers to decide whether to proceed with the task.

C.4.31 Cost-benefit Analysis

An in-depth evaluation of a given approach as to technical feasibility and/or the benefits to be gained for a specific cost. The analysis involves identifying, developing and analyzing the costs (actual and opportunity) and benefits of a given approach in quantitative terms if feasible and in qualitative terms otherwise, and preparation of a recommendation to proceed or not to proceed. The user may require that this type of analysis occur independently or with other activities comprising a full system development effort.

C.4.32 Business Process Re-engineering

A complete analysis of the processes used to generate desired products and services with a possible revamping of the entire approach. The primary drivers should always be the customer’s needs. These needs ultimately dictate the scope and the level of technology investment. The issues that need to be reconciled include time, quality, customer perspective, people empowerment, efficiency and flexibility. Technology is considered a potential enabler of the new approach.

C.4.33 Systems and Information Engineering

An integrated set of methodologies and products used to guide and develop information processing within an organization. It starts with enterprise-wide strategic planning and ends with operational applications. It includes activities required for the support of operational systems oriented to enhancing operations of hardware and software systems to include the collection and analysis of systems information, diagnosis of problems and development of recommendations to resolve problems. It establishes and maintains systems and software configuration baseline data and documentation. It includes redesign activities that modify functionality and/or produce technical improvements to enhance software and security. It monitors system execution and performance; performs problem analysis and resolution; and provides technical assistance to the end-user. It performs system and software conversion activities that include the transition of existing applications from one environment to another. It performs production control activities such as the support of cyclical changes to operational workloads, data compression, data restores, reorganization of files, recovery of systems, production of reports, download/upload of information, and setup and verification of fields and programs for the execution of production runs. It prepares and executes disaster recovery procedures; analyzes, compiles and aggregates data to produce statistical trend analysis reports; develops user-friendly interfaces between different automation functions and upload/download capabilities; and develops and implements an audit strategy to ensure the integrity and confidentiality of data.

C.4.34 Other Program-Related Services

Examples include technical and quality reviews, documentation of existing systems and procedures, preparation of standards and procedures, preparation and performance of special presentations, provision of training, document analysis, data collection and operational analysis.

PART IV

BLANKET PURCHASE AGREEMENT (BPA)

CLAUSES

1. CEILING AMOUNT

The total ceiling amount for the BPA will be $6,000,000.00

2. OBLIGATION OF FUNDS. This BPA does not obligate any funds. Funds will be obligated by the placement of call orders issued under FAR Part 13 and agency regulations.

3. PERFORMANCE LOCATION

All work under this call order will be completed at the Contractor’s office, in Washington, D.C., and/or in the any MCC eligible country, if required.

4. PERIOD OF PERFORMANCE

BASE PERIOD: 1 February 2012 – 31 January 2013 OPTION PERIOD ONE: 1 February 2013 – 31 January 2014

OPTION PERIOD TWO: 1 February 2014 – 31 January 2015

OPTION PERIOD THREE: 1 February 2015 – 31 January 2016

OPTION PERIOD FOUR: 1 February 2016 – 31 January 2017

5. QUALITY ASSURANCE

The Contractor shall have in place and maintain a Quality Control Plan (QCP) that covers, as a minimum, how the Contractor intends to meet the requirements of all performance objectives, monitor and proactively manage call order requirements. It shall also include the mechanism by which the Government will be notified of performance related incidents that are likely to affect quality of services or impact mission accomplishment. The Contractor shall provide a copy of its QCP to the COTR within 15 days of the effective date of call order award. Any proposed changes to the QCP shall be provided to the Contracting Officer for review and comment no later than 10 working days prior to the effective date of the proposed changes.

6. TRAVEL REQUIREMENTS

Long distance Travel and Other Direct Costs (ODC) are anticipated during the performance of this requirement. Since these costs cannot be accurately forecast at this time, they are awarded on a cost reimbursable basis. The contractor shall be reimbursed for actual allowable costs that apply over the life of the BPA, not to exceed the amount shown in the schedule.

Costs incurred shall be burdened with the contractor’s indirect handling rate as entered in the schedule (contractor to enter amount, but not to exceed the ceiling rate of the basic BPA). If no rate is specified in the schedule, no indirect rates shall be applied to or reimbursed on such costs.

All requests for Long Distance Travel and ODCs must be approved by the MCC Contracting Officer’s Representative (COR) prior to incurring costs. Long distance travel will be reimbursed to the extent allowable pursuant to the Federal Travel Regulations (FTR). Local travel shall be billed as an ODC and is defined as all travel within a fifty (50) mile radius of Washington, DC, or within a fifty mile radius of the contractor’s facility when the client site is outside the Washington, DC area (excluding normal commuting travel).

7. KEY PERSONNEL

A Program Management Office (PMO), staffed with two Project Managers (Key Personnel), will manage and be responsible for all work approved under this contract be ultimately responsible for the quality and efficiency of the DCO call orders to include both technical issues and business processes. The COTR/PM shall assign tasking to contractor personnel, supervise on-going technical efforts, and manage overall call order performance.

The following personnel are hereby considered essential to the work being performed hereunder, and shall be designated as Key Personnel:

Labor Category - Project Managers The Contractor shall not substitute any Key Personnel without prior consent of the Contracting Officer Technical Representative (COTR) and a written permission of the Contracting Officer (CO). Proposed substitutes should have comparable qualifications to those of the persons being replaced. The Contracting Officer will notify the Contractor within 7 days after receipt of all required information of the consent on substitutes. No change in fixed unit prices may occur as a result of key personnel substitution.

8. MINIMUM PERSONNEL SKILLS REQUIREMENTS

The contractor shall propose labor categories sufficient to accomplish all tasks included in the MIS Support Services SOW. Example labor category titles are included for reference below:

Project Manager

Experience of six or more years in IT consulting, system and application development, design and implementation, business process reengineering, IT transformation, or other related services. Possession of an advanced degree may be substituted for one year of experience. Possession of a professional certification (e.g. PMP, CAPM), other than that used to meet the minimum educational requirements, may also be substituted for one year of experience.

Senior Functional Consultant

Experience of six or more years in IT consulting, system and application development, design and implementation, business process reengineering, IT transformation, or other related services. Possession of an advanced degree may be substituted for one year of experience. Possession of a professional certification, other than that used to meet the minimum educational requirements, may also be substituted for one year of experience.

Functional Consultant

Experience of one or more years in IT consulting, system and application development, design and implementation, business process reengineering, IT transformation, or other related services. Possession of an advanced degree may be substituted for one year of experience. Possession of a professional certification, other than that used to meet the minimum educational requirements, may also be substituted for one year of experience.

Team Leader

Experience of three or more years in IT consulting, system and application development, design and implementation, business process reengineering, IT transformation, or other related services. Possession of an advanced degree may be substituted for one year of experience. Possession of a professional certification (e.g., PMP, CAPM), other than that used to meet the minimum educational requirements, may also be substituted for one year of experience.

Team Member

In second year of experience providing IT consulting, system and application development, design and implementation, business process reengineering, IT transformation, or other related services. Possession of an advanced degree may be substituted for one year of experience. Possession of a professional certification (e.g. CAPM), other than that used to meet the minimum educational requirements, may also be substituted for one year of experience.

Project Analyst

In first year of experience providing IT business consulting, financial management, project governance or other related services. Possession of an advanced degree may be substituted for one year of experience. Possession of a professional certification (e.g. CPA, PMP, or CAPM), other than that used to meet the minimum educational requirements, may also be substituted for one year of experience.

IT Analyst

In first year of experience providing IT systems analysis and business consulting, IT system processes and methodology, systems and application development and implementation or other related services. Possession of an advanced degree may be substituted for one year of experience. Possession of a professional certification other than that used to meet the minimum educational requirements, may also be substituted for one year of experience.

Information Security Team Member

In second year of experience providing information security consulting, penetration testing, vulnerability testing, incident response, forensics, or other related services. Possession of an advanced degree may be substituted for one year of experience. Possession of a professional certification (e.g., CPA, PMP, CGFM, ASA, or FSA), other than that used to meet the minimum educational requirements, may also be substituted for one year of experience.

9. AUTHORIZED USERS

The resulting BPA covers a broad range of IT related tasks, subtasks and activities required to successfully support MCC and its Foreign Affairs Partners. Detailed Statement of Work including deliverables, standards, and performance requirements will be developed for each call order issued by MCC and its Foreign Affairs Partners.

Government Contracting Officers representing MCC and MCC approved Government Contracting Officers from the Foreign Affairs community will be the only users authorized to place orders under this BPA. Any authorized user shall only be allowed to issue an order under this BPA if funds are certified and the BPA awarding office’s Call Order number is assigned. BPA holders shall not accept or perform any purported order that does not contain a Call Order number.

9.ORGANIZATIONAL CONFLICTS OF INTEREST: Current MCC Contractors and Subcontractors Notice Work under a current MCC contract may call for the Contractor to furnish important systems engineering and/or technical direction, including specifications or work statements for systems currently used or to be used in the future by MCC. In accordance with the principles of FAR Subpart 9.5, such CONTRACTORS MAY POSSESS A REAL OR APPARENT CONFLICT OF INTEREST DUE TO THE WIDE RANGING SCOPE OF SERVICES REQUIRED UNDER THIS BIDS SOLICITATION. Such a conflict will preclude an offeror, or subcontractor, from being considered for award of this BPA unless the Contracting Officer makes a written determination that the conflict can and has been mitigated. Prime contract offerors must identify any such conflicts on their behalf, or that of their subcontractors, in their proposal and provide a realistic mitigation plan in order to be considered for award of this BPA. The acceptance or non-acceptance of this plan will be at the sole discretion of the MCC after consultation with its Office of General Counsel.

11. MCC52.204-70 CONTRACTING OFFICER’S TECHNICAL REPRESENTATIVE (COTR) AND/OR PROJECT MONITOR (PM) (FEB 2009)

(a) The Contracting Officer (CO) may designate a Government representative to act as the Contracting Officer's Technical Representative (COTR) to perform functions under the contract such as review and/or inspection and acceptance of supplies, services, including construction, and other functions of a technical nature. The Contracting Officer will provide a written notice of such designation to the COTR and/or PM and the Contractor. The designation letter will set forth the authorities and limitations of the COTR and/or PM under the contract.

(b) Modifications to this contract are effective only if reduced to writing and executed by the CO. The contractor is specifically prohibited from performing any work that is outside the scope of this contract without the approval of the CO. The Contracting Officer cannot authorize the COTR or any other representative to sign documents (i.e., contracts, contract modifications, etc.) that require the signature of the Contracting Officer.

12. MCC52.204-71 SECURITY REQUIREMENTS FOR CONTRACTOR PERSONNEL (MAR 2006)

Contractor employees and/or subcontractor personnel, while on MCC premises, shall be subject to and abide by all safety and security…