Attachment 3 - Knowledge Management Sample Task Order.doc
DOC document 266 KB Posted
- Attached to
- Defense Information Systems Agency Information Technology Enterprise Support Services Federal contract opportunity
- Solicitation number
- HC1047-12-R-4013
- Issued by
- Defense Information Systems Agency
View the file
Other files for this federal contract opportunity
Show all 17
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Defense Information Systems Agency
Chief Information Officer
DISA Information Technology Enterprise Support Services (DESS)
HC1047-12-D-XXXX
Task Order (TO) 0003 (Version 1.0)
31 January 2012 Table of Contents
1Chief Information Officer
1DISA Information Technology Enterprise Support Services (DESS)
11.
Task Order CORs (TO/CORs)
11.1 Primary TO/COR.
11.2 Alternate TO/COR
12.
Task Order Title:
13.
Background
34.
Objectives
35.
Scope
35.1 Enterprise Knowledge Management Support.
46.
Specific Tasks
46.1 Enterprise Knowledge Management Support
97.
Place of Performance
97.1 Primary Place of Performance
97.2 Alternate Place of Performance
98.
Travel Requirements
99.
Period of Performance
1010.
Delivery Schedule
1811.
Service Level Agreements and Performance Metrics
2612.
Security Requirements
2612.1 The VAR/VAL
2913.
Government-Furnished Equipment (GFE)/Government-Furnished Information (GFI)
2913.1 Access/GFE
2913.2
GFI
2914.
Other Pertinent Information or Special Considerations
2914.1 Identification of Potential Conflicts of Interest (COI).
2914.2 Identification of Non-Disclosure Requirements.
3014.3 Inspection and Acceptance Criteria.
3015.
Section 508 Accessibility Standards
| Task Order Number: |
| HC1047-12-D-XXXX-0003 |
1. Task Order CORs (TO/CORs) Primary TO/COR.
| Name: |
| Mr. John Doe |
| Organization: |
| DISA/CIO/CI22 |
Department of Defense Activity
Address Code (DODAAC):
HC1047
| Address: |
| P.O. Box 549, Ft Meade, MD 20755-0549 |
| Phone Number: |
| (301) 225-XXXX |
| Fax Number: |
| (301) 225-XXXX |
| E-Mail Address: |
| John.Doe@disa.mil |
Alternate TO/COR.
| Name: |
| Ms. Jane Doe |
| Organization: |
| DISA/CIO/CI22 |
Department of Defense Activity
Address Code (DODAAC):
HC1047
| Address: |
| P.O. Box 549, Ft Meade, MD 20755-0549 |
| Phone Number: |
| (301) 225-XXXX |
| Fax Number: |
| (301) 225-XXXX |
| E-Mail Address: |
| Jane.Doe@disa.mil |
2. Task Order Title:
Defense Information Systems Agency’s (DISA’s) Information Technology (IT) Enterprise Knowledge Management Support Services
3. Background The Defense Information Systems Agency is a Combat Support Agency responsible for connecting US Forces and their coalition partners to the DoD’s Global Information Technology (IT) Enterprise. DISA provides IT networks, computing infrastructure, and enterprise services in direct support of US Warfighters to facilitate the seamless exchange of information on a global scale.
The mission of DISA’s Chief Information Officer (CIO) is to, “Lead and govern the delivery and operation of secure world-wide enterprise IT services enabling the efficient and effective execution of DISA’s global combat support missions.” In order to accomplish this mission, the DISA CIO must:
· Provide an efficient and effective IT infrastructure and services to support the Agency’s warfighting mission.
· Achieve a Mission Assurance posture that ensures the security and continuity of the Agency’s internal IT Enterprise’s infrastructure and services against an ever evolving spectrum of threats.
· Maintain compliance with all DOD information governance policies and legislation.
Govern a common architecture and service delivery framework to drive efficiencies in business system investments and portfolio and knowledge management capabilities.
The Office of the Chief Information Officer (CIO) provides streamlined, easy to follow processes and programs that are second to none through the application of Knowledge Management expertise. The CIO provides clear and succinct Privacy, Knowledge Management, and Records Management program guidance and leadership in accordance with all applicable federal laws, regulations, instructions, directives, and policies.
The Office of the Chief Information Officer (CIO) requires contractor assistance to provide information and knowledge management and systems analysis related services to the Defense Information Systems Agency (DISA) and other Department of Defense (DoD) organizations. CIO provides information and knowledge management services to DISA in the management of internal business information systems and services. Services include systems functional analyses, requirements engineering, content management, COTS software configuration, and custom software development to support communities of interest and end-user support. Government and contract resources work side-by-side in providing these services to civilian and military leadership at all levels.
The use of a wide range of methods and tools is essential for organizations examining their processes and determining more effective and efficient means of executing operations and inserting technology. Technology insertion and process change go hand-in-hand to improve the operational missions. CIO focuses on internal knowledge management, process improvement, change management, and technology insertion that enable DISA personnel to perform their mission more effectively and efficiently
4. Objectives This task order will deliver the contract staff required to assist CIO in analyzing organizational processes and issues; recommending process improvement initiatives; assisting in the definition of requirements associated with implementation; supporting the development or customization of applications; implementing a robust Knowledge Management and and Electronic Records Management Program; and all aspects of delivery such as Knowledge Engineering, Requirements Development and Validation, Application Testing, Prototyping, and Systems Engineering. The services delivered through the CIO’s On-site support contract play a critical role to ensuring full success of the Agency. Full success is achieved when the output provided through this contract sufficiently supports the requirements that comprise complementary CIO contracts. Throughout this PWS, tasks that rely on or support complementary CIO contracts will be identified as such. Any future/unknown requirements that are within the scope of the Performance Work Statement as written but are unknown or undefined at this time will be separately negotiated and incorporated via task order modification.
The strategic and collaborative planning work under this task will require highly-skilled, trained, and experienced business process improvement individuals to interact with management officials and military officers of all grades and ranks to reconcile mission critical issues that are currently impairing the execution of the Department's mission. Also, the contract staff will deliver technical services to support the electronic meeting environments, which requires a technical understanding of all associated hardware, and software and audio-visual systems.
5. Scope Enterprise Knowledge Management Support.
The contractor shall provide personnel to assist the CIO in its mission of developing, leveraging, and implementing knowledge management practices, strategies, and technologies to ensure that institutional knowledge is identified, captured, assessed, accessiable, leveraged, and transferred thereby enabling a more efficient, agile, and effective Agency and workforce. The contractor shall operate within a cross-functional environment where they will embed Knowledge Engineers within various directorates, working groups, and communities of interest (as directed by the Governent) within the Agency to ensure that Knowledge Management requirements and domain expertise is being captured, assessed, and transferred into the Knowledge Based System (E.g. SharePoint 2010, Serena Team Track, Borland Calibre, or equivalent) for Knowledge based continuity planning, process analysis, and process mapping. The contractor shall assist in the development and implementation of information exchanges and technical solutions for Enterprise and Directorate specific Knowledge Management needs, gathering KM requirements and priorities, and development and implementation of rapid solutions. The contractor shall be proficient in the areas of strategic Knowledge Management concepts, Knowledge Engineering, Software Engineering, Process Improvement, and Systems Engineering in an effort to configure, implement, and leverage SharePoint for proof of concepts, identification of quick win solutions, organization process improvement, implement collaborative capabilities, and train and educate staff on solutions developed. The contractor shall establish relationships with Directorates and process owners throughout the Agency to identify opportunities for Enterprise process improvement. This shall be accomplished in part through the development, implementation, and integration of Microsoft SharePoint 2010, the DoD Enterprise Services Portal, and other Agency collaborative capabilities, in unclassified and classified domains.
6. Specific Tasks
Enterprise Knowledge Management Support
6.1.1 The contractor shall conduct technical analyses to develop and maintain a DISA IT Enterprise Knowledge Management capability as directed by the Government. The contractor shall document the design, configuration, implementation, and continuity of operations plans required to operate and maintain these capabilities.
6.1.2 The contractor shall develop and validate Knowledge Management requirements documents (using Borland Calibre or equivalent) and test plans that are in accordance with DoD, DISA, and DISA CIO directives and instructions.
6.1.3 The contractor shall conduct technical analyses to identify and propose a logical and sequential breakdown of projects required to accomplish the goals of the DISA IT Enterprise Knowledge Management Plan.
6.1.4 The contractor shall employ Knowledge Engineering principles to plan, design, develop, and implement updated intranet sites using industry best standards and practices (E.g. Content Management, Web Development, Configuration Management (CM), and Web Hosting). The contractor shall provide requirements validation, application testing, and interface testing to support this effort.
6.1.5 The contractor shall provide personnel who have an in depth knowledge of Microsoft SharePoint and Designer 2010. This knowledge shall include expertise in work flows, web applications, data visualization, business intelligence, Knowledge Engineering, Content Management, Records Management, and Enterprise Project and Portfolio Management using Microsoft Project Web Apps in a SharePoint 2010 environment.
6.1.6 The Contractor shall identify what Knowledge Management best practices, policies, and procedures should be retained and proposed for potential Agency adoption as directed by the Government.
6.1.7 The contractor shall employ Systems and Knowledge Engineering best principles to create a Business Collaboration Platform and framework for future expansion of Microsoft SharePoint 2010 to include customized applications using Enterprise SharePoint configuration options to meet business needs. The contractor shall provide testing and analytic support to ensure that development efforts function properly and meet customer requirements.
6.1.8 The contractor shall manage and maintain current and legacy information repositories and content management solutions. The contractor shall provide personnel with the technical and strategic expertise to operate, maintain, subsume, and decommission legacy content management solutions and information repositories.
6.1.9 The contractor shall serve as the Knowledge Engineering, Enterprise Content Management, and Records Management (in accordance with DoD Directive 5015.2) expert for the Agency. The contractor shall provide outreach assistance to the user community in developing and managing SharePoint Sites and other content management repositories as directed by the Government.
6.1.10 The contractor shall use Knowledge Engineering principles to anticipate, capture, evaluate, and recommend present and future Knowledge Management tools and applications, intranet capabilities, and business processes that are best suited for the Agency’s strategic needs for potential adoption and usage.
6.1.11 The contractor shall market and evaluate KM products and services and provide an understanding of the various tools available throughout the community and best practices for their usage. The contractor shall perform requirements analysis, rapid prototyping, and testing of enhancements and fixes to Knowledge Management enabling Commercial off the shelf (COTS) and Government off the shelf (GOTS) software which include but are not limited to document management, collaboration, web content management, records management, search, dashboarding, and workflow commercial software products.
6.1.12 The contractor shall provide functional and non-functional testing support and assistance in the development of test plans, testing code, and reporting of test findings via the Serena TeamTrack or an equivalent configuration management tool. Testing requirements shall align with the Governments defined release schedule.
6.1.13 The contractor shall provide Knowledge and Records Management based training services through traditional classroom and computer based delivery methods to support training and outreach activities for DISA’s collaborative capabilities, content management solutions, and business intelligence capabilities. The contractor shall provide personnel whom are adept in public speaking, developing training plans and strategies, facilitating training, presentation development software, video teleconferencing, and synchronous collaboration tools to support this requirement.
6.1.14 The contractor shall provide personnel whom are skilled in the processes, procedures, and technologies that are associated with the support and maintenance of Federal and DoD Records Management programs, policies, and regulations (E.g. DoD Directive 5015.2). The contractor shall provide assistance in the development of file records management implementation plans, file plans, establishment of record retention schedules, decommissioning legacy records management applications, and integrating new records management applications with new and existing interfaces and capabilities.
6.1.15 The Contractor shall recommend policies, procedures, methodologies, and tools to be used by IT Service Area providers for DISA Knowledge Management objectives, and internal for collecting and defining user requirements for new, and changes to existing, systems and processes. The Contractor shall ensure that requirements definition and analysis cover the whole scope of a project life cycle and that the processes minimize the potential for incorrect, inaccurate, ambiguous, or excessive definition of requirements that result in schedule delays, wasted resources, and customer dissatisfaction, and that the appropriate review and approval procedures are in place and being used.
6.1.16 The contractor shall perform lifecycle configuration management activities in accordance with DISA configuration management policies and procedures. The contractor shall use DISA’s configuration management system (currently Serena TeamTrack) or equivalent software to record, track, monitor, and update all component configurations and subsequent component configuration changes. They shall manage, monitor, and update the configuration management system to include a logical model of the IT Service Areas’ devices and their relationships by identifying, controlling, maintaining and verifying software and documentation (i.e., maintenance contracts, SLA documents, etc.). The configuration management system shall provide accurate information on configurations and provide a sound basis for Incident, Problem, Change and Release Management and to verify configuration records against the infrastructure and correct any exceptions. The contractor shall monitor its personnel to ensure that they comply with the accurate and timely recording of all asset parameters as specified in configuration management requirements. The Contractor shall include a logical model of its service areas’ devices and their relationships by identifying, controlling, maintaining and verifying installed hardware, software, and documentation (i.e., maintenance contracts, OLA documents, SLA documents, etc.).
6.1.17 The contractor shall provide Software Configuration Management Services including the identification and maintenance of system components and the relationships and dependencies among them. The contractor shall perform the following activities in support of Software Configuration Management Services:
6.1.18 Capture and storage of application-to-component and component-to-component relationships
6.1.19 Maintenance of the history of those relationships and transformations required to appropriately manage and document (e.g., source control, version control, profiles, IA plans) configuration changes affecting the application and its processing environment
6.1.20 Record configuration items and applicable technical artifacts in the designated Configuration Management system to maintain the integrity of the products throughout the lifecycle
6.1.21 Create configuration baselines and periodically meet to review proposed baseline changes and adjudicate trouble reports prior to the submission of change request
6.1.22 Support the releases and associated changes to authorized baselines.
6.1.23 The contractor shall provide personnel whom are adept in programming logic and languages to operate and sustain the DISA Situational Awareness Table (SAT) application. The contractor shall also provide personnel whom are knowledgeable in decomissioning the application and leveraging the inherent capabilities and requirements within SharePoint 2010 or other similar COTS/GOTS products. All new development work outside the scope of operations and maintenance of the SAT application shall cease unless otherwise directed by CIO management.
6.1.24 The contractor shall provide personnel whom are adept in managing configuration changes, application customization, and operations and maintenance of SharePoint 2010, IBM FileNet P8, IBM Records Management, HP Trim, and OpenText COTS packages (E.g. Vignette Collab 7.1, Vignette Records and Documents 7.1) or equivalent. The contractor shall provide personnel whom are knowledgeable in decomissioning the Open Text solutions and leveraging the inherent capabilities and requirements within SharePoint 2010 or other similar COTS/GOTS products. Contractor personnel shall be knowledgeable in the methods for creating and modifying CTDs, ATDs, C-Spaces, and Templates. The contractor shall work with DISA personnel to create Workspaces and customized applications using Collab out-of-the-box objects either As-is or with minor configuration changes to meet specific requirements. The contractor shall work in coordination with the CIO development team, ensuring that all configuration management policies and procedures are followed in the creation of such workspaces and applications. All new development work with the exception of continued operations and maintance and those items denoted previously shall cease within the OpenText suite of tools unless otherwise directed by CIO management.
6.1.25 The Contractor shall develop/update and maintain security architecture and its documentation for the DISA MIS and Intranet Service in the context of the DISA Enterprise Architecture (EA). The security architecture shall validate the systems architecture for the services and capabilities in the Information Management Division to ensure adherence to the strategic goals and the target framework of the DISA and DoD Enterprise Architecture.
6.1.26 The contractor shall develop the As-is and To-be Knowledge Management Architecture and IT Enterprise diagrams and documents in accordance with DoDAF (e.g., OVs, SVs, TVs) principles. The architecture must be compliant with all applicable DoD and DISA policies and guidance. The contractor shall address the architecture plan in three areas; DISA enterprise security architecture planning for SSO, IDAM, DISA Enterprise Directory Service to include CMIS DB, DISANet Active Directory, LDAP, and other DISA MIS directories and other authoritative data sources; Information Sharing Architecture for DISA Enterprise Knowledge Management/Collaboration Portal and its integration with other DISA/DoD enterprise capabilities in order to more effectively share information across the DISA and DoD enterprise; and security architecture planning for Sharepoint and other MIS/Enterprise Services.
6.1.27 The contractor shall review the existing application security architecture strategies in place, document the current As-is architecture, and develop and document the To-be architecture.
6.1.28 The contractor shall maintain and update the security architecture interface control document for all DISA specific security interfaces that are designed. This document should act as an instruction manual for developers and system administrators to integrate web applications and/or web services with the deployed Intranet Security Service framework. If needed, the contractor shall assist in the proof-of-concept of any special web service interface modules to facilitate the integration of these external web components.
6.1.29 The contractor shall develop and maintain the DISA IDM Roadmap. The DISA IDM roadmap shall address DISA account management plan, delegated administration action plan, entitlement roadmap/action plan, DISAwide digital identity lifecycle management recommendation/ plan and directory federation plan with other DoD components.
6.1.30 The contractor shall develop the directory service architecture for the security architecture of DISA enterprise applications and systems. They shall review the current directory structures of IDAM, IDSS, and DoD EASF, and existing DISA portals/enterprise MIS applications and MIS enterprise applications. The contractor shall perform strategic technology assessments and evaluations, make recommendations, and document findings for evolution and migration of Agency MIS/portals/directories to integrate and automate DISA functions at the Agency level.
6.1.31 The contractor shall support requirements analysis, proof-of-concept, research and design of systems and security architecture components for the DISA Adoption of Enterprise Services (SharePoint 2010, it’s add-ons or equivalent future systems) including linkage and synchronization with Agency personnel directories and the DoD IDAM, IDSS, and the DoD EASF identity management architecture and any applications, systems, or other directories as identified by the government.
7. Place of Performance Primary Place of Performance The Contractor shall perform work in Government provided office space located in the DISA Headquarters campus located on Fort Meade, MD.
Alternate Place of Performance Contractor employees may be required to work at home, another approved DISA activity within the local travel area or at the contractor's facility in cases of unforeseen conditions or contingencies (e.g., pandemic conditions, exercises, etc.). Any equipment such as laptops or phones provided to Contractor personnel shall be returned at the termination of the engagement or at another time mutually agreeable to both parties. Contracting Officer Representative (COR)/Task Order COR (TO/COR) approval is required. Contractor shall prepare all deliverables and other contract documentation utilizing contractor resources. The contractor shall continue to provide the same level of support as stated in the PWS. In the event the services are impacted, reduced, compromised, etc., the Contracting Officer may request an equitable adjustment.
8. Travel Requirements Contractor travel is anticipated to support the requirements named in this document. The Contractor shall project anticipated travel in the quote, and obtain approval from the Customer prior to actual travel. The Contractor shall submit invoices for direct costs related to travel no later than 30 days following the end of travel. Travel, per diem, and other direct costs will be reimbursed in accordance with FAR 31.205-46.
9. Period of Performance The period of performance for this Task Order is twelve (12) months from date of award.
10. Delivery Schedule Due dates for all deliverables assocated with this Task Order are identified in the table below.
DELIVERABLES
| ITEM # |
| TASK NUMBER |
| TITLE |
| FORMAT |
| DUE DATE |
| # of COPIES |
| DISTRIBUTION |
| FREQUENCY and REMARKS |
| 1 |
| 6.a |
| Monthly Status Report |
| MS Word, IAW Contract requirements |
| Due on the 10th of the Month |
| 3 |
| Electronic copy to COR, Primary TO/COR, and Alternate TO/COR. |
| Monthly |
| 2 |
| 6.a |
| Briefings |
-Weekly Hot Topics
-Monthly IPR
| Government determined format |
| Ongoing during life of task order |
| 3 |
| 1 to Primary TO/COR, 1 to Requirements Lead, and 1 to Asst. Requirements Lead |
| As Requested |
| 3 |
| 6a |
| Maintenance of the Integrated Master Schedule (IMS) |
| MS Project |
| Bi-Monthly |
| N/A |
| Electronically presented at Bi Monthly Meetings |
| Bi-Monthly for Risk Management meetings |
| 4 |
| 6.a |
| DISA DAI Trip Report |
| MS Word |
| Within 5 day of return from travel |
| 3 |
| Electronic copy to COR, 1 to Primary TO/COR, 1 copy to the DISA Implementation Manager |
| Each trip |
| 5 |
| 6.a |
| DISA DAI Meeting Minutes |
| MS Word |
| Within 3 business days of meetings conclusion |
| 3 |
| Electronic copy to COR, one copy to Primary TO/COR, one copy to the Functional Team Lead |
| Per meeting / as requested |
| 6 |
| 6.a |
| Development and maintenance of Risk Management Strategy |
| Government specified format(s) |
| IAW the IMS |
| 3 |
| 1 to COR, 1 to Primary TO/COR, 1 to Requirements Lead |
| Ongoing during life of task order |
| 7 |
| 6.b |
| Requirements Management Monthly Status Report |
| MS Word, Contractor-Determined Format |
| Due on the 10th of the Month |
| 3 |
| 1 to COR,1 to Primary TO/COR, 1 to Requirements Management Lead |
| Monthly |
| 8 |
| 6.b |
| Blueprinting Sessions output / MD-50 input |
| Government defined format |
| IAW the IMS |
| 3 |
| 1 to Primary TO/COR, 1 copy to the Requirements Management Lead |
| As Requested |
| 9 |
| 6.6.3 |
| Staffing Plan of Action |
| Contractor Format |
| Standard Distribution |
| As necessary, 33 days after a vacancy is realized. (Three days after the 30-day fill requirement.) |
| 10 |
| 6.6.3 |
| Requirements Documents |
| Government Format |
| Standard Distribution |
| For new requirements, draft requirements document shall be provided within 30 days of assigned tasking; final requirements document shall be provided 15 days thereafter. Updates to existing requirements document must be approved by the Government TO/COR or representative |
| 11 |
| 6.6.3 |
| Test Plans |
| Government Format |
| Standard Distribution |
| Due one (1) business day prior to code freeze for each associated Problem Change Request (PCR) |
| 12 |
| 6.6.3 |
| Systems Analysis and Evaluation documents |
| Government Format |
| Standard Distribution |
| For new system analysis and evaluation, draft system analysis and evaluation document shall be provided within 15 days of assigned tasking; final requirements document shall be provided 15 days thereafter. Updates to existing system analysis and evaluation document must be approved by the Government TO/COR or representative. |
| 13 |
| 6.6.3 |
| Governance Documents (SharePoint 2010, KM COI Charter, DISA Enterprise Services Portal, IBM Filenet, HP Trim, OpenText) |
| Governemnt Format |
| Standard Distribution |
| Draft 90 days after TO award; final, 120 days after TO award; updated biannually |
| 13 |
| 6.6.3 |
| DISA Instruction: Enterprise Content Management |
| Government Format |
| Standard Distribution |
| Draft 90 days after TO award; final, 120 days after TO award |
| 14 |
| 6.6.3 |
| DISA Authoritative Source Content Framework |
| Government Format |
| Standard Distribution |
| Draft 90 days after TO award; final, 120 days after TO award; updated biannually |
| 15 |
| 6.6.3 |
| DISA Records Management Instruction |
| Government Format |
| Standard Distribution |
| Updated as changes to regulations impact; yearly updates at a minimum (MAY) |
| 16 |
| 6.6.3 |
| DISA Records Management File Plan |
| Government Format |
| Standard Distribution |
| Updated as new DISA Programs are developed or modifications are required for existing DISA Programs. |
| 17 |
| 6.6.3 |
| DISA Records Management Retention Schedule |
| Government Format |
| Standard Distribution |
| Updated as changes to regulations impact, new or existing DISA Programs. |
| 18 |
| 6.6.3 |
| DISA Records Management Implementation Plan |
| Government Format |
| Standard Distribution |
| Updated yearly (OCT) |
| 19 |
| 6.6.3 |
| DISA Privacy Instruction |
| Government Format |
| Standard Distribution |
| Updated as changes to regulations impact; yearly updates at a minimum (MAY) |
| 20 |
| 6.6.3 |
| Strategic Documents (Knowledge Management Strategy and Knowledge Management Implementation Plan) |
| Government Format |
Standard Distribution
| 21 |
| 6.6.3 |
| Best Practices Documents (Knowledge Management Standard Operating Procedures and Tactics, Techniques, and Procedures) |
| Government Format |
| Standard Distribution |
| For new best practices discovery, draft best practices document shall be provided within 15 days of assigned tasking; final best practices document shall be provided 15 days thereafter. Updates to existing best practices document must be approved by the Government TO/COR or representative. |
| 22 |
| 6.6.3 |
| Training Guides |
| Government Format |
| Standard Distribution |
| For new training material, draft plans shall be provided within 30 days of assigned tasking; final plans shall be provided 30 days thereafter. Updates to existing training material must be approved by the Government TO/COR. |
| 23 |
| 6.6.3 |
| Training Materials (Training Plans, Lesson Plans, CBT’s, and Curricula) |
| Government Format |
| Standard Distribution |
| For new training material, draft plans shall be provided within 30 days of assigned tasking; final plans shall be provided 30 days thereafter. Updates to existing training material must be approved by the Government TO/COR. |
| 24 |
| 6.6.3 |
| Triage Management Repository |
| Government Format |
| Standard Distribution |
| 30 days after TO award |
| 25 |
| 6.6.3 |
| User Guides |
| Government Format |
| Standard Distribution |
| For new user information, draft user guides shall be provided within 10 days of assigned tasking; final user guides shall be provided 10 days thereafter. Updates to existing user guides must be approved by the Government TO/COR or representative. |
| 26 |
| 6.6.3 |
| Capability Marketing Plans |
| Government Format |
| Standard Distribution |
| For new capability marketing plans, draft capability marketing plans shall be provided within 10 days of assigned tasking; final capability marketing plans shall be provided 10 days thereafter. Updates to existing capability marketing plans must be approved by the Government TO/COR or representative. |
| 27 |
| 6.6.3 |
| Marketing Articles |
| Government Format |
| Standard Distribution |
| For new marketing articles, draft marketing articles shall be provided within 5 days of assigned tasking; final marketing articles shall be provided 5 days thereafter. Updates to existing marketing articles must be approved by the Government TO/COR or representative. |
| 28 |
| 6.6.3 |
| SAT software code version upgrades and SAT database schema modifications |
| Contractor Format |
| Standard Distribution |
| SAT software code version upgrades and database schema modifications shall be provided 5 business days prior to software release. All SAT software code version upgrades and database schema changes not provided 5 business days prior to a software release must be approved by the Government TO/COR or representative. |
| 29 |
| 6.6.3 |
| VBCS software configurations and VBCS software modification documents |
| Contractor Format |
| Standard Distribution |
| VBCS software configurations and modifications shall be provided 5 business days prior to software release. All VBCS software configurations and modifications not provided 5 business days prior to a software release must be approved by the Government TO/COR or representative. |
| 30 |
| 6.6.3 |
| Microsoft SharePoint Software Configurations and Microsoft SharePoint Software Modification Documents |
| Contractor Format |
| Standard Distribution |
| Microsoft SharePoint software configurations and modifications shall be provided 5 business days prior to software release. All Microsoft SharePoint software configurations and modifications not provided 5 business days prior to a software release must be approved by the Government TO/COR or representative. |
| 31 |
| 6.6.3 |
| Non-Disclosure Agreements (NDAs) |
| Government format to be provided |
| Standard Distribution |
| Within 15 days of contractor personnel working on the task |
| 32 |
| 6.6.3 |
| Interface Document |
| Government format to be provided |
| Standard Distribution |
| Within 60 days of contractor personnel working on the task |
| 33 |
| 6.6.3 |
| Information Security Architecture Document |
| Government format to be provided |
| Standard Distribution |
| Within 120 days of contractor personnel working on the task |
| 34 |
| 6.6.3 |
| IDM Roadmap Document |
| Government format to be provided |
| Standard Distribution |
| Within 45 days of contractor personnel working on the task |
11. Service Level Agreements and Performance Metrics
SERVICE LEVEL AGREEMENTS AND PERFORMANCE METRICS
| ITEM # |
| TASK NUMBER |
| TITLE |
| PERFORMANCE STANDARD |
| ACCEPTABLE QUALITY LEVEL (AQL) |
| PERFORMANCE MEASUREMENT/MONITORING METHOD |
| INCENTIVE/DISINCENTIVE FOR MEETING/NOT MEETING AQL |
| 1 |
| 6.a |
| Monthly Status Report |
| The contractor shall provide the Monthly Status Report by the 15th day of each month for the duration of the task. (1st report due within 45 days of contract award) |
| 98% |
| 100% review of document prior to Government acceptance. |
| Positive or Negative documentation reported to past performance database (CPARS) |
| 2 |
| 6.a |
| Briefings |
-Weekly Hot Topics
-Monthly IPR
| The contractor shall provide meetings by the 15th of the month progress of tasks, address open risks and issues, and discuss the focus of future activities. For the duration of this task. (1st report due within 60 days of contract award) |
| 98% |
| 100% review of document prior to Government acceptance. |
| Positive or Negative documentation reported to past performance database (CPARS) |
| 3 |
| 6a |
| Maintenance of the Integrated Master Schedule (IMS) |
| The contractor shall provide Master Schedule Updates weekly. (1st schedule update due within 5 days, and weekly updates to be provided as new information becomes available, with at least one complete update due every Monday by 1200 EST) |
| 98% |
| Weekly review of Master Schedule, Action Tracking & Project Planning and Review Meetings. |
| Positive or Negative documentation reported to past performance database (CPARS) |
| 6 |
| 6.a |
| Development and maintenance of Risk Management Strategy |
| The contractor shall provide an on-going risk management concurrent with the analysis and evaluation tasks identified in the Master Schedule and Program Management Plan |
| 98% |
| 100% review of document prior to Government acceptance. |
| Positive or Negative documentation reported to past performance database (CPARS) |
| 7 |
| 6.b |
| Requirements Management Monthly Status Report |
| The contractor shall provide requirements documentation on-going. Concurrent with the requirements tasks identified in the Master Schedule. |
| 98% |
| 100% review of document prior to Government acceptance. |
| Positive or Negative documentation reported to past performance database (CPARS) |
| 9 |
| 6.6.3 |
| Staffing Plan of Action |
| The contractor shall provide a staffing plan of action should a vacancy remain unfilled for more than 30 days. |
| 99% |
| 100% review of document prior to Government acceptance. |
| Positive or Negative documentation reported to past performance database (CPARS) |
| 10 |
| 6.6.3 |
| Requirements Documents |
| The contractor shall provide requirements documentation on-going. Concurrent with the requirements tasks identified in the Master Schedule. |
| 98% |
| 100% review of document prior to Government acceptance. |
| Positive or Negative documentation reported to past performance database (CPARS) |
| 11 |
| 6.6.3 |
| Test Plans |
| The contractor shall provide Test Plan for each PCR 1 business day prior to code freeze |
| 98% |
| 100% review of input 1 business day prior to code freeze for a scheduled release. |
| Positive or Negative documentation reported to past performance database (CPARS) |
| 12 |
| 6.6.3 |
| Systems Analysis and Evaluation documents |
| The contractor shall provide systems analysis and evaluation documentation on-going. Concurrent with the analysis and evaluation tasks identified in the Master Schedule. |
| 98% |
| 100% review of document prior to Government acceptance. |
| Positive or Negative documentation reported to past performance database (CPARS) |
| 13 |
| 6.6.3 |
| Governance Documents (SharePoint 2010, KM COI Charter, DISA Enterprise Services Portal, IBM Filenet, HP Trim, OpenText) |
| The contractor shall provide updates to the DISA Governance Documents annually (concurrent with the month of publication of the Instruction), or as changes are required. |
| 98% |
| 100% review of document prior to Government acceptance. |
| Positive or Negative documentation reported to past performance database (CPARS) |
| 13 |
| 6.6.3 |
| DISA Instruction: Enterprise Content Management |
| The contractor shall provide updates to the DISA Instruction annually (concurrent with the month of publication of the Instruction), or as changes are required. |
| 98% |
| 100% review of document prior to Government acceptance. |
| Positive or Negative documentation reported to past performance database (CPARS) |
| 14 |
| 6.6.3 |
| DISA Authoritative Source Content Framework |
| The contractor shall provide updates to the DISA Authoritative Source Content Framework annually (concurrent with the month of publication of the Instruction), or as changes are required. |
| 98% |
| 100% review of document prior to Government acceptance. |
| Positive or Negative documentation reported to past performance database (CPARS) |
| 15 |
| 6.6.3 |
| DISA Records Management Instruction |
| The contractor shall provide updates to the DISA Instruction annually (concurrent with the month of publication of the Instruction), or as changes are required. |
| 98% |
| 100% review of document prior to Government acceptance. |
| Positive or Negative documentation reported to past performance database (CPARS) |
| 16 |
| 6.6.3 |
| DISA Records Management File Plan |
| The contractor shall provide DISA RM documentation on-going. Concurrent with the RM documentation tasks identified in the Master Schedule. |
| 98% |
| 100% review of document prior to Government acceptance. |
| Standard Distribution |
| 17 |
| 6.6.3 |
| DISA Records Management Retention Schedule |
| The contractor shall provide DISA RM documentation on-going. Concurrent with the RM documentation tasks identified in the Master Schedule. |
| 98% |
| 100% review of document prior to Government acceptance. |
| Positive or Negative documentation reported to past performance database (CPARS) |
| 18 |
| 6.6.3 |
| DISA Records Management Implementation Plan |
| The contractor shall provide DISA RM documentation on-going. Concurrent with the RM documentation tasks identified in the Master Schedule. |
| 98% |
| 100% review of document prior to Government acceptance. |
| Standard Distribution |
| 19 |
| 6.6.3 |
| DISA Privacy Instruction |
| The contractor shall provide updates to the DISA Instruction annually (concurrent with the month of publication of the Instruction), or as changes are required. |
| 98% |
| 100% review of document prior to Government acceptance. |
| Positive or Negative documentation reported to past performance database (CPARS) |
| 20 |
| 6.6.3 |
| Strategic Documents (Knowledge Management Strategy and Knowledge Management Implementation Plan) |
| The contractor shall provide updates to the DISA Strategic Documentation annually (concurrent with the month of publication of the Instruction), or as changes are required. |
| 98% |
| 100% review of document prior to Government acceptance. |
| Positive or Negative documentation reported to past performance database (CPARS) |
| 14 |
| 6.6.3 |
| Best Practices Documents (Knowledge Management Standard Operating Procedures and Tactics, Techniques, and Procedures) |
| The contractor shall provide best practices documentation on-going. Concurrent with the training and marketing tasks identified in the Master Schedule. |
| 98% |
| 100% review of document prior to Government acceptance. |
| Positive or Negative documentation reported to past performance database (CPARS) |
| 15 |
| 6.6.3 |
| Training Guides |
| The contractor shall provide training guides on-going. Concurrent with the training and marketing tasks identified in the Master Schedule. |
| 98% |
| 100% review of document prior to Government acceptance. |
| Positive or Negative documentation reported to past performance database (CPARS) |
| 16 |
| 6.6.3 |
| Training Materials (Training Plans, Lesson Plans, CBT’s, and Curricula) |
| The contractor shall provide live and recorded training on-going. Concurrent with the training tasks identified in the Master Schedule. |
| 98% |
| 100% review of training material (and scripts) prior to Government acceptance. |
| Positive or Negative documentation reported to past performance database (CPARS) |
| 17 |
| 6.6.3 |
| Triage Management Repository |
| The contractor shall maintain the Triage Management Repository on a daily basis, or as requests are received and acted upon (whichever is more frequent). |
| 98% |
| 100% review of updates prior to Government acceptance. |
| Positive or Negative documentation reported to past performance database (CPARS) |
| 18 |
| 6.6.3 |
| User Guides |
| The contractor shall provide user guides on-going. Concurrent with the training tasks identified in the Master Schedule. |
| 98% |
| 100% review of document prior to Government acceptance. |
| Positive or Negative documentation reported to past performance database (CPARS) |
| 19 |
| 6.6.3 |
| Capability Marketing Plans |
| The contractor shall provide Capability Marketing Plans on-going. Concurrent with the marketing tasks identified in the Master Schedule. |
| 98% |
| 100% review of document prior to Government acceptance. |
| Positive or Negative documentation reported to past performance database (CPARS) |
| 20 |
| 6.6.3 |
| Marketing Articles |
| The contractor shall provide Marketing Articles on-going. Concurrent with the marketing tasks identified in the Master Schedule. |
| 98% |
| 100% review of document prior to Government acceptance. |
| Positive or Negative documentation reported to past performance database (CPARS) |
| 21 |
| 6.6.3 |
| SAT software code version upgrades and SAT database schema modifications |
| The contractor shall provide upgrades and schema modifications on-going. Concurrent with the development and integration tasks as defined through PCRs and the Master Schedule. |
| 98% |
| 100% review of product prior to Government acceptance. |
| Positive or Negative documentation reported to past performance database (CPARS) |
| 22 |
| 6.6.3 |
| VBCS software configurations and VBCS software modification documents |
| The contractor shall provide configuration and software modification documentation on-going. Concurrent with the development and integration tasks as defined through PCRs and the Master Schedule. |
| 98% |
| 100% review of product prior to Government acceptance. |
| Positive or Negative documentation reported to past performance database (CPARS) |
| 23 |
| 6.6.3 |
| Microsoft SharePoint Software Configurations and Microsoft SharePoint Software Modification Documents |
| The contractor shall provide configuration and software modification documentation on-going. Concurrent with the development and integration tasks as defined through PCRs and the Master Schedule. |
| 98% |
| 100% review of product prior to Government acceptance. |
| Positive or Negative documentation reported to past performance database (CPARS) |
| 25 |
| 6.6.3 |
| Interface Document |
| The contractor shall provide Interface documentation. Once the baseline document is established, the document is to be maintained concurrent with the development and integration tasks as defined through PCRs and the Master Schedule. |
| 98% |
| 100% review of product prior to Government acceptance. |
| Positive or Negative documentation reported to past performance database (CPARS) |
| 26 |
| 6.6.3 |
| Information Security Architecture Document |
| The contractor shall provide Information Security Architecture documentation. Once the baseline document is established, the document is to be maintained concurrent with the development and integration tasks as defined through PCRs and the Master Schedule. |
| 98% |
| 100% review of product prior to Government acceptance. |
| Positive or Negative documentation reported to past performance database (CPARS) |
| 27 |
| 6.6.3 |
| IDM Roadmap Document |
| The contractor shall provide IDM Roadmap documentation. Once the baseline document is established, the document is to be maintained concurrent with the development and integration tasks as defined through PCRs and the Master Schedule. |
| 98% |
| 100% review of product prior to Government acceptance. |
| Positive or Negative documentation reported to past performance database (CPARS) |
| 28 |
| 6.6.3 |
| Non-Disclosure Agreements (NDAs) |
| The contractor shall provide NDAs within 15 days of contractor personnel working on the task |
| 100% |
| 100% review of document prior to Government acceptance. |
| Positive or Negative documentation reported to past performance database (CPARS) |
12. Security Requirements The work to be performed under this contract is up to and including the Secret level and positions are IT-II for systems access. All personnel performing services under this contract will be designated ADP Sensitivity Level II (ADP-II), and will have a favorably completed National Agency Check (NAC), or an Interim Secret clearance prior to performance.
The Contractor will forward a Visit Authorization Letter (VAL) to the Primary Task Order COR listed at beginning of this SOW for all employees prior to the beginning of each contracting/task order period of performance and as new contractor employees are assigned to the contract:
The VAR/VAL
12.1.1 Method One:
Per direction of DISA Security and the Chief of Security for Computing Services Operations, Visit Authorization Letters (VALs) or Visit Requests (VARs) for contract personnel that will be working for Computing Services either on- or off-site will be forwarded via Joint Personnel Adjudication System (JPAS) to the VAR Center using the following SMO Code: DKABAA10.
For those companies submitting the VALs via JPAS, they will also provide a copy of the VALs to the Task Order CORs of the contract for creation of records in the Contractor Verification System (CVS) so that Common Access Cards can be obtained for the contractors that require them.
12.1.2 Method Two:
For those companies that do not have the capability to send VALs via JPAS, they can send the VALs via e-mail to the Task Order CORs. Due to Privacy Act concerns, the VALs will be e-mailed as a password protected “WinZip” attachment, followed up by a second e-mail containing the password for the first e-mail.
The VAR/VAL shall be on company letterhead or pre-fabricated form and contain the following information:
· Contract number with start and end dates
· Company point of contact (POC) and telephone number
· Government Task Order COR name and telephone number
· Complete legal name of employee(s)
· Social Security Number
· Security Clearance level, date granted, and
· Adjudication facility name, i.e. DISCO
· Type of personnel security investigation (PSI) pending or completed
· Date PSI completed
DISA Security Personnel can be contacted for security related questions as follows:
For Industrial Security related issues:
Primary: Ms. Jane A. Doe, phone: (301) 225-XXX
Alternate: Mr. John A. Doe, phone: (301) 225-XXXX
Defense Information Systems Agency
ATTN: MPS61, Industrial Security
DISA HQ Complex (Command Bldg)
6910 Cooper Ave
Fort Meade, MD, 20755
For Personnel Security related issues to include interim IT access requests:
Primary: Ms Jane A. Doe, phone: (301) 225-XXXX
Alternate: Mr. John A. Doe, phone: (301) 225-XXXX
Defense Information Systems Agency
ATTN: MPS62, Personnel Security
DISA HQ Complex (Command Bldg)
6910 Cooper Ave
Fort Meade, MD, 20755
Contractor personnel must comply with local security requirements for entry and exit control for personnel and property at the government facility.
Contractor employees will be required to comply with all Government security regulations and requirements. Initial and periodic security training and briefings will be provided by Government security personnel. Failure to comply with security requirements can be cause for termination of employment.
The Contractor shall not divulge any information about DoD files, data processing activities or functions, user identifications, passwords, or any other knowledge that may be gained, to anyone who is not authorized to have access to such information. The Contractor shall observe and comply with the security provisions in effect at the DoD facility. Identification shall be worn and displayed as required.
DISA retains the right to request removal of contractor personnel regardless of prior clearance or adjudication status, whose actions, while assigned to this contract, clearly conflict with the interest of the Government. The reason for removal will be fully documented in writing by the Contracting Officer (CO). When and if such removal occurs, the contractor shall, within 15 working days, fill the vacancy with equally or more qualified personnel than the individual dismissed.
The Privacy Act of 1974 applies. The contractor may be required to have access to highly sensitive and proprietary information for the performance of this Task Order. The contractor will not divulge any information about data processing activities or functions, or any other knowledge that may be gained, to anyone who is not authorized to have access to such information. The contractor will observe and comply with the security provisions in effect at computer centers. Any required identification badges will be worn and displayed at all times. A Department of Defense Contract Security Classification Specification, Form DD 254, must be completed. A DISA Non-Discloser Agreement (NDA) must be completed by each employee. NDA is attached as Appendix One.
13. Government-Furnished Equipment (GFE)/Government-Furnished Information (GFI) Access/GFE
DISA will provide the Contractor access to the applicable Local Area Network(s), Personal Computer(s) necessary to accomplish the work tasked under this task order. The Contractor, in coordination with the Customer, will be responsible for obtaining appropriate approvals for access. Non-DISA site access requirements will be the sole responsibility of the Contractor.
GFI
A listing of GFI to be provided after contract award is included as Appendix Two. As new GFI is made available or current GFI is updated it will be provided.
14. Other Pertinent Information or Special Considerations
Identification of Potential Conflicts of Interest (COI).
The DAI system has been selected. The contractor providing support on the DISA DESS Contract will not be helping to establish requirements for this system; however, a contractor may already be supporting DISA in a capacity that may create an actual or potential conflict of interest with respect to the effort described in this PWS. Should that be the case, such a contractor must identify any actual or potential organizational conflict of interest and its plan for avoiding, neutralizing or mitigating such conflicts.
Identification of Non-Disclosure Requirements.
The contractor must identify any sensitive or proprietary information to which the contractor will have access during Task Order (TO) execution so any non-disclosure agreements can be signed by the time the TO is awarded.
Inspection and…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .