HC104718R4004_Request_for_Proposal_AMD02.docx

DEFENSE INFORMATION SYSTEMS AGENCY

DEFENSE INFORMATION TECHNOLOGY CONTRACTING ORGANIZATION

National Capital Region (NCR), PL63, PO Box 549, Ft. Meade, MD 20755-0549

12 December 2017

HC104718R4004 Advanced Wireless Services-3 (AWS-3) Early Entry Portal (EEP) Development, Operations and Maintenance Support (N4110) Small Business Set Aside

1. This Request for Proposal (RFP) AMD02 is to support the Defense Spectrum Organization’s (DSO) requirement for Advanced Wireless Services-3 (AWS-3) Early Entry Portal (EEP) Development, Operations and Maintenance Support. The Government is issuing a competitive solicitation with a 100% Small Business Set Aside using Fed-Biz Opps entry portal. The Government will conduct this acquisition in accordance with FAR 15.101-2. This requirement may in the future expand, change or be revised due to upgrades to systems as a result of technology evolution, industry standard changes and DoD regulatory requirements.

The specifics are as follows:

HC104716D0008 / Order # HC104717F0082)

2. Offerors are required to submit both a written Technical Proposal and a Cost Proposal (the following are excluded from the page count: List of Figures, List of Tables, Cross-reference Matrix, Resumes, OCCI Analysis, Filled-in FAR Clauses) to Government Officials in response to the attached Performance Work Statement (PWS) (Attachment 1). The initial Quality Assurance Surveillance Plan (QASP) (Attachment 2) is also attached for contractor reference. The Contractor is fully cognizant of the scope of this requirement and has the capability to complete all requirements described in the solicitation. Proposals which merely offer to conduct a program with the requirements for the Government’s scope of work will not be eligible for award. Further information on submission of technical and cost proposals is provided throughout this document.

a) IAW DISA Acquisition Regulation Supplement (DARS) 52.209-9000, each offeror shall specifically identify in its proposal, whether or not any potential or actual Organizational and Consultant Conflicts of Interest (OCCI) as described in Federal Acquisition Regulation (FAR) Subpart 9.5 exists for this instant procurement. If the offeror believes that no OCCI exists, the OCCI response shall set forth sufficient details to support such a position. If an offeror believes that an actual or perceived OCCI does exist on the instant procurement, the offeror shall submit an OCCI plan with the proposal, explaining in detail how the OCCI will be mitigated and/or avoided.

b) A determination has been made by the program office that the items to be purchased under this RFP are subject to Supply Chain Risk Management (SCRM) controls as outlined on Attachment 4. As a result, offerors will be required to submit a detailed SCRM plan as part of their technical proposal. Failure to present a SCRM plan with the proposal will deem the proposal ineligible for award and it will be removed from further consideration.

If a SCRM concern arises after contract award, the Government will determine whether a continuation of the contract poses an undue risk to both the common defense and security to this nation. If the Government determines that such a risk exists, the Government reserves the right to accept or reject a proposed mitigation plan by the Contractor (if one or more is presented within a reasonable time) or terminate the contract. Section 508 Accessibility standards do not apply to this requirement.

c) Section 508 Accessibility Standards apply to this requirement.

d) Period of Performance:

The resulting task order period of performance is a base period of 12 months with three (3) option years. Option periods are subject to availability of funds and may be unilaterally exercised by the Government (Dates subject to changes based on award)

Base Period: 31 Dec 2017 – 30 Dec 2018 Option Period 1: 31 Dec 2018 – 30 Dec 2019 Option Period 2: 31 Dec 2019 – 30 Dec 2020 Option Period 3: 31 Dec 2020 – 30 Dec 2021 6 Month Extension: 31 Dec 2021 – 30 Jun 2022

e) The following administrative requirements apply to the offerors’ proposals in response to the RFP. The technical portion of the proposal shall include information regarding the offeror’s ability to conform to all required terms and conditions in the solicitation. The offerors’ proposals shall address all aspects of the PWS. Page limitations are identified below under each evaluation factor and will be treated as maximums. If exceeded, excess pages will not be read or considered in evaluation of the proposal. The following items will not be considered when calculating page limits: cover page, table of contents, glossary, executive summary, generic resumes, OCCI mitigation plans, and SCRM plans. In the event any evaluation notices are issued, page limitations may also be placed on those. The technical portion of the proposal is to be submitted as a Microsoft (MS) Word 2007 or PDF document. The page format shall have a 1 inch margin using no smaller than an 10 point Ariel, Times New Roman, or Courier New font for all text to include any text contained in a table. The price proposal spreadsheet shall be a separate document from the technical proposal and shall be submitted in MS Excel 2007 format. All formulas shall remain present in the spreadsheet for verification.

The total size of each email (including all attachments) shall not exceed 20MB. Page limitations shall not be circumvented by including inserted text boxes/pop-ups or internet links to additional information; such inclusions are not acceptable and will not be considered part of a proposal. The Government reserves the right not to consider for award any proposal that does not adhere to the administrative requirements of this RFP.

f) The transmittal and cover letter shall include the following:

i. DUNS number and TIN;

ii. Company name and mailing address, and website address;

iii. Date submitted and proposal expiration date;

iv. All of the above cited information for each entity on the proposed team, if a team is proposed;

v. Do you have a Defense Contract Audit Agency (DCAA) or Defense Contract Management Agency (DCMA) Approved Accounting system? If so, provide documentation of approved Accounting system;

vi. Type of Company (i.e., small business, 8(a), woman owned, veteran owned, etc.) as validated via the System for Award Management (SAM). All offerors must register in SAM located at http://www.sam.gov

vii. Company point of Contact, Phone and Email address

3. Evaluation Factors and Basis for Award Determination:

a. Award will be made to the offeror whose proposal is determined to represent the overall best value to the Government using a Lowest Price Technically Acceptable (LPTA) evaluation process. With regard to the best value analysis for the award decision, the evaluation factors and sub-factors identified in paragraph 3c below will be used in the determination of technical acceptability.

b. After receipt of proposals, the Government will first evaluate the lowest price proposal. If the lowest price proposal is determined to be technically acceptable and otherwise properly awardable, award will be made to that offeror. The Government reserves the right to evaluate only the lowest price proposal or to conduct further evaluations of additional proposals.

c. The Government will use the following evaluation factors to determine an offeror’s relative ability to accomplish the tasks set forth in the PWS.

(1) Technical/Management Approach Factor: The Technical/Management Sub- factors will be evaluated and rated either Acceptable or Unacceptable. In order for a proposal to be rated overall Technically Acceptable, each of the following sub-factors must be rated Acceptable. A draft Software Development Plan (SDP) and Task Order Management Plan (TOMP) framework must be submitted alongside the Technical/Management Approach. There is no page limit for the SDP or TOMP. Technical/Management proposals should not exceed 25 pages.

(a) Subfactor 1: Software Development and Maintenance: In order for this subfactor to be rated Acceptable, the offeror must demonstrate an approach that specifically addresses the processes, tools, infrastructure, resources, risks, and dependencies that will be utilized to fully meet or exceed the requirements for EEP Development, Operations, and Maintenance described within Performance Work Statement Tasks 6.3 and 6.4. In addition, offeror must be able to demonstrate expertise in C-Sharp and Java Script SharePoint customizable code.

The offeror must specifically articulate:

Description of agile methodologies used throughout the lifecycle The software development process, from requirements analysis through deployment, demonstrating that new capabilities can be incorporated into EEP, meeting the requirements of PWS Task 6.3.

The operations and maintenance process – ensuring that EEP is never down for more than two (2) consecutive business days and ensuring the system is available 98% of the time, on an annual basis – meeting the requirements of PWS Task 6.4.

Approach for operating a help desk, including maintaining appropriate documentation and logs.

Approach for testing that ensures a high-quality product is delivered/maintained.

Approach for adding Universal Browser Compatibility, 508 Compliance, and Satellite Coordination Agreement Documents capabilities, including technical details, risks, levels of effort, and changes to EEPAC supporting documentation.

A draft Software Development Plan shall be delivered with the proposal and support the offeror’s EEP Development, Operations, and Maintenance approach. In order for this subfactor to be rated as acceptable, this document must demonstrate an approach that satisfies EEP development requirements. The offeror must specifically address:

· Requirements approval, documentation, and traceability

· The complete software development lifecycle

· How testing adequately reveals software deficiencies and ensures that a high- quality product is delivered

(b) Subfactor 2: Transition and Deployment: In order for this subfactor to be rated Acceptable, the offeror must demonstrate an approach that specifically addresses the processes, tools, infrastructure, resources, risks, and dependencies associated with fully meeting or exceeding the requirements for EEP Transition and Deployment, described within Performance Work Statement Task 6.2.1.

The offeror must specifically articulate:

· EEP Transition-in approach that meets the required timelines and requirements in accordance with PWS Task 6.2.1.

a. The offeror’s proposed privately hosted environment(s) and infrastructure, to include the approach to security boundaries.

b. Transition-in timeline (including downtime), dependencies, and risks

c. Testing and verification.

d. Deployment

· EEP Transition-out.

(c) Subfactor 3: Task Management: In order for this subfactor to be rated Acceptable, the offeror must demonstrate an approach that specifically addresses the processes, tools, infrastructure, resources, risks, and dependencies associated with fully meeting or exceeding the requirements for EEP Task Management described within Performance Work Statement Tasks 6.1 and 6.6.

A framework EEP Task Order Management Plan shall be delivered with the proposal and support the offeror’s approach. The offeror must specifically articulate robust:

· Schedule management processes

· Risk management processes

· Approaches to cost control

· Quality control processes

· Incorporation of critical skills

· Incorporation of key personnel management

(d) Subfactor 4: Disaster Mitigation Support: In order for this subfactor to be rated Acceptable, the offeror must demonstrate an approach that specifically addresses the processes, tools, infrastructure, resources, risks, and dependencies associated with fully meeting or exceeding the requirements for EEP Continuity of Operations described within Performance Work Statement Task 6.5.

(e) Past Performance:

The past performance will not be evaluated.

(2) Cost/Price Factor

(a) Cost proposals will be evaluated using one or more of the techniques defined in FAR Part 15.404, contract line item number (CLIN) Pricing Worksheet (Attachment 4) in order to determine if they are reasonable and complete. Cost proposals for cost reimbursable CLINs will be evaluated for realism, pursuant to FAR Part 15.404-1(d), to ensure the Government will not be placed at risk for nonperformance. Cost Plus Fixed Fee (CPFF) CLINs will be evaluated in accordance with FAR 15.404-4 and DFARS 215.404-4. Probable cost will be used for purposes of evaluation, rather than proposed costs, and probable cost will be calculated by adjusting CPFF CLINs based on results of the cost realism analysis.

The offeror shall submit pricing for the base period and all option periods, including option pricing for an additional 6-month period that may be authorized IAW FAR 52.217-8. See FAR 52.217-8 which authorizes the Government to require continued performance of any services within the limits and at the rates specified in the contract. The pricing proposal should include a separate line item for the additional 6-month period IAW FAR 52.217-8. These prices shall be identical to the quoted pricing in the 6 months prior to expiration of the base period, or the final option period, if option periods are present. The total evaluated price will consist of the contractor’s proposed price for the base period, all option periods, the option pricing for the additional 6-month period, and surge pricing as requested below.

(b) The offeror shall describe their methodology used to establish their cost/price. The offeror shall provide information describing and detailing the evaluation it performed to determine the reasonableness of subcontractor costs/prices on hourly labor rates. This analysis shall be provided to the Contracting Officer and may be submitted in accordance with the offeror’s internal accounting procedures; there is no specified format. The Offeror shall provide, or instruct the subcontractor to provide evidence of accounting system adequacy if the subcontractor is performing on any basis other than Firm Fixed Price (FFP) or Time and Materials (T&M).

(c) Cost/Price Narrative. The Prime Contractor and each of its subcontractor(s) shall include in its cost narrative its CAGE Code along with its DCAA and DCMA points of contact name, telephone number, and email address ( Reference FAR appendix 9903.201-1 -- CAS Applicability for exemption to CAS for Small Businesses).

Each Offeror's and subcontractor’s cost proposal shall be broken out by cost element as specified in FAR 15.408, Table 15-2, and in further supporting detail as shown in the Government Provided Pricing Template. The Prime contractor and each subcontractor’s Cost Proposal SHALL be submitted in Excel format (.xlsx) with all formulas visible in each cell with a value. If a subcontractor’s cost data is proprietary, the subcontractor may submit its data directly to the Government in the same format that is required of the Prime contractor.

Offeror and its subcontractor(s) shall provide whatever information is necessary to help the Government understand why the proposed costs are reasonable in its Cost Narrative Document. Offeror shall provide a job description of each of its internal labor categories proposed. Each Offeror's cost proposal shall contain sufficient quantitative and narrative documentation necessary to adequately support and explain the costs proposed, to include subcontractor proposed costs. Offeror shall disclose the type of contract that it will have with each of its subcontractors (FFP, CPFF, etc.). The Offeror and its subcontractor(s) shall disclose the location (Government site per the PWS) of each proposed labor categories in its cost proposal.

Offeror and any subcontractor(s) shall be responsible for ensuring compliance with the Service Contract Act (SCA) for all applicable labor categories. If the offerors believe that labor categories are subject to the SCA, they shall identify such labor categories as “SCA Labor” on their proposal. Offeror shall also disclose the state and county in which the proposed SCA labor categories will be performing its effort, the Wage Determination Schedule used for its proposed SCA labor rates, and the Occupation Code and Title for each proposed SCA labor category.

In support of proposed direct labor and indirect expense rates, Offeror and its subcontractor(s) shall provide documentation to include at least one of the following:

1) a copy of the most recent Forward Pricing Rate Agreement (FPRA), 2) Forward Pricing Rate Recommendation (FPRR), 3) a DCAA or DCMA report or memorandum containing the most recent finalized DCAA/DCMA audit or review, or 4) Forward Pricing Rate Proposal (FPRP) or other statement of current rates to include documentation to validate the proposed direct labor rates and indirect expense rates.

Documentation for the proposed direct labor rates may be recent actual direct labor rates supported by payroll records, and/or paystubs for personnel currently on staff that will be performing on this effort, Letters of Intent (LOIs), or salary survey data. If providing LOIs, Offeror and/or its subcontractor(s) shall include the direct hourly labor rate for the proposed employee, identify the position, submit the LOI on Offeror’s or subcontractor’s letterhead with both the prospective employee’s and the employer signatures, and state that the LOI is for AWS-3 Early Entry Portal Development, Operations and Maintenance Support; tracking number RFP-HC104718R4004, N4110. If providing a salary survey, offerors shall at a minimum, include for each applicable labor category the salary survey information in support of the proposed direct labor rates. The salary survey information at a minimum shall have: the source of data used to develop the salary ranges, the job title and description being surveyed, the geographic location the survey data is valid for, and a range of salary amounts with reference to applicability of amounts.

Documentation of indirect expense rates where an FPRP or other statement of current rates are proposed shall include the proposed expense pool (by expense account) and allocation base detail, along with the last two years actual pool (by expense account), base, and rate information. The rates reflected in the FPRA, FPRR, FPRP, DCAA/DCMA audit or review or other statement of current rates shall directly match the proposed rates as detailed in the proposal. If the rates do not match, Offeror and/or its subcontractor(s) shall provide sufficient detail explaining why the rates are different and how the proposed rates are realistic.

(d) Due to the likely inability of any offeror to accurately estimate travel and material/equipment purchases associated with this requirement, the Government is providing plug numbers to be used by all offerors when proposing ODCs. Offerors are instructed to propose plug numbers for ODCs in the following EXACT amounts, however actual travel shall be authorized by the COR in writing prior to performance and will be paid IAW FAR Part 31.205-46. No profit or fee will be authorized for travel or materials. Applicable burdens, e.g., G&A, may apply to travel IAW the contractor’s accounting practices.

These EXACT amounts shall include all audited markups and burdens and shall not be rounded or adjusted based upon independent decisions regarding actual anticipated ODCs. A proposal that fails to bid the plug numbers EXACTLY as provided may be excluded from further consideration.

(f) The Government may require surge support during the base or any option period and surge modifications will be in-scope to provide increased support for the defined task areas of the PWS. Surge support is OPTIONAL and is not a guarantee. If the Government determines that an increased quantity of support is required for the task areas defined in the PWS, the Government reserves the right to exercise the surge option unilaterally. The contracting officer will provide written notice to the offeror at least 30 calendar days prior to any unilateral exercise of the surge option. The Government is providing a percentage value to be used by all offerors when proposing surge: surge support will not exceed 5% of the offeror’s total proposed cost/price for the base and all option periods, excluding any 6-month extension of services pursuant to FAR 52.217-

8. Offerors are instructed to propose this EXACT percentage for Surge CLIN 9999. In the event the Government does elect to exercise the surge option, surge support will be realigned under new or existing CLINs for the relevant task areas identified in the PWS, and an equal amount will be deducted from optional surge CLIN 9999. The Government will not conduct a cost realism analysis on optional surge CLIN 9999 if all other labor CLINs under the contract/task order are firm-fixed price. Surge support will be provided at the same labor rates proposed and found fair and reasonable at time of contract/task order award for the applicable period of performance. When surge support is realigned under cost-type CLINs, if actual reimbursable labor rates exceed the labor rates originally proposed and found fair and reasonable at time of contract/task order award, the contractor is only entitled to a fee amount based on the originally proposed labor rates.

(g) The past performance evaluation factor will not be evaluated.

(h) The cost/price proposal will be evaluated using one or more of the techniques defined in FAR Part 15.404 in order to determine if they are reasonable and complete. The

Government will determine completeness of the offeror's proposal by verifying that all solicitation requirements have been priced, figures are correctly calculated, and costs are presented in a clear and useful format. The offeror shall submit pricing for the base period and all option periods, including option pricing for an additional 6-month period that may be authorized IAW FAR 52.217-8. See FAR 52.217-8 which authorizes the Government to require continued performance of any services within the limits and at the rates specified in the contract. The pricing proposal should include a separate line item for the additional 6-month period IAW FAR 52.217-8. These prices shall be identical to the proposed pricing in the 6 months prior to expiration of the base period, or the final option period, if option periods are present. The total proposed price will consist of the contractor’s proposed price for the base period, all option periods, and the option pricing for the additional 6-month period.

Ensure the price proposal includes detailed information regarding the resources required to accomplish the task (e.g., labor categories, labor hours, number of employees for each labor category, rates, travel, incidental equipment, etc.). If there will be any subcontractors supporting this opportunity, identify the subcontractor relationship between the prime and subcontractor, and ensure subcontractor(s) provide the following to DITCO:

(1) Unsanitized cost proposal, to include a cost build-up identifying all applicable indirect rates and profit/fee;

(2) Defense Contract Management Agency and Defense Contract Audit Agency (DCAA) cognizant points of contact. ( Reference FAR appendix 9903.201-1 -- CAS Applicability for exemption to CAS for Small Businesses)

(3) Forward Pricing Rate Recommendation (FPRR) and Forward Pricing Rates Proposal (FPRP). If no FPRR/FPRP exists and approved provisional billing rates don't exist, please provide the indirect cost pool/base for each aspect of applicable indirect rates to the Government;

(4) DCAA-approved letter of an approved accounting system (if relationship is a cost- reimbursable basis). ( Reference FAR appendix 9903.201-1 -- CAS Applicability for exemption to CAS for Small Businesses)

(5) The prime contractor or subcontractor shall conduct appropriate cost or price analyses to establish the reasonableness of proposed subcontract prices and include the results of these analyses in the price proposal.

4. The Government intends to evaluate proposals and award a contract without discussions with offerors. However, the Government reserves the right to conduct discussions or seek clarifications if the Contracting Officer (KO) determines they are necessary. In the event issues pertaining to a proposed task cannot be resolved to the KO’s satisfaction, the Government reserves the right to withdraw and cancel the proposed task order. In such an event, offerors will be notified in writing. In the event a competitive range is established and the KO determines that the number of proposals that would otherwise be in the competitive range exceeds the number at which an efficient competition can be conducted, the KO may limit the number of proposals in the competitive range to the greatest number that will permit an efficient competition.

5. Attachment 7 contains provisions that apply to this solicitation and clauses that will be applicable to the resulting award. Some of the provisions require a response from the offeror and will need to be submitted along with your proposal (separate from Technical/Cost Proposal document).

6. In response to this RFP, no terms, conditions, or assumptions will be entertained. If terms, conditions, or assumptions are included in a proposal, the proposal may be excluded on grounds that it failed to comply with the RFP’s instructions.

7. An offeror agrees that if its offer is accepted within 90 calendar days from the date of receipt of proposals (unless a different period is stated in the proposal), it will furnish the items and/or services identified in its proposal at the cost offered to the designated point(s) within the time specified in the contract.

8. Portions of the successful offeror’s proposal may be incorporated into the contract.

9. The Government may incorporate members of The MITRE Corporation, who operate The National Security Engineering Center (NSEC) and Federally Funded Research and Development Center (FFRDC), as an advisor into the source selection team.

10. Proposals are due no later than December 21, 2017 at 2:00pm EST and should be submitted via email to gloria.r.norwood.civ@mail.mil and clark.b.miller.civ@mail.mil.

Digitally signed by NORWOOD.GLORIA.ROCIO.1268785317NORWOOD.GLORIA.

DN: c=US, o=U.S. Government, ou=DoD, ROCIO.1268785317

Gloria Norwood, CONTRACTING OFFICER ou=PKI, ou=DISA, cn=NORWOOD.GLORIA.ROCIO.1268785317 Date: 2017.11.21 13:13:49 -05'00'

Attachment 1, PWS

Attachment 2, Initial QASP

Attachment 3, CLIN Pricing Worksheet

Attachment 4, Supply Chain Risk Management Plan

Attachment 5, Evaluation Table

Attachment 6, Questions and Answers Responses

Attachment 7, FAR, DFARS, DARS Provisions/Clauses

Additional attachments and background material on the requirement is available on FedBizOpps under Solicitation Number HC104718R4004, but is not included here due to file size limitations.

image2.emf

Attachment_1_-_PWS_Rev1.docx

PERFORMANCE WORK STATEMENT (PWS)

as of 18 September

Contract Number:

TBD

RFP Number:

HC104718R4004

Tracking Number:

N4110

Follow-on to Previous Contract and Task Order Number:

HC1047-07-D-0001, TO-1110/ 0951

HC1047-16-D-0008 TO# HC104717F0082

1. Contracting Officer’s Representative (COR).

To Be incorporated into final award clause DARS 52.204-9000, Points of Contact (Aug 2005)

2. Task Order Title.

Advanced Wireless Services- 3 (AWS-3) Early Entry Portal (EEP) Development, Operations, and Maintenance Support

3. Background.

In March 2014, the Federal Communications Commission (FCC), in collaboration with the National Telecommunications and Information Administration (NTIA), developed rules for auction and reallocation of the 1695-1710 MHz and 1755-1780 MHz bands, which at the time, were allocated exclusively for Federal use. On July 18, 2014, the FCC and NTIA issued a joint Public Notice (PN) DA 14-1023, GN Docket #13-185. The PN provided: (i) information for potential bidders in the AWS-3 auction; and (ii) guidance to the ultimate AWS-3 licensees and the affected Federal incumbents regarding coordination between Federal and non-Federal for shared use of the 1695-1710 MHz and 1755-1780 MHz bands. On November 13, 2014, the FCC initiated the AWS-3 Auction (“Auction 97”). Auction 97 provided for new licenses in the 1695-1710 MHz, 1755-1780 MHz, and 2155-2180 MHz bands for AWS-3. Most of the federal systems using the 1755-1780 MHz band will relocate out of the band, but the FCC’s rules provide for indefinite sharing with a limited number of federal systems. The NTIA Commerce Spectrum Management Advisory Committee Working Groups 3, 4, and 5 established protection distances around Federal systems operating in the AWS-3 bands (1695-1710, 1755-1780, and 2155-2180 MHz) to ensure interference-free operation between Department of Defense (DoD) and commercial AWS systems as the AWS systems enter the bands. Initial DoD assessments indicated it would take several years for DoD systems to transition out of the band, and some assets would remain in a sharing arrangement indefinitely. The Services and the Defense Information Systems Agency (DISA) Defense Spectrum Organization (DSO) have developed transition plans for their respective organizations to facilitate increasingly less restrictive sharing arrangements for early entry of commercial AWS systems and permanent sharing between DoD and commercial systems operating in the 1755-1780 MHz band.

The DISA DSO Transition Plan includes six tasks: DISA1: 1755-1780 MHz Early Entry Portal (hereafter referred to as the AWS-3 EEP); DISA2: 1755-1780 MHz Federal Spectrum Management System (FSMS) Portal; DISA3: 1780-1850 MHz Compression and Optimization Tool; DISA4: 2025-2110 MHz Spectrum Management/ Coordination System; DISA5: 1755-1780 MHz Spectrum Sharing Test & Demonstration (SST&D) Program; and DISA6: DoD Spectrum Relocation Management Team (DSRMT). DISA6 covers the DSRMT Government reimbursable billets to be funded through AWS-3 auction proceeds. The DSRMT will oversee DSO activities being conducted under the DISA Transition Plan, including oversight of contracted work.

The AWS-3 EEP is a custom-coded SharePoint .NET web application using the SharePoint data object model. It requires an underlying SharePoint instance and SQL server for storing SharePoint configuration, content, and user/role data. The AWS-3 EEP currently resides within a third-party data center and is accessible via the open internet to authorized users. The Initial Operating Capability (IOC) of the AWS-3 EEP focused primarily on an information exchange mechanism supporting a workflow for processing commercial AWS-3 provider coordination requests (CRs), in accordance with the Joint FCC and NTIA Public Notice on Coordination Procedures in the 1695-1710 MHz and 1755-1780 MHz Bands: July 18, 2014 , with the DoD, Department of Justice (DOJ) and Department of the Interior (DOI). The Full Operating Capability (FOC) of the AWS-3 EEP included automation of the Satellite Operations (SATOPS) Streamlined Coordination process with the DoD, AWS-3 licensee responses to the DoD results letter, and processes associated with AWS-3 licensee’s coordination with DoD after initial results of CR assessments are provided to the AWS-3 licensees (referred to as “Post-60 day Discussions”). The DoD, DOJ, and DOI have analytical capabilities to assess CRs that are manually downloaded from the AWS-3 EEP (there is no machine-to-machine interface between these analytical capabilities and the AWS-3 EEP).

4. Objectives.

The objective of this effort is to provide for continued EEP development, operations and maintenance.

5. Scope.

The Government is in need of transition, deployment, continuing development, operations, maintenance, and enhancement tasks for EEP, as defined in this PWS. The contractor shall provide all corrective maintenance, system user support, software development, system (and software) documentation, system/software operations, and maintenance services required by EEP as outlined in Section 6, titled Performance Requirements.

The Government may require surge support during the base or any option period, and surge modifications will be within the scope of the contract and provide increased support for the defined task areas of this PWS. Surge support over the life of the contract will not exceed 5% of the contractor’s total proposed cost/price for the base and all option periods, excluding any six-month extension of services pursuant to FAR 52.217-8.

6. Performance Requirements.

6.1. Task 1. - Task Order Management (FFP)(O&M). The Contractor shall utilize industry best practices for project management and agile product development to ensure on-time and on-budget delivery of quality, customer driven products. Examples of acceptable best practices include the Project Management Institute’s (PMI) Project Management Body of Knowledge (PMBOK® Guide), IT Information Library (ITIL), SEI Capability Maturity Models (software and integration), and the Scaled Agile Framework (SAFe).

6.1.1. Subtask 1.1. - Task Order Management Planning and Reporting. The contractor shall deliver effective task order management that accounts for technical approach, cost, schedule, performance parameters, and management controls employed to meet the requirements throughout task order execution. The contractor shall develop a Task Order Management Plan (TOMP) that addresses relevant aspects of managing the task order, such as:

· Product Oriented Work Breakdown Structure (WBS), aligned to the scope and deliverables of the TO

· Integrated Master Schedule structured by the Government approved WBS and logically connected with predecessor and successor relationships

· Cost

· Staffing

· Stakeholder Communications

· Risk and Opportunity Management. Approach, Assessment, Mitigation, Integration and Reporting for management and technical risks

· Action Item Tracking

· Task Order Requirements

· Technical Management

· Product Requirements

· Product Design and Development

· Product Development and Testing

· Product Deployment, Engagement and Training

· Product Operations, Support and Maintenance

· Quality Assurance/Quality Control, Configuration Management, Performance Management, Technical Risk Management

The Contractor shall deliver a Monthly Status Report on task order progress that includes recent activities, future activities, the status and progress of costs, schedule and technical performance, risks and issues. The Contractor shall summarize risks and issues in the monthly report. Those that require immediate government attention shall be, at a minimum, discussed during the monthly status meeting or brought to the COR’s attention, as needed.

Deliverable(s):

a) Initial Task Order Management Plan (TOMP) and Updates (addresses management of the following: requirements, schedule, cost, quality control, staffing, communications, risk, and procurement)

b) Monthly Status Report that addresses

· Planned vs Actual Financial Reports

· Invoices and invoice status

· Schedule status

· Attached Integrated and Baselined MS Project.mpp file and Updates

6.1.2. Subtask 1.2. – Task Order Status Meetings and Reports. The contractor shall prepare and conduct a kick off meeting within forty-five (45) days of contract award to establish a common understanding of task order requirements, schedule details and expectations. This kick-off meeting shall fully address the software development process, at a minimum: the implementation of agile development, the requirements approval process, the release roadmap, the use and pace of sprints (including completion criteria), the definition of a minimum shippable increment, and the product backlog review process. The contractor shall present the integrated master schedule and, after Government approval, establish the schedule baseline. The contractor shall prepare kick-off meeting materials and kick-off meeting minutes.

The contractor shall prepare and conduct Monthly Management Status Reviews. At Monthly Management Status Reviews, the Contractor shall prepare and discuss with the Government the status of technical activities, the EEP product backlog, risks, task order financial status of planned versus actuals costs (monthly and cumulative) by Task and by WBS for Cost-Plus Tasks. The Contractor shall also discuss schedule status, issues, get well plans, and any task order related topics (e.g. procurement, security, invoices) that require Government attention. The Monthly Management Status Review will coincide with the submission of the monthly status report. The contractor shall furnish materials to support these discussions, and the contractor shall provide minutes following every Monthly Management Status Review meeting.

The Contractor shall contribute to and/or host a maximum of 6 ad hoc customer and/or external stakeholder meetings per year as directed by the Contracting Officer’s Representative (COR). These meetings will primarily be of a technical nature, such as a deep dive, where EEP experts will provide EEP-centric perspectives and/or helping other stakeholders resolve issues. The contractor shall furnish materials to support these discussions, and the contractor shall provide minutes following any ad hoc meeting.

The contractor shall participate in bi-weekly EEP Working Group meetings, led by a third party. During these meetings, the contractor shall provide EEP development perspectives and support analyses and discussions when relevant topics are discussed. Potential EEP features that are discussed during EEP Working Groups shall be added to the product backlog for DSO consideration. Each meeting is expected to last no more than two hours, and the contractor may support these meetings via virtual means; e.g., by video or teleconference.

For all meetings and reviews, the contractor shall provide facilities capable of hosting meetings and providing demonstrations, when necessary. These facilities shall be within forty (40) linear miles of the DSO Annapolis facility. The contractor shall provide logistical support for these meetings, to include scheduling rooms, enabling remote access to meetings, coordinating dates, inviting participants, developing and distributing agendas, maintaining action item lists, recording and distributing minutes, conducting post meeting follow-up actions, etc. Remote access may include setting up Defense Collaboration Services, teleconference phone bridges, WiFi/guest network access, web conferencing, etc.

Deliverable(s):

a) Kick-off Meeting Materials and Minutes

b) Monthly Management Status Review Agenda, Materials and Minutes

c) Ad Hoc Meeting Agenda, Materials and Minutes

6.1.3. Subtask 1.3. - Project Data and Information Support. The Contractor shall provide, as requested by the COR, relevant working project data and information created in the process of performing work during the period of performance. Such artifacts are considered key for historical purposes, knowledge management, collaboration, and information sharing purposes. Materials created or in existence as a result of task order activities will not cause undue burden on the Contractor to provide or upload to a portal or SharePoint as directed by the COR. These may include (but exclude non-transferable commercial licenses):

· Artifacts and data generated during the software development and update process (e.g., build instructions, software development tool compiler settings and configuration settings, test scripts, and test harnesses). These are working products created by the contractor to perform software development that are outside of the formal deliverables specified in other tasks of this task order.

· Working products created in the execution of the tasks under this task order, at a minimum: information, documents, data, manuals, license information, standard operating procedures, and software.

· Email correspondence

· Presentations, spreadsheets, research, papers created in the process of performing a task or producing a deliverable

During the closeout process and within sixty (60) calendar days prior to the final day the period of performance, the Contractor shall produce a draft list of TO closeout items that shall be turned over/transferred to the Government. The list shall include, but not be limited to, the following: all required incumbent equipment inventory (GFE only); TO deliverables; and all required software (e.g., the TDP, a virtual machine of the production EEP, EEP production database snapshot, configuration settings, portal case information including status, data, etc.). The Contractor shall review the draft list with the Government and provide an update, if needed.

The Contractor shall deliver TO closeout items to the Government on a date agreed upon by both parties within 30 calendar days of the final day of performance.

Deliverables shall be provided in their native formats using a delivery mechanism agreed to by the COR.

Deliverable(s):

a) Project Data and Information

b) TO Closeout Items List (Draft and Final)

c) Delivery of TO Closeout Items

6.1.4. Subtask 1.4. – Handling of Non-Public Information. In performance of this contract, the contractor and its employees may have access to DoD information and Contract Sensitive/Proprietary information of the AWS-3 Licensee companies. The contractor agrees to:

A. Use and protect such information from unauthorized disclosure in accordance with (IAW) DoD Instruction 8582.01, Security of Unclassified DoD Information on Non-DoD Information Systems.

B. Use and disclose such information only for the purpose of performing this contract and to not use or disclose such information for any personal or other commercial purpose.

C. Comply with other current Federal and DoD information protection and reporting requirements for specified categories of information (e.g., medical, proprietary, critical program information (CPI), personally identifiable information (PII), or export controlled information).

D. Obtain permission of the Government Requiring Activity before disclosing/discussing such information with a third party.

E. Return and/or electronically purge, upon Government request, any DoD or AWS-3 Licensee company information no longer required for contractor performance.

F. Advise the Contracting Officer and/or Contracting Officer’s Representatives of any unauthorized release of such information.

All contractor staff and staff with access to information submitted by AWS-3 Licensees shall execute an AWS-3 non-disclosure agreement (NDA) within five (5) days of award and/or prior to accessing such information. The Government will provide an NDA template as Government Furnished Equipment/Information (GFE/I).

Deliverables:

a) AWS-3 NDAs

6.2. Task 2. – EEP Transition and Deployment.

6.2.1. Subtask 2.1. – Initial EEP Transition and Deployment (BASE PERIOD OF PERFORMANCE ONLY)(FFP)(RDT&E). The contractor shall transition the EEP from a privately hosted, legacy environment to an approved privately hosted environment located at the contractor’s facility. The contractor shall coordinate all transition/deployment activities with the DSO and the legacy environment owner throughout the transition of the EEP. The contractor shall ensure successful operational status following deployment to the new environment.

The contractor shall provide all infrastructure, hardware and any other product or service required to successfully transition the EEP.

The contractor shall develop an EEP Transition and Deployment Plan (ETDP) for migrating the existing EEP infrastructure from the current environment to a privately hosted environment provided by the contractor. The contractor shall provide a first draft of the ETDP fifteen (15) business days after contract award. Upon receipt of any DSO feedback, the contractor shall have ten (10) business days to provide an updated plan based on comments provided by the Government. The contractor shall conduct a formal review of the ETDP and associated test plans as part of the contract kick-off meeting, in accordance with Subtask 1.2.

The ETDP shall include the following:

A. A schedule of transition and deployment activities, milestones, and timelines, including identification of the critical path.

B. Identification of dependencies for transition and deployment, including dependencies on the DSO and incumbent vendor.

C. Identification of transition and deployment risks and opportunities, with appropriate mitigation and handling plans.

D. Identification of the responsible organization and a clear delineation of responsibilities for each activity required for successful transition and deployment including:

a. Physical transfer of EEP and associated artifacts.

b. Security control responsibilities.

E. Transition and deployment cost estimates, cost breakdowns, and cost information.

F. EEP deployment plan, including the complete processes for:

a. Hardware procurement.

b. Software Deployment.

c. Maintaining security boundaries, including a virtual private cloud or required logical network zones, as appropriate.

G. Checklist of activities, associated artifacts, and identification of organizations responsible for each activity to execute transition and deployment.

H. Full details of the privately hosted environment.

I. Identification of EEP artifacts that require updating as a result of the transition and deployment.

J. Overarching test strategy and associated test plan(s) for the EEP Deployment, including an operational checkout that verifies full EEP functionality.

K. Specific items to be addressed during the Operational Readiness Review (ORR).

L. A transition-in plan that includes strategies for the migration of support and addresses:

a. Implementation of supervisory and program functions.

b. The process for transitioning predecessor employees, if any.

c. The process for submitting new applications for personnel clearances, etc.

The contractor shall execute a smooth and orderly transition with the predecessor contractor to assure minimum disruption to vital contractor services and Government activities.

The contractor shall deploy and make operational the most current version of EEP, provided as Government Furnished Software (GFS). The contractor shall make required modifications to the EEP to enable deployment to the contractor’s approved privately hosted environment, in accordance with the ETDP. The contractor shall utilize contractor-supplied networking solutions and infrastructure. The provided infrastructure shall protect For Official Use Only (FOUO) information and the AWS-3 Licensees’ competition sensitive data from potential compromise.

The contractor shall begin the deployment of the EEP on a Friday, no earlier than 5pm (Eastern Time), and the specific date will be approved by DSO. This shall include a full domain transfer of 1755eep.com. The system shall be fully tested and ORR completed NLT 4PM (Eastern Time), on the sixth following business day (i.e., second Monday), and the system shall not be taken offline for more than five (5) business days. The system shall be operational, including any transfers of domain name ownership, by the start of the seventh business day (i.e., second Tuesday NLT 9am Eastern Time). Operational status, with full EEP functionality, must be declared within sixty (60) days of contract award.

The contractor shall perform deployment testing of the EEP to ensure a high-quality product is deployed with full functionality. The contractor shall document test plans within the ETDP. The contractor shall integrate the use of the current EEP Operations and Maintenance vendor into the test plan as a test observer and subject matter expert (SME) consultant during testing. Additionally, the contractor shall include Government staff and other staff, as requested by the COR, as test participants. The DSO will provide the services of the current EEP Operations and Maintenance (O&M) contractor at no cost. The contractor’s plan shall include a hotwash session with all the participants at the end of the test event.

The contractor shall test the initial deployment in accordance with the approved test plan. The contractor shall record all defects found during testing in the PB in accordance with Subtask 3.1. The contractor shall develop a deployment test report for DSO review and approval. The test report shall document hotwash discussions, test results, lessons learned, action items, and an action plan.

The contractor shall conduct an ORR for the EEP deployment and present the results prior to making EEP operational. The contractor shall prepare ORR materials and deliver ORR minutes no later than two (2) business days after the ORR. During the ORR, the contractor shall demonstrate that full EEP functionality has been preserved and deployed, and the contractor shall ensure that existing EEP accounts have been successfully ported. The DSRMT will approve or deny operational status based on testing results and the ORR. To obtain DSRMT approval, the contractor shall take required corrective actions identified during the ORR.