Att__1_LCMS_PWS_7-2-13_FINAL.docx
DOCX document 226 KB Posted
- Attached to
- Learning Content Management System Federal contract opportunity
- Solicitation number
- HSFE20-13-Q-0058
About this file
Attachment 1 - Performance Work Statement
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| HSFE20-13-Q-0058_A00005_Att__1_LCMS_PWS_8-8-13.docx | DOCX document | |
| HSFE20-13-Q-0058_A00004_Att_1_LCMS_PWS_8-6-13.docx | DOCX document | |
| HSFE20-13-Q-0058_A00002_Q A.docx | DOCX document | |
| HSFE20-13-Q-0058_A00002_Att__1_LCMS_PWS_7-25-13.docx | DOCX document | |
| Att__2_CDP_649-1-00_Visitor_Access_to_CDP_Facilities.pdf | ||
| Att__3_CDP_256-1-00_Workplace_Attire.pdf | ||
| HSFE20-13-Q-0058_Combined_Synopsis_Solicitation.doc | DOC document |
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
PERFORMANCE WORK STATEMENT CDP LEARNING CONTENT MANAGEMENT SYSTEM (LCMS)
Center for Domestic Preparedness Federal Emergency Management Agency Department of Homeland Security
Attachment 1
July 2, 2013
Table of Contents
| 1.0 GENERAL | 1 |
| 1.1 Scope | 1 |
| 1.2 Background | 1 |
| 1.3 Contractor Personnel | 1 |
| 1.4 Security, Privacy, Safety and Proprietary Data | 2 |
| 1.5 Period of Performance | 3 |
| 1.7 Kick-Off Meeting | 3 |
| 1.8 Progress Meetings | 3 |
| 1.9 General Report Requirements | 4 |
| 1.10 General Information | 4 |
2.0 GOVERNMENT DEFINITIONS………………………………………………………
2.1 Definitions…………………………………………………………………………….….4
2.2 Agency Acronyms
| 3.0 MANAGEMENT RESPONSIBILITIES | 7 |
| 3.1 Quality Control | 7 |
| 3.2 Contractor Project Manager Responsibilities | 7 |
| 4.0 contractor tasks | 9 |
| 4.1 LCMS – Requirements and Specifications | 9 |
| 4.2 Deliverables | 14 |
| 4.3 Schedule of Deliverables | 15 |
PERFORMANCE WORK STATEMENT: CDP Learning Content Management System
Page | i
1.0 GENERAL
1.1 Scope
The intention of this requirement is the acquisition of a Learning Content Management System (LCMS) and services to support the U.S. Department of Homeland Security (DHS)/Federal Emergency Management Agency (FEMA)/National Preparedness Directorate/National Training and Education Directorate (NTED)/Center for Domestic Preparedness (CDP) located in Anniston, Alabama. The contractor shall provide all services as identified in this performance work statement. The Government intends to achieve its goal of an enterprise-wide FEMA LCMS through an incremental acquisition of content authoring licenses and accompanying training, support and maintenance, a process that will initiate at the CDP. The FEMA Emergency Management Institute (EMI) and NTED will purchase content authoring licenses and associated support as an incremental acquisition under this contract. The CDP develops and delivers specialized, advanced hands-on training for emergency response providers from state, local, and tribal governments; and, when appropriate, the Federal Government, foreign governments, and private entities. The objective of this procurement is to obtain reliable, efficient and effective services by applying a sound management and technical approach that will provide the best value and meet the objectives described in this work statement.
Performance of work shall be conducted within CDP, located on the former Fort McClellan property in Anniston, AL. and contractor’s location.
1.2 Background
The CDP is a federal entity (a component of the Department of Homeland Security). On March 1, 2003 CDP transitioned from the Department of Justice (DOJ) to the Department of Homeland Security (DHS). CDP was subsequently included in the new DHS Preparedness Directorate. Enactment of the Post-Katrina Emergency Management Reform Act (PKEMRA) on April 1, 2007 resulted in the realignment of most of the DHS Preparedness Directorate functions to FEMA. FEMA established the National Preparedness Directorate (NPD) and aligned many of the former DHS Preparedness Directorate functions into the NPD including the CDP.
The CDP is a national training facility located in Anniston, Alabama that prepares state, local and tribal emergency response personnel to respond to all hazards, including terrorist attacks using weapons of mass destruction, by providing advanced, hands on training. This national training program was developed for state, local, tribal, Federal, private sector and international responders from Fire Service, Law Enforcement, Emergency Medical Services, Emergency Management, HazMat, Public Health, Healthcare, Public Communications, Public Works and Government Administrative and other emergency response personnel, their trainers and supervisors. Training courses provided by the CDP provide specific knowledge and expertise for deterrence, prevention, response, mitigation and recovery to Chemical, Biological, Radiological, Nuclear and Explosive (CBRNE) incidents; mass casualty incidents; and incidents involving hazardous materials by providing advanced, hands-on and classroom-based state of the art training.
1.3 Contractor Personnel
1.3.1 Qualified Personnel. The contractor shall provide qualified personnel to perform all requirements specified in this PWS. All contractor employees supporting this contract shall be citizens of the United States (international exceptions must receive a favorable DHS suitability determination prior to hiring action). Prior to assignment to the contract, the contractor shall submit a current résumé for all management and other key personnel if different from those personnel identified in the proposal. Any replacement of key personnel shall be subject to the Contracting Officer’s approval in accordance with the clause HSAR 3052.215-70, Key Personnel or Facilities.
1.3.2 Contractor Certifications and Specific Experience Requirements. Contractor employees shall possess the education, experience, and skills necessary to complete the requirements with or without certifications. Certifications provide credence to skills possessed and are desired, but do not automatically indicate a person’s ability to perform the given tasks. The contractor shall provide personnel that have the appropriate experience and skill level for the position assigned.
1.3.3 Contractor Identification. Contractor personnel working on-site at Government facilities shall wear a Government issued identification badge. All contractor personnel shall identify themselves as contractors when their status is not readily apparent and display the Government issued badge in plain view above the waist at all times.
1.3.3.1 Visitors. Contractor-authorized personnel visiting Government facilities must coordinate their visit with the COR to obtain appropriate visitor access (Attachment 2, CDP Visitor Access Directive). Visiting personnel will be issued a temporary visitor badge that must be worn at all times while on CDP property. Visiting contractor personnel shall comply with all Government escort rules and requirements.
1.3.4 Contractor Personnel Conduct. Contractor’s employees shall comply with applicable Government regulations, policies and procedures (e.g., fire, safety, emergency response, sanitation, environmental protection, security, “off limits” areas, wearing of parts of military uniforms, possession of drugs and possession of weapons) when visiting or working at Government facilities.
1.3.5 Dress Code. All contractor personnel shall adhere to the CDP Workplace Attire Directive or subsequent document, Attachment 3.
1.3.6 Removing Contractor Personnel for Misconduct or Security Reasons. The Government may, at its sole discretion, direct the contractor to remove any contractor employee from CDP facilities for misconduct or security reasons. Removal does not relieve the contractor of the responsibility to continue providing the services required under any task order awarded. The COR will provide the contractor with a written explanation to support any request to remove any employee.
1.4 Security, Privacy, Safety and Proprietary Data
1.4.1 Security Clearance: Unclassified
1.4.2 Privacy Act. This agreement may require the contractor personnel to safeguard data in accordance with the Privacy Act (5 USC 522a). Contractor personnel shall safeguard any documents containing Personally Identifiable Information (PII) or Sensitive PII.
1.4.3 Contractor User Security Agreement. The contractor acknowledges that during the term of this requirement, all contractor employees may be required to sign some form of Contractor User Security Agreement. The contractor agrees to have all contractor employees sign the agreement. Contractor employees may be required to complete DHS, FEMA and/or CDP security specific training as directed by the Government.
1.4.4 Proprietary Data. In the performance of services under this agreement, the contractor employees may perform operations on data containing sensitive proprietary information. All inquiries regarding operation systems, data base controls and contents, passwords or other matters shall be referred to the COR for approval of access and use of the data.
1.5 Period of Performance
The period of performance shall be as listed below. The total performance period inclusive of options is five years.
Base Period: 12 Months Option 1: 12 Months Option 2: 12 Months Option 3: 12 Months Option 4: 12 Months
1.5.1 Phase-out/Contract Closeout
The contractor shall establish and implement plans for an orderly phase-out of the contracted operations at the termination of this contract. The contractor shall submit a Phase-out Plan to the CO and COR for evaluation 60 days prior to the last day of the contract. The contractor's phase-out procedures shall not disrupt or adversely impact the day-to-day conduct of Government business.
1.6 Place of Performance
The primary place of performance shall be at the contractor’s location and the CDP located in Anniston, Alabama.
1.7 Kick-Off Meeting
The Contractor shall attend a Kick-Off Meeting with the Contracting Officer and the COR at a date to be determined. The purpose of the Kick-Off Meeting, which will be chaired by the Contracting Officer, is to discuss technical and contracting objectives of this contract and review the Contractor’s draft project management plan. The Kick-Off Meeting will be held at the Government’s facility.
1.8 Progress Meetings
The Project Manager shall be available telephonically to discuss progress, exchange information and resolve emergent technical problems and issues with the COR.
1.9 General Report Requirements
The contractor shall provide all written reports in electronic format using applications that are compatible with CDP Standard Workstation (Windows and Microsoft Office Applications). In accordance with the Paperwork Reduction Act of 1980 (44 U.S.C. § 3501) contractor and the Government will make every effort to reduce forms and reports in support of CDP training.
1.10 General Information
Workmanship. All workmanship shall meet or exceed the standards specified herein and shall be accomplished in conformance with approved and accepted standards of the industry, Federal, State and local standards.
2.0 GOVERNMENT DEFINITIONS
2.1 Definitions
Where “as shown,” “as indicated,” “as detailed” or words of similar import are used, it shall be understood that reference is made to this specification and any drawings accompanying this specification unless stated otherwise.
Where “as directed,” “as required,” “as permitted,” “approval,” “acceptance,” or words of similar import are used, it shall be understood that direction, requirement, permission, approval, or acceptance by the Contracting Officer/Contracting Officer Technical Representative is intended unless stated otherwise.
Contract Discrepancy: A failure of the contractor to perform in accordance with contract requirements and specifications. A contract discrepancy may result from a failure of the contractor to provide, or provide on time, the required contract products or services, or it may result because delivered products or services did not meet specified contract standards.
Contract Discrepancy Notice: A formal, written documentation of contractor nonconformance or lack of performance for contracted work.
Contract Discrepancy Response: A response that the contractor is required to make when notified by a Contract Discrepancy Notice that performance is unsatisfactory.
Contract Non-Compliance: A failure of the contractor to perform in accordance with contract requirements and specifications. A contract discrepancy may result from a failure of the contractor to provide, or provide on time, the required contract products or services, or it may result because delivered products or services did not meet specified contract standards.
Contracting Officer (CO). The Contracting Officer is a person with the authority to enter into, administer, and/or terminate contracts and make related determinations and findings.
Contracting Officer’s Representative (COR). A person appointed by the Contracting Officer to monitor performance, evaluate work, provide technical direction and inspect and accept completed work for the Government.
Contractor. The term contractor as used herein refers to both the prime contractor and any subcontractors. The prime contractor shall ensure that his/her subcontractors comply with the provisions of this contract.
Contractor Representative. A foreman, supervisor, or key personnel who have been given the authority, by the contractor, to act on his/her behalf.
Corrective Action Request (CAR). A request issued by the COR or Quality Assurance Evaluators to the contractor when performance is unsatisfactory. The CAR requires the contractor to explain, in writing and within five (5) days, why performance is unsatisfactory, how performance will be returned to satisfactory levels, and how reoccurrence of the problem will be prevented in the future.
Federal Acquisition Regulations (FAR): Regulations pertaining to all Federal Government contracting procedures.
Fiscal Year: A period of 12 months beginning October 1 and ending September 30 of the following year. The fiscal year is designated by the calendar year in which it ends.
Frequency of Service:
Annual (A). Services performed once during each 12-month period of the contract at intervals of 345 to 385 days.
Semi-Annual (SA). Services performed twice during each 12-month period of the contract at intervals of 160 to 200 calendar days.
Quarterly (Q). Services performed 4 times during each 12-month period of the contract at intervals of 80 to 100 calendar days.
Monthly (M). Services performed 12 times during each 12-month period of the contract at intervals of 28 to 31 calendar days.
Weekly (W). Services performed 52 times during each 12-month period of the contract at intervals of 6 to 9 calendar days.
Future Courses: Future courses shall be delivered based on identified national training needs to support emergency responders involved in all hazards incidents or the improvement/conversion of existing courses. These new courses shall be in concert with the five domains for the National Response Framework. They shall vary from 16 – 40 contact hours in duration and may be direct, indirect, or technology based deliveries.
Government: The term Government as used herein includes the Contracting Officer and COR.
Personally Identifiable Information (PII). Examples of PII per the FEMA privacy office include: name, date of birth, mailing address, telephone number, email address, zip code, FEMA Student Identification Number Database (SID), certificate/license numbers, vehicle identifiers including license plates, uniform resource locators (URLs), Internet protocol addresses, photographic facial images, or any other unique identifying number or characteristic.
Plan of Instruction (POI). The curriculum design document that provides a general description of course content, learning objectives, duration of instruction, and methods and techniques of instruction.
Qualified Personnel. "Qualified" is defined here to mean having the requisite educational and work experience that can reasonably be expected to enable the person to perform satisfactorily under this contract.
Quality Assurance (QA). A method used by the Government to provide some measure of control over the quality of purchased goods and services received.
Quality Assurance Evaluator (QAE). An individual, who is appointed by the Contracting Officer, responsible for conducting contracting evaluations to ensure contract standards are achieved.
Quality Control. Those management functions including, but not limited to, training, procedures, inspections, and tests necessary to ensure that contractor products and services conform to contract requirements, specifications and standards.
Sensitive Personally Identifiable Information (SPII). Examples of SPII per the FEMA privacy office include: Social Security Number; driver’s license numbers; biometric identifiers (e.g., fingerprints); financial account number; citizenship or immigration status; medical information; ethnic, religious, sexual orientation or lifestyle information; performance ratings, drug test results and the fact of participation in rehabilitation programs; and account passwords in conjunction with the identity of an individual.
2.2 Agency Acronyms
AFC: Alabama Fire College AICC: Aviation Industry CBT [Computer-Based Training] Committee ARTC: Advanced Responder Training Complex CAP: Contractor Acquired Property CAR: Corrective Action Request CBRNE: Chemical, Biological, Radiological, Nuclear, Explosive CDAA: Calendar Days After Award CDP: Center for Domestic Preparedness CLIN: Contract Line Item Number CO: Contracting Officer COB: Close of Business COBRATF: Chemical Ordinance Biological Radiological Training Facility COR: Contracting Officer’s Representative COTS: Commercial Off-The-Shelf CTAS: CDP Training Administration System CSS: Cascading Style Sheets DB: Database Programming DHS: Department of Homeland Security DOJ: Department of Justice EAS: Electronic Archival System EMI: Emergency Management Agency EOP: Emergency Operation Plan ERP: Emergency Response Plan FAR: Federal Acquisition Regulation FedRAMP: Federal Risk and Authorization Management Program FEMA: Federal Emergency Management Agency FEMA SID: FEMA Student Identification Number Database FISMA: Federal Information Security Management Act FTR: Federal Travel Regulation FY: Fiscal Year GFP: Government Furnished Property GOCO: Government Owned Contractor Operated GPA: Government Property Administrator GSA: General Services Administration IACET: International Association for Continuing Education and Training IAW: In Accordance With ISD: Instructional System Design LCMS: Learning Content Management System LMS: Learning Management System LRC: Learning Resource Center NIMS: National Incident Management System NLT: No Later Than NMT: No More Than NPD: National Preparedness Directorate NRF: National Response Framework NTF: Noble Training Facility NTED: National Training and Education Directorate PA: Performance Area PII: Personally Identifiable Information PKEMRA: Post-Katrina Emergency Management Reform Act PWS: Performance Work Statement QA: Quality Assurance QAE: Quality Assurance Evaluator SBU: Sensitive But Unclassified SCORM: Sharable Content Object Reference Models SPII: Sensitive Personally Identifiable Information TSP: Training Support Package
3.0 MANAGEMENT RESPONSIBILITIES
The contractor shall manage the total work effort associated with delivery support required herein to assure adequate and timely completion of these services. Included in this function shall be a full range of management duties including, but not limited to, planning, resourcing, scheduling, and quality control.
3.1 Quality Control. The contractor shall be responsible for the quality of products and services provided under the terms of this contract, to include those provided by subcontractors.
3.2 Contractor Project Manager Responsibilities
3.2.1 The contractor shall designate a Project Manager as part of the proposal, to include qualifications and resume. This individual shall be responsible for the overall management and coordination for the work required under this contract and shall act as a central point of contact with the Government. The Project Manager shall have the authority to speak for and act for the contractor in all matters related to required services under this contract. The contractor shall include in the designation letter any limitations on the Project Manager’s ability to bind the contractor to changes or adjustments. During normal duty hours, the Project Manager or designee shall respond within 30 minutes notice by phone to communicate with Government personnel. After normal duty hours, the Project Manager or designee must respond by phone within two hours after notification to respond to emergencies.
3.2.2 Work Control. The contractor shall implement necessary work control procedures to ensure timely accomplishment of work requirements, as well as to permit tracking of work in progress. The contractor shall plan and schedule work to assure material, labor, and equipment are available to complete work requirements within the specified time limits. Reports on the status of work requirements shall be provided when requested by the Contracting Officer and the COR.
3.2.3 Interference with Government Business. The contractor shall schedule and arrange work so as to cause the least interference with the normal occurrence of Government business and mission. In those cases where some interference may be unavoidable, the contractor shall notify the COR and be responsible to make every effort to minimize the impact of the interference, inconvenience, etc.
3.2.4 Disruption of Contractor Work Schedule. The contractor shall promptly notify the COR when it appears that Government activities, personnel, or other contractor's projects are hindering the effective execution of work efforts.
4.0 CONTRACTOR TASKS
4.1 Learning Content Management System (LCMS)—Requirements and Specifications The contractor shall provide an LCMS with an annual software license subscription to support an organization of 30 course/content authors. Software subscriptions are inclusive of all accompanying support, including customer training, maintenance, and upgrades. The LCMS shall have the capabilities to expand its licensed course/content authoring end user base to a maximum number not greater than 100 named accounts. Additionally, the LCMS shall meet or exceed the following requirements and specifications:
| Para No |
| Requirements / Specification |
| Description, as Required |
| 4.1.1 |
| Support software subscriptions for 100 subject matter experts and content reviewers as named accounts in the system, but not as authors. |
| 4.1.1.1 |
| Deliver e-Learning for up to 2,000 concurrent learners. |
| 4.1.1.2 |
| Leverage the customer’s Learning Management System (LMS). |
| Leverages LMS through creation of deliverable content that is compliant with Sharable Content Object Reference Models (SCORM), versions 1.2 and 2004, and the Aviation Industry CBT [Computer-Based Training] Committee (AICC). AICC compliant. |
| 4.1.1.3 |
| Support all outputs, including print, instructor-led training, e-learning, and mobile learning. |
| 4.1.1.4 |
| Compliant with SCORM 1.2 and SCORM 2004 Content Packaging and Runtime. |
| The LCMS application shall be able to publish content in the SCORM 1.2 and SCORM 2004 Content Package format with full adherence to the SCORM Runtime model. The system shall create a compliant SCORM Content Package with a compliant XML manifest, all runtime data, all core data elements, and all metadata. |
| 4.1.1.5 |
| Compliant with AICC Content Packaging and Runtime. |
| The LCMS shall be able to publish a conformant dynamic AICC Content Package with all Runtime files. |
| 4.1.1.6 |
| System repository Certification and Accreditation and compliancy with FISMA and FedRAMP. |
| Federal Information Security Management Act (FISMA); Federal Risk and Authorization Management Program (FedRAMP) |
| 4.1.1.7 |
| Support Content Object creation. |
| The LCMS shall be able to create content objects at all levels of aggregation, including raw assets, launchable resources, assignable units, and structured training packages, as in lessons and courses. The LCMS shall be able to tag these objects with default and user-defined metadata that is assigned to the aggregation level and retrieve the objects at any level for reuse and repurposing in any Content Package. |
| 4.1.1.8 |
| Support Content imports. |
| The LCMS shall be able to import raw assets, launchable resources, and SCORM Content Packages, and assign metadata to the asset or component. There shall be a means for linking the object in the repository to its source file and synchronizing changes to the source files with the object in the repository. |
At a minimum the following file types be supported:
| jpg png gif |
| html |
| doc docx |
| swf |
| wav mp3 |
| avi mpg |
| 4.1.2 |
| Support Content viewers. |
| 4.1.2.1 |
| Support development of Instructional System Design (ISD) templates. |
| The LCMS shall have the ability to save content structures that apply instructional design models and reuse them in new lessons and courses. |
| 4.1.2.2 |
| Support page layouts. |
| The control of page layouts shall be modifiable and controllable through Cascading Style Sheets (CSS) which can be saved and reapplied in the system. |
| 4.1.2.3 |
| Support “drag and drop” interface. |
| The assembly of content objects into the course structure and flow shall be done through a visual drag and drop interface that allows for unrestricted changes to the content structure within the boundaries of the defined levels of aggregation. |
| 4.1.2.4 |
| Support live preview. |
| The LCMS shall provide a live preview of content as it is created and include the ability to preview the content in any assigned navigational/look and feel shell. |
| 4.1.2.5 |
| Support Check In/Check Out functionality. |
| Developers in the LCMS shall be able to check out content objects of any type and at any level of aggregation and restrict editing of the objects by anyone but the person who checked them out until the object is checked in to the object repository. |
| 4.1.2.6 |
| Support management of documents. |
| The LCMS shall be able to import 2003, 2007, and 2010 applications of Microsoft Word, HTML, and PDF documents and associate them with training content for viewing from within the course. The LCMS shall provide a method for sharing project documents among the development team. |
| 4.1.2.7 |
| Support an object library. |
| The LCMS shall have a standard library of content object types that can be included in training content through a simple interface that places and configures the object. |
| 4.1.2.8 |
| Support MS PowerPoint import. |
| The LCMS shall be able to import Microsoft PowerPoint content from application versions 2007, 2010, 2013, and subsequent versions, if any, spanning the period of the contract. The LCMS shall be able to parse the PowerPoint content into pages, text, graphics, and audio and create separate content objects for each in the LCMS repository with assigned metadata. The LCMS shall be able to maintain the look and feel of the PowerPoint slide, including layout, font, bullets and standard animations and transitions. |
| 4.1.2.9 |
| Support MS Word import. |
| The LCMS shall be able to import Microsoft Word content from application versions 2007, 2010, 2013, and subsequent versions, if any, spanning the period of the contract. The LCMS shall be able to parse the Word content into pages, sections, text, and graphics, and create separate content objects for each in the LCMS repository with assigned metadata. The LCMS shall be able to maintain the appearance of the Word document including layout, font, and bullets. |
| 4.1.3 |
| Support multiple output formats from a single source. |
| The LCMS shall be able to tag any object within a course structure for inclusion in a specific output format from the single source. Upon publishing, the LCMS shall be able to generate all specified formats from the single source. |
At a minimum, output formats shall include the following:
Online web-based content Instructor-led materials Student workbooks, job aids, and handouts Instructor guides Classroom visual materials
CD-ROM/DVD
Content for mobile devices
| 4.1.3.1 |
| Support dynamic content delivery. |
| The LCMS shall be able to deliver content that is launched by the LMS in a dynamic mode that maintains a live link to the LCMS content repository. This dynamic link shall generate content in real-time from the repository and allow for branching, remediation, and prescriptive and adaptive learning based on student performance and interaction with the content. The LCMS shall support logic and content objects that rely on real-time interaction. The LCMS shall be able to exchange core student data with the LMS in accordance with both SCORM and AICC data models. |
| 4.1.3.2 |
| Support personalization. |
| The LCMS shall have the ability to assign any content component to an individual automatically through the use of profile metadata when the individual accesses the content. The LCMS shall have the ability from the same content file to display only the content that matches the user’s profile or any other defined associated metadata. |
NOTE: The Government requires the ability to transfer any quantity of its programmed 30 named content authoring licenses to individuals within or outside the organization, understanding that each named content authoring license is a subscription for “single-use/single-time” license.
| 4.1.3.3 |
| Support mobile outputs. |
| The LCMS shall have a means for publishing outputs that display on mobile devices, including iOS devices, netbooks, MacBooks, laptops, and Android devices. |
| 4.1.3.4 |
| Support output formats. |
| At a minimum, the LCMS shall be able to publish content to the following formats: |
SCORM 1.2 and 2004
AICC
Online Print – Microsoft Word, PDF PowerPoint
XML
HTML
Mobile Devices
| 4.1.3.5 |
| Develop assessment tools. |
| Provides a wide range of sophisticated assessment types that can be used for practice exams and certifications. |
| 4.1.3.6 |
| Report changes in learning objects. |
| Automatically tracks all changes made to all learning objects. |
| 4.1.3.7 |
| Ability to search for words, phrases, and learning objectives. |
| User shall be able to build and save search queries based on any combination of text XML, properties, workflow data, and metadata. |
| 4.1.3.8 |
| Ability to automatically broadcast changes within a document. |
| Users notified of changes to any shared object. |
| 4.1.3.9 |
| Ability to track changes. |
4.1.4
Ability to define, manage, and track critical training projects.
| 4.1.4.1 |
| Real-time collaboration between team/group development, developers, and subject matter experts. |
| Includes feature to edit and review at the learning object level; allows multiple users to simultaneously make changes and/or review different parts of a course. |
| 4.1.4.2 |
| Ability to meet legal compliance standards. |
| The LCMS software application and the content developed within the LCMS software application shall meet accessibility requirements required under Section 508 of the Rehabilitation Act of 1973 (as amended). Additionally, the software application shall store and track copyright compliance information for source files used in content developed through the software application. |
| 4.1.4.3 |
| Meets internal compliance standards, e.g., APA, Safety, OSHA, NIMS, NFPA, etc. |
| 4.1.4.4 |
| Approves changes instantly across all learning delivery formats. |
| 4.1.4.5 |
| Identifies learning components; e.g., objectives, competencies, lessons, topics, and image maps. |
| 4.1.4.6 |
| Creates multiple templates for textbook and workshop formats. |
Shall include configurable set of templates that support both textbook and workshop formats. Each can include versions for the instructor and student or one common set with separate supplemental materials. Additionally, system shall support templates for multiple training organizations and be able to hastily transition learning objectives from one template to another.
4.2 Deliverables
The contractor shall provide the following deliverables to the Government:
| Para No |
| Deliverable |
| 4.2.1 |
| Implementation Activities (as follows): |
| 4.2.1.1 |
| Kick-off meeting at customer’s location in Anniston, AL. Meet with the COR and other members of the project team within 7 calendar days after award (CDAA) of the contract for a start work meeting and prepare a report on the results of the meeting. |
| 4.2.1.2 |
| Support service – Support the LCMS development and integration into CDP training programs; create and provide support for LCMS business processes and support mechanisms (including defining LCMS roles and responsibilities); create and provide support for quality assurance processes to ensure the LCMS content meets learning content management standards (content items, video, etc.); create and support LCMS templates and reporting; support developers and reviewers for LCMS assistance (approximately 900 hours of support per contract year). This support shall be provided from the contractor’s location. |
| 4.2.1.3 |
| LCMS software installation onto customer’s host server or onto contractor-affiliated server |
| 4.2.1.4 |
| Configuration validation |
4.2.2 Two platform workshops for 10 students (each) at customer’s location in Anniston, AL. Workshops shall include, but shall not be limited, to the following activities:
4.2.2.1 Authoring templates
4.2.2.2 Single source strategy
4.2.2.3 Module authoring practices
4.2.2.4 MS Word print outputs
4.2.2.5 Page layout
4.2.2.6 MS Word import
4.2.2.7 Partitioning
4.2.2.8 PDF outputs
4.2.2.9 Personalization
4.2.3 One Train the Trainer workshop for 10 students at customer’s location in Anniston, AL. Workshop is intended for individuals responsible for teaching selected LCMS operation and administration. Workshop shall include, but shall not be limited, to the following activities:
4.2.3.1 Theme training
4.2.3.2 Personalization
4.2.3.3 Prescriptive Learning
4.2.3.4 Prototype Development
4.2.3.5 SCORM 2004
4.2.3.6 Theme Training
4.2.3.7 Project Management
4.2.3.8 LMS Integration
4.2.3.9 Asset Management
| 4.2.4 |
| Conduct analyses and provide support for application installation, configuration set up, custom code development, theme development, template development, administration mentoring, application consulting, and productivity improvements. |
| 4.2.5 |
| Provide maintenance support for application upgrades, software patches, issue resolution, and other application support functions. |
| 4.2.6 |
| Provide all written reports in electronic format using applications that are compatible with the CDP’s Standard Workstation (Windows 7 and Microsoft Office Applications). Alternative formats shall receive prior approval by the Government. |
| 4.2.7 |
| Phase-out Plan to the CO and COR for evaluation 60 days prior to the last day of the contract. |
4.3 Schedule of Deliverables
| Para No |
| Deliverable |
| 4.3.1 |
| Two platform workshops for 10 students at customer’s location in Anniston, AL. (per paragraph 6.2.2) within 45 days of contract start date. |
| 4.3.2 |
| One Train the Trainer workshop for 10 students at customer’s location in Anniston, AL. within 45 days of contract start date. Workshop is intended for individuals responsible for teaching selected LCMS operation and administration (per paragraph 6.2.3). |
| 4.3.3 |
| Conduct an analysis and provide support for application installation, configuration set up, custom code development, theme development, template development, administration mentoring, application consulting, and productivity improvements within 45 days of contract start date. |
| 4.3.4 |
| Provide maintenance support as required for application upgrades, software patches, issue resolution, and other application support functions. |
| 4.3.5 |
| Provide all written reports in hardcopy and electronic format using applications that are compatible with the CDP’s Standard Workstation (Windows and Microsoft Office Applications). Alternative formats shall receive prior approval by the Government. |
| 4.3.6 |
| Phase-out Plan to the CO and COR for evaluation 60 days prior to the last day of the contract. |
Page | 16 image1.png image2.png
File details come from the government source that posted it. Updated .