NETCENTS_2_Application Services_SB_Final_RFP_Amendment 0003_15_Jun_10.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

1. CONTRACT ID CODE

See Block #2

PAGE OF PAGES

2. AMENDMENT/MODIFICATION NO.

3. EFFECTIVE DATE

15 JUN 2010

4. REQUISITION/PURCHASE REQ.NO.

5. PROJECT NO. (If applicable)

6. ISSUED BY 754 ELSG/ES CODE FA8771 7. ADMINISTERED BY (If other than Item 6) CODE

DEPARTMENT OF THE AIR FORCE

HQ 754 ELSG/KA

490 EAST MOORE DR., SUITE 270

MAFB - GUNTER ANNEX AL 36114-3000

MARGIE A. JOHNSON 334-416-6341

MARGIE.JOHNSON@GUNTER.AF.MIL

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code) (X) 9A. AMENDMENT OF SOLICITATION NO.

TO ALL PROSPECTIVE OFFERORS

FA8771-09-R-0021

X

9B. DATED (SEE ITEM 11)

20 MAY 2010

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 13)

CODE FACILITY CODE

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers is extended, X is not extended.

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER.

If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATION OF CONTRACTS/ORDERS,

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

(X )

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: ( ) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NO. ITEM

10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

See Schedule

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print).

16A. NAME AND TITLE OF SIGNER (Type or print)

LINDA R. LOWMILLER

15B. CONTRACTOR/OFFEROR

15C. DATE SIGNED 16B. UNITED STATES OF AMERICA

16C. DATE SIGNED

(Signature of person authorized to sign)

BY________________________________________

(Signature of Contracting Officer)

NSN 7540-01-152-8070 30-105 STANDARD FORM 30 (REV.10-83)

PREVIOUS EDITION UNUSABLE Prescribed by GSA ConWrite Version 6.12.0 FAR (48 CFR) 53.243 Created 15 Jun 2010 1:29 PM

SCHEDULE OF CHANGES

FA8771-09-R-0021 0003

The purpose of this amendment is to provide a corrected attachment.

1. Section J, Attachment 16, Application Services Small Business Systems Sustainment

Firm Fixed Price Sample Task Order, provided with Amendment 0002 did not reflect all the changes provided within the Schedule of Changes. Therefore, the attached Section J, Attachment 16, Application Services Small Business Systems Sustainment Firm Fixed

Price Sample Task Order hereby replaces Section J, Attachment 16, Application Services

Small Business Systems Sustainment Firm Fixed Price Sample Task Order in

Amendment 0002.

2. No other changes are made as a result of this amendment.

Section J, Attachment 16

FA8771-09-R-0021-0003

NETCENTS-2 APPLICATION SERVICES SMALL BUSINESS

SUBFACTOR 3 – Systems Sustainment Firm Fixed Price Sample Task Order

The competitive nature of this contract necessitates that each respondent propose a solution to a sample task that will assist the Source Selection Evaluation Team in its efforts to assess the depth and breadth of each contractor's capabilities. This sample task order will be evaluated as a “best value” competition and not solely as a “price” competition. The Government does not expect to receive any deliverable that is

CDRL-driven in connection with this sample task order proposal.

The contractor shall use the information contained in this sample task order to prepare a proposal for the

Government‟s evaluation of meeting the stated requirements.

1. ASSUMPTIONS

1.1 Period of Performance. While a typical task order will not exceed five years, the offeror is required to provide pricing information IAW Section J, Attachment 14, Price Proposal Workbook.

1.2 Real World Task Order Criteria. For the purposes of this evaluation, the Government will not evaluate or ask the offeror to price the following activities. They are included here so that offerors understand that these types of activities would be included in real world system sustainment task orders:

Project Management; Maintenance of On-line Documentation; User Training; Systems Deployment

Support; Development and Test Environment creation and maintenance (to include Systems

Administration and Database Administration); COTS software purchase and management, and Quality

Assurance activities.

1.2.1 Commercial-off-the-Shelf (COTS). In a real world task order, the purchase and management of

COTS software may be included in real world system sustainment task orders.

1.2.2 Documentation Requirements. In a real world task order, maintenance of On-line

Documentation, Monthly Status Reports, final, reviewed copies of system support documentation, Technical Analysis Reports, Test Reports, Copies of Software Product End Item for Release, release instructions, user guides, hardware and software documentation. For documentation purposes of this sample task order, the offeror needs to consider only documentation efforts specified in Section 5, Requirements.

1.2.3 Technical Meetings. In a real world task order, the offeror would likely be required to meet with Government representatives within 10 workdays after the contract award to reach a common understanding of task order requirements, deliverables, and Government expectations. The Quality Assurance Surveillance Plan Addendum would also be finalized at this meeting. The contractor would also provide technical expertise for technical reviews and meetings related to the requirements of the task order.

1.2.4 Site Locations, Furnishings and Travel. In a real world task order, locations for the conduct of the task order would be specified as would equipment to be provided by the Government. For this sample task order, little travel is required; assume 1% of labor costs.

1.2.5 Deliverables. The following are typical CDRLs that would be expected in a „real world‟ task order:

Monthly Status Report

Final copies of system support documentation

Technical Analysis Report

Copies of Software Product End Item for Release

1.2.6 Surge Requirements. In a „real world‟ task order, the Government would require the contractor to meet surge requirements by providing additional Full Time Equivalent (FTE) personnel. If a surge condition became a firm requirement, the Government (PCO) would determine if it falls within the scope of the task order. Upon such a determination, the Government (PCO) would notify the Contractor of the need to exercise this option for Surge Capability. Upon written notification of the Government‟s intent to exercise this option, the Contractor would identify qualified personnel to meet the requirement for both the

Base Period and the Option Period.

1.2.7 Emerging Standards and Technologies. Other requirements that would be included in real world system sustainment task orders relate to requirements that the Contractor must keep up to date with emerging standards and technologies that impact Air Force systems and infrastructure which include but are not limited to:

a. New Operating Systems such as Vista and new versions of Solaris and Windows

b. New Internet Protocol Version 6.0 (IPv6)

c. New browsers such as I.E. 8.0

d. Security requirements such as Security Technical Implementation Guide (STIG) and Gold Disk

e. Global Information Grid (GIG) and Net-Centric Enterprise Services (NCES)

2. INTRODUCTION

The Billeting System (BS) was developed in the 1990‟s to facilitate the administration of short-term, long-term, and permanent lodging facilities for active duty and retired military personnel, their families, and

DoD civilian employees, at bases within the 123 rd

Mission Support Wing.

3. OBJECTIVE

The objective of this hypothetical task order is to provide system sustainment services in support of the rd

Mission Support Wing Billeting System (BS). The Program Office for the system is assumed to be at

MAFB-Gunter Annex, Montgomery Alabama.

4. SCOPE

The Contractor shall analyze, develop, and evaluate application software to sustain the legacy Wing

Billeting System. The contractor shall support the J2EE architecture to enhance anticipated growth, encourage component-oriented code reusability, and leverage the strengths of inter-tier communication.

The contractor shall organize business rules into Enterprise Java Beans (EJBs), to develop the application within the J2EE architecture and house and distribute these EJBs from the Java Application

Server. The Contractor shall use a documented and generally accepted software development methodology to sustain the system. The Contractor‟s methodology shall include use of the IBM/Rational tools currently in use. These tools include but are not limited to: RequisitePro, Rational Rose, SoDA, ClearCase, ClearQuest, Quality Management Solutions, ProjectConsole, Purify, Quantify, PureCoverage, and Robot. The software development approach shall permit incremental phases to be defined and delivered. Additionally, any required software development must comply with the Clinger-Cohen Act, DoD 5000 series directives, and Section 508 of the Americans with Disabilities Act, eGOV, and IT

Accessibility standards as applicable.

System sustainment is defined as the processes, procedures, people, materiel, and information required to support, maintain, and operate the software and hardware aspects of a system. The Contractor shall provide all necessary personnel, supervision, management, materials, non-personal technical services, and equipment to perform system sustainment support services for the BS.

5. REQUIREMENTS

The operational environment, operational test environment, and independent test environment is assumed to be Government owned and managed, and the development environment is on contractor facilities, and associated hardware and software is Government-off-the-shelf (GOTS) with some Commercial-off-the-Shelf (COTS) products embedded. Assume the contractor has access to the Governments help desk tracking system. The testing equipment and all hardware and software used at the contractor facility are assumed to be Government furnished. The system expects one major (baseline) release per year (releasing 100% of code), quarterly releases (modifying 10% of the code), and maintenance releases (modifying 15% of the code) to correct identified deficiencies. For the purpose of this evaluation, the defect rate is assumed to be zero. The following table provides system information that can be used to address technical and pricing subfactors.

Factor Data

Code and data complexity High

Stability High

Number of concurrent users 72

Application age 10 years

Function Points Inputs

External Inputs 50 Input Screens

External Outputs 50 Screen Reports

50 Printed Reports

Logical Internal Files 120 Database Files

External Interfaces 6

External Inquiries 20

Initial response time <2 seconds

Life expectancy 5+years

Operating System Solaris 8

Platform Sun

Factor Data

Programming languages J2EE

Programs 6

Database ODBC

COTS Crystal Reports 2008

Avg Transactions per Day 3600

Interfaces Four of the bidirectional interfaces are real-time/on-demand/system-to-system type transactions with a volume of

75 average transactions/interchanges per day total and 1 batch monthly interface that exchanges 200 transactions average per month. The input only interface is real-time/on-demand/system-to-system type transactions with a volume of

175 average transactions/interchanges per day

Upgrades The application experiences 1 OS upgrade per year

Average Help Desk Call Volume 100 calls per month for Tier 2

50 calls per month for Tier 3

5.1 Systems Support

The Contractor shall design, develop, test and package systems and software changes as well as provide problem resolutions for the existing system. The Contractor shall maintain the current baseline of the system and provide software changes and problem fixes to these baselines as required. The Contractor shall provide to the Government all developed, modified, or converted source modules, processes, programs, scripts, operating instructions, databases, system files, documentation, test files and test conditions used to develop each approved systems change request.

5.2 Help Desk Support

The contractor shall provide continuous help Help Desk Tier 1, Tier 2, and Tier 3 support 7-days a week, 365 days a year. The contractor shall provide patch management support for multiple software versions, providing technical assistance, training, warranty and maintenance, for reporting deficiencies in software and hardware. The contractor shall provide methods for responding to customer requests and order processing. The contractor shall use deficiency reporting tools and establish methods for resolving and closing deficiency reports. The contractor shall monitor discrepancy reports, provide performance improvement recommendations, identify environmental changes and changes in Government equipment or regulations and make the recommended performance improvement, environmental, or equipment changes as requested by the Government.

Definitions:

Tier 1: Provides basic application software and/or hardware support to callers.

Tier 2: Provides more complex support on application software and/or hardware and is usually an escalation of the call from Tier 1.

Tier 3: Provides support on complex hardware and operating system software and usually involves subject matter experts.

5.3 System Maintenance

The contractor shall provide system maintenance activities to include maintaining the existing legacy system and environments IAW disciplined engineering practices. The contractor shall develop and maintain software components according to a systems engineering approach that is in accordance with

Federal Desktop Core Configuration (FDCC) guidelines and includes appropriate configuration management to include their methods and processes to identify, control, monitor, verify and manage software configuration items. The contractor shall employ disciplined systems engineering processes, using commercial best practices in accordance with of AFI 63-1201, Life Cycle Systems Engineering, for systems engineering processes in planning, architecting, requirements development and management, design, technical management and control, technical reviews, technical measurements, integrated risk management, configuration management, data management, interface management, decision analysis, and test and evaluation, and verification and validation.

5.4 Testing

5.4.1 Regression Testing

The contractor shall establish and maintain a production environment that mirrors the operational environment in order to perform regression testing of the entire system for each upgrade or patch installed to ensure continuing functionality. The development environment shall include tools, test suites, support databases, a software test lab, configuration management, hardware spares, process and procedure documentation, and delivered source code. If a test fails, the contractor shall analyze and document test data for each component and rework the system to establish functional equilibrium.

Testing shall be performed in two steps: operational testing, then system acceptance testing and be performed IAW AFI 99-103 Test and Evaluation. The contractor shall provide a logical test process that minimizes interruptions and avoids sustained downtime and presents a contingency procedure to be implemented in the event of systems failure during testing. The contractor shall develop scripts and conduct testing for the application, database, and operating system IAW test plans.

5.4.2 Performance Testing

The contractor shall provide system performance testing IAW AFI 99-103 Test and Evaluation. In the event the system does not meet the availability rate, the acceptance testing shall continue on a day-by-day basis until the availability rate is met. In the event the system has not met the availability rate after 60 calendar days, the Government reserves the right to require replacement of the component(s) adversely affecting the availability rate at no additional cost. Availability rate does not include scheduled downtime for software and hardware upgrades and maintenance. The contractor shall conduct testing for the effects of load and stress IAW test plans.

5.4.3 Quality Assurance Program

The Contractor shall perform Software Quality Assurance testing on all efforts under this contract. The

Contractor shall implement and maintain an effective quality improvement program. The Contractor shall assist the Government in the development of test plans, test data, and test conditions; evaluate test results to ensure the Government requirements are met; review and evaluate systems and software changes, documentation, and configuration control processes to ensure requirements are met; and provide recommendations for improvement. The contractor shall develop and implement processes for systems and software changes, documentation, and configuration control to ensure requirements for

Certification and Accreditation (C&A) are satisfied.

5.5 Configuration Management

The contractor shall perform Configuration Management (CM) activities. CM activities include baseline identification, change control, status accounting, and auditing. The contractor shall conduct configuration management, change management, and release management to plan, identify, control, monitor, verify, and manage software configuration items.

5.6 Software Distribution

The contractor shall make distribution of software modifications or minor enhancements IAW AFI 33-114

Software Management. The contractor shall distribute software, documentation, source code, and data for test and fielding or minor enhancements. The contractor shall support electronic distribution of software, documentation, and supporting materials.

5.7 Security

The contractor shall assist in the prevention of computer hacking and other security problems by implementing preventive measures in compliance with the AF enterprise architecture. The contractor shall ensure that any development/sustainment efforts provided shall be fully compatible with existing

Government firewalls and intrusion detection systems.The contractor shall provide security and information assurance support, protecting information and information systems, and ensuring confidentiality, integrity, authentication, availability and non-repudiation. The contractor shall provide support for Certification and Accreditation (C&A) processes, DIACAP processes, SISSU processes, and

Enterprise Information Technology Data Repository (EITDR) certification.

5.8 Protection of System Data

The contractor shall protect system design-related documents and operational data whether in written form or in electronic form via a network in accordance with all applicable policies and procedures for such data, including DOD Regulations 5400.7-R and 5200.1-R to include latest changes, and applicable service/agency/ combatant command policies and procedures. The contractor shall protect system design related documents and operational data at least to the level provided by Secure Sockets Layer

(SSL)/Transport Security Layer (TSL)-protected web site connections and with DoD‟s Common Access

Cards(CAC). In either case, the certificates used by the contractor for these protections shall be DoD approved Public Key Infrastructure (PKI) certificates issued by a DoD approved External Certification

Authority (ECA) and shall make use of at least 128-bit encryption.

5.9 Travel

The contractor shall coordinate specific travel arrangements with the Contracting Officer or Contracting

Officer‟s Representative to obtain advance, written approval for the travel about to be conducted. The contractor‟s request for travel shall be in writing and contain the dates, locations, and estimated costs of the travel.

If any travel arrangements cause additional costs to the task order that exceed those previously negotiated, written approval by CO is required, prior to undertaking such travel.

5.10 Other Direct Cost (ODC)

The contractor shall identify ODC and miscellaneous items. No profit or fee will be added.