Financial Management Services _FMS_

Document Sample
Financial Management Services _FMS_ Powered By Docstoc
					          Financial Management
          Line of Business

1   Migration Planning Guidance
2   (Version 2)

3   Section 2.4 Boilerplate Solicitation Template
4   Introduction
5   This section contains the Boilerplate Solicitation Template which
6   provides a standardized approach for developing a Statement of
7   Objective, including a solicitation outline with proposed boilerplate
8   language and sample text (e.g., recommended evaluation criteria
9   and rating factors).

10                                                 Table of Contents
11    PART I - THE SCHEDULE ..................................................................................................... 6
12    SECTION A - NOTICE TO POTENTIAL OFFERORS ............................................................ 6
13           A.1 Solicitation Acronyms/Glossary ............................................................................... 6
14    SECTION B - SUPPLIES OR SERVICES AND PRICE/COSTS .......................................... 10
15           B.1     Contract Line Items .............................................................................................. 10
17           C.1 Introduction ........................................................................................................... 11
18           C.2 Background .......................................................................................................... 11
19           C.3 Acquisition Strategy .............................................................................................. 11
20           C.4 Scope of Contract ................................................................................................. 11
21           C.5 Compliance With Standards ................................................................................. 12
22           C.6 Project Goals and Objectives ............................................................................... 15
23           C.7 Required Products and Services .......................................................................... 18
24           C.8 Application/Reference Information........................................................................ 22
25           C.9 Assumptions/Constraints ...................................................................................... 22
26           C.10 Concept of Operations .......................................................................................... 23
27           C.11 Functional/Technical Requirements – Financial Management Systems
28                Requirements ........................................................................................................ 23
29           C.12 Performance Management ................................................................................... 34
30    SECTION D - PACKAGING AND MARKING ....................................................................... 36
31    SECTION E - INSPECTION AND ACCEPTANCE ............................................................... 37
32           E.1 Notice Listing Contract Clauses Incorporated by Reference (Inspection and
33               Acceptance) .......................................................................................................... 37
34           E.2     Government Acceptance and Review .................................................................. 37
35           E.3     Exit Criteria ........................................................................................................... 37
36    SECTION F - DELIVERIES OR PERFORMANCE ............................................................... 38
37           F.1 Notice Listing Contract Clauses Incorporated By Reference (Deliveries or
38               Performance) ......................................................................................................... 38
39           F.2     Reports ................................................................................................................. 38


40           F.3     Malfunction/Corrective Action Report ................................................................... 38
41           F.4     Period of Performance .......................................................................................... 39
42           F.5     52.217-8 Option to Extend Services ..................................................................... 39
43           F.6     52.217-9 Option to Extend the Term of the Contract ............................................ 39
44    SECTION G - CONTRACT ADMINISTRATION DATA ........................................................ 40
45           G.1 Invoice Requirements ........................................................................................... 40
46           G.2 Method of Payment .............................................................................................. 41
47           G.3 Contracting Officer’s Technical Representative (COTR) ...................................... 42
48           G.4 Government Property ........................................................................................... 42
49           G.5 Subcontractor Consent ......................................................................................... 43
50           G.6 Agency Small Business Subcontracting Goals ..................................................... 44
51    SECTION H - SPECIAL CONTRACT REQUIREMENTS ..................................................... 45
52           H.1 Waiver of Delivery Schedule ................................................................................ 45
53           H.2 End of Contract Succession Support .................................................................... 45
54           H.3 Contract Phase Out Plan ...................................................................................... 45
55           H.4 Computer Programmers and System Analysts ..................................................... 45
56           H.5 Submittal Data on Personnel ................................................................................ 46
57           H.6 Dissemination of Information ................................................................................ 46
58           H.7 Release of Reports ............................................................................................... 46
59           H.8 Release of News Information ............................................................................... 46
60           H.9 Software Rights .................................................................................................... 46
61           H.10 Royalty Free License ............................................................................................ 47
62           H.11 Type of Service..................................................................................................... 47
63           H.12 Citizenship ............................................................................................................ 47
64           H.13 Employee Relationship ......................................................................................... 47
65           H.14 Inapplicability of Employee Benefits ..................................................................... 48
66           H.15 Contractor Supervision ......................................................................................... 48
67           H.16 All Items to Become Property of the Government................................................. 48


68           H.17 Contractor Employee Suitability and Security Requirements ............................... 48
69    PART II - CONTRACT CLAUSES ........................................................................................ 53
70    SECTION I - CONTRACT CLAUSES ................................................................................... 53
71           I.1    Notice Listing Contract Clauses Incorporated by Reference (Contract
72                  Clauses) ................................................................................................................ 53
73           I.2    Key Personnel ...................................................................................................... 58
74           I.3    Wage Determinations 05-2103 (Rev. 4), Washington, DC Metropolitan Area ....... 58
76    SECTION J - LIST OF ATTACHMENTS .............................................................................. 59
77           J.1    FM Due Diligence Cover Letter and Checklist ...................................................... 59
78    PART IV - REPRESENTATIONS AND INSTRUCTIONS ..................................................... 60
80       STATEMENTS OF OFFEROR ..................................................................................... 60
81           K.1    52.204-8 Annual Representations and Certifications (JAN 2006)......................... 60
82           K.2    Signature Block .................................................................................................... 61
84           L.1 Notice Listing Solicitation Provisions Incorporated By Reference
85               (Instructions, Conditions, and Notices to Offerors) ................................................ 62
86           L.2    52.216-1 Type of Contract (APR 1984) ................................................................ 62
87           L.3    52.233-2 Service of Protest (SEP 2006) ............................................................... 62
88           L.4 52.252-1 Solicitation Provisions Incorporated By Reference (FEB 1998).............. 63
89           L.5    Special Notice to Offerors ..................................................................................... 63
90           L.6    Instructions for the Preparation of Proposals ........................................................ 64
91           L.7    Solicitation Response Requirements .................................................................... 66
92           L.8    Proposal Volumes Requirements ......................................................................... 82
93           L.9    Number of Awards ................................................................................................ 93
94           L.10 All or Nothing Proposals ....................................................................................... 93
95           L.11 Questions Regarding This Solicitation .................................................................. 93
96           L.12 Contract Schedule ................................................................................................ 94
97    SECTION M - EVALUATION FACTORS FOR AWARD .................................................... 100


 98           M.1 Notice Listing Solicitation Provisions Incorporated by Reference (Evaluation
 99               Factors for Award) ............................................................................................... 100
100           M.2 Method of Award (Best Value) ............................................................................ 100
101           M.3 Evaluation Factors and Ratings .......................................................................... 101



103           PART I - THE SCHEDULE


105   A.1           Solicitation Acronyms/Glossary
106   The following glossary/acronym listing is hereby incorporated into the
107   solicitation:
108   Glossary/Acronyms
109   ACH Automated Clearing House
110   ANSI/EIA American National Standards Institute/Electronic Industries Association
111   ATO Authority to Operate
112   BCWP Budgeted Cost of Work Performed
113   BPR Business Process Re-engineering
114   C&A Certification and accreditation
115   CAP Contractor-acquired-Government owned property
116   CCR Central Contractor Registration
117   CDRL Contract Data Requirements List
118   CFR Code of Federal Regulations
119   CFSR Core Financial System Requirements
120   CGAC Common Government-wide Accounting Classifications
121   CGFM Certified Government Financial Manager
122   CIA Certified Internal Auditor
123   CISA Certified Information Systems Auditor
124   CISM Certified Information Security Manager
125   CMM-I Capability Maturity Model - Integrated
126   CO Contracting Officer
127   COOP Continuity of Operations Plan
128   COR Contracting Officer’s Representative
129   COTR Contracting Officer’s Technical Representative
130   COTS Commercial Off-the-Shelf


131   CPA Certified Public Accountant
132   CPR Contract Performance Report
133   CWBS Consolidated Work Breakdown Structure
134   CY Calendar Year
135   DAA Designated Approving Authority
136   DDC Duel Diligence Checklist
137   DRP Disaster Recovery Plan
138   DUNS Data Universal Numbering System (DUNS) Number
139   EDI Electronic Data Interchange
140   EIT Electronic and Information Technology
141   ETS e-Government Travel System
142   EVMS Earned Value Management System
143   FAR Federal Acquisition Regulation
144   FBWT Fund Balance with Treasury
145   FEA Federal Enterprise Architecture
146   FEDLINE Fedline Communications System
147   FFMIA Federal Financial Management Improvement Act
148   FFP Firm Fixed Price
149   FIPS PUB Federal Information Processing Standards Publication
150   FISMA Federal Information Security Management Act
151   FM Financial Management
152   FMLOB Financial Management Line of Business
153   FOIA Freedom of Information Act
154   FPA Federal Privacy Act
155   FSIO Financial Systems Integration Office
156   FY Fiscal Year
157   GAO Government Accountability Office
158   GFE Good Faith Estimate


159   GL General Ledger
160   GPRA Government Performance and Results Act
161   GSA General Services Administration
162   IAG Investment Advisory Group
163   IBR Integrated Baseline Review
164   IDIQ Indefinite Delivery/Indefinite Quantity
165   IGCE Independent Government Cost Estimate
166   IMP Integrated Master Plan
167   IMS Integrated Master Schedule
168   IT Information Technology
169   LOE Level of Effort
170   LPMB Linking Performance Measurement to Budget
171   IV&V Independent Verification and Validation
172   NAICS North American Industrial Classification System
173   NIST National Institute of Standards and Technology
174   OCD Operational Capabilities Demonstration
175   OCM Organizational Change Management
176   OERPS Office of Executive Resources and Personnel Security
177   O&M Operations and Maintenance
178   OMB Office of Management and Budget
179   OPM Office of Personnel Management
180   PAT Product Acceptance Test
181   PIA Privacy Impact Assessment
182   PMO Program Management Office
183   POC Point of Contact
184   PMP Project Management Professional
185   PWS Performance Work Statement
186   QA Quality Assurance


187   QAP Quality Assurance Plan
188   QASP Quality Assurance Surveillance Plan
189   RFP Request for Proposal
190   RFQ Request for Quotations
191   SC&A Security Certification & Accreditation
192   SCAMPI Standard CMMI Appraisal Method for Processing Improvement
193   SEI CMMI Software Engineering Institute Capability Maturity Model - Integrated
194   SLA Service Level Agreement
195   SME Subject Matter Expert
196   SOA Service Oriented Architecture
197   SOO Statement of Objectives
198   SSA Source Selection Authority
199   SSB Source Selection Board
200   SSEP Source Selection Evaluation Plan
201   SSP Shared Service Provider
202   T&M Time and Materials
203   TIN Tax Identification Number
204   TPOC Technical Point of Contact
205   USSGL United States Standard General Ledger
206   WBS Work Breakdown Schedule
207   WD Wage Determinations
208   WDOL Wage Determinations OnLine



211   B.1           Contract Line Items
212   [Issuing Agency] will issue a contract using a combination of firm-fixed priced and time
213   and materials where appropriate for the requirements sought by this request for
214   proposal. This contract will establish the total price of the work to be performed, and the
215   price(s) for each contract line item(s) contained in the contract and will be executed in
216   accordance with any pricing arrangement prescribed in the Federal Acquisition
217   Regulation (FAR) that is appropriate to perform the subject work.



220   C.1          Introduction
221   [Issuing Agency] plans to migrate to a new core financial management system and to
222   host the new system at an Office of Management and Budget (OMB)-designated
223   Federal Shared Service Provider (SSP) or with a commercial provider.
224   This initiative will be conducted in compliance with all applicable Federal financial
225   systems regulations and guidance. Of particular applicability is the Financial Systems
226   Integration Office (FSIO) guidance.
227   This project will focus on the replacement of those processes and systems that are
228   considered a consolidated ―core‖ based on FSIO standards.

229   C.2          Background
230   To address challenges and opportunities in the rapidly changing Federal financial
231   management and technology environment, the FSIO has developed Core Financial
232   System Requirements (CFSR) to standardize the Federal financial management
233   process.

234   C.3          Acquisition Strategy
235   [Issuing Agency] reserves the right to select a single contractor, or a combination of
236   contractors that will provide the Agency with the best resources for successfully
237   deploying CFSR. FSIO has determined that a Federal agency financial management
238   solution will require the following core services:
239           Hosting Services
240           Financial Management Application Management Services
241           Implementation/Integration Services (Including Business Process Re-engineer
242              (BPR) and Change Management)
243           Business Services / Transaction Processing Services

244   C.3.1        Shared Services Providers
245   In accordance with OMB guidance, [Issuing Agency] is requesting proposals from
246   Financial Management Line of Business (FMLoB) SSPs as well as qualified commercial
247   providers for services requested. All proposals will be evaluated in accordance with the
248   evaluation factors for award in Section M of this solicitation with a best value
249   determination approach used when making the final selection.

250   C.4          Scope of Contract
251   The Contractor must furnish the following:
252      [X] Hosting service


253      [X] Application management services
254      [X] Implementation/integration services (Including Business Process Re-engineer
255      (BPR) and Change Management)
256      [X] Full Business services/Transaction processing services
257   The above item(s) shall be supplied/performed in accordance with the Statement of
258   Objectives (SOO) and with the terms and conditions of the contract.

259   C.5          Compliance With Standards
260   All equipment and/or software acquired under this acquisition must conform to
261   specifications contained in the applicable Federal, industry, and national standards that
262   address financial management systems. Below is a list of government-wide laws,
263   regulations, guidelines and standards pertaining to Federal Agency financial
264   management:

265   C.5.1        U.S. Code
266   5 U.S.C. § 552 contains provisions of the Freedom of Information Act.
267   31 U.S.C. § 1301(a) (the ―Purpose Statute‖) requires that monies be expended only for
268   the purposes for which appropriations were made.
269   31 U.S.C. §§ 1341, 1342, 1349–51, and 1511–19 (jointly referred to as the ―Anti-
270   deficiency Act‖) prohibit obligating more money than an agency has or before it gets the
271   money, accepting voluntary services or monies not specifically allowed by law, and
272   obligating more money than has been appropriated or allotted in a time period.
273   31 U.S.C. § 1501 (the ―Recording Statute‖) requires that an obligation be recorded
274   when, and only when, it is supported by written evidence of a binding agreement (an
275   offer and its acceptance) for goods or services for a purpose authorized in the
276   appropriation.
277   31 U.S.C. § 1502 (a) (the ―Bona Fide Needs Statute‖) requires that obligations against
278   an appropriation be limited to a specific time period and that obligations be charged to
279   the appropriation in force when the obligation is made.
280   31 U.S.C. §§1551–1557 (Closed Accounts subchapter) contains the M-year legislation
281   which requires that all Federal agencies close fixed-year appropriation accounts and
282   cancel any remaining balances by September 30th of the 5th year after the period of
283   availability began.
284   31 U.S.C. § 3302 (b) (the ―Miscellaneous Receipts (Deposit) Statute‖) requires that,
285   except for trust funds and revolving funds, collected monies from any source be
286   deposited in the Treasury as soon as practicable without deduction for any charge or
287   claim.
288   31 U.S.C. § 3512 requires the head of each executive agency to establish and maintain
289   systems of accounting and internal control designed to provide effective control over,
290   and accountability for, all assets for which the agency is responsible.


291   44 U.S.C. § 3101 addresses records management within Federal agencies.
292   5 CFR 1315 is the codification of former OMB Circular A-125, Prompt Payment.

293   C.5.2        Federal Legislation
294   Accountability of Tax Dollars Act of 2002 (ATDA)
295   Cash Management Improvement Act of 1990 (CMIA) (Pub. L. No. 101-453), extended
296   by the Cash Management Improvement Act Amendments of 1992 (Pub. L. No. 102-589)
297   Chief Financial Officers Act of 1990 (CFO Act) (Pub. L. No. 101-576)
298   Clinger-Cohen Act of 1996 (Information Technology Management Reform Act, Division
299   E of Pub. L. No. 104-106)
300   Computer Security Act of 1987 (Pub. L. No. 100-235)
301   Debt Collection Improvement Act of 1996 (Pub. L. No. 104-134)
302   Economy Act (31 U.S.C. 1535)
303   Federal Financial Management Improvement Act of 1996 (FFMIA) (Pub. L. No. 104-
304   208)
305   Federal Managers’ Financial Integrity Act of 1982 (Pub. L. No. 97-255) (FMFIA)
306   Federal Records Act of 1950, as amended (Records Management by Federal Agencies,
307   44 U.S.C. § 3101 et seq.)
308   Freedom of Information Act and Amendments of 1974 (Pub. L. No. 93-502) (5 U.S.C. §
309   552)
310   Government Management Reform Act of 1994 (GMRA) (Pub. L. No. 103-356)
311   Government Paperwork Elimination Act of 1998 (Pub. L. No. 105-277)
312   Government Performance and Results Act of 1993 (GPRA) (Pub. L. No. 103-62)
313   Improper Payments Information Act of 2002 (IPIA)
314   Internal Revenue Service Restructuring and Reform Act of 1998 (IRS RRA)
315   (Pub. L. No. 105-206)
316   Omnibus Reconciliation Act of 1993 (Pub. L. No. 103-66)
317   Paperwork Reduction Reauthorization Act of 1986 (Pub. L. No. 104-13)
318   Prompt Payment Act of 1982 (Pub. L. No. 97-177) and Amendments of 1996 (Pub. L.
319   No. 100-496)
320   Rehabilitation Act Amendments of 1998 (Workforce Investment Act) (Pub. L. No. 106-
321   246)
322   Reports Consolidation Act of 2000
323   Sarbanes-Oxley Act of 2002 (Pub. L. No. 107-204)
324   Tax Increase Prevention and Reconciliation Act of 2005 (TIPRA)


327   C.5.3       Treasury Financial Manual
328   I TFM-2-3100, Instructions for Disbursing Officers’ Reports
329   I TFM-2-3300, Statement of Transactions (FMS 224) Reporting by Agencies for which
330   the Treasury Disburses
331   I TFM-2-4100, Debt Management Reports
332   I TFM-2-4700, Agency Reporting Requirements for the Financial Report of the United
333   States Government
334   I TFM-4-2000, Payment Issue Disbursing Procedures
335   I TFM-4-700, Cancellations, Deposits, and Claims for Checks Drawn on the U.S.
336   Treasury
337   I TFM-6-3100, Certifying Payments and Recording Corresponding Intragovernmental
338   Receivables in the Federal Government’s Judgment Fund
339   I TFM-6-4000, Intra-Governmental Payment and Collection (IPAC) System
340   I TFM-6-5000, Administrative Accounting Systems Requirements in Support of the Debt
341   Collection Improvement Act of 1996
342   I TFM-6-5100, Recovering Unclaimed Federal Financial Assets
343   I TFM-6-8040, Disbursements
344   I TFM-6-8500, Cash Forecasting Requirements
345   TFM Supplement No. S2 08-03, U.S. Government Standard General Ledger
346   TFM Supplement for Treasury Report on Receivables and Debt Collection Activities

347   C.5.4       Office of Management and Budget (OMB)
348   OMB Circular A-11, Preparation, Submission, and Execution of the Budget
349   OMB Circular A-25, User Charges
350   OMB Circular A-123, Management’s Responsibility for Internal Control
351   OMB Circular A-127, Financial Management Systems
352   OMB Circular A-130, Management of Federal Information Resources
353   OMB Circular A-134, Financial Accounting Principles and Standards
354   OMB Circular A-136, Financial Reporting Requirements

355   C.5.5       Statements of Federal Financial Accounting and Concepts
356   SFFAC 1, Objectives of Federal Financial Reporting
357   SFFAC 2, Entity and Display
358   SFFAS 1, Accounting for Selected Assets and Liabilities
359   SSFAS 4, Managerial Cost Accounting Concepts and Standards
360   SSFAS 5, Accounting for Liabilities of the Federal Government
361   SFFAS 7, Accounting for Revenue and Other Financing Sources


362   C.5.6        Federal Financial Management System Requirements
363   Framework for Federal Financial Management Systems, April 2004
364   Core Financial System Requirements, January 2006
365   Acquisition / Financial Systems Interface Requirements, June 2002
366   Benefit System Requirements, September 2001
367   Direct Loan System Requirements, June 1999
368   Grant Financial System Requirements, June 2000
369   Guaranteed Loan System Requirements, March 2000
370   Human Resources and Payroll System Requirements, April 1999
371   Inventory, Supplies, and Materials System Requirements, August 2003
372   Managerial Cost Accounting Implementation Guide, February 1998
373   Managerial Cost Accounting System Requirements, February 1998
374   Property Management System Requirements, October 2000
375   Revenue System Requirements Document, January 2003
376   Seized Property and Forfeited Assets System Requirements, December 1999
377   Travel System Requirements, July 1999

378   C.5.7        Financial Management Lines of Business Standards
379   Common Government-wide Accounting Classification Structure, Version 1.0, July 2007
380   Standard Business Processes, July 2008 – includes Funds Management, Payment
381   Management, and Receivables Management processes

382   C.5.8        Other Federal Financial Standards, Guidelines and Regulations
383   Electronic and Information Technology Accessibility Standards (issued by the
384   Architectural and Transportation Barriers Compliance Board) as required by Section
385   508 of the Rehabilitation Act) (
386   Federal regulations established by the National Archives and Records Administration
387   (
388   Federal regulations issued by the National Institute of Standards and Technology
389   (
390   Rules related to payment formats issued by The Electronic Payments Association (also
391   called NACHA) (

392   C.6          Project Goals and Objectives
393   The primary objective of this acquisition is to improve financial management
394   performance by efficiently providing Agencies with core financial system requirements
395   that both complies with federal accounting and systems standards and provides
396   maximum support to the Agency mission. To meet this objective, FMLOB targets the
397   replacement of agency financial systems and the replacement of the legacy financial


398   and program ledgers used in the Agency programs. Some Agencies have outdated
399   mainframe technology and is no longer supported by the vendor for ongoing compliance
400   with federal financial management requirements, thus posing unacceptable risks to the
401   Agency. Replacing core financial management system and program ledgers, with a
402   modern, Web-accessible core financial management system is also expected to
403   eliminate the need to operate and maintain many of Agency legacy feeder systems as
404   well as the data warehouses currently required to produce timely external financial
405   statements.
406   This acquisition is designed to meet specific goals established by [Issuing Agency] and
407   has the Replacement of the Agency financial management system following key
408   attributes:
409          Interface and when necessary Integration with existing and emerging
410           eGovernment initiatives such as eGovernment Travel Services (ETS), ePayroll,
411 , eLoans, current corporate solutions for which financial results must
412           be reflected in the budgetary and general ledger accounts of the Agency (e.g.,
413           asset management and procurement), and program-specific systems that are
414           subsidiary to the general ledger (e.g., programmatic loan systems).
415          Integrated performance management and budgeting, allowing Agencies to meet
416           the Federal Government objectives including the Government and Performance
417           Results Act (GPRA) requirements, and CFO Act.
418          Compliance with the Federal Financial Management Improvement Act (FFMIA),
419           including federal financial management system requirements, applicable federal
420           accounting standards, and U.S. Standard General Ledger (USSGL) at the
421           transaction level.
422          [Issuing Agency]-identified interface requirements.

423   The work to be performed under this acquisition shall be executed with a performance-
424   based approach in order to provide the most cost effective and technically sound
425   solution. The [issuing agency] shall rely on the Offeror’s expertise to streamline the
426   process of completing the acquisition milestones. The Offeror shall plan and develop a
427   solution to implement a [issuing agency] financial management system that meets the
428   objectives and anticipated outcomes.
429   The FM Provider shall achieve the following objectives in the performance of the
430   resultant contract:
431            An integrated core financial management system that meets FSIO and [Issuing
432               Agency] specific requirements as well as the financial management system
433               requirements set forth in Section 7 of OMB Circular A-127;
434            Improved financial processes that complement financial management systems
435               operational efficiency and effectiveness;
436            Documentation that includes, but is not limited to, software configuration,
437               technical specifications, system interface descriptions, and user manuals;


438            Training and user support for the users of the new system that is based on the
439               level, responsibility and roles of individual users;
440            System hosting and administration and application management services;
441            Improved customer information and relationship management capabilities; and
442            Enhanced tools to support executive and managerial decision-making
443               responsibilities.

444   This acquisition will focus on the replacement of those processes and systems that are
445   considered a consolidated core based on [issuing agency] financial operations and
446   FSIO standards. Those processes that are included in this consolidated core are:
447            Budget Execution – Includes distributing funds, controlling funds, and fund
448               status reporting.
449            Payment Management – Includes payee information maintenance, accounts
450               payable, invoice management, disbursing, and payment follow-up.
451            Receivable Management – Includes customer information maintenance,
452               receivables and billing, debt management, collections and offsets.
453            Cost Management – Includes cost setup and accumulation, cost distribution,
454               and cost reporting.
455            General Ledger Management – Includes General Ledger (GL) account
456               definition, transaction definition, GL analysis and reconciliation, accounting
457               period maintenance and closing, and financial reporting.
458            Fund Balance with Treasury Management Function - The Fund Balance with
459               Treasury (FBWT) represents the money an agency can spend on future
460               authorized transactions. Agencies record transactions that increase and
461               decrease their FBWT to USSGL account 1010 in their GL. Appropriation
462               warrants, non-expenditure transfers, collections, and disbursements are
463               some of the transactions that impact an agency’s FBWT.

464   [Issuing agency] is seeking the services of an OMB designated Federal Shared Service
465   Provider (SSP) or a commercial provider in the areas of Hosting and Administration,
466   and Application Management Services to provide:
467          Functional integration, which may require fewer feeder systems
468          Usability of web-based user interfaces
469          Access to up-to-date data and reports
470          More powerful and flexible query and reporting capabilities
471          Automated electronic workflow for routing and approvals
472          Accountability and ability to audit transactions
473          Process efficiency and effectiveness
474          Increased internal controls


475          Increased speed and transparency in external reporting
476          Error messaging for issue resolution
477          Compliant and vendor-supported commercial off-the-shelf software

478   C.7           Required Products and Services
479   This proposed solution shall permit the [issuing agency] to acquire the life cycle system
480   integration necessary to deploy the new core financial management system in a hosted
481   environment. The major components associated with this acquisition are:
482            Hosting Services
483            Application Management Services
484            Implementation/Integration Services (Including Business Process Re-engineer
485                (BPR) and Change Management
486            Full Business Services/Transaction Processing Services

487   It is the [issuing agency’s] objective to make full use of the Contractor’s expertise and
488   experience in developing a Performance Work Statement (PWS) to support objectives
489   outlined in document.
490   The following sections provide an overview of the work that will be required under this
491   solicitation. The information is intended to highlight specific agency expectations and
492   constraints.

493   C.7.1         Hosting Services
494   Hosting and Administration involves providing the information technology (IT)
495   infrastructure (facilities and infrastructure software) that serve as the foundation for
496   running business software applications and the services to maintain that infrastructure.
497   The contractor will provide all the necessary services to support and host the solution,
498   consistent with the goals and objectives of this SOO. This includes both infrastructure
499   hosting and application functional and technical support. The contractor is expected to
500   provide a complete hosting solution that includes all the services necessary to deliver
501   their proposed approach from project initiation through system cut-over and all post-
502   deployment production operations.
503   The contractor will perform all operations and maintenance (O&M) activities for the new
504   financial system including the security of the deployed system infrastructure. The
505   contractor will also be responsible for ensuring that a proper Continuity of Operations
506   plan (COOP) is in place. This includes, but is not limited to, maintaining a mirrored
507   image of the [issuing agency’s] financial system at a specified disaster recovery site.
508   The contractor may also be responsible for providing all software, hardware and
509   infrastructure needed to host the proposed financial management system.


510   The contractor shall be responsible for providing a change control process that enforces
511   consistent configuration management across all increments, instances, and upgrades of
512   the new financial systems.

513   C.7.2          Application Management Services
514   Application Management Services involves providing the software and services for
515   running and managing access to financial management software and the feeder
516   systems that provide data to the financial management software. It is anticipated that
517   the solution shall consist of the use of one or more commercially available products with
518   limited or no custom development. Therefore, instead of software development, the
519   Contractor shall be required to integrate one or more operational components and
520   configure the integrated solution to operate within the hosted environment.
521   The foundation of the proposed financial system solution must be a FSIO-certified core
522   financial management system that is compliant with OMB Circular A-127, Financial
523   Management Systems.

524   C.7.3          Implementation/Integration Services (Business Process
525                  Reengineering and Change Management
526   The deployment activities shall include, but are not limited to, installation, testing, cut-
527   over, and post-deployment support. The Contractor’s proposed deployment approach
528   and schedule should demonstrate coordination with the data conversion and training
529   activities.
530   The Contractor shall provide all necessary services for the successful integration of a
531   FSIO-compliant core financial system, which shall include, at a minimum, the services
532   described in the following sections.

533   C.7.3.1        Implementation Approach
534   The current timeline for the FM investment calls for the implementation effort to begin
535   [enter date] and for the new financial system to achieve full operational capability in a
536   hosted environment by October 1, 20XX. Full operational capability is defined as the
537   FM Provider becoming [issuing agency’s] financial system of record, with all core
538   financial transactions, batch or on-line, being done at the FM Provider location.

539   C.7.3.2        Requirements Analysis and Definition

540   The [issuing agency] agency has defined an initial set of functional and technical
541   requirements. The Contractor shall expand upon these requirements to develop data,
542   operational, and interface requirements that are specific to the new FSIO compliant
543   financial system. At a minimum, this will entail gathering requirements that encompass
544   the following areas:
545             Data formats (e.g., chart of accounts)
546             User categories (e.g., roles, responsibilities and security profiles)


547             Operational standards and procedures
548             Security standards
549             Reports
551   See Section C.11 Functional/Technical Requirements – Financial Management System
552   Requirements for full core financial management mandatory requirements.

553   C.7.3.3       System Configuration

554   It is anticipated that the Contractor shall provide multiple configured environments to
555   include, at a minimum, development, test, training, production, and disaster recovery
556   environments. The Contractor is responsible for providing all software, hardware and
557   infrastructure needed for these environments.
558   Systems engineering processes that are certified by the Software Engineering Institute
559   Capability Maturity Model – Integrated (SEI CMMI) at level three (Level III) or higher or
560   similar certifications are not required but are a plus.

561   C.7.3.4       Testing

562   Testing approval shall be obtained through interim conference room pilots and user
563   acceptance testing by stakeholders. At interim points during the configuration process,
564   stakeholders will participate in pilots of subsets of the configured system to ensure that
565   the system is meeting the defined functional, technical, and interface requirements.

566   C.7.3.5       Data Conversion

567   The Contractor shall conduct all activities required to successfully convert and migrate
568   the cleaned data from its current location(s) and format(s) to the new physical
569   location(s) and format(s) defined by the system solution prior to deployment. At a
570   minimum, data conversion must be performed to include all open documents and
571   balances, and must reconcile to the balances of the source of the input data.

572   C.7.3.6        Interface Development

573   Each Agency has a variety of interfaces from departmental and agency-specific legacy
574   systems, which must be carried forward with the new financial system. The Contractor
575   shall focus, during implementation, on the development of corporate legacy systems’
576   interfaces to the new financial system. Any of these system interfaces may require
577   financial data warehouses.
578   The Contractor shall develop and deploy interfaces for Agency legacy systems, in
579   coordination with the legacy system owners and the implementation schedules for the
580   FM system. Each interface development effort should be driven by the existing design,
581   but the Contractor is encouraged to suggest enhancements as necessary. The
582   Contractor must demonstrate past experience in implementing multiple interfaces with
583   heterogeneous technologies – such as, real-time exchanges using Extensible Markup


584   Language (XML) messaging middleware, flat file upload and scheduled batch
585   transactions.
586   The Contractor shall provide proof of prior implementations of interfaces using
587   recognized life cycle management protocols. Any proposed approach must clearly
588   identify stages for design, build, unit testing, integration testing, quality assurance
589   testing, and user acceptance testing. CMM-I or equivalent certification at level III or
590   greater is required. As with system configuration, each interface shall be subject to
591   production readiness review, Agency-conducted end-to-end QA testing, and user
592   acceptance testing before it can be deployed.
593   The Contractor shall follow ISO International Standards Organization and the American
594   National Standards Institute (ANSI) procedures for user interface development.

595   C.7.3.7       System Training

596   The Contractor will be responsible for developing a system training plan, developing
597   system training materials, and delivering the system training. The Contractor’s
598   approach must take into consideration the number of Agency employees using the
599   financial management system and their geographical location throughout the United
600   States. The training approach should be tailored to multiple audiences (e.g., managers,
601   query users, intermittent users, or experienced users). Also, training delivery should
602   reflect multiple delivery approaches to include web-based, train-the-trainer and
603   classroom delivery. The training schedule must be tied to the agency deployment
604   schedule.

605   C.7.3.8       Documentation

606   The Contractor shall clearly and thoroughly document the financial management
607   systems, interfaces and processing instructions associated with the new solution. This
608   documentation shall include, but not be limited to, software design documents, user
609   manuals, and operating procedures, and shall be provided in both hardcopy and
610   electronic format. A documentation maintenance plan shall also be developed to
611   ensure that these documents are kept up-to-date and readily available for examination,
612   and back versions are kept.

613   C.7.3.9       Business Process Re-engineering, Change Management, and Communications

614   The contractor shall implement a FSIO certified software package by performing
615   business process reengineering activities (BPR) to maximize effectiveness of human
616   capital, process and information technology investments. The contractor should adhere
617   to standard FSIO-compliant processes, and changes may need to occur within the
618   agency business processes to meet this FSIO standardization. The majority of the
619   logical-level business process redesign occurs during the fit-gap portion of the
620   requirements phase. The contractor will need to support BPR throughout the project
621   lifecycle to ensure effective transitions to the new standard business processes.


622   A change management plan is required and would include a communications plan to
623   keep the [issuing agency] informed of the changes as they are planned and as they are
624   achieved by the utilization of progress reports. Another element the change
625   management plan is user training to ensure the system being acquired will be useable
626   and familiar to the users upon implementation.
627   The contractor will need to provide how they plan to fulfill the requirements, either as
628   part of the primary contract, through a subcontract or partner, or a willingness to
629   cooperatively interface with a separately acquired contractor of the agency’s choice.

630   C.7.4         Business Services/Transaction Processing Services
631   FM Providers delivers business services, including functions such as payment
632   management including processing of invoices and payments and receivables
633   processing including billings and collection activities. Agency provides complete details
634   of service support expectations.

635   C.8           Application/Reference Information

636   C.8.1         Federal Financial Management System Requirements
637   Framework for Federal Financial Management Systems, January 1995, April 2004
638   Core Financial System Requirements, February 1999, November 2001, January 2006
639   Core Financial System Requirements, November 2001
640   Acquisition / Financial Systems Interface Requirements, June 2002
641   Benefit System Requirements, September 2001
642   Direct Loan System Requirements, June 1999
643   Grant Financial System Requirements, June 2000
644   Guaranteed Loan System Requirements, March 2000
645   Human Resources and Payroll System Requirements, April 1999
646   Inventory, Supplies, and Materials System Requirements, August 2003
647   Managerial Cost Accounting Implementation Guide, February 1998
648   Managerial Cost Accounting System Requirements, February 1998
649   Property Management System Requirements, October 2000
650   Revenue System Requirements Document, January 2003
651   Seized Property and Forfeited Assets System Requirements, December 1999
652   Travel System Requirements, July 1999

653   C.9           Assumptions/Constraints
654   Agency will determine requirements.


656   C.10           Concept of Operations
657   Agency will determine requirements.

658   C.11           Functional/Technical Requirements – Financial Management
659                  Systems Requirements

660   C.11.1         Mandatory Requirements
661   Offerors shall have the ability to provide a web-based full core financial management
662   solution that meets the following mandatory requirements.

663   C.11.2         Qualified Software

664   Full Core and Qualified Test
665   All software used shall be certified software based on the full core and all incremental
666   tests. A listing of certified software is located at the following:


668   C.11.2.1       Core Financial Systems Requirements

669   Core financial systems requirements are detailed at the following:

671   Offerors shall have the capability to fulfill all tested core financial systems requirements
672   as indicated in the most recent Tested Requirements Matrix located at the following:
674   Agencies will identify which of the untested core financial systems requirements that
675   must be satisfied in proposed solutions by including those requirements in the agency
676   specific requirements.

677   C.11.2.2       Data Recovery

678   Offerors shall provide sufficient data recovery features to assure the recovery of all data
679   in the event of any hardware or software failure. These features may include the use of
680   a combination of roll-back/roll-forward, checkpoint/restart, journalizing, and other
681   techniques to assure the availability of accurate, consistent data in the database.
682   The Offeror shall demonstrate the ability to successfully recover from a backup.

683   C.11.2.3       Data Management
684           The proposed software shall support on-line or ad-hoc queries.


685          If the proposed solution utilizes multiple database technology, all
686           databases must reconcile to the on-line system prior to the start of the
687           next working day.
688          Multiple users of the proposed system shall be able to read and write each
689           table, or file, with changes to the table, or file, being made only after a
690           user's transaction successfully completes, and other users shall be
691           allowed to concurrently read/update other table/file entries during the
692           update.
693          The proposed system shall be implemented with an active data dictionary
694           that supports all operations of the system and which is also available to
695           Government staff to support changes to the system.
696          The proposed system shall provide an integrated report writer for end user
697           that gives them the capability to:
698          Create and generate reports;
699          Save report specifications.

700   C.11.2.4       Systems Operations
701          The proposed system shall allow any end-user operation to be performed
702           either through a batch submission or through on-line, interactive
703           submission.
704          The proposed system shall allow Government management and staff to
705           execute any module, query, or report -- for which they have the proper
706           security permissions -- in an interactive mode from their desk top, with the
707           results being returned either to their desk top system or to their local
708           printer.
709          The proposed system shall provide for the automatic distribution of
710           specified reports to the users' work stations and/or printers (local), and the
711           users shall also be provided the ability to restrict the printing of specific
712           reports at their location.
713          The proposed system shall allow default values for on-line activities to be
714           set on a user basis such that, regardless of the physical device from which
715           the user accesses the system, it shall appear as the user's own work
716           station (functionality should not be tied to hardware/device, the capability
717           should be in the software vendor's package offering).
718          The proposed system shall provide a common automated interface to
719           facilitate the exporting and importing of detailed transaction data into the
720           applications and which, at a minimum, shall:
721          Support bulk data entry, to and from other Government systems, these
722           bulk data entry shall pass through standard system edits so as to assure
723           the integrity of the data, and
724          Support the export of data to desk top systems via output files.
725          All application software that comprises the proposed system shall provide
726           full on-line, interactive capability at user work stations.


727          The proposed system shall provide automated work flow management by
728           routing information to users, notifying users of pending actions, and
729           provide a mechanism for managing suspense files to assure all actions
730           are completed in a timely manner.
731          The proposed system shall allow the user to run reports and/or queries in
732           an on-line, interactive mode that spans fiscal years; the only system
733           limitation shall be that the data for each of the required fiscal years be on-
734           line at the time that the query or report is requested. The proposed
735           system shall allow agencies to control and monitor system resources
736           utilized by online reporting.
737          The proposed system shall maintain and report a history of all changes to
738           each table, and of all transactions, sufficient to allow the roll-back of the
739           system to any point in time, the recovery of any transactions and the
740           subsequent roll-forward of the system; and the proposed system shall
741           provide a roll-back/roll-forward capability on a table-by-table, or file-by-file,
742           basis and any tables or files not directly impacted by the roll-back/roll-
743           forward operation shall remain available to the users throughout the
744           recovery operation.
745          The proposed system shall maintain an audit trail of all detailed
746           transactions identified by individual user.
747          The proposed system shall provide the capability to utilize/interface with
748           the following technologies:
749          Electronic Data Interchange (EDI).
750                o Electronic signature;
751                o Imaging and storage of source documents.
752          The proposed system shall provide the capability to support the
753           Government-wide mandate for Electronic Commerce/EDI.

754   C.      System Operating Characteristics

755   The proposed system shall have the following design/operating characteristics:
756          Web operations
757          Decentralized operations within a given Government agency
758          Ad-hoc query capabilities
759          Secure communications
760          Be web-accessible and provide real-time responses.
761          Be an integrated, modular system which is easily operated and managed
762           with minimal manual intervention.
763          Be able to interface readily with other Government systems -- i.e., by
764           accepting/exporting properly formatted data.
765          Be supported by: (1) a comprehensive glossary of data fields used within
766           the system, (2) a comprehensive, current technical user guide(s), and (3)
767           an equally comprehensive, current functional guide(s).


768          Data identified within the comprehensive glossaries shall be available for
769           on-line and ad-hoc queries.

770   C.11.2.5      Management Applications

771   In the area of general management applications, the proposed system shall meet the
772   following requirements:
773          Provide for fully automated data reconciliation between: (1) modules and
774           (2) control and subsidiary ledgers. The Government desires that all
775           modules are fully integrated and that the supporting ledgers are balanced
776           and internally consistent without any manual intervention. This includes,
777           but is not limited to, instances where transactions are rolled backward in
778           time and then rolled forward.
779          Support data gathering and reporting, and automated internal Government
780           Agency reporting, at the point of origin.
781          Provide automated management to support distribution of the database
782           and decentralized processing at multiple locations.
783          Provide an ad hoc query capability which allows downloading of results to
784           a desk top computer.

785   C.11.2.6      User Orientation

786   To foster user acceptance Agency-wide, the proposed system shall:
787          Provide users with an integrated menu-driven approach to system access
788           and query activities.
789          Provide users with query capability that uses English language commands
790           to structure queries. (Features at least both expert and novice modes
791           of system operations.)

792   C.11.2.7      Data Handling Requirements

793   The proposed system shall have the following general data handling characteristics and
794   capabilities:
795          Use a standard set of data elements in a common data dictionary, along
796           with the use of common terminology for all system components including
797           reports.
798          Minimize redundant data entry.
799          Accommodate manual entry and batch processing of data using identical
800           validation rules.
801          Support the downloading and uploading of authorized data between
802           central database(s) and PCs.
803          Support fully automated interfaces to existing systems, to permit functional
804           integration.


806   C.11.3         Technical Support
807   The contractor shall operate a "Help Line", available on an agreed-upon schedule
808   based on individual Agency requirements and staffed by personnel specifically familiar
809   with the [Issuing Agency] implementation of the contractor's proposed system.

810   C.11.4         Section 508 Accessibility

811   Federal agencies are required by Section 508 of the Rehabilitation Act of 1973, as
812   amended (29 U.S.C. 794d), to offer access to electronic and information technology for
813   disabled individuals within its employ, and for disabled members of the public seeking
814   information and services. This access must be comparable to that which is offered to
815   similar individuals who do not have disabilities. Standards for complying with this law
816   are prescribed by the Architectural and Transportation Barriers Compliance Board (The
817   Access Board). Information on the Section 508 standards can be viewed at:


820   All electronic and information technology (EIT) must meet the applicable accessibility
821   standards at 36 CFR 1194, unless an agency exception to this requirement exists. 36
822   CFR 1194 implements Section 508 of the Rehabilitation Act of 1973, as amended, and
823   is viewable at

824   The standards do not require the installation of specific accessibility-related software or
825   the attachment of an assistive technology device, but require the EIT be compatible with
826   such software and devices so that it can be used with assistive technology if so required
827   by the agency in the future.

828   Deliverables under this vehicle shall incorporate these standards as well as any agency
829   specific standards developed customer agencies. The Offeror’s response to the
830   solicitation shall contain documentation of compliance with these standards, including
831   the Voluntary Product Accessibility Template, if applicable. However, the Contracting
832   Officer may request additional technical documentation, if necessary to make this
833   determination.

834   The final work products must include documentation that the deliverable conforms to the
835   Section 508 Standards promulgated by the US Access Board.
836   In the event of a dispute between the Offeror and a [Issuing agency], the assessment of
837   the Section 508 compliance will control, and the Offeror shall make any additional
838   changes needed to conform with the Section 508 standards.

839   C.11.5         Privacy Act Protected Data

840   The Offeror must prevent unauthorized access to Government data at all times, and
841   must demonstrate in its proposal how its systems and processes will prevent


842   unauthorized access. Since the successful Offeror will deliver services to Federal
843   agencies and handle Federal employee information, the Offeror and its employees will
844   be governed by the provisions of the Federal Privacy act (FPA). Refer to the most
845   current version of Federal Acquisition Regulations (FAR) 48 CFR Ch.1, Part 24.1
846   ( to ensure compliance with the FPA.
847   Additionally, for the purposes of the 5 U.S.C. 552a (i) (US Code for records maintained
848   on individuals) the Offeror and its employees will be held to the same standards as
849   Federal employees.

850   Any information system developed and/or operated for the Government under the terms
851   of this solicitation shall be developed and/or operated so as to comply with all relevant
852   provisions of the Federal Privacy Act of 1974, the Federal e-Government Act of 2002,
853   and any other applicable Federal privacy statutes and regulations. At a minimum, this
854   means that a Privacy Impact Assessment (PIA) is required of all systems that gather
855   personal information. The PIA is a checklist required by the E-Government Act of 2002
856   that should be used when designing and developing a new or amended information
857   system that contains information on individuals. The purpose of the PIA is to ensure that
858   privacy protections and Privacy Act requirements are considered in information
859   systems.

860   If the PIAs are to be performed by an entity other than the offeror, then the offeror must
861   make accessible to the [Issuing agency], or their designee, information systems residing
862   in the offerror’s facilities that support the [Issuing agency’s] operations and assets. If the
863   PIAs are performed by the provider, then the provider must report the results of the PIA
864   to the [Issuing agency].

865   For additional information on FPA compliance visit the OPM website dedicated to this
866   purpose at:


868   C.11.6         Security

869   The Offeror shall afford ordering [Issuing agency], including the Office of Inspector
870   General, access to the Offeror’s and subcontractor’s facilities, installations, operations,
871   documentation, databases, and personnel used in performance of task orders. Access
872   shall be provided to the extent required to carry out a program of IT inspection,
873   investigation, and audit to safeguard against threats and hazards to the integrity,
874   availability, and confidentiality of customer agency data or to the function of computer
875   systems operated on behalf of customer agencies, and to preserve evidence of
876   computer crime.

877   [Issuing agency], at their discretion, may suspend or terminate the access and/or use of
878   any or all government agency access and systems for conducting business with any/or
879   all Offerors when a security or other electronic access, use or misuse issue gives cause


880   for such action. The suspension or termination may last until a time as the government
881   determines that the situation has been corrected or no longer exists.

882   Offerors are responsible for the security, integrity and appropriate authorized use of
883   their systems interfacing with the government and or used for the transaction of any and
884   all government business. The government, through the agency’s Contracting Officer,
885   may require the use or modification of security and/or secure communications
886   technologies related to agency systems access and use.

887   The Government requires that the successful Offeror’s security procedures be
888   monitored, verified and validated by its Federal agency customers. The Offeror shall
889   meet or exceed the minimum security guidelines set forth by the Federal Information
890   Security Management Act (FISMA), OMB policy and National Institute of Standards and
891   Technology (NIST) (See section C.1.6 in this Attachment). Furthermore, the Offeror
892   shall adhere to established Certification and Accreditation (C&A) procedures for each
893   component of the defined-benefit technology solution prior to that component becoming
894   operational. The Offeror shall use the NIST guidelines for C&A.

895   Activities may necessitate the Offeror to have access to a Federal Automated
896   Information System (AIS) or systems, as well as the implementation of new systems.
897   Based upon the definitions contained in Federal Information Processing Standards
898   Publication 199 (FIPS PUB 199), ordering agencies will make sensitivity determinations
899   and include their determinations in task order requests.

900   FIPS PUB 199 is accessible on line at the following:


902   Information technology resources include, but are not limited to, hardware, application
903   software, system software, and information (data). Information technology services
904   include, but are not limited to, the management, operation (including input, processing,
905   transmission, and output), maintenance, programming, and system administration of
906   computer systems, networks, and telecommunications systems. The Offeror shall be
907   responsible for implementing sufficient Information Technology security, to reasonably
908   prevent the compromise of government IT resources for all of the government systems
909   that are interconnected with the government network or systems operated by the
910   government.

911   All Offeror personnel, as well as equipment used to process or store government data,
912   or to connect to government networks, must comply with the requirements contained in
913   the relevant security standards and Government regulations (see section C.1.6).

914   Access security for the proposed system shall be provided at the screen, record, and
915   field level for all information in the database. Access security must also have integrated
916   security features that are configurable by the system administrator to control access to
917   the application, functional modules, transactions, and data, including sensitive data


918   elements such as social security numbers and banking information by named user,
919   groups of users, or functional role. The application’s integrated security features should
920   be compliant with the NIST Security Standards.

921   Users of the proposed system shall be able to delegate their authorities’ subject only to
922   security and access controls.

923   The proposed system shall restrict access (input or query) down to the data element
924   level for each user-ID. All unauthorized login attempts, and all unauthorized access
925   attempts, shall be written to a log file with the date and time, terminal ID, user ID,
926   table(s) and function(s) ID recorded. This information should be accessible via query
927   and report.

928   The proposed system shall generate and maintain audit trails recording all changes and
929   all accesses to the database, including the terminal from which the change/access was
930   made, the date and time of the change/access, and the ID of the person making the
931   change/access.

932   Controls within the proposed system shall have been designed to support operation in
933   accordance with OMB Circular A-123, Section III ("Integrated Internal Control
934   Framework") and OMB Circular A-130, Appendix III ("Security of Federal Automated
935   Information Systems").



938   System security facilities shall provide the Government System Administrators full
939   control over access by users, including the ability to specify the type of access on the
940   basis of requester's ID, password, terminal used, and function performed.

941   C.11.7         IT Security References

942   The following list of resources provides additional information that may be helpful to
943   Offerors in preparing their responses to this solicitation:

944   Office of Management and Budget (OMB) Circular No. A-130, Management of Federal
945   Information Resources. Documents may be found at:


947   Office of Management and Budget (OMB) guidelines on The E-Government Act of
948   2002, Sec. 208 on Privacy Provisions (see Privacy Impact Assessment requirements).
949   Information available at:



951   National Institute of Standards and Technology (NIST) Special Publication 800-18,
952   Guide for Developing Security Plans for Information Technology Systems. This
953   document is available at:


955   National Security Telecommunications and Information Systems Security Policy
956   (NSTISSP) No. 11, National Information Assurance Acquisition Policy. This document
957   is available at:


959   National Institute of Standards and Technology (NIST) Special Publication 800-37,
960   Guide for the Security Certification and Accreditation of Federal Information Systems.
961   This document can be found at:


964   Draft NIST Special Publication 800-53, Revision 1, and Recommended Security
965   Controls for Federal Information Systems. This document can be found at:


968   Draft NIST Special Publication 800-53A, Guide for Assessing the Security Controls for
969   Federal Information Systems. This document can be found at:


971   NIST Cryptographic Toolkit. Information regarding encryption standards approved for
972   use by Government organizations may be found at:


974   NIST Special Publication 800-12, An Introduction to Computer Security. Documents
975   may be found at:


977   NIST Special Publication 800-14, Generally Accepted Principles and Practices for
978   Securing Information Technology Systems. Documents may be found at:


980   NIST SP 800-16, Information Technology Security Training Requirements. Documents
981   may be found at:




 985   NIST SP 800-47, Security Guide for Interconnecting Information Technology Systems.
 986   This document can be found at:


 988   Federal Information Security Management Act (FISMA). This document is available at:


 990   National Security Agency Common Criteria Evaluation and Validation Scheme (CCEVS)
 991   security


 993   Department of Defense, Directive on Information Assurance:


 995   Department of Defense, Instruction on Information Assurance:


 997   The successful Offeror shall provide details as to how their services, systems and the
 998   surrounding processes will adhere to the relevant security standards and Government
 999   regulations.

1000   C.11.8         Continuity of Operations Planning

1001   The successful Offeror must propose services and systems that comply with the
1002   guidance contained in the Federal Preparedness Circular 65 (FPC-65). This guidance
1003   describes the requirements of Continuity of Operations Planning (COOP) and calls for
1004   essential functions to be operational within 12 hours of COOP activation. The proposed
1005   services must meet this standard and must be tested at least annually.


1007   The Offeror must provide its plans for providing continuity of operations in the event of
1008   an emergency or disaster. These plans must focus on maintaining the continuity of the
1009   shared services provided to agencies. Offerors should note that FSIO consider COOP
1010   planning an area of significant importance. In order to meet this objective, the Offeror
1011   must describe its approach, in detail, for developing and implementing: a Disaster
1012   Recovery Plan (DRP).


1013   C.11.9        Disaster Recovery Testing
1014   The successful Offeror shall support and participate in annual testing of Disaster
1015   Recovery Plans at [Issuing agency]. In addition, the successful Offeror must perform an
1016   annual test of the Offeror's DRP. That test must meet Federal standards and any
1017   applicable agency customer standards. The results of that test, and any resulting plan
1018   for changes to the DRP, should be made available to customer agencies after the
1019   conclusion of the test. The Government reserves the right to observe the successful
1020   Offeror's Disaster Recovery testing process.

1021   C.11.10       Ownership Rights
1022   All data and materials associated with the administration of federal clients and any
1023   Government furnished equipment are the property of the Federal Government. At end of
1024   the contract, all property must be turned over in its entirety to the Government.

1025   C.11.11       IV&V Testing and Acceptance
1026   Individual agency task order may call for Independent Validation and Verification (IV&V)
1027   tests. The Government reserves the right to subject the successful Offeror’s services to
1028   (IV&V) tests, including remediation and retest as required, before acceptance by the
1029   Government.
1030   Placements of orders for operations services could be dependent on this acceptance.
1031   Government acceptance is subject to Federal Acquisition Regulation (FAR) 52.212-4(a)
1032   Inspection/Acceptance.

1033   C.11.12       Audit Requirements
1034   The Government reserves the right to audit the successful Offeror’s services both
1035   before implementation and in operation. The successful Offeror must be available to
1036   support an audit. The Audit may include, but is not limited to, billing audit, security and
1037   controls audit and audit of the successful Offeror’s performance metric monitoring
1038   processes and results.

1039   C.11.13       Training
1040   The Offeror shall provide agreed-upon levels of training for end-user and systems
1041   operations to key Government staff. The Offeror, and shall grant the Government the
1042   right to use all provided training materials and to allow the Government the option of
1043   using third-party supplied training or in-house training.
1044   The proposed system shall include on-line tutorials and documentation, as well as a
1045   context-sensitive help function allowing users to readily determine the valid actions that
1046   can be performed from any point in the program explaining the cause and possible
1047   resolution for any error messages obtained.
1048   The Offeror shall keep all training material updated to reflect current production
1049   implementation.


1050   C.11.14        Value-Added Services
1051   Offerors should also consider their financial management system’s ability to provide the
1052   following value added services:
1053          The ability to allow managers to monitor workload by technicians including
1054           the number of invoices assigned to each technician, status of those
1055           invoices (for example: Late, Discount, Days to Pay, Must Pay,
1056           Remaining).
1057          The capability to present column, row, & field names in business language
1058           instead of database language
1059          The ability to add and present descriptive labels for the encoded values in
1060           fields, i.e. value of 1 means ―active‖, value 2 means ―inactive‖
1061          The ability to insert additional help messages as needed.
1062          The ability to provide a comparison utility for vendor baseline configuration
1063           version vs. any customizations to allow agency to evaluate the impact of a
1064           software update.

1065   C.12           Performance Management
1066   The Offeror shall provide a quality assurance surveillance plan (QASP) that
1067   incorporates quality control for Agency-designed financial management system services
1068   for review and approval. The plan documents management practices used to ensure
1069   that the results of the financial management system are of the type and quality needed
1070   for their intended use. A Quality Control Plan (QCP) documents the technical and
1071   quality aspects of financial management project, including project management,
1072   implementation and assessment. It will specify responsibilities, monitoring objectives,
1073   sampling design, sample collection methods, quality control, data management and
1074   data validation activities. The quality control plan should identify the organization or
1075   individual responsible for quality control and the specific procedures used to ensure
1076   delivery of a quality product. The plan will also detail quality assurance measures and
1077   the method of accountability and required documentation. The plan should include a
1078   minimum of project deliverables and schedule, organizational chart, project quality
1079   control requirements, communications plan and review process.
1080   The Offeror shall establish a performance management plan that verifies and validates
1081   that the approach and the system that they are deploying meets the goals and
1082   objectives of [Issuing Agency]. This plan must include the continued support of
1083   business outcomes, operational metrics, and quality management. The plan should
1084   capture performance measures in areas such as customer satisfaction, system
1085   availability, and mission & business results.
1086   The Offeror shall identify any assumptions or constraints that may impact the ability to
1087   meet proposed metrics. The Offeror shall also define any additional proposed metrics,
1088   which demonstrate the commitment to project success and demonstrates their
1089   knowledge of the risks and responsibilities associated in deploying a program of this
1090   scope. The QASP shall align specific tasks, deliverables and milestones in the


1091   proposed plan with clearly defined metrics. The Offeror and [Issuing Agency] shall
1092   mutually agree on each metric(s) quantifiable performance levels.

1093   C 12.1       Quality Control Plan (QCP)
1094   The Offeror shall provide, in conjunction with their QASP, a QCP that integrates the
1095   Offeror quality assurance and quality reporting process, and provides for a surveillance
1096   mechanism for each metric and a collaborative reporting plan for regular performance
1097   reporting. The proposed plan shall provide [Issuing Agency] with complete visibility to
1098   the metrics and performance. While performance will be formally reviewed on a regular
1099   basis, [Issuing Agency] will have unrestricted self-service access to this performance
1100   information. After contract award, the Offeror shall immediately notify [Issuing Agency]
1101   of any problems, issues, or concerns that are identified through cost, schedule and
1102   performance analysis and reporting. The Offeror shall provide a mechanism and
1103   schedule for [Issuing Agency] and the Offeror to regularly review the business outcome
1104   metrics and develop and execute action plans to ensure continuous improvement.
1105   Reviews of business outcomes, operational metrics, and quality management shall be
1106   performed regularly. Performance management shall be an iterative process that will
1107   evolve as business outcomes, performance metrics, and quality management are
1108   updated to align with [Issuing Agency] financial management goals.





1115   E.1          Notice Listing Contract Clauses Incorporated by Reference
1116                (Inspection and Acceptance)
1117   The following contract clauses are pertinent to this section and are hereby incorporated
1118   by reference (by Citation Number, Title, and Date) in accordance with the clause at FAR
1119   "52.252-2 CLAUSES INCORPORATED BY REFERENCE" in Section I of this contract.
1120   See FAR 52.252-2 for an internet address (if specified) for electronic access to the full
1121   text of a clause.
1122   NUMBER                       TITLE                                          DATE
1123   52.246-4                  INSPECTION OF SERVICES--FIXED-PRICE               AUG 1996

1124   E.2          Government Acceptance and Review
1125   a) The Government will review and verify that all deliverables associated with this
1126   contract fulfill the requirements and standards stated herein.
1127   (b) Inspection and acceptance of all services under this contract must be accomplished
1128   by a Government Contracting Officer (CO) or designated representative(s) in writing.
1129   The designated representative(s) will inspect, and be responsible for the review and
1130   acceptance of all deliverables under the contract prior to its acceptance by the CO.
1131   Acceptance testing will be performed by the designated representative(s).

1132   E.3          Exit Criteria
1133   The offeror shall be issued a task order for performance of the Product Acceptance Test
1134   (PAT), in accordance with the successful proposal’s performance work statement. The
1135   price for the product acceptance test represents the minimum ordering amount under
1136   the contract or interagency agreement. Unsuccessful completion of the PAT shall result
1137   in termination of the contract/Investment Advisory Group (IAG). This clause shall not be
1138   construed to take precedence over the Default clause of the contract.



1141   F.1           Notice Listing Contract Clauses Incorporated By Reference
1142                 (Deliveries or Performance)
1143   The following contract clauses are pertinent to this section and are hereby incorporated
1144   by reference (by Citation Number, Title, and Date) in accordance with the clause at FAR
1145   "52.252-2 CLAUSES INCORPORATED BY REFERENCE" in Section I of this contract.
1146   See FAR 52.252-2 for an internet address (if specified) for electronic access to the full
1147   text of a clause.
1148   NUMBER                   TITLE                                                 DATE
1149   52.242-15                STOP-WORK ORDER                                      AUG 1989
1150   52.247-34                F.O.B. DESTINATION                                   NOV 1991
1151   52.247-48                F.O.B. DESTINATION--EVIDENCE OF SHIPMENT FEB 1999

1152   F.2           Reports
1153   The Contractor shall prepare and deliver reports listed below to the designated
1154   addressees. Each report shall cite the contract number and identify the [issuing
1155   agency].

1156   F.3           Malfunction/Corrective Action Report
1157   To ensure the [issuing agency] will receive the quality from the solution being deployed
1158   and the performance of the contract, a QASP will be implemented. The QASP will
1159   ensure the vendor/contractor will meet or exceed agreed upon performance objectives
1160   or service level parameters in a Service Level Agreement. The QASP will focus on the
1161   system implementation, availability, functionality and cost. The QASP will require
1162   reporting in the following key areas/metrics. The [issuing agency] reserves the right to
1163   make any necessary changes to these areas/metrics in support of government
1164   requirements.
1165   The reporting requirements will include (at a minimum):
1166   1. Overall System Activity and Performance Reports
1167   (availability/uptime/connectivity/etc.)
1168   2. System’s Implementation (metrics during the implementation of solution)
1169   3. System’s FMLoB Functional Capabilities
1170   4. System’s FMLoB Reporting Capabilities
1171   5. Data Assurance/Maintenance/Backup
1172   6. Security/Intrusion


1173   7. Customer Support
1174   8. Maintenance/Upgrade
1175     Copies shall be distributed as follows:
1176         __ to the local site coordinators affected
1177         X to Project Officer
1178         __ to Contracting Officer

1179   F.4           Period of Performance
1180   The Period of Performance is as follows:
1181           Implementation Period:      Twenty four (24) months from date of award
1182           Base Period 1-2:            Twenty four (24) months from end of implementation
1183           period
1184                 If exercised:
1185           Option Periods 1 - 8:       In sequential order, twelve (12) months from the end
1186                                       of the previous period.

1187   F.5           52.217-8 Option to Extend Services
1188   The Government may require continued performance of any services within the limits
1189   and at the rates specified in the contract. These rates may be adjusted only as a result
1190   of revisions to prevailing labor rates provided by the Secretary of Labor. The option
1191   provision may be exercised more than once, but the total extension of performance
1192   hereunder shall not exceed six months. The Contracting Officer may exercise the option
1193   by written notice to the Contractor within _____ [insert the period of time within which
1194   the Contracting Officer may exercise the option].

1195   F.6           52.217-9 Option to Extend the Term of the Contract
1196      (a) The Government may extend the term of this contract by written notice to the
1197   Contractor within _____ [insert the period of time within which the Contracting Officer
1198   may exercise the option]; provided that the Government gives the Contractor a
1199   preliminary written notice of its intent to extend at least _____ days [60 days unless a
1200   different number of days is inserted] before the contract expires. The preliminary notice
1201   does not commit the Government to an extension.
1202      (b) If the Government exercises this option, the extended contract shall be considered
1203   to include this option clause.
1204      (c) The total duration of this contract, including the exercise of any options under this
1205   clause, shall not exceed ___________ (months) (years).



1208   G.1           Invoice Requirements
1209   Contractor will prepare and submit proper invoices in accordance with the criteria
1210   outlined below to the Payment Office, not more frequently than monthly, unless
1211   otherwise so authorized in the contract.
1212   If the contract is a fixed-price type contract, the contractor may submit SF-1034, Public
1213   Voucher, or the equivalent thereto, i.e., a contractor's own invoice.
1214   Original Invoices should be submitted to the payment office below:
1215           [Enter Issuing agency’s payment center address here]
1216   A courtesy copy of each invoice should also be submitted to the Contracting Officer’s
1217   Technical Representative (COTR). The name of the COTR will be determined at a later
1218   date.
1219   The Invoice must include the same budget line items or cost categories as appears in
1220   the contract, including any modifications thereto and the following:
1221   (1) Name and address of the Contractor;
1222   (2) Invoice date;
1223   (3) Contract number or other authorization for supplies delivered or services performed
1224   (including order number and contract line item number);
1225   (4) Description, quantity, unit of measure, unit price, and extended price of supplies
1226   delivered or services performed;
1227   (5) Shipping and payment terms (e.g., shipment number and date of shipment, prompt
1228   payment discount terms. Bill of lading number and weight of shipment will be shown for
1229   shipments on Government bills of lading;
1230   (6) Name and address of Contractor official to whom payment is to be sent (must be
1231   the same as that in the contract or in a proper notice of assignment);
1232   (7) Name (where practicable), title, telephone number and mailing address of person to
1233   be notified in event of a defective invoice;
1234   (8) Any other information or documentation required by other requirements of the
1235   contract.
1236   In addition to the above, invoices should be numbered consecutively. All final invoices
1237   shall be clearly marked Final Invoice.


1240   G.2           Method of Payment
1241   A. Payments under this contract will be made either by check or electronic funds
1242   transfer (through the Treasury Fedline Communications System (FEDLINE) or the
1243   Automated Clearing House (ACH)), at the option of the Government. After award, but
1244   no later than 14 days before an invoice or contract financing request is submitted, the
1245   Contractor shall designate a financial institution for receipt of electronic funds transfer
1246   payments. The contractor shall submit this designation to the Contracting Officer or
1247   other Government official as directed.
1248   B. For payments through FEDLINE, the Contractor shall provide the following
1249   information:
1250   (1) Name, address, and telegraphic abbreviation of the financial institution receiving
1251   payment.
1252   (2) The American Bankers Association 9-digit identifying number of the financing
1253   institution receiving payment if the institution has access to the Federal Reserve
1254   Communications System.
1255   (3) Payee's account number at the financial institution where funds are to be
1256   transferred.
1257   (4) If the financial institution does not have access to the Federal Reserve
1258   Communications System, provide the name, address, and telegraphic abbreviation of
1259   the correspondent financial institution through which the financial institution receiving
1260   payment obtains electronic funds transfer messages. Provide the telegraphic
1261   abbreviation and American Bankers Association identifying number for the
1262   correspondent institution.
1263   C. For payments through ACH, the Contractor shall provide the following information:
1264   (1) Routing transit number of the financial institution receiving payment (same as
1265   American Bankers Association identifying number used for FEDLINE).
1266   (2) Number of account to which funds are to be deposited.
1267   (3) Type of depositor account ("C" for checking, "S" for savings).
1268   (4) If the Contractor is a new enrollee to the ACH system, a "Payment Information
1269   Form," SF 3881, must be completed before payment can be processed.
1270   D. In the event the Contractor, during the performance of this contract, elects to
1271   designate a different financial institution for the receipt of any payment made using
1272   electronic funds transfer procedures, notification of such change and the required
1273   information specified above must be received by the appropriate Government official 30
1274   days prior to the date such change is to become effective.


1275   E. The documents furnishing the information required in paragraphs B and C above
1276   must be dated and contain the signature, title, and telephone number of the Contractor
1277   official authorized to provide it, as well as the Contractor's name and contract number.
1278   F. Contractor failure to properly designate a financial institution or to provide
1279   appropriate payee bank account information may delay payments of amounts otherwise
1280   properly due.

1281   G.3           Contracting Officer’s Technical Representative (COTR)
1282   (a) Mr. /Ms. [TO BE DETERMINED], [Enter Issuing agency’s address here], is hereby
1283   designated to act as contracting officer's technical representative (COTR) under this
1284   contract.
1285   (b) The COTR is responsible, as applicable, for receiving all deliverables; inspecting
1286   and accepting the supplies or services provided hereunder in accordance with the terms
1287   and conditions of this contract; providing direction to the contractor which clarifies the
1288   contract effort, fills in details or otherwise serves to accomplish the contractual scope of
1289   work; evaluating performance; and certifying all invoices/vouchers for acceptance of the
1290   supplies or services furnished for payment.
1291   (c) The COTR does not have the authority to alter the contractor's obligations under the
1292   contract, and/or modify any of the expressed terms, conditions, specifications, or cost of
1293   the agreement. If, as a result of technical discussions, it is desirable to alter/change
1294   contractual obligations or the scope of work, the contracting officer must issue such
1295   changes.

1296   G.4           Government Property
1297   (a)    Government Furnished Facilities (GFE). The Government may, in certain cases,
1298   provide office facilities, equipment, and materials for daily business use of staff called
1299   for under this contract.
1300   (b)    Government Furnished Equipment/Information. The contractor shall identify, in
1301   the proposal, any Government furnished equipment/information or Contractor-acquired
1302   – Government owned property (CAP), necessary to perform this task. This shall include
1303   any contractor purchased or acquired/Government owned items. Detailed bills of
1304   materials should be submitted along with the proposal; noting part numbers, prices, and
1305   need dates for all required GFE.
1306   (c)     The contractor shall maintain a detailed inventory accounting system for
1307   Government furnished equipment/material or CAP. The inventory accounting system
1308   must specify, as a minimum: product description (make, model), Government tag
1309   number, date of receipt, name of recipient, location of receipt, current location, purchase
1310   cost (if CAP), and contract/order number under which the equipment is being used. The
1311   contractor shall either: a) attach an update inventory report to each monthly progress
1312   and status report, or b) certify that the inventory has been updated and is available for


1313   Government review. In either case the contractor’s inventory listings must be available
1314   for Government review within one business day of COR request.

1315   G.5           Subcontractor Consent
1316   (a) If the contractor has an approved purchasing system, consent is required for
1317   subcontracts specifically identified by the contracting officer in the subcontracts clause
1318   of the contract. The contracting officer may require consent to subcontract if the
1319   contracting officer has determined that an individual consent action is required to protect
1320   the Government adequately because of the subcontract type, complexity, or value, or
1321   because the subcontract needs special surveillance. These can be subcontracts for
1322   critical systems, subsystems, components, or services. Subcontracts may be identified
1323   by subcontract number or by class of items (e.g., subcontracts for engines on a prime
1324   contract for airframes).

1325   (b) If the contractor does not have an approved purchasing system, consent to
1326   subcontract is required for cost-reimbursement, time-and-materials, labor-hour, or letter
1327   contracts, and also for unpriced actions (including unpriced modifications and unpriced
1328   delivery orders) under fixed-price contracts that exceed the simplified acquisition
1329   threshold, for—

1330         (1) Cost-reimbursement, time-and-materials, or labor-hour subcontracts; and

1331         (2) Fixed-price subcontracts that exceed—

1332                 (i) For the Department of Defense, the Coast Guard, and the National
1333                 Aeronautics and Space Administration, the greater of the simplified
1334                 acquisition threshold or 5 percent of the total estimated cost of the
1335                 contract; or

1336                 (ii) For civilian agencies other than the Coast Guard and the National
1337                 Aeronautics and Space Administration, either the simplified acquisition
1338                 threshold or 5 percent of the total estimated cost of the contract.

1339   (c) Consent may be required for subcontracts under prime contracts for architect-
1340   engineer services.

1341   (d) The contracting officer’s written authorization for the contractor to purchase from
1342   Government sources (see Part 51) constitutes consent.




1345   G.6           Agency Small Business Subcontracting Goals
1346   FSIO strongly encourages issuing Agencies to support small business. The contractor’s
1347   goal for all subcontracting dollars is fifty percent (50%) for small business. Of the 50%
1348   goal for small business, the following table represents sub-category goals for allocating
1349   funds among small disadvantaged, service disabled veteran, woman-owned, and
1350   HUBZone small businesses:
1351           Small Disadvantaged Businesses - 20%
1352           Service-Disabled Veteran Small Businesses - 3%
1353           Woman-Owned Small Businesses - 7.5%
1354           HUBZone Businesses - 3%
1355   The offeror shall be familiar with and shall periodically review the published Agency
1356   goals for small business utilization.



1359   H.1           Waiver of Delivery Schedule
1360   None of the following shall be regarded as an extension, waiver, or abandonment of the
1361   delivery schedule or a waiver of the Government's right to terminate for default: (i) Delay
1362   by the Government in terminating for default; (ii) Acceptance of delinquent deliveries;
1363   and (iii) Acceptance or approval of samples submitted either after default in delivery or
1364   in sufficient time for the contractor to meet the delivery schedule.
1365   Any assistance rendered to the contractor on this contract or acceptance by the
1366   Government of delinquent goods or services hereunder will be solely for the purpose of
1367   mitigating damages and is not to be construed as an intention on the part of the
1368   Government to condone any delinquency, or as a waiver of any rights the Government
1369   may have under subject contract.

1370   H.2           End of Contract Succession Support
1371   The Offeror recognizes that the services under this contract are critical to the
1372   Government and must continue without interruption. Contractor also recognizes that
1373   when the contract expires, a successor, either the Government or another contractor,
1374   may continue the services. The Contractor agrees to furnish phase-in-training, apply its
1375   best efforts and cooperation to carry out an orderly and efficient transition to a
1376   successor.

1377   H.3           Contract Phase Out Plan
1378   The Offeror shall address those actions, plans, procedures and resources (less)
1379   necessary to complete the contract term without impacting service or response in
1380   functional areas. Describe in detail how responsibility and accountability will be
1381   relinquished for all Government furnished property and documentation of the system.
1382   Discuss procedures for identifying accrued personnel benefits such as personal and
1383   sick leave, the scheduling of such absences, and their effect on contract performance
1384   during phase out.

1385   H.4           Computer Programmers and System Analysts
1386   a. The Department of Labor has determined that computer programmers and system
1387   analysts are not in the learned professions for purposes of an exemption from the
1388   Service Contract Labor Standards Act, 41 U.S.C. Sections 351-358, as amended. This
1389   determination is published at 29 C.F.R Section 541.302(h).
1390   b. Therefore, the Service Contract Act must be included in this contract unless the
1391   contractor can provide signed certifications and supporting evidence acceptable to the
1392   Contracting Officer that ALL computer programmers and systems analysts (including
1393   trainees) whose services will be acquired under this contract are either:


1394   (1) Engaged in managerial and administrative duties which qualify then for exemption
1395   under 29 C.F.R 541.1 or 541.2, or
1396   (2) High salaried professional employees as defined in 29 C.F.R. 541.315.
1397   (a) Compensated on a salary or fee basis at a rate of at least $250 per week exclusive
1398   of board, lodging, or other facilities, and
1399   (b) Whose primary duty consists of the performance of work requiring knowledge of an
1400   advance type in a field of science or learning which includes work requiring the constant
1401   exercise of discretion and judgment.

1402   H.5           Submittal Data on Personnel
1403   The Contractor shall provide a list of personnel including their area of expertise who will
1404   be available for assignment to support the contract. A resume shall be submitted for all
1405   key personnel identified in Section I.10, Key Personnel. Resumes shall clearly show
1406   how and where individuals possess the required experience for the position listed in
1407   Section L.7.2.2 Management Approach.

1408   H.6           Dissemination of Information
1409   There shall be no dissemination or publication, except within and between the
1410   Contractor and any subcontractors, of information developed under this contract or
1411   contained in the reports to be furnished pursuant to this contract without prior written
1412   approval from the Contracting Officer.

1413   H.7           Release of Reports
1414   The Contractor is prohibited from releasing to any source, other than the sponsoring
1415   activity, any interim, draft and final reports or information pertaining to services
1416   performed under this contract until report approval or official review has been obtained.
1417   Furthermore, the contractor shall ensure that the cover of all interim, draft and final
1418   reports contain the following statement: "The view, opinions, and/or findings contained
1419   in this report are those of the author(s) and should not be construed as an official
1420   Government position, policy or decision, unless so designated by other documentation."

1421   H.8           Release of News Information
1422   No news release (including photographs and films, public announcements, denial or
1423   confirmation of same) on any part of the subject matter of this contract or any phase of
1424   any program hereunder shall be made without the prior written approval of the
1425   Contracting Officer.

1426   H.9           Software Rights
1427   All software provided under this contract shall be delivered with unlimited rights in
1428   accordance with the provisions of FAR 52.227-14.



1430   H.10          Royalty Free License
1431   In consideration of the sum to be paid to the contractor under this contract, the
1432   contractor hereby agrees and does grant, convey, and reserves to the United States of
1433   America a nonexclusive, irrevocable, world wide, royalty-free license in all written
1434   material, published, printed, presented or used in connection with the contract, in which
1435   the contractor presently holds a copyright or in the future shall obtain a copyright therein
1436   or in which he has the right to issue royalty-free licenses thereto.

1437   H.11          Type of Service
1438   a. The Government and the Contractor understand and agree that the services
1439   delivered by the Contractor to the Government are non-personal services. The parties
1440   also recognize and agree that no employer-employee or master-servant relationship
1441   exists or will exist between the Government and the Contractor. The Contractor and the
1442   Contractor's employees are not employees of the Federal Government and are not
1443   eligible for entitlement and benefits given federal employees.
1444   b. Contractor personnel under this contract shall not:
1445   (1) Be placed in a position where there is an appearance that they are employed by a
1446   Federal Officer, or are under the supervision, direction, or evaluation of a Federal
1447   Officer.
1448   (2) Be placed in a position of command, supervision, administration or control over
1449   personnel or personnel of other Government Contractors, or become a part of the
1450   Government organization.
1451   (3) Be used in administration or supervision of procurement activities.

1452   H.12          Citizenship
1453   All contract employees shall be U.S. citizens or legal immigrant aliens.

1454   H.13          Employee Relationship
1455   a. The services to be performed under this contract do not require the Contractor or his
1456   employees to exercise personal judgment and discretion on behalf of the Government,
1457   but rather, the Contractor's employees will act and exercise personal judgment and
1458   discretion on behalf of the Contractor.
1459   b. Rules, regulations, directives and requirements which are issued by Government
1460   Authorities under their responsibility for good order, administration and security are
1461   applicable to all personnel who enter a Government installation or who travel on
1462   Government transportation. This is not to be construed or interpreted to establish any
1463   degree of Government control which is inconsistent with a non-personal services
1464   contract.


1465   H.14         Inapplicability of Employee Benefits
1466   This contract does not create an employer-employee relationship. Accordingly,
1467   entitlement and benefits applicable to such relationships do not apply.
1468   a. Payments under this contract are not subject to Federal income tax withholding.
1469   b. Payments under this contract are not subject to Federal Insurance Contributions Act.
1470   c. The Contractor is not entitled to unemployment compensation benefits under the
1471   Social Security Act, as amended, by virtue of performance under this contract.
1472   d. The Contractor is not entitled to any workmen's compensation benefits by virtue of
1473      this contract.
1474   e. The entire consideration and benefits to the Contractor for performance of this
1475      contract is contained in the provisions for payment under this contract.

1476   H.15         Contractor Supervision
1477   The Government will not supervise, direct, or evaluate the contractor's employees.
1478   Similarly, the contractor's employees shall not supervise, direct, or evaluate
1479   Government employees or employees employed by other contractors. The contractor's
1480   employees shall not become an integrated part of any Government organization, nor
1481   shall they administer or control any Government procurement activities.

1482   H.16         All Items to Become Property of the Government
1483   Title to all sources data and materials furnished by the government, together with all
1484   plans, system analysis and design specifications and drawings, completed programs
1485   except priority programs and documentation thereof, reports and listings, and all other
1486   items pertaining to the work and services to be performed under orders pursuant to this
1487   contract, including any copyright shall become and remain with the government upon
1488   completion. The government shall have the full right to use each of these for its
1489   purposes without compensation or approval on the part of the contractor. The
1490   government shall have access to and the right to make copes of the above mentioned
1491   items. All proprietary programs shall be indicated as such in individual proposals.

1492   H.17         Contractor Employee Suitability and Security Requirements

1493   H.17.1       Background Investigations
1494   For the employees needing to regularly and frequently enter Federal facilitates and
1495   those needing access to government systems.

1496   H.17.1.1     Background Investigation Requirements

1497   The investigation requirements for contractor employees are based on the risk or
1498   sensitivity level designation of the position. The Contracting Officer, Contracting
1499   Officer's Technical Representative, or other agency's designated official informs the


1500   Contractor of the risk or sensitivity level for each contractor employee position. The
1501   minimum level of investigation for each risk or sensitivity level is indicated below.
1502   Position Risk/Sensitivity Level:          Minimum Investigation Requirement:
1503   Low Risk/Non-sensitive                    National Agency Check & Inquiries (NACI)
1504   Moderate Risk                             Minimum Background Investigation (MBI)
1505   High Risk                                 Background Investigation (BI)
1506   Noncritical-Sensitive                     Minimum Background Investigation (MBI)*
1507   Critical-Sensitive                        Single Scope Background Investigation
1508   (SSBI)*
1509   * Individuals occupying Critical-Sensitive positions (i.e., require Top Secret security
1510   clearances) are subject to reinvestigation every 5 years. Individuals occupying Non-
1511   critical-Sensitive positions are subject to reinvestigation every 10 years for Secret
1512   security clearances and every 15 years for confidential security clearances.

1513   H.17.1.2      Conducting Background Investigations

1514   All contract employees require a background investigation. The Office of Personnel
1515   Management (OPM) will conduct background investigations for [issuing agency]
1516   employees and contractor employees. Since OPM only accepts requests from Federal
1517   agencies to conduct background investigations, the [Enter issuing agency’s name here]
1518   will make arrangements with the Contractor to send the contractor employee's
1519   completed papers to [issuing agency] for submission to OPM.

1520   H.17.1.3      Payment for Background Investigation

1521   If [issuing agency] bears the cost for background investigations on contractor
1522   employees, the designated [issuing agency] official will forward the required documents
1523   to OPM. If the Contractor bears the cost of the investigations, [Describe the
1524   arrangements by which the Contractor will reimburse the issuing agency for the cost of
1525   the investigations.].

1526   H.17.2        The Investigation Process
1527   The Contractor shall submit written procedures to the designated [issuing agency]
1528   official describing the method by which the following investigation requirements will be
1529   satisfied.

1530   H.17.2.1      Pre-employment Checks

1531   Before a contractor employee can begin work for [issuing agency] , he or she must
1532   provide the Contractor with a properly completed OF-306, Declaration for Federal
1533   Employment, on which the employee has completed items 1 through 7c, questions 9
1534   through 13, and item 16 as necessary, and has signed item 17. (A copy of the OF-306


1535   form can be found at the following website: If the
1536   Contractor has not received a completed OF-306 from the contractor employee within 5
1537   days after requesting the form, the Contractor shall notify the designated [issuing
1538   agency] official.
1539    If the person answers "Yes" to one or more of questions 9 through 13, the Contractor
1540   shall notify the designated [issuing agency] official immediately. The designated
1541   [issuing agency] official will inform the Contractor whether or not the contractor
1542   employee may work on the contract. Before making this decision the designated
1543   [issuing agency] official may also require a pre-employment FBI fingerprint check on
1544   contract employees. This procedure is described in Chapter 2, Section 6.

1545   H.17.2.2       Submission of Investigation Documents

1546   The Contractor shall submit the required documents below to the designated [issuing
1547   agency] official within 7 calendar days of each contractor employee's placement on the
1548   contract in a High Risk, Moderate Risk, Low Risk, or Non-critical-Sensitive position.
1549   However, the Single Scope Background Investigation must be completed before the
1550   contractor employee is placed in a Critical-Sensitive position, unless the [issuing
1551   agency] approves the placement of the contractor employee's placement in the position
1552   before the investigation is completed. The specific form that he or she completes
1553   depends on the risk or sensitivity level of the work that he or she will perform. These
1554   forms can be found on the following website:
1555          The SF-85, Questionnaire for Non-sensitive Positions, is used with positions or
1556           work that is designated at the Low Risk level. The minimum investigation
1557           required is a National Agency Check and Inquiries.
1558          The SF-85P, Questionnaire for Public Trust Positions, is used with positions or
1559           work that is designated at the Moderate or High Risk level. The minimum
1560           investigation required for the Moderate Risk level is a Minimum Background
1561           Investigation. The minimum investigation required for the High Risk level is a
1562           Background Investigation.
1563          The SF-86, Questionnaire for National Security Positions, is used with positions
1564           or work that is designated at the Non-critical-Sensitive or Critical-Sensitive level.
1565           The minimum investigation for Non-critical-Sensitive work is a Minimum
1566           Background Investigation. The minimum investigation for Critical-Sensitive work
1567           is a Single Scope Background Investigation.
1568   The Contractor shall also ensure that each contractor employee is fingerprinted using
1569   Form FD-258. The Contractor can get copies of this form from the designated [issuing
1570   agency] officials.
1571    The Contractor shall submit the following completed forms and documents to the
1572   designated [issuing agency] official for each contractor employee based on the risk or
1573   sensitivity level of work that such employee is performing:


1574   Low Risk:                     High/Moderate Risk:        Critical/Non-critical Sensitive:
1575   SF-85                               SF-85P                        SF-86
1576   FD-258                              FD-258                       FD-258
1577   OF-306                              OF-306                       OF-306
1578   Application/Resume                  Application/resume           Application/resume

1579   H.17.2.3       Temporary Contractor Employees

1580   If the contractor employee is assigned to Low Risk work and is employed on a
1581   seasonal, daily, or intermittent basis, or for no more than 180 days, the NACI is not
1582   required. However, the Contractor shall submit the fingerprints of the contractor
1583   employee to the designated [issuing agency] official on a Form FD-258.

1584   H.17.3         Adjudication

1585   H.17.3.1       Referral of Suitability Issues

1586   When OPM has completed the contractor employee's background investigation, it shall
1587   send the report of investigation to the Department's Office of Executive Resources and
1588   Personnel Security (OERPS). If the report contains suitability issues, the OERPS will
1589   forward the report to the designated [issuing agency] official for review and adjudication.

1590   H.17.3.2       Suitability Standard and Criteria

1591   The Contractor shall provide all requested information to OPM per [issuing agency] for
1592   suitability determination according to suitability standard and criteria found at 5CFR 731.
1593   The Contractor employee suitability determinations request must include:

1594           OFI 86A (Request for Determination or Advisory), If known, list the position
1595            sensitivity in block 11.

1596           Contract employee resume or OF 612 (Optional Application for Federal
1597            Employment)

1598           OF 306 (Declaration for Federal Employment), signed and dated by the
1599            contractor employee. If an OF 306 was not completed, please note this on the
1600            OFI 86A.

1601           Record of contact with the contractor employee or other contacts/investigations
1602            made by the agency concerning the issues

1603   H.17.3.3       Unfavorable Suitability Determination

1604   If the designated [issuing agency] official determines that the contractor employee is
1605   unsuitable, the Contracting Officer will inform the Contractor in writing that the


1606   contractor employee is denied access to [issuing agency] facilities and/or information
1607   and information systems. If revoking access to [issuing agency] facilities and/or
1608   information and information systems negatively impacts the contractor employee's
1609   ability to perform, he or she shall be removed from the contract. Any removal of a
1610   contractor employee shall not be considered grounds for a delay or adjustment claim
1611   from the Contractor.

1612   H.17.4       Non-disclosure Agreement
1613    The Contractor shall require each contractor employee to review and sign a non-
1614   disclosure agreement when he or she begins work on the [issuing agency] contract.
1615   The Contractor must send the signed copy to the designated [issuing agency] official.



1619    ***If a public sector offer is selected by [issuing agency], certain FAR clauses may not
1620   apply to the work contracted to the public sector Offeror. However, such FAR clauses
1621   and other FAR requirements may apply to the work that is subcontracted to a non-
1622   federal provider. ***

1623   I.1     Notice Listing Contract Clauses Incorporated by Reference (Contract
1624           Clauses)
1625   The following contract clauses pertinent to this section are hereby incorporated by
1626   reference (by Citation Number, Title, and Date) in accordance with the clause at FAR
1627   "52.252-2 CLAUSES INCORPORATED BY REFERENCE" in Section I of this contract.
1628   See FAR 52.252-2 for an internet address (if specified) for electronic access to the full
1629   text of a clause.
1630         NUMBER              TITLE                                                 DATE
1631         52.202-1           DEFINITIONS                                           JUL 2004
1632         52.203-3           GRATUITIES                                            APR 1984
1633         52.203-5           COVENANT AGAINST CONTINGENT FEES                      APR 1984
1634         52.203-6           RESTRICTIONS ON SUBCONTRACTOR SALES SEP 2006
1635                            TO THE GOVERNMENT
1636         52.203-7           ANTI-KICKBACK PROCEDURES                              JUL 1995
1637         52.203-8           CANCELLATION, RESCISSION, AND RECOVERY JAN 1997
1638                            OF FUNDS FOR ILLEGAL OR IMPROPER
1639                            ACTIVITY
1640         52.203-10          PRICE OR FEE ADJUSTMENT FOR ILLEGAL OR JAN 1997
1641                            IMPROPER ACTIVITY
1642         52.203-12          LIMITATION ON PAYMENTS TO INFLUENCE                   SEP 2007
1643                            CERTAIN FEDERAL TRANSACTIONS
1644         52.204-2           SECURITY REQUIREMENTS                                 AUG 1996
1645         52.204-4           PRINTED OR COPIED DOUBLE-SIDED                        AUG 2000
1646                            ON RECYCLED PAPER


1647       52.204-7    CENTRAL CONTRACTOR REGISTRATION        JUL 2006
1648       52.204-9    PERSONAL IDENTITY VERIFICATION OF      SEP 2007
1649                   CONTRACTOR PERSONNEL
1653                   DEBARMENT
1654       52.215-2    AUDIT AND RECORDS--NEGOTIATION         JUN 1999
1655       52.215-8    ORDER OF PRECEDENCE--UNIFORM           OCT 1997
1656                   CONTRACT FORMAT
1657       52.215-14   INTEGRITY OF UNIT PRICES               OCT 1997
1661       52.219-9    SMALL BUSINESS SUBCONTRACTING PLAN     OCT 2001
1662                   ALTERNATE II (OCT 2001)
1663       52.219-16   LIQUIDATED DAMAGES-SMALL BUSINESS      JAN 1999
1664                   SUBCONTRACTING PLAN
1665       52.222-1    NOTICE TO THE GOVERNMENT OF LABOR      FEB 1997
1666                   DISPUTES
1667       52.222-3    CONVICT LABOR                          JUN 2003
1669       52.222-26   EQUAL OPPORTUNITY                      MAR 2002
1671                   VETERANS, OF THE VIETNAM ERA, AND OTHER
1672                   ELIGIBLE VETERANS
1673       52.222-36   AFFIRMATIVE ACTION FOR WORKERS WITH    JUN 1998
1674                   DISABILITIES


1675       52.222-37   EMPLOYMENT REPORTS ON SPECIAL          SEP 2006
1678       52.222-50   COMBATING TRAFFICKING IN PERSONS       AUG 2007
1679       52.223-6    DRUG-FREE WORKPLACE                    MAY 2001
1680       52.224-1    PRIVACY ACT NOTIFICATION               APR 1984
1681       52.224-2    PRIVACY ACT                            APR 1984
1682       52.225-1    BUY AMERICAN ACT--SUPPLIES             JUN 2003
1683       52.225-13   RESTRICTIONS ON CERTAIN FOREIGN        FEB 2006
1684                   PURCHASES
1685       52.227-1    AUTHORIZATION AND CONSENT              DEC 2007
1686       52.227-2    NOTICE AND ASSISTANCE REGARDING        DEC 2007
1688       52.227-14   RIGHTS IN DATA--GENERAL                DEC 2007
1689       52.227-17   RIGHTS IN DATA--SPECIAL WORKS          DEC 2007
1690       52.227-19   COMMERCIAL COMPUTER                    DEC 2007
1691                   SOFTWARE--LICENSE
1692       52.229-3    FEDERAL, STATE, AND LOCAL TAXES        APR 2003
1693       52.232-1    PAYMENTS                               APR 1984
1694       52.232-8    DISCOUNTS FOR PROMPT PAYMENT           FEB 2002
1695       52.232-11   EXTRAS                                 APR 1984
1696       52.232-17   INTEREST                               JUN 1996
1697       52.232-18   AVAILABILITY OF FUNDS                  APR 1984
1698       52.232-23   ASSIGNMENT OF CLAIMS                   JAN 1986
1699       52.232-33   PAYMENT BY ELECTRONIC FUNDS--CENTRAL OCT 2003
1700                   CONTRACTOR REGISTRATION
1701       52.233-3    PROTEST AFTER AWARD                    AUG 1996
1702       52.233-4    APPLICABLE LAW FOR BREACH OF           OCT 2004


1703                   CONTRACT CLAIM
1704       52.237-3    CONTINUITY OF SERVICES                 JAN 1991
1705       52.239-1    PRIVACY OR SECURITY SAFEGUARDS         AUG 1996
1706       52.242-15   STOP WORK ORDER                        AUG 1989
1707       52.242-13   BANKRUPTCY                             JUL 1995
1708       52.243-1    CHANGES--FIXED PRICE                   AUG 1987
1709                   ALTERNATE I (APR 1984)
1710       52.244-6    SUBCONTRACTS FOR COMMERCIAL ITEMS      MAR 2007
1711       52.246-23   LIMITATION OF LIABILITY                FEB 1997
1712       52.248-1    VALUE ENGINEERING                      FEB 2000
1713                   ALTERNATE I (APR 1984)
1714       52.249-2    TERMINATION FOR CONVENIENCE OF THE     MAY 2004
1715                   GOVERNMENT (FIXED-PRICE)
1716       52.249-8    DEFAULT (FIXED-PRICE SUPPLY AND        APR 1984
1717                   SERVICE)
1718       52.252-2    CLAUSES INCORPORATED BY REFERENCE      FEB 1998
1719       52.253-1    COMPUTER GENERATED FORMS               JAN 1991
1720       52.222-39   NOTIFICATION OF EMPLOYEE RIGHTS        DEC 2004
1722       52.222-41   SERVICE CONTACT ACT OF 1965, AS        JUL 2005
1723                   AMENDED
1726                   YEAR AND OPTION CONTRACTS)             NOV 2006
1727       52.222-49   SERVICE CONTRACT AWARD – PLACE OF      MAY 1989
1728                   PERFORMANCE UNKNOWN
1729       52.232-25   PROMPT PAYMENT                         OCT 2008
1730       52.246-20   WARRANTY OF SERVICES                   MAY 2001


1731           52.234-3           NOTICE OF EARNED VALUE MANAGEMENT
1732                              SYSTEMS – POST AWARD IBR                                APR 2008
1733           52.234-4           EARNED VALUE MANAGEMENT SYSTEM                          JUL 2006

1734   I.1.1          52.252-2 Clauses Incorporated By Reference
1735   This contract incorporates one or more clauses by reference, with the same force and
1736   effect as if they were given in full text. Upon request, the Contracting Officer will make
1737   their full text available. Also, the full text of a clause may be accessed electronically at
1738   this/these address(es):
1740           52.253-1           COMPUTER GENERATED FORMS                                JAN 1991

1741   I.1.2          52.222-39 Notification of Employee Rights Concerning Payment of
1742                  Union Dues or Fees

1744   I.1.3          52.222-41 Service Act of 1965, As Amended

1746   I.1.4          52.222-43 Fair Labor Standards Act and Service Act – Price
1747                  Adjustment (Multiple Year and Option Contracts)

1749   I.1.5          52.222-49 Service Contract Act – Place of Performance Unknown

1751   I.1.6          52.232-25 Prompt Payment

1753   I.1.7          52.246-20 Warranty of Services

1755   I.1.8          52.234-3 Notice of Earned Value Management Systems (EVMS) – Post
1756                  Award IBR

1758   I.1.9          52.234-4 Earned Value Management Systems (Jul 2006)


1760   I.2            Key Personnel
1761   Before changing an individual identified as key personnel, the Contractor shall notify the
1762   Contracting Officer in writing, no less than 14 business days in advance and shall
1763   submit written justification (including the name and qualifications of the proposed
1764   substitute(s). The proposed substitute(s) shall possess qualification equal to or superior
1765   to those of the key personnel being replaced. The Contractor shall not substitute key
1766   personnel without written consent from the Contracting Officer.
1767           [Insert list of applicable subcontractors.]

1768   I.3            Wage Determinations 05-2103 (Rev. 4), Washington, DC Metropolitan
1769                  Area
1770   For updates and alternate locations see




1775   J.1           FM Due Diligence Cover Letter and Checklist
1776  (download section 2.1)




1781   K.1           52.204-8 Annual Representations and Certifications (JAN 2006)


1785   K.2               Signature Block
1786   I, the undersigned, do hereby attest that all representations and certifications made in
1787   this Section K are true.
1788   Also, I, the undersigned, am aware of the penalties prescribed in 18 U.S. Code 1001 for
1789   making false statements in offers; and I am legally authorized to bind the company or
1790   organization represented.
1791           __________________________________________ _____________
1792           (Signature)                                                  (Date)
1794           __________________________________________
1795           (Typed or Printed Name)
1797           __________________________________________
1798           (Title)
1800           __________________________________________
1801           (Solicitation Number)
1802           __________________________________________
1803           (Name of Company/Organization Represented)
1805           __________________________________________
1806           (DUNS Number)
1808           __________________________________________
1809           (Address, including Zip Code)
1810           _______________________________________
1811           (Telephone Number, including Area Code)



1814   L.1           Notice Listing Solicitation Provisions Incorporated By Reference
1815                 (Instructions, Conditions, and Notices to Offerors)
1816   The following solicitation provisions pertinent to this section are hereby incorporated by
1817   reference (by Citation Number, Title, and Date) in accordance with the FAR provision at
1819   Section L of this solicitation. See FAR 52.252-1 for an internet address (if specified) for
1820   electronic access to the full text of a provision.
1821   NUMBER                    TITLE                                                  DATE
1822   52.215-1                  INSTRUCTIONS TO OFFERORS--COMPETITIVE JAN 2004
1823                             ACQUISITION ALTERNATE I (OCT 1997)
1824   52.222-24                 PREAWARD ON-SITE EQUAL OPPORTUNITY                    FEB 1999
1825                             COMPLIANCE EVALUATION
1826   52.214-34                 SUBMISSION OF OFFERS IN THE ENGLISH                   APR 1991
1827                             LANGUAGE
1828   52.214-35                 SUBMISSION OF OFFERS IN US CURRENCY                   APR 1991

1829   L.2           52.216-1 Type of Contract (APR 1984)
1830   The Government contemplates award of an Indefinite Delivery / Indefinite Quantity
1831   (IDIQ) contract resulting from this solicitation. Task Orders issued under the resulting
1832   contract will be issued on either a Firm Fixed Price (FFP) or Time and Materials (T&M)
1833   basis.

1834   L.3           52.233-2 Service of Protest (SEP 2006)
1835   (a) Protests, as defined in section 33.101 of the Federal Acquisition Regulation, that are
1836   filed directly with an agency, and copies of any protests that are filed with the General
1837   Accountability Office (GAO), shall be served on the Contracting Officer (addressed as
1838   follows) by obtaining written and dated acknowledgment of receipt from:



                          [Enter Issuing agency Contractor Officer name here]
                                           Contracting Officer

        HAND-CARRIED ADDRESS                                 MAILING ADDRESS

        [Enter Issuing agency address here]                  [Enter Issuing agency Address here]

1841   (b) The copy of any protest shall be received in the office designated above within one
1842   day of filing a protest with the GAO.

1843   L.4           52.252-1 Solicitation Provisions Incorporated By Reference (FEB
1844                 1998)
1845    This solicitation incorporates one or more solicitation provisions by reference, with the
1846   same force and effect as if they were given in full text. Upon request, the Contracting
1847   Officer will make their full text available. The Offeror is cautioned that the listed
1848   provisions may include blocks that must be completed by the Offeror and submitted with
1849   its quotation or offer. In lieu of submitting the full text of those provisions, the Offeror
1850   may identify the provision by paragraph identifier and provide the appropriate
1851   information with its quotation or offer. Also, the full text of a solicitation provision may be
1852   accessed electronically at this/these address(es):

1854   L.5           Special Notice to Offerors

1855   L.5.1         Consideration of Non-FSIO-Certified Software
1856   [Issuing agency] is aware that some financial management software product versions
1857   may be in the process of certification testing by FSIO and may become certified within
1858   the solicitation and/or award period. If the Offeror chooses to propose their
1859   implementation of their Financial Management (FM) Service based on the presumption
1860   of FSIO certification prior to award and implementation, Offerors must include pricing for
1861   this major software release in accordance with their proposed approach in the Technical
1862   and Management Approach Volume(s).


1864   L.5.2         Pre-Proposal Reading Room
1865   [Issuing agency] intends to leverage the investment from previous financial
1866   management efforts on this contract. However, given the sensitive nature and volume of
1867   information related to those previous efforts, that information is not included as
1868   attachments to this solicitation. Instead, [the issuing agency] will provide the location
1869   with copies of relevant information available for review by potential Offerors.
1870   Appointments to use the Reading Room are available to each potential Offeror by
1871   contacting the Contract Specialist by 12:00 p.m. Eastern Time, [date]. Each
1872   appointment is one business day, from 8:00 a.m. to 5:00 p.m., and appointments are
1873   available starting [date] and ending [date]. Potential Offerors may only sign up for one
1874   appointment initially to allow all potential Offerors the opportunity to sign up for a
1875   Reading Room appointment. All appointment dates that remain open as of [time, date],
1876   will then be made available to Offerors who had a Reading Room appointment
1877   scheduled from [date] through [date].
1878   Materials provided in the Reading Room may not be removed or copied in any manner
1879   conceivable, except that handwritten notes taken by potential Offerors are allowed. The
1880   Reading Room will be monitored by federal or contractor personnel to help ensure no
1881   materials are removed; however, these monitoring personnel will not be able to provide
1882   information about the acquisition and should not be asked acquisition questions by
1883   potential Offerors.

1884   L.6           Instructions for the Preparation of Proposals

1885   L.6.1         Failure to Submit Requested Information
1886   Failure to submit any of the information requested by this solicitation may be cause for
1887   unfavorable consideration and/or elimination from the competition.

1888   L.6.2         Use of Support Contractors
1889   Offerors are advised that the Government will utilize support contractors to assist during
1890   the source selection. The exclusive responsibility for source selection will reside with the
1891   Government. Proprietary information submitted in response to this solicitation will be
1892   protected from unauthorized disclosure as required by Subsection 27 of the Office of
1893   Procurement Policy Act as amended (41 U.S.C. 423) (hereinafter referred to as "the
1894   Act") as implemented in the FAR. These support contractors are bound contractually by
1895   non-disclosure clauses and precluded from submitting an offer either as a prime or sub-
1896   contractor. Contractor personnel assisting in the proposal evaluation are procurement
1897   officials within the meaning of the Act, and will take all necessary action to preclude
1898   unauthorized use or disclosure of a competing Offeror’s proprietary data.


1901   L.6.3          Proposals Become Government Property
1902   Upon receipt, all proposals become Government property. After contract award, the
1903   unsuccessful Offerors will be required to return to the Government all information, data,
1904   drawings, specifications, etc., provided to the Offerors by the Government.

1905   L.6.4          Availability of Funds Contingency
1906   The Government's obligation under this contract is contingent upon the availability of
1907   funds from which payment for contract purposes can be made. No legal liability on the
1908   part of the Government for any payment may arise until funds are made available to the
1909   Contracting Officer for this contract and until the Contractor receives notice of such
1910   availability, to be confirmed in writing by the Contracting Officer. The Government
1911   reserves the right to phase the project based upon funds available. Any phases will be
1912   based on the successful Offeror's price/cost proposal submitted in accordance with
1913   Section L herein.

1914   L.6.5          Confidential Information
1915   The Freedom of Information Act (FOIA) and its amendments have resulted in an
1916   increasing number of requests from outside the Government for copies of contract
1917   qualifications and proposals submitted to federal agencies. If an Offeror’s submissions
1918   contain information that the Offeror believes should be withheld from such requestors
1919   under FOIA on the grounds that they contain ―trade secrets and commercial or financial
1920   information‖ [5 USC§552(b) (4)], the Offeror should mark its submissions in the
1921   following manner:
1922          The following notice should be placed on the title page:

1923           “Some parts of this document, as identified on individual pages, are considered
1924           by the submitter to be privileged or confidential trade secrets or commercial or
1925           financial information not subject to mandatory disclosure under the Freedom of
1926           Information Act. Material considered privileged or confidential on such grounds is
1927           contained on page(s) _______.”

1928          Each individual item considered privileged or confidential under FOIA
1929           should be marked with the following notice:

1930           “The data or information is considered confidential or privileged, and is not
1931           subject to mandatory disclosure under the Freedom of Information Act.”




1934   L.7           Solicitation Response Requirements

1935   L.7.1         General
1936   The Offeror shall submit documentation illustrating their approach for satisfying the
1937   requirements of this solicitation. Proposals must be clear, concise, coherent, and
1938   prepared in sufficient detail for effective evaluation of the Offeror’s proposal against the
1939   evaluation criteria. Also, this documentation shall cover all aspects of this solicitation
1940   and include the Offeror’s approach for organizational change management and program
1941   management activities. Proposals must clearly demonstrate how the Offeror intends to
1942   accomplish the project and must include convincing rationale and substantiation of all
1943   claims. Unnecessarily elaborate brochures or other presentations beyond those
1944   sufficient to present a complete, effective response to the solicitation are not desired
1945   and shall not be evaluated.
1946   The Offeror shall describe its proposal, through the use of graphs, charts, diagrams and
1947   narrative, in sufficient detail for the Government to understand and evaluate the nature
1948   of the approach. In its evaluation and risk assessment, the Government will consider the
1949   degree of substantiation of the proposed approaches in the proposal volumes and in
1950   response to any discussions.
1951   All correspondence in conjunction with this solicitation should be directed to the
1952   Government's Point of Contact (POC) identified below:

                                    POC: [Enter issuing agency POC]

                                  Phone: [Enter issuing agency POC
                                         phone number here]

                                     Fax: [Enter issuing agency fax
                                          number here]

                                  E-mail: [Enter issuing agency e-mail
                                          address here]

1953   L.7.2         Technical and Management Approach Volume Requirements
1954                 (Volume I)
1955   Volume I shall consist of the Offeror’s Technical and Management Approach in
1956   response to the Statement of Objectives (SOO). The Offeror shall provide a total
1957   solution that includes financial management software, implementation services,
1958   application management services, and hosting and IT Administration that addresses all
1959   of the objectives and requirements in the SOO. This volume shall consist, at minimum,
1960   of the following sections:


1961            Executive Summary. The Offeror shall provide a summary of their
1962             technical and management approach, highlighting any key or unique
1963             features and the Offeror’s value proposition to [issuing agency]
1964            Performance Work Statement (PWS). The Offeror shall provide a PWS in
1965             response to the SOO provided in this solicitation as part of Volume IV. The
1966             PWS shall incorporate all of the objectives and requirements set forth in
1967             the SOO, be submitted in the Offeror’s format, and include the same
1968             performance metrics that are included in the Offeror’s proposed Quality
1969             Assurance Surveillance Plan (QASP), Quality Assurance Plan (QAP), and
1970             proposed Service Level Agreement (SLA). The PWS will be incorporated
1971             into the contract at the time of award.
1972            Technical and Management Approach. In alignment with the proposed
1973             PWS, the Offeror shall describe its recommended approach for meeting all
1974             of the objectives of the shared service provider project. The Offeror shall
1975             describe its approach in each of the following areas and how it will meet
1976             the objectives in each area as presented in the SOO.

1977   L.7.2.1          Technical Approach

1978   The Offeror’s response shall:
1979             (a) Provide a description of the proposed financial system’s overall functional and
1980             technical capabilities with particular emphasis on any pre-configured or custom
1981             functionality provided by the Offeror;
1982             (b) Provide information on the specific core financial functionality and system
1983             features that support [issuing agency]’s financial management processes;
1984             (c) Particularly address the ability of the proposed solution to support those
1985             [issuing agency] processes that are not considered ―core‖ by the Financial
1986             System Integration Office (FSIO), but that are provided to [issuing agency] as
1987             part of the proposed solution;
1988             (d) Discuss the architecture and other technical elements that comprise the
1989             proposed solution’s technical environment (e.g., Service Oriented Architecture
1990             (SOA) enablement, scalability, ability to integrate with other commercial-off-the-
1991             shelf (COTS) products and legacy systems, development tools, etc.);
1992             (e) Provide a list of the reports, queries, and preconfigured workflows that are
1993             standard in the proposed solution. For standard reports, a one-page sample of
1994             each report shall be included in the proposal in Volume IV;
1995             (f) Provide a summary of the Offeror’s findings as a result of completing the
1996             Requirements Template included in [Section X] of this solicitation. The
1997             requirements included in the Requirements Template represent (1) the FSIO
1998             mandatory requirements, (2) FSIO value-added requirements, including those
1999             that [issuing agency] defines as mandatory, and (3) [issuing agency] -specific
2000             requirements that are beyond those defined by FSIO. Instructions for completing


2001           the template, which is a Microsoft (MS) Excel spreadsheet, are included on the
2002           first worksheet of the document. The Offeror’s completed Requirements
2003           Template shall be included in Volume IV;
2004           (g) Include a statement and any supporting information that demonstrates that all
2005           proposed software products will be supported for the term of the contract, to
2006           include option periods, if exercised. ―Supported‖ is defined here as continued
2007           compliance with FSIO requirements and any legislative, OMB, Treasury or other
2008           federal mandates affecting financial management and reporting requirements
2009           that are enacted or promulgated after award of this contract. A letter certifying
2010           this support shall be included in Volume IV;
2011           (h) Provide the estimated schedule for major release upgrades over the period of
2012           performance for this contract as part of the MS Project-based schedule required
2013           as part of the response;
2014           (i) Identify any assumptions made in preparing this portion of the Offeror’s
2015           response; and
2016           (j) Describe the Offeror’s approach for remaining current against FSIO tested
2017           requirements.

2018   L.      Implementation Services:

2019   The Offeror shall provide a description of the implementation services proposed, which
2020   shall include, at a minimum, a discussion of the following:
2021           (a) An implementation strategy that addresses fulfillment of those [issuing
2022           agency] deliverables identified as an SSP responsibility in [Section X], regardless
2023           of the Offeror’s internal implementation strategy. The Offeror’s implementation
2024           strategy shall also include a description of whether the Offeror is proposing a
2025           phased approach to the implementation. If so, the Offeror shall clearly describe
2026           the scope of each phase (e.g., system functionality, user groups, etc.);
2027           (b) The Offeror’s proposed implementation schedule, including all dependent and
2028           concurrent tasks. The schedule provided shall support full operational capability
2029           of the new financial system in a hosted environment by [date]. It must also
2030           comply with the WBS, WBS Dictionary, and Schedule template provided as
2031           attachments in Section J of the RFP;
2032           (c) The Offeror’s strategy for working with [issuing agency] to configure and fully
2033           implement (including Authority to Operate) the shared service provider by [date].
2034           (d) The Offeror’s requirements gap analysis approach, including a description of
2035           the Offeror’s baseline system configuration and the manner in which gaps
2036           between the baseline software and [issuing agency] needs will be identified;
2037           (e) The Offeror’s system configuration and interface development approach;


2038           (f) The Offeror’s testing approach;
2039           (g) The Offeror’s data conversion approach, to include the levels at which data
2040           should be converted for all open documents, grants (entire history), and the last
2041           fiscal year’s transactions;
2042           (h) The Offeror’s training development and delivery approach, including post go-
2043           live training and the ongoing measurement of [issuing agency] personnel’s
2044           competency to apply targeted training to areas of deficiency;
2045           (i) The Offeror’s documentation processes and procedures and the specific
2046           documents that will be developed and delivered to [issuing agency];
2047           (j) Any assumptions made in preparing this portion of the Offeror’s response.

2048   L.     Hosting & IT Administration

2049   The Offeror shall provide a detailed description of the hosting and IT Administration
2050   services proposed to support and host the proposed solution, consistent with the goals
2051   and objectives of the FMLoB initiative. The description provided shall address, at a
2052   minimum:
2053   (a) The Offeror’s proposed hosting model, including identifying whether [issuing agency]
2054   will be provided with a shared or single instance of the proposed financial system;
2055   (b) The Offeror’s system change control management processes and procedures to
2056   include explanations of how hosted customers are included in the process and how it is
2057   determined what new functionality will be incorporated into future releases;
2058   (c) The Offeror’s user support approach, methodologies, tools, and reporting
2059   mechanisms that will satisfy the objectives described in the SOO;
2060   (d) A summary of the Offeror’s findings after completing the FMLoB Due Diligence
2061   Checklist for SSPs. The completed Due Diligence Checklist shall be included in Volume
2062   4;
2063   (e) The scope of the Offeror’s operations and maintenance services and the
2064   methodologies and tools used to support those services;
2065   (f) The Offeror’s historic performance as a hosting provider, including discussion of the
2066   system availability rates for previous and current hosting and IT Administration
2067   customers;
2068   (g) The Offeror’s Continuity of Operations approach;
2069   (h) The Offeror’s Service Level Agreement (SLA), which shall be included in its entirety
2070   in Volume 4. The SLA shall describe the specific approach and methodology for hosting
2071   and IT administration performance measurement. The SLA proposed shall, at a
2072   minimum, adhere to the recommendations and general structure set forth in Sections
2073   2.5 and 2.6 of the FMLoB Migration Planning Guidance. In addition, the Offeror shall


2074   describe its approach for proposing updates to the SLA and addressing performance
2075   deficiencies per the SLA. The Offeror shall ensure that the performance metrics listed in
2076   the proposed SLA align with the information metrics included in the PWS and QASP.
2077   (i) Any assumptions made in preparing this portion of the Offeror’s response.

2078   L.    Application Management Services

2079   The Offeror shall describe their approach to providing the software and services for
2080   running and managing access to the proposed SSP and the interfaces with feeder
2081   systems that exchange data with the FM SSP.

2082   L.    Professional Services

2083   The Offeror may be requested to provide Subject Matter Experts (SME(s)) for financial
2084   management services or financial management information systems services
2085   throughout the system life cycle. The Offeror shall describe their approach to providing
2086   SMEs who understand FSIO requirements and financial issues supported or potential
2087   supported by vendor software applications.

2088   L.    Deliverables

2089   The Offeror shall provide a table that summarizes all proposed deliverables associated
2090   with their methodologies, approaches, processes and plans that are discussed in their
2091   technical and management proposal. Deliverables shall include, at a minimum, those
2092   [issuing agency] deliverables identified as an SSP responsibility in the Attachment J.1,
2093   Due Diligence Checklist, regardless of the technical approach proposed. This table shall
2094   include proposed due dates for all deliverables that align with the proposed schedule
2095   included with the Offeror’s proposal.
2096   In development of the deliverable table and deliverable due dates, the Offeror should
2097   consider that [issuing agency] intends for the Contractor to provide deliverable items to
2098   [issuing agency]’s Contracting Officer (CO), the Contracting Officer’s Technical
2099   Representative (COTR), and any Technical Point of Contact (TPOC). The COTR shall
2100   coordinate the review of each deliverable. The COTR will provide comments to the
2101   Contractor within ten (10) working days of the submission of each item.
2102   In the case of document deliverables, the Contractor shall incorporate [issuing agency]
2103   comments and return a revised final deliverable document to the COTR within five (5)
2104   working days of receipt. All deliverables shall become the property of [issuing agency].
2105   Each document deliverable shall be submitted in three (3) hard copies and one (1) copy
2106   in an acceptable electronic format, using Microsoft Excel 2003, Microsoft Word 2003,
2107   Microsoft Project 2003, or any other format that is mutually agreed upon by the COTR
2108   and the Contractor. The time frames and format requirements apply to all written reports
2109   and documents to be delivered to [issuing agency].
2110   Technical approaches shall be clearly defined and supported by deliverables, tasks,
2111   timeframes, assumptions, and constraints. Technical approaches should not merely


2112   parrot the objectives set forth in the SOO or state that the ―Offeror will perform the
2113   statement of objectives‖ or use similar verbiage.

2114   L.7.2.2         Management Approach

2115   Volume I shall also describe the Offeror’s planned approach for managing the execution
2116   of its solution. At a minimum, the Management Approach shall include the following
2117   sections:

2118   L.       Organizational Structure

2119   The Offeror shall describe its proposed project organization structure, including the
2120   roles and responsibilities of each company or organization that is a member of the
2121   team. The Offeror shall also indicate the positions of key personnel and proposed
2122   interfaces with the [issuing agency] PMO. In the event teaming or subcontracting
2123   arrangements are proposed for accomplishing the required work, the Offeror shall
2124   describe how the prospective team subcontractors were chosen as part of the Offeror's
2125   proposed team and rationale for selection. The Offeror shall describe the prime
2126   contractor's management structure and internal controls to ensure efficient and quality
2127   performance of team subcontractors.

2128   L.       Project Plan

2129   The Offeror shall describe the proposed tasks that the Offeror will perform to satisfy all
2130   of [issuing agency]’s objectives. The Project Plan, which shall consist of a Work
2131   Breakdown Structure (WBS), WBS Dictionary, and a master schedule (all based on
2132   attachments provided in Section J of the RFP), should highlight the sequence of events
2133   that the Offeror will use to fulfill the proposed objectives and requirements, consistent
2134   with the Offeror’s proposed pricing. This Plan should allow [issuing agency] to clearly
2135   identify and understand the proposed approach, tasks, and timeframes. The Offeror
2136   shall also clearly indicate which tasks the Offeror expects to be performed by [issuing
2137   agency]. The Offeror shall describe the roles, responsibilities, anticipated time
2138   commitment, and necessary skill set for each [issuing agency] resource that the Offeror
2139   includes in the Project Plan. It is important to note that the Project Plan in the proposal
2140   of the selected Offeror shall be used for the Pre-Award Integrated Baseline Review
2141   (IBR). Significant changes should not be required to the Project Plan prior to the Pre-
2142   Award IBR. Any changes shall require justification by the Offeror and approval by
2143   [issuing agency].

2144   L.       Project Management

2145   The Offeror shall provide a description of the proposed methodologies and tools that will
2146   be utilized by the Offeror for the management and execution of the Offeror’s solution.
2147   This includes, at a minimum, the following:
2148            Project management methodologies, including any certifications that the
2149             Offeror’s organization has and will apply to this work. Such methodologies
2150             should address, at a minimum, the following project management areas:


2151           -   Schedule management
2152           -   Scope management
2153           -   Project financial management
2154           -   Communications management (e.g., status reporting)
2155          Project start-up approach.
2156          Approach for collaborating with the PMO and other [issuing agency]
2157           contractors, including an explanation of communication strategies and
2158           processes for identifying and resolving problems. The Offeror shall also
2159           propose how the relationship between the PMO and implementation
2160           organizations can operate most effectively and efficiently in support of a
2161           successful project completion. Additional contractor support is being
2162           provided to [issuing agency] in the area of PMO support and Independent
2163           Validation & Verification (IV&V).
2164          Exit strategy and transition plan that address situations such as
2165           transitioning to another SSP or hosting provider at the end of the contract
2166           period; and transitioning to another provider in the event that the
2167           Government elects not to exercise an option period or elects to terminate
2168           the contract for default or convenience.
2169          If the Offeror’s proposed provider of implementation services is different
2170           than the provider of other services, the management approach should
2171           include processes and procedures for ensuring a seamless transition of
2172           the project management responsibilities from the implementation to the
2173           Operations & Maintenance (O&M) phases of the project.

2174   L.      Risk Management

2175   The Offeror shall describe its proposed approach to proactively managing and
2176   mitigating risks throughout the duration of the contract, from pre-implementation to
2177   operations and maintenance. The approach shall include the identification of major risks
2178   encountered on similar projects and how the proposed approach mitigates those risks.

2179   L.      Quality Assurance Surveillance Plan (QASP)

2180   The objective of the QASP is to specify all work requiring surveillance by the
2181   Government and the method(s) of surveillance to ensure that the Contractor performs in
2182   accordance with the performance metrics and standards defined in the PWS. Since the
2183   Government will measure the Contractor’s performance against standards in the PWS,
2184   the QASP is interdependent with the PWS, and must be coordinated with that
2185   document. The Offeror is strongly encouraged to propose additional metrics to
2186   demonstrate its commitment to project success and its level of expertise in financial
2187   systems software, implementation services, application management, and hosting and
2188   IT administration. Once the QASP has been mutually agreed upon by [issuing agency]
2189   and the successful Offeror prior to contract award, the Offeror and [issuing agency] will
2190   comply with the plan for the life of the contract. In accordance with the QASP, [issuing
2191   agency] will make quantitative and qualitative assessments of the Contractor’s
2192   performance. [Issuing agency] retains the right to initiate modifications to the


2193   surveillance process at any time. Any proposed modifications shall be reviewed with the
2194   Contractor and, once mutually agreed upon by [issuing agency] and the Contractor,
2195   shall be implemented for the remainder of the contract.
2196   The Offeror shall include a description of the methodology, processes, data collection
2197   systems, tools, techniques, and resources that the Offeror proposes to effectively
2198   manage the delivery of products and services that meet or exceed the objectives
2199   described in the SOO. The QAP shall describe the Offeror’s systematic method for
2200   providing confidence that the Offeror’s products and services are developed and
2201   delivered according to established processes and are of the highest quality. It shall
2202   define the policy for quality assurance activities, the organizational structure of the
2203   quality assurance group, roles and responsibilities of the quality assurance group, and a
2204   schedule for reviews and audits. The proposed approach shall provide [issuing agency]
2205   with complete visibility and unrestricted self-service access to quality control review and
2206   audit results.

2207   L.     Earned Value Management

2208   The Offeror shall describe its processes and tools for managing and reporting earned
2209   value in accordance with American National Standards Institute/Electronic Industries
2210   Association (ANSI/EIA) Standard 748. The approach shall also include a description of
2211   the Offeror’s Earned Value Management System (EVMS) and clearly state that the
2212   EVMS requirements proposed will be applied to any subcontractors utilized, in
2213   accordance with FAR 34.201(d) and 52.234-3(c). If the Offeror has an EVMS that is
2214   compliant with ANSI/EIA Standard 748, then documentation of this compliance by a
2215   cognizant federal agency shall be included in Volume 4. If the Offeror’s EVMS has not
2216   been certified as compliant with ANSI/EIA Standard 748 by a cognizant federal agency
2217   at the time of award, then the Offeror shall describe in its proposal its plan for obtaining
2218   compliance within 30 calendar days of contract award. Any costs associated with
2219   implementing an EVMS system that is compliant with ANSI/EIA Standard 748 will not be
2220   reimbursed by [issuing agency]. [Issuing agency] will conduct a pre-award Integrated
2221   Baseline Review (IBR).
2222   (a) The Offeror shall provide documentation that a cognizant federal agency has
2223   determined that the proposed EVMS complies with the EVMS guidelines in ANSI/EIA
2224   Standard - 748 (current version at time of solicitation).
2225           (1)   Documentation must include the following information:
2226          Name of contracting activity
2227          Contract number
2228          Contract type
2229          Total contract value
2230          Contract work
2231          Name of contracting officer, telephone and fax number and email address
2232          Name of government program manager, telephone and fax number and
2233           email address


2234   The Government reserves the right to contact customers that the Offeror identifies and
2235   solicit further information about the Offeror’s EVMS. The accuracy of EVMS data,
2236   including phone numbers of the points of contact are the full responsibility of the Offeror,
2237   and inaccuracy may result in non-consideration of the reference. Other related EVMS
2238   information may be sought and used for evaluating completeness and accuracy of the
2239   contractor's proposals. EVMS information may be obtained from a variety of sources,
2240   including other government contracting project managers and other government
2241   contracting activities reports.
2242   Offerors shall identify the major subcontractors, or major subcontracted effort if major
2243   subcontractors have not been selected, planned for application of the guidelines. The
2244   prime Contractor and the Government shall agree to subcontractors selected for
2245   application of the EVMS guidelines.
2246   The Government will conduct an IBR, prior to contract award. The objective of the IBR
2247   is for the Government and the Contractor to jointly assess technical areas, such as the
2248   Contractor’s planning, to ensure complete coverage of the contract requirements,
2249   logical scheduling of the work activities, adequate resources, methodologies for earned
2250   value including, but not limited to Budgeted Cost for Work Performed (BCWP) and
2251   identification of inherent risks. This IBR will be scheduled with Offeror(s) notified by the
2252   CO of inclusion in the competitive range and notified of [issuing agency]’s desire for the
2253   IBR.
2254   The Government will also conduct a Post Award IBR. The purpose of the Post Award
2255   IBR is to verify the technical content and the realism of the related performance
2256   budgets, resources, and schedules. It should provide a mutual understanding of the
2257   inherent risks in Offeror’s contracted performance plans and the underlying
2258   management control systems, and it should formulate a plan to handle these risks. The
2259   IBR is a joint assessment by the Offeror and the Government, of the:
2260          Ability of the project’s technical plan to achieve the objectives of the scope
2261           of work.
2262          Adequacy of the time allocated for performing the defined tasks to
2263           successfully achieve the project schedule objectives;
2264          Ability of the Performance Measurement Baseline (PMB) to successfully
2265           execute the project and attain cost objectives, recognizing the relationship
2266           between budget resources, funding, schedule, and scope of work;
2267          Availability of personnel, facilities, and equipment when required, to
2268           perform the defined tasks needed to execute the program successfully;
2269          Degree to which the management process provides effective and
2270           integrated technical/schedule/cost planning and baseline control.
2271   The timing and conduct of the post-award IBR shall be held within 30 calendar days of
2272   award in accordance with agency procedures.
2273   (b)   If the Offeror proposes to use a system that has not been determined to be in
2274   compliance, as identified in EVMS guidelines in ANSI/EIA Standard - 748 (current


2275   version at time of solicitation), the Offeror shall submit a comprehensive plan for
2276   compliance with the EVMS guidelines.
2277           The plan shall -
2278          Describe the EVMS the Offeror intends to use in performance of the
2279           contracts;
2280          Distinguish between the Offeror’s existing management system and
2281           modifications proposed to meet the guidelines;
2282          Describe the management system and its application in terms of the
2283           EVMS guidelines;
2284          Describe the proposed procedure for administration of the guidelines, as
2285           applied to subcontractors; and
2286          Provide documentation describing the process and results of any third-
2287           party or self-evaluation of the system’s compliance with the EVMS
2288           guidelines.
2289              (1) The Offeror shall provide information and assistance as required by the
2290              Contracting Officer to support review of the plan.
2291              (2) The Government will review and approve the Offeror’s plan for an EVMS
2292              before contract award.
2293              (3) The Offeror’s EVMS plan must provide milestones that indicate when the
2294              Offeror anticipates that the EVMS will be compliant with the ANSI/EIA
2295              Standard -748 guidelines.
2296            (c)   The Integrated Master Schedule (IMS) is an integrated schedule
2297           containing the networked, detailed tasks necessary to ensure successful
2298           program execution. The IMS is vertically traceable to the Project Management
2299           Plan (PMP), the Work Breakdown Structure (WBS) and the Statement of
2300           Objectives (SOO). The IMS is used to verify attainability of contract objectives, to
2301           evaluate progress toward meeting contract objectives, and to integrate the
2302           program schedule activities with all related components. The IMS shall indicate
2303           all contract events, significant accomplishments, and accomplishment criteria
2304           and be supported by detailed tasks, activities, and milestones and their
2305           dependencies such that it calculates an accurate critical path. That IMS shall be
2306           in a Microsoft Project 2003 compatible format and allow the presentation of Gantt
2307           and Network Diagram charting. The IMS shall be provided in hard and soft copy
2308           as part of Volume IV of the Offeror’s proposal and be priced as an individual item
2309           in the price proposal.
2310              (1) The IMS is required to include significant external interfaces and critical
2311              items from suppliers, teammates, or other detailed schedules that depict
2312              significant and/or critical elements and Government furnished equipment or
2313              information dependencies for the entire contractual effort in a single
2314              integrated network. The determination of significant and critical shall be
2315              agreed to by the Government.


2316           (2) The IMS status shall be reported according to the Offeror’s management
2317           control system and shall be submitted no less frequently than monthly (unless
2318           requested otherwise by the Government). The IMS may reflect data either as
2319           of the end of the calendar month or as of the Offeror’s accounting period
2320           cutoff date, provided it is consistent and traceable to the Contract
2321           Performance Report (CPR) (if applicable).
2322           (3) Format: The IMS shall be created using the Microsoft Project 2003
2323           scheduling software application. Unless otherwise directed by the
2324           Government, the IMS shall be delivered electronically in the native digital
2325           format (i.e., an electronic file produced by the Offeror’s scheduling tool).
2326           (4) Content: The schedule shall contain the contract milestones,
2327           accomplishments, and discrete tasks/activities (including planning packages
2328           where applicable) from contract award to the completion of the contract. The
2329           schedule shall be an integrated, logical network-based schedule that
2330           correlates to the WBS, and is vertically and horizontally traceable to the
2331           cost/schedule reporting instrument used to address variances. The schedule
2332           shall have a numbering system that provides traceability to the PMP and
2333           SOO. It shall contain contractual milestones and descriptions and display
2334           summary, intermediate, and detailed schedules, and periodic analysis of
2335           progress to date. It shall include fields and data that enable the user to
2336           access the information by product, process, or organizational lines.
2337           (5) Contract Milestones and Definitions: Key programmatic events, which
2338           define progress and completion for each WBS element, along with the
2339           definition for successful completion of the milestone.
2340           (6) Summary Master Schedule, which is a top-level schedule of key
2341           tasks/activities and milestones at the summary level of the WBS and PMP. It
2342           shall be an integrated roll up of the intermediate and detailed schedules (see
2343           (7) Intermediate Schedules and (8) Detailed Schedules below) (vertical
2344           integration).
2345           (7) Intermediate Schedules: Mid-level contract schedules that include key
2346           tasks/activities and milestones and all associated accomplishments in the
2347           summary master schedule, traceable to the Consolidated Work Breakdown
2348           Structure (CWBS) element or Integrated Master Plan (IMP) event as
2349           necessary to display work effort at the intermediate level of summarization.
2350           There may be several intermediate schedules that depict varying levels of
2351           detail. They shall be integrated roll ups of the detailed schedules (see 2.4
2352           below) (vertical integration).
2353           (8) Detailed Schedules, is the lowest level of contract tasks/activities that form
2354           the network. The detailed schedules shall contain horizontal and vertical
2355           integration, as a minimum, at the work package and planning package level.
2356           The detailed schedules shall include all tasks/activities, work packages, and


2357           planning packages identified in the contract Performance Measurement
2358           Baseline (PMB). Every discrete task/activity, work package, and planning
2359           package shall be clearly identified and directly related to a control account.
2360           Work packages and planning packages shall be individually represented and
2361           summarize to or reconcile with the total budget for that control account. If
2362           Level of Effort (LOE) control accounts, work packages, or planning packages
2363           are included as tasks in the IMS, they shall be clearly identified as such. The
2364           detailed tasks/activities, work packages, and planning packages shall be
2365           traceable to only one CWBS, IMP, and performing organizational element, as
2366           applicable. The level of detail in the IMS (including number and duration of
2367           tasks/activities) shall follow the Offeror’s EVM process as documented in the
2368           EVMS system description, program directives, etc. Shorter-term work
2369           packages (ideally equal in length to the status interval) are preferred because
2370           they provide more accurate and reliable measures of work accomplished.
2371           (9) Key Elements of Detailed Schedules: The key elements of the detailed
2372           schedules include the following:
2373              a.     Task/Activity: An element of work with duration.
2374              b.     Milestone: A specific definable accomplishment in the contract
2375              network, recognizable at a particular point in time. Milestones have zero
2376              duration and do not consume resources.
2377              c.     Duration: The length of time estimated (or realized) to accomplish
2378              a task/activity.
2379              d.     Percent Complete (Schedule): The proportion of an activity or task
2380              that has been completed to time now. This usually involves updating or
2381              status the activity or task utilizing one of two methods: (1) update the
2382              remaining time to complete (remaining duration) and the scheduling
2383              software will then automatically update the schedule percent complete or
2384              (2) update the schedule percent complete and allow the scheduling
2385              software to calculate the time remaining (remaining duration) to complete.
2386              Either method will use the following formula: Percent of Duration
2387              Completed = (Actual Duration / Total Duration) X 100.
2388              e.       Task/Activity and Milestone Descriptions: These are descriptive
2389              titles that are concise, complete, and clearly identify the work effort being
2390              accomplished. Abbreviations may be used to shorten the descriptive titles.
2391              f.      Task/Activity Fields/Codes and Data Dictionary: A list of field/code
2392              definitions and field/code structures.
2393              g.     Relationship/Dependency: These identify how predecessor and
2394              successor tasks/activities and milestones are logically linked.
2395              Relationships, also called network logic or dependencies, are modeled in
2396              four ways:


2397                  FS (Finish to Start): A predecessor task/activity or milestone that
2398                  must finish before a succeeding task/activity or milestone can start.
2399                  FS relationships shall be used whenever possible.
2400                  SS (Start to Start): A predecessor task/activity or milestone that
2401                  must start before a succeeding task/activity or milestone can start.
2402                  FF (Finish to Finish): A predecessor task/activity or milestone
2403                  that must finish before a succeeding task/activity or milestone can
2404                  finish.
2405                  SF (Start to Finish): A predecessor task/activity or milestone that
2406                  must start before a succeeding task/activity or milestone can finish.
2407           h.     Total Float/Slack: The amount of time a task/activity or milestone
2408           can slip before it delays the contract or project finish date.
2409           i.     Free Float/Slack: The amount of time a task/activity or milestone
2410           can slip before it delays any of its successor tasks/activities or milestones.
2411           j.    Lag: An interval of time that must occur between a predecessor and
2412           successor task/activity or milestone. Since negative time is not
2413           demonstrable, negative lag is not encouraged. (Note: Lag shall not be
2414           used to manipulate float/slack or constrain schedule.)
2415           k.     Early Start (ES) or Start: The earliest start date a task/activity or
2416           milestone can begin the precedence relationships. This can be a
2417           computer-calculated date.
2418           l.     Early Finish (EF) or Finish: The earliest finish date a task/activity or
2419           milestone can end. This can be a computer-calculated date.
2420           m.     Late Start (LS): The latest start date a task/activity or milestone
2421           can start without delaying the contract or project target completion date.
2422           This can be a computer-calculated date.
2423           n.      Late Finish (LF): The latest date a task/activity or milestone can
2424           finish without delaying the contract or project target completion date. This
2425           can be a computer-calculated date.
2426           o.       Critical Path: A sequence of discrete tasks/activities in the network
2427           that has the longest total duration through the contract or project. Discrete
2428           tasks/activities along the critical path have the least amount of float/slack.
2429           The critical path and near-critical paths (reporting requirements for near-
2430           critical paths shall be specified in the CDRL) are calculated by the
2431           scheduling software application. The guidelines for critical path and near-
2432           critical path reporting are as follows:
2433                  Methodology: The IMS software application computes a critical
2434                  path and near-critical paths based on precedence relationships, lag


2435                  times, durations, constraints, and status. Artificial constraints and
2436                  incorrect, incomplete, or overly constrained logic shall be avoided
2437                  because they can skew the critical path and near-critical paths.
2438           p.     Identification: The critical path shall be easily identified.
2439           q.      Constraints: Limits applied to network start and finish dates (e.g.,
2440           ―finish no later than‖). (Note: Certain types of constraints shall be used
2441           judiciously and shall not impact or distort the network critical path.)
2442           r.      Current Schedule: The IMS reflects the current status and forecast.
2443           It includes forecasted starts and finishes for all remaining tasks/activities
2444           and milestones. Significant variances to the baseline schedule shall be
2445           explained in the periodic analysis.
2446           s.     Baseline Schedule. Baseline dates in the IMS shall be consistent
2447           with the baseline dates in the PMB for all work packages, planning
2448           packages, and control accounts. The guidelines for maintaining the
2449           baseline schedule are as follows:
2450                  Schedule Changes: Changes to the schedule to incorporate a
2451                  modification to the scope of work shall be baselined when
2452                  incorporated into the schedule.
2453                  Baseline Schedule Changes: Changes to the baseline schedule
2454                  shall be made in accordance with the Offeror’s EVM process. Any
2455                  movement of contractual milestones in the baseline schedule shall
2456                  be derived only from authorized contract changes.
2457           t.     Schedule Progress: The IMS shall reflect actual progress and
2458           maintain accurate start and finish dates for all tasks/activities and
2459           milestones. The guidelines for reflecting schedule progress are as follows:
2460                  Actual Start and Finish Dates: Actual start and actual finish
2461                  dates shall be recorded in the IMS. Actual start and actual finish
2462                  dates, as recorded, shall not be later than the status date.
2463                  Progress Line: The progress line depicted in a Gantt chart shall
2464                  be applied to the current schedule.
2465           u.     Retention of Data for Completed Tasks/Activities: Historical
2466           performance on completed tasks/activities shall be maintained
2467           electronically for analytical use. Historical performance shall be
2468           maintained at the time of key program events (Integrated Baseline
2469           Review, Critical Design Review, etc.) for all critical tasks/activities. Data to
2470           be retained includes logic, actual and baseline durations, actual and
2471           baseline start and finish dates, and the three-point estimates that were
2472           used before the task/activity started.


2473                 v.       External Dependencies: The IMS shall identify significant external
2474                 dependencies that involve a relationship or interface with external
2475                 organizations, including all Government furnished items (e.g., decisions,
2476                 facilities, equipment, information, data, etc.). The determination of
2477                 significant shall be agreed to by the Government and Offeror and shall be
2478                 defined and documented in the CDRL. The required or expected delivery
2479                 dates shall also be identified in the IMS.
2480                 w.     Schedule Margin: A management method for accommodating
2481                 schedule contingencies. It is a designated buffer and shall be identified
2482                 separately and considered part of the baseline. Schedule margin is the
2483                 difference between contractual milestone date(s) and the Offeror’s
2484                 planned date(s) of accomplishment.
2485                 x.      User Defined Fields: All user defined fields in the IMS shall be
2486                 identified by providing a mapping of all fields used in the scheduling
2487                 software application.
2488                 y.     Reserved Fields: The Government will reserve some fields and/or
2489                 require the Offeror to use certain fields for specific information.
2490                 z.     Calendar: The arrangement of normal working days, together with
2491                 non-working days, such as holidays, as well as special work days (i.e.,
2492                 overtime periods) used to determine dates on which project work will be
2493                 completed.
2494           (10) Monthly Analysis: Monthly analysis is a monthly assessment of schedule
2495           progress to date and includes changes to schedule assumptions, variances to
2496           the baseline schedule, causes for the variances, potential impacts, and
2497           recommended corrective actions to minimize schedule delays. The analysis shall
2498           also identify potential problems and an assessment of the critical path and near-
2499           critical paths.

2500   L.     Staffing Plan

2501   The Offeror shall assign sufficient experienced personnel who are qualified in the
2502   conduct of similar operations (including but not limited to implementation expertise,
2503   Organizational Change Management (OCM) expertise, technical and functional
2504   expertise, system training expertise, data conversion expertise, application
2505   management expertise, and financial management system hosting and IT
2506   administration expertise) and who have relevant backgrounds and experience.
2507   Therefore, Offeror shall include a Staffing Plan in their response.
2508   As part of the Staffing Plan, the Offeror shall identify key personnel. Key personnel are
2509   personnel the Offeror deems essential to contract performance. Key personnel include
2510   only those persons who will be assigned to this project and who will be the actual
2511   personnel responsible for management and/or performance in the event the proposal
2512   results in award. At a minimum, key personnel shall include:


2513          Prime Program Manager
2514          Prime Project Manager
2515          Functional/Process Lead
2516          Technical Lead
2517          System Training Lead
2518          Data Conversion Lead
2519          Interfaces Lead
2520          User Support Lead
2521          OCM Lead
2522   The Prime Program Manager, Prime Project Manager, and Functional/Process Lead
2523   must have previous experience implementing the proposed core financial management
2524   system for a Federal government agency or component subject to the Chief Financial
2525   Officers Act or Accountability of Tax Dollars Act.
2526   The Offeror may propose additional key personnel positions based on its past
2527   experience in the organization and execution of projects that are similar in size, scope
2528   and complexity as the SSP. In such event, the Offeror shall include the rationale for this
2529   staffing approach in the Staffing Plan. The Offeror may propose one individual for
2530   multiple key personnel positions. In such event, the Offeror shall include the rationale
2531   for this staffing approach in the Staffing Plan. Each of the key personnel identified will
2532   be required to participate in discussions if the Offeror is selected. The Staffing Plan shall
2533   identify those key personnel that hold project management certifications, such as the
2534   Project Management Institute’s Project Management Professional (PMP) certification.
2535   The Staffing Plan shall also identify for each of the key personnel those Past
2536   Performance references included in the Offeror’s proposal that the individual supported.
2537   Substitution of key personnel during contract performance is subject to the terms of the
2538   ―Key Personnel‖ clause of the contract.
2539   The Staffing Plan shall include, at a minimum, the following information:
2540          A description of each role on the project team and the responsibilities of
2541           that role.
2542          An organizational chart that defines the relationships between the roles,
2543           identifies the assigned personnel for each role, and indicates which
2544           individuals are key personnel. Where personnel have not been named,
2545           indicate the role and the number of proposed personnel.
2546          A description of how the Offeror will ensure that staff identified as key
2547           personnel will remain on the project for at least fifteen (15) months after
2548           contract award.
2549          A staff continuity approach that addresses the method of ensuring project
2550           continuity during staff transition throughout the life of the contract.
2551   A summary of key and other proposed personnel shall be included in the price proposal
2552   workbook (see the Price Volume response section).


2554   L.      Resumes

2555   The Offeror shall provide the resumes of all key personnel and a representative resume
2556   for each SME labor category proposed. Resumes shall be no more than two (2) pages
2557   long. Resumes shall include the individual’s specific experiences that are directly
2558   related to the objectives and requirements of this RFP and clearly demonstrate the
2559   relationship between each proposed individual’s relevant professional certifications and
2560   qualifications, and the tasks or role to be performed by that individual. Past experience
2561   shall be listed in reverse chronological order, with the latest dates of employment first,
2562   and will identify the company or agency, period of employment, title and job description
2563   of the individual, and level of responsibility. The resume should be included in Section
2564   IV.

2565   L.      Assumptions

2566   The Offeror must describe any assumptions made in preparing this portion of the
2567   Offeror’s response. All assumptions will be evaluated for reasonableness.

2568   L.     Organizational Conflict of Interest Certification

2569   The Offeror shall state whether it is or is not aware of any information bearing on the
2570   existence of any potential organizational conflict of interest. If the Offeror is aware of
2571   information bearing on whether a potential conflict may exist, the Offeror shall provide a
2572   disclosure statement describing this information, and include it in Volume IV.

2573   L.8            Proposal Volumes Requirements
2574   The proposal shall be accompanied by a cover letter (letter of transmittal) prepared on
2575   the company’s letterhead stationery. The cover letter (letter of transmittal) shall identify
2576   all enclosures being transmitted and shall be used only to transmit the proposal and
2577   shall include no other information. The first or title page shall be in accordance with FAR
2578   52.215-1, paragraph (c) (2).
2579   The following are further descriptions of the information that shall be provided with the
2580   proposal.
2581                Table 1: Proposal Organization, Copy, and Page Limit Requirements

                      Volume                    Copies        Paper Copies          Page Limit

                Executive Summary                   1         Original plus 7           10

                     Volume I:                      1         Original plus 7           50
             Technical and Management                                           Excluding resumes


                     Volume                  Copies     Paper Copies              Page Limit

                    Volume II:                  1       Original plus 7              20
                Past Performance

                    Volume III:                 1       Original plus 7              10

                    Volume IV:                  1       Original plus 7            No limit
               Contract Information

2582   The Offeror shall prepare their proposal using the following guidelines:
2583          The Offeror shall not include any pricing information in non-price volumes
2584           unless otherwise directed. Any pricing information in these volumes will be
2585           discarded.
2586          The Offeror shall provide a Title Page, Table of Contents, List of Figures,
2587           List of Tables, Glossary, and List of Abbreviations and Acronyms for each
2588           volume of the proposal and ensure that they reference all sections,
2589           indices, foldouts, figures, tables, charts, and diagrams. These elements
2590           shall not count towards the page limitations.
2591          The Offeror shall provide a Master Index at the beginning of each volume.
2592           The Master Index must provide a single integrated index for the entire
2593           proposal and must identify each major subsection by volume, number,
2594           title, and page number. This index must also cross-reference the
2595           appropriate proposal volume and paragraphs to specific RFP objectives
2596           and requirements. The intent of the Master Index is to assure that all
2597           requirements are addressed and easily accessible to evaluators. Copies
2598           of the Master Index must be identical for all volumes. The Master Index is
2599           not subject to page limitations.
2600   The cover letter, Title Page, Table of Contents, List of Figures, List of Tables, Master
2601   Index, Glossary, and List of Abbreviations and Acronyms do not count against page
2602   count limitations. All other volumes and sections shall be limited to the number of pages
2603   stated in Table 1 above. Proposal contents that exceed the stated page limitations will
2604   be removed from the proposal by the Contracting Officer, prior to turning the proposal
2605   over to the Government evaluation teams, and will not be considered in the evaluation.


2609   L.8.1         Volume I: Technical and Management

2610   L.8.1.1       Proposal Format

2611   Text shall be single-spaced, on 8 1/2 x 11 inch paper (except as specifically noted), with
2612   a minimum one-inch margin all around. Pages shall be numbered consecutively within
2613   each volume. A page printed on both sides shall be counted as two pages. Submission
2614   as double-sided printing/copying on recycled paper is encouraged. 11‖ x 17‖ sized fold-
2615   out pages may be used for tables, charts, graphs, or pictures that cannot be legibly
2616   presented on 8 ½‖ x 11‖ papers. One side of an 11‖ x 17‖ is a two sheet equivalent
2617   (with regards to the page count limitations).
2618   Print shall be of a minimum 12-point font size or a maximum 10 characters per inch (10-
2619   pitch, pica) spacing. Bolding, underlining, and italics may be used to identify topic
2620   demarcations or points of emphasis. Graphic presentations, including tables, while not
2621   subject to the same font size and spacing requirements, shall have spacing and text
2622   that is easily readable.
2623   Each volume in the proposal shall include a copy of the cover letter (letter of
2624   transmittal), a title page and a table of contents. The table of contents shall list sections,
2625   subsections, and page numbers. Each volume shall contain a glossary of all
2626   abbreviations and acronyms used. Each acronym used shall be spelled out in the text
2627   the first time it appears in each proposal volume.
2628   In addition to the paper copies identified above, the Offeror shall submit all proposal
2629   information in electronic format on a CD. Text and graphics portions of the electronic
2630   copies shall be in a format readable by Microsoft (MS) Word 2003. Data submitted in
2631   spreadsheet format shall be readable by MS Excel 2003. The required Project Schedule
2632   shall be readable in MS Project 2003. In case of conflict between the paper copy and
2633   the electronic copy of the proposals submitted, the original paper copy shall take
2634   precedence.
2635   Each volume shall be bound separately in hard side three-ring binders. CDs shall be
2636   ―read-only‖ CDs formatted for Microsoft Windows XP with files unlinked to any other
2637   files.

2638   L.8.2.1       Submission Address

2639   The proposals all copies shall be sent or hand-carried to:
2640                                [Enter Issuing agency address here]
2641                                ATT:[Enter Issuing agency Contact Name]
2642                                REF: XXXXXXXXXXXX




2645   L.8.3.1       Submission Due Date

2646   All volumes referenced in Section L must be received prior to [time, date]. The
2647   Government POC will provide a receipt showing the time and date of delivery. Late
2648   submissions will not be accepted.

2649   L.8.4.1       Restriction of Disclosure/Proprietary Information

2650   If the Offeror wishes to restrict the disclosure or use of its proposal, use the legend
2651   permitted by FAR 52.215-1(e).

2652   L.8.5.1       Cross Referencing
2653   Each volume, other than the Price/Cost volume, shall be written to the greatest extent
2654   possible on a stand-alone basis so that its content may be evaluated with a minimum of
2655   cross-referencing to other volumes of the proposal. Cross-referencing within a proposal
2656   volume is permitted where its use would conserve space without impairing clarity.
2657   Hyper-linking of cross-references within the same MS Word 2003 file is permissible and
2658   encouraged. Information required for proposal evaluation, which is not found in its
2659   designated volume or cross-referenced, is assumed omitted from the proposal.

2660   L.8.6.1       Oral Presentations, Operational Capabilities Demonstrations, and
2661                 Discussions
2662   In accordance with FAR 52.15.306(c), the Government intends to evaluate proposals
2663   and award a contract after conducting oral presentations (Orals), Operational Capability
2664   Demonstrations (OCDs) and discussions, if necessary, with Offerors whose proposals
2665   have been determined to be within the competitive range. [Issuing agency] may conduct
2666   discussions with individual Offerors during or after the Orals or OCDs. The Offeror's
2667   initial proposal should contain the Offeror's best terms from a price and technical
2668   standpoint.
2669   Only Offerors who are determined to be in the competitive range based on the
2670   evaluation of written proposals will be invited by [issuing agency] to participate in Orals
2671   and OCDs. The purpose of the Orals and OCDs is for Offerors selected for inclusion in
2672   the competitive range to demonstrate that they can provide well-qualified staff, vendor
2673   software Federal Financials software, and all applicable services to meet the objectives
2674   and requirements contained in the solicitation.
2675   Each selected Offeror must participate in Orals and an OCD in order to remain eligible
2676   for contract award. Offerors not selected to participate in Orals and OCDs will be
2677   notified in writing that they have been eliminated from the competition. Those Offerors
2678   selected to participate will be provided rules, guidelines, content and materials
2679   requirements, and other instructions for the Orals and OCDs, as well as a set of
2680   scenarios that must be demonstrated to [issuing agency] during OCDs. OCD scenarios
2681   will focus on [issuing agency]’s unique requirements and other functionality that
2682   represent current areas of challenge for [issuing agency]. Initial guidelines for the Orals
2683   and OCDs will be distributed at the time of establishment of the competitive range. The


2684   scenarios that must be demonstrated to [issuing agency] during the OCDs will also be
2685   included.
2686   The order in which Offerors shall conduct their Orals and OCDs will be determined by
2687   random drawing by the CO. The CO will contact each Offeror to establish a date and
2688   time for the Offeror to present their Orals and OCD. Offerors must complete their Orals
2689   and OCDs within the scheduled dates and times. Requests from Offerors to reschedule
2690   their Orals and OCDs will not be entertained by the Government. [Issuing agency]
2691   reserves the right to reschedule Orals and OCDs at the sole discretion of the CO. All
2692   Offerors will have the same amount of time between notification from the CO and the
2693   scheduled first day of an Offeror’s Orals and OCDs. OCD scenarios will be the same for
2694   all Offerors. The Offeror shall be responsible for any equipment required for the Orals
2695   and OCD to include all preconfigured hardware and software. The number of [issuing
2696   agency] participants will be provided when the Orals and OCDs are scheduled.

2697   L.8.7.1       Electronic Copy of Proposal Volumes

2698   (a) By submission of a proposal on electronic media, the Offeror must ensure that the
2699   submission is readable, in the format specified in the solicitation, and has been verified
2700   as free of computer viruses. Prior to any evaluation, the Government will check all files
2701   for viruses and ensure that all information is readable. In the event that any files are
2702   defective (unreadable), the Government may only evaluate the readable electronic files.
2703   However, if the defective (unreadable) media renders a significant deficiency in the
2704   Offeror's proposal, the government may consider the proposal incomplete and not
2705   consider such proposal further for evaluation.
2706   (b) The Offeror must ensure that:
2707   (1) The electronic and paper copies of its proposal submitted in response to the
2708   solicitation are identical;
2709   (2) It has verified that its electronic proposal is readable on Microsoft Windows XP and
2710   Microsoft Office Word 2003
2711   (3) It has verified that the electronic proposals are free of computer viruses using
2712   standard commercial anti-virus software.
2713   (c) A proposal that fails to conform to the requirements of paragraphs (a) and (b) above
2714   may be subject to interception or delay at Governmental electronic communications
2715   portals. This interception or delay may result in the proposal being lost, deleted,
2716   destroyed, or forwarded in such a manner that the proposal arrives at the target
2717   destination past the time and date of the deadline for submission established in the
2718   solicitation. In the event that a proposal is lost, deleted, or destroyed due to the
2719   Offeror's failure to conform to the requirements of paragraphs (a) and (b) above, such
2720   proposal will be considered to have never been delivered to the Government. In the
2721   event that a proposal is delayed due to the Offeror's failure to conform to the
2722   requirements of paragraphs (a) and (b) above, the proposal will be treated as late in


2723   accordance with the provision of this solicitation entitled Late Submissions,
2724   Modifications, and Withdrawals of Proposals.

2725   L.8.1.8          Communication with the Contracting Office

2726   Solicitation information and amendments will be posted to the Federal Business
2727   Opportunities website at Offerors may e-mail written questions
2728   requesting clarification of the RFP to the Government via the [issuing agency] point of
2729   contact e-mail address. The Government will answer questions received up to [time,
2730   date]. Questions received after this date may not be answered. Only proposals
2731   submitted in accordance with Section L of this solicitation will be accepted.

2732   L.8.2            Volume II: Past Performance
2733   Volume II shall consist of three Past Performance sections, one for each of the three
2734   required Past Performance References. To help Offerors determine relevant contracts
2735   to include in this volume, [issuing agency] provides the following Past Performance
2736   Relevance Profile for suggested Past Performance submissions:
2737                             Table 2: Past Performance Relevance Profile

       Relevant Past Performance References will generally include one or more of the
                The system was based on an installed and operational FSIO-compliant
                 core financial system

                The client had 350 or more total financial system users;

                The work performed included a system life cycle implementation activity,
                 such as those included in this solicitation (e.g., requirements definition,
                 system design, testing, data conversion, and training);

                The work performed included a hosting and IT administration activity,
                 such as hardware monitoring and management, power backup
                 redundancy, network monitoring and management, full system backups
                 and restores, mirrored sites, Disaster Recovery and Continuity of
                 Operations planning and testing, server systems administration,
                 database administration, information security (including intrusion
                 detection and security certifications and assessments);

                The work performed included an application management activity, such
                 as interface maintenance and execution, installation and testing of
                 software patches and upgrades, application performance management,
                 information security, application configuration management, release
                 management, software bug fixes; user ID and password resets, and
                 customer support services (Tier 1, Tier 2 and/or Tier 3)


              The work was performed (i.e., some portion of the engagement occurred)
               within the past three years.

2738   The Past Performance section shall include three current contracts or contracts
2739   completed within the last three years that are relevant to the objectives and
2740   requirements of this solicitation. The Offeror may also include current and completed
2741   contracts that are relevant to the objectives and requirements of this solicitation and that
2742   were performed for state government, local government, and/or private sector clients.
2743   Each past performance entry shall contain the client’s name, the project title, the period
2744   of performance, the contract number, the contract value, and two points of contact
2745   (including the telephone number and email address for each point of contact, if
2746   available). These entries should be included at the beginning of each section of Volume
2747   II. The Offeror shall provide detailed references for each Past Performance entry. A
2748   detailed reference will consist of (1) an overview of the contract, and (2) a Past
2749   Performance Survey (see Section M that is to be completed by the Offeror’s client on
2750   that past performance. The overview for each detailed reference shall include the same
2751   information included on the first page of the Past Performance Survey, though this
2752   information does not have to be formatted identically to the format in the Questionnaire.
2753   This information will allow [issuing agency] to easily match the completed surveys from
2754   other clients to the correct proposal. The Offeror shall also include in each overview a
2755   description of the scope of work performed and the results achieved. Each overview
2756   shall not exceed three (3) pages. To facilitate [issuing agency]’s understanding of past
2757   performance information, the Offeror shall discuss its past performance solutions in
2758   terms of the original software name (i.e., the name that the software vendor assigned to
2759   the software) and not names assigned to the solution by the client or the Offeror. The
2760   Offeror shall include the overviews of their detailed past performances in Volume II.
2761   Offerors are required to complete Section 1 of the Past Performance Survey for each
2762   detailed reference and to provide the survey to the respective clients. Completed
2763   surveys must be received at the proposal submission address contained herein by the
2764   proposal due date. Instructions for submitting the questionnaire to [issuing agency] are
2765   included in the Past Performance Survey attachment as part of Section M. Offerors may
2766   provide information on problems encountered and corrective actions taken, on any of
2767   the contracts identified in Volume II.

2768   L.8.3         Volume III: Cost
2769   Volume III shall consist of the following: the Offeror’s Cover Letter, the Offeror’s price
2770   and cost proposal information, and a printed copy of the Offeror’s completed Price/Cost
2771   Proposal workbook (MS Excel; see Section L for this attachment), and required
2772   information for SME Services described below. Please note that private sector Offerors
2773   must cite their Tax Identification Number (TIN), Dun & Bradstreet Number (DUNS),
2774   North American Industrial Classification System (NAICS), and other pertinent
2775   information. Volume III is considered a separate volume from the technical and
2776   management approach. No pricing information should be included elsewhere in the
2777   proposal.


2778   The price proposal shall be submitted as a Firm Fixed Price offer for each deliverable
2779   proposed in the contract base period and each option period and align with the
2780   information submitted in the MS Project file submitted separately (See Section L for
2781   appropriate attachments and subsections below). Public sector Offerors’ price proposals
2782   shall identify the full cost of performance to the Government. Also, public sector price
2783   proposals must include sufficient detail to allow [issuing agency] to understand the basis
2784   for proposed costs and evaluate price reasonableness. All Offerors shall provide
2785   separate pricing for any Software, Hardware, IT Hosting and Administration,
2786   Implementation Services proposed and identify any proposed item above and beyond
2787   the objectives and requirements of the SOO as optional.
2788   Offerors shall also provide labor categories, descriptions, and applicable hourly rates for
2789   Financial Management Subject Matter Expert (SME) and Financial Management
2790   Information Systems services in the Price/Cost Proposal Spreadsheet (see Section L
2791   below). These services may be used in future Time & Materials (T&M) task orders at the
2792   sole discretion of the Government. For these services, the Offerors shall:
2793   (1) Public sector Offerors: Identify the labor categories proposed, a description of the
2794   skills and experience per category, the hourly cost proposed, and any other proposed
2795   associated costs, for calculating the proposed cost.
2796   (2) Private sector Offerors: Provide a copy of the Offeror’s GSA Schedule Contract(s)
2797   (including contract clauses) listing the applicable categories and fixed hourly rates.
2798   Fixed rates shall include all costs and fees, including overhead and fee, and shall
2799   identify any reduction in GSA Schedule rates offered. Offerors are encouraged to
2800   discount their rates.

2801   L.8.3.1       Price/Cost Summary

2802   The Offeror shall provide a pricing/costing summary in their price/cost proposal to show
2803   the following:
2804                  Table 3: Price/Cost Proposal Summary Pricing Requirements

         Implementation Period 1:                       Total proposed firm fixed price for
                                                        deliverables proposed in this period

         Implementation Period 2:                       Total proposed firm fixed price for
                                                        deliverables proposed in this period

         Base Period 1:                                 Total proposed firm fixed price for
                                                        deliverables proposed in this period

         Base Period 2:                                 Total proposed firm fixed price for
                                                        deliverables proposed in this period

         Option Period 1:                               Total proposed firm fixed price for


                                                         deliverables proposed in this period

         Option Period 2:                                Total proposed firm fixed price for
                                                         deliverables proposed in this period

         Option Period 3:                                Total proposed firm fixed price for
                                                         deliverables proposed in this period

         Option Period 4:                                Total proposed firm fixed price for
                                                         deliverables proposed in this period

         Option Period 5:                                Total proposed firm fixed price for
                                                         deliverables proposed in this period

         Option Period 6:                                Total proposed firm fixed price for
                                                         deliverables proposed in this period

         Option Period 7:                                Total proposed firm fixed price for
                                                         deliverables proposed in this period

         Option Periods Total:                           Total for Option Periods 1 through 7

         Grand Total:                                    Total for Base Period and all Option

2805   L.8.3.2       Price/Cost Proposal Workbook

2806   The Offeror’s proposed prices shall be clearly linked to the solution as proposed in the
2807   MS Excel workbook attached in Section L. For each base and option period, the Offeror
2808   shall identify the proposed price by the elements at the appropriate WBS level in the
2809   Offeror’s proposed Project Plan. The Offeror shall clearly indicate at which WBS level
2810   they are providing the price details by providing the WBS code associated with the
2811   priced element. See Section L for additional, related guidance on completing the
2812   required WBS and associated price/cost elements.
2813   In addition, the Offeror shall provide a time-phased invoicing schedule in the MS Excel
2814   workbook attached to this solicitation under Section J, showing the month and contract
2815   period in which individual deliverables are scheduled to be invoiced. The invoicing
2816   schedule must identify the WBS Element for each deliverable proposed. Offerors shall
2817   also provide labor categories, descriptions, and applicable hourly rates for Financial
2818   Management SME and Financial Management Information Systems services in this
2819   Price/Cost Proposal Workbook.

2820   L.8.3.3       Other Price/Cost Proposal Details

2821   The Offeror shall provide detailed pricing/costing in their price/cost proposal as follows:


2822   (a) Software Licenses. The Offeror shall provide pricing for the acquisition and
2823   maintenance of all proposed software licenses. This pricing should include maintenance
2824   upgrades for all software. The Offeror shall clearly indicate in which base and/or option
2825   period(s) the price(s) will apply.
2826   (b) Hardware. The Offeror shall provide pricing for any and all hardware and
2827   infrastructure proposed. Note that a secure data communications line from [issuing
2828   agency] location to the shared service provider site should not be included in the prices
2829   proposed. [Issuing agency] will provide an appropriate data communications line from
2830   [issuing agency] location to the shared service provider site.
2831   (e) Major Software Releases. The Offeror shall provide pricing for all major [software]
2832   releases that are proposed during the period of performance for this contract. The
2833   Offeror shall clearly indicate in which base and/or option period(s) the price(s) will apply
2834   in the price/cost spreadsheet attached in Section M of this solicitation. The pricing for
2835   major software releases should not be included in the pricing for the software licenses
2836   described in section (a) above.
2837   (f) Any travel costs will be in accordance with the Federal Travel Regulations.
2838   (g) For pricing and evaluation purposes, the Offeror shall assume a start-of-work date of
2839   [date].


2841   L.8.4         Volume IV: Contract Information
2842   This volume will include a completed SF33, and the information required to complete
2843   Section B, Section F, Section G, Section H, Section J, and Section K not specified in
2844   this solicitation for inclusion elsewhere and any other information required to complete
2845   the contract. The Offeror shall include in Volume IV all supporting documentation
2846   requested in this solicitation. Specifically, the minimum supporting documentation to be
2847   included in this Volume is described in the sections that follow.

2848   L.8.4.1       *Completed FSIO Due Diligence Checklist

2849   The Due Diligence Checklist (DDC) provides a means for both OMB and FSIO to
2850   assess the capabilities of current and future SSPs. Private Offerors must submit Version
2851   4.0     of   the     FSIO      DDC      published   on     August     6,   2007     (see
2852 (download section 2.1). For
2853   public FM SSPs, the latest completed DDC provided to OMB must be submitted.

2854   L.8.4.2       Samples of Reports

2855   The Offeror shall provide samples of each report (standard or custom-developed)
2856   provided as part of its SSP offering.

2857   L.8.4.3       Key Personnel Resumes

2858   Resumes of the Key Personnel proposed.

2859   L.8.4.4       Proposed Integrated Master Schedule

2860   A completed MS Project file is required under this solicitation.

2861   L.8.4.5       EVMS Compliance Documentation or Compliance Plan(s)

2862   Information describing the Offeror’s processes and tools for managing and reporting
2863   earned value in accordance with American National Standards Institute/Electronic
2864   Industries Association (ANSI/EIA) Standard 748. For all Offerors, the description of the
2865   EVMS and a statement that the EVMS requirements proposed will be applied to any
2866   subcontractors utilized, in accordance with FAR 34.201(d) and 52.234-3(c), must be
2867   provided. For Offeror’s with a certified EVMS in place, documentation of compliance by
2868   a cognizant federal agency must be provided. If the Offeror’s EVMS has not been
2869   certified as compliant with ANSI/EIA Standard 748 by a cognizant Federal Agency at
2870   the time of proposal submission, then the Offeror shall describe in its proposal its plan
2871   for obtaining compliance within 30 calendar days of contract award.

2872   L.8.4.6       Federal Enterprise Architecture Compliance

2873   Offerors must demonstrate alignment of their SSP solution with the Federal Enterprise
2874   Architecture (FEA) via appropriate artifacts (e.g., reference models, FEA annual
2875   assessments). Offerors who have not achieved FEA alignment shall provide a timeline


2876   describing the Offeror’s commitment to align with the FEA prior to signing contracts with
2877   [issuing agency] if selected.

2878   L.8.4.7       FISMA Compliance Documentation

2879   Offerors shall provide evidence of their solution’s FISMA compliance, including
2880   evidence of a Security Certification & Accreditation (SC&A) and Authority To Operate
2881   (ATO) from a Designated Approving Authority (DAA).

2882   L.8.4.8       Sample Continuity of Operations Plan (COOP)

2883   A sample Continuity of Operations Plan (COOP) shall be provided by the Offeror and
2884   information on the last Disaster Recovery Test performed.

2885   L.8.4.9       Proposed Service Level Agreement

2886   The Offeror shall include its proposed SLA with proposed service levels corresponding
2887   to the proposed PWS, QAP, QASP, and the FMLoB Service Assessment Guide.

2888   L.8.4.10      Latest SAS 70 Audit Report Findings
2889   Information on any SAS-70 findings shall be provided by the Offeror with specific information on
2890   any finding that impacted the Offeror’s services to a Federal Agency customer.

2891   L.9           Number of Awards
2892   The government does not anticipate making more than one award as a result of this
2893   solicitation. However, this does not preclude the Government from making more than
2894   one award.

2895   L.10          All or Nothing Proposals
2896   Proposals may not be submitted for the performance of less than all of the
2897   types/quantities/option years of services required by this solicitation.

2898   L.11          Questions Regarding This Solicitation
2899   If interested vendors are uncertain as to any requirements of the specification(s)
2900   detailed in this solicitation, questions may be directed to the Contract Specialist in
2901   charge of this procurement. Questions must be submitted in writing and should make
2902   reference to the solicitation page number and to the section paragraph number of this
2903   solicitation that is the subject of the question. Questions must be received in the Office
2904   of Procurement Services no later than [time, date], in order to be addressed prior to the
2905   closing date. Should any questions be received after the date stated above, the
2906   Government reserves the right not to provide an answer. If, however, the Government
2907   determines that the questions raise an issue of significant importance, the government
2908   will respond electronically.


2909   Offerors may submit questions via email to [enter name of issuing agency POC]. The
2910   Government will not consider any information concerning questions, comments, or
2911   requests for clarification in response to telephone calls from Offerors.
2912   Please be advised that it is the sole responsibility of the Offeror to continually view the
2913   Federal Business Opportunities website for any amendments to this solicitation.

2914   L.12          Contract Schedule
2915   The proposed price table is listed below:
2916   Implementation Year 1
2917   CLIN Description                            QTY UM       Unit Price    Total Price
2918   0001 Integration Services                   1     JOB    $__________ $_________
2919   0002 Software Licensing                     1     LOT    $__________ $_________
2920   0003 Reserved                               N/A   N/A
2921   0004 Other Direct Costs                     1     LOT    $__________ $_________
2922   0005 Operation and Maintenance
2923           Integration                         1     LOT    $__________ $_________
2924   0006 Reserved                               N/A   N/A
2925                                                            TOTAL         $__________
2927   Implementation Year 2
2928   CLIN Description                            QTY UM       Unit Price    Total Price
2929   0001 Integration Services                   1     JOB    $__________ $_________
2930   0002 Software Licensing                     1     LOT    $__________ $_________
2931   0003 Reserved                               N/A   N/A
2932   0004 Other Direct Costs                     1     LOT    $__________ $_________
2933   0005 Operation and Maintenance
2934           Integration                         1     LOT    $__________ $_________
2935   0006 Reserved                               N/A   N/A
2936                                                            TOTAL         $__________


2938   Base Year 1
2939   CLIN Description                 QTY UM      Unit Price   Total Price
2940   0001 Integration Services        1     JOB   $__________ $_________
2941   0002 Software Licensing          1     LOT   $__________ $_________
2942   0003 Reserved                    N/A   N/A
2943   0004 Other Direct Costs          1     LOT   $__________ $_________
2944   0005 Operation and Maintenance
2945           Integration              1     LOT   $__________ $_________
2946   0006 Reserved                    N/A   N/A
2947                                                TOTAL        $__________
2949   Base Year 2
2950   CLIN Description                 QTY UM      Unit Price   Total Price
2951   0001 Integration Services        1     JOB   $__________ $_________
2952   0002 Software Licensing          1     LOT   $__________ $_________
2953   0003 Reserved                    N/A   N/A
2954   0004 Other Direct Costs          1     LOT   $__________ $_________
2955   0005 Operation and Maintenance
2956           Integration              1     LOT   $__________ $_________
2957   0006 Reserved                    N/A   N/A
2958                                                TOTAL        $__________


2961   Option Year 1
2962   CLIN Description                 QTY UM      Unit Price   Total Price
2963   0001 Integration Services        1     JOB   $__________ $_________
2964   0002 Software Licensing          1     LOT   $__________ $_________
2965   0003 Reserved                    N/A   N/A
2966   0004 Other Direct Costs          1     LOT   $__________ $_________
2967   0005 Operation and Maintenance
2968           Integration              1     LOT   $__________ $_________
2969   0006 Reserved                    N/A   N/A
2970                                                TOTAL        $__________
2972   Option Year 2
2973   CLIN Description                 QTY UM      Unit Price   Total Price
2974   0001 Integration Services        1     JOB   $__________ $_________
2975   0002 Software Licensing          1     LOT   $__________ $_________
2976   0003 Reserved                    N/A   N/A
2977   0004 Other Direct Costs          1     LOT   $__________ $_________
2978   0005 Operation and Maintenance
2979           Integration              1     LOT   $__________ $_________
2980   0006 Reserved                    N/A   N/A
2981                                                TOTAL        $__________


2984   Option Year 3
2985   CLIN Description                 QTY UM      Unit Price   Total Price
2986   0001 Integration Services        1     JOB   $__________ $_________
2987   0002 Software Licensing          1     LOT   $__________ $_________
2988   0003 Reserved                    N/A   N/A
2989   0004 Other Direct Costs          1     LOT   $__________ $_________
2990   0005 Operation and Maintenance
2991           Integration              1     LOT   $__________ $_________
2992   0006 Reserved                    N/A   N/A
2993                                                TOTAL        $__________
2995   Option Year 4
2996   CLIN Description                 QTY UM      Unit Price   Total Price
2997   0001 Integration Services        1     JOB   $__________ $_________
2998   0002 Software Licensing          1     LOT   $__________ $_________
2999   0003 Reserved                    N/A   N/A
3000   0004 Other Direct Costs          1     LOT   $__________ $_________
3001   0005 Operation and Maintenance
3002           Integration              1     LOT   $__________ $_________
3003   0006 Reserved                    N/A   N/A
3004                                                TOTAL        $__________


3007   Option Year 5
3008   CLIN Description                 QTY UM      Unit Price   Total Price
3009   0001 Integration Services        1     JOB   $__________ $_________
3010   0002 Software Licensing          1     LOT   $__________ $_________
3011   0003 Reserved                    N/A   N/A
3012   0004 Other Direct Costs          1     LOT   $__________ $_________
3013   0005 Operation and Maintenance
3014           Integration              1     LOT   $__________ $_________
3015   0006 Reserved                    N/A   N/A
3016                                                TOTAL        $__________
3018   Option Year 6
3019   CLIN Description                 QTY UM      Unit Price   Total Price
3020   0001 Integration Services        1     JOB   $__________ $_________
3021   0002 Software Licensing          1     LOT   $__________ $_________
3022   0003 Reserved                    N/A   N/A
3023   0004 Other Direct Costs          1     LOT   $__________ $_________
3024   0005 Operation and Maintenance
3025           Integration              1     LOT   $__________ $_________
3026   0006 Reserved                    N/A   N/A
3027                                                TOTAL        $__________


3030   Option Year 7
3031   CLIN Description                 QTY UM      Unit Price   Total Price
3032   0001 Integration Services        1     JOB   $__________ $_________
3033   0002 Software Licensing          1     LOT   $__________ $_________
3034   0003 Reserved                    N/A   N/A
3035   0004 Other Direct Costs          1     LOT   $__________ $_________
3036   0005 Operation and Maintenance
3037           Integration              1     LOT   $__________ $_________
3038   0006 Reserved                    N/A   N/A
3039                                                TOTAL        $__________
3041   Option Year 8
3042   CLIN Description                 QTY UM      Unit Price   Total Price
3043   0001 Integration Services        1     JOB   $__________ $_________
3044   0002 Software Licensing          1     LOT   $__________ $_________
3045   0003 Reserved                    N/A   N/A
3046   0004 Other Direct Costs          1     LOT   $__________ $_________
3047   0005 Operation and Maintenance
3048           Integration              1     LOT   $__________ $_________
3049   0006 Reserved                    N/A   N/A
3050                                                TOTAL        $__________



3053   M.1           Notice Listing Solicitation Provisions Incorporated by Reference
3054                 (Evaluation Factors for Award)
3055   The following solicitation provisions pertinent to this section are hereby incorporated by
3056   reference (by Citation Number, Title, and Date) in accordance with the FAR provision at
3058   Section L of this solicitation. See FAR 52.252-1 for an internet address (if specified) for
3059   electronic access to the full text of a provision.
3060   NUMBER                    TITLE                                                   DATE
3061   52.217-5                  EVALUATION OF OPTIONS                                 JUL 1990

3062   M.2           Method of Award (Best Value)
3063   Award will be made to the Offeror whose proposal is most advantageous to the
3064   Government, price and other factors considered. The Government intends to evaluate
3065   proposals using a two-step methodology.
3066   In the first step, proposals shall be evaluated based on the technical factors and sub
3067   factors described below (Functional Requirements & Technical Requirements, Past
3068   Performance & Risks, Implementation Support, Pricing, Project Management), and for
3069   price reasonableness. Prior to being evaluated in terms of the technical factors and sub
3070   factors, proposals must meet the requirements set forth in Section C and be compliant
3071   with the terms and conditions of this solicitation. Offerors proposed price will be
3072   considered independently of the technical criteria and will not of themselves be
3073   accorded any specific numerical rating. Based on these evaluations, a Competitive
3074   Range (FAR Part 15) consisting of the most highly rated proposals will be established.
3075   The second step will involve evaluation of a product demonstration against test cases.
3076   Vendors that meet the stated requirements and are determined to be in the Competitive
3077   Range will be included in the next phase of the evaluation and be asked to demonstrate
3078   their product against test cases. Scripts that define scenarios and processes to
3079   determine their operational capability in meeting technical and functional requirements
3080   will be provided to each Vendor in the Competitive Range.
3081   The contract resulting from this solicitation will be awarded to the responsible Offeror
3082   whose offer, conforming to the solicitation, is determined to provide the "best value" to
3083   the Government, which may not necessarily be the proposals offering the lowest cost
3084   nor receiving the highest technical rating. It should be noted that cost is not a
3085   numerically weighted factor. Although non-cost factors are significantly more important
3086   than cost, cost is an important factor and should be considered when preparing
3087   responsive offers (proposals). The importance of cost as an evaluation factor will
3088   increase with the degree of equality of the proposals in relation to the remaining
3089   evaluation factors.


3090   When the Offerors within the Competitive Range are considered essentially equal in
3091   terms of technical, past performance and other non-cost factors (if any), or when cost is
3092   so significantly high as to diminish the value of the technical superiority to the
3093   Government, cost may become the determining factor for award. In summary,
3094   cost/non-cost trade offs will be made, and the extent to which one may be sacrificed for
3095   the other is governed only by the tests of rationality and consistency with the
3096   established factors.
3097   Prospective contractors are advised that the selection of a contractor for contract award
3098   is to be made after a careful evaluation of the offers (proposals) received, by a panel of
3099   specialists chosen by [issuing agency]. Each panelist will evaluate the proposals for
3100   technical acceptability using the ratings described in Section M.3, below. The factors
3101   are presented in the order of emphasis that they will receive. The scores will then be
3102   averaged to select a contractor for award on the basis of their proposal being the most
3103   advantageous to the Government, price and other factors considered.
3104   If there are no significant technical differences among Offerors, price alone will be the
3105   determining factor for source selection.

3106   M.3           Evaluation Factors and Ratings
3107   ***Offers will be evaluated using a Cascading method of evaluation.
3108           (1)   Offers are being solicited from both small and large business under
3109                 a two-tiered solicitation.
3110           (2)   Offers from all small business will be considered for award prior to
3111                 any offers from large businesses.
3112           (3)   (a) If the Contracting Officer determines that sufficient competition
3113                 exists between small businesses, an award will be made to a small
3114                 business, under the first tier, without consideration of offers
3115                 submitted by large businesses.
3116                 (b)If the Contracting Officer determines that insufficient competition
3117                 exists between small businesses, offers from large businesses as
3118                 well as small businesses will be considered for award.***

3119   M.3.1         General
3120   The Government will apply the following evaluation criteria to identify the best value
3121   proposal(s). The evaluation criteria represent key areas of importance to be considered
3122   in the source selection decision. The evaluation criteria (factors, sub factors, and
3123   elements) were chosen to support a meaningful discrimination between and among
3124   competing proposals. The proposals will be evaluated against the Government’s
3125   objectives and requirements using these factors:
3126          Past Performance;
3127          Technical and Management Approach;


3128          Cost.
3129   Note: for purposes of this acquisition, references to ―Price‖ and ―Cost‖ are considered
3130   interchangeable.

3131   M.3.2           Definitions
3132   In order to provide insight into the Government’s value of the evaluation criteria, the
3133   following terminology is used:
3134          More Important. The criterion is greater in value than another criterion.
3135          Comparatively Equal. The criterion is nearly the same in value as another
3136           criterion; any difference is very slight and unimportant.

3137   M.3.3           Relative Importance of Evaluation Criteria
3138   Non–cost factors are comparatively equal. Each of the non–cost factors is divided into
3139   sub factors. Non–cost factors are divided into sub factors, which are further divided into
3140   elements. Sub factors are comparatively equal within each factor. All elements within a
3141   sub factor are comparatively equal. Each non–cost factor individually is more important
3142   than the Cost factor. When combined, the non-cost factors are significantly more
3143   important than Cost factor. [Each issuing agency may not agree with this order of
3144   importance for the evaluation factors and may tailor this section based on their
3145   requirement].

3146   M.3.4           Non-Cost Factor Evaluation Ratings
3147                               Table 4: Non-Cost Factor Evaluation Ratings

       Adjectival Rating      Capability            Strengths            Weaknesses         Past Performance

                           The proposal         There are              Weaknesses are      Highly relevant/very
                           exceeds              numerous               considered          recent past
                           requirements and     strengths that are     insignificant and   performance in all
                           clearly              of direct benefit to   have no apparent    identified past
                           demonstrates the     the Government.        impact to the       performance efforts;
                           Offeror’s                                   program.            excellent
                           capability to                                                   performance ratings.

                           The proposal is      Some strengths         A few               Relevant/somewhat
                           satisfactory; the    exist that are of      weaknesses exist;   recent past
                           Offeror is capable   benefit to the         they are            performance in all
           Excellent       of meeting           Government; the        correctable with    identified past
                           performance          strengths clearly      minimal             performance efforts;
                           requirements.        offset                 Government          acceptable
                                                weaknesses.            oversight or        performance ratings.


       Adjectival Rating       Capability            Strengths           Weaknesses          Past Performance

                           The proposal is       Few strengths         Substantial          Somewhat
                           minimally             exist that are of     weaknesses exist     relevant/not very
                           adequate; the         benefit to the        that may impact      recent past
                           Offeror is most       Government; the       the program; they    performance; mostly
          Acceptable       likely able to meet   strengths do not      are correctable      acceptable
                           performance           offset the            with some            performance ratings.
                           requirements.         weaknesses.           Government
                                                                       oversight and

                           The proposal is       Little, if any,       Weaknesses exist     Little relevant past
                           inadequate; it is     strengths exist       that adversely       performance
                           doubtful whether      that are of benefit   impact the           identified; mostly
                           the Offeror can       to the                program; they are    unacceptable
           Marginal        meet performance      Government; the       correctable with     performance ratings.
                           requirements.         weaknesses            significant
                                                 clearly offset the    Government
                                                 strengths.            oversight and

                           The proposal is       There are no          Numerous             Little relevant past
                           highly inadequate;    beneficial            weaknesses exist     performance
                           the Offeror cannot    strengths.            that are so          identified; almost all
                           meet performance                            significant that a   unacceptable
                           requirements.                               proposal re–write    performance ratings.
                                                                       is not feasible
                                                                       within a suitable

                                                                                            Completely lacks
                                                                                            relevant performance
                                                                                            history or past
            Neutral            Not used               Not used              Not used        performance is
                                                                                            unavailable, not due
                                                                                            Offeror’s failure to
                                                                                            provide information.


3149   M.3.5            Risk Assessment Ratings
3150   The Government performs a risk assessment of each Offeror’s proposal. The proposal
3151   risk assessment focuses on the risks and weaknesses associated with the Offeror’s
3152   proposed approach. Assessment of risk is done at the non-cost factor levels, and
3153   includes potential for disruption of schedule, degradation of performance, and the need
3154   for increased Government oversight as well as the likelihood of unsuccessful contract
3155   performance. For any risk identified, the evaluation addresses the Offeror’s proposal for


3156   mitigating those risks and why that approach is or is not feasible. The table below
3157   provides definitions to be used for risk assessment of non-cost factors.
3158                       Table 5: Risk Assessment Ratings for Non-Cost Factors

        Rating                                        Description

       High      Offeror’s proposed approach is likely to cause significant disruption of schedule or
                 degradation of performance, and will require a high level of contractor emphasis and
                 Government monitoring to overcome difficulties

       Medium    Offeror’s proposed approach is likely to cause a moderate disruption of schedule or
                 degradation of performance, and will require a medium level of contractor emphasis and
                 Government monitoring to overcome difficulties

       Low       Offeror’s proposed approach is likely to cause minimal or no disruption of schedule or
                 degradation of performance, and will require a low level of contractor emphasis and
                 Government monitoring to overcome difficulties

3159   (1) Risks may occur as a result of a particular technical approach, business process,
3160   management approach, or as a result of the schedule and economic impacts associated
3161   with these approaches.
3162   (2) A risk assessment rating will be used along with the ratings for each assessed
3163   factor. The statements within the rating definitions assess different evaluation aspects
3164   rather than the risk assessment ratings. The statements within the rating definitions
3165   reflect how well the Past Performance and Technical and Management volumes meet
3166   the solicitation requirements.

3167   M.3.6         Non–Cost Factor Evaluation Criteria

3168   Factor 1 – Past Performance
3169   The Government assesses the Offeror’s capability to perform tasks under the
3170   solicitation by evaluating the Offeror’s past performance as a prime contractor on
3171   previous contracts. Only past performance data regarding SSP efforts completed within
3172   the last three years, or work that is ongoing, is evaluated. The lack of relevant past
3173   performance information will result in the assignment of a neutral rating (i.e., neither
3174   favorable nor unfavorable). Technically complex tasks managed and implemented
3175   across an enterprise will be rated higher than tasks of lesser size, scope, and
3176   complexity. Each Past Performance summary submitted by Offeror will be evaluated
3177   according to the following elements.
3178   The Government evaluates the Offeror’s past performance as the prime contractor in
3179   management of large and complex FM SSP–related efforts. The evaluation focuses on
3180   the Offeror’s technical understanding and technical capability as demonstrated by the
3181   size, scope, complexity, and results achieved in fulfilling the objectives of actual


3182   contracts and task orders similar to those contained in Section C of the solicitation.
3183   Technically complex tasks managed and implemented across an enterprise similar to
3184   [issuing agency] rate higher than tasks of lesser size, scope, and complexity. The
3185   evaluation also focuses on the innovative solutions developed and implemented by the
3186   Offeror to address complex efforts and technical challenges, along with the results
3187   achieved. Emphasis is placed on the application and use of performance metrics and
3188   quality assurance plans that demonstrate program objectives and customer
3189   expectations were met or exceeded.
3190           Element 1 - Past Performance Information Data
3191           The Government evaluates the Offeror’s proposal to determine the degree to
3192           which the Offeror demonstrated its past performance in hosting, maintaining, and
3193           operating financial management systems consistent with the objectives and
3194           complexity described in the SOO (Section C). At a minimum, Offerors must
3195           provide evidence of experience (i.e., in at least three contract(s) or order(s))
3196           covering all SOO task areas. Technically complex shared service provider
3197           performance across an enterprise rates higher than tasks of less size, scope,
3198           and complexity. Successful past performance of data migration and data
3199           cleansing will also warrant a higher rating.
3200           Element 2 - Cost Control
3201           The Government evaluates the Offeror’s ability to deliver services at an agreed–
3202           to price/cost. Variances in the award amounts and the amounts at completion (or
3203           Estimate To Complete) are evaluated to determine the extent to which the
3204           Offeror controlled customer costs. Past Performance with lower cost variance
3205           relative to OMB thresholds will be evaluated higher than past performance with
3206           larger variances.
3207           Element 3 - Schedule Control
3208           The Government evaluates the Offeror’s ability to deliver a service according to
3209           an agreed–to schedule. The cause of any schedule variances is evaluated to
3210           determine the extent to which the Offeror was able to deliver services on time.
3211           Element 4 - Organizational Change Management
3212           The Government evaluates the Offeror’s ability in Past Performance to provide
3213           integration and coordination of all activities needed to execute the contract to
3214           satisfy the customer’s requirements and objectives, including transition
3215           management services (e.g., training, migration planning, change management,
3216           sequencing).
3217           Element 5 - Quality
3218           The Government evaluates the Offeror’s ability to provide a service that met the
3219           customer’s quality requirements. Examine the Offeror’s performance to


3220           determine if the quality of service necessary in providing conformance to contract
3221           requirements was met.
3222           Element 6 - Socioeconomic Goals
3223           The Government evaluates the Offeror’s ability to meet subcontracting goals
3224           (large businesses and federal agencies proposing the use of contractors).
3225           Consider any circumstances that negatively impacted the Offeror’s ability to
3226           consistently meet or exceed small business subcontracting goals.
3227           Element 7 - Subcontracting Management
3228           The Government evaluates the Offeror’s proposal to determine the extent that
3229           subcontracting management goals were met. This determination includes
3230           whether subcontracts were awarded in a timely manner, whether subcontractors
3231           were paid on time, and whether there were any significant problems with
3232           subcontracts that resulted in cost, schedule, or performance problems in the
3233           contract completion.
3234           Element 8 - Business Relations
3235           The Government evaluates the Offeror’s ability to demonstrate a business–like
3236           concern for the customer’s interests and the ability to demonstrate reasonable
3237           and cooperative behavior. The Government examines the assessment to
3238           determine the degree to which the Offeror met the levels of cooperation needed
3239           to act as an effective business partner.

3240   Factor 2 – Technical & Management Approach
3241   The Government assesses the Offeror’s capability to perform under the contract by
3242   evaluating the Offeror’s proposed technical approach and capabilities.

3243   Sub factor 1 – Technical Approach
3244   In response to the solicitation, the Government will evaluate the Offeror’s proposed technical
3245   solutions to address tasks similar to those in the solicitation.
3246           Element 1- Viability of Shared Service Provider Offering
3247           The Government evaluates the Offeror’s proposal on whether the solution being offered
3248           by the SSP includes an installed and operational FSIO-compliant core financial system;
3249           the minimum FSIO-required services (as defined in the FSIO Migration Planning
3250           Guidance): IT Hosting and Administration, Application Management, Implementation
3251           Services; a SAS-70 Type II audit within the past year that resulted in either an
3252           unqualified opinion or with findings that are not significant enough to impact the
3253           organization’s ability to serve as an FM SSP; a financial audit within the past year that
3254           resulted in a clean opinion or a qualified opinion with findings that do not impact the
3255           organization’s ability to serve as an FM SSP; and standards and templates for systems
3256           implementation, interface configuration, operations, and ongoing support.
3257           Element 2 - Implementation Services


3258           The Government evaluates the proposal on the extent that the Offeror demonstrates a
3259           repeatable set of best practices for delivering standardized services for the
3260           implementation of their SSP solution. The Offeror’s proposal is also evaluated on the
3261           degree to which the Offeror’s response demonstrates flexibility to accommodate unique
3262           agency business processes and a formal governance model for configuration
3263           management that communicates changes and impacts to the customer.
3264           Element 3 - IT Hosting & Administration
3265           The Offeror’s proposal is evaluated to determine the degree to which the Offeror’s
3266           response demonstrates an understanding of the scope and complexity of infrastructure
3267           necessary and the level of effort involved to effectively provide IT Hosting and
3268           Administration of the underlying infrastructure for an shared service provider under this
3269           task as well as an ability to support increasing transaction volumes consistent with
3270           expanding services to meet customer needs, without adversely impacting current
3271           support levels.
3272           Element 4 - Application Management Services
3273           The Offeror’s proposal is evaluated to determine the degree to which the Offeror’s
3274           response demonstrates an understanding of the scope, complexity, and level of effort
3275           involved in managing a financial management application; staffing a help desk with
3276           regular hours of operation and personnel trained in the use of the [proposed software];
3277           and the provision and adequacy of formal procedures for communication, escalation,
3278           and resolution of issues, including critical issues, non-critical issues, incidents and
3279           problems.
3280           Element 5 - Service Level Agreement
3281           The Government evaluates whether the Offeror’s SSP SLA has a performance
3282           measurement methodology with metrics that address system availability, performance,
3283           and costs and meets the FMLoB Service Assessment Guide performance measures.
3284           Element 6 - Security and Incident Response
3285           The Offeror’s proposal is evaluated to determine the existence and adequacy of (1)
3286           COOP for each agency it services and for which successful Disaster Recovery Testing
3287           has been performed within the last 12 months; (2) the offered SSP is implemented with
3288           the appropriate security controls consistent with the Federal Information Security
3289           Management Act (FISMA) and NIST Special Publication 800-53; (3) processes for
3290           performing periodic testing and evaluation of information security controls in accordance
3291           with FISMA and NIST Special Publications 800-37 and 800-53A; (4) evidence that all
3292           environments and applications being used to provide shared service provider services
3293           have been FISMA Security Certified and Accredited (SC&A) within the last three years;
3294           (5) no indication of significant deficiencies from the most recent FISMA risk assessment
3295           review completed for the FM SSP; (6) documentation that a Federal Information Security
3296           Management Act (FISMA) risk assessment was completed within the last 36 months in
3297           accordance with NIST Special Publication 800-30; (7) an appointed information systems
3298           security officer as required under FISMA.


3300           Element 7 - Federal Enterprise Architecture
3301           The Government evaluates the Offeror’s proposed Target Enterprise Architecture for its
3302           alignment with the FEA Business and Data Reference Models.
3303           Element 8 - Requirements Compliance
3304           The Government evaluates the extent to which the Offeror demonstrates its customer-
3305           relevant financial management systems are substantially compliant with FFMIA system
3306           requirements, including FSIO mandatory requirements, USSGL, Common Government-
3307           wide Accounting Classifications (CGAC) structure, and accounting standards; and its
3308           ability to support [issuing agency] mandatory requirements.
3309           Element 9 - Feeder System Interfaces
3310           The Government evaluates the extent to which the Offeror demonstrates its ability to
3311           support an interface to the FM-related E-Gov Initiatives including E-Travel, Central
3312           Contractor Registration (CCR), and E-Payroll; its ability to use acceptable tools and
3313           processes to develop automated interfaces with feeder systems electronically as part of
3314           its solution. Support is defined as being capable of interfacing or integrating with one or
3315           more of the solutions provided by these initiatives. The Offeror’s proposal is evaluated
3316           on the capability of the Offeror’s existing feeder system interfaces to accommodate data
3317           interchange for the type of transactions processed and interchange methods used by
3318           [Issuing Agency] ’s feeder systems to provide continued automation of [Issuing Agency]
3319           business functions and processes to support the objectives and requirements of the
3320           solicitation; and experience implementing agreements similar to the interconnection
3321           security agreement and Memoranda of Understanding outlined in NIST Special
3322           Publication 800-47 for agency feeder systems such as Federal ePayroll, eTravel,
3323           SmartPay credit card systems, etc.
3324           Element 10 - Enhancement Development Approach
3325           The Offeror’s proposal will be evaluated on their demonstrated ability to provide software
3326           enhancements to address customer unique requirements in such a way that does not
3327           impact the core vendor software Commercial Off-the-shelf (COTS) product.
3328           Element 11 - Financial Management Reporting
3329           The Government evaluates the extent to which the Offeror demonstrates their SSP
3330           solution provides standard and ad hoc reporting capabilities that fulfill [Issuing Agency]’s
3331           objectives and requirements for financial management reporting. The Offeror’s proposal
3332           is evaluated on the capability of reports provided to fulfill external reporting
3333           requirements; to convey information in a clear, concise, and easy to use manner; and to
3334           enable more efficient financial control and improved financial management decision
3335           making within [Issuing Agency].

3336   Sub factor 2 – Management Approach
3337   The Government assesses the Offeror’s ability to successfully manage shared service
3338   provider implementations and operations by evaluating its structure, quality focus,
3339   business operations, Human Resource practices, and Subcontracting Plan.


3340           Element 1- Organizational Structure
3341           The Government evaluates the Offeror’s proposed organizational structure for
3342           the extent to which streamlined business operations, rapid decision making
3343           capability, and effective delivery of services is likely.
3344           Element 2 - Quality Assurance Plan
3345           The Government evaluates the QA Plan presented by the Offeror to ensure high
3346           quality in its SSP solution. Consistency with the proposed QASP, PWS, and SLA
3347           is also evaluated.
3348           Element 3 - Ability to Recruit, Train, and Maintain High–Quality Personnel
3349           Offerors shall provide a Compensation for Professional Employees Plan for
3350           evaluation and evidence that staff at each data center providing shared service
3351           provider services have the appropriate security clearances as required by NIST
3352           Federal Information Processing Standard 201, PIV Part1.
3353           Element 4 - Subcontracting Plan (large businesses and federal agencies
3354           proposing the use of contractors)
3355           The Offeror must identify key aspects of its Subcontracting Plan and how the
3356           Offeror plans to meet or exceed the small business contracting goals set forth in
3357           the solicitation.
3358           Element 5 - Key Personnel
3359           The Offeror is evaluated on the suitability of proposed Key Personnel, the
3360           applicability and quality of their skill and experience. While no minimum
3361           experience is required, the Government will evaluate the extent to which
3362           proposed key personnel resumes demonstrate the full breadth of financial
3363           management and technical expertise necessary to implement, host, and manage
3364           a core financial management solution. Key personnel with financial personnel
3365           certifications (e.g., Certified Public Accountant - CPA; Certified Government
3366           Financial Manager - CGFM; Certified Internal Auditor - CIA; Certified
3367           Management Accountant - CMA; Certified Information Systems Auditor - CISA;
3368           and Certified Information Security Manager – CISM) are rated higher than Key
3369           personnel without a certification.

3370   M.3.7         Cost Factor Evaluation Criteria
3371   (1)     The Offeror is required to submit all cost data in the format indicated in the
3372   solicitation (See Sections B, J, and L). Offerors are required to submit their proposed
3373   costs for the entire period of performance, as set forth in the appropriate attachment to
3374   Section J of the solicitation. The evaluation period commences with the start of work
3375   which shall be assumed to be [date].


3376   (2)   The Government will evaluate the proposed costs for completeness and
3377   reasonableness. Reasonableness of the overall cost will be determined on the basis of
3378   adequate cost competition and by comparison with the Independent Government Cost
3379   Estimate (IGCE).
3380   (3)     The Government may evaluate cost realism with regard to the ability of the
3381   Offeror to meet objectives and requirements in terms of skills required, complexity of
3382   disciplines, and job difficulty if the Government deems such analysis necessary. The
3383   Offeror’s cost proposal will be compared to the technical proposals to determine the
3384   Offeror’s (a) understanding of work to be performed and (b) capability and capacity to
3385   provide the required services and accomplish the required objectives and requirements.
3386   Unrealistically low costs may indicate a lack of complete understanding of the objectives
3387   and requirements, a high–risk approach to performance, and/or an inability to attract
3388   and maintain a high–quality workforce. The Government considers the findings of such
3389   analysis regarding an Offeror’s ability to perform and the risk of its approach.
3390   (4)     The Government bases the cost evaluation for all proposals on the total
3391   Discounted Life Cycle Cost (DLCC) for each proposal. The total DLCC for the contract
3392   is the total of the costs to [issuing agency] for each contract period (base and option
3393   periods) with appropriate discount rates applied. The Government will use the discount
3394   factors based upon the nominal discount rate specified in the current OMB Circular A–
3395   94.