A07_Draft_Solicitation_W91CRB-17-R-0019.pdf

CODE

(Hour)

PAGE(S)

until 05:00 PM local time 03 Mar 2017

X

A X B X C

D

EX

X G F 51 - 59

H

RATING PAGE OF PAGES

7. ISSUED BY

(Date)

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

Previous Edition is Unusable 33-134 STANDARD FORM 33 (REV. 9-97)

Prescribed by GSA FAR (48 CFR) 53.214(c)

1 59

(If other than Item 7)

15A. NAME 16. NAME AND TITLE OF PERSON AUTHORIZED TO

AND

ADDRESS

SIGN OFFER (Type or print)

OF

OFFEROR

AMENDMENT NO. DATE

15B. TELEPHONE NO (Include area code) 17. SIGNATURE15C. CHECK IF REMITTANCE ADDRESS

IS DIFFERENT FROM ABOVE - ENTER

SUCH ADDRESS IN SCHEDULE.

18. OFFER DATE

1. THIS CONTRACT IS A RATED ORDER

UNDER DPAS (15 CFR 700)

2. CONTRACT NO.

W91CRB 8. ADDRESS OFFER TO

See Item 7

9. Sealed offers in original and 1 copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if handcarried, in the depository located in

CAUTION - LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and

ACC-APG

conditions contained in this solicitation.

10. FOR INFORMATION

CALL:

A. NAME (NO COLLECT CALLS)

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

2 - 10

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

11 - 28 J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

30 - 31

X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 32 - 33

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror) M

L INSTRS., CONDS., AND NOTICES TO OFFERORS

EVALUATION FACTORS FOR AWARD

NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. DISCOUNT FOR PROMPT PAYMENT

(See Section I, Clause No. 52.232-8)

14. ACKNOWLEDGMENT OF AMENDMENTS

(The offeror acknowledges receipt of amendments

AMENDMENT NO. DATE

to the SOLICITATION for offerors and related documents numbered and dated):

FACILITY

12. In compliance with the above, the undersigned agrees, if this offer is accepted within calendar days (60 calendar days unless a different period

SOLICITATION, OFFER AND AWARD

X

(X) SEC. DESCRIPTION (X) SEC. DESCRIPTION PAGE(S)

PART I - THE SCHEDULE

26. NAME OF CONTRACTING OFFICER (Type or print) 27. UNITED STATES OF AMERICA 28. AWARD DATE

EMAIL:TEL: (Signature of Contracting Officer)

CODE CODE

B. TELEPHONE (Include area code) C. E-MAIL ADDRESS

AWARD (To be completed by Government)

19. ACCEPTED AS TO ITEMS NUMBERED 20. AMOUNT 21. ACCOUNTING AND APPROPRIATION

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

10 U.S.C. 2304(c)( ) 41 U.S.C. 253(c)( ) (4 copies unless otherwise specified)

23. SUBMIT INVOICES TO ADDRESS SHOWN IN ITEM

24. ADMINISTERED BY (If other than Item 7) CODE 25. PAYMENT WILL BE MADE BY CODE

PART IV - REPRESENTATIONS AND INSTRUCTIONS

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

34 - 49

PART II - CONTRACT CLAUSES

ACC - APG - W91CRB

4310 BOOTHBY HILL AVE

ABERDEEN PROVING GROUND MD 21005-3013

FAX:

TEL:

FAX:

TEL:

NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".

SOLICITATION

6. REQUISITION/PURCHASE NO.5. DATE ISSUED

03 Mar 2017

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

W91CRB-17-R-0019

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 12 Months ART Support

FFP

Pursuant to the Army Procurement Response Team PWS included herein.

FOB: Destination

NET AMT

0002 700 Job ART Support

T&M Extended Hour and FY End Support per PWS paragraphs 2.2.4 and 2.4.3. Not to Exceed 700 Hours.

TOT ESTIMATED PRICE

CEILING PRICE

Travel

T&M Travel expenses will be reimbursed pursuant to PWS paragraph 4.4.

Contractor Manpower Reporting

FFP

Pursuant to PWS paragraph 4.9. This CLIN is Not Seperately Priced

Contract Deliverables

FFP

Pursuant to PWS paragraph 5.0. This CLIN is Not Seperately Priced.

0006 1 Job Transition-In

FFP

Pursuant to PWS paragraph 2.9

1001 12 Months OPTION ART Support

FFP

1002 700 Job OPTION ART Support

T&M Extended Hour and FY End Support per PWS paragraphs 2.2.4 and 2.4.3. Not to

OPTION Travel

T&M

OPTION Contractor Manpower Reporting

FFP

OPTION Contract Deliverables

FFP

2001 12 Months OPTION ART Support

FFP

2002 700 Job OPTION ART Support

T&M Extended Hour and FY End Support per PWS paragraphs 2.2.4 and 2.4.3. Not to

OPTION Travel

T&M

OPTION Contractor Manpower Reporting

FFP

OPTION Contract Deliverables

FFP

3001 12 Months OPTION ART Support

FFP

3002 700 Job OPTION ART Support

T&M Extended Hour and FY End Support per PWS paragraphs 2.2.4 and 2.4.3. Not to

OPTION Travel

T&M

OPTION Contractor Manpower Reporting

FFP

OPTION Contract Deliverables

FFP

4001 12 Months OPTION ART Support

FFP

4002 700 Job OPTION ART Support

T&M Extended Hour and FY End Support per PWS paragraphs 2.2.4 and 2.4.3. Not to

OPTION Travel

T&M

OPTION Contractor Manpower Reporting

FFP

OPTION Contract Deliverables

FFP

Section C - Descriptions and Specifications

PERFORMANCE WORK STATEMENT

1.0 Scope

The Office of the Deputy Assistant Secretary of the Army for Procurement (ODASA(P)) is responsible to Army leadership for the management, measurement, oversight, and continuous improvement of the Army’s procurement mission. ODASA(P) serves as the executive agent for all contracting services and outcomes across the Army, for both the Continental and outside the Continental United States (CONUS and OCONUS). A key mission of the ODASA(P) is to provide organizational oversight and end-user support for the procurement business systems in use across the Army Contracting Enterprise. ODASA(P) ensures that contracting tools and systems are available, reliable and properly maintained to support the procurement of systems, goods and services for soldiers both in garrison and in deployed environments. Additionally, the ODASA(P) serves as the singular advocate for business systems impacting the Army Contracting Enterprise.

The purpose of this Performance Work Statement (PWS) is to obtain tactical and strategic technical and functional support of the current contract writing system environment throughout the Army’s acquisition community. Tactical and strategic support includes: analytical, technical and functional engineering support services for the deployment, upgrade, and sustainment of the Department of Defense (DoD) Standard Procurement System’s (SPS) contract writing software known as Procurement Desktop-Defense (PD²). The test and production SPS-A enclaves are located in Radford, VA at the Army Acquisition, Logistics & Technology Enterprise Systems & Services (ALTESS) with a COOP site located in Huntsville, AL at Redstone Arsenal at the Network Enterprise Center-Redstone (NEC- R). The contractor shall be required to perform the SPS-Army Enclave Support task listed in the PWS at both locations. The team performing the work under this PWS is referred to as the Army Response Team (ART).

The ART shall also support the SPS-Army (SPS-A) enclave and tickets that are out of scope of the SPS Joint Program Management Office’s Help Desk. The services sought herein shall also include but not limited to the PD² integration software components incorporated in the suite of tools known as the PD² Adapter, SPS Legacy and 3rd Party Integrations, General Funds Enterprise Business System (GFEBS), Electronic Document Access (EDA) and the Configuration Data Repository-Administration (CDR/CDR-A). The Contractor shall work closely with ODASA(P) and other servicing organizations including but not limited to: Army Business Center for Acquisition Systems (ABCAS), the Virtual Contract Enterprise (VCE) Acquisition Logistics and Technology Enterprise Systems and Services (ALTESS), and Network Enterprise Center Redstone (NEC-R) to deliver quality, day-to-day engineering support services to the Army’s SPS user community.

In additional to SPS support, this PWS also include support for the following areas:

User and System Support for:

o Federal Procurement Data System-Next Generation (FPDS-NG) o General Funds Enterprise Business System (GFEBS)

Targeted Training for the Army Contracting Enterprise Service Model Maturation

The services to be performed are non-personal in nature as defined by FAR 37.103. Through the delivery of these services, ODASA(P)’s objectives are to improve the Army Contracting Enterprise workforce with knowledge and training, improve customer service and field productivity through consolidation and standardization, improve processes, enhance subject matter expertise in functional areas, and create more effective test management and execution to build better products and understanding to the contracting workforce.

The following sections provide the support requirements

2.0 Requirements

2.1 Program Management and Control

The contractor shall monitor and control program scope through the understanding of the ODASA(P) Enterprise Business Systems Division (EBSD) organization mission, vision, and goals. The contractor shall plan, manage, integrate and control the requirements defined in this PWS and successfully complete the work required. The contractor shall resolve any issues and problems brought to their attention by the Army during the performance of this contract. The contractor shall monitor contract performance and ensure the accurate and timely submission of reports. The contractor shall provide management services for the contract, including the following, at a minimum:

2.1.1 Schedule Management

The contractor shall outline the necessary tasks and demonstrates the understanding of each task as it relates to desired program outcomes. The project manager shall identify project milestones, maintain an Integrated Master Schedule (IMS), and report progress against this schedule on a monthly basis.

The Integrated Master Schedule (IMS) shall be delivered on the 1st business day of each month.

2.1.2 Risk Management

The contractor shall develop a Risk Management Plan, and implement a Risk Assessment Matrix as a method to track and manage program risks. The Risk Management Plan shall include the analysis of likely risks, as well as mitigation strategies and action plans to assist the project should common problems arise. The Risk Assessment Matrix serves as a register where risks are identified, assessed, and prioritized based on the probability of the risk occurring and the potential consequence to the program. Risk assessments shall be conducted on an ongoing basis to ensure the timely application of resources to minimize, monitor, and control the probability and/or impact of unfortunate events or to maximize the realization of opportunities.

The Risk Management Plan shall be reviewed with the Government when changes are made within the Matrix. The Risk Management Plan shall be delivered on a quarterly basis or as required by the COR.

2.1.3 Resource Management

The contractor ensure proper resources are allocated to successfully complete the work outlined in this PWS, monitor the completion of each task, and provide a detailed Resource Plan that outlines the allocation of resources in support of each task. The outline includes but is not limited to name, role, and responsibility.

The Resource Management Plan shall be delivered on the 1st business day of each month.

2.1.4 Management Reporting

The contractor shall deliver a variety of management reports that communicate project status and strive to improve the services being provided.

The contractor shall submit Weekly Project Status Reports by close of business every Monday that contain updates on project schedule, identified risks, mitigation strategies, resource constraints, known issues, and open actions.

The contractor shall submit a Monthly Performance Status Report that shall contain but not be limited to a summary of the technical environment (e.g., SPS Service release versions across the number of Army Sites), Financial Status including but not limited to CLIN balances, and any personnel resource changes. The report shall be delivered on the 10th of each month or prior business day if day falls on weekend or holiday.

The contractor shall participate in Quarterly Progress Meetings with the Army to review current support requirements, highlight any notable trends or systemic issues, and identify any contract or service level concerns.

These meetings will occur at either the Contractor or government facility. Additional meetings may be scheduled as required by either the Army or Contractor. The contractor shall assist in producing the agenda and meeting briefing, which shall be exchanged at least three (3) workdays prior to each meeting.

Weekly Project Status reports shall be delivered at the close of business (COB) every Monday.

Monthly Performance Status reports shall be delivered on the 10th of every month or prior business day if day falls on weekend or holiday.

Quarterly Progress meetings shall be held quarterly, during the first week of the following quarter. Content for the meeting shall be delivered three workdays prior to each meeting.

2.2 Standard Procurement System (SPS) Program Support

The Standard Procurement System (SPS) Procurement Desktop – Defense (PD²) software is currently in sustainment, and service releases are planned. The Army plays a critical role in the requirements development and testing of delivered software changes.

2.2.1 SPS Requirements

The contractor shall support ODASA(P) by providing impact analyses for all requirements submitted to the JPMO for consideration. Analysis should focus on the Army’s use of SPS, including impacts to interfacing systems.

Additionally, the contractor shall vet and prioritize requirements from an Army perspective, and participate in DLA JPMO Operational Requirements Committee (ORC) meetings and review sessions, providing the Army perspective and/or prioritizations for group consideration.

Summary of meeting minutes and actions to include content summary, risks, and recommended actions shall be delivered within 2 business days of the meetings

2.2.2 SPS Testing

As the SPS software vendor delivers service releases and other software updates to the Government, the Army has a role in the JPMO’s Software Acceptance Testing (SAT) process, helping to ensure that all potential software defects, failed requirements, and other anomalies are discovered, documented, and communicated, and the testing process is managed effectively.

The contractor support SPS testing efforts on behalf of the Army. The contractor shall be required to partner with Army Stakeholders within the community (ACC, MEDCOM, USACE, NGB, etc.,) to solicit testing support across the enterprise. The support contractor shall develop training, documentation, business processes, based on operational use on behalf of the Army. The contractor shall also complete execution of desired/assigned test scripts and conduct excursion testing to ensure the software will perform operationally in the Army environment.

The support team shall participate in the following SPS Service Releases release testing processes unless otherwise directed by the ODASA(P):

PD² Application Sybase Adaptive Server Enterprise (ASE) PD² Adapter Document Transfer Utility (DTU) Application Server Framework (ASF) Out-of-cycle Sybase updates (as they are released by SPS vendor only) SPS Legacy Integration Releases Army Integrity Tool and associated edits Java Updates (as released by the SPS vendor for use with SPS) Integration-related “punch out” utilities (e.g., PDS Punch-out)

The support team shall work with the SPS JPMO to do the following for each release as required:

Participate in test script development/review sessions Determine the number of Army-specific man hours required to execute the JPMO’s prescribed test scripts Validate the test scripts to be used during each test Coordinate tester access to Army SPS test environment Manage and participate in test execution process to include test script and targeted excursion testing Report daily progress to ODASA(P) and the SPS JPMO During active test execution, participate in daily SPS JPMO status and review sessions Document and log all potential software defects or problems within the SPS JPMO bug tracking system Provide input to ODASA(P) regarding the acceptance or rejection of service releases and other tested software updates

This task includes the following ongoing subtasks (both in and out of active test cycles):

Review new or revised DoD or Army initiatives including upcoming and proposed system changes for possible impact on SPS, FPDS-NG, GFEBS, or the Army Business Intelligence Systems (ACBIS and VCE) for possible impact on each other

Maintain Army SPS test documentation for all releases tests Actively engage the Army SPS user community to:

o Advertise upcoming SPS testing events o Solicit for field-participation in SPS testing events o Gather requests for software change/improvements

2.2.3 SPS Test Environment Management

Manage Army SPS test server infrastructure (Windows servers, Solaris instances, and third party components) to ensure proper hardware and software configurations are installed and working properly

Work with hosting environment representatives (e.g., ALTESS) to mitigate or document information assurance risks, and test software functionalities, as necessary

2.2.4 After Hours Monthly Maintenance and Patch Testing

The contractor shall provide after hours support to perform application testing after monthly maintenance and Information Assurance driven-patching occurs at the SPS-A host facility. Testing shall be ad hoc and regression in nature and ensure the system is operational after the maintenance and patch activities have occurred.

2.2.5 Deployment Support – Installation and Training Services in Support of a new SPS Install Provide an approval process (Green Light Process) for each contracting office that is preparing to install a new version of the SPS software at non SPS-A sites. The approval will at a minimum insure that each database is sound and can safely be converted to the new version of the software. Each office will be required to go through this approval process prior to having access to the new software. The desk officer will be provided the status of each office as it is approved or rejected. If this process reveals that an office should not be upgraded, the ART team shall assist the office to correct the problem. This assistance may require reinstallation of SPS software (specifically Sybase and the PD² Database) components when such reinstallation is necessary to recover a site’s operations as the result of any downtime caused by a hardware or software failure as defined in the SPS Help Desk Agreement as a Severity 1 or 2 issue.

2.3 Standard Procurement System – Army (SPS-A) Enclave Support

2.3.1 Configuration Management

The contractor shall manage a comprehensive Configuration Management (CM) process in order to create and maintain a baseline record of all the components of the infrastructure for the purpose of maintaining system integrity and traceability. Infrastructure includes the hardware, software, network appliances, storage, and other components that comprise the SPS-Army system. The contractor shall update the Architectural System Design Document that documents the baseline infrastructure and CM Plan that documents the systematic configuration control process when changes to system components are necessary. Within the CM Plan, the contractor shall establish clearly defined roles and responsibilities of all SPS-A service providers and shall document these items in a responsibility assignment (RACI) matrix.

The Architectural System Design Document shall be maintained throughout the life of the contract and delivered on a quarterly basis or as required by the COR.

The Configuration Management Plan shall be maintained throughout the life of the contract and delivered on a quarterly basis or as required by the COR.

2.3.2 Operational Support

The contractor shall field an SPS-A System Administration Team that shall provide the necessary functional and technical support to maintain the day-to-day operations of the systems hosted within the SPS-A enclaves at ALTESS and the COOP site at NEC-R. Effective provisioning of support requires resources with skill sets capable of diagnosing, troubleshooting and resolving issues across a wide spectrum of technologies including, but not limited to: PD², PRweb, PD² Adapter, Sybase ASE, PowerBuilder, webMethods Integration Server, Citrix XenApp, Citrix Provisioning Server, VMware, MS SQL Server, MS Windows Server, and Sun Solaris. The contractor shall provide initial response to end-user requests for assistance within one hour.

The contractor shall provide post deployment support of the SPS-A capability to post solicitation data in a standard format to third-party web services automatically from the various SPS production databases. This implementation effort shall require resources that are familiar with the PD² data model, the PD² Adapter, Sybase ASE, and webMethods Integration Server.

Additional responsibilities include the documentation and execution of SPS-A Operations and Maintenance Standard Operating Procedures, to include: log review/analysis, database consistency checks, database backups/restores, integration upkeep, implementation of SPS Service Releases and Sybase Application upgrades, clause and standard data updates, user maintenance, and other routine tasks. In some cases, duties shall include assisting users with PD²-related functional matters and to support changes to the site-specific security model. In addition, the administration team is expected to run reports as needed using ACBIS, the FPDS-NG site, the EDA site, or other Army or DoD Business Intelligence systems.

The contractor shall perform all system administration (SA) duties in the PWS without anyone initiating a help desk ticket.

The SPS-A Operations and Maintenance SOP shall be reviewed, updated as required, and delivered on a quarterly basis throughout the life of the contract.

2.3.3 Technology Lifecycle Management

The contractor shall provide the Government with expert advice for the on-going optimum configuration of the SPS software components within the hosted environments that make up the SPS-Army Consolidated Enclaves. Support is required in determining both current and future hardware, software, and network configurations to support the core PD² contract writing software; the PRweb software; and the integration software components.

The contractor shall perform networking optimization tasks relative to the additional increased level of effort and shall include but are not limited to: conducting bandwidth analyses, conducting predictive analyses and troubleshooting, coordinating with external network support entities (e.g., DISA, 2RCC, Army Cyber Command, OCONUS service providers), coordinating with local Army site-level network points of contact, researching impacts of Army technology stack upgrades and integrations as they relate to legacy systems such as SPS. The contractor shall develop a weekly workload summary report to include actions taken, participants, next steps, POCs, as well as bandwidth analysis reports for Army locations that have exhibited symptoms of poor performance or have risk for developing potential impacts in the future. In addition, the contractor shall develop technology research reports for optimization of service delivery (e.g., technology refresh) as requested by the Government.

The Weekly Workload Summary Report shall be maintained throughout the life of the contract and delivered on a weekly basis as part of the weekly submission or as required by the COR.

The Technology Research Reports and Bandwidth Analysis Reports shall be maintained throughout the life of the contract and delivered on an ad hoc basis as required by the COR.

The contractor shall develop a Technology Lifecycle Management Plan to account for the technology refresh of the infrastructure within the SPS-Army enclaves. To assure continued supportability throughout its lifecycle, the contractor shall conduct an analysis to address issues of capability enhancement, technology vendor roadmaps, and end-of life support issues that may require premature technology refresh requirements. Effective and accurate license management is also essential to include in such a plan.

The Technology Lifecycle Management Plan shall be shall be maintained throughout the life of the contract and delivered on a quarterly basis or as required by the COR.

2.3.4 Continuity of Operations

The contractor shall maintain a Continuity of Operations Plan (COOP) to provide a repeatable methodology for the successful backup and recovery for all components within the SPS-A enclave. The contractor shall continue to analyze the existing COOP and Disaster Recovery (DR) strategy employed by the SPS-A Administration Team, and shall develop and refine a more complete and testable procedure that shall align with defined Army COOP guidance and vendor best practices. The contractor shall conduct a test of the COOP with end-user support.

The Continuity of Operations Plan shall be shall be maintained throughout the life of the contract and

The Continuity of Operations Test shall be tested delivered on a quarterly basis or as required by the COR.

2.3.5 Information Assurance

The contractor shall support the Government in complying with the Army’s Information Assurance (IA) processes and procedures in support of the SPS-A Enclaves. Specifically, the contractor shall provide direct input into the Plan of Action & Milestones (POA&M) template as part of the DoD Information Assurance Risk Management Framework (RMF) process to achieve and maintain system accreditation. The contractor shall perform the following:

Input and support to the Information System Security Officer (ISSO) to include but not be limited to:

maintaining the Plan of Action & Milestones in eMASS (or other Army approved tracking system) throughout the life of the contract and reviewed on a quarterly basis or as required by the COR paying particular focus on expiring and high risk items.

Actively participate in regular and periodic program security reviews to include documentation reviews and updates as well as consultation and performing key compliance activities and initiatives.

Identify and remediate risks associated with the SPS-A environment Update and maintain all ART deliverables as artifacts within the RMF repository as they align to RMF security controls and associated configuration control item (CCI) requirements.

2.3.6 Performance Management

The contractor shall develop a Performance Management Plan to outline the identification, collection, monitoring, and measurement of performance metrics necessary to assess the health of the SPS-A environments. The plan should focus on Reliability, Availability, Maintainability, and Scalability of the systems within the SPS-A enclave, and the optimization of application delivery to the end-user.

In order to address Delivery Optimization strategy, the contractor shall look at network optimization (to include the use of WAN optimizers) and software optimization (configuration changes to the baseline). In addition, the Performance Management Plan should collect data from both the data center and the end-point.

The Performance Management Plan shall be shall be maintained throughout the life of the contract and

2.4 Technical and Functional User Support for SPS

2.4.1 Field Support

The contractor shall provide information technology/engineering services to support the hardware/software infrastructure of all the U.S. Army’s SPS operational user community worldwide. The Army’s acquisition and SPS goals shall be achieved by approximately 8,100 acquisition professionals through the user of the software suite comprised of PD², the PD² Adapter, the SPS Legacy Integrations, and/or other government (or contractor) owned interfacing processes. The goal is to enable the various Army Commands (ACOMs); Army Service Component Commands (ASCCs); Direct Reporting Units (DRUs); and other Agencies to sustain operational success with PD² current and future versions.

The contractor shall manage a centralized Service Desk operation to include an incident, change, and problem management solution for support issues and provide initial response to end-user requests for assistance within one hour of receipt during the contracted service hours.

2.4.2 Escalation Procedures

User issues are reported either through the SPS JPMO Help Desk or the Army Enterprise Service Desk (AESD).

Either of these service/help desks could issue a service/help desk ticket to the ART team. When an issue develops that cannot be resolved through the SPS Help Desk or SPS-Army Enclave Service Desk and is escalated to the ART, ART shall take immediate action to resolve the issue or provide alternatives to eliminate or mitigate the issue during standard working hours of 0800-1700 EST. The contractor shall provide initial response to end-user requests for assistance within one hour.

2.4.3 After Hours Support

There are three areas of after hours support that the contractor shall support.

2.4.3.1 End of Fiscal Year Support

The contractor shall establish an End of Fiscal Year User Support Center (EOFYUSC) to support end-of-year contractual operations and ad hoc critical after hours support on an on-call basis.

The EOYUSC or After Hours Support staff shall coordinate with the JPMO and the Army Help Desk to track, monitor and resolve existing issues and service requests. If the EOYUSC or after hours support staff is concerned that a service request or issue is not receiving appropriate attention, then the staff shall consult with the ART Management Team to determine the appropriate plan of action and provide feedback to the user and Desk Officer.

The contractor staff disseminates pertinent information via the Army’s SPS e-mail listserver or other Army communication forum that may be in place. Service requests and issues and resulting resolutions that arise repetitively are documented and shared with Army users via the listserver or other communication forum that may be in place, as well as being reported to ODASA(P) and their service partners for posting to the appropriate Army SPS web site(s).

The period of performance of the EOFY support shall be no more than seven (7) calendar days prior to the start of new Fiscal Year. A minimum of one (1) functional and one (1) technical FTE shall be available on-call from 1700- 2400 Eastern Daylight Savings time (EST) during the weekdays and 0800-2400 on weekends. During the hours of operation, the staff shall perform the following tasks: Army tickets categorized as Severity 1 or 2 that are EOFY related, either through the SPS Help Desk or through the Army criteria, are immediately assigned to an EOFYUSC staff member and worked as priority. Other tickets in the queue and operational efforts (e.g., updating documentation) that can be accomplished when no other “hot” issues exist shall be worked to make the best use of the time. The contractor shall establish a dedicated phone number for the users to call during this time.

A daily status report shall be developed that tracks the total number of tickets received (i.e., total volume of new requests), the distribution of requests across the extended hour period, category, and all Severity 1 and 2 tickets with a description of the issue and resolution plan. The report should also indicate which requests received are critical to completing end of fiscal year (EOFY) related processing as well as any other “Hot Issues” that need to be brought to management attention. Daily status reports shall be emailed to ODASA(P) Desk Officer, Program Manager, and Contracting Officer’s Representative (COR) and reported in the subsequent weekly, monthly, and quarterly reports.

A summary report collating the weekly reports shall be delivered at the end of the period.

Daily status report shall be delivered each day Summary report shall be delivered at the end of the period.

2.4.3.2 After Hours Tier 2 Support

The period of performance of the critical after hours Tier 2 support shall be ad hoc by nature and only utilized during mission critical failures that require ART support during non-working hours (i.e., 1700-0800) Eastern Standard or Eastern Daylight Time) year round. For afterhours support that is not EOYUSC related, the staff shall work Army tickets categorized as Severity 1/Priority 1/Critical. The staff member shall work with the Help Desks and others to achieve timely resolution.

An After Action report shall be developed that details the total number of Severity 1/Priority 1/Critical tickets received, a description of the issue and resolution. This report shall be emailed to the ODASA(P) Desk Officer, Program Manager, and Contracting Officer’s Representative (COR) on a weekly basis and prior to invoicing the Government. The contractor shall accumulate these metrics and shall report the accumulative totals in the subsequent weekly, monthly, and quarterly reports.

After Action report shall be delivered on a weekly basis as needed and prior to invoicing for the support

2.4.3.3 After Hours Maintenance Support

The contractor may be required to work one weekend a month to perform software updates as required (e.g., Java update). ODASA(P) and the contractor shall ensure that the applicable weekend selected does not coincide with other work that may be done by other entities, e.g., ALTESS network maintenance weekend. The contractor shall work to ensure that the environment is restored to working order by the beginning of the work week through testing, server restarts, etc., as appropriate.

An After Hours Maintenance Support report shall be developed that summarizes the effort and result. This report shall be emailed to the ODASA(P) Desk Officer, Program Manager, and Contracting Officer’s Representative (COR) on a monthly basis and prior to invoicing the Government. The contractor shall include this report in the monthly and quarterly reports.

Maintenance Support report shall be delivered on a monthly basis as needed and prior to invoicing for the support.

2.5 Federal Procurement Data System-Next Generation (FPDS-NG) Support Primary FPDS-NG support is currently being provided by the Army Business Center for Acquisition Systems (ABCAS) in accordance with a Functional Support Agreement (FSA) between ABCAS and ODASA(P). The support contractor shall provide depth in support and user documentation, as it pertains to these areas including:

Data Validation - On a quarterly basis, the support team shall perform data verification and validation (V&V) activities on behalf of the Army, including a review of the Army’s contract action reporting from the previous quarter. The support team shall work with ODASA(P) to establish V&V criteria, report structures, and a communication plan possible impact on SPS, FPDS-NG, GFEBS, or the Army Contracting Business Intelligence System (ACBIS) for possible impact on each other

Provide policy guidance and training for Army users Test new releases prior to fielding Respond to data calls and contracting offices that created recurring and special reports to external executive agencies Provide Level 2 Help Desk support through SPS authorized users who support over 6500 Army contracting professionals Provide functional and technical SMEs for FPDS-NG Website data correction support User Documentation and training tips The support team shall serve as the Army representative to the GSA FPDS-NG program office to provide input and feedback on system change requirements, and develop/submit Army requirements for change within the system. The support team shall support the following activities:

o Proposed system change requirements gathering and analysis o Participation in FPDS-NG program office stakeholder change control activities o Detailed change control activity reporting and impact analysis to ODASA(P)

Each DoD component is required to appoint a representative to be empowered to review and correct data within the FPDS-NG system, in accordance with GSA rules and guidelines. The support team shall provide a primary and backup point of contact to serve as the Army’s data correction representatives, and shall be empowered to conduct data correction activities. Upon receipt of a data correction request from an Army contracting location, the support team shall follow all rules and guidelines set forth by the FPDS-NG program office for conducting data correction activities, and shall report all data corrections to ODASA(P) on a monthly basis. Additionally, the support team shall develop a data correction standard operating procedure (SOP) and deliver to ODASA(P).

2.6 General Funds Enterprise Business System (GFEBS) SME Support Primary GFEBs support is currently being provided by the Army Business Center for Acquisition Systems (ABCAS) in accordance with a Functional Support Agreement (FSA) between ABCAS and ODASA(P) and an MOA between GFEBs and ODASA(P). The support contractor shall provide secondary support in the following areas as required to provide depth in interface and business process support, user documentation, as it pertains to SPS integration including:

possible impact on SPS, FPDS-NG, GFEBS, or the Army Contracting Business Intelligence System (ACBIS) for possible impact on each other

Participate in project reviews as requested to provide a summary of actions and issues, to include identification of risks, actions taken and proposed resolution. If the situation dictates, alert ODASA(P) when a risk is identified.

Software release planning, requirements analysis, testing and deployment and implementation support.

GFEBS Interface Testing Support User Documentation and training tips

2.7 Targeted Acquisition Training

One of the ODASA(P)’s strategic initiatives is to use current user support trends to identify areas for workforce skillset improvement and training within the Army contracting community. The goal is to transition knowledge from legacy e-business subject matter experts to mid-level journeyman that shall be leading implementation, deployment and training effort for the future contract writing system, the Army Contract Writing System (ACWS).

The desired results are increased productivity as it relates to contract writing, higher quality contract data, increased productivity and decreased need for functional process and user-error and ad-hoc support. As such, the support contractor shall work with ODASA(P) EBS to develop training programs tailored to Army SPS user community needs.

This task shall include the identification of training courses needed, working with ODASA(P) to prioritize the needs, development of training course material as well as the delivery of training to targeted Army SPS sites. At minimum, these training courses shall be developed to highlight current system functionalities and the business processes associated with their use. Training materials should be derived from use cases from the field that reinforce the recognized best practices promoted by the ODASA(P) and should focus on the importance of data quality and data integrity as it pertains to transactional interfaces (with GFEBS, CEFMS, Wide Area Workflow (WAWF), etc.) and contract reporting systems (FPDS-NG, ACBIS, VCE-BI, , Electronic Document Access (EDA), etc.)

2.8 Service Model Maturation

In order to sustain operational success, the Army requires a comprehensive Service Model – a plan for the efficient delivery and management of shared IT services by improving processes across service providers that support networks, applications, databases and systems. The contractor shall provide recommendations and updates to improve the plan during the year of execution, and incorporate the user transition and communication plans necessary to reduce user transition issues and improve user satisfaction. These plans shall contain but not be limited to a comprehensive list of IT services that are available to the various acquisition professionals, including a description of the service, the agreed upon service levels, how to obtain the service, who is authorized to obtain the service, and escalation procedures in case a service is not adequately being provided.

The plan shall review and make updates to the five-year IT Support Plan that continues to focus on the end-user, the Army contracting professional. The contractor shall propose methods on improving or streamlining the existing ODASA(P) Service Model, to include a focus on Help Desk and Support processes and procedures and refine the existing IT Support Plan to include expanding the Service Desk concept past the "incident, change, and problem management" support to include additional actionable ITIL based processed as necessary.

The contractor shall perform an analysis of these existing services through service provider interviews and end-user surveys and shall collect metrics from existing systems and generate a monthly Metrics Report to ensure adequate resources are aligned properly to accommodate both peak and non-peak service levels.

The contractor shall perform focused trend analysis of service desk tickets from the Army Enterprise Service Desk (AESD) and the JPMO. This analysis shall also take into consideration data from anomaly reports and other available data to improve the services ODASA(P) provides. These services include additional training requirements, improved testing procedures, and refinement of the service model. The contractor shall build a data driven model to identify trends, roots causes of service desk incidents and problems as well as predict rising concerns within the Army Contracting Enterprise who uses SPS, FPDS-NG, and GFEBs through the support of the

AESD.

The IT Support Plan shall be maintained throughout the life of the contract and delivered on a quarterly basis or as required by the Contracting Officer’s Representative (COR.)

The Metrics Report shall be delivered on the 10th of each month or prior business day if the 10th falls on weekend or holiday.

2.9 Transition Plan

The purpose of Transition Plan is to layout the tasks and activities that needs to take place to efficiently transition from the incumbent contractor to a new contractor at the end of this contract.

The Transition Plan shall include an introduction or scope statement addressing background information on the project, show the relationship of the project to other projects and/or organizations or agencies, address maintenance resources required, identify the transition team’s organization and responsibilities, as well as the tools, techniques, and methodologies that are needed to perform an efficient and effective transition.

The Transition Plan shall include deployment schedules, resource estimates, and identification of special resources and staffing, define management controls and reporting procedures, as well as the risks and contingencies. Special attention must be given to minimizing operational risks as well, the contractor shall produce an impact statement outlining the potential impact of the transition to the existing operations and support staff and to the user community. The duration of the transition-in period shall be 30 calendar days.

A Transition Plan for the end of the performance period shall be delivered 60 calendar days prior to the end of the period of performance for Government approval. After the transition plan is approved the contractor shall implement plan to ensure a smooth transition to the new contractor. The duration of the transition-out period shall be 30 calendar days.

The contractor shall submit a Transition Plan detailing the status of the tasks included in the PWS. The report shall be delivered 60 days prior to the performance period end date.

3.0 Required Knowledge and Expertise

Successful engagement and execution requires knowledge and expertise in several areas including:

Relevant history of the ODASA(P) Enterprise Business Systems Directorate and the support teams and field organizations for which they are responsible

The impacts of Federal procurement policy on business systems o Understanding of relevant regulations, including the Federal Acquisition Regulation (FAR), DoD

Federal Acquisition Supplement (DFARS), and Army Federal Acquisition Regulation Supplement

(AFARS)

The implementation and support lifecycle of the Standard Procurement System (SPS), particularly it is deployed within the Army o In-depth knowledge of the SPS program including functional and technical architecture, system administration, and training methodologies o Capability to diagnose, troubleshoot and resolve issues across a wide spectrum of technologies including, but not limited to: PD², PD² Adapter, Sybase ASE, PowerBuilder, webMethods Integration Server, Citrix XenApp, Citrix Provisioning Server, VMware, MS SQL Server, MS Windows Server, and Sun Solaris

The use of information technology, human capital, organizational change management and communication strategy to plan and execute Army programs

Dedicated resource familiar with ITIL framework and its application to the Army Enterprise Service Desk

(AESD)

Dedicated functional and technical, flexible support resources that are spread across SPS, FPDS-NG, GFEBs integration as resource needs across these program areas fluctuate.

Dedicated communications specialist with organization change management, training, and effective knowledge management skills that can be leveraged across all the knowledge management and content development needs.

Resources expected to participate in the technical administration of the Government system shall be required to meet the certification requirements in AR 25-1 and AR 25-2. These regulations require personnel with elevated privileges of a government system or network to possess the Security+ certification AND a secondary certification in a relevant technology field (such as the GSLC, GISF, CAP, TIA Net+, A+, Network+, or SSCP certifications).

The contractor is required to have an in-depth knowledge of the SPS program. This requirement includes the overall implementation and support lifecycle of the system, as well as functional and technical architecture, system administration, and trainer expertise for the Procurement Desktop – Defense (PD²) software. The contractor supporting this effort requires resources capable of diagnosing, troubleshooting and resolving issues across a wide spectrum of technologies including, but not limited to: PD², PRweb, PD² Adapter, Sybase ASE, PowerBuilder, webMethods Integration Server, Citrix XenApp, Citrix Provisioning Server, VMware, Microsoft SQL Server, Microsoft Windows Server, and Sun Solaris. In addition, the administration team is expected to run reports as needed using ACBIS, the FPDS-NG site, the EDA site, or other Army or DoD Business Intelligence systems.

Certification Requirements Each member of the proposed technical administration team shall be required to meet the certification requirements in AR 25-1 and AR 25-2 and DoD Directive 8570.1M. These regulations require personnel with elevated privileges of a government system or network to possess the Security+ certification AND a secondary certification in a relevant technology field (such as the GSLC, GISF, CAP, TIA Net+, A+, Network+, or SSCP certifications). In addition team members must meet the minimum security clearance or investigation requirements of the Army. The Contractor shall ensure that personnel accessing information systems have the proper and current information assurance certification to perform information assurance functions in accordance with DoD 8570.01-M, Information Assurance Workforce Improvement Program. The Contractor shall meet the applicable information assurance certification requirements, including: 1) DoD-approved information assurance workforce certifications appropriate for each category and level as listed in the current version of DoD 8570.01-M, 2) Appropriate operating system certification for information assurance technical positions as required by DoD 8570.01-M. Upon request by the Government, the Contractor shall provide documentation supporting the information assurance certification status of personnel performing information assurance functions. Contractor personnel who do not have proper and current certifications shall be denied access to DoD information systems for the purpose of performing information assurance functions.

4.0 Administrative

4.1 Place of Performance / Period of Performance: The place of performance is contractor facility. The period of performance is listed in the contract.

4.2 Quality Assurance: The Government will evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan. This plan is primarily focused on what the Government must do to ensure the contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

4.3 Quality Control: The contractor shall develop and maintain an effective Quality Control Program (QCP) to ensure services are performed in accordance with this PWS. The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The contractor’s Quality Control Program is the means by which he assures himself that his work complies with the requirement of the contract. The Initial QCP shall be delivered with the contractor’s proposal. Three copies of a comprehensive written QCP shall be submitted to the KO and COR within 10 working days when changes are made after contract award.