HS0021-15-R-0010-0008.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

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

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

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to update Task Order 0001 PWS 1.6.15.1; L.4 Table 1; and L.4.c.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 31

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

16C. DATE SIGNED

BY 22-Jul-2015

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X HS0021-15-R-0010

X 9B. DATED (SEE ITEM 11)

24-Mar-2015

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

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

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

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

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

CONTRACT ORDER NO. IN ITEM 10A.

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

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

D. OTHER (Specify type of modification and authority)

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

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

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

22-Jul-2015

CODE

DEFENSE SECURITY SERVICE

ASHLEY MADDOX 571.305.6547

RUSSELL-KNOX BUILDING

27130 TELEGRAPH ROAD

QUANTICO VA 22134

HS0021 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

HS0021-15-R-0010

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

PI TASK ORDER - PWS

TASK ORDER 0001

PERFORMANCE WORK STATEMENT (PWS)

Program Integration (PI) Program Support Services (PSS)

PART 1

GENERAL INFORMATION

1. GENERAL: This PWS describes the technical and administrative requirements necessary to create and implement non-personal services contract to provide Program Integration (PI) Program Support Services (PSS) services to the Business Enterprise (BE) offices of the Defense Security Service (DSS). The Government shall not exercise direct supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Offeror who, in turn is responsible to the Government for the accomplishment of the work.

1.1 Description of Services/Introduction: The Offeror shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items as well as non-personal services necessary to perform the PI-PSS as defined within this PWS except for those items specified as Government furnished property and services. The Offeror shall perform to the standards in this order as well as those in the base contract.

1.2 Background: The BE Office, through advanced planning, collaboration, requirements clarification and communication, ensures requirements are identified, programmed and managed in a consistent and coordinated fashion. PI provides a liaison between support functions and operations, facilitates advanced planning through Integrated Product Teams (IPTs) and Working Groups (WGs), coordinates all Agency programs and projects, and reviews and analyzes business processes for improvements.

1.3 Objective: The objective of this PWS is to provide a broad range of inter-related management and support requirements in support of the program management, resource allocation, and business operations for the BE Offices. This contract supports all of BE operations, streamlining the program control functions across our portfolio of efforts. Roles supported include portfolio/program/project management, technical managers, transition managers, and Contracting Officer’s Representatives (CORs), responsible for BE emergent technology efforts, projects, and interest areas. This order and PWS are intended to support DSS BE PI and the Tier 1 projects that PI is responsible for overseeing. More information on the amount of Tier 1 projects can be found in section 7.2 of this PWS.

Aside from accomplishing these tasks separately, as they are described below, the Offeror is expected to take an integrated, process-oriented approach that will result in standardized, repeatable process improvements that maximize the use of knowledge management to effectively utilize resources. By providing a matrix of support across the program and projects in the BE/PI office, the Offeror will be better able to standardize and tighten existing processes, to identify process improvement areas, provide economies of scale, and to suggest strategic approaches across the full range of program management activities.

1.4 Scope: The scope of this effort includes, Integrated Business Management Program Support Services to include the following:

1.4.1. Requirements Planning in support of DSS to include the following:

1.4.1.1. Performance Work Statement/Statement of Objectives Development and Support, Milestone Schedule Development and Support, and Requirements Documents Preparation and Support;

1.4.1.2. Strategic Process Improvement and Business Requirements Responsibilities including the following:

1.4.1.2.1. Improvement Action and Implementation Plan, Business Process Reengineering;

1.4.1.2.2. After action reports to document results (SWOT - strength, weakness, opportunity threat impacts) of the process improvement efforts;

1.4.1.2.3. Functional Process Improvement (FPI) activities;

1.4.1.2.4. Functional Economic Analysis (FEA) to document potential savings;

1.4.1.2.5. Develop and maintain performance measures;

1.4.2. Program/project/portfolio management support to include the following;

1.4.2.1. Focused process reviews (diagnose);

1.4.2.2. Strategic process improvement planning (establish plan);

1.4.2.3. Tracking/monitoring and feedback for program/project management functions (act/track/plan);

1.4.2.4. Process management for establishing baselines and monitoring, updating, and continuous refinement of processes, practices, templates, etc. (learn/leverage/refine)

1.4.3. Analyses and Quality Assurance (QA) support to overall quality assurance support such as documentation reviews, information dissemination, and mitigation plan documentation to ensure all systems are properly documented in accordance with approved DoD and DSS standards and the following:

1.4.3.1. Business Trends analysis;

1.4.3.2. Earned Value Management analysis assistance.

1.5 Period of Performance: The period of performance shall be for one (1) Base Year of 12 months from the date of contract award, with four (4) 12 month option periods.

1.6 General Information:

1.6.1 On-Site Working Conditions, Holidays and other Closures:

1.6.1.1 (See Base IDIQ PWS)

1.6.1.2 (See Base IDIQ PWS)

1.6.1.3 (See Base IDIQ PWS)

1.6.1.4 (See Base IDIQ PWS)

1.6.1.5 (See Base IDIQ PWS)

1.6.1.6 (See Base IDIQ PWS)

1.6.1.6.1 (See Base IDIQ PWS)

1.6.1.6.2 (See Base IDIQ PWS)

1.6.1.7 (See Base IDIQ PWS)

1.6.2 Hours of Operation: When the Offerors personnel are working at the Government’s site, the Offeror is responsible for conducting business during normal business hours between 8:00 a.m. to 4:30 p.m., Monday through Friday, except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. The Offeror must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS. When hiring personnel, the Offeror shall keep in mind that the stability and continuity of the workforce are essential. The Government is not responsible for paying any overtime premiums or expenses under this contract. The Offeror’s Program Manager (PM) and the Government’s COR and Task Manager shall consult and coordinate on any proposed alternate work schedules that may be arranged depending on the operational tempo and needs of the mission.

1.6.3 Place of Performance: (See Base IDIQ PWS)

1.6.4 Type of Contract: The Government will award a Firm Fixed Price Task Order.

1.6.5 Security Requirements: A Top Secret (TS) Facility Clearance is required for this procurement at time of proposal submission.

1.6.5.1 Physical Security: (See Base IDIQ PWS)

1.6.5.2 Badges Control: (See Base IDIQ PWS)

1.6.6 Post Award Conference/Periodic Progress Meetings: The Offeror agrees to attend any post award conference convened by the contracting activity in accordance with Federal Acquisition Regulation (FAR) Subpart 42.5. The CO, COR, with other Government personnel, as appropriate, may meet periodically (not more than quarterly) with the Offeror to review the Offeror's performance. At these meetings the CO will apprise the Offeror of how the Government views the Offeror's performance and the Offeror will apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the government. Either party may request an ad hoc meeting to discuss any situation that requires the attention of parties where it would not be appropriate to wait until the next scheduled periodic meeting.

1.6.7 Contract Management: (See Base IDIQ PWS)

1.6.7.1 Contracting Officer (CO): (See Base IDIQ PWS)

1.6.7.2 Contracting Officer Representative (COR): (See Base IDIQ PWS)

1.6.8 Key Personnel and Non-Key Personnel: The following personnel are considered key personnel by the Government and the offeror is required to provide resumes to the Government for these personnel:

Program Manager (PM), Requirements Analyst, Business Analyst, and Integrated Master Scheduler. The

Offeror shall provide a Program Manager who shall be responsible for the performance of the work. The name of this person and an alternate who shall act for the Offeror when the manager is absent shall be designated in writing to the CO. The alternate PM shall not be a sub-Offeror. The program manager or alternate shall have full authority to act for the Offeror on all contract matters relating to daily operation of this contract and shall be available during normal working hours. The following personnel are considered Non-Key Personnel and the offeror is not required to provide resumes to the Government for these personnel but the personnel shall meet the minimum requirements below: Technical Writer and Project Manager(s).

Qualifications for all personnel (including the Key Personnel identified above in section 1.6.8) are listed below:

1.6.8.1 Program Manager:

Minimum Requirements Bachelor’s degree (or higher level degree) in Program/Project Management, Business Management, Finance, Information Technology/Computer Science, Logistics Management or related discipline 10 years of demonstrated Portfolio, Program and Project Management (PM) experience Active Project Management Professional (PMP) certification or Program Management Professional (PgMP) certification 5 years of DoD experience 5 years of demonstrated experience with the Defense Acquisition System 3 years’ experience with the DoD Planning, Programming, Budgeting, and Execution (PPBE) processes as they relate to the Deputy Chief Manager Office (DCMO), the DoD Office of the Chief Information Officer (OCIO) and the Investment Review Board (IRB) 5 years of demonstrated intermediate knowledge of the Software Development Life Cycle (SDLC) or similar life cycle management methodology 2 years of demonstrated intermediate knowledge of PM documentation (e.g. Project Management Plan, Project Schedule, and Standard Operating Procedure)

1.6.8.2 Requirements Analyst:

Minimum Requirements

Bachelor’s degree (or higher level degree) in Program/Project Management, Business Management, Finance, Information Technology/Computer Science, Logistics Management or related discipline 5 years of demonstrated intermediate knowledge of gathering, analyzing and documenting business and functional requirements.

5 years’ experience working DoD programs 5 years of intermediate knowledge in interviewing, analyzing, observing and professional writing experience.

5 years of intermediate knowledge of creating and completing SDLC documentation

1.6.8.3 Business Analyst

Minimum Requirements

Bachelor’s degree (or higher level degree) in Program/Project Management, Business Management, Finance, Information Technology/Computer Science, Logistics Management or related discipline 5 years’ experience working with DoD business requirements

5 years’ experience performing strategic planning to identify the organizational business needs to assist in bridging the gap between business problems and the technology solutions 5 years’ experience in performing Business Model analysis to assist in standardizing the organization’s workflow 5 years’ experience conducting systems analysis

1.6.8.4 Integrated Master Scheduler

Minimum Requirements

Bachelor’s degree (or higher level degree) in Program/Project Management, Business Management, Finance, Information Technology/Computer Science, Logistics Management or related discipline 5 years professional experience with developing, communicating and implementing Integrated Master Schedules 5 years demonstrated experience with multi-phased projects 5 years’ experience using MS Project Server Active Project Management Professional (PMP) certification 5 years demonstrated portfolio, program and project management experience

1.6.8.5 Technical Writer

Minimum Requirements

Bachelor’s degree (or higher level degree) in Program/Project Management, Business Management, Finance, Information Technology/Computer Science, Logistics Management or related discipline 5 years of experience in professional writing.

5 years’ experience creating and completing SDLC documentation, to include but not limited to training and instructional information, guidelines, processes and procedural documentation.

1.6.8.6 Project Managers (to support the Tier 1 projects identified in Section 7.2 of the Task Order

0001 PWS.)

Minimum Requirements Bachelor’s degree (or higher level degree) in Program/Project Management, Business Management, Finance, Information Technology/Computer Science, Logistics Management or related discipline Active Project Management Professional (PMP) certification 5 years demonstrated program and/or project management experience 5 years demonstrated knowledge developing Program/Project Management (PM) documentation (e.g. project management plan, work breakdown structure, risk management plan, project schedule, meeting agendas, meeting minutes) 3 years of DoD experience 3 years of demonstrated knowledge of the Software Development Lifecycle or Systems Development Lifecycle or similar lifecycle management methodology Must be able to Multitask and handle more than one Tier 1 project at a time

1.6.9 Identification of Offeror Employees: (See Base IDIQ PWS)

1.6.10 Performance Evaluations in Offeror Performance Assessment Reporting System (CPARS):

1.6.10.1 (See Base IDIQ PWS)

1.6.10.2 (See Base IDIQ PWS)

1.6.10.3 (See Base IDIQ PWS)

1.6.11 Travel Costs: Travel outside the local commuting area is not anticipated under this contract. During execution of the contract if the Offeror is required to travel, a contract modification will be executed by the Contracting Officer to incorporate a Cost CLIN for the required travel.

1.6.12 Nondisclosure Agreements: (See Base IDIQ PWS)

1.6.12.1 The non-disclosure agreements contained in Section J shall be signed by all Offeror employees supporting this effort and forwarded to the Office of Acquisitions in care of the CO, prior to the commencement of work.

1.6.12.2 (See Base IDIQ PWS)

1.6.13 Quality Control (QC): The Offeror shall develop and maintain an effective quality control program to ensure services are performed in accordance with this PWS. The Offeror must have an ISO certification 9001:2008. The Offeror shall develop and implement plans, procedures, and incident reports in support of identification, prevention, and to proactively non-recurrence of defective services, capabilities, or products.

The Offeror’s quality control program (QCP) is the means by which he assures himself that his work complies with the requirement of the contract. The QCP is to be delivered 10 days after the date of contract award. A comprehensive written QCP shall be submitted to the CO and COR within 5 working days when changes are made thereafter. After Government acceptance of the QCP, the Offeror shall receive the CO’s acceptance in writing of any proposed change to the Offeror’s QC system.

1.6.13.1 Quality Control Reports: The Offeror shall submit a monthly Quality Control Report for each functional area identified in the contract. The report shall be submitted to the COR and contracting officer on the last day off the month for review as part of the Offeror's quality control program.

1.6.14 Quality Assurance: The government shall evaluate the Offeror’s performance under this contract in accordance with the contractors Quality Control Plan and the Governments Quality Assurance Surveillance Plan (QASP). The QASP is a Government developed and applied document used to make sure systematic quality assurance methods are used in the administration of the Performance Based Service Contract (PBSC) standards included in this PWS and contract. The intent is to ensure that the Offeror performs in accordance with the performance metrics and the Government receives the quality of services called for in the contract. The QASP details how the performance standards identified in the PWS will be measured, who will perform the measurement, the frequency of surveillance, and the acceptable defect rate(s). The QASP may be updated from time to time by the government.

1.6.15 Transition:

1.6.15.1 The Phase-In transition period is anticipated to last for 30 days from date of award. The Offeror shall create and submit a draft transition plan with their proposal. A final Transition plan is required within five days of awardwhen requested by the CO but and the Offeror shall keep the Government fully informed of status throughout the a transition period. Throughout the a phase-in period, it is essential that attention be given to minimize interruptions or delays to work in progress that would impact the mission. The Offeror must plan for the transfer of work control and delineating the method for processing and assigning tasks during the phase-in period.

1.6.15.2 The Phase-Out transition period is anticipated to last for 30 days to the end of the contract; phase-out shall begin 30 days immediately prior to contract end. Upon the Contracting Officer’s written notice, the Offeror shall create and submit a transition plan for approval by the Government. The Offeror shall keep the Government fully informed of status throughout the transition period. Throughout the phase-out period, it is essential that attention be given to minimize interruptions or delays to work in progress that would impact the mission. The Offeror must plan for the transfer of work control and delineating the method for processing and assigning tasks during the phase-out periods. The Offeror shall provide sufficient experienced personnel during the phase-in, phase-out period to ensure that the services called for by this contract are maintained at the required level of proficiency.

1.6.15.3 The Offeror shall provide a transition plan when requested by the CO. The transition plan shall detail the plan the Offeror will employ during contract phase-in process (phase-out only upon request). The Government will monitor the transition plan during performance of the phase-in (phase out) period to ensure that the Offeror is performing in accordance with the transition plan.

At a minimum, the plan shall address the following:

Transition Strategy to include time schedules for both Phase-In and Phase-Out Identify any risks and a mitigation strategy to manage the risks Phase-In Requirements:

o Plan on hiring incumbent workers, if applicable, or filling vacancies.

o If incumbent employees are not hired, plan on how the current knowledge is transferred to new staff.

o Training of new staff

Phase-Out Requirements (when requested):

o Plan for maintaining coverage while new Offeror Phases-in.

o Plan on how the current knowledge and workload will be transferred to new

Offeror/staff.

o Plan on how Offeror will manage the closeout of tasks to be completed before transition is completed.

o Identification of any potential areas that will cause the Government Harm.

1.6.16 Program Review with DSS:

1.6.16.1 The Offeror, the CO, and COR(s) shall meet to review performance under this contract, to determine on-going status, to identify and resolve problems and/or to provide information to decision-maker(s).

1.6.16.2 During the first month weekly transition/phase-in meetings will be held.

1.6.16.3 Thereafter, the Offeror, the CO, and COR(s) will meet quarterly to discuss key process indicators, process deficiencies and problem resolutions. During these meetings, the Offeror’s performance and any existing problems will be discussed. A mutual effort will be made to resolve all problems/issues identified.

PART 2

DEFINITIONS & ACRONYMS

2. DEFINITIONS AND ACRONYMS:

2.1. DEFINITIONS:

2.1.1. CONTRACTOR. (See Base IDIQ PWS)

2.1.2. CONTRACTING OFFICER (CO). (See Base IDIQ PWS)

2.1.3. CONTRACTING OFFICER'S REPRESENTATIVE (COR). (See Base IDIQ PWS)

2.1.4. DEFECTIVE SERVICE. (See Base IDIQ PWS)

2.1.5. DELIVERABLE. (See Base IDIQ PWS)

2.1.6. KEY PERSONNEL. (See Base IDIQ PWS)

2.1.7. PHYSICAL SECURITY. (See Base IDIQ PWS)

2.1.8. QUALITY ASSURANCE. (See Base IDIQ PWS)

2.1.9. QUALITY ASSURANCE SURVEILLANCE PLAN (QASP). (See Base IDIQ PWS)

2.1.10. QUALITY CONTROL. (See Base IDIQ PWS)

2.1.11. SENIOR STAFF. (See Base IDIQ PWS)

2.1.12. SUBCONTRACTOR. (See Base IDIQ PWS)

2.1.13. ISFD. The ISFD application is a DSS managed database with centralized industrial security facility information. The application interfaces with the system of record for security plans, OBMS, automates the Request for Information (RFI) process and facilitates mass communication to Industry POCs.

2.1.14. NCAISS. The DSS NISP Central Access and Information Security System (NCAISS) program provides identity and access related functionality across DSS' Information Technology (IT) infrastructure.

This initiative is designed to enable multiple DSS business systems to have service-accessibility that is controlled through PKI-compliant single sign-on (SSO) authentication.

2.1.15. NCCS. NISP Contract Classification System is designed to create a Federated solution for maintaining and reporting classified contracts’ DD254 contract security classification specification.

Leveraging and existing Army system, ACCS, and build in the additional functional requirements to meet all participating organization’s needs.

2.1.16. NISS. National Industrial Security System (NISS) is the in-the-planning Material solution for the Agency’s Industrial Security Mission. The system will automate the facility clearance enabling processes which are executed by various members of the Industrial Operations Directorate, including but not limited to Facility Clearance Branch (FCB), Industrial Security Reps (ISRs), Industrial Security System Professionals (ISSPs) and Foreign Ownership Control and Influence (FOCI) branches. Initial operating capabilities (IOC) will include functionality contained within the legacy Industrial Security Facilities Database (ISFD) and the Department of Energy (DoE) electronic Facility Clearance (eFCL) system, anticipated for delivery by FY17.

2.1.17. OBMS. The ODAA Business Management System program is the automation development of ODAA’s manual management of approving and assessing cleared industries classified information system processing.

2.1.18.

2.1.19.

2.1.20. DITMS. The DSS Insider Threat Mitigation System is a project that consists of hardware and software installation and initial operation at DSS Data Center. DITMS is a component of the Insider Threat Identification and Mitigation Program which is being operated under control of DSS Counterintelligence.

2.1.21. CDS. The Cross Domain Solution will allow DSS users to transfer specified data files between NIPRNet and SIPRNet domains using the DISA service.

2.1.22. ARCTC. This system includes case management, database repository, and data integration from multiple disparate locations allowing CI to perform analysis on disparate data sources, search and discovery tools, analytical functions, metrics reporting and data mining. This system provides a secure enterprise-level intelligence data analytics.

2.1.23. STEPP. The Security Training, Education and Professionalization Portal are the Defense Security Services’ learning management system. The Center for Development of Security Excellence (CDSE) provides security education, training, and certification products and services to a broad audience supporting the protection of National Security and professionalization of the DoD security enterprise.

2.2. ACRONYMS:

(See Base IDIQ PWS) ARCTC Analysis, Research, Case Tracking, and Collaboration CDS Cross Domain Solution CFR Code of Federal Regulations DITMS DSS Insider Threat Management System ECP Electronic Communications Plans eFCL Electronic Facility Clearance System eQIP Electronic Questionnaires for Investigations Processing FCD Facilities Clearance Division FISL Fundamentals of Industrial Security IRB Investment Review Board ISFD Industrial Security Facility Database NCAISS NISP Central Access and Information Security System NCCS NISP Contract Classification System NISS National Industrial Security System OBMS ODAA Business Management System PIPO Phase In/Phase Out STEPP Security Training, Education and Professionalization Portal

PART 3

GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES

3. GOVERNMENT FURNISHED ITEMS AND SERVICES:

3.1 Services: (See Base IDIQ PWS)

3.1.1. (See Base IDIQ PWS)

3.1.2. Consent to Monitoring: (See Base IDIQ PWS)

3.2 Facilities: (See Base IDIQ PWS)

3.3 Replacement, Modernization, and Modification: (See Base IDIQ PWS)

PART 4

CONTRACTOR FURNISHED ITEMS AND SERVICES

4. CONTRACTOR FURNISHED ITEMS AND RESPONSIBILITIES:

4.1 General: (See Base IDIQ PWS)

4.2 Facility Clearance: A Top Secret (TS) Facility Clearance is required for this procurement.

4.3 Security Clearances: (See Base IDIQ PWS)

4.4 Materials and Equipment: (See Base IDIQ PWS)

PART 5

SPECIFIC TASKS

5. SPECIFIC TASKS:

5.1 Program/Project Management Support:

Reserved

5.2 Performance Standards:

5.2.1 The Offeror shall be effective in ensuring quality, accuracy and timely support of the Business Enterprise Program Integration (PI) Office, including reviews (complete with an assessment and implementation plan, as needed) of mission statements, Federal policies and regulatory directives at least 90% of the time. The Government will use the following methods of surveillance, as appropriate, to ensure the Offeror is providing the Acceptable Quality Level for this Performance Standard: Random monitoring, 100% inspection of all deliverables, Monthly Reports, Customer Surveys by the assigned Task Manager, COR, and/or CO.

5.2.2 The Offeror shall provide assistance to the government program/project managers in initiating, planning, executing, monitoring & controlling, and closing the entire range of programs and projects over which the PI Office has cognizance at least 95% of the time. The Government will use the following methods of surveillance, as appropriate, to ensure the Offeror is providing the Acceptable Quality Level for this Performance Standard: Random monitoring, 100% inspection of all deliverables, Monthly Reports, Customer Surveys by the assigned Task Manager, COR, and/or CO.

5.2.3 The Offeror shall provide professional business services that include project leadership and communications with stakeholders; project planning and management; performance monitoring and measurement; reporting and documentation associated with project/program/portfolio objectives and analysis; developing and implementing policies and processes; program integration services; and project close-out and transition services at least 95% of the time. The Government will use the following methods of surveillance, as appropriate, to ensure the Offeror is providing the Acceptable Quality Level for this Performance Standard: Random monitoring, 100% inspection of all deliverables, Monthly Reports, Customer Surveys by the assigned Task Manager, COR, and/or CO.

5.2.4 The Offeror shall attend key on-site events such as configuration control board meetings, program management meetings and other direct support events to ensure that the requirements of this contract are accomplished at least 95% of the time. The Government will use the following methods of surveillance, as appropriate, to ensure the Offeror is providing the Acceptable Quality Level for this Performance Standard:

Random monitoring, 100% inspection of all deliverables, Monthly Reports, Customer Surveys by the assigned Task Manager, COR, and/or CO.

5.2.5 Offeror will assist in providing agendas and meeting minutes at least 99% of the time. The Government will use the following methods of surveillance, as appropriate, to ensure the Offeror is providing the Acceptable Quality Level for this Performance Standard: Random monitoring, 100% inspection of all deliverables, Monthly Reports, Customer Surveys by the assigned Task Manager, COR, and/or CO.

5.2.6 The Offeror will participate in programmatic meetings, reviews, and briefings associated with this contract at least 99% of the time. The Government will use the following methods of surveillance, as appropriate, to ensure the Offeror is providing the Acceptable Quality Level for this Performance Standard:

Random monitoring, 100% inspection of all deliverables, Monthly Reports, Customer Surveys by the assigned Task Manager, COR, and/or CO.

5.3 Tasks:

5.3.1. Program/Project/Portfolio Management.

5.3.1.1 The Offeror shall provide program management support that includes program/project/portfolio analysis of functional, management, and technical requirements for the applicable projects within the Program Integration Office.

5.3.1.2 The Offeror shall also assist the Government in tracking actions related to OSD guidance, engineering review boards, sustainment conferences, etc., as necessary.

5.3.1.3 The Offeror shall provide portfolio/program/project assessment reports as requested or shall collect program management documentation from various action offices in the Agency to summarize progress and issues of portfolios/programs/projects during their lifecycles and shall assist in aggregating management data for both continuing reports and in response to ad hoc requests for information.

5.3.1.4 The Offeror shall perform a variety of PM support functions, including estimation and tracking of project and system costs, development and maintenance of work breakdown structures (WBS) and schedules.

5.3.1.5 The Offeror will develop and maintain an Integrated Master Schedule (IMS). The Contract shall support the PI Office in developing and maintaining a RACI matrix. The Offeror shall participate in developing and disseminating the communications plans for designated programs.

5.3.1.6 The Offeror shall collect information, develop and analyze individual project schedules so that there is a finalized project schedule which conveys resource commitments, critical paths, costs and durations of projects being executed throughout the organization.

5.3.1.7 The Offeror shall provide program management and planning documentation to summarize progress and issues of the financial portfolio (across all programs/projects under the Program Integration Office), specific programs and individual projects as they progress and the aggregate set of projects within assigned task areas.

5.3.1.8 The Offeror shall develop, monitor, and report on applicable performance-based metrics to include internal management controls.

5.3.1.9 The Offeror will be responsible for configuration management (with respect to tracking and maintaining the product configuration items associated with each program/project), workflow management, and productivity assessments. In so doing, the Offeror will interact with and collect data from other Government internal and external sources, as well as from other contractors.

5.3.1.10 The Offeror shall participate in program reviews and IPTs. The Offeror shall also assist with the development and monitoring of program and project schedules, planned and ad hoc reviews, and providing information needed for program/project descriptions, briefs, and brochures.

5.3.1.11 The Offeror shall participate in developing and disseminating the communications and training plans for the designated programs.

5.3.1.12 The Offeror shall update, maintain, and coordinate efforts in support of the following:

Clinger-Cohen Act (CCA) Compliance, Business Capability Lifecycle to include the Investment Review Board (IRB), The Defense Acquisition System, DoD Risk Management Framework, Business Process Reengineering, DoD Business Case Analysis, transition strategies, DSS policies and procedures, and other program strategy documents.

5.3.1.13 The Offeror shall assist the program office and project teams with the development of various specific and individual program related documentation to include Decision Briefings/White Papers.

5.3.1.14 The Offeror shall assist and provide the documentation, and updating of standardized processes, plans, training guides, deployment processes, operational instructions, process maps, standard operating instructions, user guides, templates, technical reports, and relevant performance agreements (e.g., operational level agreements and /or service level agreements) related to the various functions, and knowledge areas.

5.3.1.15 The Offeror shall actively participate in the design and documentation of the Knowledge Management repositories and networking tools.

5.3.1.16 The Offeror shall assess current portfolio/program/project processes and analyze them for effectiveness, highlighting potential bottlenecks, roadblocks, and major problem areas. The analysis shall include recommendations to overcome or mitigate these concerns and streamline the processes. Key process descriptions will cover the process purpose, controls, inputs, outputs, entrance/exit criteria, basic steps, verification/validation processes, roles, mechanisms, and associated metrics.

5.3.1.17 The Offeror shall provide technical expertise for the review and possible re-engineering of technical and business processes such as acquisition, financial reporting, solutions fielding, strategic and operational planning, transition engineering, training, operations, and customer support. Processes shall be in accordance with appropriate user (e.g., DoD, DSS, Industry).

5.3.1.18 The Offeror shall provide process reviews, analysis, and recommendations, and other program or process improvements suggestions in technical reports as needed.

5.3.2 Strategic Process Improvement and Business Requirements Responsibilities.

5.3.2.1 The Offeror shall develop an Improvement Action and Implementation Plan to take corrective measures. The plan will identify specific timelines, and key thresholds to monitor. The plan will have checkpoints for reassessment or re-direction as necessary. The plan will have a complexity component that identifies if all actions can be corrected within the Program Integration Office, or if external organizations will be needed for coordination. The complexity component relates to the number of organizational elements beyond the PI Office that must comply with the plan.

5.3.2.2 The Offeror shall develop Business Process Reengineering (BPR) plans and conduct BPR activities and shall examine organizational goals, objectives, structures/hierarchies, culture, systems, and roles.

5.3.2.3 The Offeror shall develop after action reports to document results (SWOT - strength, weakness, opportunity threat impacts) of the process improvement efforts. The Offeror shall conduct Functional Process Improvement (FPI) activities; e.g., review current processes, data and systems, and identify non-value added activities, identify value-added activities for integration;

develop Functional Economic Analysis (FEA) to document potential savings; and develop and maintain performance measures.

5.3.2.4 The Offeror shall provide BPR Plans, FPI and FEA recommendations, and other program or process improvements suggestions in technical reports as needed.

5.3.2.5 The Offeror shall assist in gathering and documenting business, stakeholder, solution and functional requirements through interviews, focus groups, workshops and other decision making techniques. Documents of collected requirements will be created and include requirements objectives, business rules, organization principles and impacts, service levels, assumptions and requirements traceability matrix.

5.3.2.6 The Offeror will assist in creating templates for various requirements types to be used in the requirements gathering and defining process.

5.3.2.7 The Offeror shall provide requirements clarification to include technical writing expertise by translating business requirements into development/functional/ technical language.

5.3.3 Analyses and Quality Assurance (QA) Support.

5.3.3.1 This area includes the following:

5.3.3.1.1 Planning, analyzing, and reporting programmatic impacts on the costs, return on investment, schedule dependencies, and recommending both functional and technical solutions;

5.3.3.1.2 Assisting in developing and maintaining Mission Analysis and Quality Assurance Standard Operating Procedures;

5.3.3.1.3 Documentation review, staffing, and control services to ensure all systems are properly documented in accordance with approved DoD and DSS standards and in accordance with guidance appropriate to the type of project;

5.3.3.1.4 Participating in information dissemination activities and general outreach activities relating to the program office mission and functions;

5.3.3.1.5 Establishment, monitoring, and reporting of program metrics to include 1) common Knowledge Management information and related metadata, and 2) Internal Management Controls;

5.3.3.1.6 Offeror shall assist in developing and maintaining a risk register and perform risk monitoring;

5.3.3.1.7 The contract shall assist in developing and disseminating Status Reports as it relates to the Quality Assurance;

5.3.3.1.8 Document mitigation plans;

5.3.3.1.9 Preparation of program/project status reports, in response to either regularly required reports or short notice, ad hoc report requirements;

5.3.3.1.10 Participating in or coordinating IPT activities;

5.3.3.1.11 Review and analysis or program/project documentation, including document cross-walks between requirements (functional and technical), measures, or assessment criteria and functionality; and

5.3.3.1.12 The Offeror shall evaluate programs and projects to ensure that key considerations have been adequately planned for and that relevance guidance has been complied with.

PART 6

APPLICABLE PUBLICATIONS

6. APPLICABLE PUBLICATIONS

6.1 The Offeror must abide by all applicable regulations, publications, manuals, and local policies and procedures.

6.2 (See Base IDIQ PWS)

6.3 (See Base IDIQ PWS)

6.4 (See Base IDIQ PWS)

6.5 Information Assurance: (See Base IDIQ PWS)

6.6 Information Assurance Workforce Certification: (See Base IDIQ PWS)

6.7 Section 508 Compliance Statements: (See Base IDIQ PWS)

If any aforementioned documents are inaccessible, they are available from DSS upon request.

In the event that applicable governing regulations and/or directives conflict, the more stringent of the governing regulations and/or directives shall take precedence.

PART 7

ATTACHMENT/TECHNICAL EXHIBIT LISTING

7. Attachments/Technical Exhibit List:

7.1 Technical Exhibit 1 – Performance Requirements Summary

7.2 Technical Exhibit 2 – Historical Workload Summary

7.1 TECHNICAL EXHIBIT 1

PERFORMANCE REQUIREMENTS SUMMARY

Performance Objective Standard Method of Surveillance

PRS # 1

The Offeror shall support of the Business

Enterprise Program Integration (PI) Office IAW

PWS 5.2.1.

Completed at least 90% of the time. Random inspection

PRS # 2

The Offeror shall provide assistance to the government program/project manager IAW PWS 5.2.2.

Completed at least 95% of the time. Random inspection

PRS # 3

The Offeror shall provide professional business services IAW PWS 5.2.3.

Completed at least 95% of the time. Random inspection

PRS # 4

The contract shall attend key on-site events IAW

PWS 5.2.4.

Completed at least 95% of the time. Random inspection

PRS # 5

The contract shall assist in providing agendas and meeting minutes IAW PWS 5.2.5.

Completed at least 99% of the time. Random inspection

PRS # 6

The contract shall participate in programmatic meetings, reviews and briefings IAW PWS 5.2.6.

Completed at least 99% of the time. Random inspection

7.2 TECHNICAL EXHIBIT 2

HISTORICAL WORKLOAD SUMMARY

The Government historically has had eight (8) to 12 tier one projects per year. Tier 1 projects normally cross directorates and/or are sponsored by a directorate outside of BE. These projects are normally high visibility efforts that are reported and briefed to DSS senior leaders.

Examples of Tier 1 Projects that the Government has supported in the past are:

1. The Open Source Corporate Management Information System (OSCMIS)*;

2. Cross Domain Solution (CDS);

3. Operational Analysis Group (OAG) Web Form;

4. National Industrial Security Program (NISP) Control Access and Information Security System (NCAISS);

5. National Industrial Security Program (NISP) Contract Classification System (NCCS);

6. National Industrial Security System (NISS);

7. Security Training, Education and Professionalization Portal (STEPP);

8. Office of the Designated Approving Authority (ODAA) Business Management System (OBMS);

9. The Industrial Security Facilities Database (ISFD);

10. DSS Insider Threat Mitigation System (DITMS);

11. Defense Insider Threat Management and Analysis Center (DITMAC);

12. Analysis, Research, and Case Tracking and Collaboration (ARCTC)

* Program is no longer a DSS Project and no future support required.

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

INSTRUCTIONS TO OFFERORS

Section L: INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

L.1. EXCEPTIONS OR CONDITIONS CONTAINED IN OFFEROR'S PROPOSAL.

In the event the offeror takes any exception to, or sets any conditions for its proposal under this solicitation, such exceptions or conditions shall be set forth in a cover letter to offeror's proposal. However, if the Government does not deem these exceptions or conditions as in the best interest of the Government, the offerors proposal may be deemed nonresponsive and shall not be considered for award. Generally, exceptions or conditions will make a proposal nonresponsive.

L.2 ELIGIBILITY.

To be eligible to submit an offer under this Solicitation and receive award, an offeror must be eligible for award as a small business in accordance with FAR 19.301-1 and must meet the following requirements:

L.2.1.1 The Program Support Services (PSS) requirement is a critical program necessary for Defense Security Service (DSS) to successfully meet its mission. The Government requires that the Offeror's performance begin upon award without delay. Therefore, the Offeror shall have a facility clearance of TOP SECRET in accordance with the DoD 5220.226M, National Industrial Security Program Operating Manual (NISPOM) at the time of proposal submission. This requirement applies to any entity needing access to classified material in the performance of any contract that may result from this solicitation.

L.2.1.2 Proposals are required to meet all of the Basic Contract and Task Order 0001 PWS requirements.

Failure to comply with the terms and conditions of the solicitation shall result in the Offeror’s proposal being found to be technically unacceptable and shall not be considered for award.

L.3. INTRODUCTION.

The DSS Office of Acquisitions is releasing this solicitation as a Request for Proposal in electronic format only.

The electronic version of this solicitation is the official version for this acquisition. No hard copy of the solicitation will be issued. Any amendments to this solicitation will be submitted in the same manner as this solicitation.

Proposals shall be sufficiently detailed to enable the Government to perform an accurate and complete evaluation strictly from the proposal contents. However, in the area of Past Performance the Government may use data obtained from other sources. The offeror’s proposal shall consist of four volumes. The Volumes are: Volume I - Solicitation, Offer and Award Documents, Section K, Representations and Certificates, and Quality Control Plan;

Volume II – Technical Capability (which shall include resumes for Key Personnel); Volume III – Past Performance;

and Volume IV – Price. Files shall not contain any classified data. The use of hyperlinks in proposals is prohibited.

Offerors shall indicate in their proposal the validity of proposals for at least 120 days from the closing date of this solicitation.

L.3.1.1. PROPOSAL PREPARATION COSTS. The Government will not be obligated to pay any costs incurred by an Offeror in the preparation and submission of a proposal in response to this solicitation.

L.3.1.2. Acceptable Proposal - The Government must have received from the Offeror an acceptable proposal. The proposal is acceptable when it meets all of the terms and conditions of the solicitation, which includes the base contract PWS and Task Order 0001 PWS. Additionally, the Government may declare an offer to be nonresponsive (as detailed in Section L.1. above) if it does not meet all of the terms and conditions of this solicitation.

L.3.1.3. Proposal Retention - In accordance with FAR Subpart 4.8, Government contract files, the Government will retain one copy of all unsuccessful proposals. Unless the Offeror requests otherwise, the Government will destroy extra copies of all proposals.

L.4. PROPOSAL FILES.

a. Format. Microsoft Office Professional 2007 or later shall be used to create the files. All graphics shall be compatible with MS PowerPoint 2007. All information pertaining to a particular file shall be confined to that file.

The titles for each file, along with the references are detailed below. Each file shall contain the applicable proposal information in the referenced paragraph. All proposal submissions shall be clearly indexed and logically assembled.

Each volume shall be clearly identified and shall begin at the top of a page. All pages of each volume shall be appropriately numbered and identified by the complete company name, date and solicitation number in the header and/or footer. A Table of Contents shall be created. MS Word (.doc) files shall use the following page setup parameters:

Margins – Top, Bottom, Left, Right - 1” Gutter – 0” From Edge – Header, Footer - 0.5” Page Size, Width – 8.5” Page Size, Height – 11”

The following additional restrictions apply:

Each paragraph shall be separated by at least one blank line. A standard, 12-point minimum font size applies. Arial or Times New Roman fonts are required. Tables and illustrations may use a reduced font size not less than 8-point and may be landscape. Single space type shall be used with the exception of organization line and block charts and the Price/Cost proposal. Graphics may be submitted in black & white, half-tone or in color, in font sizes sufficient for all information to be read or reproduced without difficulty (but in no case less than 8 point Arial or Times New Roman). Foldout pages, limited to 11x17 inch page size, are permissible and shall count as two pages. Page numbers, headers and footers may be within the page margins ONLY, and are not bound by the font requirements.

Company logos are prohibited with the exception of the Title Page. Volumes that contain pages that exceed the margin, font or total page limit shall be considered technically unacceptable and the offeror shall not be considered for award.

b. File Packaging. The proposal shall be labeled with the solicitation number, as well as the name, address, and telephone number of the Offeror. Offerors shall also provide their CAGE, DUNS, and Tax Payer Identification Number for the Prime Offeror and all Subcontractors.