These are the procedures of APCI:

• Ideal project pathway through the APCI Institute
• Procedure for updating the Asgardia Projects Database
• Procedure for monitoring project progress, minimizing risks, and optimizing efficiency
• Procedure for assessing project success, documenting lessons learned, and improving best practices
• APCI Control Framework

But first an overview of the abbreviations used and some comments on usage and maintenance.

Abbreviations:

• ACSM = Asgardia Components & Services Marketplace
• ACQia = Institute of Asgardia for the Assurance of Compliance and Quality
• AIS = Asgardia Institute of Standards
• AMIA = Asgardia Manufacturing & Integration Approach
• AMoM = Asgardia Ministry of Manufacturing
• APCI = Asgardia Project Coordination Institute
• APMC = Asgardia Parliamentary Manufacturing Committee
• APMF = Asgardian Project Management Framework
• IpfAMIA = Institute for the Promotion and Facilitation of AMIA

(Back to the top of this page)

Usage and maintenance:

• APCI is maintained by AMoM and APMC;
• APMF is maintained by APCI;
• APCI and APMF are for use by the whole of Asgardia;
• AIS and ACQia are maintained by AMoM;
• AIS and ACQia are for use by the whole of Asgardia;
• IpfAMIA and ACSM are maintained by AMoM and APMC;
• AMIA is maintained by IpfAMIA;
• AMIA, IpfAMIA and ACSM for use by manufacturing activities within the whole of Asgardia.

(Back to the top of this page)

Procedure: Ideal project pathway through the APCI Institute
Ideally, a project follows a number of stages when using APCI:

1. Call for projects
• Launch of the Call for Projects: The project aligns with the criteria of the Institute's call for projects.
• Project Submission: The project proposer submits a detailed proposal using the official form (see the Templates.
2. Pre-selection
• Eligibility Verification: The Institute verifies that the project meets the basic criteria in terms of relevance, feasibility, and alignment with strategic objectives.
• Preliminary Evaluation: The project is ranked based on its impact potential, innovation, and return on investment.
3. Selection and Integration
• Final Selection: The project is selected for integration into the Institute's incubator after a thorough evaluation.
• Welcome Meeting: The project proposer attends a welcome meeting where available resources and services are presented.
• Development of a Personalized Plan: A personalized project plan is developed with clear milestones and specific objectives.
4. Support and Development
• Mentorship and Support: The project receives ongoing support from mentors and experts, with access to technical and financial resources.
• Access to Project Management Tools: The project proposer uses tools provided by the Institute to track progress and manage tasks.
• Regular Reviews: Periodic reviews are conducted to assess progress against set objectives.
5. Implementation
• Completion of Development: The project reaches its final development milestones, with the completion of prototypes or final products.
• Testing and Validation: Rigorous testing is conducted to validate the functionality, safety, and compliance of the project.
• Launch and Deployment: The project is officially launched, with communication campaigns and events to maximize impact.
6. Post-Launch Monitoring
• Monitoring and Evaluation: The project is monitored to assess performance, gather user feedback, and identify possible improvements.
• Ongoing Support: The project proposer continues to receive support for ongoing operations, updates, and maintenance.
7. Closure and Succession
• Final Evaluation: A final evaluation is conducted to measure the project's success against initial objectives.
• Documentation of Lessons Learned: Lessons learned are documented to serve as a reference for future projects.
• Succession or Maintenance Planning: A plan is established for the continuation or transition of the project into a maintenance or succession phase.
8. Communication of Results
• Publication of Results: The project results are published through the Institute's official channels and shared with the Asgardian community.
• Celebration of Success: Events or public announcements are organized to celebrate the project's success.

(Back to the top of this page)

Procedure: Procedure for updating the Asgardia Projects Database
The objective of this procedure is to ensure that the Asgardia Project Database is consistently updated with accurate and current information, reflecting the status, progress, and any changes to ongoing projects.
Steps to Follow:

1. Initiation of Update
• Trigger: An update is triggered by specific events such as project milestones, approval stages, completion of reviews, or any changes in project scope, resources, or timelines.
• Responsibility: The project manager or assigned team member initiates the update process.
2. Accessing the Database
• Log in: The responsible APCI employee logs into the project database using secure credentials.
• Verify Access: Ensure you have the necessary permissions to modify the project records.
3. Inputting New Data
• Select the Project: Navigate to the specific project entry that requires updating.
• Enter New Information: Input the latest information, including:
• project status (e.g., "In Progress," "Completed," "On Hold");
• updated milestones or completion dates;
• changes in project scope or objectives;
• revised budgets, resource allocations, or timelines;
• key decisions or approvals received;
• any issues encountered and their resolutions.
• Attachments: Upload any relevant documents, such as new project plans, reports, or approval letters.
4. Review and Verification
• Double-check Entries: Review all new entries for accuracy and completeness.
• Cross-Verification: If necessary, cross-check with other project documents or team members to ensure information consistency.
5. Save and Confirm Update
• Save Changes: Once all data is entered and reviewed, save the changes in the database.
• Confirmation: Ensure that the system confirms the successful update of the project record.
6. Notification
• Inform Stakeholders: Send a notification to relevant stakeholders (e.g., Steering Committee members, project team) informing them of the update, especially if it involves significant changes.
• Update Log: Record the update in the project log, noting the date, time, and person responsible for the update.

Additional activities are specified in the APCI (Control Framework).

(Back to the top of this page)

Procedure: Procedure for monitoring project progress, minimizing risks, and optimizing efficiency
The objective of this procedure is to ensure that projects are consistently monitored to meet their objectives, minimize risks, streamline efficiency, and optimize resource utilization.
This procedure can be done as an informal review and as a formal Audit.
Steps to Follow:

1. Project Monitoring Initiation
• Kick-off: At the start of the project, establish monitoring protocols and assign roles for ongoing tracking.
• Responsibility: The project manager or assigned monitoring officer initiates the monitoring process.
2. Establish Key Performance Indicators (KPIs)
• Define Objectives: Clearly define the specific objectives and deliverables for the project.
• Set KPIs: Establish measurable KPIs that align with project goals (e.g., milestone completion, budget adherence, resource utilization).
• Document: Record the KPIs and share them with the project team for transparency.
3. Regular Monitoring and Reporting
• Set Review Intervals: Determine regular intervals for monitoring progress (e.g., weekly, bi-weekly, monthly).
• Data Collection: Gather data on project progress against the defined KPIs, including task completion, resource usage, and timeline adherence.
• Status Reports: Prepare regular status reports that highlight progress, achievements, and any deviations from the plan.
4. Risk Identification and Management
• Risk Assessment: Continuously assess potential risks that could impact project objectives, including financial, operational, and technical risks.
• Risk Mitigation Plans: Develop and implement risk mitigation strategies to address identified risks, such as contingency plans or resource reallocation.
• Update Risk Register: Maintain a risk register that documents identified risks, their potential impact, and mitigation actions taken.
5. Streamline Efficiency
• Process Evaluation: Regularly evaluate project processes to identify inefficiencies or bottlenecks.
• Implement Improvements: Introduce process improvements, such as automating tasks, reallocating resources, or adjusting workflows to enhance efficiency.
• Feedback Loop: Establish a feedback loop where team members can suggest improvements and report inefficiencies.
6. Optimize Resource Utilization
• Resource Allocation Review: Regularly review resource allocation to ensure optimal usage, avoiding both underutilization and overloading of resources.
• Adjustments: Reallocate resources as needed to areas where they are most needed or where bottlenecks have been identified.
• Resource Utilization Tracking: Track the utilization of resources, including manpower, budget, and materials, and compare them against the project plan.
7. Regular Progress Meetings
• Conduct Meetings: Hold regular progress meetings with the project team and stakeholders to discuss current progress, risks, and efficiency measures.
• Action Items: Assign action items based on the meeting outcomes to address any issues or opportunities for improvement.
8. Reporting to Stakeholders
• Progress Updates: Provide regular updates to stakeholders, including the Steering Committee, highlighting progress, risks, and resource utilization.
• Decision Points: Present key decision points to stakeholders, especially when significant adjustments or risk mitigation actions are required.
9. Continuous Improvement
• Post-Monitoring Evaluation: After each monitoring cycle, evaluate the effectiveness of the monitoring process itself and make improvements as necessary.
• Lessons Learned: Document lessons learned regarding risk management, efficiency, and resource optimization to improve future projects.
10. Project Closure Review
• Final Assessment: At the end of the project, conduct a final review to assess overall performance against objectives, risks encountered, and resource utilization.
• Documentation: Prepare a final report summarizing the project’s achievements, risks managed, efficiencies gained, and resources used.
• Feedback Incorporation: Incorporate feedback from this review into the project closure process and use it to refine monitoring procedures for future projects.

(Back to the top of this page)

Procedure: Procedure for assessing project success, documenting lessons learned, and improving best practices
The objective of this procedure is to systematically assess and evaluate the success of projects, document lessons learned, and provide recommendations for improvement to enhance future project outcomes and refine existing best practices.
Steps to Follow:

1. Initiate the Evaluation Process
• Trigger: Begin the evaluation process immediately after the project has been completed or a significant milestone has been reached.
• Responsibility: The project manager or an assigned evaluation officer initiates the assessment process.
2. Gather Project Data
• Data Collection: Compile all relevant data from the project, including KPIs, final deliverables, timelines, budget performance, and resource utilization.
• Stakeholder Feedback: Collect feedback from all key stakeholders, including team members, clients, and partners, regarding the project’s execution and outcomes.
• Document Review: Review all project documentation, such as status reports, meeting minutes, and risk registers, to gather comprehensive insights.
3. Evaluate Project Success
• Success Criteria: Evaluate the project against predefined success criteria, including achievement of objectives, adherence to budget and schedule, quality of deliverables, and stakeholder satisfaction.
• Performance Metrics: Analyze performance metrics to determine how effectively the project met its goals, including any deviations and their impacts.
• Outcome Analysis: Assess the final outcomes of the project in terms of its impact, benefits realized, and any unforeseen consequences.
4. Identify and Document Lessons Learned
• Lessons Learned Sessions: Conduct dedicated sessions with the project team to identify key lessons learned, including what worked well and what could be improved.
• Categorize Lessons: Organize the lessons learned into categories, such as project planning, risk management, communication, and resource allocation.
• Documentation: Record the lessons learned in a formal document, ensuring that they are detailed and actionable.
5. Assess and Update Best Practices
• Review Best Practices: Compare the lessons learned with existing best practices to identify areas where current practices can be enhanced.
• Develop Recommendations: Formulate recommendations for updating and improving best practices based on the insights gained from the project evaluation.
• Update Guidelines: Revise existing project management guidelines, templates, and tools to incorporate the new best practices.
6. Prepare and Present the Evaluation Report
• Report Preparation: Compile a comprehensive evaluation report that includes the project’s success assessment, lessons learned, and recommendations for improvement.
• Executive Summary: Include an executive summary highlighting key findings and actionable recommendations.
• Presentation to Stakeholders: Present the evaluation report to relevant stakeholders, including the Steering Committee, to ensure that the findings are understood and agreed upon.
7. Implement Recommendations
• Action Plan: Develop an action plan to implement the recommendations for improvement in future projects.
• Assign Responsibilities: Assign responsibilities for implementing the recommended changes to appropriate team members or departments.
• Monitor Implementation: Track the implementation of recommendations to ensure they are effectively integrated into future project practices.
8. Archive and Share Lessons Learned
• Central Repository: Store the lessons learned document in a central repository accessible to all project managers and team members for future reference.
• Knowledge Sharing: Organize knowledge-sharing sessions or workshops to disseminate the lessons learned and updated best practices across the organization.
9. Continuous Improvement
• Ongoing Review: Regularly review the effectiveness of the updated best practices and make further adjustments as needed based on new project experiences.
• Feedback Loop: Establish a feedback loop where project teams can continuously contribute to the refinement of best practices.

(Back to the top of this page)

Procedure: APCI Control Framework
The APCI Control Framework contains a list of recurring activities of APCI: maintenance, backups, reviews and so on. The frequency of the recurring activities depends on the situation and the context.

1. For all projects in the Asgardia Projects Database
• Scheduled Checks: Regularly check the accuracy and completeness of the information on the project in the Asgardia Projects Database.
• Scheduled Reviews: Conduct regular reviews of the project to ensure whethery the project still complies to APFM.
• Optional Audits: Regularly check whether an Audit should be conducted, to ensure compliance against APMF.
2. Asgardia Projects Database
• Data Backup: Ensure that regular backups of the Asgardia Project Database are performed to prevent data loss.
• Security Compliance: Adhere to all security protocols, ensuring confidentiality, integrity and accessability of the Asgardia Project Database, among others ensuring that only authorized APCI personnel can access and update it.
3. APCI's administration and APCI itself
• Data Backup: Ensure that regular backups of the all APCI data, including its administration, are performed to prevent data loss.
• Security Compliance: Adhere to all security protocols, ensuring confidentiality, integrity and accessability of all APCI data, among others ensuring that only authorized APCI personnel can access and update it.

(Back to the top of this page)