SP470116R0042_RFP_Windows_Spt.pdf

7. ISSUED BY CODE

DLA / DCSO-P

700 Robbins Avenue See Block 7 Philadelphia, PA 19111

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

SOLICITATION

9. Sealed offers in original and (See Page 2) copies for furnishings the supplies or services in the Schedule will be received at the place specified in item 8, or if hand carried, in the depository located in See Page 2 until 2:00 PM local time June 28, 2016

(Hour) (Date) 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 conditions contained in this solicitation.

11. TABLE OF CONTENTS

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

PART I - THE SCHEDULE PART II - CONTRACT CLAUSES

x A SOLICITATION/CONTRACT FORM 1-7 x I CONTRACT CLAUSES 56-118 x B SUPPLIES OR SERVICES AND PRICES/COSTS 8-9 PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACH.

x C DESCRIPTION/SPECS./WORK STATEMENT 10-43 x J LIST OF ATTACHMENTS N/A x D PACKAGING AND MARKING 44 PART IV - REPRESENTATIONS AND INSTRUCTIONS x E INSPECTION AND ACCEPTANCE 45 x

K REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

x F DELIVERIES OR PERFORMANCE 46-47 x G CONTRACT ADMINISTRATION DATA 48-54 x L INSTRS., CONDS., AND NOTICES TO OFFERORS 120-125 x H SPECIAL CONTRACT REQUIREMENTS 55 x M EVALUATION FACTORS FOR AWARD 126-129

OFFER (Must be fully completed by offeror)

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

12. In compliance with the above, the undersigned agrees, if this offer is accepted within 120 calendar days (60 calendar days unless a different 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 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)

10 CALENDAR DAYS (%) 20 CALENDAR DAYS (%) 30 CALENDAR DAYS (%) CALENDAR DAYS(%)

14. ACKNOWLEDGMENT OF AMENDMENTS

(The offeror acknowledges receipt of amendments to the SOLICITATION for offerors and related documents numbered and dated):

AMENDMENT NO. DATE AMENDMENT NO. DATE

15A. NAME AND

ADDRESS

OF OFFER-

OR

CODE FACILITY 16. NAME AND THE TITLE OF PERSON AUTHORIZED TO SIGN OFFER

(Type or print)

15B. TELEPHONE NUMBER 15C. CHECK IF REMITTANCE ADDRESS IS

DIFFERENT FROM ABOVE - ENTER SUCH

ADDRESS IN SCHEDULE.

17. SIGNATURE 18. OFFER DATE

AREA CODE NUMBER EXT.

AWARD (To be completed by Government)

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

22. AUTHORITY FOR USING OTHER THAN FULL OPEN COMPETITION:

10 U.S.C. 2304 (c) 41 U.S.C. 253 (c)

23. SUBMIT INVOICES TO ADDRESS SHOWN IN

(4 copies unless otherwise specified)

ITEM

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

26. NAME OF CONTRACTING OFFICER (Type or print)

Maureen Gushue

27. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

28. AWARD DATE

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

AUTHORIZED FOR LOCAL REPRODUCTION

Previous edition is unusable

STANDARD FORM 33 (REV,. 9-97)

Prescribed by GSA - Far (48 CFR) 53.214 (c)

SOLICITATION, OFFER AND AWARD 1. THIS CONTRACT IS A RATED ORDER

UNDER DPAS (15 CFR 7900)

RATING PAGE OF PAGES

1 131

2. CONTRACT NUMBER 3. SOLICITATION NUMBER

SP4701-16-R-0042

4. TYPE OF SOLICITATION

SEALED BID (IFB)

XX NEGOTIATED (RFP)

5. DATE ISSUED

6. REQUISITION/PURCHASE NUMBER

62889405

SP4701 8. ADDRESS OFFER TO (If other than item 7)

10. FOR

INFORMATION

CALL:

A. NAME

Ellen Lester

B. TELEPHONE (NO COLLECT CALLS) C. E-MAIL ADDRESS

Ellen.Lester@dla.mil

AREA CODE

NUMBER

737-5875

EXT.

SP4701-16-R-0042 Page 2 of 131

Continuation of SF33

A.1 Proposals shall be submitted via email directly to the attention of Ellen Lester, the Contracting Officer at Ellen.Lester@dla.mil.

Subject Line of Email Response shall include the RFP # SP4701-16-R-0042

Closing Date and Time: Tuesday, June 28, 2016 at 2:00 PM Eastern Standard Time

Late Proposals will be handled in accordance with FAR 15.208 and 52.212-1.

A.2 CAUTION - CONTRACTOR CODE OF BUSINESS ETHICS (DEC 2010)

FAR Part 3.1002(a) requires all government contractors to conduct themselves with the highest degree of integrity and honesty. Contractors should have a written code of business ethics and conduct. To promote compliance with such code of business ethics and conduct, contractors should have an employee business ethics and compliance training program that facilitates timely discovery and disclosure of improper conduct in connection with government contracts and ensures corrective measures are promptly instituted and carried out. A contractor may be suspended and/or debarred for knowing failure by a principal to timely disclose to the government, in connection with the award, performance, or closeout of a government contract performed by the contractor or a subcontract awarded there under, credible evidence of a violation of federal criminal law involving fraud, conflict of interest, bribery, or gratuity violations found in title 18 of the United States Code or a violation of the False Claims Act (31 U.S.C. 3729-3733).

The solicitation or contract includes FAR Clause 52.203-13, Contractor Code of Business Ethics and Conduct contained elsewhere in the solicitation. The contractor shall comply with the terms of the clause and have a written code of business ethics and conduct; exercise due diligence to prevent and detect criminal conduct, promote ethical conduct and a commitment to compliance with the law within their organization; and timely report any violations of Federal criminal law involving fraud, conflict of interest, bribery or gratuity violations found in Title 18 of the United States Code or any violation of the False Claims Act (31 U.S.C 3729-3733).

A.3 LOW PRICE TECHNICALLY ACCEPTABLE (LPTA) SINGLE AWARD

It is the Government’s intention to award a single firm fixed price contract using competitive 8(a) procedures for this requirement. The award will be based on a Lowest Price Technically Acceptable (LPTA) proposal. The offeror is responsible for providing adequate documentation to enable a thorough evaluation of the proposal. The offeror shall submit a proposal that clearly and concisely describes and defines the offeror’s response to the requirements contained in the RFP. North American Industry Classification System (NAICS) code and related small business size standards are 541513 and $27.5M respectively.

The Government will review the proposal for technical acceptability at a fair and reasonable price. The price may not result in a cost which exceeds a fair market price. The Government will review the mailto:Ellen.Lester@dla.mil

SP4701-16-R-0042 Page 3 of 131 proposals to ensure that the proposals meet the requirements set forth in the Performance Work Statement

(PWS).

A.4 GOVERNMENT RIGHTS

The Government reserves the following rights:

A.4.1 Award without Discussion

The Government reserves the right to evaluate the proposal and make an award without discussions, therefore proposals should contain the offeror’s best terms. Additionally, the Government reserves the right to conduct discussions and request proposal revisions if it is determined to be necessary.

A.4.2 No Award

The Government reserves the right not to make an award as a result of this RFP if such award is determined contrary to the best interest of the Government.

A.4.3 Proposal Preparation Cost

The Government shall not be responsible or liable for any costs incurred by any parties in the preparation and submission of any proposal in response to this RFP.

A.5 CONTRACTING OFFICER

Contracting Officer Ellen Lester DLA Contracting Services Office Philadelphia 700 Robbins Avenue Philadelphia, PA 19111 Phone #: (215) 737-5875 Fax # : (215) 737-7942 Email: Ellen.Lester@dla.mil

A.6 CONTRACT TYPE

The Government contemplates awarding a firm fixed price contract for the Labor CLINs and Time and Material for the Travel CLINs and On-Call Technical Support (INFOCON) CLINs.

A.7 CONTRACTING AND/OR TECHNICAL QUESTIONS

Questions in respect to the RFP should be submitted via email to the Contracting Officer listed above in A.5. Any pricing or technical questions or requests for clarifications should be submitted to the Contracting Officer in writing on or before Tuesday, June 14, 2016 by 5:00 PM EST to allow the Government adequate time to provide answers or to consider potential changes to the RFP. Offerors are strongly urged to follow-up the submission of any questions to the Contracting Officer via telephone mailto:Ellen.Lester@dla.mil

SP4701-16-R-0042 Page 4 of 131 and/or email to ensure that questions have been received.

A.8 QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)

Offeror shall submit a QASP for review and approval 10 days after contract award. The QASP shall address the deliverables outlined in the PWS. Instructions for the requirements of the QASP can be found in the Federal Acquisition Regulation Part 46.4. This plan shall describe the Contractor’s methodology for compliance with the Deliverables and Performance Requirements contained in the PWS. The Government will notify the contractor of any required revisions to the QASP. The contractor shall make the appropriate revisions to the QASP within 5 business days and provide the revised QASP to the Government for review and approval.

A.9 PERFORMANCE MEASUREMENTS.

For specific tasks identified in C.3.3, the agreed to completion date will be based on the estimates provided by the Contracting Officer Technical Representative (COTR). Progress will be tracked based on the milestone event of contractor receiving tasking from the COTR. Performance evaluation will be based on the complexity and completion of the tasking. The number of completed actions will be balanced against the quality of this output. All contractor produced documentation and procedures will comply with all major regulatory and process requirements and agency policies and procedures. Receipt and completion of tasks are tracked through email between the COTR and the contractor team lead.

The tasks the contractor shall perform are defined in Section C.3.3. Additional information about the deliverables produced from the identified tasks is listed in Table 1. The standard set for all tasks is 100% Satisfactory Completion, and 100% COTR Inspection is the surveillance method which will be utilized.

This information is detailed in Table 2 under deliverables. The performance measurements for all task will be pursuant to a performance measurement that ties performance goals and acceptable quality levels to an overall monthly Performance Rating of Good, Fair, Poor or Unacceptable. Performance measurement is further defined below.

A.9.1 Inspection and Acceptance Criteria.

Final inspection and acceptance of all work performed, reports and other deliverables will be performed at the place of delivery by the COTR.

A.9.2 Surveillance Schedule.

Specific surveillance schedules for tasks can be found in Table 2.

The surveillance staff has two components:

Contracting Officer: The primary function of the Contracting Officer, with regard to the surveillance activity, is to authorize changes to the PWS. The Contracting Officer is responsible for ensuring the completion of all work in accordance with the PWS, and the QASP provides a means to accomplish this.

The contracting Officer will rely on the COTR to provide information and recommendations.

SP4701-16-R-0042 Page 5 of 131

Contracting Officer’s Technical Representative (COTR): The COTR’s responsibility is to monitor and inspect, report, and make recommendations to the Contracting Officer regarding the quality of contractor work performed or not performed.

A.9.3 Performance Standards and Payments.

The performance will be rated each month by the COTR. These findings will be the basis for the amount paid for that month. The ratings, as described in the table below, will be based on the performance of the contractor on the timeliness and quality of the services provided using the rating scale for each criterion as shown below.

Performance measurement progress will be tracked based on the milestone event of the Contractor receiving tasking from the COTR. Performance evaluation will be based on the complexity and completion of the tasking. The number of completed actions will be balanced against the quality of this output. All contractor produced documentation and procedures will comply with all major regulatory and process requirements and agency policies and procedures. Receipt and completion of tasking is tracked through email between the COTR and the Contractor team lead.

Below are the Performance Standards that will be used in evaluating performance on a monthly basis and in determining the amount of the payment owed to the contractor.

Performance standards and ratings are designed to determine if performance exceeds, meets, or does not meet a given metric and acceptable quality level. The performance will be rated each month by the COTR. These findings will be the basis for the amount paid for that month. Note: The application of these performance ratings or failure of the Government to apply these performance ratings does not waive any of the Government’s rights to damages under this contract. The following overall ratings shall be used:

Good – Performance meets or exceeds contract requirements in terms of timeliness and quality. COTR recommends and the Contracting Officer will make a determination to pay the contract 100% of the invoice amount.

Fair – Performance meets contract requirements with either only minor performance issues or minor timeliness issues. The performance and/or timeliness issues do not adversely impact the mission of the Agency. Performance is satisfactory and has been timely. The COTR recommends and the Contracting Officer will make a determination to pay the contractor 95% of the invoice amount.

Poor – Performance narrowly meets contract requirements by at least one of the following: bordering on unacceptability in terms of quality of performance, bordering on unacceptability in terms of timeliness, or potentially have an adverse impact on the mission of the Agency. The COTR recommends and the Contracting Officer will make a determination to pay the contractor 80% of the invoice amount.

SP4701-16-R-0042 Page 6 of 131

Unacceptable – Performance has been at a less than acceptable level in terms of timeliness or quality.

Possible issues include, but are not limited to: missed milestones, low quality documents requiring multiple reviews and rewrites, significant or serious complaints submitted by the customers, documents that do not comply with acquisition or policy regulations, or one or more cure notices have been issued. Payment will be withheld pending resolution of cure notice(s). Termination for default or cause may result.

The performance will be rated each month by the COTR. These findings will be the basis for the amount paid for that month. The ratings, as described in the table above, will be based on the performance of the contractor on the timeliness and quality of the services provided using the rating scale for each criterion as shown below.

Timeliness Good Meets or exceeds contract requirements in terms of timeliness of delivery.

Fair Minor timeliness issues that do not adversely impact the mission of the Agency.

Poor Timeliness issues that are not minor and/or borders on unacceptability. Adverse impact on the mission of the Agency is possible.

Unacceptable Contractor failed to meet the timeliness requirements.

Possible issues include, but are not limited to; one or more deliverables not submitted on time or missed milestones.

One or more cure notices may have been issued by the Contracting Officer.

Quality Good Meets or exceeds contract requirements in terms of quality of work performed.

Fair Performance meets contract requirements with only minor issues and the issues do not adversely impact the mission of the Agency.

Poor Performance narrowly meets contract requirements and either borders on unacceptability in terms of quality, or adverse impact on the mission of the Agency is possible.

Unacceptable Quality of performance has been at a less than acceptable level. Possible issues include, but are not limited to: low quality documents requiring multiple reviews and rewrites, significant or serious complaints submitted by the customers, documents that did not comply with acquisition or policy regulations or one or more cure notices have been issued by the Contracting Officer.

SP4701-16-R-0042 Page 7 of 131

A. 10 Non-Disclosure Agreement

Contractor personnel working on this effort will be required to sign the non-disclosure agreement found at Attachment 1.

SP4701-16-R-0042 Page 8 of 131

SECTION B

SUPPLIES/ SERVICES

B.1. Provide Enterprise Windows Administration Support Services in accordance with the task outlined in the Performance Work Statement (PWS). The periods of performance listed below are when services are to begin for the designated locations listed on pages 22 and 23 of the

PWS.

Pricing for the Enterprise Windows Administration Support Services will be Firm Fixed Price (FFP) for the Labor CLINs and Time and Material for the Travel CLINs and On-Call Technical Support (INFOCON) CLINs. See Section L of this Request for Proposal (RFP) for Pricing Instructions.

NOTE: As part of the price proposal, Offerors shall identify any/all assumptions that may impact pricing. These assumptions will be taken into consideration in determining the total cost of the Offeror’s proposal.

Base Period of Performance (POP): August 1, 2016 through January 31, 2017

CLIN Description Quantity Unit Unit Price Total 0001 Labor for Windows Support.

POP: 8/1/2016 through 1/31/2017

6 Months $ $

0002 Labor for Windows Support.

POP: 9/12/2016 through 1/31/2017

4.5 Months $ $

0003 Labor for Windows Support

POP: 12/27/2016 through 1/31/2017

1.5 Months $ $

0004 Travel (as required) NTE NTE $2,500.00 $2,500.00 0005 On-Call Technical Support

(INFOCON)

NTE NTE $500.00 $500.00

Option 1 Period of Performance (POP): February 1, 2017 through July 31, 2017

1001 Labor for Windows Support.

POP: 2/1/2016 through 7/31/2017

6 Months $ $

1002 Labor for Windows Support.

POP: 3/20/2017 through 7/31/2017

4.5 Months $ $

1003 Travel (as required) NTE NTE $2,500.00 $2,500.00 1004 On-Call Technical Support

SP4701-16-R-0042 Page 9 of 131

Option 2 Period of Performance (POP): August 1, 2017 through February 28, 2018

2001 Labor for Windows Support.

POP: 8/1/2017 through 2/28/2018

7 Months $ $

2002 Labor for Windows Support.

POP: 10/23/2017 through 2/28/2018

4.5 Months $ $

2003 Labor for Windows Support.

POP: 11/13/2017 through 2/28/2018

3.5 Months $ $

2004 Travel (as required) NTE NTE $2,500.00 $2,500.00 2005 On-Call Technical Support

Total Price including Base period and all Option periods $___________________

SP4701-16-R-0042 Page 10 of 131

SECTION C

PERFORMANCE WORK STATEMENT (PWS)

C.3.1 BACKGROUND. Defense Logistics Agency (DLA) is an agency of the Department of Defense.

DLA Information Operations, Infrastructure Services, Enterprise Infrastructure Services, and Technology Foundation Services are located enterprise wide at multiple DLA locations. Skills and expertise are needed to perform the activities required for Microsoft Windows operating system administration on the required Enterprise Infrastructure Test and Production platforms. The Contractor shall be responsible for the security and system administration of various Windows Server platforms. System administration will be in support of DLA Non-Secure Internet Protocol Router Network (NIPRNET) and Secret Internet Protocol Router Network (SIPRNET) networks. The Contractor shall also provide support to DLA Disaster Recovery (DR) and Continuance of Operation Plans (COOP) on mission critical systems. This includes traveling offsite to practice DR/COOP exercises and for support in a true disaster scenario.

C.3.2 SCOPE. The objective of this statement of work is to support the DLA Information Operations and DLA Transaction Services staff with the required skills to provide system administration for selected Mid- Tier systems. The Contractor shall provide and administer Microsoft Windows Operating System (OS) to ensure effective daily operation and to resolve problems as they arise, which shall be met through performance of tasks listed below in Sections 3.3.1, through 3.3.6. The Contractor shall use personnel qualified in labor categories described in Section 3.5.2.

C.3.2.1 Technical Support. DLA is on the fast track to convert a large percentage of our physical servers into virtual servers to save money on hardware, easier administrative costs, faster recovery and easier DR/COOP solutions. Technical support is provided in the areas of Microsoft Windows or higher operating systems that include Windows 2008, 2008r2, 2012r2, and future versions of all DLA Microsoft Windows Servers. Windows Administrators must be able to create and maintain Windows Server Group Policy’s, File and Print Services, Server Roles and Features, Active Directory Infrastructure, Network Services and Policy’s, File and Storage Solutions, Implement Business Continuity and Disaster Recovery. Also, support software and/or system related changes; identification and resolution of software bugs, research and application changes, updates, and patches; review, analysis and testing of new technologies introduced to the environment; performance monitoring and tuning, and implementation of ‘best practices”.

C.3.2.2 Task Management. Routine tasks are generally identified via Remedy incidents and are responded to with little or no Government coordination. The DLA Information Operations Internal Data Center Windows Branch Chief identifies and/or receives new requirements, coordinates tasks with staff members and reviews and approves completed work.

C.3.2.3 Task Identification. Taskings will be grouped according to one of the following types: Project Management (PM), Work Order (WO), and Incidents (INC). Each group is measured differently.

Independent taskings are coordinated wit the contractor by the Contracting Officer’s Technical Representative (COTR). Depending if the task is a PM, WO, or INC, different time lines will apply for completion.

SP4701-16-R-0042 Page 11 of 131

C.3.3 SPECIFIC TASKS.

The Contractor shall provide resources to perform duties and functions in the management and administration of the DLA information infrastructure. This support will be performed remotely from Columbus, OH; Dayton, OH; and Richmond, VA. Servicing multiple operating locations within DLA (Battle Creek, MI; Richmond, VA; Ft. Belvoir, VA; Hill AFB, UT; Philadelphia, PA; Columbus, OH;

New Cumberland, PA; Tracy, CA; and Dayton, OH), to maintain the DLA Transaction Services and Technology Foundation Services infrastructure and services 24-hours per day, 7-days per week, 365-days per year. All work shall be performed at the government facility and/or at a remote site with prior approval from the COTR. The personnel assigned by the Contractor must contain the skills required to be productive/functional within the first week of the contract and possess the proper clearances as outlined in Section C.3.5.2.1.

This contract requires support in systems administration, systems management, and security; and is further broken down into the following specific tasks and subtasks.

C.3.3.1 Project Management (PM) Tasks. System administration tasks can best be broken down into these groups:

• Security and patch management. The contractor shall provide regular OS and firmware patching and updates based on established patching cycle for the vendor. OS hardening in accordance with Security Technical Implementation Guide (STIG) and DLA Computer Emergency Response Team (DLA CERT) tasks using Security Content Application Protocol (SCAP), Assured Compliance Assessment Solution (ACAS) tools, and Security Readiness Reviews (SRRs). Monitor security alerts and bulletins for the support environment and provide a plan of action with milestones (POAM) to correct any security related issues, identify false positives, or complete Authorizing Official Risk Acceptance (AORA) documentation to accept the risk. Support all DLA audit activities as it relates to Enterprise Infrastructure software, hardware, and applications. These include but are not limited to Blue Team reviews, CCRI, DIACAP and other reviews.

• Disaster Recovery (DR) and Continuity of Operations (COOP). Establish and support DR and COOP. Provide input to the DR/COOP for disaster recovery of mission critical Mid-Tier platforms. Participation in disaster recovery exercises and providing associated documentation will be required. In the event of an actual emergency, the Contractor shall participate in the recovery of any and all Mid-Tier systems impacted by the emergency.

• System performance monitoring. The contractor shall provide monthly system metrics to include CPU and memory utilization, system availability, I/O trends and disk utilization statistics. Provide trending charts as needed to graphically depict useful trends in order to make informed business decisions. Perform system/application diagnostics through the use of Government-provided maintenance tools to ensure availability and to provide a notification vehicle of problems to administrators. Reallocate system resources as necessary, optimize systems performance, and recommend additional components to improve overall performance.

• Documentation. Develop and maintain detailed documentation for Mid-Tier systems to include architecture diagramming and standard operating procedures. Present informal/formal briefings as required to provide project status. Communicate orally and/or in writing to coordinate task/project

SP4701-16-R-0042 Page 12 of 131 completion. Develop project plans, work breakdown structures, risk management plans and status reports for administering, maintaining, and improving existing and new Mid-Tier Support Procedures.

• DLA Enterprise projects. The contractor shall support multiple DLA Enterprise projects that include virtualization, Federal Data Center Consolidation Initiative (FDCCI), milCloud, geographical re-alignment, physical server build projects, and virtual appliance builds, and local data center upgrades.

• Data Center Operations and miscellaneous. Most of these items will be tasks through work orders or incidents, however there are circumstances where it would fall under a PM task. These include:

Power requests, server racking, hardware installation, physical cabling, hardware acquisition (requests for quote, purchase requests), warranty and support contract maintenance (software and hardware), performance tuning, capacity management, server monitoring and event alert response, system tools installation (HBSS, ISS, anti-virus, ArcSight, and other tools), file system management, user ID management, system audit log configuration, firewall rule requests, email management, PKI management via Secure Shell (SSH) keys, virtual appliance integration, and evaluation and integration of new products.

DELIVERABLES that fall into this category may include to the following:

C.3.3.1.1 - Develop project plans, work breakdown structures, risk management plans and status reports for administering, maintaining, and improving existing and new Mid-Tier Support Procedures.

C.3.3.1.2 – Each Contractor resource shall provide a weekly status report on the satus of assisgned tasks to the COTR, to include at a minimum: Number of Remedy tickets received, completed and open; Detailed progress report of security findings, activities and accomplishments during the reporting period, summary of work accomplished during the reporting period and percent complete; Identification of problems, issues or delays and recommendations for resolution, and corrective action taken to correct identified problems;

Planned activities, as well as the status of deliverables, including planned delivery date(s) and actual and/or anticipated delivery date(s); Recommended strategy changes to include lessons learned. For open items, the report must include the expected completion date.

C.3.3.1.3 - Develop and maintain detailed support documentation for associated Mid-Tier Management Solutions.

C.3.3.1.4 - Participate in disaster recovery exercises and provide associated documentation.

C.3.3.1.5 - Present informal/formal briefings as required to provide project status. Communicate orally and/or in writing to coordinate task/project completion.

C.3.3.1.6- Create and maintain quality and assurance plans. Update as required.

C.3.3.2 Work Order Tasks. The Contractor shall provide system administration support for selected Mid-Tier platforms by performing the following:

SP4701-16-R-0042 Page 13 of 131

• The Contractor shall evaluate requests and provide comments for new Mid-Tier hardware or upgrades to existing Mid-Tier hardware. Comments shall be provided to the initiator of the request in the form of an e-mail or verbal request from the COTR.

• Assist Database Administrators (DBA) interactively on installing and upgrading Windows and Oracle software. Configure systems to meet requirements of DCCBA Group.

• Recommend system configurations for possible purchases. Recommend hardware improvements when appropriate. Provide capacity planning on the Mid-Tier platforms. Provide Information Operations with information on sizing and solving new requirements for Mid-Tier software and hardware. Provide requirements for future needs to the Mid-Tier platforms to support applications.

• Metrics for tracking and reporting capacity shall include Central Processing Unit (CPU), memory, and disk space utilization as well as the availability of each. Existing, averaged, and peeked views must be provided with projections of when capacity may be impacted.

• Document and provide input to each application Program Manager concerning performance tuning and optimization issues on the production and testing Mid-Tier hardware and peripherals.

• Develop and maintain the Component Report, which consists of a listing of all components making up each hardware system to include size of machines, peripherals, operating system versions, application software, communications connections, and any other information requested by Information Operations. Interface with personnel performing program management, Configuration Management (CM), the COTR, and Information Operations in developing this information.

• The Contractor shall evaluate functional requirements to ensure appropriate direction to program managers and developers. Response shall be in the form of e-mail to the application Program Manager and COTR. Ensure proper communications connections within the Mid-Tier hardware to include Wide Area Network (WAN), Local Area Network (LAN), and Fiber Channel connections.

• The Contractor shall support Information Operations to provide connectivity to the Mid-Tier platforms and testing of the connections.

• Plan, schedule and participate in the installation of system software upgrades and/or patches.

Hardware installation plan and schedule must be provided to the COTR prior to installation for discussion, coordination, and adoption. Installations will only be done upon COTR approval. The Contractor shall coordinate all system software installations on Mid-Tier platforms with Functional users, Database administrators and the COTR. Upon completion of installation, the Component report must be updated to reflect the upgrade/patch.

• Upon request, the Contractor shall attend walk through and any required meetings concerning application changes and new development. Issues, concerns, and/or recommendations shall be documented and provided to COTR.

DELIVERABLES that fall into this category may include the following:

C.3.3.2.1 - Recommend system configurations for possible purchases. Recommend hardware improvements when appropriate. Provide capacity planning on the Mid-Tier platforms. Provide Information Operations with information on sizing and solving new requirements for Mid-Tier software and hardware. Provide requirements for future needs to the Mid-Tier platforms to support applications.

C.3.3.2.2 – Provide Metrics for tracking and reporting capacity which shall include CPU, memory, and disk space utilization as well as the availability of each. Existing, averaged, and peeked views must be provided with projections of when capacity may be impacted.

SP4701-16-R-0042 Page 14 of 131

C.3.3.2.3- Document and provide input to each application Program Manager concerning performance tuning and optimization issues on the production and testing Mid-Tier hardware and peripherals.

C.3.3.2.4 - Develop and maintain the Component Report, which consists of a listing of all components making up each hardware system to include size of machines, peripherals, operating system versions, application software, communications connections, and any other information requested by Information Operations. Interface with personnel performing program management, CM, the COTR, and Information Operations in developing this information

C.3.3.2.5 - Evaluate functional requirements to ensure appropriate direction to program managers and developers. Response shall be in the form of e-mail to the application Program Manager and COTR.

Ensure proper communications connections within the Mid-Tier hardware to include WAN, LAN, and Fiber Channel connections.

C.3.3.3 Incident Tasks. The Contractor shall provide support to:

• Monitor the TFS Windows Admin group located in ITSM Remedy.

• Monitor Mid-tier OS software/hardware availability and performance.

• Develop tests and procedures to regularly assess the health of Mid-tier Systems and take corrective measures where appropriate.

• Provide 24x7 on-call support for production MAC 1 systems (may require carrying on-call phone).

• Respond to problem reports, research problems, determine cause, and recommend or initiate corrective action.

• Identify and resolve OS software/hardware application bugs.

• The Contractor shall contact hardware and /or software manufacturers per the terms of its licensing and maintenance agreement with said manufacturer to resolve system problems, if necessary. All actions in response to problem reports shall be documented and routed back for closure.

DELIVERABLES that fall into this category may include the following:

C.3.3.3.1 - Monitor Mid-Tier OS software/hardware availability and performance. Develop tests and procedures to regularly assess the health of Mid-tier Systems and take corrective measures where appropriate.

C.3.3.4 Documentation and Conducting Training. On-the-job training and/or formal training and documentation as required for DLA employees and other configurators as it relates to Information Assurance, existing technologies, or new technologies, including training for DLA Information Assurance Team members to understand and support modification. Formal training, if required, would be conducted in a classroom environment. This may also include, at the discretion of the COTR, peer reviews.

C.3.3.5 Monthly Status Reports. Provide monthly status reports on the status of assigned tasks to the COTR AND COR, to include at a minimum: Number of automated ticketing system tickets received, completed and open; Detailed progress report of security findings, activities and accomplishments during the reporting period, summary of work accomplished during the reporting period and percent complete;

Identification of problems, issues or delays and recommendations for resolution, and corrective action

SP4701-16-R-0042 Page 15 of 131 taken to correct identified problems; Planned activities, as well as the status of deliverables, including planned delivery date(s) and actual and/or anticipated delivery date(s); Recommended strategy changes to include lessons learned. For open items, the report must include the expected completion date.

C.3.4 FORMAT FOR SUBMISSION AND APPROVAL OF DELIVERABLES AND

PERFORMANCE REQUIREMENTS.

In fulfillment of this effort, the contractor shall provide the deliverables identified in this section. All deliverables shall be submitted to the Contracting Officer’s Technical Representative (COTR) unless otherwise agreed upon. In addition, monthly status reports will be provided to the COTR and Contracting Officer’s Representative (COR).

The Government will review the draft deliverables, provide comments back to the contractor and approve or disapprove the deliverables. The contractor will have a maximum of ten (10) working days from the day comments are received to incorporate all changes and submit the final deliverable to the Government.

All days identified below are intended to be workdays unless otherwise specified.

The format for the individual deliverables will be determined through consultation between the COTR and the contractor. Products that reflect the contractor’s analysis and opinion (e.g. studies or analyses) may be in contractor format. All documents will be provided in either hard copy or electronically as requested by the COTR. Electronic documents will be provided in the appropriate Microsoft Office format (e.g. Word or PowerPoint). If appropriate, the Government may ask that they be provided in compressed or PDF format.

C.3.4.1 Deliverables & Performance Requirement Summary Tables.

TABLE 1: DELIVERABLES

Table 1 identifies Deliverables associated with Section 3.3 – Specific Tasks.

PWS

Para #

Task Deliverable Reference # and Title Quantity;

No. of Report

Deliverable Due Date

C.3.3.1 Project Management

C.3.3.1.1 - Develop project plans, work breakdown structures, risk management plans and status reports for administering, maintaining, and improving existing and new Mid-Tier Support Procedures.

not less than 1 per month

As indicated by COTR

C.3.3.1 Project Management

C.3.3.1.2 - Provide monthly status reports on the status of assigned tasks to the COTR, to include at a minimum: Number of Remedy tickets received, completed and open;

Detailed progress report of security findings, activities and

Monthly:

12 reports

Monthly is first Tuesday of every Month

SP4701-16-R-0042 Page 16 of 131 accomplishments during the reporting period, summary of work accomplished during the reporting period and percent complete;

Identification of problems, issues or delays and recommendations for resolution, and corrective action taken to correct identified problems;

Planned activities, as well as the status of deliverables, including planned delivery date(s) and actual and/or anticipated delivery date(s);

Recommended strategy changes to include lessons learned. For open items, the report must include the expected completion date

C.3.3.1 Project Management

C.3.3.1.3 - Develop and maintain detailed support documentation for associated Mid-Tier Management Solutions.

not less than 1 per month

As indicated by COTR

C.3.3.1 Project Management

C.3.3.1.4 - Participate in disaster recovery exercises and associated documentation.

Approx. 2 exercises per year

As indicated by COTR

C.3.3.1 Project Management

C.3.3.1.5– Present informal/formal briefings as required to provide project status. Communicate orally and/or in writing to coordinate task/project completion.

approx. 1 per month

As indicated by COTR

C.3.3.1 Project Management

C.3.3.1.6- Create and maintain quality and assurance plans. Update as required.

1 per year As indicated by COTR

C.3.3.2 Work Order C.3.3.2.1 – Recommend system configurations for possible purchases. Recommend hardware improvements when appropriate.

Provide capacity planning on the Mid-Tier platforms. Provide Information Operations with information on sizing and solving new requirements for Mid-Tier software and hardware. Provide requirements for future needs to the Mid-Tier platforms to support applications.

Approximately 20 per year

As indicated on the WO Remedy Ticket

SP4701-16-R-0042 Page 17 of 131

C.3.3.2 Work Order C.3.3.2.2 – Provide metrics for tracking and reporting capacity shall include CPU, memory, and disk space utilization as well as the availability of each. Existing, averaged, and peeked views must be provided with projections of when capacity may be impacted.

Not less than 1 per month

As indicated on the WO Remedy Ticket

C.3.3.2 Work Order C.3.3.2.3 – Document and provide input to each application Program Manager concerning performance tuning and optimization issues on the production and testing Mid-Tier hardware and peripherals.

Not less than 1 per month

As indicated on the WO Remedy Ticket

C.3.3.2 Work Order C.3.3.2.4 – Develop and maintain the Component Report, which consists of a listing of all components making up each hardware system to include size of machines, peripherals, operating system versions, application software, communications connections, and any other information requested by Information Operations. Interface with personnel performing program management, Configuration Management (CM), the COTR, and Information Operations in developing this information.

Approximately 10 per year

As indicated on the WO Remedy Ticket

C.3.3.2 Work Order C.3.3.2.5 - Evaluate functional requirements to ensure appropriate direction to program managers and developers. Response shall be in the form of e-mail to the application Program Manager and COTR.

Ensure proper communications connections within the Mid-Tier hardware to include WAN, LAN, and Fiber Channel connections.

Not less than 1 per month

As indicated on the WO Remedy Ticket

C.3.3.3 Incident C.3.3.3.1 - Monitor Mid-tier OS software/hardware availability and performance. Develop tests and procedures to regularly assess the health of Mid-tier Systems and take

Approximately 5 per year

As indicated on the INC Remedy Ticket

SP4701-16-R-0042 Page 18 of 131 corrective measures where appropriate.

C.3.3.4 Documentation and Conducting Training

C.3.3.4 Documentation and Conducting Training

As required As required

C.3.7 Transition and Turn Over Procedures

C.3.7 Transition and Turn Over Procedures

1 90 days after contract award.

C.3.3.5 Monthly Status Reports

C.3.3.5 Monthly Status Reports 12; Monthly Due Tuesday of the following week

A.8 Quality Assurance Surveillance Plan (QASP)

A.8 Quality Assurance Surveillance Plan (QASP)

Initial, As required

Within 10 days of contract award

C.3.8 GFP Inventory Listing

C.3.8 Government Furnished Property (GFP) Inventory Listing

Initial, As required

Within 15 days of contract start date

C.3.10 Final Results Briefing

C.3.10 Final Results Briefing 1 10 days prior to final contract expiration

C.3.11 Quarterly Report

C.3.11 Quarterly Report Quarterly Quarterly

TABLE 2: PERFORMANCE REQUIREMENTS

Table 2 identifies the performance requirements resulting from the tasks defined in Section 3.3.

PWS

Para #

Task Title Deliverable Reference #, Title and Acceptable Quality Level

Surveillance Methods

Performance Review

C.3.3.1 Project Management

C.3.3.1.1 - Develop project plans, work breakdown structures, risk management plans and status reports for administering, maintaining, and improving existing and new Mid-Tier Support Procedures.

100% COTR

Inspection

Performance Ratings in accordance with Section A.9

C.3.3.1 Project Management

C.3.3.1.2 - Provide monthly status reports on the status of assigned

100% COTR

Inspection

Performance Ratings in

SP4701-16-R-0042 Page 19 of 131 tasks to the COTR, to include at a minimum: Number of Remedy tickets received, completed and open; Detailed progress report of security findings, activities and accomplishments during the reporting period, summary of work accomplished during the reporting period and percent complete;

Identification of problems, issues or delays and recommendations for resolution, and corrective action taken to correct identified problems; Planned activities, as well as the status of deliverables, including planned delivery date(s) and actual and/or anticipated delivery date(s); Recommended strategy changes to include lessons learned. For open items, the report must include the expected completion date.

accordance with Section A.9

C.3.3.1 Project Management

C.3.3.1.3 - Develop and maintain detailed support documentation for associated Mid-Tier Management Solutions.

100% COTR

Inspection

Performance Ratings in accordance with Section A.9

C.3.3.1 Project Management

C.3.3.1.4 - Participate in disaster recovery exercises and associated documentation.

100% COTR

Inspection

Performance Ratings in accordance with Section A.9

C.3.3.1 Project Management

C.3.3.1.5 – Present informal/formal briefings as required to provide project status. Communicate orally and/or in writing to coordinate task/project completion.

100% COTR

Inspection

Performance Ratings in accordance with Section A.9

C.3.3.1 Project Management

C.3.3.1.6- Create and maintain quality and assurance plans.

100% COTR

Inspection

Performance Ratings in accordance with Section A.9

C.3.3.2 Work Order C.3.3.2.1 – Recommend system configurations for possible purchases. Recommend hardware improvements when appropriate.

100%

COTR

Inspection

Performance Ratings in accordance with Section A.9

SP4701-16-R-0042 Page 20 of 131

Provide capacity planning on the Mid-Tier platforms. Provide Information Operations with information on sizing and solving new requirements for Mid-Tier software and hardware. Provide requirements for future needs to the Mid-Tier platforms to support applications.

C.3.3.2 Work Order C.3.3.2.2 – Provide metrics for tracking and reporting capacity shall include CPU, memory, and disk space utilization as well as the availability of each. Existing, averaged, and peeked views must be provided with projections of when capacity may be impacted.

100%

COTR

Inspection

Performance Ratings in accordance with Section A.9

C.3.3.2 Work Order C.3.3.2.3 – Document and provide input to each application Program Manager concerning performance tuning and optimization issues on the production and testing Mid-Tier hardware and peripherals.

100%

COTR

Inspection

Performance Ratings in accordance with Section A.9

C.3.3.2 Work Order C.3.3.2.4 – Develop and maintain the Component Report, which consists of a listing of all components making up each hardware system to include size of machines, peripherals, operating system versions, application software, communications connections, and any other information requested by Information Operations. Interface with personnel performing program management, Configuration Management (CM), the COTR, and Information Operations in developing this information.

100%

COTR

Inspection

Performance Ratings in accordance with Section A.9

C.3.3.2 Work Order C.3.3.2.5 - Evaluate functional requirements to ensure appropriate direction to program managers and developers. Response shall be in the form of e-mail to the application Program Manager and

100%

COTR

Inspection

Performance Ratings in accordance

SP4701-16-R-0042 Page 21 of 131

COTR. Ensure proper communications connections within the Mid-Tier hardware to include WAN, LAN, and Fiber Channel connections.

C.3.3.3 Incident C.3.3.3.1 - Monitor Mid-tier OS software/hardware availability and performance. Develop tests and procedures to regularly assess the health of Mid-tier Systems and take corrective measures where appropriate.

100%

COTR

Inspection

Performance Ratings in accordance with Section A.9

C.3.3.4 Documentation and Conducting Training

C.3.3.4 Documentation and Conducting Training

100%

COTR

Inspection

Performance Ratings in accordance with Section A.9

C.3.7 Transition and Turn Over Procedures

C.3.7 Transition and Turn Over Procedures Transition Plan and Turn Over Procedures

100%

COTR

Inspection

Performance Ratings in accordance with Section A.9

C.3.3.5 Monthly Status Reports

C.3.3.5 Monthly Status Reports 100%

COTR

Inspection

Performance Ratings in accordance with Section A.9

A.8 Quality Assurance Surveillance Plan (QASP)

A.8 Quality Assurance Surveillance Plan (QASP)

100%

COTR

Inspection

Performance Ratings in accordance with Section A.9

C.3.8 GFP Inventory Listing

C.3.8 Government Furnished Property (GFP) Inventory Listing

100%

COTR

Inspection

Performance Ratings in accordance with Section A.9

C.3.10 Final Results Briefing

C.3.10 Final Results Briefing 100%

COTR

Inspection

Performance Ratings in accordance with Section A.9

C.3.11 Quarterly Review

C.3.11 Quarterly Review 100%

COTR

Inspection

Performance Ratings in accordance

SP4701-16-R-0042 Page 22 of 131

C.3.5 PERSONNEL REQUIREMENTS

The anticipated hours listed for the labor categories are only approximations. Contractors are not restricted to these specific quantities or labor categories in their proposals. It is the Contractor’s responsibility to determine the appropriate labor mix and number of hours to ensure successful performance of the tasks outlined in the PWS.

Base Period (August 1, 2016 – January 31, 2017) (6 Months)

Program Manager (Offsite) – 40-80 Hours 80 Team Lead Systems Administrator (Columbus, OH) 960 Systems Administrator (Onsite Columbus, OH) 2,880 Systems Administrator (Offsite Columbus, OH) 960 Systems Administrator (Onsite Dayton, OH) 1,920 Systems Administrator (Onsite Fort Belvoir, VA) 1,920 Systems Administrator (Offsite Fort Belvoir, VA) 3,840

Base Period (September 12, 2016 – January 31, 2017) (4.5 Months) Systems Administrator (Onsite Richmond, VA) 2,880

Base Period (December 27,2016 – January 31, 2017) (1.5 Months) Systems Administrator (Onsite Dayton, OH) 240

1st Option (February 1, 2017 - July 31, 2017) (6 Months) Program Manager (Offsite) – 40-80 Hours 80

Team Lead Systems Administrator (Columbus, OH) 960 Systems Administrator (Onsite Columbus, OH) 2,880 Systems Administrator (Offsite Columbus, OH) 960 Systems Administrator (Onsite Dayton, OH) 2,880 Systems Administrator (Onsite Fort Belvoir, VA) 1,920 Systems Administrator (Offsite Fort Belvoir, VA) 3,840 Systems Administrator (Onsite Richmond, VA) 3,840

1st Option (March 20, 2017 - July 31, 2017) (4.5 Months) Systems Administrator (Onsite Mechanicsburg, PA) 720

Systems Administrator (Onsite Philadelphia, PA) 720

2nd Option (August 1, 2017 - February 28, 2018) (7 Months) Program Manager (Offsite) – 40-80 Hours 80

Team Lead Systems Administrator (Columbus, OH) 960 Systems Administrator (Onsite Columbus, OH) 2,880